From: Bernd Schubert <bs@q-leap.de>
To: linux-raid@vger.kernel.org
Subject: Re: Debian and udev (was: RFC - device names and mdadm with some reference to udev.)
Date: Sat, 1 Nov 2008 00:08:05 +0100 [thread overview]
Message-ID: <20081031230805.GA13203@lanczos.q-leap.de> (raw)
In-Reply-To: <20081031205434.GB9554@piper.oerlikon.madduck.net>
On Fri, Oct 31, 2008 at 09:54:34PM +0100, martin f krafft wrote:
> also sprach Kay Sievers <kay.sievers@vrfy.org> [2008.10.28.0103 +0100]:
> > All stuff in /lib/udev/rules.d/ is not marked as "config" in the
> > package and will be overwritten with a udev update, regardless if the
> > content has been edited or not. We moved the "default" rules there
> > because people edited the files in /etc and wondered why stuff broke
> > in weird ways on updates. /etc/udev/rules.d/ is for "user rules" or
> > on-the-fly created system specific ones, like persistent net names and
> > cdrom rules. In an ideal setup you would be able to do rm -rf
> > /etc/udev/rules.d/*, reboot, and start device configuration from
> > scratch.
> >
> > Debian didn't catch up the last months, they use an older version of
> > udev, and have always had thier very own idea of rules, that didn't
> > match the udev default.
>
> Debian is nearing a release, we have other things to worry about.
>
> But to clarify Kay's statement:
> yes, we cannot follow the udev default if we accept that users might
> want to edit udev rules, even if they risk breaking stuff. We very
> specifically discourage the administrator to write to anywhere but
> /usr/local and /etc for good reasons. Thus, the rules have to go to
> /etc/udev.
Rules written by the adminstrator have to go to /etc/udev, but system
default rules certainly not. And IMHO it is plain wrong when
Debian maintainers think they know better than the rest of the world.
(And yes, I'm a debian user myself and also a package maintainer).
Cheers,
Bernd
next prev parent reply other threads:[~2008-10-31 23:08 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 22:56 RFC - device names and mdadm with some reference to udev Neil Brown
2008-10-27 8:22 ` martin f krafft
2008-10-27 15:13 ` Doug Ledford
2008-10-27 16:10 ` Andre Noll
2008-10-27 16:37 ` Kay Sievers
2008-10-27 16:59 ` martin f krafft
2008-10-27 18:31 ` Kay Sievers
2008-10-28 6:21 ` Luca Berra
2008-10-27 17:24 ` Doug Ledford
2008-10-27 23:36 ` Neil Brown
2008-10-29 18:49 ` Doug Ledford
2008-10-28 6:32 ` Luca Berra
2008-10-28 9:42 ` occasional bitmap was " David Greaves
2008-10-27 17:30 ` Andre Noll
2008-10-27 16:13 ` Kay Sievers
2008-10-27 22:37 ` Neil Brown
2008-10-27 22:51 ` Kay Sievers
2008-10-27 23:56 ` Neil Brown
2008-10-28 0:20 ` Kay Sievers
2008-10-28 6:17 ` Luca Berra
2008-10-27 12:41 ` Kay Sievers
2008-10-27 13:23 ` David Lethe
2008-10-27 23:27 ` Neil Brown
2008-10-27 23:48 ` David Lethe
2008-10-27 13:24 ` Andre Noll
2008-10-27 14:20 ` Kay Sievers
2008-10-27 23:23 ` Neil Brown
2008-10-28 0:03 ` Kay Sievers
2008-10-28 0:43 ` Neil Brown
2008-10-28 1:16 ` Kay Sievers
2008-10-28 1:44 ` Neil Brown
2008-10-28 1:52 ` Kay Sievers
2008-10-28 1:54 ` Kay Sievers
2008-10-31 20:54 ` Debian and udev (was: RFC - device names and mdadm with some reference to udev.) martin f krafft
2008-10-31 23:08 ` Bernd Schubert [this message]
2008-10-29 8:56 ` RFC - device names and mdadm with some reference to udev Gabor Gombas
2008-10-31 20:49 ` mdp devices on Debian (was: RFC - device names and mdadm with some reference to udev.) martin f krafft
2008-10-30 17:18 ` RFC - device names and mdadm with some reference to udev Doug Ledford
2008-10-31 9:45 ` Neil Brown
2008-11-03 9:29 ` Gabor Gombas
2008-11-03 10:33 ` Kay Sievers
2008-11-03 11:58 ` Gabor Gombas
2008-11-03 12:11 ` Kay Sievers
2008-11-03 14:34 ` Doug Ledford
2008-11-03 15:20 ` Dan Williams
2008-11-07 6:13 ` Neil Brown
2008-11-02 13:47 ` Luca Berra
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=20081031230805.GA13203@lanczos.q-leap.de \
--to=bs@q-leap.de \
--cc=linux-raid@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.