Some LFS 6.5 -> 6.6 Inconsistencies

2010-06-06 Thread Tim Burress
Hello, I've just finished upgrading from LFS 6.5 to 6.6 and there were a few small inconsistencies I noticed along the way: (1) When building make, the book calls for a patch called make-3.81-upsream_fixes-1.patch, but this is not available in the FTP archive (or at least the mirror I used).

Re: the issue of environment value $PS1 set under Ubuntu 10.04

2010-06-06 Thread Simon Geard
On Sun, 2010-06-06 at 17:56 +0800, littlebat wrote: > Base on my knowledge, I found the env command can't set like "set +h" > or "umask 022" those are set in the file .bashrc. I don't know of any way of setting umask that way, but any option you can pass to "set" can also be passed to "bash" itsel

Re: perl, gdbm and perl's obsequious help

2010-06-06 Thread Tobias Gasser
> And this may very well be the issue, since nobody has reported this > problem when building LFS before. not quite true! i had issues with perl, but everyone on this list told me i made a mistake. as i couldn't track the problem down to it's realy cause, i just gave up argueing. and the docs a

Re: the issue of environment value $PS1 set under Ubuntu 10.04

2010-06-06 Thread Bruce Dubbs
littlebat wrote: >> Try adding "--noprofile --rc ~lfs/.bashrc" to the bash command. Or >> just > > Ubuntu bash has a bug, even if I specified --rcfile, it still read > /etc/bash.bashrc. That's because /etc/profile does it explicitly: PS1='\...@\h:\w\$ ' if [ -f /etc/bash.bashrc ]; then . /e

Re: the issue of environment value $PS1 set under Ubuntu 10.04

2010-06-06 Thread littlebat
> Try adding "--noprofile --rc ~lfs/.bashrc" to the bash command. Or just Ubuntu bash has a bug, even if I specified --rcfile, it still read /etc/bash.bashrc. > add "--noprofile --norc" and set everything in the env command. Base on my knowledge, I found the env command can't set like "set +