| devd.conf (186432) | devd.conf (187743) |
|---|---|
| 1# $FreeBSD: head/etc/devd.conf 186432 2008-12-23 15:47:31Z thompsa $ | 1# $FreeBSD: head/etc/devd.conf 187743 2009-01-26 23:05:50Z sam $ |
| 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 --- 16 unchanged lines hidden (view full) --- 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# | 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 --- 16 unchanged lines hidden (view full) --- 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# |
|
| 34notify 0 { 35 match "system" "IFNET"; 36 match "type" "ATTACH"; 37 action "/etc/pccard_ether $subsystem start"; 38}; 39 | 39notify 0 { 40 match "system" "IFNET"; 41 match "type" "ATTACH"; 42 action "/etc/pccard_ether $subsystem start"; 43}; 44 |
| 40notify 0 { 41 match "system" "IFNET"; 42 match "type" "DETACH"; 43 action "/etc/pccard_ether $subsystem stop"; 44}; 45 | |
| 46# 47# Try to start dhclient on Ethernet like interfaces when the link comes 48# up. Only devices that are configured to support DHCP will actually 49# run it. No link down rule exists because dhclient automaticly exits 50# when the link goes down. 51# 52notify 0 { 53 match "system" "IFNET"; --- 255 unchanged lines hidden --- | 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"; --- 255 unchanged lines hidden --- |