From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Support for multiple usermaps in hotplug usb.agent
Date: Mon, 22 Jul 2002 04:55:20 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102731353432243@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102703767903147@msgid-missing>
Maksim (Max) Krasnyanskiy wrote:
>>Why do you rebuild the usermap database. Would it be easier to just find
>>a group of usermap's via a glob and then parse all of them each hotplug,
>>like Maksim's patch ?
>>
>>The only advantage I can think of rebuilding the database, is you can
>>better control conflicts, but that's a tricky situation anyway.
>
> They don't resolve any conflicts. update.usermap is pretty much just
> for map in $(all installed maps); do
> cat $map >> /etc/hotplug/usb.usermap
> done
So at a technical level, ignoring the "where does stuff install" issue
(we want just one answer, the path doesn't much matter) the only real
difference is who does the match/catenate, and when.
In fact, if Max's patch had scanned /usr/lib/hotplug/*/usb.usermap,
then there'd be compatibility with Debian, and Debian could get rid
of the "update.usermap" script. Yes?
How did /usr/lib/hotplug get settled on? There's also some code using
/usr/share/usb (/usr/lib is wrong for sharable stuff ...) for firmware
downloading, and I see that RedHat has /usr/share/hwdata/usb.ids ... that
is, not using /usr/share/usb either. Does the Linux Filesystem standard
have anything useful to say about this? Shouldn't it?
In general I tend to think avoiding extra commands ("update.usermap")
is a good thing, but then so is avoiding wildcards in shell scripts.
In this case I'd prefer the latter, I must say.
- Dave
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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 prev parent reply other threads:[~2002-07-22 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 0:10 Support for multiple usermaps in hotplug usb.agent Maksim (Max) Krasnyanskiy
2002-07-21 13:57 ` Maksim (Max) Krasnyanskiy
2002-07-21 13:58 ` Maksim (Max) Krasnyanskiy
2002-07-21 17:26 ` Fumitoshi UKAI
2002-07-21 17:54 ` Johannes Erdfelt
2002-07-22 4:55 ` David Brownell [this message]
2002-07-22 22:03 ` Maksim (Max) Krasnyanskiy
2002-07-24 1:34 ` David Brownell
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=marc-linux-hotplug-102731353432243@msgid-missing \
--to=david-b@pacbell.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 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.