From: Stefanos Harhalakis <v13@it.teithe.gr>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev patch
Date: Sun, 10 Dec 2006 13:53:04 +0000 [thread overview]
Message-ID: <200612101553.08434.v13@it.teithe.gr> (raw)
In-Reply-To: <200612092004.09587.v13@it.teithe.gr>
[-- Attachment #1.1: Type: text/plain, Size: 2401 bytes --]
On Saturday 09 December 2006 21:42, Bryan Kadzban wrote:
> Stefanos Harhalakis wrote:
> > Currently udev does not reread changed rule files when using
> > symlinks. Debian uses the symlink approach
>
> I have often wondered why Debian uses symlinks for the rules files. Is
> it just for compatibility with an ancient version of udev, that put the
> rules somewhere else? Or is it something with package upgrades, to
> handle it better when users decide to remove rules files? (If that's
> the case, then could the normal dpkg config-file handling -- or anything
> that wouldn't require the files to be kept in two places -- work?) Or
> is it something else?
>
> Or has this already been discussed to death on Debian lists? ;-)
I'm not a debian developer, maintainer or anything more than a debian user,
so I'll just copy & paste a part from the README.Debian of the udev package:
-----
MAINTAINERS BEWARE: the use of /etc/udev/rules.d/ by other packages is
discouraged, except when only RUN rules are added.
If you think your package needs to create a file there, then please
contact the udev package maintainer and explain your needs.
Packages should NEVER create files in /etc/udev/rules.d/, but create a
symlink the first time the package is installed (and never try again, to
allow the local system administrator to remove it).
-----
A mail that illustrates this can be found at:
http://lists.alioth.debian.org/pipermail/pkg-alsa-devel/2006-March/003158.html
There is a debhelper for udev rules called 'dh_installudev' which says:
-----
DESCRIPTION
dh_installudev is a debhelper program that is responsible for
installing udev rules files.
Files named debian/package.udev will be installed as etc/udev/pack‐
age.rules in the package build directory.
Then postinst and postrm commands are automatically generated to enable
the rules file when the package is first installed, by creating a sym‐
link to it in the /etc/udev/rules.d/ directory. See dh_installdeb(1)
for an explanation of how this works.
-----
So I believe that this matches both of your answers, about better
removal/addition and about the long discussion :-)
I've CC'd this to Marco d'Itri <md@linux.it>, which is the debian udev
package maintainer and may answer your questions in more depth.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 226 bytes --]
_______________________________________________
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:[~2006-12-10 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 18:04 udev patch Stefanos Harhalakis
2006-12-09 19:42 ` Bryan Kadzban
2006-12-10 13:53 ` Stefanos Harhalakis [this message]
2006-12-10 19:01 ` Bryan Kadzban
2006-12-14 19:10 ` Marco d'Itri
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=200612101553.08434.v13@it.teithe.gr \
--to=v13@it.teithe.gr \
--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).