From: Daniel Drake <dan@reactivated.net>
To: linux-hotplug@vger.kernel.org
Subject: udev/hotplug success story
Date: Sun, 08 Feb 2004 21:11:16 +0000 [thread overview]
Message-ID: <4026A5F4.1000901@reactivated.net> (raw)
Hi Greg,
Thought you might be interested to know that I've got my setup working great
with udev controlling /dev.
I'm running a gentoo based system, kernel 2.6.2-mm1, udev 016, hotplug 20040105
A few comments:
With the default devfs-like config, udev correctly places a symlink to
/dev/hdc as /dev/cdroms/cdrom0.
With devfs, I had it setup so that I could also use /dev/dvd there. Writing a
rule for udev to do that is no problem. I told it to name the device "hdc" and
SYMLINK "dvd". The only thing there, is that it then overwrote the devfs-like
rule, and /dev/cdroms/cdrom0 no longer existed. In the end I just added
another SYMLINK to cdroms/cdrom0, but I was wondering, is there a better way -
are there rules that I can pass that append SYMLINKs onto other ones?
Hotplug is doing a good job of managing my usb modules. When I plug my camera
in, it loads usb-storage as expected. However, it doesnt load sd_mod, meaning
that no /dev/sda1 is created, and I can't access my pictures.
I could easily get around this by writing a script to "modprobe sd_mod", and
then adding a line to /etc/hotplug/usb.usermap.
To better fit in with the purpose of hotplugging, I would think that this
module should be loaded automatically after usb-storage. Is this a
bug/missing-feature, or intentional?
Final comment: I think that the documentation for hotplug is a little lacking.
In particular, I had trouble finding out what the match_flags column in
usb.usermap does, I eventually found the answer by looking through the code of
usb.agent
cheers,
Daniel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
next reply other threads:[~2004-02-08 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 21:11 Daniel Drake [this message]
2004-02-08 23:50 ` udev/hotplug success story Måns Rullgård
2004-02-09 23:12 ` Patrick Mansfield
2004-02-13 1:38 ` Greg KH
2004-03-03 21:48 ` 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=4026A5F4.1000901@reactivated.net \
--to=dan@reactivated.net \
--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).