Re: Permissions in udev don't work when klibc is used ?

[Darren Salt <linux@youmustbejoking.demon.co.uk>]

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