No, this isn?t a case of multi partitions, clusters, or anything silly. I just want a set of aliases loaded for su. /root/.bash_profile isn?t loading, and there isn?t any obvious choice as to where the loaded .bash* were loading from.> On May 13, 2019, at 9:11 AM, Stephen John Smoogen <smooge at gmail.com> wrote: > > While moving /root to /home/root is done in someplaces, it only works if > /home is not on a different partition. If you put /home on a different > partition you will find all kinds of weird behavior happening on start up.Cheers, Bee
Once upon a time, Bee.Lists <bee.lists at gmail.com> said:> No, this isn?t a case of multi partitions, clusters, or anything silly. I just want a set of aliases loaded for su. /root/.bash_profile isn?t loading, and there isn?t any obvious choice as to where the loaded .bash* were loading from..bash_profile will not be read when you just run "su", because .bash_profile is read in a login shell, and "su" does not create a login shell. .bashrc will be read (and is really where aliases belong anyway), or you can "su -" to create a login shell. -- Chris Adams <linux at cmadams.net>
OK that?s exactly what I just was questioning. The documentation wasn?t clear on the ?man bash? (INVOCATION) notes. So I entered my inclusion of my aliases file (it?s my own) inside .bashrc. Thank you> On May 13, 2019, at 1:31 PM, Chris Adams <linux at cmadams.net> wrote: > > .bash_profile will not be read when you just run "su", because > .bash_profile is read in a login shell, and "su" does not create a login > shell. > > .bashrc will be read (and is really where aliases belong anyway), or you > can "su -" to create a login shell.Cheers, Bee