/dev/od0 auto-ejects after each close() ?!

From: Steffen Kremser <steffen.kremser_at_danet.de>
Date: Mon, 13 Sep 1999 10:33:45 +0200

Hi!

We're trying to "just read some data" (using mtools and/or dd)
from a MO-Drive attached to our AS4100 running 4.0D (+jumbo 4)

under Linux and HP/UX we could "simply" open the the device
but DU seems to be rather picky about the hardware class ...

after some searching, i tentatively installed the OSDS package:

OSDSCAM160 installed SCSI Device Drivers
OSDSMAN160 installed Online Manual Pages
OSDSOSF160 installed File System Patches
OSDSVFS160 installed Optical File System

so now we have a device file for the hardware (/dev/od0)
(and after disabling that ofsd we can actually open it ;-)

vmunix: scsi3 at psiop1 slot 0
vmunix: optical at scsi3 target 3 lun 0 (LID=5) (MaxoptixT5-2600 A6.7)
vmunix: op330 at scsi3 unit 216 (MaxoptixT5-2600 A6.7)

remains one hitch: the media cartridge is always ejected on close();
that makes autoprobing for the media format somewhat unpractical..

It even ejects in response to a "scu -f /dev/od0 prevent"
which seems counter-intuitive to me..

any ideas ?

Steffen Kremser
------------------------------------------------------------------------
Steffen M. Kremser Danet GmbH
steffen.kremser_at_danet.de Mobile Communications Technology
Tel: +49-6151-868-484 Gutenbergstr. 10
Fax: +49-6151-868-498 64331 Weiterstadt, Germany
PGP: 1024/4DF769B5 Fingerprint: 85866AC0420EEDB7E0E0E9D988E772E1
Received on Mon Sep 13 1999 - 09:10:22 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:39 NZDT