From owner-freebsd-hackers Fri Jan 27 08:59:38 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA22209 for hackers-outgoing; Fri, 27 Jan 1995 08:59:38 -0800 Received: from foxtrot.innovus.com (foxtrot.innovus.com [192.75.186.38]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id IAA22203 for ; Fri, 27 Jan 1995 08:59:34 -0800 Message-Id: <199501271659.IAA22203@freefall.cdrom.com> Received: by foxtrot.innovus.com (1.37.109.8/16.2) id AA05050; Fri, 27 Jan 1995 12:04:00 -0500 From: Martin Renters Subject: Re: SyQuest works with FreeBSD 2.0R ! To: peter@bonkers.taronga.com (Peter da Silva) Date: Fri, 27 Jan 95 12:03:59 EST Cc: dufault@hda.com, terry@cs.weber.edu, john@pyromania.apana.org.au, hackers@FreeBSD.org In-Reply-To: <199501271358.HAA09305@bonkers.taronga.com>; from "Peter da Silva" at Jan 27, 95 7:58 am Mailer: Elm [revision: 70.85] Sender: hackers-owner@FreeBSD.org Precedence: bulk > The real solution to removable media is to put some sort of ident in the > disklabel (including time and system ID) and track that. If you have a mounted > filesystem and get a UNIT ATTENTION then you can see whether it's been > swapped or not. > > (yes, you can still defeat this with a dd to the raw device) > > What would be really cool would be to create a new pseudo-device entry when > you mount the device, and treat each volume as a separate device. Then you > could simply stall attempts to access a filesystem mounted on a device that's > been removed. Perhaps even have a hook to alert the user when they do that > to insert the appropriate volume... This is what HP does for their optical juke boxes. Except in that case a robot decides you've looked at that disk long enough and puts another one in. As an aside, don't these drives have "PREVENT MEDIA EJECT" SCSI commands to lock the disks in? Martin