From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 004 release
Date: Wed, 22 Oct 2003 23:52:10 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106686825619939@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106675444401980@msgid-missing>
On Wed, Oct 22, 2003 at 05:24:24AM +0200, Kay Sievers wrote:
> On Tue, Oct 21, 2003 at 01:50:46PM -0700, Greg KH wrote:
> > On Tue, Oct 21, 2003 at 10:34:04PM +0200, Kay Sievers wrote:
> >
> > > I was looking how to set permissions on the created node.
> > > What is the future of struct device_attr?
> > > Same values are in struct udevice now?
> >
> > device_attr will go away. I was leaving the namedev.c file alone when I
> > did the udevice cleanups so that merging with Dan's changes would be
> > easier. Now I'm about to go clean that up.
>
> Hi,
>
> attached is a patch for udev-add.c to set file permissions.
Nice.
> 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?
Remember we have to be able to create nodes before the real /etc is even
mounted.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
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:[~2003-10-22 23:52 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 [this message]
2003-10-24 13:42 ` Kay Sievers
2003-10-25 10:40 ` Erik van Konijnenburg
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-106686825619939@msgid-missing \
--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).