Bug 27265

Summary: binary upgrade to 4.3R doesn't preserve device permissions
Product: Base System Reporter: a <a>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.3-RELEASE   
Hardware: Any   
OS: Any   

Description a 2001-05-11 11:00:05 UTC
the permissions on /dev/bpf* were reset when i used sysinstall
to do a binary upgrade from 4.2R to 4.3R.

i like to have them set to g+r so i don't have to run everything
as root.
Comment 1 Kris Kennaway 2001-05-15 00:43:03 UTC
On Fri, May 11, 2001 at 02:59:05AM -0700, a@b.com wrote:
> 
> >Number:         27265
> >Category:       misc
> >Synopsis:       binary upgrade to 4.3R doesn't preserve device permissions
> >Confidential:   no
> >Severity:       non-critical
> >Priority:       low
> >Responsible:    freebsd-bugs
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Fri May 11 03:00:05 PDT 2001
> >Closed-Date:
> >Last-Modified:
> >Originator:     christian
> >Release:        4.3-RELEASE
> >Organization:
> >Environment:
> FreeBSD hp0.pacbell.net 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Mon Apr 30 12:47:33 PDT 2001     root@hp0.pacbell.net:/usr/src/sys/compile/HP9780C-LITE  i386
> >Description:
> the permissions on /dev/bpf* were reset when i used sysinstall
> to do a binary upgrade from 4.2R to 4.3R.
> 
> i like to have them set to g+r so i don't have to run everything
> as root.


Yes, this is as expected.  The upgrade procedure needs to remake the
devices to deal with device nodeswhich have changed, as well as adding
new ones.  There's no easy way for it to know that you made a local
customization which you want to be maintainer after the upgrade.

Perhaps what you really want here is fbtab(5), or a local
customization script which you can use to customize device
permissions.

Kris
Comment 2 dd freebsd_committer freebsd_triage 2001-06-01 03:25:05 UTC
State Changed
From-To: open->closed

This is expected behavior.