From owner-freebsd-current Sat May 30 19:59:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18088 for freebsd-current-outgoing; Sat, 30 May 1998 19:59:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles307.castles.com [208.214.167.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18068 for ; Sat, 30 May 1998 19:59:00 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA08633; Sat, 30 May 1998 18:54:47 -0700 (PDT) Message-Id: <199805310154.SAA08633@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mikhail Teterin cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 17:52:15 EDT." <199805302152.RAA17435@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 18:54:47 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Poul-Henning Kamp once stated: > > =Removing /dev/lpt0 doesn't make sense, it doesn't remove the driver, > =it doesn't attach from the hardware, it merely removes the namesticker > =from the mailbox. > > May be this should be the semantics of `rm' on the DEVFS? Removal > of the driver, or telling it to stop driving a particular device? > (If possible, otherwise, rm fails?) mknod (or, `touch'!!) can then > be used to load the driver back (if possible). > > Too far off? Not useful. You want to poke a single entity (the driver) and have it remove all it's nodes, rather than have to guess at all the nodes everywhere that it might own and run around deleting them all. -- \\ 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