Date: Tue, 13 Dec 2005 11:21:43 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Brooks Davis <brooks@one-eyed-alien.net>, "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de>, freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights Message-ID: <20051213192143.GA5926@odin.ac.hmc.edu> In-Reply-To: <20051213180418.GA20852@slackbox.xs4all.nl> References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 07:04:18PM +0100, Roland Smith wrote: > On Tue, Dec 13, 2005 at 08:49:47AM -0800, Brooks Davis wrote: > > On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote: > > > On my FreeBSD 6-stable (the last build is less then 24hours ago) my > > > devfs doesn't apply permissions set in /etc/devfs.conf when I attach = new > > > devices. I have to call: > > > /etc/rc.d/devfs restart > > > manually for the settings to be applied. This is rather uncomfortable= in > > > some cases (especially with my PDA). > > >=20 > > > I don't know weather this is the normal behaviour, anyway if it is, > > > shouldn't devfs be restarted automatically as soon as external devices > > > (usb, firewire, ir) are attached? > >=20 > > This is normal. devfs.conf is for boot only, you need devfs.rules for > > runtime. Unfortunatly, the documentation of this fact and the > > docuementation of devfs.rules sucks. >=20 > Hmm, it's quite explicitly mentioned in the manual pages for devfs.conf a= nd > devfs.rules.=20 >=20 > Feel free to suggest improvements... 90% of the problem is the existence of devfs.conf. devfs(8) appears capable of everything it does, but we still have two ways to do it which is gratuitously confusing. The devfs(8) documentation is lacking in a complete, working example, any documentation of the rc.conf variables (which also aren't documented in rc.conf(5) either), and any mention of that the purpose or usage of lines like: [devfsrules_unhide_basic=3D2] Setting the mode of a device node really ought to be trivial, but last time I looked at it I was clearly missing something and couldn't get it working. I decided the device in question really ought to be attached at boot and thus gave up and used devfs.conf since I had productive work to do. Some cook easy to use cookbook example would be really helpful for those who don't have time to figure out all the details. Comparativly few people will want to do anything more than make a device or two more accessable. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDnx9GXY6L6fI4GtQRAqrDAJ0eNNBxca5Sac7w3HS7tJyhOdAeRQCdEHLV mHB2xd8oHpYImTpWmeHoLV4= =jWnE -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051213192143.GA5926>