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.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm currently in the section 6.4 of the LFS book (7.9 version) and I have to enter the chroot environtment. It said me that as a "root" user I have to type the following code:
After it is done, the ~# that appears next yo the the root username becomes a /#. Moreover, in the book it says that the bash prompt would say "I have no name!" which do not appear.
My questions are:
1. Am I doing everything ok?
2. How I can check if I am in the chroot environtment?
3. Is it normal that the bash don't say "I have no name"?
It says "I have no name" if there is no root account listed in your chroot environment's /etc/passwd file. That would normally be the case at this stage, since /etc/passwd is created within the chroot environment. Did you perhaps copy an existing passwd file into your new setup?
How do you know you are in chroot? Just list some top-level directories. For example ls /bin will show an empty or almost empty directory in your new environment. If you are still in the old one, the directory will be full of files.
You do know that you need to be root (or use sudo) to chroot?
I do not why but the /etc/passwd file was already created. I think it might be because of the kernel I'm using, but I am not sure. I deleted the file and then, following the instructions in the book, I re-create it and it worked.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.