(related to bug #1627) I noticed this too. It results from the new /etc/profile checking $SHELL for being "/bin/bash" which it isn't after the changeroot (it is "/bin/sh" although I changerooted with chroot /mnt/gentoo /bin/bash). So a simple 'export SHELL="/bin/bash"' fixes the problem. But there should be a better solution... tigor
Weird.
Near as I can tell, the problem is actually that bash itself won't even bother with /etc/profile *unless it is started as a login shell*. Thus, chroot /mnt/gentoo /bin/bash --login Works just great. Another possible solution is to do the following: 1. source /etc/profile in ~/.bashrc 2. in /etc/profile, set an environment variable that can be checked to avoid double-sourcing, in the case of a login shell (which would also source ~/.bash_profile which itself often sources ~/.bashrc) I can offer suggestions on such an alteration to /etc/profile, but the real root cause is bash not being started with --login
Additional Comments: make sure the "source /etc/profile" line takes place **after** the "export PS1=..." line in the (default) .bashrc Mine looks like this: # ~/.bashrc: executed by bash(1) for non-login shells. export PS1='\h:\w\$ ' umask 022 source /etc/profile # You may uncomment the following lines if you want `ls' to be colorized: # export LS_OPTIONS='--color=auto' # eval `dircolors` # alias ls='ls $LS_OPTIONS' # alias ll='ls $LS_OPTIONS -l' # alias l='ls $LS_OPTIONS -lA' # # Some more alias to avoid making mistakes: # alias rm='rm -i' # alias cp='cp -i' # alias mv='mv -i' And either bash, bash -i, or bash --login works. Also note that, as root, I copied the .bash_profile and .bashrc files out of /etc/skel As can be seen, I modified the .bashrc to source /etc/profile
