public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Greg KH <greg@kroah.com>
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 22:49:51 +0200	[thread overview]
Message-ID: <1075841390.7473.57.camel@nosferatu.lan> (raw)
In-Reply-To: <20040203201359.GB19476@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 544 bytes --]

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?


Thanks,

-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-02-03 20:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 20:13 [ANNOUNCE] udev 016 release Greg KH
2004-02-03 20:49 ` Martin Schlemmer [this message]
2004-02-03 23:14   ` Greg KH
2004-02-03 21:28 ` Martin Schlemmer
2004-02-03 23:03   ` Martin Schlemmer
2004-02-03 23:13     ` Greg KH
2004-02-04  0:01       ` Kay Sievers
2004-02-04  4:25       ` Martin Schlemmer
2004-02-08 11:27         ` Martin Schlemmer
2004-02-08 13:01           ` Martin Schlemmer
2004-02-03 21:43 ` Martin Schlemmer
2004-02-11 22:13   ` Greg KH
2004-02-11 22:27     ` Martin Schlemmer
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=1075841390.7473.57.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=greg@kroah.com \
    --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