home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!shady!DSM530!sts
- From: sts@DSM530.UUCP (sts)
- Newsgroups: comp.unix.aix
- Subject: Re: Adding SCSI OSDISK
- Message-ID: <109@DSM530.UUCP>
- Date: 10 Jan 93 22:09:04 GMT
- References: <C0I05H.1A5I@austin.ibm.com> <uk19il4@zuni.esd.sgi.com> <C0JIv9.Gx9@austin.ibm.com>
- Organization: DSM Chemicals, Augusta GA
- Lines: 16
-
- In article <C0JIv9.Gx9@austin.ibm.com> swan@austin.ibm.com (Randal C. Swanberg) writes:
- :>>
- :>> But why fail at that point? The obvious thing to do is to follow
- :>> a startunit (failed or successful!) with a testunitready, and only
- :>> cause a failure if the testunitready says the drive isn't ready...
- :>
- :I agree, that sounds like a more robust method. Actually, you could
- :issue the testunitready first to see if the startunit was even needed.
- :
- :You could also ask the same question of the disk implementation: Why
- :fail at that point? The obvious thing to do is to see that you are
- :already spun-up and act as though you successfully completed the
- :startunit.
- :
- Thumbs down to the drive for not ignoring the startunit. Thumbs down
- to AIX for not making it an option in smit.
-