devd.conf revision 166754
1110566Smike# $FreeBSD: head/etc/devd.conf 166754 2007-02-15 16:38:10Z imp $ 2141379Sdas# 3110566Smike# Refer to devd.conf(5) and devd(8) man pages for the details on how to 4110566Smike# run and configure devd. 5110566Smike# 6110566Smike 7110566Smike# NB: All regular expressions have an implicit ^$ around them. 8110566Smike# NB: device-name is shorthand for 'match device-name' 9110566Smike 10110566Smikeoptions { 11110566Smike # Each directory directive adds a directory the list of directories 12110566Smike # that we scan for files. Files are read-in in the order that they 13110566Smike # are returned from readdir(3). The rule-sets are combined to 14110566Smike # create a DFA that's used to match events to actions. 15110566Smike directory "/etc/devd"; 16110566Smike directory "/usr/local/etc/devd"; 17110566Smike pid-file "/var/run/devd.pid"; 18110566Smike 19110566Smike # Setup some shorthand for regex that we use later in the file. 20110566Smike #XXX Yes, these are gross -- imp 21110566Smike set scsi-controller-regex 22110566Smike "(aac|adv|adw|aha|ahb|ahc|ahd|aic|amd|amr|asr|bt|ciss|ct|dpt|\ 23110566Smike esp|ida|iir|ips|isp|mlx|mly|mpt|ncr|ncv|nsp|stg|sym|trm|wds)\ 24110566Smike [0-9]+"; 25110566Smike}; 26110566Smike 27110566Smike# Note that the attach/detach with the highest value wins, so that one can 28110566Smike# override these general rules. 29110566Smike 30110566Smike# 31110566Smike# Configure the interface on attach. Due to a historical accident, this 32110566Smike# script is called pccard_ether. 33110566Smike# 34110566Smikenotify 0 { 35110566Smike match "system" "IFNET"; 36114817Speter match "type" "ATTACH"; 37114817Speter action "/etc/pccard_ether $subsystem start"; 38110566Smike}; 39175402Sbde 40175402Sbdenotify 0 { 41175402Sbde match "system" "IFNET"; 42175402Sbde match "type" "DETACH"; 43175402Sbde action "/etc/pccard_ether $subsystem stop"; 44110566Smike}; 45110566Smike 46143214Sdas# 47143214Sdas# Try to start dhclient on Ethernet like interfaces when the link comes 48113145Sdas# up. Only devices that are configured to support DHCP will actually 49124653Sdas# run it. No link down rule exists because dhclient automaticly exits 50124653Sdas# when the link goes down. 51124653Sdas# 52113145Sdasnotify 0 { 53113145Sdas match "system" "IFNET"; 54113145Sdas match "type" "LINK_UP"; 55175402Sbde media-type "ethernet"; 56 action "/etc/rc.d/dhclient start $subsystem"; 57}; 58 59# 60# Like Ethernet devices, but separate because 61# they have a different media type. We may want 62# to exploit this later. 63# 64detach 0 { 65 media-type "802.11"; 66 action "/etc/pccard_ether $device-name stop"; 67}; 68attach 0 { 69 media-type "802.11"; 70 action "/etc/pccard_ether $device-name start"; 71}; 72notify 0 { 73 match "system" "IFNET"; 74 match "type" "LINK_UP"; 75 media-type "802.11"; 76 action "/etc/rc.d/dhclient start $subsystem"; 77}; 78 79# An entry like this might be in a different file, but is included here 80# as an example of how to override things. Normally 'ed50' would match 81# the above attach/detach stuff, but the value of 100 makes it 82# hard wired to 1.2.3.4. 83attach 100 { 84 device-name "ed50"; 85 action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000"; 86}; 87detach 100 { 88 device-name "ed50"; 89}; 90 91# When a USB Bluetooth dongle appears activate it 92attach 100 { 93 device-name "ubt[0-9]+"; 94 action "/etc/rc.d/bluetooth start $device-name"; 95}; 96detach 100 { 97 device-name "ubt[0-9]+"; 98 action "/etc/rc.d/bluetooth stop $device-name"; 99}; 100 101# When a USB keyboard arrives, attach it as the console keyboard. 102attach 100 { 103 device-name "ukbd0"; 104 action "/etc/rc.d/syscons setkeyboard /dev/ukbd0"; 105}; 106detach 100 { 107 device-name "ukbd0"; 108 action "/etc/rc.d/syscons setkeyboard /dev/kbd0"; 109}; 110 111# The entry below starts moused when a mouse is plugged in. Moused 112# stops automatically (actually it bombs :) when the device disappears. 113attach 100 { 114 device-name "ums[0-9]+"; 115 action "/etc/rc.d/moused start $device-name"; 116}; 117 118# Firmware download into the ActiveWire board. After the firmware download is 119# done the device detaches and reappears as something new and shiny 120# automatically. 121attach 100 { 122 match "vendor" "0x0854"; 123 match "product" "0x0100"; 124 match "release" "0x0000"; 125 action "/usr/local/bin/ezdownload -f /usr/local/share/usb/firmware/0854.0100.0_01.hex $device-name"; 126}; 127 128# Firmware download for Entrega Serial DB25 adapter. 129attach 100 { 130 match "vendor" "0x1645"; 131 match "product" "0x8001"; 132 match "release" "0x0101"; 133 action "if ! kldstat -n usio > /dev/null 2>&1 ; then kldload usio; fi /usr/sbin/ezdownload -v -f /usr/share/usb/firmware/1645.8001.0101 /dev/$device-name"; 134}; 135 136# This entry starts the ColdSync tool in daemon mode. Make sure you have an up 137# to date /usr/local/etc/palms. We override the 'listen' settings for port and 138# type in /usr/local/etc/coldsync.conf. 139attach 100 { 140 device-name "ugen[0-9]+"; 141 match "vendor" "0x082d"; 142 match "product" "0x0100"; 143 match "release" "0x0100"; 144 action "/usr/local/bin/coldsync -md -p /dev/$device-name -t usb"; 145}; 146 147# 148# Rescan scsi device-names on attach, but not detach. However, it is 149# disabled by default due to reports of problems. 150# 151attach 0 { 152 device-name "$scsi-controller-regex"; 153// action "camcontrol rescan all"; 154}; 155 156# Don't even try to second guess what to do about drivers that don't 157# match here. Instead, pass it off to syslog. Commented out for the 158# moment, as the pnpinfo variable isn't set in devd yet. Individual 159# variables within the bus supplied pnpinfo are set. 160nomatch 0 { 161# action "logger Unknown device: $pnpinfo $location $bus"; 162}; 163 164# Various logging of unknown devices. 165nomatch 10 { 166 match "bus" "uhub[0-9]+"; 167 action "logger Unknown USB device: vendor $vendor product $product \ 168 bus $bus"; 169}; 170 171# Some PC-CARDs don't offer numerical manufacturer/product IDs, just 172# show the CIS info there. 173nomatch 20 { 174 match "bus" "pccard[0-9]+"; 175 match "manufacturer" "0xffffffff"; 176 match "product" "0xffffffff"; 177 action "logger Unknown PCCARD device: CISproduct $cisproduct \ 178 CIS-vendor $cisvendor bus $bus"; 179}; 180 181nomatch 10 { 182 match "bus" "pccard[0-9]+"; 183 action "logger Unknown PCCARD device: manufacturer $manufacturer \ 184 product $product CISproduct $cisproduct CIS-vendor \ 185 $cisvendor bus $bus"; 186}; 187 188nomatch 10 { 189 match "bus" "cardbus[0-9]+"; 190 action "logger Unknown Cardbus device: device $device class $class \ 191 vendor $vendor bus $bus"; 192}; 193 194# Switch power profiles when the AC line state changes. 195notify 10 { 196 match "system" "ACPI"; 197 match "subsystem" "ACAD"; 198 action "/etc/rc.d/power_profile $notify"; 199}; 200 201# Notify all users before beginning emergency shutdown when we get 202# a _CRT or _HOT thermal event and we're going to power down the system 203# very soon. 204notify 10 { 205 match "system" "ACPI"; 206 match "subsystem" "Thermal"; 207 match "notify" "0xcc"; 208 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'"; 209}; 210 211/* EXAMPLES TO END OF FILE 212 213# The following might be an example of something that a vendor might 214# install if you were to add their device. This might reside in 215# /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical 216# example, a pccard ethernet-like device. Students of history may 217# know other devices by this name, and will get the in-jokes in this 218# entry. 219nomatch 10 { 220 match "bus" "pccard[0-9]+"; 221 match "manufacturer" "0x1234"; 222 match "product" "0x2323"; 223 action "kldload if_deqna"; 224}; 225attach 10 { 226 device-name "deqna[0-9]+"; 227 action "/etc/pccard_ether $device-name start"; 228}; 229detach 10 { 230 device-name "deqna[0-9]+"; 231 action "/etc/pccard_ether $device-name stop"; 232}; 233 234# Examples of notify hooks. A notify is a generic way for a kernel 235# subsystem to send event notification to userland. 236# 237# Here are some examples of ACPI notify handlers. ACPI subsystems that 238# generate notifies include the AC adapter, power/sleep buttons, 239# control method batteries, lid switch, and thermal zones. 240# 241# Information returned is not always the same as the ACPI notify 242# events. See the ACPI specification for more information about 243# notifies. Here is the information returned for each subsystem: 244# 245# ACAD: AC line state (0 is offline, 1 is online) 246# Button: Button pressed (0 for power, 1 for sleep) 247# CMBAT: ACPI battery events 248# Lid: Lid state (0 is closed, 1 is open) 249# Thermal: ACPI thermal zone events 250# 251# This example calls a script when the AC state changes, passing the 252# notify value as the first argument. If the state is 0x00, it might 253# call some sysctls to implement economy mode. If 0x01, it might set 254# the mode to performance. 255notify 10 { 256 match "system" "ACPI"; 257 match "subsystem" "ACAD"; 258 action "/etc/acpi_ac $notify"; 259}; 260*/ 261