/dev permissions after reboot (and panic)

[Peter Avalos]

On Sun, Jul 17, 2005 at 11:52:59AM -0700, Matthew Dillon wrote:
> 
> :
> :Maybe related.
> :
> :I had to make upgrade twice today
> :because my first one messed up the dev permissions
> :of pseudo-ttys /dev/ptyp? were 644 instead of 666.
> :Noticed this after urxvt and aterm begun complaining about 
> :not being able to open and or initialize their pseudo--ttys
> :
> :--ed
> :Eduardo Tongson   <>
> 
>     Yah, I've been trying to track this down.  It does not
>     appear to be related to softupdates.
> 
>     Either MAKEDEV itself has a bug and is not adjusting
>     the permissions properly, or the chmod MAKEDEV is doing
>     is being lost.  The '644' permissions are the default
>     permissions when the node is created.  MAKEDEV does a
>     separate chmod to fix the permissions up.
> 

Doing an ls after MAKEDEV shows correct permissions.  It's when I
reboot when it comes back with a 644 mode.  So I think MAKEDEV
is doing the right thing.

>     I'm looking into a possible inode update race caused
>     by e.g. a newly created inode being flushed simultanious
>     with a chmod being made.
> 
> 					-Matt
> 					Matthew Dillon 
> 					<dillon at xxxxxxxxxxxxx>
Attachment:
pgp00012.pgp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgp00012.pgp
Type: application/octet-stream
Size: 189 bytes
Desc: "Description: PGP signature"
URL: <http://lists.dragonflybsd.org/pipermail/bugs/attachments/20050717/fbbebbfb/attachment-0022.obj>