On Mon, Aug 18, 2014 at 6:03 AM, Rich Shepard <[email protected]> wrote:
> On Sun, 17 Aug 2014, King Beowulf wrote: > > > 1. [rant] You should be true root for this to properly work. Not "sudo" > > nonsense. A true root user can r/w anything to/from anywhere. Using sudo > > you are still in a user shell not a root shell. This can prevent you from > > accessing various files. IMHO, this is the greatest injustice that the > > *buntus and others have foisted onto the Linux public. [/rant] > > Also, operating as root in a user login shell can create problems when > building from source. Those problems are avoided running the build from a > root login shell (su -). > Never build as root, period. Build as a user, install as root (if you must - personally, I prefer to install to user-owned directories if I'm building from source - saves me ever having to be root at any point in the process (unless setuid is needed, of course). The login shell versus simple interactive shell would have zero effect on builds, unless for some reason they depend on utmp/wtmp user login records. The only other difference in login versus non-login interactive shells is that the former sources .profile/.bash_profile, whereas the latter sources ~/.bashrc. But normally you'd have the former source the latter anyway. You're a lot more likely to run into problems _editing_ files with sudo vs su, than with building something from source; in that case, it'd be because su will set HOME by default, whereas usually sudo requires you to pass -H if you want it set. That's usually a far bigger difference in most people's environments than login vs non-login shell. -mjc _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
