From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-hotplug-devel] Re: udev - TODO update
Date: Tue, 02 Mar 2004 20:15:35 +0000 [thread overview]
Message-ID: <20040302201534.GA3191@kroah.com> (raw)
In-Reply-To: <20040212234538.GC21117@vrfy.org>
On Tue, Mar 02, 2004 at 08:32:38AM +0100, Wout Mertens wrote:
> Sunday at 05:01, Kay Sievers ponderously produced:
>
> > On Sat, Feb 28, 2004 at 05:37:10PM -0500, Robert Love wrote:
> > > On Sat, 2004-02-28 at 17:19, Kay Sievers wrote:
> > >
> > > > I did it :)
> > > > Please have a look. If this is what you want, I will solve the klibc
> > > > beast.
> > >
> > > You are incredible, Kay. This is exactly what I was planning.
> >
> > And this is exactly what I want to hear :)
> >
> > > Adding utmp parsing to klibc cannot be fun, though.. ;)
> >
> > Oh, it's only list of a static record in a file. So here is the first try.
>
> Uhm, actually, you should use getpwuid() on a real system. /etc/group is
> just some old file. /etc/nsswitch.conf tells you where to find the real
> information, which could be on LDAP or whatnot. getent() does this for
> you.
>
> Of course, klibc probably doesn't have getpwuid(). So for early
> userspace your implementation may be correct.
>
> But consider my previous post: Why not just copy the permissions from
> /dev/console?
Because udev creates /dev/console :)
thanks,
greg k-h
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-03-02 20:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 23:45 udev - TODO update Kay Sievers
2004-02-13 1:26 ` Greg KH
2004-02-13 1:59 ` Kay Sievers
2004-02-13 6:16 ` Daniel Drake
2004-02-13 8:31 ` Olaf Hering
2004-02-13 17:52 ` Mike Frysinger
2004-02-13 19:34 ` Daniel Stekloff
2004-02-13 22:53 ` Greg KH
2004-02-17 1:41 ` Greg KH
2004-02-17 1:48 ` Mike Frysinger
2004-02-27 0:41 ` Kay Sievers
2004-02-27 0:49 ` Robert Love
2004-02-27 1:00 ` Greg KH
2004-02-27 1:13 ` Mike Frysinger
2004-02-27 1:23 ` Mike Waychison
2004-02-27 1:27 ` Robert Love
2004-02-27 1:36 ` Robert Love
2004-02-27 2:24 ` Bill Nottingham
2004-02-27 11:03 ` Robert McMeekin
2004-02-27 15:45 ` Kay Sievers
2004-02-27 17:35 ` Greg KH
2004-02-27 17:37 ` Greg KH
2004-02-27 18:08 ` Mike Waychison
2004-02-27 19:10 ` Bill Nottingham
2004-02-27 19:19 ` Robert Love
2004-02-27 19:20 ` Robert Love
2004-02-28 0:55 ` Greg KH
2004-02-28 13:07 ` Erik van Konijnenburg
2004-02-28 16:47 ` Robert Love
2004-02-28 22:19 ` Kay Sievers
2004-02-28 22:37 ` Robert Love
2004-02-29 4:01 ` Kay Sievers
2004-03-01 22:44 ` Greg KH
2004-03-01 23:05 ` Robert Love
2004-03-01 23:16 ` Greg KH
2004-03-02 0:04 ` Kay Sievers
2004-03-02 0:09 ` Greg KH
2004-03-02 7:24 ` [linux-hotplug-devel] " Wout Mertens
2004-03-02 7:32 ` Wout Mertens
2004-03-02 20:15 ` Greg KH [this message]
2004-03-02 20:55 ` Wout Mertens
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=20040302201534.GA3191@kroah.com \
--to=greg@kroah.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).