linux-kernel - Re: /sys/$DEVPATH/uevent vs uevent attributes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <45A83D37.2010807@tls.msk.ru>
Date:	Sat, 13 Jan 2007 05:00:23 +0300
From:	Michael Tokarev <mjt@....msk.ru>
To:	Greg KH <greg@...ah.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: /sys/$DEVPATH/uevent vs uevent attributes

Greg KH wrote:
> On Fri, Jan 12, 2007 at 10:32:10PM +0300, Michael Tokarev wrote:
>> (No patch at this time, -- just asking about an.. idea ;)
> 
> Let's see what such a patch looks like to see if it would be workable or
> not.

Umm.. it's definitely workable, and even almost trivial.

Just splitting kobject_uevent() routine into two parts, one to format
the environment variables, and one to actually send things over netlink
and executing the hotplug_helper if defined, and using the first part
to format the content of `uevent' file will do the trick.

I don't know how to do the last part.

> And no one forces you to use udev, I have machines with a static /dev
> that work just fine :)

It has less and less chances to work correctly.  For example, this dynamic
sdX thing, when I don't know anymore which sdX is which, without some help
from /dev/disk/by-XXX/.

And more and more software requires udev, at least as packages by distos.
For example, today I've got rid of udev on one of our servers, which has
been installed (debian) due to xen-utils having Depends: udev.  Even when
it doesn't *really* *require* udev, -- i replaced the whole thing with a
5-line shell script.

/mjt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/