Date: Fri, 1 Sep 2000 09:05:07 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: Thrumbar Pathfinder <Thrumbar@Worldnet.att.net> Cc: freebsd-hardware@FreeBSD.org, arch@FreeBSD.org Subject: Re: Auto-Mount/Dismount optional drivers development??? Message-ID: <Pine.NEB.3.96L.1000901090036.38524A-100000@fledge.watson.org> In-Reply-To: <fgpuqsobe1qu8ucjmadno3m8o5v7jrked1@4ax.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1000901090036.38524A-100000>