From owner-freebsd-current Fri Apr 24 18:03:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13497 for freebsd-current-outgoing; Fri, 24 Apr 1998 18:03:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13491 for ; Fri, 24 Apr 1998 18:03:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA02290; Fri, 24 Apr 1998 18:00:18 -0700 (PDT) Message-Id: <199804250100.SAA02290@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: next stages in devfs In-reply-to: Your message of "Tue, 21 Apr 1998 00:24:00 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Apr 1998 18:00:18 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > THere are a few stages that need to be taken for devfs at this point. > Some of them need discussion: > > removable media: > how do we detect that they have changed? > this is ok for SCSI, as the first access after a change will > have the usual effect.. (annoying but safe). > but there is no way to know that the floppy has changed (is there?, > I heard recently that there is actually a way to tell this under AT or > newer machines (that's everything with a 386 or greater). > does anyone have any info on this? ATAPI gives you the same basic behaviour as SCSI. Some removable ATA drives also appear to have this feature. All of the media-changed mechanisms I'm familiar with are response-based, ie. you only find out about the change when you try to access the device. You can adopt an active strategy for dealing with this. I would propose that a device that supports removable media should register a periodic callback. The callback, when invoked, should check the status of the device. This would effectively let you generate asynchronous media change notifications. Floppy drives, as has been mentioned, are problematic. 8( > * The LS120 driver hasn't been integrated.. can someone who has one > let me know so I can co-ordinate that.. I can lend you an ATAPI Zip and/or LS-120 for this. Let me know if you need it. > What is a good naming scheme for extended partitions? We have one that works just fine, as has been observed. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message