02-24-2014
Great, now what's the relationship between plug n play and the udev daemon? Is it udev's job to query the device, get the ID number and determine what hardware is plugged in, thus adding or removing the needed modules?
9 More Discussions You Might Find Interesting
1. SuSE
I'm using SuSE 9.2 Pro and trying to use a program call BestCrypt. I get it installed and type bctool and it says "Kernel modules not loaded". If you need to know anymore about it you can find it at http://www.jetico.com/linux/bcrypt-help/index.htm
linux:/home/chris/Desktop/Xtheater-0.9.2 #... (6 Replies)
Discussion started by: CTroxtell21
6 Replies
2. HP-UX
Hi all,
what do kernel modules libaudit, klog and strlog do?
Specifically I want to determine if it was possible for us to determine if kernel level auditing is enabled at all?
regards (0 Replies)
Discussion started by: slash_blog
0 Replies
3. Programming
Hi,all:
I run my program which consists of one kernel module and one user mode process on a dual core server. The problem here is the kernel module consumes 100% of one core while the user mode process only consumes 10% of the other core, is there any solution that I can assign some computing... (1 Reply)
Discussion started by: neyshule
1 Replies
4. UNIX for Advanced & Expert Users
I installed in VM the Mandriva Linux with 2.6.27 kernel.
But presently when I fire make the modules .ko does not get built.
I get the following output on firing command in the kernel module folder.
$ make
Building first_driver.c ... make: Entering directory... (1 Reply)
Discussion started by: rupeshkp728
1 Replies
5. Programming
I am aware of debugging linux applications using gdb and ddd.
Now I have written a simple kernel module having init_module, exit _module and some functions for tasklets and workqueues.
I want to debug these kernel modules like I used to debug applications setting breakpoints etc.
How can I debug... (1 Reply)
Discussion started by: rupeshkp728
1 Replies
6. Emergency UNIX and Linux Support
Hi,
I need to set qlogic qla2xxx parameters in /etc/modprobe.conf
(Oracle Linux Server release 5.7, almost equal to RedHat 5.7)
two questions:
how can I pass this parameters to the module while it is loaded (fibre channel luns are in use), if possible at all
and how can I check the... (3 Replies)
Discussion started by: funksen
3 Replies
7. UNIX for Dummies Questions & Answers
This query is regarding the makefiles of linux kernel modules.
I saw at some sites on net it is suggesting to include the following path:
KERNEL_SOURCE := /usr/src/linux...
while at some places it is askibg to include /lib/modules path:
KERNEL_SOURCE := /lib/modules/2.6.27-7-generic/build... (0 Replies)
Discussion started by: rupeshkp728
0 Replies
8. Linux
Hi,
I am running CentOS 6.5 and I want to remove auto loading 8021q and garp modules, but there are no configure files in /etc/modprobe.d define bot modules.
I even added both module names to /etc/modprobe.d/blacklist.conf, both of them are still loaded after the reboot. How can I disable... (2 Replies)
Discussion started by: hce
2 Replies
9. UNIX for Beginners Questions & Answers
I'm a little embarrassed after all these years I've never really successfully compiled my own kernel. I used this guide to make the following files:
linux-headers-5.1.9_5.1.9-1_amd64.deb
linux-image-5.1.9_5.1.9-1_amd64.deb
linux-libc-dev_5.1.9-1_amd64.deb
When I first booted into this... (4 Replies)
Discussion started by: Azrael
4 Replies
LEARN ABOUT CENTOS
systemd.device
SYSTEMD.DEVICE(5) systemd.device SYSTEMD.DEVICE(5)
NAME
systemd.device - Device unit configuration
SYNOPSIS
device.device
DESCRIPTION
A unit configuration file whose name ends in ".device" encodes information about a device unit as exposed in the sysfs/udev(7) device tree.
This unit type has no specific options. See systemd.unit(5) for the common options of all unit configuration files. The common
configuration items are configured in the generic "[Unit]" and "[Install]" sections. A separate "[Device]" section does not exist, since no
device-specific options may be configured.
systemd will dynamically create device units for all kernel devices that are marked with the "systemd" udev tag (by default all block and
network devices, and a few others). This may be used to define dependencies between devices and other units. To tag a udev device, use
"TAG+="systemd"" in the udev rules file, see udev(7) for details.
Device units are named after the /sys and /dev paths they control. Example: the device /dev/sda5 is exposed in systemd as dev-sda5.device.
For details about the escaping logic used to convert a file system path to a unit name see systemd.unit(5).
THE UDEV DATABASE
The settings of device units may either be configured via unit files, or directly from the udev database (which is recommended). The
following udev device properties are understood by systemd:
SYSTEMD_WANTS=
Adds dependencies of type Wants from the device unit to all listed units. This may be used to activate arbitrary units when a specific
device becomes available. Note that this and the other tags are not taken into account unless the device is tagged with the "systemd"
string in the udev database, because otherwise the device is not exposed as systemd unit (see above). Note that systemd will only act
on Wants dependencies when a device first becomes active, it will not act on them if they are added to devices that are already active.
Use SYSTEMD_READY= (see below) to influence on which udev event to trigger the device dependencies.
SYSTEMD_ALIAS=
Adds an additional alias name to the device unit. This must be an absolute path that is automatically transformed into a unit name.
(See above.)
SYSTEMD_READY=
If set to 0, systemd will consider this device unplugged even if it shows up in the udev tree. If this property is unset or set to 1,
the device will be considered plugged the moment it shows up in the udev tree. This property has no influence on the behavior when a
device disappears from the udev tree. This option is useful to support devices that initially show up in an uninitialized state in the
tree, and for which a "changed" event is generated the moment they are fully set up. Note that SYSTEMD_WANTS= (see above) is not acted
on as long as SYSTEMD_READY=0 is set for a device.
ID_MODEL_FROM_DATABASE=, ID_MODEL=
If set, this property is used as description string for the device unit.
SEE ALSO
systemd(1), systemctl(8), systemd.unit(5), udev(7), systemd.directives(7)
systemd 208 SYSTEMD.DEVICE(5)