devd.conf revision 207020
1# $FreeBSD: head/etc/devd.conf 207020 2010-04-21 21:51:14Z thompsa $ 2# 3# Refer to devd.conf(5) and devd(8) man pages for the details on how to 4# run and configure devd. 5# 6 7# NB: All regular expressions have an implicit ^$ around them. 8# NB: device-name is shorthand for 'match device-name' 9 10options { 11 # Each directory directive adds a directory the list of directories 12 # that we scan for files. Files are read-in in the order that they 13 # are returned from readdir(3). The rule-sets are combined to 14 # create a DFA that's used to match events to actions. 15 directory "/etc/devd"; 16 directory "/usr/local/etc/devd"; 17 pid-file "/var/run/devd.pid"; 18 19 # Setup some shorthand for regex that we use later in the file. 20 #XXX Yes, these are gross -- imp 21 set scsi-controller-regex 22 "(aac|adv|adw|aha|ahb|ahc|ahd|aic|amd|amr|asr|bt|ciss|ct|dpt|\ 23 esp|ida|iir|ips|isp|mlx|mly|mpt|ncr|ncv|nsp|stg|sym|trm|wds)\ 24 [0-9]+"; 25}; 26 27# Note that the attach/detach with the highest value wins, so that one can 28# override these general rules. 29 30# 31# Configure the interface on attach. Due to a historical accident, this 32# script is called pccard_ether. 33# 34# NB: DETACH events are ignored; the kernel should handle all cleanup 35# (routes, arp cache) if you need to do something beware of races 36# against immediate create of a device w/ the same name; e.g. 37# ifconfig bridge0 destroy; ifconfig bridge0 create 38# 39notify 0 { 40 match "system" "IFNET"; 41 match "type" "ATTACH"; 42 action "/etc/pccard_ether $subsystem start"; 43}; 44 45# 46# Try to start dhclient on Ethernet like interfaces when the link comes 47# up. Only devices that are configured to support DHCP will actually 48# run it. No link down rule exists because dhclient automaticly exits 49# when the link goes down. 50# 51notify 0 { 52 match "system" "IFNET"; 53 match "type" "LINK_UP"; 54 media-type "ethernet"; 55 action "/etc/rc.d/dhclient quietstart $subsystem"; 56}; 57 58# 59# Like Ethernet devices, but separate because 60# they have a different media type. We may want 61# to exploit this later. 62# 63detach 0 { 64 media-type "802.11"; 65 action "/etc/pccard_ether $device-name stop"; 66}; 67attach 0 { 68 media-type "802.11"; 69 action "/etc/pccard_ether $device-name start"; 70}; 71notify 0 { 72 match "system" "IFNET"; 73 match "type" "LINK_UP"; 74 media-type "802.11"; 75 action "/etc/rc.d/dhclient quietstart $subsystem"; 76}; 77 78# An entry like this might be in a different file, but is included here 79# as an example of how to override things. Normally 'ed50' would match 80# the above attach/detach stuff, but the value of 100 makes it 81# hard wired to 1.2.3.4. 82attach 100 { 83 device-name "ed50"; 84 action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000"; 85}; 86detach 100 { 87 device-name "ed50"; 88}; 89 90# When a USB Bluetooth dongle appears activate it 91attach 100 { 92 device-name "ubt[0-9]+"; 93 action "/etc/rc.d/bluetooth quietstart $device-name"; 94}; 95detach 100 { 96 device-name "ubt[0-9]+"; 97 action "/etc/rc.d/bluetooth quietstop $device-name"; 98}; 99 100# When a USB keyboard arrives, attach it as the console keyboard. 101attach 100 { 102 device-name "ukbd0"; 103 action "/etc/rc.d/syscons setkeyboard /dev/ukbd0"; 104}; 105detach 100 { 106 device-name "ukbd0"; 107 action "/etc/rc.d/syscons setkeyboard /dev/kbd0"; 108}; 109 110attach 100 { 111 device-name "ums[0-9]+"; 112 action "/etc/rc.d/moused quietstart $device-name"; 113}; 114 115detach 100 { 116 device-name "ums[0-9]+"; 117 action "/etc/rc.d/moused stop $device-name"; 118}; 119 120# Firmware download into the ActiveWire board. After the firmware download is 121# done the device detaches and reappears as something new and shiny 122# automatically. 123attach 100 { 124 match "vendor" "0x0854"; 125 match "product" "0x0100"; 126 match "release" "0x0000"; 127 action "/usr/local/bin/ezdownload -f /usr/local/share/usb/firmware/0854.0100.0_01.hex $device-name"; 128}; 129 130# Firmware download for Entrega Serial DB25 adapter. 131attach 100 { 132 match "vendor" "0x1645"; 133 match "product" "0x8001"; 134 match "release" "0x0101"; 135 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"; 136}; 137 138# This entry starts the ColdSync tool in daemon mode. Make sure you have an up 139# to date /usr/local/etc/palms. We override the 'listen' settings for port and 140# type in /usr/local/etc/coldsync.conf. 141notify 100 { 142 match "system" "USB"; 143 match "subsystem" "DEVICE"; 144 match "type" "ATTACH"; 145 match "vendor" "0x082d"; 146 match "product" "0x0100"; 147 match "release" "0x0100"; 148 action "/usr/local/bin/coldsync -md -p /dev/$cdev -t usb"; 149}; 150 151# 152# Rescan scsi device-names on attach, but not detach. However, it is 153# disabled by default due to reports of problems. 154# 155attach 0 { 156 device-name "$scsi-controller-regex"; 157// action "camcontrol rescan all"; 158}; 159 160# Don't even try to second guess what to do about drivers that don't 161# match here. Instead, pass it off to syslog. Commented out for the 162# moment, as the pnpinfo variable isn't set in devd yet. Individual 163# variables within the bus supplied pnpinfo are set. 164nomatch 0 { 165# action "logger Unknown device: $pnpinfo $location $bus"; 166}; 167 168# Various logging of unknown devices. 169nomatch 10 { 170 match "bus" "uhub[0-9]+"; 171 action "logger Unknown USB device: vendor $vendor product $product \ 172 bus $bus"; 173}; 174 175# Some PC-CARDs don't offer numerical manufacturer/product IDs, just 176# show the CIS info there. 177nomatch 20 { 178 match "bus" "pccard[0-9]+"; 179 match "manufacturer" "0xffffffff"; 180 match "product" "0xffffffff"; 181 action "logger Unknown PCCARD device: CISproduct $cisproduct \ 182 CIS-vendor $cisvendor bus $bus"; 183}; 184 185nomatch 10 { 186 match "bus" "pccard[0-9]+"; 187 action "logger Unknown PCCARD device: manufacturer $manufacturer \ 188 product $product CISproduct $cisproduct CIS-vendor \ 189 $cisvendor bus $bus"; 190}; 191 192nomatch 10 { 193 match "bus" "cardbus[0-9]+"; 194 action "logger Unknown Cardbus device: device $device class $class \ 195 vendor $vendor bus $bus"; 196}; 197 198# Switch power profiles when the AC line state changes. 199notify 10 { 200 match "system" "ACPI"; 201 match "subsystem" "ACAD"; 202 action "/etc/rc.d/power_profile $notify"; 203}; 204 205# Notify all users before beginning emergency shutdown when we get 206# a _CRT or _HOT thermal event and we're going to power down the system 207# very soon. 208notify 10 { 209 match "system" "ACPI"; 210 match "subsystem" "Thermal"; 211 match "notify" "0xcc"; 212 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'"; 213}; 214 215# Sample ZFS problem reports handling. 216notify 10 { 217 match "system" "ZFS"; 218 match "type" "zpool"; 219 action "logger -p kern.err 'ZFS: failed to load zpool $pool'"; 220}; 221 222notify 10 { 223 match "system" "ZFS"; 224 match "type" "vdev"; 225 action "logger -p kern.err 'ZFS: vdev failure, zpool=$pool type=$type'"; 226}; 227 228notify 10 { 229 match "system" "ZFS"; 230 match "type" "data"; 231 action "logger -p kern.warn 'ZFS: zpool I/O failure, zpool=$pool error=$zio_err'"; 232}; 233 234notify 10 { 235 match "system" "ZFS"; 236 match "type" "io"; 237 action "logger -p kern.warn 'ZFS: vdev I/O failure, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size error=$zio_err'"; 238}; 239 240notify 10 { 241 match "system" "ZFS"; 242 match "type" "checksum"; 243 action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'"; 244}; 245 246# User requested suspend, so perform preparation steps and then execute 247# the actual suspend process. 248notify 10 { 249 match "system" "ACPI"; 250 match "subsystem" "Suspend"; 251 action "/etc/rc.suspend acpi $notify"; 252}; 253notify 10 { 254 match "system" "ACPI"; 255 match "subsystem" "Resume"; 256 action "/etc/rc.resume acpi $notify"; 257}; 258 259/* EXAMPLES TO END OF FILE 260 261# The following might be an example of something that a vendor might 262# install if you were to add their device. This might reside in 263# /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical 264# example, a pccard ethernet-like device. Students of history may 265# know other devices by this name, and will get the in-jokes in this 266# entry. 267nomatch 10 { 268 match "bus" "pccard[0-9]+"; 269 match "manufacturer" "0x1234"; 270 match "product" "0x2323"; 271 action "kldload if_deqna"; 272}; 273attach 10 { 274 device-name "deqna[0-9]+"; 275 action "/etc/pccard_ether $device-name start"; 276}; 277detach 10 { 278 device-name "deqna[0-9]+"; 279 action "/etc/pccard_ether $device-name stop"; 280}; 281 282# Examples of notify hooks. A notify is a generic way for a kernel 283# subsystem to send event notification to userland. 284# 285# Here are some examples of ACPI notify handlers. ACPI subsystems that 286# generate notifies include the AC adapter, power/sleep buttons, 287# control method batteries, lid switch, and thermal zones. 288# 289# Information returned is not always the same as the ACPI notify 290# events. See the ACPI specification for more information about 291# notifies. Here is the information returned for each subsystem: 292# 293# ACAD: AC line state (0 is offline, 1 is online) 294# Button: Button pressed (0 for power, 1 for sleep) 295# CMBAT: ACPI battery events 296# Lid: Lid state (0 is closed, 1 is open) 297# Suspend, Resume: Suspend and resume notification 298# Thermal: ACPI thermal zone events 299# 300# This example calls a script when the AC state changes, passing the 301# notify value as the first argument. If the state is 0x00, it might 302# call some sysctls to implement economy mode. If 0x01, it might set 303# the mode to performance. 304notify 10 { 305 match "system" "ACPI"; 306 match "subsystem" "ACAD"; 307 action "/etc/acpi_ac $notify"; 308}; 309*/ 310