nicholas@cs.uwa.oz.au (Nicholas Yue):
quoted text
> G'day,
>   How do I mount the 2nd hard-disk (automagically ;-). The boot floppy can
> be configured to mount the root file system form /dev/hdX

Minix does this in /etc/rc, but as linux currently ignores that, the
best way is to do it in your .profile (or /etc/.profile).  You migh want
to use 'mount /dev/hdX /home &> /dev/null' so that eventual multiple
mounts won't print error messages.  Likewise you can unmount in .logout,
but unmounting isn't really necessary (but do remeber to sync).

many:
quoted text
>
> kermit works, but dies due to ^C. What's wrong? It also complains
> about not being able to lock the line.

This /seems/ to be standard behaviour of unix-kermit, and it is
certainly not of my doing. It's a nuisance. Line-locking is done by
creating a file in the directory /usr/spool/uucp/LCK, and unless that
directory exists, kermit isn't able to lock it.

Then to bug-reports and updates:

hd.c is buggy, and I'm investigating it.  When read-errors occur, weird
things can happen, including writing to the disk.  This might be the
cause of some peoples problems: there is no problem if you have a
sector-translating controller (eg IDE etc) that never returns errors.  I
think I've gotten it working, and hopefully the 0.11 version (due out in
about a week) will be correct. 

0.11 will also finally be totally self-sustaining: I have gotten the
source to bruce evans' assembler and linker, and at least I haven't
heard of many problems with mkfs and fsck.  I didn't have time to
implement symlinks, so there are no real new features: just bug-fixes
and enhancements.  Thanks to everybody who sent diffs etc.  You know who
you are, and I've tried to accnowledge everyone in the source.  Wolfgang
XXXX, who made the German keyboard patch, please mail me your last name. 

Known bugs still unresolved: at least one machine has trouble reading
the floppy, and one 486 seems to have problems with the harddisk even
with my new patches.  Another machine seems to get divide by zero
errors, and I have absolutely no idea why this happens.  As it looks
now, these won't be corrected in 0.11 unless I can find the reason for
them within the week :-(

		Linus