I have a little story to tell. It's about that fun little process called
"getting the damn SCSI devices to work". I think it points out a design
decision in NetBSD that could use some rethinking (IMHO).

...Come to think of it, I have no idea if this is a cross-platform thing
or an Amiga-only "feature". If I'm barking up the wrong list, feel free
to boo me off the soapbox. 8)

Over the last week, my SyQuest drive has developed gremlins. Instead of
reading SyQuest disks, it now spends all of its time sitting around making
loud clicks. Keeps me awake at night (no joke). Well, I decided to "fix"
the thing, at least temporarily.

1> Open A2000 casing, physically unplug power to SyQuest
2> Reboot. No bus.
3> Reopen, reseat cards, reboot.  (Okay, okay, this isn't NetBSD's fault)  8)
4> NetBSD boots up. Everything is happy for about .5 seconds--then the fsck
   starts. Screams! AAAAGH! Can't check /dev/rsd2a -- device not config'd.
5> Manual fsck - same results.
6> The light dawns--by removing my SyQuest drive, rsd1 disappeared, and
   rsd2 automagically became rsd1.  8-P

The upshot: I had to edit /etc/fstab and decrement every device number,
then reboot and let the fscks go through. Plus, I'm _praying_ I don't have
any scripts hidden around which are device-specific.  8-P

Could we puh-leeeeze get the device numbering set up so that it at least
sorta reflects physical ID numbers? Or, at the very least, doesn't change
if you add/remove anywhere but the end of the ID chain?

Something to chat about for 1.2.  8)

							Thanks,
							   -Frank

--
 ____ PRI | Frank R. Dana Jr.|Tau Epsilon Phi|email:danaf@cs.rpi.edu | _ _
 \ _/__ D |----------------------------------------------------------| U U
  \X  / E |  I come from Queens, my birthday is National Coming Out  |  < 
    \/    |    Day... alright, already! I get the hint!! Jeez...     | \_/