04-05-2006
udev core 5
installed fedora core 5 on a pc with USB and some usual things. in boot up it is stopped at "Starting udev:". Its harddisk light is busy. is it reconfiguring the kernel?. what do to solve this problem?.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Can anybody tell What is the exact difference between a Dual-core processor and a Core-to-duo processor ?Advance thanks to all my friends. (1 Reply)
Discussion started by: Ajith kumar.G
1 Replies
2. Shell Programming and Scripting
Hello!
I'm sorry if this is the false Forum, didn't really knew where to put it...
My question:
I have serveral USB-Sticks and wrote several Udev-Rules for theme, each Sticks needs to do something else, but all are using the same script (they have common tasks to do) and only some parts are... (2 Replies)
Discussion started by: al0x
2 Replies
3. UNIX for Advanced & Expert Users
I have been trying to get USB storage devices to auto-mount themselves under "/media/usb/<dev>" but have been running into some problems with udev (on FC7, btw... running udevd v.106)
Every time I put in a FAT (not 32) USB stick, udev identifies it as "USB storage", identifies the partition and... (3 Replies)
Discussion started by: jjinno
3 Replies
4. Linux
Hi everybody!
I installed Fedora 14 from dvd iso file (3.3 GB). But after that, when i enter command init 3 or init 5 an error occurs: "retrigger failed udev events". Who has experienced pls give me some suggestions. Tks so much!
Ok now I can use graphic mode. The first time, I use 256MB for... (0 Replies)
Discussion started by: nguyendu0102
0 Replies
5. Red Hat
On a test server running CentOS 6, I try to permanently set the owner, group and mode of disk devices for use with a DB2 database. For this I created an udev rule file /etc/udev/rules.d/99-db2.rules:
KERNEL=="sdb*", OWNER="db2usrl1", GROUP="db2adml1", MODE="0600"
After a reboot, the owner and... (4 Replies)
Discussion started by: hergp
4 Replies
6. Shell Programming and Scripting
Hi All,
I need a simple udev rules in my server Centos 5.4. This rules needs to get trigger my script whenever the cdrom is attached to the server.
Could you please provide your suggestion on it.
Thanks,
Kalai (0 Replies)
Discussion started by: kalpeer
0 Replies
7. UNIX for Dummies Questions & Answers
Hello All,
I found this site here: AndDiSa Android Blog: Nexus 7 MTP automount on OpenSuse 11.4
That sites explains how to mount an Android device that can only connect to a computer using MTP or PTP instead of what it used
to get treated as, which was a Mass Storage Device.
In my Rules... (0 Replies)
Discussion started by: mrm5102
0 Replies
8. Shell Programming and Scripting
Hi Guys,
Can someone take a look at my scripts what missing, plugin usb drive the script is running can log all my echo but cannot execute command. Is there any configuration in linux or to my scripts need to add?.
What i want to achieve is every time I plugin the usbdisk automatic mount to... (21 Replies)
Discussion started by: lxdorney
21 Replies
LEARN ABOUT CENTOS
device_rename
DEVICE_RENAME(9) Device drivers infrastructure DEVICE_RENAME(9)
NAME
device_rename - renames a device
SYNOPSIS
int device_rename(struct device * dev, const char * new_name);
ARGUMENTS
dev
the pointer to the struct device to be renamed
new_name
the new name of the device
DESCRIPTION
It is the responsibility of the caller to provide mutual exclusion between two different calls of device_rename on the same device to
ensure that new_name is valid and won't conflict with other devices.
NOTE
Don't call this function. Currently, the networking layer calls this function, but that will change. The following text from Kay Sievers
offers
SOME INSIGHT
Renaming devices is racy at many levels, symlinks and other stuff are not replaced atomically, and you get a "move" uevent, but it's not
easy to connect the event to the old and new device. Device nodes are not renamed at all, there isn't even support for that in the kernel
now.
In the meantime, during renaming, your target name might be taken by another driver, creating conflicts. Or the old name is taken directly
after you renamed it -- then you get events for the same DEVPATH, before you even see the "move" event. It's just a mess, and nothing new
should ever rely on kernel device renaming. Besides that, it's not even implemented now for other things than (driver-core wise very
simple) network devices.
We are currently about to change network renaming in udev to completely disallow renaming of devices in the same namespace as the kernel
uses, because we can't solve the problems properly, that arise with swapping names of multiple interfaces without races. Means, renaming of
eth[0-9]* will only be allowed to some other name than eth[0-9]*, for the aforementioned reasons.
Make up a "real" name in the driver before you register anything, or add some other attributes for userspace to find the device, or use
udev to add symlinks -- but never rename kernel devices later, it's a complete mess. We don't even want to get into that and try to
implement the missing pieces in the core. We really have other pieces to fix in the driver core mess. :)
COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 DEVICE_RENAME(9)