Re: [bug] /etc/profile: line 30: /dev/null: Permission denied (Was: Re: [PATCH] Remove broken by design and by implementation devtmpfs maintenance disaster)

[Linus Torvalds]

On Thu, 17 Sep 2009, Kay Sievers wrote:

> On Thu, Sep 17, 2009 at 20:53, Ingo Molnar <mingo@xxxxxxx> wrote:
> > I've reproduced a bug with the following .config options:
> >
> > ÂCONFIG_DEVTMPFS=y
> > ÂCONFIG_DEVTMPFS_MOUNT=y
> >
> > /dev/null and /dev/zero are not read/writable to ordinary users,
> > breaking normal bootup and login:
> 
> Udev should run long before some ordinary/non-root user can login, and
> apply the permissions as it always does. It's known to work on Fedora,
> SUSE, Ubuntu. What kind of system/environment/setup is that where you
> see this?

I don't know if this is what Ingo does, but I have a few machines where I 
don't run the distro-supplied 'initrd' at all, because it's easier to boot 
without it. The Fedora initrd doesn't allow me to sanely set root 
filesystem parameters without totally rewriting the initrd image, which 
I'm not interested in, for example (they'll take effect for the root 
initrd, not the final root).

That may be "not supported", but the point is, we want to make the kernel 
be as self-sufficient as possible, and the whole _point_ of this devtmpfs 
seemed to be to increase self-sufficiency rather than decrease it by 
requiring 'udev' to have run very very early.

If you have udev running really early, then what's the point of devtmpfs? 
You might as well just have udev and tmpfs.

So I suspect /dev/null and /dev/zero should be special - just make them 
have 0666 permissions. Because they really _are_ special, and no other 
permissions ever make sense for them.

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/