yes. booting as --readonly solves the problem. I feel the old tar ball has many more bugs. It will be helpful for the new hurd users to get the latest hurd package as a tar ball (as it is the easiest to download and install) ----- Original Message ----- From: "M. Gerards" <[EMAIL PROTECTED]> To: "Reny Sebastian" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, April 01, 2003 12:57 PM Subject: Re: boot problem - fsck
> > I have problem in booting Hurd in multiuser mode. > > fsck says, > > /sbin/fsck: / : Cannot make readonly : Device or Resource busy > > Unknown error during fsck (exit status 50) > > IIRC this is a bug in the Hurd that has been fixed in October. Just install the > newest Hurd package. The workaround for this bug is setting the filesystem > readonly before booting. You can find more info about this bug in the > mailinglist archives. > > > _______________________________________________ > Help-hurd mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/help-hurd ______________________________________ Scanned and protected by Email scanner _______________________________________________ Help-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/help-hurd
