Re: Changes in the LFS build procedure

2008-06-03 Thread Bruce Dubbs
Jeremy Huntwork wrote: > Bruce Dubbs wrote: >> What this means is that the process to update bootscripts is now to change >> the appropriate file in BOOK/bootscripts and update the entity in >> packages.ent >> >> To have the current date. >> Likewise, for udev-config, update the files in BOO

Re: Changes in the LFS build procedure

2008-06-03 Thread Jeremy Huntwork
Bruce Dubbs wrote: > What this means is that the process to update bootscripts is now to change > the > appropriate file in BOOK/bootscripts and update the entity in packages.ent > > To have the current date. > > Likewise, for udev-config, update the files in BOOK/udev-config and the entity

Changes in the LFS build procedure

2008-06-03 Thread Bruce Dubbs
I have just made some relatively large changes in the LFS build procedure. 1. Both bootscripts and udev-config directories have been moved to be under the BOOK directory. 2. The Makefile has been updated to automatically generate the bootscripts and udev-config tarballs. The entities that speci

Re: glibc @BASH@ thing

2008-06-03 Thread Petr Ovtchenkov
On Tuesday 03 June 2008 15:18:39 Mateusz Grotek wrote: > > > Yes. I understand that. So i'm trying to send this patch to libc-alpha > too. I donno if glibc utilities would work with dash (without bash > installed). But if it is possible, we could give users choice which > shell they like. Pe

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

2008-06-03 Thread Dan Nicholson
On Mon, Jun 2, 2008 at 12:29 AM, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote: > 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 us

Re: glibc @BASH@ thing

2008-06-03 Thread Gilles Espinasse
Selon Mateusz Grotek <[EMAIL PROTECTED]>: > Yes. I understand that. So i'm trying to send this patch to libc-alpha > too. I donno if glibc utilities would work with dash (without bash > installed). But if it is possible, we could give users choice which > shell they like. People from ubuntu made d

Re: glibc @BASH@ thing

2008-06-03 Thread Mateusz Grotek
Gilles Espinasse pisze: > Selon Mateusz Grotek <[EMAIL PROTECTED]>: > > >> Bruce Dubbs pisze: >> >>> Mateusz Grotek wrote: >>> >>> > ... > and that's all. With this fix it works correctly and this sed thing if LFS book isn't needed. You could ask why this solution is bet

Re: glibc @BASH@ thing

2008-06-03 Thread Gilles Espinasse
Selon Mateusz Grotek <[EMAIL PROTECTED]>: > Bruce Dubbs pisze: > > Mateusz Grotek wrote: > > ... > >> and that's all. With this fix it works correctly and this sed thing if > >> LFS book isn't needed. You could ask why this solution is better than fix? > >> It is, because it enables you not to use

Re: glibc @BASH@ thing

2008-06-03 Thread Mateusz Grotek
Bruce Dubbs pisze: > 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> /