udev rules for mounting CDROM


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting udev rules for mounting CDROM
# 1  
Old 05-21-2012
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
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. 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

2. Ubuntu

FAQ adding rules in udev for my usb 8G to autorun rsync

Hi, I would like to ask if someone knows and show/point me or simple help me how udev rules work in lucyd, upon my quest and search all the tuts i used is based on old udev since something i read the udev change in lucyd version.. I want to accomplised when i plug my usb 8Gb device and automount... (0 Replies)
Discussion started by: jao_madn
0 Replies

3. 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

4. Solaris

I/O error when mounting cdrom in Solaris 10

hi unix friends, has anyone faced this problem before ? i inserted my cd into my X1450 machine, it says I/O error. mount -F hsfs -o ro /dev/dsk/clt0d0s0 /cdrom mount: I/O error mount: cannot mount /dev/dsk/c1t0d0s0 what should i do ? (4 Replies)
Discussion started by: Exposure
4 Replies

5. Solaris

cdrom mounting

Hi, I want to know HOw can I know on which slice cdrom is mounted?by default on which slice generally it is mounting? (1 Reply)
Discussion started by: manoj.solaris
1 Replies

6. Linux

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?. (0 Replies)
Discussion started by: GJ2
0 Replies

7. UNIX for Dummies Questions & Answers

Mounting cdrom on DG/UX

Hi, I'm looking to mount a cd on an old AViiON system we have. No one here really has any expertise with this platform so any help will be appreciated. I * think* the device is sd(apsc(pci(1),B,0,7),5,0), however I'm not sure at all. Thanks! (0 Replies)
Discussion started by: madesjardins
0 Replies

8. UNIX for Dummies Questions & Answers

mounting cdrom

Hey everyone, Quick question...I am trying to get packages off a cdrom for NETBSD. I tried mounting using this command mount /dev/rccd0a /etc/home/cdrom. But I just get an error. I did a dmesg |grep ^cd and it said that my cdrom was at cd0.? Am I doing something wrong.? Any help would... (2 Replies)
Discussion started by: vaff4k
2 Replies

9. UNIX for Dummies Questions & Answers

stop cdrom from auto-mounting

Somebody loaded RH 7.3 for me on my PC & now I'm running through & configuring all my settings. Question: Every time I insert a CD into the cdrom, it automatically mounts the cdrom if there's anything on the CD. How do I disable this? I don't want it to automount. Thanks in advance!! (2 Replies)
Discussion started by: jalburger
2 Replies

10. Solaris

mounting cdrom on Solaris 9

Here's some cmd output: bash-2.05# ls /dev/dsk/* /dev/dsk/c0t0d0s0 /dev/dsk/c0t0d0s4 /dev/dsk/c0t1d0s0 /dev/dsk/c0t1d0s4 /dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s5 /dev/dsk/c0t1d0s1 /dev/dsk/c0t1d0s5 /dev/dsk/c0t0d0s2 /dev/dsk/c0t0d0s6 /dev/dsk/c0t1d0s2 /dev/dsk/c0t1d0s6 /dev/dsk/c0t0d0s3 ... (4 Replies)
Discussion started by: AJA
4 Replies
Login or Register to Ask a Question
UDEVADM(8)							      udevadm								UDEVADM(8)

