I'm pretty sure there's a way to make slackware run iwconfig/wicd/dhcpcd on boot so I don't have to do it myself each time; can anyone explain how? I checked slackwiki (which as a new guy I can't link) but couldn't find anything.

Also, my university works from either a wireless or a wired connection. Is it possible to autodetect the wired connection, and if it's connected (ethernet cable) to configure that instead?

On a completely unrelated note, animated .gifs seem to slow everything down a whole lot. Is there a way to fix that?

As for generic instructions see http://alien.slackbook.org/dokuwiki/...eless_networks

Your question about "wicd" should be answered by the README which accompanies it - wicd is not part of Slackware, you will have to bind it's startup script "rc.wicd" into the Slackware rc scripts yourself.

Eric

Greetins,

About activating your wireless card upon boot up it is easy to do, once you have the right module(s) loaded. I'm going to assume you already have them working.

Check /etc/rc.d directory and you will find a rc.wireless script in there. If you want it starting during boot up procedures, make sure it has execution permissions set properly (chmod 755 /etc/rc.d/rc.wireless).

About having a dhcp client starting up when booting, the right file for configuring this is /etc/rc.d/rc.inet1.conf (find the section corresponding to your network interface and set USE_DHCP[x]="yes", where x stands for your interface number id -- such as 1 for eth1).

About automatic link detection I can not help you. Anyway, as a workaround, you can create two small scripts setting up connection parameters for each case.

I do not have a clue about your animated GIF issue, unless either they are too big, or your connection is too bad (damaged hubs, switches, cables and/or connectors), or it is too heavily loaded, or it is too slow. Provided the server has enough bandwidth to serve it reasonably fast, of course.

Regards

Hahah, I think I got it working. At least, it worked on this boot (woo). Turns out I didn't need wicd after all (though it handles the wired connections quite nicely).

I also just experienced my first Lilo screw-up. Scared the hell out of me, it did.

As for the .gifs, it might just be the old version of Firefox that I'm using. I've been trying to find a working Midori package for 12.1 for a while now; currently, trying to run Midori gives me "cannot find [some library]".

Nice.

I have installed Firefox 3.0 binary distribution pretty easily: just unpacked to /usr/local/lib/firefox and created a symlink pointing to firefox script in it.

I do not have tested it thoroughly but it runs nicely on the sites I have visited already.

Give it a try.

Oh, heh. Shortly after my last post, I downloaded a "Firefox 3" package from Linuxpackages.net. I obviously didn't read closely enough: I am now running Firefox 3-in Portugese.
Oh, the things life throws at you.