From owner-freebsd-hackers Fri Jan 27 06:11:45 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA17080 for hackers-outgoing; Fri, 27 Jan 1995 06:11:45 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id GAA17071 for ; Fri, 27 Jan 1995 06:11:41 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA12216 (5.67a/IDA-1.5); Fri, 27 Jan 1995 07:59:05 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA09308; 27 Jan 95 07:58:16 CST (Fri) Received: from localhost (localhost [127.0.0.1]) by bonkers.taronga.com (8.6.8/8.6.6) with SMTP id HAA09305; Fri, 27 Jan 1995 07:58:15 -0600 Message-Id: <199501271358.HAA09305@bonkers.taronga.com> X-Authentication-Warning: bonkers.taronga.com: Host localhost didn't use HELO protocol To: Peter Dufault Cc: terry@cs.weber.edu (Terry Lambert), john@pyromania.apana.org.au, hackers@FreeBSD.org Subject: Re: SyQuest works with FreeBSD 2.0R ! In-Reply-To: Your message of "Fri, 27 Jan 95 06:50:47 EST." <199501271150.GAA07921@hda.com> X-Mailer: exmh version 1.4.1 7/21/94 Date: Fri, 27 Jan 1995 07:58:08 -0600 From: Peter da Silva 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... (ok, that's blue-sky... an ID in the disklabel is just good hygeine)