[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Hurd freezes



Kent West <westk@acu.edu> writes:

> I never quite get finished with the installation, as problems arise
> (see
> http://faculty.acu.edu/~westk/A_Beginners_Second_Attempt_to_Install_the_Hurd.html
> for details). At one point I typed "mount" to see what drives were
> mounted, and the system froze. I couldn't switch to a different VT, or
> telnet/ssh in (no network yet), etc. Can I assume that once the system
> is properly running I would have been able to switch to a different VT
> or ssh in and kill the offending "mount" process?

Mount crashes and if it didn't crash it wouldn't work because it
doesn't know which filesystems are mounted. Filesystems are just
processes, there is no way to tell ATM which processes take care of
which filesystem. 

There will be a /etc/mtab server someday (hopefully ;)) that knows
about mounted filesystems.

About the VC's. Currently there are two consoles for the Hurd: the one
in GNUMach and one in the Hurd, the one you are using is the old
GNUMach thingy. Here are instructions how to use the new one:
http://mail.gnu.org/archive/html/bug-hurd/2002-09/msg00121.html

There are some bugs in the Debian packages of the Hurd for console
switching, but these have been fixed i CVS.

> Can I also assume this is just part of the "alpha" quality of this
> stage of development, and in the future I'll see more stability from
> the Hurd?

You can blame GNUMach and the alpha quality of the Hurd :)

Thanks,
Marco



Reply to: