From owner-freebsd-current Tue Apr 21 00:37:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16164 for freebsd-current-outgoing; Tue, 21 Apr 1998 00:37:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16116 for ; Tue, 21 Apr 1998 07:37:09 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA25726 for ; Tue, 21 Apr 1998 00:29:22 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd025724; Tue Apr 21 07:29:19 1998 Date: Tue, 21 Apr 1998 00:24:00 -0700 (PDT) From: Julian Elischer To: current@FreeBSD.ORG Subject: next stages in devfs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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? Maybe FreeBSD could do what some other vendors do and have a constant probe (non activating) going on all detected drives (once per few seconds) I know some people hate the idea but it is one solution. Win95 does this. (how it notices new CDs) Joerg, do you have any thoughts as to how I could better integrate the floppy (you being an expert there). What I have done works but its probing at bootup (with annoying error messages due to lack of media) needs work (should a floppy drive look for sub-partitions at all?) should it try work out what media is in the drive and only show one device? Maybe a control program similar to 'mt' might be a better way of handling density. (doesn't fdformat do that? hmmm) * The LS120 driver hasn't been integrated.. can someone who has one let me know so I can co-ordinate that.. * I have not written a bad144 layer. how important is that these days? * There needs to be a handler for extended DOS partitions. I need a tester for that too.. :-) What is a good naming scheme for extended partitions? an extended partition in sd0s1 would start sd0s1x1 as a suggestion with further logical drives as sd0s1x2 sd0s1x3 etc. Is that reasonable? The naming order is also up for grabs because theoretically there could be 4 per layer.. I'd resist calling them sd0s1s1 and sd0s1s1s1, sd0s1s2s1 etc, as their actual layout on the disk would suggest. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message