linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Only lookup uid/gid when applying rules
Date: Sat, 05 Aug 2006 03:07:14 +0000	[thread overview]
Message-ID: <1154747234.3540.100.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <200608011135.25769.uberlord@gentoo.org>

On Sat, 2006-08-05 at 03:59 +0100, Roy Marples wrote:
> On Saturday 05 August 2006 03:42, you wrote:
> > > Now should the onus be on distro's to magically add foo even though it
> > > *may* be not needed, or should it be on udev to work out if it even needs
> > > to lookup the user/group "foo"?
> >
> > You should fix your base-system, which is causing the trouble, simple as
> > that.
> 
> So, we have to keep in sync all user/groups udev requires?

Yes, and not only for udev.

> As opposed to adding them dynamically when the user actually installs the 
> software the uses said users/groups? Or even has the hardware?

Well, just make sure you don't have the rules that require entries you
don't want to add to your system.

> Case in point - my LDAP server has no need for the user/group tss other than 
> the fact that udev requires it due to a rule that will never be applied.

Sure, put it in /etc, where system groups belong.

> And you still think my base-system should be fixed?

Definitely.

> What happens down the road when you next require user foo and group
> bar due to a rule which may or may not be needed?

Just make sure, the udev rules are in sync with the rest of your system.

> I give up. It's hopeless. I just cannot convice you that it's better to be 
> slow than broken.

Right, you can't. Not every system is broken like yours seems to be,
therefore we will not optimize udev for such broken systems.

Kay


-------------------------------------------------------------------------
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ÞVDEV
_______________________________________________
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

  parent reply	other threads:[~2006-08-05  3:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 10:35 [PATCH] Only lookup uid/gid when applying rules Roy Marples
2006-08-01 12:35 ` Kay Sievers
2006-08-01 12:54 ` Roy Marples
2006-08-01 13:12 ` Kay Sievers
2006-08-01 13:56 ` Roy Marples
2006-08-04 23:32 ` Roy Marples
2006-08-05  0:04 ` Kay Sievers
2006-08-05  0:29 ` Marco d'Itri
2006-08-05  0:40 ` Kay Sievers
2006-08-05  0:43 ` Marco d'Itri
2006-08-05  0:49 ` Kay Sievers
2006-08-05  0:52 ` Marco d'Itri
2006-08-05  2:20 ` Roy Marples
2006-08-05  2:42 ` Kay Sievers
2006-08-05  2:59 ` Roy Marples
2006-08-05  3:07 ` Kay Sievers [this message]
2006-08-05  3:37 ` Roy Marples

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=1154747234.3540.100.camel@pim.off.vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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).