- Apr 27, 2005
-
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
Thanks to Kay for pointing it out.
-
Greg Kroah-Hartman authored
Thanks to Kay for pointing it out.
-
Tobias Klauser authored
Thanks-To: Tobias Klauser <tklauser@access.unizh.ch> While crawling through the udev manpage I noticed some typos and other grammatical errors. English is not my native language, so I'm not sure if I fixed everything right. I would be glad if any English-speaking person could check this patch before applying.
-
Kay Sievers authored
-
Kay Sievers authored
Leave that part up to the one who itegrates udev into a system as there is much more to care of than to call a init stript for a dynamic dev.
-
Kay Sievers authored
-
Kay Sievers authored
-
Kay Sievers authored
-
Kay Sievers authored
-
Kay Sievers authored
-
Kay Sievers authored
-
Kay Sievers authored
-
Kay Sievers authored
Initialize the defaults in udev_config.c instead of namedev.c. Replace macro by expanded code. Switch to mode_t instead of string value. Add and clarify some comments.
-
Kay Sievers authored
-
Kay Sievers authored
-
Kay Sievers authored
Remove udev.bus, cause it's currently unused and newer kernels will pass it in the hotplug environment as PHYSDEVBUS. Remove udev.action, cause it's unused. Rename udev_set_values() to udev_init_device().
-
Kay Sievers authored
Accept event without a subsystem and pass it through udevd. Pass empty environment while starting udevd.
-
Kay Sievers authored
-
Kay Sievers authored
Add UDEV_LOG to the man udev man page. Remove mention of specific variables from the udevd/udevsend man page as we changed to pass the whole environment. Correct printed Usage: of udevtest and udevinfo. Init the config in udevtest earlier to accept input with and without the sysfs mount point.
-
Kay Sievers authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
Damm, it's hard to merge a multi-line tree into one flat line at times...
-
Kay Sievers authored
The /etc/dev.d/input/input.dev was called twice for /dev/input/mouse. Skip the execution if we get a directory named after the subsystem. Move UDEV_NO_DEVD where it belongs.
-
Kay Sievers authored
-
Kay Sievers authored
This cuts the size of the binaries, as only objects that are actually used are linked into the binary: 45592 -> 43608 udev 4380 -> 4380 udevsend 10380 -> 4652 udevd 34732 -> 33100 udevinfo 45432 -> 37208 udevtest
-
Kay Sievers authored
-
sschweizer@gmail.com authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
sjoerd@spring.luon.net authored
I just noticed that the DEVNAME enviroment variable isn't being set anymore in udev 0.046 on device removal, while it was being set in 0.042. We're using the property tto do umount -l <devices> when a block device is removed. Afaik there is no other way to associate a device with it's DEVNAME on removal ? Also are there cases where doing umount -l on the removed devices is wrong? I guess the device is gone, so there is no sense in keeping it mounted (it's not like the filesystem is gonna come back in a sane state again).. Attached (trivial) patch brings back the DEVNAME variable on device removal.
-
Greg Kroah-Hartman authored
-
Kay Sievers authored
If /proc/sys/kernel/hotplug points to /sbin/udevsend we handle the whole hotplug event with multiplexing /etc/hotplug.d/.
-