Date: Wed, 29 Jun 2005 16:50:20 GMT From: Matteo Riondato <matteo@freebsd.org> To: freebsd-rc@FreeBSD.org Subject: Re: kern/63954: devfs loses permissions Message-ID: <200506291650.j5TGoKfH068606@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/63954; it has been noted by GNATS. From: Matteo Riondato <matteo@freebsd.org> To: Mike Makonnen <mtm@identd.net> Cc: bug-followup@FreeBSD.org, edwin@mavetju.org, mmolteni@cisco.com, freebsd-rc@freebsd.org Subject: Re: kern/63954: devfs loses permissions Date: Wed, 29 Jun 2005 18:45:50 +0200 On Wed, Jun 29, 2005 at 07:13:19PM +0300, Mike Makonnen wrote: > On Wed, Jun 15, 2005 at 06:27:44PM +0200, Matteo Riondato wrote: > > Patch for this against /etc/rc.d/devfs follows and can be found at > > http://www.riondabsd.net/diff/devfs.diff. Please note that this patch > > includes fix for PR bin/65693 (wildcarded device names in devfs.conf > > ). I hope someone will pick this up and commit the patch. > > > > ummm... you have the right idea, except it has already been implemented for > a while: devfs.rules(5). The devfs.conf(5) file is > still with us because it does one thing devfs.rules(5) can't do, which is > make symlinks (which it can't because devfs(8) can't :-)) > > So, what you should do is edit /etc/devfs.rules with: > [myworkstation=500] > add path bpf* mode 0640 > > Then edit /etc/rc.conf and add: > devfs_system_ruleset=myworkstation Then having any other kind of rule in devfs.conf should is kind of useless, at least for devices that can "disappear", since rules referring to them will not be added do the devfs ruleset, and this implies that one have to rerun /etc/rc.d/devfs after reinserting the pcmcia nic or after launching tcpdump or whatever. Anyway, I see that this is documented on devfs.conf(5), so you can close this PR (and bin/65693 too). -- Matteo Riondato FreeBSD Volunteer (http://freebsd.org) G.U.F.I. Staff Member (http://www.gufi.org) FreeSBIE Developer (http://www.freesbie.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506291650.j5TGoKfH068606>