> Sent: Friday, January 17, 2020 at 2:20 PM > From: "Ken Moffat via blfs-support" <[email protected]> > To: "BLFS Support List" <[email protected]> > Cc: "Ken Moffat" <[email protected]> > Subject: Re: [blfs-support] Some BLFS Build Problems > > On Thu, Jan 16, 2020 at 03:14:46PM -0700, Alan Feuerbacher via blfs-support > wrote: > > > > You're right about the permissions problem: I've been building and testing > > as root during this entire build. I changed the owner of all appropriate > > files in my LFS system from root:root to lfs:wheel, since lfs is > > unprivileged, and then built the offending packages again. All ok now. > > > > This brings up something I'm a bit confused about: Several years ago one of > > you LFS staff guys suggested that I build everything as root, since that was > > his own practice, even though not recommended by LFS staff. But it's now > > clear to me that the staff recommendations really ought to be followed, > > which I'm doing from now on. > > > Possibly me: for my own normal builds I mostly stay as root. There > are a few packages which *have to* be built as a normal user. But > then I only run tests for very few packages on my own builds. > > My view is that the perceived safety benefits of using sudo will not > buy me very much support when I'm in "deep build" mode ;-) OTOH, > backups often halp. > > For kernels, even at the end of an LFS build, I _do_ usually build > as a normal user (lfs at the end of LFS, my normal user for later > kernel upgrades). > > And for when I'm editing, I follow the book: build as a user, run > tests as a user where appropriate, DESTDIR or similar to see what > gets installed. > > ĸen > -- > The politics of wizardry were either very simple, and resolved by > someone ceasing to breathe, or as complex as one ball of yarn in a > room with three bright-eyed little kittens. - Unseen Academicals > -- > http://lists.linuxfromscratch.org/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page >
Hello, I too build BLFS as root. I never run the test suites as I refuse to over double the time it takes to install a new lfs/blfs system. I now only use jhalf to build LFS, and as of my last BLFS build, I now use jhalf to create the "cut down" linear version of the book. When I worked for a webhosting company and I was setting up 6 production servers simultaneously I was using root on red hat servers. As they were using cpanel, it was easier and acceptable to the company for me to use root the entire time. I am not one who buys into the crap that developers try to force down peoples throats regarding root privs. They do not own the hardware that people are installing on. It is controlled by the owner of that hardware. If a company wants to use root, then developers have no right to force their own opinions on others. As Ken said, the only exception I make to that is when a package absolutely has to be built as a normal user. For the most part, if people follow the book exactly, without any deviations they will end up with a fully functioning system at the end. The key to a successful build is to read the instructions carefully, and copy and paste the commands exactly as written. Once you have successfully built BLFS a couple of times, then you can experiment a little. Regards, Christopher. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
