News:

Pretty crazy that we're closer to 2030, than we are 2005. Where did the time go!

Main Menu

Wireless Adapter

Started by Nate, January 10, 2006, 04:00:31 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Joe

Quote from: iago on January 12, 2006, 06:54:38 PM
The file is stored twice.  It is tarred, which combines all the files together, then it is gzipped. 

file -> file.tar -> file.tar.gz. 

tar file -> file.tar
gzip file.tar -> file.tar.gz

gunzip file.tar.gz -> file.tar
untar file.tar -> file

Read the manpage for tar, it tells you how to automatically ungzip it using the -z parameter.  It goes on to explain how this .tar and .gz business works, which is helpful no matter which OS you're on. 

Also, the word is "why", not "y".. I spend a lot of time helping you here, don't be lazy.  It makes me feel like I'm wasting my time. 

tar -xvvzf filename.tar.gz
x is for extract
vv is for very verbose
z is un-gzip
f is for who knows what
Quote from: Camel on June 09, 2009, 04:12:23 PMI'd personally do as Joe suggests

Quote from: AntiVirus on October 19, 2010, 02:36:52 PM
You might be right about that, Joe.


iago

Quote from: Joe[e2] on January 13, 2006, 05:51:12 PM
tar -xvvzf filename.tar.gz
x is for extract
vv is for very verbose
z is un-gzip
f is for who knows what

That's very nice, considering that he's on Windows. 

Also, f stands for "file", by default files are tarred/untarred from stdin. 

Nate

Ok i have actually made progress on this by leaps and bounds.  It actually recognizes the adapter but only when i boot from a disk.  My problem now is how do i make it see the network?

iago

If the network is DHCP-enabled, then run:
dhcpcd -d <device>

and it should pull an ip.  The device will be "eth0" or "eth1" or "wi0" or something. 

If you have an encryption key on your network, you'll need to do other stuff.  Here is the script I wrote to set up my network:
http://www.javaop.com/~iago/home-wireless.sh
it uses a static ip, but it should be easy enough to modify it to your needs. 

Nate

#19
Online thx.  I ended up using Ubuntu, Slackware had alot of problems on my comp and i dont know why.

The only thing now is that i have to reconfigure the wlan everytime i reboot and i only seem to be able to configure it on root.

iago

That's how I do it.  I know that Slackware has a rc.wireless startup script, but I don't use it.  The first thing I do when I log in at home is 'sudo ./home-wireless'.  When I'm not at home, I run the appropriate script.  It saves me a lot of trouble of re-modifying configuration files whenever I change networks.