Wanderings.

• [done] put justin in wheel, disk and plugdev
• [todo] add /usr/sbin and /sbin and /usr/local/sbin to $PATH

So configurations should be made to rc.inet1.conf, rc.wireless.conf, and wpa_supplicant.conf. In our case, rc.wireless.conf needs no changes because this is for hardware specific settings for certain wireless cards. Mine is fine with the generic. So that leaves only /etc/wpa_supplicant.conf, and /etc/rc.d/rc.inet1.conf.

1. For automatic association on bootup:
1. put APs in wpa_supplicant.conf in the order in which they need to be looked for (this is my assumption – test later. for now only one ap is in there. Example:
   

   #home
   network={
   scan_ssid=1
   ssid="dd-wrt"
   key_mgmt=NONE
   }

   # Mom and Dad
   network={
   scan_ssid=1
   ssid="2535swift"
   proto=WPA2
   key_mgmt=WPA-PSK
   pairwise=CCMP
   group=CCMP
   psk=""
   }

   # Gryffindor (Robin and Richard0
   network={
   scan_ssid=1
   ssid="Gryffindor"
   proto=WPA2
   key_mgmt=WPA-PSK
   pairwise=TKIP
   group=TKIP
   psk=""
   }

   # Wildcard match for SSID (plaintext APs only). This example select any
   # open AP regardless of its SSID.
   network={
   key_mgmt=NONE
   }

2. Edit /etc/rc.d/rc.inet1.conf, uncommenting and changing only the lines uncommented below to suit my needs:
   
## Example config information for wlan0. Uncomment the lines you need and fill
## in your info. (You may not need all of these for your wireless network)
IFNAME[4]="wlan0"
USE_DHCP[4]="yes"
DHCP_HOSTNAME[4]="justin-laptop-wireless"
WLAN_WPA[4]="wpa_supplicant"

2. For APs on the fly,

   Just use wpa_gui. Below is a description of how to use it if wpa_supplicant weren’t already running. In my case it is running, so we can just use wpa_gui.

   1. Start wpa suppicant
   2. start wpa_gui and put in wpa stuff for the access point to connect to
   3. check stdout/stderr in the terminal where wpa supplicant is running to make sure associated. Confirmation should have already been given by the wpa_gui. if associated then proceed
   4. close wpa_gui
   5. background wpa_suppicant
   6. dhclient on that interface
   7. confirm it got an IP
   8. background that dhclient, and close the terminal

maybe this will work for me and maybe not. I’d like to have fbdev on consoles, but this is really trivial. if it gets in the way of anything at all, ,namely 1) optimal X config, or 2) stability – if anything goes wrong, is it best to have character cell console?
lilo.conf:

# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
#vga = normal

http://slackbuilds.org/repository/12.1/audio/audacity/

Audacity 1.3 requires libsndfile, and either wxGTX or wxPython. I opted for wxGTK.