Re: /dev/null permission change from 4.3 -> 4.4...
On Sun, Sep 23, 2001 at 05:52:13PM -0700, Sean Chittenden wrote: > Howdy. This question was originally framed as a "why doesn't > uptime work for users in 4.4, when it used to in 4.3," but after looking > into things further, it's now a "why is /dev/null set to mod 0600?" On > a 4.3 system that I have, the perms on dev/null are 666. Something must have gone wrong..it's still supposed to be 666, and is on my machines. Kris PGP signature
Re: /dev/null permission change from 4.3 -> 4.4...
On Sun, 23 Sep 2001 at 17:52:13 -0700, Sean Chittenden wrote: > Howdy. This question was originally framed as a "why doesn't > uptime work for users in 4.4, when it used to in 4.3," but after > looking into things further, it's now a "why is /dev/null set to mod > 0600?" On a 4.3 system that I have, the perms on dev/null are 666. > > I've chmod'ed all of my boxen back to 0666, but... I'm curious > as to why this happened and the rationale behind the change. I've > observed this difference on at least 15 other 4.4 systems. What > gives? Hmm, it's still marked with the sign of the beast here. $ ls -l /dev/null crw-rw-rw- 1 root wheel2, 2 Sep 23 07:47 /dev/null $ uname -a FreeBSD athalon 4.4-STABLE FreeBSD 4.4-STABLE #9: Sun Sep 23 07:40:24 SAST 2001 root@athalon:/usr/obj/usr/src/sys/ATHALON i386 $ -- Piet Delport <[EMAIL PROTECTED]> Today's subliminal thought is: PGP signature
/dev/null permission change from 4.3 -> 4.4...
Howdy. This question was originally framed as a "why doesn't uptime work for users in 4.4, when it used to in 4.3," but after looking into things further, it's now a "why is /dev/null set to mod 0600?" On a 4.3 system that I have, the perms on dev/null are 666. I've chmod'ed all of my boxen back to 0666, but... I'm curious as to why this happened and the rationale behind the change. I've observed this difference on at least 15 other 4.4 systems. What gives? -sc PS Build processes was: cd /usr/src make update make world make kernel KERNCONF=KERNNAME mergemaster -- Sean Chittenden To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
