From owner-freebsd-current Sun Oct 1 3:39:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (beachchick.freebsd.dk [212.242.34.253]) by hub.freebsd.org (Postfix) with ESMTP id BB3B237B502; Sun, 1 Oct 2000 03:39:34 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e91AdON13128; Sun, 1 Oct 2000 12:39:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alexander Langer Cc: Jeremy Lea , Mike Meyer , current@FreeBSD.ORG Subject: Re: setting device permissions for DEVFS In-Reply-To: Your message of "Sun, 01 Oct 2000 12:32:17 +0200." <20001001123217.A2644@cichlids.cichlids.com> Date: Sun, 01 Oct 2000 12:39:23 +0200 Message-ID: <13126.970396763@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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