From: Chris Staub <[EMAIL PROTECTED]> >> ptys. I've checked the things in the FAQ, and most seem OK. I >> depart from the book by installing /dev on the real FS, rather >>than a tempfs.
>What exactly do you mean by that last sentence? Exactly? This is my version of Ch6.8, my script ch6-04-dev: #!/bin/bash -e # Build /dev echo "Estimated build time: 0.0SBU" git `basename $0` && #PGR LFS makes these permanent for booting #PGR mknod -m 600 /dev/console c 5 1 && *1 #PGR mknod -m 666 /dev/null c 1 3 && *2 #PGR To allow multiple session building, use real /dev #PGR mount -nvt tmpfs none /dev && *3 mknod -m 622 /dev/console c 5 1 && *4 ...8<... *1: That goes on the real /dev for booting. (see *4) *2: This has already been made because git requires it for previous steps *3: My 1 SBU is >25min. (Building glibc took over 5 hours.) This is going to require multiple build sessions. So I'm populating the devices Ch6 requires in the real /dev rather than a tempfs, so they'll be there for the next session. *4: This goes to the real /dev for Ch6 building. Eventually udev will take over, but that's a long ways down the road. >I'm not seeing DEVPTS in my kernel config either, but I clearly have >support for it. It's possible it's enabled by default on newer kernels. >The most likely cause is that you simply didn't mount /dev/pts inside >the chroot. -- From: "Dan Nicholson" <[EMAIL PROTECTED]> >Looks like you're not mounting devpts in /mnt/lfs/dev/pts (or shm). >You need to mount /proc /sys /dev/shm and /dev/pts in $LFS. These are >actual filesystems (see your host's fstab). I thought I was covering that with this from /mnt/lfs/root/.bash_profile, since the chroot starts a login shell: #!/bin/bash #PGR remounts for LFS-6.1.1 Ch6 building if ! grep /dev/pts /proc/mounts >/dev/null ; then mount -vt devpts -o gid=4,mode=620 none /dev/pts fi When I got in the chroot and looked at /proc/self/mounts, it looked like they were already mounted. You're saying that once I get into the chroot, I need to mount or umount/mount them all again? I'm confused about what the host does and what is done within the chroot--how much the chroot sees of the hosts environment. I need mounts inside the chroot so it uses everything on ITS /proc, /sys, shm & pts without connection to the host? What I'm finding are little mistakes in my build scripts now and then, so even within a build session, sometimes I have to logout of the chroot to go edit a script, then come back. Not being sure what's still there, I protected the mount with checking /proc/mounts re your previous suggestion. I should add similar statements for /sys, shm & pts? Paul Rogers ([EMAIL PROTECTED]) http://www.xprt.net/~pgrogers/ Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
