From owner-freebsd-hardware Fri Sep 1 6: 5:14 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8743437B422; Fri, 1 Sep 2000 06:05:09 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id JAA38677; Fri, 1 Sep 2000 09:05:07 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 1 Sep 2000 09:05:07 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Thrumbar Pathfinder Cc: freebsd-hardware@FreeBSD.org, arch@FreeBSD.org Subject: Re: Auto-Mount/Dismount optional drivers development??? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You can imagine the decisions and resulting activities, in the case of removable media, being made in a userland daemon listening for device events. I guess the pertinent question then is, what is the best way in which to deliver this sort of event information to userland processes? To what extent can this event stream be abstracted so as to not represent driver-specific events ("cdrom device (whatever) was ejected" in a cdrom schema as opposed to something acd-specific), and should it be extensible to allow the representing of driver-specific events. Polling for device availability in userland seems like a less pretty solution. Right now, devices in /devfs appear based on whether or not the drive is available, not media. I wonder if there would be an appropriate way for events to be notified via a combination of kqueue() and devfs nodes? Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message