linux-kernel - Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev tmpfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090514092854.GF1365@ucw.cz>
Date:	Thu, 14 May 2009 11:28:54 +0200
From:	Pavel Machek <pavel@....cz>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Greg KH <greg@...ah.com>, Jan Blunck <jblunck@...e.de>
Subject: Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev
	tmpfs

Hi!

> > so just to state the obvious: this code is not needed to boot fast.
> > It is mostly a workaround for having a bad initrd; if you don't use an
> > initrd, or if you use an initrd that's made with the right device nodes
> > in it already, you really just don't need this.
> >
> > I would much rather that you just fix your initrd... than to put this
> > sort of thing into the kernel....
> 
> How will you solve the dynamic device numbers? They are a complete
> reality today.

Maybe dynamic device numbers are bad idea to start with? 

I'd like to keep static /dev, thank you... With big enough major/minor
space (which we have today, I believe), complexity of dynamic device
numbers can and should be avoided.

Plus... this patch 'hardcoded' device names. Why not 'hardcode'
 device numbers in the same way, so that static /dev keeps working?
Namespace should be big enough...

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/