aimania@killer.DALLAS.TX.US (Walter Rothe) (11/28/88)
I've read quite a few messages on the net about autobooting disk controllers.
But as far as I am concerned, there is no overriding benefit of an autobooting
hard disk. Most disks take so long to spin up that you might as well have
booted off the floppy. Especially if your startup sequence quickly switches to
the hard disk. On an earlier startup sequence it was a race to see if the
disk would get up to speed after power on before the startup-sequence started
using it. About 5% of the time the disk took too long(ST225N).
Also, any reboots after the disk is spun up can be accomplished
faster using a small partition for RAD:.
Only minor inconvenience is that you have to take any disk out of df0:
otherwise the system will try to reboot from floppy without trying RAD:.
Is there something you can patch in your startup sequence to force loading
from RAD: instead of trying the floppy first?
--
Walter Rothe at the UNIX(Tm) Connection, Dallas, Tx
UUCP: {rutgers}!smu.killer.aimaniaaimania%killer.dallas.tx.us%CERNVAX.BITNET@cunyvm.cuny.edu (11/29/88)
I've read quite a few messages on the net about autobooting disk controllers.
But as far as I am concerned, there is no overriding benefit of an autobooting
hard disk. Most disks take so long to spin up that you might as well have
booted off the floppy. Especially if your startup sequence quickly switches to
the hard disk. On an earlier startup sequence it was a race to see if the
disk would get up to speed after power on before the startup-sequence started
using it. About 5% of the time the disk took too long(ST225N).
Also, any reboots after the disk is spun up can be accomplished
faster using a small partition for RAD:.
Only minor inconvenience is that you have to take any disk out of df0:
otherwise the system will try to reboot from floppy without trying RAD:.
Is there something you can patch in your startup sequence to force loading
from RAD: instead of trying the floppy first?
--
Walter Rothe at the UNIX(Tm) Connection, Dallas, Tx
UUCP: {rutgers}!smu.killer.aimaniascotth@harlie.SGI.COM (Scott Henry) (11/29/88)
From article <5691@louie.udel.EDU>, by aimania%killer.dallas.tx.us%CERNVAX.BITNET@cunyvm.cuny.edu: > > I've read quite a few messages on the net about autobooting disk controllers. > But as far as I am concerned, there is no overriding benefit of an autobooting >... > Only minor inconvenience is that you have to take any disk out of df0: > otherwise the system will try to reboot from floppy without trying RAD:. > Is there something you can patch in your startup sequence to force loading > from RAD: instead of trying the floppy first? All it takes is a non-bootable disk in DF0: (ie: a "data" disk). I have been using a very tiny RAD: for non-floppy re-boots with my Microbotics StarDrive for several weeks now. I frequently have a non-bootable disk in DF0:, and RAD: boots right up (it access both/all floppies first, as usual). > > -- > Walter Rothe at the UNIX(Tm) Connection, Dallas, Tx > UUCP: {rutgers}!smu.killer.aimania Scott Henry <scotth@harlie.sgi.com> #include <std_disclaimer.h> -- Scott Henry <scotth@harlie.sgi.com> {or, also on the Internet:} <skywalker@cup.portal.com> #include <std_disclaimer.h>