Re: tar question
On 31/10/06, Mike Spenard [EMAIL PROTECTED] wrote: After tar has finished writing to the tape device is there a way to see how large the finished tar on tape is? Forgive me if this sounds impressively stupid, but would you not just use ls(1) for that? Also, is there a way to monitor the transfer rate to the tape device? I doubt that there's a trivial way to do that, and I'm not knowledgeable enough to really be able to help with any non-trivial way to do this.
Re: tar question
On Tue, Oct 31, 2006 at 11:06:13AM +0100, ropers wrote: On 31/10/06, Mike Spenard [EMAIL PROTECTED] wrote: After tar has finished writing to the tape device is there a way to see how large the finished tar on tape is? Forgive me if this sounds impressively stupid, but would you not just use ls(1) for that? No, tapes are not block devices; only block devices hold filesystems. (When you think about it, this makes sense; seek times would be prohibitively high for tapes.) Also, is there a way to monitor the transfer rate to the tape device? I doubt that there's a trivial way to do that, and I'm not knowledgeable enough to really be able to help with any non-trivial way to do this. How about tar czpf / | dd obs=$BIGNUM /dev/nrst0? More sophisticated methods are always possible, of course... Joachim
Re: tar question
On 31/10/06, Joachim Schipper [EMAIL PROTECTED] wrote: On Tue, Oct 31, 2006 at 11:06:13AM +0100, ropers wrote: On 31/10/06, Mike Spenard [EMAIL PROTECTED] wrote: After tar has finished writing to the tape device is there a way to see how large the finished tar on tape is? Forgive me if this sounds impressively stupid, but would you not just use ls(1) for that? No, tapes are not block devices; only block devices hold filesystems. (When you think about it, this makes sense; seek times would be prohibitively high for tapes.) Also, is there a way to monitor the transfer rate to the tape device? I doubt that there's a trivial way to do that, and I'm not knowledgeable enough to really be able to help with any non-trivial way to do this. How about tar czpf / | dd obs=$BIGNUM /dev/nrst0? More sophisticated methods are always possible, of course... I was thinking about something similar but using buffer from the misc/buffer port somehow instead of dd. I believe that that program will give you both the total size (in bytes transferred, I'm not certain this is the same as the size of the achive on the tape as I don't know anything about tape drives) and the rate of the transfer. Read the manual. Cheers, Andreas -- Andreas Kahari Somewhere in the general Cambridge area, UK
Re: tar question
On 31/10/06, Joachim Schipper [EMAIL PROTECTED] wrote: On Tue, Oct 31, 2006 at 11:06:13AM +0100, ropers wrote: On 31/10/06, Mike Spenard [EMAIL PROTECTED] wrote: After tar has finished writing to the tape device is there a way to see how large the finished tar on tape is? Forgive me if this sounds impressively stupid, but would you not just use ls(1) for that? No, tapes are not block devices; only block devices hold filesystems. (When you think about it, this makes sense; seek times would be prohibitively high for tapes.) Ah! Thank you! :)
Re: tar question
On Tue, Oct 31, 2006 at 11:53:53AM +0100, Andreas Kahari wrote: | How about tar czpf / | dd obs=$BIGNUM /dev/nrst0? More sophisticated | methods are always possible, of course... | | I was thinking about something similar but using buffer from the | misc/buffer port somehow instead of dd. I believe that that program | will give you both the total size (in bytes transferred, I'm not | certain this is the same as the size of the achive on the tape as I | don't know anything about tape drives) and the rate of the transfer. dd(1) does that too, you can send SIGINFO to dd and it'll tell you the rate at which it has been transferring data and the amount transferred up till then. Once it's done you get the same information without sending SIGINFO. Cheers, Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: tar question
2006/10/31, Mike Spenard [EMAIL PROTECTED]: After tar has finished writing to the tape device is there a way to see how large the finished tar on tape is? gtar has --totals Also, is there a way to monitor the transfer rate to the tape device? gtar has --checkpoint Best Martin
Re: tar question
Mike Spenard [EMAIL PROTECTED] wrote: After tar has finished writing to the tape device is there a way to see how large the finished tar on tape is? Also, is there a way to monitor the transfer rate to the tape device? dd gives you both of these pieces of information. just pipe tar through dd instead of pointing tar directly to the tape device -- A novice was trying to fix a broken Lisp machine by turning the power off and on. Knight, seeing what the student was doing, spoke sternly: You can not fix a machine by just power-cycling it with no understanding of what is going wrong. Knight turned the machine off and on. The machine worked. -- Danny Hillis
tar question
Hello, How can I exclude files or directories when using tar? I found that gnu tar uses --exclude, but how can I do this in openbsd?! How can I do this for example under openbsd: tar czf x.tar.gz /usr/src --exclude CVS/ Thank you very much! Regards Didier
Re: tar question
sorry forget it guys ;-/ installing gtar is the issue ...
Re: tar question
On 10/17/06, Didier Wiroth [EMAIL PROTECTED] wrote: Hello, How can I exclude files or directories when using tar? I found that gnu tar uses --exclude, but how can I do this in openbsd?! Use find (/usr/bin/find) to select the files you require, and pipe the output to tar. -- ach
