>I was wondering if there is a way to see how big
>an archive would be if I were to tar an entire disk.
Ignoring many details and questions that occur to
me (like the question of whether this is the right
way to approach the problem in the first place) I'd
suggest something like this:
tar cvzf - / | dd bs=1024k of=/dev/null
which would have tar generating the (compressed) archive
image and feeding it to dd, who has been told to simply
throw everything into the bit-bucket. The intent here
is that dd will report how many records (blocks) tar
has handed to it, for example:
2356+1 records in
2356+1 records out
which, since we specified 1Mb records, means the archive
would require approx 2.4 Gb. As I said, various details
are being ignored here, but that's one simple-minded way
to do it...
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
