Date: Sun, 01 Oct 2000 12:39:23 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Alexander Langer <alex@big.endian.de> Cc: Jeremy Lea <reg@FreeBSD.ORG>, Mike Meyer <mwm@mired.org>, current@FreeBSD.ORG Subject: Re: setting device permissions for DEVFS Message-ID: <13126.970396763@critter> In-Reply-To: Your message of "Sun, 01 Oct 2000 12:32:17 %2B0200." <20001001123217.A2644@cichlids.cichlids.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20001001123217.A2644@cichlids.cichlids.com>, Alexander Langer write s: >Thus spake Poul-Henning Kamp (phk@critter.freebsd.dk): > >> You guys are overlooking something about DEVFS: devices may appear >> post-boot. > >Ah, yes. > >BTW: Devices don't disappear if you unload devices. >This happens for example with bktr.ko. That is because the bktr driver fails to call destroy_dev() when it unloads. >Hmm. A technical question: How would the devd be notifed about an >event in the devfs? There are many ways to do this, a kqueue() or poll() based solution is probably the correct way, monitoring the sysctl vfs.devfs.generation is the Q&D way. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13126.970396763>