From: <li...@li...> - 2000-06-27 06:12:26
|
Salut, It's been rumoured that Stelian Pop said: > > Use the no rewinding tape device (such as /dev/nst0) and: > > mt -f /dev/nst0 rewind > dump 0f /dev/nst0 /dev/sda1 > dump 0f /dev/nst0 /dev/sda2 Dohh, thanks, I figured this out shortly after sending the email. One important remark, though: I run dump remotely (using ssh) and experienced several inconveniences/problems: -- If I don't set up a .rhosts (so that ssh prompts for a passwd) then somehow it seems that dump has grabbed stdin, and won't pass on the password to ssh. So the only way to dump remoely is to set up a .rhosts file (yuck). -- suppose that above problem was solved. There is then the inconvenience that said passwd would have to be entered for each invocation of dump (as well as for the mt), which makes running from a shell script hard/impossible. Ideally, I'd be able to just log in one session, and run the shell script in that and have it all exit when done. Other than that, it seems to work fine (although ssh on a 486 on an old ne2000 ethernet is slowwww at 70kb a sec). Which brings me to another question: How much buffering, if any, does dump do, and is this adjustable? At 70kb/sec, the tape drive seems to be doing a lot of rewind/preroll/record type back-n-forth tape movement. Of course, tape drives are usually happier when you can stream to them at thier natural streaming speed. --linas |