All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Permissions in udev don't work when klibc is used ?
Date: Mon, 23 Feb 2004 14:30:28 +0000	[thread overview]
Message-ID: <1077546628.1105.14.camel@pim> (raw)
In-Reply-To: <200402231118.26239.remco@d-compu.dyndns.org>

On Mon, 2004-02-23 at 15:01, Remco wrote:
> On Monday 23 February 2004 11:47, you wrote:
> > On Mon, 2004-02-23 at 11:18, Remco wrote:
> > > P.S:
> > > Unless I overlooked it, maybe a fair warning should be in place to tell
> > > people that permissions don't work when using klibc. (If my findings are
> > > correct off course)
> >
> > Hey, how about reading the man pages?
> >
> > "If  udev  was  built using klibc or is used before the user database is
> > accessible (e.g.  initrd(4)), only numeric owner and group  values  may
> > be used."
> >
> > thanks,
> > Kay
> 
> 
> O.k., I found that, however, it wasn't the obvious place for me to look.
> I looked for the word "permission" in the udev source tree and checked the 
> Changlog, FAQ, README and TODO but none of these documents gave an 
> explanation. (yes, udev.8 was among the documents found, but I didn't read it 
> at that point) Personally, I tend to read man pages after I install a 
> package, as I expect them to guide me through an installed, to be configured,  
> package, not one to be installed. (This may be a bad assumption)
> 
> Since one has to decide whether to use klibc or not before starting to 
> compile, I expected any (dis)advantages of each approach to be mentioned in 
> an INSTALL or README.
> 
> Besides that, if permissions are important enough, I think the one line in the 
> man page doesn't stand out enough to point out that permissions might not 
> work as expected under certain circumstances. (I simply expected user and 
> group names to work)

Yes, I agree. But remember udev is so very young and not perfect.
We worked hard on more important features the last weeks, so this was
simply not handled.
I will post a patch tonight, that extends klibc_fixups.* which is able
to parse /etc/passdw, /etc/group. It already works on my box.

So just wait a few hours :)

thanks,
Kay



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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:[~2004-02-23 14:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 10:18 Permissions in udev don't work when klibc is used ? Remco
2004-02-23 10:47 ` Kay Sievers
2004-02-23 14:01 ` Remco
2004-02-23 14:30 ` Kay Sievers [this message]
2004-02-23 15:18 ` Remco
2004-02-23 16:39 ` Olaf Hering
2004-02-23 18:31 ` Kay Sievers
2004-02-23 18:55 ` Olaf Hering
2004-02-23 19:01 ` Darren Salt
2004-02-23 19:10 ` Kay Sievers

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=1077546628.1105.14.camel@pim \
    --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 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.