Nov 26, 1997

It's actually pretty easy for me to take a snapshot of the current
MkLinux kernel and server sources and make the pieces of an update
-- I just pick a version number, turn the crank, and presto, there
are the pieces of an update.

However, a "real" update also includes attempting to get the system
to a stable state, trying it out and testing it on many platforms,
preparing the READMEs, attempting to explain the increasingly-more-
complex upgrade path and install procedures, etc.

So, here's a really quick-n-dirty "update", it's not for general
consumption, so that's why it's here in the wip directory, instead
of being turned into an actual update (with a big announcement and
all).  We would like to get some mileage on these pieces, but there
are definitely some things in here that make this kernel/server
non-ideal for everyone.

----------------------------------------------------------------------
READ THIS READ THIS READ THIS READ THIS READ THIS READ THIS READ THIS!

These pieces are NOT for everyone.  You must be quite comfortable doing
upgrades and installing kernels and servers before you attempt to do
this.  ALSO, there are some changes in the kernel and server that
change the names of SCSI devices.  You will have to have your fstab
fixed BEFORE you reboot with the new kernel.  If it doesn't work for
you, then you'll need to fix your fstab BACK to how it was using your
old kernel somehow.  This is definitely not for the timid.
----------------------------------------------------------------------

Here's what is in this wip since update6:
 - fix for the "too-many-whoops" crash (similar to wip 971111)
 - additional ATI video cards are recognized
 - additional IMS video cards are recognized
 - based on linux source 2.0.32
   - protects against teardrop attack
 - CHANGE TO SCSI DEVICE NAMING (all caps because you must PAY ATTENTION HERE)
   - The SCSI busses are scanned, from ID 0 up to ID 6
   - If you have two SCSI busses, the internal bus comes first.
   - Disks are labeled in the order that they are found, /dev/sda, /dev/sdb,
     etc...
   - CDROMs are ordered similarly, /dev/scd0, /dev/scd1, etc.
   - And the same for tapes, /dev/st0, /dev/st1, etc.
   - Example - internal disk at scsi id 2, cd at 3, disk at 4, external disk at
               2, internal disks are /dev/sda and /dev/sdb, external disk is
               /dev/sdc, cd is /dev/scd0
             - note that example has two drives with ID 2, one internal one
               external, both are accessible!
   - Yes, you are correct, if you have disks on your internal bus and
     disks on your external bus, and you add or remove one on your
     internal bus, your external drives will "move".
   - Yes, there are pro's and con's to this
   - Yes, this is how linux works
   - Yes, this is how linux-ppc and linux-pmac work
   - This _is_ how MkLinux works as of this wip, in DR3, and going forward
     until mainline Linux makes a move to somehow address the "con's".
   - No, you will not complain about this on the mklinux-* mailing lists.
 - Changes to the serial port mapping
   - /dev/cua0 is the modem port
   - /dev/cua1 is the printer port
   - you will need to change your symbolic link "/dev/modem" if you still want
     /dev/modem to still access the modem port
   - this is more compatible with the rest of the world, including linux-pmac
   - you shouldn't make a "/dev/printer" link from "/dev/cua1".  The lp
     packages use "/dev/printer" as a named socket.  You might want to use
     "/dev/prn" instead.
 - bug fix in inode.c to scan the entire inode list for a free inode, instead
   of just half of it.  Should fix the "run out of inodes, contact Linus" bug.
 - fewer of those annoying console messages that mess up your X display.
 - there may be a problem with the 2.0.32 server leaking memory, it's being
   looked at.

Please do _not_ report any bugs you find with this stuff to
bugs@mklinux.apple.com, nor to the Apple bug reporter web page.  If you
_do_ have any problems with this wip, please bring it up on the mailing list
mklinux-setup.  (For more information on how to get onto mklinux-setup mailing
list, send just the word "help" in the body of an email message to
"majordomo@mklinux.apple.com".)

Enjoy,
Gilbert