Description of problem:
When setting up bridged interfaces, any wireless options are ignored
because of an apparently bogus "exit 0" in /sbin/ifup that causes it
to exit before wireless options are processed.  The following seems to
fix it:

--- /sbin/ifup  2003-11-07 08:59:26.000000000 -0600
+++ /sbin/ifup  2004-05-08 02:54:51.405951000 -0500
@@ -180,7 +180,6 @@
       # Upon adding a device to a bridge, 
       # it's necessary to make radvd reload its config
       [ -r /var/run/radvd/radvd.pid ] && kill -HUP `cat
/var/run/radvd/radvd.pid`
-      exit 0
 fi 
 
 # now check the real state

Version-Release number of selected component (if applicable):
initscripts-7.42.2-1

How reproducible:
Every time.

Steps to Reproduce:
1. Create a bridge interface (TYPE=Bridge).
2. Add a wireless interface (BRIDGE=<bridge interface>, TYPE=Wireless)
and set some wireless options (ESSID, KEY, etc.).
3. Watch those options be silently ignored when bringing up the interface.
  
Actual results:
iwconfig on the wireless interface shows whatever the default (driver)
settings for the card are, such as ESSID "test".

Expected results:
iwconfig should report the options in ifcfg-<interface>.  Removing
that one line from /sbin/ifup makes this work.

Additional info:
I haven't had a chance to see if this is still broken in FC2/rawhide yet.