Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Kay Sievers <kay.sievers <at> vrfy.org>
Subject: Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev tmpfs
Newsgroups: gmane.linux.kernel.cross-arch
Date: Saturday 2nd May 2009 17:57:23 UTC (over 8 years ago)
On Sat, May 2, 2009 at 18:59, Jeff Garzik  wrote:
> Christoph Hellwig wrote:

>> It basically does re-introduce devfs under a different name, and from
>> looking at the implementation it might not be quite as bad a Gooch's
>> original, but it's certainly worse than Adam Richters rewrite the we
>> never ended up merging.
>
> I was interested in this Richter devfs rewrite, since I was unfamiliar
with
> it.
>
> For the benefit of the thread, here is a URL that people can examine:
>
>        http://marc.info/?l=linux-kernel&m=104138806530375&w=2

And it did:
  - the crazy devfs naming scheme with:
      /dev/ide/host0/bus0/target0/lun0/part1, /dev/tty/0,
    and it did not even create our current names by default
  - path lookup interception and called modprobe behind your back
  - call_usermodhelper() from the kernel to name devices
  - introduced a new filesystem type and a bunch of
    new datatypes
  - and so on ...

I don't think anybody else besides Christoph would call devtmpfs
"seriously worse" than this. :) None of these "features" are needed
today, or even close to even worth to think about it.

And for the "policy in kernel department" which will be the next naive
argument: The kernel carries the policy today for 98% of the devices,
if you change any driver given name, it will no longer show up in /dev
with the current name. That's the reality since years, and will not be
different anytime soon, there is no real naming policy besides the
current kernel supplied names.

Now that we managed to define a common set of /dev names we all share
across distros, it's time to let the kernel know about the remaining
2% and let it pre-create the device nodes itself for userspace to pick
up, with all the earlier mentioned opportunities it offers.

The final policy will still live in udev which sets ownership and
mode, and possibly overwrites the node name. Nothing really has
changed, it can just be made faster, and it is much more reliable if
stuff in userspace goes wrong.

Thanks,
Kay
 
CD: 4ms