"Billy B. McCoy" wrote (in part): > > > 4) There is no /usr/src/linux/.config file, and the 'make' > > > produces errors without it. (/var/log/messages too long to attach :( > > > > The above symlink should take care of it (assuming you have created a > > .config in /usr/src/linux-2.0.36.) > > > > Bob > ... > Thanks Bob, > 1) I didn't address the 'kcore' subject: In testing & loading this > package, the /proc/kcore file has used up all my disk space. Is > there a way to dump this file? It is RO by root. On my system, it reads: -r-------- 1 root root 67112960 Jun 6 13:37 kcore which could certainly consume a lot of disk space (roughly one byte per byte of main memory). Why are you copying it to disk anyway? > 2) The .config file is not located in /usr/src/linux-2.0.36 either :( > How do I create this file (not empty of course). I wish Red Hat would distribute that (the one they used to build the system they ship). I have guessed that the following procedure will come up with the one they used to build the system, but I can find no assurance that it is correct: 1.) Install the kernel source, presumably in /usr/src/linux-2.0.36 where just the header files are now. 2.) Run make xconfig (if you like a window-type setup). 3.) Click the button about ftape 4.) Check that the configuration is how you want it. (I had to switch it to do a CTC-2Mb controller instead of the standard floppy one.) 5.) Click "save and exit" (or whatever it is called). 5a.) If you are brave (I suggest skipping it), build and install the new kernel (I did not do this). 6.) Then build the ftape suite. Unfortunately, at least with the Red Hat Linux 6.0 (which uses kernel 2.2.5-15), you MUST have the .config file, even if you fill out everything you (think) you need in the MCONFIG file, in order to get ftape to build. > 3) What is a good simple public tape backup software package to use > and where can I download it? There appear to be a number of packages > @ ftp://www.zn.ruhr-uni-bochum.de/pub/linux/ I looked at BRU that a lot of people seem to like. I found it so confusing that I just have some scripts for cron to do every morning around 4 A.M. Here is one of mine, with a lot of stuff edited out to make it shorter and easier to understand. # NOW DO THE BACKUP. # Retension the tape. /usr/bin/ftmt -f $OUTPUT_DEVICE_NR reten & # Delete old file list; we will concatenate the new one to an empty one. /bin/rm -f $WHERE /bin/touch $WHERE # Make the list of files to backup. Write them relative to root, so they can # be restored easily elsewhere if required. We try to do only those we cannot # get from the R.H. disk and the Applixware and Informix-SE disks (whose stuff # is on /opt). We do the Netscape plugins since some are hard to get and # configure, but they change seldom. We do not do /data, as this is # huge and it makes more sense to back that one up separately and manually. /usr/bin/find ./boot -depth -newer $NEWER_THAN \! -type d -print >> $WHERE /usr/bin/find ./etc -depth -newer $NEWER_THAN \! -type d -print >> $WHERE ... # Wait for /usr/bin/ftmt -f $OUTPUT_DEVICE_NR reten & to complete. wait # Now back them up. cat $WHERE | cpio -o -a --io-size=$IO_SIZE --format=crc -O $OUTPUT_DEVICE # Put the drive offline so no one will write on it mistakenly. # someone will need to explicitly do /usr/bin/ftmt -f $OUTPUT_DEVICE reset to # use the tape again. /usr/bin/ftmt -f $OUTPUT_DEVICE_NR offl # Mark when the Sunday backup was done, so the ones for each other day of the # week will be incremental from the Sunday ones. # Keep Sunday.backup from growing too large: keep about a month's worth. tail --lines 5 --quiet $BACKUP_DIR/Sunday.backup > /tmp/Sunday.backup mv /tmp/Sunday.backup $BACKUP_DIR/Sunday.backup echo /etc/cron.sunday/backup.cron `date` $WHERE $IO_SIZE >> $BACKUP_DIR/Sunday.backup > 4) Where are the ftape_tools packages located? http://www.math1.rwth-aachen.de/~heine/ftape/development.html I suggest looking at that page, since you can get either a .tar.gz file or an .rpm file, depending on what you prefer. -- Jean-David Beyer Shrewsbury, New Jersey Registered Linux User 85642.