NAME
udevadm - udev management tool SYNOPSIS
udevadm [--debug] [--version] [--help] udevadm info options udevadm trigger [options] udevadm settle [options] udevadm control command udevadm monitor [options] udevadm test [options] devpath DESCRIPTION
udevadm expects a command and command specific options. It controls the runtime behavior of udev, requests kernel events, manages the event queue, and provides simple debugging mechanisms. OPTIONS
--debug Print debug messages to stderr. --version Print version number. --help Print help text. udevadm info options Queries the udev database for device information stored in the udev database. It can also query the properties of a device from its sysfs representation to help creating udev rules that match this device. --query=type Query the database for specified type of device data. It needs the --path or --name to identify the specified device. Valid queries are: name, symlink, path, property, all. --path=devpath The devpath of the device to query. --name=file The name of the device node or a symlink to query --root The udev root directory: /dev. If used in conjunction with a name or symlink query, the query returns the absolute path including the root directory. --attribute-walk Print all sysfs properties of the specified device that can be used in udev rules to match the specified device. It prints all devices along the chain, up to the root of sysfs that can be used in udev rules. --device-id-of-file=file Print major/minor numbers of the underlying device, where the file lives on. --export-db Export the content of the udev database. --version Print version. --help Print help text. udevadm trigger [options] Request device events from the kernel. Primarily used to replay events at system coldplug time. --verbose Print the list of devices which will be triggered. --dry-run Do not actually trigger the event. --type=type Trigger a specific type of devices. Valid types are: devices, subsystems, failed. The default value is devices. --action=action Type of event to be triggered. The default value is change. --subsystem-match=subsystem Trigger events for devices which belong to a matching subsystem. This option can be specified multiple times and supports shell style pattern matching. --subsystem-nomatch=subsystem Do not trigger events for devices which belong to a matching subsystem. This option can be specified multiple times and supports shell style pattern matching. --attr-match=attribute=value Trigger events for devices with a matching sysfs attribute. If a value is specified along with the attribute name, the content of the attribute is matched against the given value using shell style pattern matching. If no value is specified, the existence of the sysfs attribute is checked. This option can be specified multiple times. --attr-nomatch=attribute=value Do not trigger events for devices with a matching sysfs attribute. If a value is specified along with the attribute name, the content of the attribute is matched against the given value using shell style pattern matching. If no value is specified, the existence of the sysfs attribute is checked. This option can be specified multiple times. --property-match=property=value Trigger events for devices with a matching property value. This option can be specified multiple times and supports shell style pattern matching. --tag-match=property Trigger events for devices with a matching tag. This option can be specified multiple times. --sysname-match=name Trigger events for devices with a matching sys device name. This option can be specified multiple times and supports shell style pattern matching. udevadm settle [options] Watches the udev event queue, and exits if all current events are handled. --timeout=seconds Maximum number of seconds to wait for the event queue to become empty. The default value is 180 seconds. A value of 0 will check if the queue is empty and always return immediately. --seq-start=seqnum Wait only for events after the given sequence number. --seq-end=seqnum Wait only for events before the given sequence number. --exit-if-exists=file Stop waiting if file exists. --quiet Do not print any output, like the remaining queue entries when reaching the timeout. --help Print help text. udevadm control command Modify the internal state of the running udev daemon. --log-priority=value Set the internal log level of udevd. Valid values are the numerical syslog priorities or their textual representations: err, info and debug. --stop-exec-queue Signal udevd to stop executing new events. Incoming events will be queued. --start-exec-queue Signal udevd to enable the execution of events. --reload-rules Signal udevd to reload the rules files. The udev daemon detects changes automatically, this option is usually not needed. Reloading rules does not apply any changes to already existing devices. --property=KEY=value Set a global property for all events. --children-max=value Set the maximum number of events, udevd will handle at the same time. --help Print help text. udevadm monitor [options] Listens to the kernel uevents and events sent out by a udev rule and prints the devpath of the event to the console. It can be used to analyze the event timing, by comparing the timestamps of the kernel uevent and the udev event. --kernel Print the kernel uevents. --udev Print the udev event after the rule processing. --property Also print the properties of the event. --subsystem-match=string[/string] Filter events by subsystem[/devtype]. Only udev events with a matching subsystem value will pass. --tag-match=string Filter events by property. Only udev events with a given tag attached will pass. --help Print help text. udevadm test [options] devpath Simulate a udev event run for the given device, and print debug output. --action=string The action string. --subsystem=string The subsystem string. --help Print help text. AUTHOR
Written by Kay Sievers kay.sievers@vrfy.org. SEE ALSO
udev(7) udevd(8) udev 06/02/2010 UDEVADM(8)