udev core 5


 
Thread Tools Search this Thread
Operating Systems Linux udev core 5
# 1  
Old 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?.
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Fdisk and grep command not working in udev trigger

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

2. UNIX for Dummies Questions & Answers

Question about udev Rules File?

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

3. Shell Programming and Scripting

udev rules for mounting CDROM

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

4. Red Hat

set device mode permanently with udev rule

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

5. Linux

Error: Retrigger failed udev events in Fedora 14!

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

6. UNIX for Advanced & Expert Users

Problems with udev & mounting fat32 usb storage

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

7. Shell Programming and Scripting

Pass params with Udev

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

8. UNIX for Dummies Questions & Answers

difference between Dual-core & Core-to-duo

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
Login or Register to Ask a Question
CRDA(8) 							       Linux								   CRDA(8)

NAME
crda - send to the kernel a wireless regulatory domain for a given ISO / IEC 3166 alpha2 SYNOPSIS
crda Description crda is the Linux wireless central regulatory domain agent. crda is intended to be used by udev scripts and should not be run manually unless debugging udev scripts. crda is triggered to run by the kernel by sending a udev event upon a new regulatory domain change. Regula- tory domain changes are triggered by the wireless kernel subsystem (upon initialization and on reception of country IEs), wireless drivers, or userspace (see iw ). Upon a regulatory domain change the kernel sends a udev change event for the regulatory platform. The kernel ignores regulatory domains sent to it if it does not expect them. The regulatory domain is read by crda from the regulatory.bin file. RSA Digital Signature If built with openssl or gcrypt support crda will have embedded into it an RSA digital signature which will prevent it from reading cor- rupted or non-authored regulatory.bin files. Authorship is respected by the RSA public key packed into crda. This specific crda package has been built with an RSA public key from John Linville (the Linux wireless kernel maintainer) and as such will only read regulatory.bin files signed by him. For further information see the regulatory.bin man page. UDEV RULE
A udev regulatory rule must be put in place in order to receive and parse udev events from the kernel in order to get udev to call crda with the passed ISO / IEC 3166 alpha2 country code. An example udev rule which can be used (usually in /lib/udev/rules.d/85-regula- tory.rules ): KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/crda" Environment variable Set the COUNTRY environment variable with a specific ISO / IEC 3166 alpha2 country code and then run crda without arguments. This will send a regulatory domain for that alpha2 to the kernel. SEE ALSO
iw(8) regulatory.bin(5) http://wireless.kernel.org/en/developers/Regulatory/ crda 23 January 2009 CRDA(8)