On 07/06/10 10:30, littlebat wrote:
>>> Ubuntu bash has a bug, even if I specified --rcfile, it still read
>>> /etc/bash.bashrc.
>>
>> That's because /etc/profile does it explicitly:
>
> I have replaced bash in Ubuntu with the bash comes with LFS6.6. I found there
> isn't a system-wide .bashrc fil
> > Ubuntu bash has a bug, even if I specified --rcfile, it still read
> > /etc/bash.bashrc.
>
> That's because /etc/profile does it explicitly:
I have replaced bash in Ubuntu with the bash comes with LFS6.6. I found there
isn't a system-wide .bashrc file(just like /etc/bash.bashrc in Ubuntu 10.
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
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
> 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 +
On Friday 04 June 2010 04:40:51 littlebat wrote:
>
> cat > ~/.bash_profile << "EOF"
> exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash
> EOF
>
Try adding "--noprofile --rc ~lfs/.bashrc" to the bash command. Or just
add "--noprofile --norc" and set everything in the env command.
There
On Fri, Jun 4, 2010 at 1:40 AM, littlebat wrote:
> This issue was posted onto lfs-support mailing list yesterday (see:
> http://linuxfromscratch.org/pipermail/lfs-support/2010-June/038814.html ),
> unluckly I disabled the mail delivery of LFS mailing list some days ago, so I
> can't continue di
This issue was posted onto lfs-support mailing list yesterday (see:
http://linuxfromscratch.org/pipermail/lfs-support/2010-June/038814.html ),
unluckly I disabled the mail delivery of LFS mailing list some days ago, so I
can't continue discuss it on the lfs-support mailing list. And, I consider
