On 2009-09-06 20:28, Raphael Geissert wrote: > Hi, > > On Sunday 06 September 2009 10:19:14 Török Edwin wrote: > >> Package: readahead-fedora >> Version: 1.5.0-3 >> Severity: normal >> >> I have insserv installed, set CONCURRENCY=makefile in /etc/default/rcS, but >> the 'unable to create here-document: read-only filesystem' error still >> occurs. >> >> readahead seems to start after mountkernfs, however thats not enough, /tmp >> is still readonly at that time, and bash wants to use /tmp for here-docs >> (debian bug #377763). >> > > I wasn't aware of that behaviour of bash, it doesn't make sense I must say. > > >> Does it need to use a here-doc? Can't early-readahead use a sequence of >> echo >>? >> > > I'll make it use printf instead on the next upload. >
Thanks. > >> Note that I have my /var on another partition. I tried setting all var >> paths to use /etc/readahead in /etc/readahead.conf, but I still see the >> error, so it must be due to bash trying to use /tmp. >> > > Yeah, it has to be bash trying to write to /tmp, as the init scripts are > designed not to fail in case /var or /usr are not available. > > Not really relevant for this bug report, but why are you still using bash > as /bin/sh? > I tried switching /bin/sh to dash a while ago. It worked well for Debian packages, however it caused some serious problems with other open source software, in particular one install script did a rm -rf /$FOO, and FOO was not set (I guess it used some bashism to set it, and dash silently failed to do that). That of course resulted in rm -rf / being executed as root. Luckily I noticed that my install script was taking too long, the HDD led was on, so I killed the script. It only managed to delete /usr and part of /var, that was easily restored. Since then I decided to keep my /bin/sh as bash, the few % of boot time speedup is not worth the risk for me (I do use dash on my laptop though). Most of the boot time on this box is spent in the AHCI BIOS anyway, which spends several seconds to scan for each of my 6 disks. Best regards, --Edwin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
