Ftape install help: Well I finally have the ftape installed and working with Linux, I am using kernel version 1.1.35, modulils [newest from sunsite], and ftape-1.13b. The main problem I had was not having all the right files to support the installation... i.e. the latest version of libc.so.4.5.26 and libm.so.4.5.26 in the /lib directory... If you manually install these don't for get to link libc.so.4 -> libc.so.4.5.26 here is how: rm libc.so4 ln -s libc.so.4.5.26 libc.so.4 // this creates the symbolic link rm libm.so4 ln -s libm.so.4.6.26 libm.so.4 // again create a symb. link then you need version 2.5.8 of gcc and install that by doing: umask 022 cd / tar xzf gcc-2.5.8-p1.tar.gz tar xzf gcc-2.5.8-p2.tar.gz // I didn't install this but you may and you need the newest version of the kernel, or at least I did: umask 022 // get permissions right cd /usr/src rm -rf linux // have to be root to do this tar xzf linux-1.1.35.tar.gz now this is where I can't really help, In order to compile the new version of the kernel you need a version of "ld" that supports -qmagic. I tried to find it, but didn't maybe if is in the gcc-2.5.8-p2.tar.gz file. I just ftp'd it from my friend. After I got that things started working. Recompile your kernel (with Q-117 support, the default 3 buffers works) just in case a new person reads this I will step through this also as I hated starting out and someones help file assumes you have done everything... cd /usr/src/linux make mrproper make clean make config // Will prompt you for your configuration info make dep make zlilo // you can do "make" but this way is easier for me // you dont have to move everything around after it's // done :) after the kernel is done compiling, and provided there were no problems you need to setup your boot disk/partition using: liloconfig that will setup your boot device (disk, or HD Partition, etc.) now reboot and after logging in type: uname -sr // if things went OK should say "Linux 1.1.35" if you want use your favorite editor and change the /etc/issue to change the version number displayed at startup. Now get the ftape and modutils files and extract them somewhere to work on them.. mkdir /new // a place to put new stuff cd /new tar xzf ftape-1.1b.tar.gz mkdir modutils // the latest version didn't have a directory included cd modutils tar xzf modules.tar.gz Now you need to now create some device files to access the tape drive by doing the following: mknod -m 666 /dev/rft0 c 27 0 mknod -m 666 /dev/rft1 c 27 1 mknod -m 666 /dev/rft2 c 27 2 mknod -m 666 /dev/rft3 c 27 3 mknod -m 666 /dev/nrft0 c 27 4 mknod -m 666 /dev/nrft1 c 27 5 mknod -m 666 /dev/nrft2 c 27 6 mknod -m 666 /dev/nrft3 c 27 7 ln -s /dev/rft0 /dev/ftape // link in some easy to use names ln -s /dev/nrft0 /dev/nftape // " " " " " " " " now modify the ftape.h file in the uncompressed ftape directory using you editor. Change the following: #define RETRIES_ON_CRC_ERROR 3 /* number of low level retries */ #define RETRIES_ON_ECC_ERROR 3 /* ecc error when correcting segment*/ #define RETRIES_ON_WRITE_ERROR 5 /* general write error */ to #define RETRIES_ON_CRC_ERROR 5 /* number of low level retries */ #define RETRIES_ON_ECC_ERROR 5 /* ecc error when correcting segment*/ #define RETRIES_ON_WRITE_ERROR 10 /* general write error */ This is just to allow some more room for dirty heads and I/O errors. Now you can compile the ftape driver: cd /??/ftape-1.13b // /??/ is wherever you put it make it should compile cleanly after a few minutes.. and leave you with a ftape.o which is needed to insert into the kernel using the modutils. Now compile the modutils: cd /??/modutils make install this should install the binaries to your /usr/bin or /usr/sbin. now if you got some garbage at the end but have the executable files there then you can safely ignore it. It tries to install the ftape.o into the kernel but probably couldn't find it so... cd /??/ftape-1.13b insmod ftape.o // insert the ftape driver into the kernel if you didn't get any errors then see if it is actually there by doing: lsmod it should echo: Module: #pages: ftape 39 if that is good then it should work. to test it out here are some commands to use the tape drive. Note, the tape must be formatted first, and you must use the erase command before using tar with it (at least that's my understanding, but I could be wrong) mt -f /dev/rft0 rewind // rewind the tape if it isn't // if it is won't do anything mt -f /dev/ftape fsf 0 // read the tape header mt -f /dev/ftape erase // erase anything on the tape tar cvf /dev/ftape ??? // ?? being the file you want to // put onto the tape tar tf /dev/ftape // read back what is on the tape tar xf /dev/ftape // get what is on the tape. // you can extract a file by calling // it by nameafter the /dev/ftape // if it isn't found it will let you // know I am aware that there are still some problem with this driver, but it sure beats using floppy disks. I would give commands for cpio and dd but I just got the ftape driver working this morning, and what I have listed has worked for me. I hope this was comprehensive enough to help more people to get to this level and maybe we will have more people trying to fix any errors when they come up instead of just trying to get the damned thing working. Here is where you can get the files I used: sunsite.unc.edu: // or other mirror, files might not be in as of 28JUL94 // the same place though :( -------------------------------------------------------------------------- /pub/Linux/kernel/patches/tapes/ftape-1.13b.tar.gz // QIC-40/80 tape driver /pub/Linux/kernel/v1.1/linux-1.1.35.tar.gz // kernel sources /pub/Linux/kernel/v1.1/modules.tar.gz // modutils for v1.1.X /pub/Linux/GCC/libc-4.5.26.tar.gz // lib's needed /pub/Linux/GCC/gcc-2.5.8-p1.tar.gz // gcc 2.5.8 part 1 /pub/Linux/GCC/gcc-2.5.8-p2.tar.gz // gcc 2.5.8 part 2 If anyone has any contribution/ flames/ questions/ etc. feel free to email me with your perspective(s) also if this helped at all please email me as if it helps enough people, I may try doing some other help file on other problematic installations, provided that I have figured it out... :) I can be reached at: jeremy.main@m.cc.utah.edu Jeremy [a struggling pre-computer science major at the University of Utah] [I'm working on the 6 year degree program!!!! ]