home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!ra!tantalus.nrl.navy.mil!eric
- From: eric@tantalus.nrl.navy.mil (Eric Youngdale)
- Subject: Re: ST01/02 and Syquest 5110
- Message-ID: <C0LGtv.AMD@ra.nrl.navy.mil>
- Sender: usenet@ra.nrl.navy.mil
- Organization: Naval Research Laboratory
- References: <1993Jan08.142417.1962@gold.sub.org> <C0Ju8I.1uux@austin.ibm.com> <C0K0JH.5vx@mentor.cc.purdue.edu>
- Date: Sat, 9 Jan 1993 16:08:19 GMT
- Lines: 21
-
- In article <C0K0JH.5vx@mentor.cc.purdue.edu> wilker@hopf.math.purdue.edu (Clarence Wilkerson) writes:
- >Some drivers have a jumper to activate spin up only after access for the
- >first time. I know that some of the HP drives are like that.
- >
- >I have a similar problem. I have a scsi tape drive attached to the
- >Seagate ST-01. If it's turned on, it's found on bootup and is accessible
- >later. Because it's noisy ( rather the fan in its case is) it's often off.
- >Would there be someway to have a static table of attached scsi devices
- >that aren't mounted on bootup, but get switched on later?
-
- This would not be easy. All of the device detection is done before the
- root filesystem is mounted, so there would be no way of reading this at boot
- time. It would be possible to compile something into the kernel somehow.
- There would probably be some kind of list that you would have to modify prior
- to building the kernel that would have to be edited. Unfortunately this type
- of solution would only work for people willing and able to recompile the
- kernel.
-
- -Eric
- --
- Eric Youngdale
-