linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Zeuthen <david@fubar.dk>
To: linux-hotplug@vger.kernel.org
Subject: Re: Make an un-device?
Date: Wed, 24 Mar 2010 17:07:52 +0000	[thread overview]
Message-ID: <1269450472.28921.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20100324124352.0978847e@zooty>

On Wed, 2010-03-24 at 12:43 -0400, Tom Horsley wrote:
> Usually people want to know how to make udev recognize
> devices. I have a device that is recognized just fine, but
> I'd really like to declare it an un-device. I don't
> want any /dev/ files created for it, I don't want the
> driver loaded unless something else needs it. I want
> it to disappear from creation completely.
> 
> Can custom udev rules do this?

Not specifically - ignore_device used to do something like this but we
removed that directive from udev... and even if we still had the
ignore_device directive, suppressing events at the udev level is wrong..
and that's why we removed ignore_device.

> Specifically, the device is the incredibly annoying fake CD
> drive that appears along side my usb hard disk
> when I plug it in.

One way to make such annoying drives disappear in GNOME and some other
desktop environments is to set the UDISKS_PRESENTATION_HIDE (or if you
are on an older distro than F13 vintage, it's called
DKD_PRESENTATION_HIDE) udev property like e.g. this

http://cgit.freedesktop.org/udisks/tree/data/80-udisks.rules#n188

Another way to solve this is adding an entry to something like one of
the unusual_* files under drivers/usb/storage in the kernel... but that
includes recompiling the kernel.

HTH,
David



  reply	other threads:[~2010-03-24 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 16:43 Make an un-device? Tom Horsley
2010-03-24 17:07 ` David Zeuthen [this message]
2010-03-24 17:16 ` Kay Sievers
2010-03-24 17:23 ` Tom Horsley
2010-03-24 17:52 ` Paul Fox
2010-03-24 22:08 ` David Zeuthen
2010-03-25 13:48 ` Dan Nicholson
2010-03-25 15:03 ` Kay Sievers

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=1269450472.28921.13.camel@localhost.localdomain \
    --to=david@fubar.dk \
    --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).