Update 2: Sep 30, 2004, 3:14am
Edited the /etc/rc.d/rc.wireless.conf
Changed the ESSID from Any to
Logged out and logged in - no luck.
/etc/rc.d/rc.pcmcia stop , then start - no luck.
reboot - got it working on the reboot…Dunno if it was the manual editing of the file…or the Kwifi manager.
Change it in /etc/X11/xinit/
or
use xwmconfig.
or
at the login screen, change the Session to whatever you want.
(This was tested in Slackware 10)
To display a graphical login prompt, change the runlevel from 3 to 4
/etc/inittab
Got the Hawking Wireless card working on Slackware 10 (Dell Laptop).
I cannot say “finally” because I had never tried earlier 
Had left the card in the PCMCIA slot during install and it installed drivers or modules for it automatically.
Leaving the card in the slot during installation has nothing to do with it.
It is when the system is rebooting that the Cardbus services are activated and
these devices detected.
Saw that KDE had KWifiManager installed. This KWifi is pretty cool. It shows the signal strength, the access point MAC address,
the IP address. Just like the Windows utility. KWiFiManger simply reports the information being handled by wireless tools. In addition, it also has different configuration profiles too.
It wouldn’t work the first time though after I changed the SSID and activated the configuration.
So I gave it a restart and it worked !
Reboot not really necessary.
I tried this and it worked!
/etc/rc.M
Apparently, this was a re-init of all services for the Multiuser profile,
I guess rc.pcmcia would have done the same.
So that got my Internet working (I saw the IP address was assigned).
It got detected as eth0, which is quite confusing. The onboard NIC became eth1.
In some distro of Linux, I had seen that the wireless connections were referred to by wlan0, wlan1 and so on…
In any case, wireless is working and at last the laptop can be moved out of my room.
It’s only this card that was working and I don’t know how to get the other cards working (as yet).
So here are some commands and snippets I learnt along the way:
/etc/rc.d/wireless - This file is read when initializing the wireless connections when booting up.
Wireless networking is managed via the /etc/rc.d/rc.wireless, /etc/rc.d/rc.wireless.conf and /etc/rc.d/rc.wlan scripts.
Wireless Tools for Linux
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html
Some links on KWifiManager
http://www.linuxquestions.org/questions/archive/3/2003/11/4/118736
Slackware 10 on a Dell Laptop
http://www.mikeoliveri.com/utils/dellslack.html
Slackware Network Configuration
http://openskills.info/view/boxdetail.php?IDbox=1103&boxtype=distro
Installed Eclipse 3.0.2 on a Dell Laptop running Slackware 10.0
Installed Java into /usr/local
This link gives a walkthrough to editing the /etc/profile file.
http://www.linuxforum.com/forums/index.php?showtopic=86431
———————————————————————————
Best solution - set both variables for all users:
-remove the addition to /home/danny/.bash-profile (we’ll move it to /etc/profile)
-edit /etc/profile
add:
export JAVA_HOME=/home/danny/Development/Java/j2sdk1.4.2_05
export PATH=$PATH:$JAVA_HOME/bin
Home is not set to ../j2sdk1.4.2_05/jre/bin/java as that is an actual file, and it should be set to the top directory of java.
The PATH is set to incluse $JAVA_HOME/bin instead of $JAVA_HOME/jre/bin/ as I think that the former is the correct java to use for the sdk, though both look the same:
| CODE |
| root@lfs:/opt/j2sdk/j2sdk/bin# ./java -version java version “1.4.2_03″ Java(tm) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) Java HotSpot(tm) Client VM (build 1.4.2_03-b02, mixed mode) root@lfs:/opt/j2sdk/j2sdk/bin# cd ../jre/bin root@lfs:/opt/j2sdk/j2sdk/jre/bin# ./java -version java version “1.4.2_03″ Java(tm) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) Java HotSpot(tm) Client VM (build 1.4.2_03-b02, mixed mode) |
If it doesn’t work for you then try
export PATH=$PATH:$JAVA_HOME/jre/bin
instead
Once the profile is changed, bash needs to load the profile. You can login again, start another bash session (new console or konsole or whatever) or type:
source /etc/profile
check the settings have taken effect with:
echo $JAVA_HOME
echo $PATH
You may also want to set MANPATH to include $JAVA_HOME/man
export MANPATH=$MANPATH:$JAVA_HOME/man
if your distro uses /etc/man.conf then add the manpath to that instead.
add the line:
MANPATH /home/danny/Development/Java/j2sdk1.4.2_05/man
You mentioned CLASSPATH in the topic, this is from the Beyond Linux From Scratch instructions:
| QUOTE |
Handling CLASSPATH When compiling packages, the CLASSPATH environment variable is used by JDK to locate classes at compile-time and run-time. It is tedious to add all the classes used to the CLASSPATH manually. You may add the following lines to your shell startup file to set CLASSPATH automatically to include all JAR files in a specified directory, which in the example below is /usr/lib/auto-java-classpath. AUTO_CLASSPATH_DIR=/usr/lib/auto-java-classpath
|
so you can modify that to use whatever directory you want to have your classes, and put it into /etc/profile
———————————————————————————