From: Greg KH <greg@kroah.com>
To: Martin Schlemmer <azarah@nosferatu.za.org>
Cc: linux-hotplug-devel@lists.sourceforge.net,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] udev 016 release
Date: Tue, 03 Feb 2004 23:14:56 +0000 [thread overview]
Message-ID: <20040203231455.GB22058@kroah.com> (raw)
In-Reply-To: <1075841390.7473.57.camel@nosferatu.lan>
On Tue, Feb 03, 2004 at 10:49:51PM +0200, Martin Schlemmer wrote:
> On Tue, 2004-02-03 at 22:13, Greg KH wrote:
>
> >
> > Right now, udevsend and udev are built against klibc (udevsend
> > is only 2.5Kb big), and udevd is linked dynamically against
> > glibc, due to it using pthreads. This is ok, as udev can
> > still be placed into initramfs and run at early boot, it's
> > only after init starts up that udevsend and udevd will kick
> > in.
> >
>
> I am guessing this breaks group names (and not gid's) in
> udev.permissions? Or was support added to klibc?
Sorry, that should have read something to the effect that the .rpm is
built using klibc, and that udevd can't be build against it yet due to
pthreads being used.
It's entirely possible to build everything against glibc, and then you
get back the group name stuff for the udev.permission file.
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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-02-03 23:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 20:13 [ANNOUNCE] udev 016 release Greg KH
2004-02-03 21:30 ` Marco d'Itri
2004-02-03 22:23 ` Eric Sandall
2004-02-03 22:46 ` Greg KH
[not found] ` <1075843712.7473.60.camel@nosferatu.lan>
[not found] ` <1075849413.11322.6.camel@nosferatu.lan>
2004-02-03 23:13 ` Greg KH
2004-02-04 0:01 ` Kay Sievers
[not found] ` <1075841390.7473.57.camel@nosferatu.lan>
2004-02-03 23:14 ` Greg KH [this message]
2004-02-03 23:33 ` Eric Sandall
2004-02-03 23:53 ` Greg KH
2004-02-04 0:35 ` Eric Sandall
2004-02-04 22:31 ` Greg KH
[not found] ` <1075844602.7473.75.camel@nosferatu.lan>
2004-02-11 22:13 ` Greg KH
[not found] ` <1076538429.22542.12.camel@nosferatu.lan>
2004-02-12 1:19 ` Greg KH
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=20040203231455.GB22058@kroah.com \
--to=greg@kroah.com \
--cc=azarah@nosferatu.za.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@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).