linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik van Konijnenburg <ekonijn@xs4all.nl>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 004 release
Date: Sat, 25 Oct 2003 10:40:49 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106707889914701@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106675444401980@msgid-missing>

On Fri, Oct 24, 2003 at 03:42:26PM +0200, Kay Sievers wrote:
> On Wed, Oct 22, 2003 at 04:52:10PM -0700, Greg KH wrote:
> > On Wed, Oct 22, 2003 at 05:24:24AM +0200, Kay Sievers wrote:
> > > The problem is that the resolving of owner/group name to its numeric id
> > > needs shared libc libs. What does this mean for klibc?
> > 
> > Hm, not good.  udev has to be able to be linked statically.  I just got
> > the klibc build working properly, and it makes a world of difference in
> > size compared to glibc.
> > 
> > Could we convert the permissions file to numbers at build time?  That
> > way the /etc/* file parsing would not be needed.  Yeah, it's not the
> > nicest solution.  Anyone know of any other way we can do this properly?
> 
> here is the patch for ownership setting on the ceated device node,
> supporting only numeric id's given in udev.permissions.
> For now, it may be better than nothing.

What about the following approach?

- You don't want uid/gid resolved at build time or specified
  numericaly, it would make the sysadm very unhappy.
- On the other hand, nobody cares much about device ownership
  before /etc/passwd is mounted and the nsswitch is operational.
  At that time, it is sufficient for udev to just create the device,
  so that root can mount it.
- So you really need two versions of udev, one suitable for use on
  initramfs (linked to klibc) that ignores ownership while creating
  devices, another (linked to glibc) that does proper user/group
  name resolution, using /etc/group, LDAP or whatever they'll
  think up next.
- Somewhere early in the boot cycle you will need a script that
  switches from the minimal udev to full udev and that applies
  the ownership info from the config file to devices that already
  have been created.

Regards,
Erik



-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
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:[~2003-10-25 10:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 16:28 [ANNOUNCE] udev 004 release Greg KH
2003-10-21 20:34 ` Kay Sievers
2003-10-21 20:50 ` Greg KH
2003-10-21 21:45 ` Jesse Barnes
2003-10-21 22:13 ` Greg KH
2003-10-22  1:46 ` Greg KH
2003-10-22  3:24 ` Kay Sievers
2003-10-22  7:09 ` Daniel Stekloff
2003-10-22  8:52 ` Ananth N Mavinakayanahalli
2003-10-22 23:52 ` Greg KH
2003-10-24 13:42 ` Kay Sievers
2003-10-25 10:40 ` Erik van Konijnenburg [this message]
2003-10-25 10:40 ` Erik van Konijnenburg
2003-11-14  1:36 ` Greg KH
2003-11-23 21:32 ` 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=marc-linux-hotplug-106707889914701@msgid-missing \
    --to=ekonijn@xs4all.nl \
    --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).