From 57bed3df9310db328d80b32b31fdefa8418bbd1e Mon Sep 17 00:00:00 2001 From: Jim Pryor Date: Sun, 13 Sep 2009 23:43:48 -0400 Subject: Rename set_interface to bring_interface 3. Change the name of "set_interface up/down..." to "bring_interface up/down" to differentiate it from the similarly-named, merely record-keeping functions. Signed-off-by: Jim Pryor --- src/connections/wireless | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'src/connections/wireless') diff --git a/src/connections/wireless b/src/connections/wireless index 42504d2..e1d4a44 100644 --- a/src/connections/wireless +++ b/src/connections/wireless @@ -42,7 +42,7 @@ wireless_up() { fi report_debug wireless_up ifup - set_interface up-old "$INTERFACE" || return 1 + bring_interface up-old "$INTERFACE" || return 1 quirk prescan && iwlist "$INTERFACE" scan &> /dev/null # bcm43xx if quirk preessid; then # ipw3945 @@ -102,7 +102,7 @@ wireless_up() { if quirk "predown"; then # madwifi FS#10585 # ignore quirk nodown---is that appropriate? # this adds a flush call as well---is that appropriate? - set_interface forcedown-old "$INTERFACE" + bring_interface forcedown-old "$INTERFACE" fi report_debug wireless_up iwconfig "$INTERFACE" $WEP_OPTS @@ -114,7 +114,7 @@ wireless_up() { fi if quirk "predown"; then # madwifi FS#10585 - set_interface up-old "$INTERFACE" + bring_interface up-old "$INTERFACE" fi report_debug ethernet_up wep_check @@ -212,7 +212,7 @@ wireless_down() { # respects quirk nodown---is that appropriate? # wasn't this already called in ethernet_down? but does the call there respect quirk nodown? # this adds a flush call as well---is that appropriate? - set_interface down-old "$INTERFACE" + bring_interface down-old "$INTERFACE" # Handle wireless kill switches # Any reason why a hardware switch should be considered on interface down? -- cgit v1.2.3-24-g4f1b