oneechanhax/phunix
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

'fix' crlf style

Browse Source
This commit is contained in:
Ben Gras 2007-07-24 14:49:39 +00:00
parent 816f5dd550
commit 2dc2db4ba1
1 changed files with 40 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

80
drivers/orinoco/INSTALL.txt
View File

@ -1,40 +1,40 @@
The driver has been tested on Minix 3.1.3, svn revision 2928: The driver has been tested on Minix 3.1.3, svn revision 2928:
http://derelict.cs.vu.nl/images/minix3_1_3_ide_r2928.iso.bz2 http://derelict.cs.vu.nl/images/minix3_1_3_ide_r2928.iso.bz2
To install the driver do: To install the driver do:
#sh install_script #sh install_script
This script will patch, compile and install 2 code files in Minix: This script will patch, compile and install 2 code files in Minix:
/usr/src/services/rs/service.c /usr/src/services/rs/service.c
/usr/src/commands/dhcpd/devices.c /usr/src/commands/dhcpd/devices.c
(see the docs directory for more information) (see the docs directory for more information)
Furthermore, the script will patch 1 configuration file: Furthermore, the script will patch 1 configuration file:
/etc/drivers.conf /etc/drivers.conf
(adding an entry for 'orinoco') (adding an entry for 'orinoco')
and 1 script file: and 1 script file:
/usr/etc/rc /usr/etc/rc
(adding an entry in a for-loop to start orinoco) (adding an entry in a for-loop to start orinoco)
Finally, the script will copy the orinoco driver into the drivers directory, Finally, the script will copy the orinoco driver into the drivers directory,
compile and install it. compile and install it.
When the script completes successfully, the inet.conf file has to be adjusted When the script completes successfully, the inet.conf file has to be adjusted
so that Minix will use the orinoco driver. Add an entry like: so that Minix will use the orinoco driver. Add an entry like:
eth0 orinoco 0 {default;}; eth0 orinoco 0 {default;};
The last step is to set the essid and WEP key of the network in the boot The last step is to set the essid and WEP key of the network in the boot
monitor. When in the boot monitor, type: monitor. When in the boot monitor, type:
essid=<essid> essid=<essid>
wep=<WEP key> wep=<WEP key>
save save
The essid is the name of the wireless network The essid is the name of the wireless network
The WEP key is a string of 13 ASCII characters, being the key of the wireless The WEP key is a string of 13 ASCII characters, being the key of the wireless
network. This variable shouldn't be set when the network is not WEP protected. network. This variable shouldn't be set when the network is not WEP protected.
If the essid is not set, the card will just try connect a network quite at random If the essid is not set, the card will just try connect a network quite at random
N.B.: WPA is not supported N.B.: WPA is not supported
N.B.: WEP seems to be buggy. At my place it works, at the VU it doesnt. So if N.B.: WEP seems to be buggy. At my place it works, at the VU it doesnt. So if
things don't work, try without WEP things don't work, try without WEP