summaryrefslogtreecommitdiff
path: root/udev.c
AgeCommit message (Collapse)Author
2005-06-25unify execute_command() and execute_program()Kay Sievers
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-06-22fix the fix and change the file to wait for to the "bus" linkKay Sievers
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-06-22fix udevstart and let all events trvel trough udevKay Sievers
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-06-16udevd: control log-priority of the running daemon with udevcontrolKay Sievers
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-06-14udev: fix netdev RUN handlingHannes Reinecke
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-06-05udev: handle all events - not only class and block devicesKay Sievers
Handle all events with rules. If udev is expected to handle hotplug.d/ the exernal helper must be called. Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-06-05volume_id: use udev-provided log-levelKay Sievers
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-06-05udev: move dev.d/ handling to external helperKay Sievers
Modern rules are expected to call notification and postprocessing with the RUN key. For compatibility the current behavior can be emulated with an external helper. Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-06-05udevd: listen for netlink eventsKay Sievers
After the first valid netlink-event all event with a serial number received on the udevsend socket will be ignored. Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-04-26[PATCH] export DEVNAME to RUN-key executed programskay.sievers@vrfy.org
2005-04-26[PATCH] add RUN key to be able to run rule based notificationkay.sievers@vrfy.org
SUBSYSTEM=="block", RUN="/sbin/program" will execute the program only for block device events. ACTION="remove", SUBSYSTEM=="block", RUN"/sbin/program" will execute the program, if a block device is removed.
2005-04-26[PATCH] move execute_program to utils + add action to init_devicekay.sievers@vrfy.org
2005-04-26[PATCH] support log-priority levels in udev.confkay.sievers@vrfy.org
2005-04-26[PATCH] rename namedev_dev to udev_rulekay.sievers@vrfy.org
2005-04-26[PATCH] correct enum device_typekay.sievers@vrfy.org
2005-04-26[PATCH] replace strncpy()/strncat() by strlcpy()/strlcat()kay.sievers@vrfy.org
2005-04-26[PATCH] split udev and udevstartkay.sievers@vrfy.org
2005-04-26[PATCH] rename LOG to USE_LOG in all placeskay.sievers@vrfy.org
2005-04-26[PATCH] allow unlimitied count of symlinkskay.sievers@vrfy.org
2005-04-26[PATCH] correct udev_init_devicekay.sievers@vrfy.org
2005-04-26[PATCH] determine device type in udev_init_device()kay.sievers@vrfy.org
2005-04-26[PATCH] switch device type to enumkay.sievers@vrfy.org
2005-04-26[PATCH] handle renamed network interfaces properly if we manage hotplug.d/kay.sievers@vrfy.org
If we take over the hotplug call and manage the events we don't need to call the event fake script in dev.d/. Just set all expected values to the new network interface name and call hotplug.d/. This way the device renaming is completely handled inside of udev and userspace can't get confused.
2005-04-26[PATCH] complete removal of explicit udev permissions config filekay.sievers@vrfy.org
2005-04-26[PATCH] klibc supports LOG_PID now, so remove our own implementationkay.sievers@vrfy.org
2005-04-26bleah, more merge fixes...Greg KH
2005-04-26[PATCH] export DEVNAME regardless of the state of udev_dev_dkay.sievers@vrfy.org
2005-04-26[PATCH] check earlier if we should run as udevstartkay.sievers@vrfy.org
2005-04-26[PATCH] remove double initializationkay.sievers@vrfy.org
2005-04-26[PATCH] add -V option to udev to print the version numberkay.sievers@vrfy.org
On Sat, 2004-12-11 at 18:44 +0200, Martin Schlemmer [c] wrote: > > Any suggestions to determining the version of the installed udev? > This is now during startup, to see if we can make use of using > udevsend as hotplug agent. If the system was up, udevinfo could > be used, but that is in /usr/bin that might be on a seperate /usr. > I know we might move udevinfo to /bin, but that might be an issue > for some, and adding a -V switch to /sbin/udev might be a better > choice.
2005-04-26[PATCH] handle /etc/hotplug.d/ only if the event comes from udevdkay.sievers@vrfy.org
2005-04-26[PATCH] trivial cleanups and change some commentskay.sievers@vrfy.org
2005-04-26[PATCH] remove unused variableskay.sievers@vrfy.org
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().
2005-04-26[PATCH] use blacklist on device "remove" and remove dev.d/ call code duplicationkay.sievers@vrfy.org
2005-04-26[PATCH] don't call the hotplug scripts with a test runkay.sievers@vrfy.org
2005-04-26fixups to get back to proper patch orderGreg KH
Damm, it's hard to merge a multi-line tree into one flat line at times...
2005-04-26[PATCH] don't call dev.d/ scripts twice, if directory = subsystemkay.sievers@vrfy.org
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.
2005-04-26[PATCH] rename udev_lib to udev_utils and dev_d to udev_multiplexkay.sievers@vrfy.org
2005-04-26[PATCH] fix spurious valgrind warning in udev.greg@kroah.com
2005-04-26[PATCH] DEVNAME on device removalsjoerd@spring.luon.net
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.
2005-04-26[PATCH] handle whole hotplug event with udevd/udevkay.sievers@vrfy.org
If /proc/sys/kernel/hotplug points to /sbin/udevsend we handle the whole hotplug event with multiplexing /etc/hotplug.d/.
2005-04-26[PATCH] integrate wait_for_sysfs in udevkay.sievers@vrfy.org
Move the wait_for_sysfs logic into the udev binary. udev is called for every hotplug event. It also waits for /devices events.
2005-04-26[PATCH] export DEVNAME on remove eventkay.sievers@vrfy.org
Fix from Sjoerd Simons <sjoerd@spring.luon.net>, it got lost on the recent reorganization of the udev processing stages.
2005-04-26[PATCH] export udev_log flag to the environmentkay.sievers@vrfy.org
Forked scripts and callouts may want to follow udev's configured behavior and log only if udev is logging itself.
2005-04-26[PATCH] disable logging for udevstartkay.sievers@vrfy.org
The slow logging facilites on some systems are a reason for the reported slowness of udevstart. On one of my boxes udevstart is down from 9 second to 0.3 seconds.
2005-04-26[PATCH] rename udevdb* to udev_db*kay.sievers@vrfy.org
2005-04-26[PATCH] Make dev.d/ handling a separate processing stagekay.sievers@vrfy.org
Move the logic when and how to call the dev.d/ scripts into the main processing path.
2005-04-26[PATCH] make the udev object available to more processing stageskay.sievers@vrfy.org
Remove the overwriting of main_argv[] hack and use the values from the udev object. Pass the udev object to call_foreach_file(). In the udevstart case, export SUBSYSTEM and UDEVSTART to the environment.
2005-04-26[PATCH] add ACTION to udev object to expose it to the whole processkay.sievers@vrfy.org
2005-04-26[PATCH] let udev act as udevstart if argv[1] == "udevstart"kay.sievers@vrfy.org
"udev udevstart" will run udev as udevstart. This makes it easier to run a test in the source tree without the need to create a symlink.
generated by cgit v1.2.3-54-g00ecf (git 2.45.2) at 2024-11-24 13:25:24 +0000