Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Damn, I meant for that to be a lower case 'a', but it doesn't matter as you've found the solution - you should be running these commands as root. I'm not sure what you're asking at the end, but when you create files as root, they will be owned by the user "number 0" (usually called root). There shouldn't be any confusion between the systems, as that user will be "number 0" in both systems. Once you get to step 6.3 and start using the chroot command, things should become a bit more clear.
Ahh, I see now. No, as long as you make sure you are in the chroot environment before you run anything, your FC3 host shouldn't be affected in any way. If you log out or reboot, be sure to rerun the chroot command before you continue with LFS.
Nope, you shouldn't need the lfs user any more (but don't delete it yet, in case I've forgotten something). The instructions for the chroot command are in 6.3, and once you reach that point, you should always make sure you re-run that command (as root, not lfs) before continuing with your LFS instructions.
In other words:
1) From this point on, ALWAYS log in as root, never as lfs (unless told otherwise)
2) When you get to section 6.3, bookmark it, and re-run the chroot command any time you've had to log in to continue your build, right up until you get your LFS system to boot.