linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev enhancements
Date: Tue, 21 Dec 2004 16:59:45 +0000	[thread overview]
Message-ID: <20041221165945.GB30446@kroah.com> (raw)
In-Reply-To: <41C1551F.6060601@suse.de>

On Thu, Dec 16, 2004 at 10:27:59AM +0100, Hannes Reinecke wrote:
> Hi all,
> 
> I'm trying to figure out the best way to incorporating udev into some 
> system tools. Currently we're facing the following problem:
> 
> Any program dealing with device nodes (e.g. parted) need to figure out 
> some information about the device it handles:
> - partition naming: given a device name, generate the name of a
>   partition on that device.
> - number of partitions: each block device type has it's own maximal
>   number of partitions.
> 
> These information is mostly gathered from the device name. Of course, 
> you can't do that if you're using udev.
> So, to retain the existing functionality we would need to add two major 
> improvements to udev:
> 
> - Build udevinfo as library. This way any program can just link to this 
> library and retrieve any information from there instead of rely on some 
> build-in logic. That should actually be quite simple ...

Look at how HAL uses udevinfo to get this kind of information.  You
don't need to make udevinfo into a library to do this.  In fact, now
that the udev database is just a directory of files, you don't really
need udevinfo to get this yourself (just be careful if we change the
database format in the future...)

> - Add a 'dry-run' logic to udev/udevinfo: Given a devicename, how would 
> a partition on that device be named?

Look at udevtest, that provides a "dry-run" functionality.

> And it would also break the deadlock we're having now:
> Removable IDE devices _always_ do a re-read partition on _open_.
> So if we're using device_id to fetch information about a partition, 
> we're triggering hotplug events for each partition, which causes 
> device_id to re-run, which causes hotplug-events, which ...

Use {all_partitions} for such devices.  Linus has even argued that udev
itself should do this by default for these types of things just to make
it simpler.

thanks,

greg k-h


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2004-12-21 16:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16  9:27 udev enhancements Hannes Reinecke
2004-12-16 14:41 ` Harald Hoyer
2004-12-16 14:48 ` Olaf Hering
2004-12-16 21:55 ` Kay Sievers
2004-12-21 16:59 ` Greg KH [this message]

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=20041221165945.GB30446@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).