From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - simple klibc textual uid/gid handling
Date: Mon, 23 Feb 2004 18:52:54 +0000 [thread overview]
Message-ID: <20040223185254.GE21453@kroah.com> (raw)
In-Reply-To: <20040223181935.GA21904@vrfy.org>
On Mon, Feb 23, 2004 at 07:46:49PM +0100, Kay Sievers wrote:
> On Mon, Feb 23, 2004 at 10:21:01AM -0800, Greg KH wrote:
> > On Mon, Feb 23, 2004 at 07:19:35PM +0100, Kay Sievers wrote:
> > > Here we get a very dumb getpwnam() and getgrnam() for klibc to
> > > stop the confusion of not handling textual id's if klibc is used.
> > >
> > > If used with initrd we just need to copy the /etc/passwd and /etc/group
> > > file and all should work well.
> >
> > Argh! I was just starting to work on this myself! Will I ever get to
> > implement a new feature in udev again... :)
>
> Oh, and I announced it today 4 hours ago on the list.
> Maybe I need to cc you directly if new things are in work :)
Heh, no, I haven't caught up on email from the weekend yet :)
> Just to avoid conflicts:
> The next thing I will do is to check the string handling
> for overflows. :)
Keep up the great work.
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
prev parent reply other threads:[~2004-02-23 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 18:19 [PATCH] udev - simple klibc textual uid/gid handling Kay Sievers
2004-02-23 18:21 ` Greg KH
2004-02-23 18:46 ` Kay Sievers
2004-02-23 18:52 ` Greg KH [this message]
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=20040223185254.GE21453@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).