How do i go wireless in Slack 12?

mikelist · 12-14-2007, 06:19 PM

i just installed slackware 12 on my laptop. all i had to do was check iwconfig to make sure the wireless was recognized, then "dhcpcd eth1"
at which point i checked ifconfig to make sure.

i really can't speak about any other machines, mine is an older dell latitude cp.

maniac matt · 12-14-2007, 10:16 PM

Quote:

Originally Posted by titopoquito

trickykid meant something like this:

file ~/.bashrc

Code:

export PATH=$PATH:/sbin

file ~/.bash_profile

Code:

if -f ~/.bashrc; then
  . ~/.bashrc

This way /sbin is -- like all folders in your path before -- is searched for executables when you type in a command.

Well, i am sorry to say that i don't quite get how to do this... do i need to find a file named "/.bashrc", and add those lines?

basically.. i don't know where to start.

help?
-matt

pappy_mcfae · 12-15-2007, 02:23 AM

Quote:

Originally Posted by maniac matt

Well, i am sorry to say that i don't quite get how to do this... do i need to find a file named "/.bashrc", and add those lines?

basically.. i don't know where to start.

help?
-matt

That's easy. Assuming you use KDE as your X Windows manager:
1) Open konqueror using the "System" icon on your desktop.
2) Click on "Storage Media".
3) Click on your root media disk.
4) Under that, click on the /root folder.
5) In the pane on the right, right click and select "Create New"-->"Text File; enter .bashrc in the dialog box.
6) Repeat above step, but this time enter .bash_profile in the dialogue box.
7) Open the newly created ~/.bash_profile; cut and paste the following into it:

Code:

# ~/.bash_profile
# Source .bashrc
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi

8) Save and exit
9) Open the newly created ~/.bashrc file; cut and paste the following into it:

Code:

# ~/.bashrc bash configuration file
export PATH=$PATH:/sbin
#

10) Save, exit, reboot.

~/.bashrc is a really useful tool. Mine compensates for the fstrans=no bug in checkinstall, sets the color schemes for my console (and konsole) sessions, loads my UTF8 console font, and adds my custom programs and scripts folders into my path.

FYI, if it's confusing, ~/.bashrc is short for /root/.bashrc

Hope that helps

Blessed be!
Pappy

titopoquito · 12-15-2007, 05:16 AM

Quote:

4) Under that, click on the /root folder.
[... snip ...]
FYI, if it's confusing, ~/.bashrc is short for /root/.bashrc

I didn't mean to put them in /root but in your normal user's folder. Don't want to start a flame war here but basically it's useless to create the PATH line for root user (like I stated above) and most people will also advice to not use root account for all tasks as long as you don't really know what you are doing. Since you seem to be a beginner, you should do most things from a normal user account anyway unless you are prepared to reinstall Slackware a couple of times.
So these files belong into /home/matt if you have an user called "matt" (I guess you do

). If they don't exist, just create them. Edit them with any editor of your choice (nano, vim, emacs in console, kedit, kwrite, mousepad ... in graphical mode).
If you want this for all users for which you might have accounts on your machine, you can put the line in /etc/profile (you have to be root to do this). Or you create the files also in /etc/skel so that any time you create a new user, that user will get them copied to her/his /home/name-of-user folder.

If you want to understand why they are useful and why they both are required read the BASH guide for beginners at www.tldp.org.

Alien Bob · 12-15-2007, 08:44 AM

Quote:

FYI, if it's confusing, ~/.bashrc is short for /root/.bashrc

Please please please don't start trying to help people by using the root account in your examples.
Running as root for day-to-day activities is very unsafe, I guess there are people who do not care to be hacked at some time, but this forum targets the questions of newbie Slackware users.

I do not want see any posts in this forum that would make it appear as if running as root is safe to do.

Eric

Nille_kungen · 12-15-2007, 09:42 AM

I would use ip alias in /etc/rc.d/rc.inet1
If you connect to allot of networks regularly this is the best way to solve it.
Heres an example of an ip alias.
# Config information for eth0
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""

# Config information for eth0:1
IFNAME[1]="eth0:1"
IPADDR[1]="192.168.1.10"
NETMASK[1]="255.255.255.0"
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""

maniac matt · 12-16-2007, 11:37 AM

Thanks Pappy, i will give it a shot, and Alien Bob, i will be sure to put it into my /home/matthew file.

Also thank you to Nille Kungen.. i will also give that a shot.

-Thanks again, Matthew

unixfool · 12-17-2007, 06:52 AM

Scratched this post...misread some things. My apologies.