linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott James Remnant <scott@canonical.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: default udev rules
Date: Mon, 11 Aug 2008 15:36:59 +0000	[thread overview]
Message-ID: <1218469019.14932.20.camel@quest> (raw)
In-Reply-To: <1218277281.31266.32.camel@lgn.site>

[-- Attachment #1: Type: text/plain, Size: 2562 bytes --]

On Mon, 2008-08-11 at 17:27 +0200, Kay Sievers wrote:

> On Mon, 2008-08-11 at 16:21 +0100, Scott James Remnant wrote:
> > On Mon, 2008-08-11 at 16:54 +0200, Kay Sievers wrote:
> > 
> > > > Setting any group names, and thus any group-writable permissions; our
> > > > rules have these split out into a separate file which is added later.
> > > 
> > > That makes no difference, assigning perms works any time.
> > > 
> > But assigning groups doesn't.
> 
> Wrong.
> 
Last time I tried it, I had screenfuls of errors.

> > As you're well aware, we run udev in the initramfs, where any attempt to
> > look up a group name will simply end in an error.
> 
> Copy over /etc/groups and done! And who cares about groups in initramfs,
> we fall back to root then, and done!
> 
Can't just copy over groups, we'd also have to copy over all of the
nsswitch configuration, maybe start an LDAP server, etc.

It's just far too much when it's just as simple to set the group names
in a separate udev rule.

> I'm still looking forward to the facts. Thanks!
> 
Frankly Kay, your attitude is incredibly hostile today.

You'd like us to use a set of udev rules in the tarball which are based
on the SuSE and RedHat ones - that's fine, I fully appreciate that
getting some harmony between the distributions would be nice.

But you seem unwilling to appreciate that in some cases, they don't work
for other people - or cause new problems.

And we already have rules that *do* work for us, and that *aren't*
causing us any problems.


We have concerns, and you're telling us that they are petty.

You're also telling us that *we* have to do the work to use your rules,
and have the fight with you to get your rules changed where we need to.
Your attitude while doing this is hostile, this is hardly putting us in
the mood to have that fight.


Right now, we have working udev packages.  We use a mix of the upstream
rules (for things like persistent storage) and our own.  Every now and
then, I check what needs to be merged back into our own rules.

At some point in the future, I'll sit down and work through the
differences and give you some patches.

I'd like to think you'd apply those patches without question, or maybe
have a little light-hearted discussion about them; but your current mood
suggests to me that you'd simply tell me how wrong my patches are.

So how's that supposed to encourage me to do that work, when I have
plenty of other things to do?

Scott
-- 
Scott James Remnant
scott@canonical.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-08-11 15:36 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-09 10:21 default udev rules Kay Sievers
2008-08-09 15:23 ` Marco d'Itri
2008-08-09 18:55 ` Greg KH
2008-08-09 19:30 ` Marco d'Itri
2008-08-09 19:44 ` Greg KH
2008-08-09 20:03 ` Kay Sievers
2008-08-10 18:07 ` Scott James Remnant
2008-08-10 19:18 ` Marco d'Itri
2008-08-10 19:25 ` Greg KH
2008-08-10 19:47 ` Kay Sievers
2008-08-10 20:35 ` Kay Sievers
2008-08-11  8:45 ` Kay Sievers
2008-08-11  8:58 ` Marco d'Itri
2008-08-11  9:01 ` Marco d'Itri
2008-08-11 13:03 ` Scott James Remnant
2008-08-11 14:54 ` Kay Sievers
2008-08-11 15:18 ` David Zeuthen
2008-08-11 15:20 ` Scott James Remnant
2008-08-11 15:21 ` Scott James Remnant
2008-08-11 15:27 ` Kay Sievers
2008-08-11 15:28 ` Kay Sievers
2008-08-11 15:35 ` Scott James Remnant
2008-08-11 15:36 ` Scott James Remnant [this message]
2008-08-11 15:42 ` Scott James Remnant
2008-08-11 15:50 ` Kay Sievers
2008-08-11 16:00 ` Scott James Remnant
2008-08-11 16:06 ` piterpk
2008-08-11 16:14 ` Marco d'Itri
2008-08-11 16:19 ` Kay Sievers
2008-08-11 16:26 ` Marco d'Itri
2008-08-11 16:34 ` Kay Sievers
2008-08-11 16:37 ` Greg KH
2008-08-11 16:41 ` Kay Sievers
2008-08-11 16:45 ` Marco d'Itri
2008-08-11 16:48 ` Marco d'Itri
2008-08-11 16:48 ` Kay Sievers
2008-08-11 16:53 ` Scott James Remnant
2008-08-11 16:54 ` Marco d'Itri
2008-08-11 16:58 ` Greg KH
2008-08-11 17:00 ` Kay Sievers
2008-08-11 17:01 ` Kay Sievers
2008-08-11 17:06 ` Scott James Remnant
2008-08-11 17:08 ` Scott James Remnant
2008-08-11 17:10 ` Scott James Remnant
2008-08-11 17:24 ` Kay Sievers
2008-08-11 17:37 ` David Zeuthen
2008-08-11 17:40 ` Scott James Remnant
2008-08-11 18:00 ` Scott James Remnant
2008-08-11 18:01 ` Kay Sievers
2008-08-11 18:06 ` Scott James Remnant
2008-08-11 22:26 ` Greg KH
2008-08-11 22:28 ` Greg KH
2008-08-11 22:29 ` Greg KH
2008-08-11 23:40 ` Scott James Remnant
2008-08-11 23:41 ` Scott James Remnant
2008-08-12  0:00 ` Greg KH
2008-08-12 20:32 ` Kay Sievers
2008-08-13  1:53 ` H. Peter Anvin
2008-08-13  1:55 ` H. Peter Anvin
2008-11-18 17:39 ` Harald Hoyer
2008-11-18 17:52 ` Kay Sievers
2008-11-19  2:09 ` Piter PUNK

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=1218469019.14932.20.camel@quest \
    --to=scott@canonical.com \
    --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).