public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compression tools Compared
Date: Sat, 13 Aug 2005 17:32:07 +1200	[thread overview]
Message-ID: <1123911127.28841.10.camel@sf.rout.dyndns.org> (raw)
In-Reply-To: <200508130058.19730.mcbrides9@comcast.net>

On Sat, 2005-08-13 at 00:58 -0400, Jerry McBride wrote:
> Anyone else here subscribe to the LINUX JOURNAL?
> 
> In the September issue there's a neat article titled tha same as the subject 
> line of this message.
> 
> The skinny is, there's some really nice file compressors out there and I never 
> heard of two of them... Anyone else know about LZMA or 7ZA?
> 
> The two mentioned compression tools work pretty much like gzip. You tar up 
> your files, pipe to the compression filter and then on to the target file. 
> Below is a small example of what I've been seeing here at the shack.
> 
> -rw-r--r--  1 root root 12359680 Aug 12 23:57 backup.tar
> -rw-r--r--  1 root root  3536665 Aug 13 00:01 backup.tar.7z
> -rw-r--r--  1 root root  4438465 Aug 13 00:08 backup.tar.bz2
> -rw-r--r--  1 root root  4747637 Aug 13 00:03 backup.tar.gz
> -rw-r--r--  1 root root  2731412 Aug 13 00:10 backup.tar.lzma
> -rw-r--r--  1 root root  5125474 Aug 13 00:16 backup.tar.lzop
> 
> What you're seeing are the results of compressing /lib on my gentoo powered 
> laptop. I've not bothered with timing the processes as the better compression 
> rates are at the cost of speed and memory usage. Not good for "while you 
> wait" processing, but just plain perfect for backups and what-have-you on 
> servers... One side note, 7za does not record user/group info... 


Are you saying it removes user/group info from the tar file?


> It's a shame 
> too as this make it pretty much useless in most linux backup scenarios. This 
> lzma creature is simply awesome.
> 
> You can find it at: http://martinus.geekisp.com/rublog.cgi/Projects/LZMA
> 
> Cheers all....
> 
> -- 
> 
> ******************************************************************************
>                      Registered Linux User Number 185956
>               FSF Associate Member number 2340 since 05/20/2004
>              Join me in chat at #linux-users on irc.freenode.net
>     Buy an Xbox for $149.00, run linux on it and Microsoft loses $150.00!
>     12:28am  up 26 days, 27 min,  1 user,  load average: 0.00, 0.00, 0.00
-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-08-13  5:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-13  4:58 [gentoo-user] Compression tools Compared Jerry McBride
2005-08-13  5:32 ` Nick Rout [this message]
2005-08-13 13:36   ` Jerry McBride
2005-08-16  5:14     ` Nick Rout
2005-08-16 17:23       ` Matt Randolph
2005-08-16 17:32         ` Matt Randolph
2005-08-17  4:53           ` Matt Randolph
2005-08-17  7:58             ` Neil Bothwick
2005-08-13  5:33 ` Nick Rout
2005-08-13 12:13 ` Fernando Meira
2005-08-13 12:34   ` fire-eyes
2005-08-13 12:44     ` Stephen Micheals
2005-08-13 12:55       ` fire-eyes
2005-08-13 13:56         ` Zac Medico
2005-08-13 14:49 ` Norberto Bensa
2005-08-13 18:00   ` fire-eyes
2005-08-17 14:55 ` Kirk Strauser
2005-08-24 20:13   ` Jerry McBride

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1123911127.28841.10.camel@sf.rout.dyndns.org \
    --to=nick@rout.co.nz \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox