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 00:40:45 +0000	[thread overview]
Message-ID: <1154738445.3540.42.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <200608011135.25769.uberlord@gentoo.org>

On Sat, 2006-08-05 at 02:29 +0200, Marco d'Itri wrote:
> On Aug 05, Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > Currently - with or without this patch - on a LDAP configuration that
> > does not return anything on bootup, we assign all OWNER/GROUP
> > permissions to "root". This can't be fixed later in the boot cycle, so
> > we have a serious problem anyway. The question is, if we really should
> > assign it to "root", or maybe fall-back to the built-in /etc/{passwd,groups}
> > parser? 
> I believe that falling back to the local static database would be more
> confusing. And probably useless too, since on a properly configured
> system an user would be first looked up in /etc/passwd and only if not
> there LDAP would be used.
> Debian had similar problems, and after quickly reading his introduction
> I did not find anything questionable in Roy's patch.

Well, on bootup we trigger events for _all_ devices, which will use most
of the rules, and we require the uid/gid to be resolved at that point in
time, long before we have access to the network. That's the issue we
need to solve, not to make it only faster to fail and assign "root" to
all nodes, be it the daemon or the event process who's doing that.

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  0:40 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 [this message]
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
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=1154738445.3540.42.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).