From: Darren Salt <linux@youmustbejoking.demon.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: Permissions in udev don't work when klibc is used ?
Date: Mon, 23 Feb 2004 19:01:40 +0000 [thread overview]
Message-ID: <4C855FEA33%linux@youmustbejoking.demon.co.uk> (raw)
In-Reply-To: <200402231118.26239.remco@d-compu.dyndns.org>
I demand that Kay Sievers may or may not have written...
[snip: user/group names, klibc]
> I want to keep the difference between glibc and klibc as small as possible.
> It's easy to do with just a few lines and it's better than a magic update
> script and a udev.permissions without user readable content.
This seems reasonable...
> And initrd just needs a copy of the system files.
And when they're updated (assuming that the change, be it in a udev
configuration file or /etc/passwd or /etc/group or similar) affects
ownership)? Automatically rebuild the image, rerun lilo? :-)
Not that it really matters: ISTM that an early udev could populate the
initial /dev (almost) entirely from sysfs, using default settings of
root:root 0600. Once into early userspace, a "full" udev would be run, with
one of the effects being to set access rights to something more appropriate.
(I don't use an initrd for non-rescue non-install boots, and plan to (try to)
continue this even if/when It Is Decreed That Thou Shalt Use An Initrd, It Is
No Longer Optional. I just don't *want* an initrd...)
--
| Darren Salt | d youmustbejoking,demon,co,uk | nr. Ashington,
| Debian, | s zap,tartarus,org | Northumberland
| RISC OS | @ | Toon Army
| <URL:http://www.youmustbejoking.demon.co.uk/progs.packages.html>
tartar sauce: n. # rm -rf /usr/{local/,}src/*
-------------------------------------------------------
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-23 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 10:18 Permissions in udev don't work when klibc is used ? Remco
2004-02-23 10:47 ` Kay Sievers
2004-02-23 14:01 ` Remco
2004-02-23 14:30 ` Kay Sievers
2004-02-23 15:18 ` Remco
2004-02-23 16:39 ` Olaf Hering
2004-02-23 18:31 ` Kay Sievers
2004-02-23 18:55 ` Olaf Hering
2004-02-23 19:01 ` Darren Salt [this message]
2004-02-23 19:10 ` Kay Sievers
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=4C855FEA33%linux@youmustbejoking.demon.co.uk \
--to=linux@youmustbejoking.demon.co.uk \
--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).