[Josh Triplett] > I already used CONCURRENCY=startpar on my system, and it worked > quite well, but I didn't use CONCURRENCY=makefile because it > actually boots slower on my system.
Interesting. I assume there are bugs in some combination of init.d scripts on your system. I use CONCURRENCY=makefile on several systems, and it work for me. :) > After upgrading, when I rebooted to test the new mechanism, it seems > that some key init scripts (such as mounting the root filesystem > read-write and setting the hostname) either didn't run or didn't run > soon enough; I got a pile of errors about failures to write due to a > read-only filesystem, and the system stopped at some point and never > finished booting. To recover, I had to boot into single-user mode, > remount the filesystem read-write, and set CONCURRENCY=none in > /etc/default/rcS. > > I've attached pictures taken of the messages shown when booting with > CONCURRENCY=startpar. Can you provide the output from /usr/share/insserv/make-testsuite, and also the content of /var/log/boot after editing /etc/default/bootlogd to enable bootlogd and rebooting once to record all errors? Also, please provide the output from 'ls /etc/rc?.d'. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
