Date: Mon, 24 Sep 2001 02:28:27 -0700 From: Sean Chittenden <sean@chittenden.org> To: Gavin Atkinson <gavin@ury.york.ac.uk> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /dev/null permission change from 4.3 -> 4.4... Message-ID: <20010924022827.B27608@rand.tgd.net> In-Reply-To: <Pine.BSF.4.33.0109241013580.36876-100000@ury.york.ac.uk>; from "gavin@ury.york.ac.uk" on Mon, Sep 24, 2001 at = 10:16:44AM References: <20010923175213.B18824@rand.tgd.net> <Pine.BSF.4.33.0109241013580.36876-100000@ury.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. > > It's been brought up a couple of times on -stable since 4.4rc1 came out... > I had the same problem, with /dev/null (and ISTR /dev/random) were both > 0600. more recent mergemasters have not caused problems for me. Sounds plausible... I just finished bringing a few 4.2 systems up to 4.4 and they were just fine. I think you're right though in that the systems that were having the probs were tracking -STABLE and probably have had it like that since whenever the problem was in -RC and I just noticed it now. So long as it's no longer a problem, I'll mod the devices back to normal. Were /dev/null and /dev/urandom the only two that you noticed? urandom seems to be set correctly (0444). -sc -- Sean Chittenden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010924022827.B27608>