From: Robert Love <rml@ximian.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev - TODO update
Date: Sat, 28 Feb 2004 22:37:10 +0000 [thread overview]
Message-ID: <1078007830.11422.7.camel@localhost> (raw)
In-Reply-To: <20040212234538.GC21117@vrfy.org>
On Sat, 2004-02-28 at 17:19, Kay Sievers wrote:
> I did it :)
> Please have a look. If this is what you want, I will solve the klibc
> beast.
You are incredible, Kay. This is exactly what I was planning.
Adding utmp parsing to klibc cannot be fun, though.. ;)
> We don't need the same for the group ownership, or do we?
Probably not, although I guess I could see wanting to make the node also
owned by the user's primary group. That would be ultra trivial - it is
just the fourth field in the user's line in passwd.
> Oh, I don't think that we still want the to implement daemon. udevd simply
> calls our normal udev now and this seems to work well.
> Or do I miss something? Greg?
No, the current implementation of the daemon does not have any issues.
I was just worried at the time. As long as we parse the permissions
file on each node creation, we are fine.
Robert Love
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-02-28 22:37 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 23:45 udev - TODO update Kay Sievers
2004-02-13 1:26 ` Greg KH
2004-02-13 1:59 ` Kay Sievers
2004-02-13 6:16 ` Daniel Drake
2004-02-13 8:31 ` Olaf Hering
2004-02-13 17:52 ` Mike Frysinger
2004-02-13 19:34 ` Daniel Stekloff
2004-02-13 22:53 ` Greg KH
2004-02-17 1:41 ` Greg KH
2004-02-17 1:48 ` Mike Frysinger
2004-02-27 0:41 ` Kay Sievers
2004-02-27 0:49 ` Robert Love
2004-02-27 1:00 ` Greg KH
2004-02-27 1:13 ` Mike Frysinger
2004-02-27 1:23 ` Mike Waychison
2004-02-27 1:27 ` Robert Love
2004-02-27 1:36 ` Robert Love
2004-02-27 2:24 ` Bill Nottingham
2004-02-27 11:03 ` Robert McMeekin
2004-02-27 15:45 ` Kay Sievers
2004-02-27 17:35 ` Greg KH
2004-02-27 17:37 ` Greg KH
2004-02-27 18:08 ` Mike Waychison
2004-02-27 19:10 ` Bill Nottingham
2004-02-27 19:19 ` Robert Love
2004-02-27 19:20 ` Robert Love
2004-02-28 0:55 ` Greg KH
2004-02-28 13:07 ` Erik van Konijnenburg
2004-02-28 16:47 ` Robert Love
2004-02-28 22:19 ` Kay Sievers
2004-02-28 22:37 ` Robert Love [this message]
2004-02-29 4:01 ` Kay Sievers
2004-03-01 22:44 ` Greg KH
2004-03-01 23:05 ` Robert Love
2004-03-01 23:16 ` Greg KH
2004-03-02 0:04 ` Kay Sievers
2004-03-02 0:09 ` Greg KH
2004-03-02 7:24 ` [linux-hotplug-devel] " Wout Mertens
2004-03-02 7:32 ` Wout Mertens
2004-03-02 20:15 ` Greg KH
2004-03-02 20:55 ` Wout Mertens
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=1078007830.11422.7.camel@localhost \
--to=rml@ximian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.