Re: dhclient in LFS

2008-06-02 Thread Petr Ovtchenkov
On Monday 26 May 2008 22:37:33 Ken Moffat wrote: > On Mon, May 26, 2008 at 07:19:49AM -0600, Gerard Beekmans wrote: > > > > > Why dhclient over dhcpcd? I don't really care much, but my argument is > > > > > Not real reason why I mentioned one over the other. dhclient is easier > > to type th

Re: cp foo{,.bak} not always supported

2008-06-02 Thread Alexander E. Patrakov
2008/6/1, Gilles Espinasse <[EMAIL PROTECTED]>: > cp configure{,.bak} > cp: missing destination file operand after `configure{,.bak}' > Try `cp --help' for more information. This simply can't happen if the user follows the book to the letter. Look at http://www.linuxfromscratch.org/lfs/view/devel

Re: cp foo{,.bak} not always supported

2008-06-02 Thread Bryan Kadzban
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Bruce Dubbs wrote: > My point is that this is an unusual user problem and it is not > appropriate for the book to address it. Ah. Yes, I'd completely agree with that. :-) (I was trying to suggest that the "set -B" be added to the IPCop scripts

Re: LFS Future Braindump

2008-06-02 Thread Christian Wurst
On Thu, May 29, 2008 at 9:47 AM, Randy McMurchy <[EMAIL PROTECTED]> wrote: > Christian Wurst wrote these words on 05/28/08 06:55 CST: >> Well, I disagree here. The FAQ is very technical in nature, and thus >> takes some time to understand what the package does. > > I snipped your explanation and so

glibc @BASH@ thing

2008-06-02 Thread Mateusz Grotek
Hi. There is some simple solution to make ldd.bash.in work with dash, and other shells. Change this line: BEGIN if set -o pipefail 2> /dev/null; then END to these two lines: BEGIN if set -o | grep pipefail 1> /dev/null 2> /dev/null; then set -o pipefail 2> /dev/null END and that's all. With th

Re: cp foo{,.bak} not always supported

2008-06-02 Thread Gilles Espinasse
- Original Message - From: "Bruce Dubbs" <[EMAIL PROTECTED]> To: "LFS Developers Mailinglist" Sent: Monday, June 02, 2008 3:39 AM Subject: Re: cp foo{,.bak} not always supported > Bryan Kadzban wrote: > > > I strongly suspect the user was running either sh (which was not linked > > to

Re: glibc @BASH@ thing

2008-06-02 Thread Bruce Dubbs
Mateusz Grotek wrote: > Hi. There is some simple solution to make ldd.bash.in work with dash, > and other shells. > Change this line: > BEGIN > if set -o pipefail 2> /dev/null; then > END > to these two lines: > BEGIN > if set -o | grep pipefail 1> /dev/null 2> /dev/null; then > set -o pipefai