From: | Rich Freeman <rich0@g.o> | ||
---|---|---|---|
To: | gentoo-user@l.g.o | ||
Subject: | Re: [gentoo-user] Failure with cfg-update:* invalid key... try again: bash: readkey: command not found | ||
Date: | Sat, 24 Jan 2015 13:14:59 | ||
Message-Id: | CAGfcS_kLF1eqh9SdJWqrkjnxZ4xuMBwqRQd6YRyzWRatmBeLTw@mail.gmail.com | ||
In Reply to: | [gentoo-user] Failure with cfg-update:* invalid key... try again: bash: readkey: command not found by Meino.Cramer@gmx.de |
1 | On Sat, Jan 24, 2015 at 3:34 AM, <Meino.Cramer@×××.de> wrote: |
2 | > Hi, |
3 | > |
4 | > after submitting |
5 | > |
6 | > cfg-update -u |
7 | > |
8 | > I got |
9 | > |
10 | > * invalid key... try again: bash: readkey: command not found |
11 | > |
12 | > printed on the screen endlessly. |
13 | > |
14 | > How can I scuccessfully use cfg-update as before? |
15 | > What did I wrong? |
16 | |
17 | Update to cfg-update 1.8.9. Go figure, cfg-update was one of the few |
18 | programs out there that actually used the functionality exploited by |
19 | shellshock... |
20 | |
21 | -- |
22 | Rich |