Date: Wed, 22 Mar 2000 09:34:43 +1000 (EST) From: George Michaelson <ggm@dstc.edu.au> To: freebsd-config@freebsd.org Subject: install/fixit floppies need wicontrol for WaveLAN Message-ID: <200003212334.JAA00416@asuncion.dstc.edu.au>
next in thread | raw e-mail | index | archive | help
/usr/sbin/wicontrol is 88k static linked. Probably less if integrated into a /stand merge-binary. Without wicontrol, you cannot set post-PCMCIA initialization parameters for the wi0 driver to bring it live. Even though ifconfig can 'probe' wi0, if you can't set MAC address and encryption and wireless encoding/datarate options, in some locked-down wireless networks, wi is useless. If its too big to add to the code in /stand, then adding it to fixit and README/INSTALL instructions would help. A more general suggestion for README/INSTALL: What to do if <x> is missing for you to hack around install problems: If you have another running FreeBSD machine and some program or datafile <x> is viable to run if only it was on the install or fixit floppy, then as long as you have a working 1.44Mb or other floppy drive, you can transfer it by using a raw floppy as a virtual 'tape' device. 1) launch shell 2) on source machine, tar cBpf /dev/fd0 <x> 3) on installing machine, remove mfsroot or fixit floppy 4) cd /tmp; cpio -I /dev/fd0 -i 5) the program or data you need is now in /tmp/<x>. 6) if its over 1.44Mb, then you will need to reassemble the file on the destination machine which may be a problem without tools like dd/cat. I suggest cutting with tar because 99% of users use tar and not CPIO in daily working life. They may be able to cut a tarfile on another box to raw media as well as doing it this way. There is probably some issues with doing this, but for the example above, it worked for me! cheers -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-config" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003212334.JAA00416>