mirror of
https://github.com/morgan9e/systemd
synced 2026-04-14 00:14:32 +09:00
ae2859df40
On Tuesday 18 November 2003 02:14, Greg KH wrote: > On Mon, Nov 17, 2003 at 06:33:32PM +0100, Arnd Bergmann wrote: > > That would at least be part of the solution I'm looking for. How about > > extra format characters for bus_id and for the result of a callout > > program? > > Sure, I can see the use for that. Want to send a patch? :) > Take a look at the current bk tree (which has moved to > bk://linuxusb.bkbits.net/udev/ ) I've made finding that device a lot > easier now, and it works for all rule types. Great, just what I was missing. I didn't see the any link to the bk repository. Here's the patch for the bus_id. I'll need to think about the handling of callout results a bit more.
udev - a userspace implementation of devfs For more information on the design, and structure of this project, see the files in the docs/ directory. To use: - You must be running a 2.6 version of the Linux kernel. - Make sure sysfs is mounted. udev will figure out where sysfs is mounted, but the traditional place for it is at /sys. You can mount it by hand by running: mount -t sysfs none /sys - Make sure you have the latest version of the linux-hotplug scripts. They are available at linux-hotplug.sf.net or from your local kernel.org mirror at: kernel.org/pub/linux/utils/kernel/hotplug/ They are required in order for udev to work properly. If for some reason you do not install the hotplug scripts, you must tell the kernel to point the hotplug binary at wherever you install udev at. This can be done by: echo "/sbin/udev" > /proc/sys/kernel/hotplug - Build the project: make - Install the project: make install This will put the udev binary in /sbin, create the /udev and /etc/udev directories, and place the udev configuration files in /etc/udev. You will probably want to edit the namedev.* files to create custom naming rules. More info on how the config files are set up are contained in comments in the files, and is located in the documentation. - Add and remove devices from the system and marvel as nodes are created and removed in /udev/ based on the device types. - If you later get sick of it, uninstall it: make uninstall Things are still quite rough, and it's a bit beyond proof of concept code. Help is very much appreciated, see the TODO file for a list of things left to be done. If you want to build using klibc, use the Makefile.klibc file: - read the klibc/klibc/README file for how to set up the linux symlink properly. - make clean - make -f Makefile.klibc and marvel at the tiny binary you just created :) Any comment/questions/concerns please let me know. greg k-h greg@kroah.com