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 for Android: free password hash cracker in your pocket

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

Message-ID: <20090501161745.GA29627@puku.stupidest.org>
Date:	Fri, 1 May 2009 09:17:45 -0700
From:	Chris Wedgwood <cw@...f.org>
To:	Greg KH <greg@...ah.com>
Cc:	Kay Sievers <kay.sievers@...y.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Jan Blunck <jblunck@...e.de>
Subject: Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev
	tmpfs

On Fri, May 01, 2009 at 09:09:51AM -0700, Greg KH wrote:

> You usually need to do more.  We started out just only doing block
> devices, but you also need the memory devices, and console, and a
> few others as well.

I could add that.  It's probably not hard.

What's more, it has liblkid support so you could mount by label and a
few other things.  It seems reasonable that you could add lvm support
as well.

The main downsides I see right now are:

  - it's not in the kernel by default

  - it's actually quite large beacuse i link against glibc

It's not clear these are show stoppers long term.


> After all that, you have already written another tool, which seems
> like overkill when we can do it all in the kernel so much easier and
> simpler.

I think that's a different argument.  Doesn't the same logic imply we
shouldn't have udevd?
--
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/