Linux From Scratch This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
11-10-2002, 11:20 AM
|
#1
|
LQ Newbie
Registered: Oct 2001
Location: Raleigh, NC, USA
Distribution: RH7.2 + LFS
Posts: 21
Rep:
|
LFS Book Chapter 6 - 1st step (chroot to /mnt/lfs) doens't work
6 months or so back I installed LFS 3.1. Everything was cool until I reached the point where I couldn't get networking to work.
Here I am 6 months later ... and I figured I'd just start again from 'scratch'. I downloaded the cvs packages and got started. I've tried a couple iterations and am bombing at the same spot,at least diverging from the instructions in the book.
The basic problem is the first step I take in chapter 6: 'chroot'
to /mnt/lfs doens't appear to work. I'm not that experienced with the chroot command, but I figure after performing the command, your shell will interpret your new root as the NEWROOT specified in your command. In other works, after doing a 'chroot /mnt/lfs ..', if you 'cd' to '/' you should actually be where '/mnt/lfs' was before you chrooted.
The problem I'm having is that after performing the chroot, my '/' is still where it originally was. Thus, all the subsequent commands in the instructions don't work because the '/' given in the command is with respect to the chrooted environment (i.e. old '/mnt/lfs') ... and it appears I haven't successfully chrooted, so the instructions as posted no longer work.
I considered modifying the commands subsequent to the chroot command to treat /mnt/lfs as my '/', but I figured I should find out why this happened instead.
Any pointers, advice would be appreciated.
I looked for some other posts regarding chroot problems and ran the ldd command as suggested in another post. The response was "not a dynamic executable" which was not surprising because I pretty much followed the LFS book instructions to a 'T'.
Thanks
p.s. I'm really eager to get an LFS system up and running, so I'm hoping for some help here ... otherwise I'll be forced to abandon once again.
p.p.s. I'm running from RH7.2. All linux partitions are ext3 except /mnt/lfs which was created with the mke2fs command as detailed in the instructions. Don't see why this would affect chroot, but felt it was some configuration info I should include in the post.
|
|
|
11-10-2002, 11:28 AM
|
#2
|
Senior Member
Registered: Jul 2001
Location: 406292E 290755N
Distribution: GNU/Linux Slackware 8.1, Redhat 8.0, LFS 4.0
Posts: 1,004
Rep:
|
What does echo $LFS give you?
A hint, copy and paste the command from the HTML version into the terminal.
|
|
|
11-10-2002, 11:40 AM
|
#3
|
LQ Newbie
Registered: Oct 2001
Location: Raleigh, NC, USA
Distribution: RH7.2 + LFS
Posts: 21
Original Poster
Rep:
|
First of all, thanks for the reply.
$LFS is '/mnt/lfs' as it should be.
The tricky thing about C&Ping this command was the following:
1) First of all, 'chroot' is not found unless I explicitly give it the path '/usr/sbin/chroot' so I couldn't cut&paste.
Hmmm, I guess that was the main reason. The last command in that chunk didn't work either '/static/bin/bash --login' ... but that's because it's looking at my RedHat root instead of $LFS.
Anything else?
|
|
|
11-11-2002, 04:39 AM
|
#4
|
Senior Member
Registered: Nov 2002
Location: British Columbia, Canada
Distribution: Gentoo x86_64; FreeBSD; OS X
Posts: 3,764
Rep:
|
This is a noodle-scratcher!
A few ideas:
make sure you use host distro chroot, not LFS chroot
make sure you are in a directory above $LFS when you chroot
stop using $LFS variable after chrooting
make sure you are logged in as root when chrooting
one thing I know fershur:
"I considered modifying the commands subsequent to the chroot command to treat /mnt/lfs as my '/', but I figured I should find out why this happened instead."
This will not work because all the packages you install after will be linked to your host libraries etc. . .And your LFS will never work independantly.
Is chroot giving you an error message, or just failing silently?
|
|
|
11-12-2002, 03:06 PM
|
#5
|
Member
Registered: Jul 2002
Location: Santa Cruz, CA
Distribution: lfs
Posts: 538
Rep:
|
If you are taking some of the stuff out of the chroot command that the book specify's, then you might run into problems. the "/static/bin/env -i" part clears all of your current environment variables, and then the command goes on to give you new ones. If you don't clear the environment, it might cause your /static/bin/bash search to stay in your base distro's filesystem.
|
|
|
11-12-2002, 06:08 PM
|
#6
|
LQ Newbie
Registered: Oct 2001
Location: Raleigh, NC, USA
Distribution: RH7.2 + LFS
Posts: 21
Original Poster
Rep:
|
resolved...
because I couldn't cut & paste directly from the book, I entered the command manually not taking into account the fact that the '\' was a continuation character. So my chroot ended at the first line.
It's working now.
My bad. Thanks guys.
|
|
|
11-07-2003, 09:21 PM
|
#7
|
LQ Newbie
Registered: Oct 2003
Posts: 27
Rep:
|
ok i seem to have a problem with the same step when i run the chroot i get this
chroot: /tools/bin/env: No such file or directory
i am using the 5.0 version of the book and have cut and pasted the same exact text
chroot $LFS /tools/bin/env -i \
HOME=/root TERM=$TERM PS1='\u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
/tools/bin/bash --login
i am running slackware 9.0 and i do get the /mnt/lfs when i run lfs
thanks
|
|
|
11-20-2003, 02:47 PM
|
#8
|
Member
Registered: Sep 2003
Location: South East, PA
Distribution: Slackware -current
Posts: 36
Rep:
|
[removed: my own stupidity]
Last edited by kipp; 11-20-2003 at 08:33 PM.
|
|
|
10-24-2004, 09:36 PM
|
#9
|
LQ Newbie
Registered: Jul 2004
Location: St. Louis, Missouri
Distribution: Fedora Core 1 / 2
Posts: 3
Rep:
|
CHROOT Fails in Chapter 6
Apparently this is a real obvious situation, but I have yet to figure it out for myself. What was the solution to this problem?
Code:
/tmp/lfs > ls -alh
total 64K
drwxrwxrwx 15 root root 4.0K Oct 24 20:29 .
drwxrwxrwt 10 root root 12K Oct 24 21:15 ..
drwxr-xr-x 2 root root 4.0K Oct 24 19:43 bin
drwxrwxr-x 3 root root 4.0K Oct 24 20:29 dev
drwxr-xr-x 2 root root 4.0K Oct 23 21:34 etc
drwxr-xr-x 4 root root 4.0K Oct 23 21:37 i686-pc-linux-gnu
drwxr-xr-x 25 root root 4.0K Oct 24 16:58 include
drwxr-xr-x 8 root root 4.0K Oct 24 19:43 lib
drwxr-xr-x 3 root root 4.0K Oct 24 17:12 libexec
dr-xr-xr-x 98 root root 0 Oct 20 14:05 proc
drwxr-xr-x 2 root root 4.0K Oct 24 19:43 sbin
drwxr-xr-x 15 root root 4.0K Oct 24 17:16 share
drwxrwxrwx 8 root root 4.0K Oct 24 18:46 sources
drwxrwxrwx 2 root root 4.0K Oct 23 06:32 tools
drwxr-xr-x 2 root root 4.0K Oct 24 16:22 var
/tmp/lfs >
cd /
/ > chroot /tmp/lfs /bin/env -i \
HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
/bin/bash --login +h
chroot: /bin/env: No such file or directory
/ >
Is it not true that the paths are relative to the new root and not the old?
I'm sure scratching my head! Thanks in advance for any helpful nudge!
|
|
|
10-25-2004, 10:11 PM
|
#10
|
LQ Newbie
Registered: Jul 2004
Location: St. Louis, Missouri
Distribution: Fedora Core 1 / 2
Posts: 3
Rep:
|
Ok, here's what I figured out -- on my own:
In my directory listing, one would note a tools directory. Wax that sucker and create a symlink pointing to the root of the file system as follows:
ln -s / /mnt/lfs/tools
chroot commands can now find their libraries and all works as advertised.
|
|
|
03-13-2006, 04:11 AM
|
#11
|
LQ Newbie
Registered: Mar 2006
Posts: 1
Rep:
|
hello for all
i'm facing the same problem as the rest, when t completed chapter5, i reached the chroot:
cd $LFS
chroot $LFS /usr/bin/env -i HOME=/root \
TERM=$TERM /bin/bash --login
i typed this command,($LFS=/mnt/lfs) and the result is:
chroot: /bin/bash: No such file or directory
i'm hoping to get the help and the reason of this problem
note:i use fedora core3 dist. i work with LFS version 3.1
thanks
|
|
|
03-15-2006, 12:31 AM
|
#12
|
LQ Newbie
Registered: Mar 2006
Posts: 1
Rep:
|
For me help:
chroot "$LFS" /tools/bin/env -i \
HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
/tools/bin/bash --login +h
|
|
|
All times are GMT -5. The time now is 07:47 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|