All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev enhancements
Date: Thu, 16 Dec 2004 14:41:42 +0000	[thread overview]
Message-ID: <41C19EA6.2090700@redhat.com> (raw)
In-Reply-To: <41C1551F.6060601@suse.de>

Hannes Reinecke wrote:
 > 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 ...
 >
 > Not nice. And no clean way to resolve it in kernel-land, either, as most
 > removable IDE devices have no clean way to detect a media change.


in fedora udev-048 we use in udev.rules:
KERNEL="hd[a-z]*", BUS="ide", SYSFS{removable}="1", NAME{ignore_remove}="%k"

this prevents the removal of the device nodes.


-------------------------------------------------------
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

  reply	other threads:[~2004-12-16 14:41 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 [this message]
2004-12-16 14:48 ` Olaf Hering
2004-12-16 21:55 ` Kay Sievers
2004-12-21 16:59 ` 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=41C19EA6.2090700@redhat.com \
    --to=harald@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.