Changeset 0a3a152


Ignore:
Timestamp:
12/20/13 07:14:00 (14 months ago)
Author:
Kris Moore <kris@…>
Branches:
master, releng/10.0, releng/10.0.1, releng/10.0.2, releng/10.0.3, releng/10.1, releng/10.1.1
Children:
f18d2b4
Parents:
424c041
Message:

Update our devd.conf with latest from 10.0-RC2

File:
1 edited

Legend:

Unmodified
Added
Removed
  • src-sh/pc-extractoverlay/desktop-overlay/etc/devd.conf

    r1620346 r0a3a152  
    1 # $FreeBSD: releng/8.0/etc/devd.conf 192198 2009-05-16 15:12:56Z maxim $ 
     1# $FreeBSD$ 
    22# 
    33# Refer to devd.conf(5) and devd(8) man pages for the details on how to 
     
    99 
    1010options { 
    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. 
     11        # Each "directory" directive adds a directory to the list of 
     12        # directories that we scan for files.  Files are loaded in the order 
     13        # that they are returned from readdir(3).  The rule-sets are combined 
     14        # to create a DFA that's used to match events to actions. 
    1515        directory "/etc/devd"; 
    1616        directory "/usr/local/etc/devd"; 
     
    3333# 
    3434# 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 
     35#     (routes, arp cache).  Beware of races against immediate create 
     36#     of a device with the same name; e.g. 
     37#     ifconfig bridge0 destroy; ifconfig bridge0 create 
    3838# 
    3939notify 0 { 
    4040        match "system"          "IFNET"; 
     41        match "subsystem"       "!usbus[0-9]+"; 
    4142        match "type"            "ATTACH"; 
    4243        action "/etc/pccard_ether $subsystem start"; 
     
    4445 
    4546# 
    46 # Try to start dhclient on Ethernet like interfaces when the link comes 
     47# Try to start dhclient on Ethernet-like interfaces when the link comes 
    4748# up.  Only devices that are configured to support DHCP will actually 
    48 # run it.  No link down rule exists because dhclient automaticly exits 
     49# run it.  No link down rule exists because dhclient automatically exits 
    4950# when the link goes down. 
    5051# 
     
    8889}; 
    8990 
    90 # When a USB Bluetooth dongle appears activate it 
     91# When a USB Bluetooth dongle appears, activate it 
    9192attach 100 { 
    9293        device-name "ubt[0-9]+"; 
     
    9899}; 
    99100 
     101# Firmware downloader for Atheros AR3011 based USB Bluetooth devices 
     102#attach 100 { 
     103#       match "vendor" "0x0cf3"; 
     104#       match "product" "0x3000"; 
     105#       action "sleep 2 && /usr/sbin/ath3kfw -d $device-name -f /usr/local/etc/ath3k-1.fw"; 
     106#}; 
     107 
    100108# When a USB keyboard arrives, attach it as the console keyboard. 
    101109attach 100 { 
     
    108116}; 
    109117 
    110 attach 100 { 
    111         device-name "ums[0-9]+"; 
    112         action "/etc/rc.d/moused quietstart $device-name"; 
    113 }; 
    114  
    115 detach 100 {  
    116         device-name "ums[0-9]+";  
    117         action "/etc/rc.d/moused stop $device-name";  
    118 };  
     118notify 100 { 
     119        match "system" "DEVFS"; 
     120        match "subsystem" "CDEV"; 
     121        match "type" "CREATE"; 
     122        match "cdev" "ums[0-9]+"; 
     123 
     124        action "/etc/rc.d/moused quietstart $cdev"; 
     125}; 
     126 
     127notify 100 { 
     128        match "system" "DEVFS"; 
     129        match "subsystem" "CDEV"; 
     130        match "type" "DESTROY"; 
     131        match "cdev" "ums[0-9]+"; 
     132 
     133        action "/etc/rc.d/moused stop $cdev"; 
     134}; 
    119135 
    120136# Firmware download into the ActiveWire board. After the firmware download is 
    121 # done the device detaches and reappears as something new and shiny 
     137# done, the device detaches and reappears as something new and shiny 
    122138# automatically. 
    123139attach 100 { 
     
    139155# to date /usr/local/etc/palms. We override the 'listen' settings for port and 
    140156# type in /usr/local/etc/coldsync.conf. 
    141 attach 100 { 
    142         device-name "ugen[0-9]+"; 
    143         match "vendor" "0x082d"; 
    144         match "product" "0x0100"; 
    145         match "release" "0x0100"; 
    146         action "/usr/local/bin/coldsync -md -p /dev/$device-name -t usb"; 
    147 }; 
    148  
    149 # 
    150 # Rescan scsi device-names on attach, but not detach.  However, it is 
     157notify 100 { 
     158        match "system"          "USB"; 
     159        match "subsystem"       "DEVICE"; 
     160        match "type"            "ATTACH"; 
     161        match "vendor"          "0x082d"; 
     162        match "product"         "0x0100"; 
     163        match "release"         "0x0100"; 
     164        action "/usr/local/bin/coldsync -md -p /dev/$cdev -t usb"; 
     165}; 
     166 
     167# 
     168# Rescan SCSI device-names on attach, but not detach.  However, it is 
    151169# disabled by default due to reports of problems. 
    152170# 
     
    255273}; 
    256274 
    257 # When wifi goes up, setup lagg0 again 
     275/* EXAMPLES TO END OF FILE 
     276 
     277# An example of something that a vendor might install if you were to 
     278# add their device.  This might reside in /usr/local/etc/devd/deqna.conf. 
     279# A deqna is, in this hypothetical example, a pccard ethernet-like device. 
     280# Students of history may know other devices by this name, and will get 
     281# the in-jokes in this entry. 
     282nomatch 10 { 
     283        match "bus" "pccard[0-9]+"; 
     284        match "manufacturer" "0x1234"; 
     285        match "product" "0x2323"; 
     286        action "kldload if_deqna"; 
     287}; 
     288attach 10 { 
     289        device-name "deqna[0-9]+"; 
     290        action "/etc/pccard_ether $device-name start"; 
     291}; 
     292detach 10 { 
     293        device-name "deqna[0-9]+"; 
     294        action "/etc/pccard_ether $device-name stop"; 
     295}; 
     296 
     297# Examples of notify hooks.  A notify is a generic way for a kernel 
     298# subsystem to send event notification to userland. 
     299 
     300# Here are some examples of ACPI notify handlers.  ACPI subsystems that 
     301# generate notifies include the AC adapter, power/sleep buttons, 
     302# control method batteries, lid switch, and thermal zones. 
     303# 
     304# Information returned is not always the same as the ACPI notify 
     305# events.  See the ACPI specification for more information about 
     306# notifies.  Here is the information returned for each subsystem: 
     307# 
     308# ACAD:            AC line state (0 is offline, 1 is online) 
     309# Button:          Button pressed (0 for power, 1 for sleep) 
     310# CMBAT:           ACPI battery events 
     311# Lid:             Lid state (0 is closed, 1 is open) 
     312# RCTL:            Resource limits 
     313# Suspend, Resume: Suspend and resume notification 
     314# Thermal:         ACPI thermal zone events 
     315# 
     316# This example calls a script when the AC state changes, passing the 
     317# notify value as the first argument.  If the state is 0x00, it might 
     318# call some sysctls to implement economy mode.  If 0x01, it might set 
     319# the mode to performance. 
     320notify 10 { 
     321        match "system"          "ACPI"; 
     322        match "subsystem"       "ACAD"; 
     323        action                  "/etc/acpi_ac $notify"; 
     324}; 
     325 
     326# This example works around a memory leak in PostgreSQL, restarting 
     327# it when the "user:pgsql:swap:devctl=1G" rctl(8) rule gets triggered. 
    258328notify 0 { 
    259         match "system"          "IFNET"; 
    260         match "subsystem"       "wlan0"; 
    261         match "type"            "LINK_UP"; 
    262         media-type              "802.11"; 
    263         action "ifconfig lagg0 laggport wlan0"; 
    264 }; 
     329        match "system"          "RCTL"; 
     330        match "rule"            "user:70:swap:.*"; 
     331        action                  "/usr/local/etc/rc.d/postgresql restart"; 
     332}; 
     333 
     334*/ 
    265335 
    266336# Action to take when we add / remove a sound device 
     
    294364        action "/usr/local/share/pcbsd/scripts/lidchanged.sh open"; 
    295365}; 
    296  
    297 /* EXAMPLES TO END OF FILE 
    298  
    299 # The following might be an example of something that a vendor might 
    300 # install if you were to add their device.  This might reside in 
    301 # /usr/local/etc/devd/deqna.conf.  A deqna is, in this hypothetical 
    302 # example, a pccard ethernet-like device.  Students of history may 
    303 # know other devices by this name, and will get the in-jokes in this 
    304 # entry. 
    305 nomatch 10 { 
    306         match "bus" "pccard[0-9]+"; 
    307         match "manufacturer" "0x1234"; 
    308         match "product" "0x2323"; 
    309         action "kldload if_deqna"; 
    310 }; 
    311 attach 10 { 
    312         device-name "deqna[0-9]+"; 
    313         action "/etc/pccard_ether $device-name start"; 
    314 }; 
    315 detach 10 { 
    316         device-name "deqna[0-9]+"; 
    317         action "/etc/pccard_ether $device-name stop"; 
    318 }; 
    319  
    320 # Examples of notify hooks.  A notify is a generic way for a kernel 
    321 # subsystem to send event notification to userland. 
    322 # 
    323 # Here are some examples of ACPI notify handlers.  ACPI subsystems that 
    324 # generate notifies include the AC adapter, power/sleep buttons, 
    325 # control method batteries, lid switch, and thermal zones. 
    326 # 
    327 # Information returned is not always the same as the ACPI notify 
    328 # events.  See the ACPI specification for more information about 
    329 # notifies.  Here is the information returned for each subsystem: 
    330 # 
    331 # ACAD:         AC line state (0 is offline, 1 is online) 
    332 # Button:       Button pressed (0 for power, 1 for sleep) 
    333 # CMBAT:        ACPI battery events 
    334 # Lid:          Lid state (0 is closed, 1 is open) 
    335 # Suspend, Resume: Suspend and resume notification 
    336 # Thermal:      ACPI thermal zone events 
    337 # 
    338 # This example calls a script when the AC state changes, passing the 
    339 # notify value as the first argument.  If the state is 0x00, it might 
    340 # call some sysctls to implement economy mode.  If 0x01, it might set 
    341 # the mode to performance. 
    342 notify 10 { 
    343         match "system"          "ACPI"; 
    344         match "subsystem"       "ACAD"; 
    345         action                  "/etc/acpi_ac $notify"; 
    346 }; 
    347 */ 
Note: See TracChangeset for help on using the changeset viewer.