After installation using the LFS-7.3 book, the reboot process is not
working, with error messages about /run being a read-only filesystem
when attempting to execute /etc/rc.d/rcS.d/S00mountvirtfs

I noticed that rcsysinit.d is not present in /etc/rc.d. Are the scripts
that should be in this directory responsible for re-mounting the root
filesystem as rw?
According to the book, it should be present. Should it have been
installed by the lfs-bootscripts-20130123 package or have I missed seom
vital instruction?

"The intialization file above will instruct rc to run all the scripts
starting with an S in the /etc/rc.d/rcsysinit.
d directory followed by all the scripts starting with an S in the
/etc/rc.d/rc?.d directory where the question
mark is specified by the initdefault value."

My current /etc/rc.d contents:
root:/etc/rc.d# ls -l
total 36
drwxr-xr-x 2 root root 4096 May 28 18:43 init.d
drwxr-xr-x 2 root root 4096 May 28 18:43 rc0.d
drwxr-xr-x 2 root root 4096 May 28 18:43 rc1.d
drwxr-xr-x 2 root root 4096 May 28 18:43 rc2.d
drwxr-xr-x 2 root root 4096 May 28 18:43 rc3.d
drwxr-xr-x 2 root root 4096 May 28 18:43 rc4.d
drwxr-xr-x 2 root root 4096 May 28 18:43 rc5.d
drwxr-xr-x 2 root root 4096 May 28 18:43 rc6.d
drwxr-xr-x 2 root root 4096 May 28 18:43 rcS.d

/etc/inittab:
# Begin /etc/inittab
id:3:initdefault:
si::sysinit:/etc/rc.d/init.d/rc S

l0:0:wait:/etc/rc.d/init.d/rc 0
l1:S1:wait:/etc/rc.d/init.d/rc 1
l2:2:wait:/etc/rc.d/init.d/rc 2
l3:3:wait:/etc/rc.d/init.d/rc 3
l4:4:wait:/etc/rc.d/init.d/rc 4
l5:5:wait:/etc/rc.d/init.d/rc 5
l6:6:wait:/etc/rc.d/init.d/rc 6

ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

su:S016:once:/sbin/sulogin

1:2345:respawn:/sbin/agetty --noclear tty1 9600
2:2345:respawn:/sbin/agetty tty2 9600
3:2345:respawn:/sbin/agetty tty3 9600
4:2345:respawn:/sbin/agetty tty4 9600
5:2345:respawn:/sbin/agetty tty5 9600
6:2345:respawn:/sbin/agetty tty6 9600
# End /etc/inittab

Thanks,
- Geoff
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to