Re: dependencies on makedev
- To: debian-devel@lists.debian.org
- Subject: Re: dependencies on makedev
- From: md@Linux.IT (Marco d'Itri)
- Date: Mon, 2 Jan 2006 01:48:23 +0100
- Message-id: <[🔎] 20060102004823.GC11160@wonderland.linux.it>
- Mail-followup-to: debian-devel@lists.debian.org
- In-reply-to: <20051231174838.GC27509@kitenet.net>
- References: <Pine.LNX.4.58.0512291347310.12512@gradall.private.brainfood.com> <20051229195913.GA17865@wonderland.linux.it> <Pine.LNX.4.58.0512291427420.12512@gradall.private.brainfood.com> <87y8234cpz.fsf@hardknott.home.whinlatter.ukfsn.org> <87y8234cpz.fsf@hardknott.home.whinlatter.ukfsn.org> <Pine.LNX.4.58.0512292124130.12512@gradall.private.brainfood.com> <E1EsBgm-0002pi-00@chiark.greenend.org.uk> <43B4D328.6070107@derobert.net> <20051230095949.GD4014@wonderland.linux.it> <20051231174838.GC27509@kitenet.net>
On Dec 31, Joey Hess <joeyh@debian.org> wrote:
> Is there any good way to map from a given device (or set of related
> devices) in /dev to a udev rule that will match and allow overriding
> only that device?
For the general case, no: e.g. compare udevinfo -a -p /sys/block/hda and
udevinfo -a -p /sys/class/sound/dsp .
But you can break it up in enough special cases which individually are
easily tractable, e.g. by looking at $ENV{ID_PATH} for block devices,
hardware IDs for PCI and USB devices, etc.
--
ciao,
Marco
Attachment:
signature.asc
Description: Digital signature
Reply to: