From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] usb.agent should processes usermap before other maps.
Date: Thu, 18 Jul 2002 23:03:37 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102703327732408@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102696506820116@msgid-missing>
>> I'd rather not have distros diverge needlessly. The reason
>> we have so many incompatible Linux sysadmin toolsets is ...
>> well, I'm sure you can figure it out! :) The goal IMO is
>> to have one set of tools, and I'm not convinced there's a
>> reason to diverge here.
>
> Yes, but I'm not sure why does it matter what Debian does.
Because if you solve the same problem in a different way,
you're creating another problem. Maybe we need to do so,
but you ought to at least try to avoid creating such problems
in the first place -- so they don't need re-fixing again.
> They probably had to do something because current hotplug
> doesn't support multiple usermaps. I'm sure they'd be happy
> to switch to new hotplug. If they don't they could still
> generate /etc/hotplug/usb/usermap.debian and it will work.
I'd be pleased to see you work this issue with the Debian
maintainer of hotplug. Maybe he would be; maybe he's seen
some other issues that fit in here too.
- Dave
> We could also preserve 100% compatibility with older Debian
> by doing something like this
> MAPS="$HOTPLUG_DIR/usb.usermap $MAP_USERMAP_DIR/usermap.*"
> ie process old usb.usermap in addition to new maps.
> So, old Debian packages that use usb.usermap generator will still
> work. And new onces will switch to more convenient way of doing it.
>
> btw Generating global usb.usermap doesn't make a lot of sense to me.
> My patch is much simpler.
>
> Max
>
>
-------------------------------------------------------
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-18 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 3:59 [PATCH] usb.agent should processes usermap before other maps Maksim (Max) Krasnyanskiy
2002-07-18 5:35 ` David Brownell
2002-07-18 16:49 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-07-18 17:19 ` [PATCH] usb.agent should processes usermap before other maps David Brownell
2002-07-18 17:47 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-07-18 17:51 ` [PATCH] usb.agent should processes usermap before other maps Johannes Erdfelt
2002-07-18 20:17 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-07-18 20:55 ` [PATCH] usb.agent should processes usermap before other maps David Brownell
2002-07-18 21:40 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-07-18 21:49 ` [PATCH] usb.agent should processes usermap before other maps David Brownell
2002-07-18 22:03 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-07-18 23:03 ` David Brownell [this message]
2002-07-18 23:47 ` Maksim (Max) Krasnyanskiy
2002-08-09 18:22 ` [PATCH] usb.agent should processes usermap before other maps 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-102703327732408@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.