* Calculating service dependencies gawk: /lib/rcscripts/awk/gendepends.awk:440: (FILENAME=- FNR=170) fatal: can't redirect to `/var/lib/init.d/deptree' (Read-only file system) ln: cannot remove `/var/lib/init.d/started/checkroot': Read-only file system ln: creating symbolic link `/var/lib/init.d/started/hostname' to `/etc/init.d/hostname': Read-only file system ln: cannot remove `/var/lib/init.d/started/modules': Read-only file system ln: creating symbolic link `/var/lib/init.d/started/checkfs' to `/etc/init.d/checkfs': Read-only file system ln: creating symbolic link `/var/lib/init.d/started/localmount' to `/etc/init.d/localmount': Read-only file system /sbin/rc: line 469: /var/lib/init.d/softlevel: Read-only file system mkdir: cannot create directory `/var/lib/init.d/failed': Read-only file system /sbin/runscript.sh: line 32: /var/lib/init.d/softlevel: No such file or directory This happens with a varying amount of the ln lines upon boot. depscan.sh doesn't output anything nor fix the problem.. from the looks of things, it looks like the filesystem is still mounted readonly however this happens after "remounting root filesystem read-write". All of the scripts in the error still execute after this depcheck is over however, so it still boots. Started happening after the emerge of the new portage. Marking critical, although the system still boots; something as scary as trying to write to a readonly filesystem when it is supposedly already readwrite is kind of bad. Reproducible: Always Steps to Reproduce: 1. 2. 3. # emerge info Portage 2.0.50-r11 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.6.8-blut1) ================================================================= System uname: 2.6.8-blut1 i686 mobile AMD Athlon(tm) XP2500+ Gentoo Base System version 1.5.3 distcc 2.17 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d acpi aim alsa apache2 arts avi berkdb bitmap-fonts cdr crypt cups dba dvd encode esd faad flac flash foomaticdb gb gd gdbm gif gimp-print gnome gnutls gphoto2 gpm gstreamer gtk gtk2 gtkhtml icq imagemagick imlib jabber jack java jpeg kde ladcca libg++ libwww mad mbox mikmod mmx motif mozsvg mpeg msn mysql ncurses nls nptl offensive oggvorbis opengl pam pcmcia pdflib perl php png python qt quicktime readline samba sdl silc slang snmp socks5 spell sse ssl svga tcltk tcpd tiff truetype trusted usb wmf wxwindows x86 xft xine xml xml2 xmms xprint xv yahoo zlib"
any change you have hotplug in /etc/runlevels/boot? try `rc-update del hotplug`.
Yes, that fixed it, however I would prefer to use hotplug as I have a UDEV system... is this a portage bug, baselayout bug, or hotplug bug?
because you use udev doesnt mean you need hotplug this is a baselayout bug ... the hotplug script screws a lot of things up
*** Bug 66963 has been marked as a duplicate of this bug. ***
I am a posted from the duped bug above. Removing hotplug from boot and into default seems to have ameliorated the symptoms of this bug. However, on one of two test reboots, my nvidia module failed to load despite its presence in /etc/modules.autoload. The problem I was having was intermittent to begin with, so two reboots is not a really good test of this problem being fixed. However, I'm happy for now.
i don't think that deleting hotplug fixes the problem (at least, it doesn't for me). Please see the bug marked as a dupe of this.
removing hotplug 'fixed' this for users if you see this problem without hotplug, try baselayout-1.11.3+ which will have some fixes to better handle this
moving hotplug from boot to default seems to work for me too! rc-update del hotplug boot rc-update add hotplug default
For me, it did upgrading to baselayout-1.11.4.
