mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grzegorz Kulewski <kangur@polcom.net>
To: linux-hotplug-devel@vger.kernel.org
Cc: greg@kroach.com, linux-kernel@vger.kernel.org
Subject: [QUESTION/PROPOSAL] udev (fwd)
Date: Wed, 3 Mar 2004 20:27:17 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.58.0403032023090.1319@alpha.polcom.net> (raw)

[PLEASE CC LKML or me because I am not subscribed to LHD!]

Greg asked for it, so here it is:

Question:

If I understand well, currently, when kernel detects new device, it 
creates all important files in /sys for it, excluding device file.

So, (sorry if it was asked 100000000 times...
... but) why when kernel detects new device or module is loaded, no device 
file in sysfs is created? The device files in /dev would be only links to 
these in /sys. 

This way we could stop care about major/minor numbers and leave it to sysfs...
And it maybe could decrease the possible races related to udev because it 
would only create or remove links to files in /sys.

Programs will be able to easily find, for what device and where located in 
system (buses, etc.) the device file in /dev is - with readlink.

And it should make the entire process more clear.

What You think about it?



thanks and sorry for my english

Grzegorz Kulewski


             reply	other threads:[~2004-03-03 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 19:27 Grzegorz Kulewski [this message]
2004-03-03 19:40 ` Tim Hockin
2004-03-03 20:51   ` Grzegorz Kulewski
2004-03-03 22:10     ` Tim Hockin
2004-03-03 19:41 ` Chris Friesen
2004-03-03 20:04 ` Felipe Alfaro Solana
2004-03-03 21:08 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.58.0403032023090.1319@alpha.polcom.net \
    --to=kangur@polcom.net \
    --cc=greg@kroach.com \
    --cc=linux-hotplug-devel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®