On Fri, Jun 20, 2008 at 12:04:23AM +0200, David wrote:
> I just tested this, and it doesn't seem to work for me :-/ (that's why
> I'm CC-ing the bug).
>
> As before, hitting Ctrl+C does interrupt the / fsck, and the boot
> continues. However, the root filesystem remains readonly, my system
> has a lot of bootup errors and the bootup process takes a long time,
> forcing me to reboot again and let the / fsck finish. It's a nasty DoS
> condition :-/
That sounds like it's a problem with sysvinit scripts; its not the
responsibility of e2fsck to remount the filesystem read-write. I'm
guessing the ^C managed to interrupt the sysvinit scripts as well as
the fsck program.
> Here is my /etc/e2fsck.conf:
>
> =====
> [options]
> buggy_init_scripts = 1
> allow_cancellation = 1
> =====
>
> My version has an extra "l" in cancellation, because that's how it is
> spelled in the man page.
That's how it's spelled /usr/dict/words, too. :-)
cancellation
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
