>
> Hi!
I see your testing how many hours I do stay up :-)
> Trying to kill the keyboard, [EMAIL PROTECTED] produced:
> > Make sure you use 10k blocks! afio defaults to 5k (unless you hard code it
> > to 10k, I have found that it *CAN* goof up and spit out a 5k block if you
> > just use the command line. I hardcoded it to 10k.)
>
> You *can* use buffer (or dd, or even tar|tar IIRC) to reblock,
> however that might frag up afio's detection of end-of-medium.
Sometimes, that happens, which is why I suggest the rehardcoding default
blocksize of afio.
> And since you are gonna use a script anyway, you can lock it down
> in a script. You could also tell ftape to change the buffer size.
Which I mentioned.
> > 3:
> > There are litterally tons of undocumented options for afio. See the source.
>
> Undocumented options are usually undocumented for a reason, like
> they are unreliable or liable to change. Just know what you do.
>
Nahh the man pages are outdated, and README has the info on untested stuff.
from the afio readme:
Afio has far too many options and features (some of which are not even
in the manual page). Anything in afio that doesn't relate to reading
or writing an archive from/to a simple file or pipe or backing up and
restoring from floppies remains untested.
In particular, nobody has verified if the options -p -b -d -e -g -h
-j -l -m -u and -R and the special case archive names !command'
and ystem:file' really do what they claim to do.
Typical ested' afio uses are
... | afio -o -v -f -b 1024 -s 1440x -F -Z /dev/fd0H1440
... | afio -o -v -s 1440k -F -V -Z -G1 /dev/fd0H1440
afio -oZvx /tmp/pipe1 </tmp/pipe2
afio -i -Z -k -v -x -n /tmp/pipe1
... | afio -s 512m -c 1024 -Z -T 20k -G 1 -E /backup/compressed -v -o \
-L /backup/LOG -z /dev/tape 2>/dev/tty8 >/var/adm/backup
WARNING1: The Linux floppy drivers below kernel version 1.1.54 do not
allow afio to find out if a floppy write error has happened. If you
are running a kernel below 1.1.54, afio will happily fail to backup to
(say) a write protected disk and not report anything wrong! The only
way to find out about write errors in this case is by watching the
kernel messages, or by switching on the verify option.
WARNING2: the code for -F (and -f and -K) is a complete mess. It will
probably work in the normal case, but don't expect it to handle a
write/verify error correctly. If you get such an error, best thing is
to restart afio completely.
Now you know why I compile all my own stuff :-)
Yours,
--
http://dr.ea.ms http://IDE.cabi.net http://startrek.off.net
http://CPM.doa.org
________________
-= Andrew Kroll =---------------\ /-----------------------------
Tired of Bill Gates? LL \ /Think Bill is getting MY CASH??
Win '95 sucks! DOS is OK. LL II NNNNN UU UU XX XX Linux! A free Un*x
Want to turn your PC intoLL II NN NN UU UU XXX clone for 386/486/P5's
a powerful workstation? LLLLL II NN NN UUUUU XX XX FINALLY A -=REAL=- OS!
-------------------------------------\ /--= <[EMAIL PROTECTED]> =--
\ /
\/
!FREE! At your favorite FTP site!
