From owner-freebsd-hackers Fri Jan 27 11:27:30 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA25289 for hackers-outgoing; Fri, 27 Jan 1995 11:27:30 -0800 Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA25283 for ; Fri, 27 Jan 1995 11:27:29 -0800 Received: by tfs.com (smail3.1.28.1) Message-Id: From: julian@tfs.com (Julian Elischer) Subject: Re: SyQuest works with FreeBSD 2.0R ! To: peter@bonkers.taronga.com (Peter da Silva) Date: Fri, 27 Jan 1995 11:26:34 -0800 (PST) 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 07:58:08 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1018 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. > At the moment, a unit-attention invalidates all accesses, until all have been closed. (the device becomes 'locked'. when the reference count has gone down to 0, the lock is released.. > (yes, you can still defeat this with a dd to the raw device) not at the moment..... > > 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... and send messages to the operator to mount volume "xxx"? hmm sounds a bit like a certain large blue coloured machine I remember once.. >