From: Johannes Stezenbach <js@linuxtv.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Dax Kelson <dax@gurulabs.com>,
Linux kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Smaller compressed kernel source tarballs?
Date: Fri, 22 Sep 2006 19:41:37 +0200 [thread overview]
Message-ID: <20060922174137.GA29929@linuxtv.org> (raw)
In-Reply-To: <4514103D.8010303@zytor.com>
On Fri, Sep 22, 2006 at 09:33:01AM -0700, H. Peter Anvin wrote:
> Jan Engelhardt wrote:
> >>>widely used until there is an "lzip" which does the same thing. I
> >>>actually started the work of adding LZMA support to gzip, but then
> >>>realized it would be better if a new encapsulation format with proper
> >>>64-bit support everywhere was created.
> >>It doesn't handle streaming?
> >>
> >>So you can't do: tar c dirname | 7zip dirname.tar.7z ?
> >
> >man 7z [slightly changed for reasonability]:
> >
> > -si
> > Read data from StdIn (eg: tar -c directory | 7z a -si
> > directory.tar.7z)
> >
>
> Yes, but you can't make it write to an unseekable stdout.
It seems the "lzma" program from LZMA Utils can:
http://tukaani.org/lzma/
"Very similar command line interface than what gzip and bzip2 have."
(Debian sid has this in the "lzma" package.)
Johannes
next prev parent reply other threads:[~2006-09-22 17:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 20:32 Smaller compressed kernel source tarballs? Dax Kelson
[not found] ` <20060921204250 .GN13641@csclub.uwaterloo.ca>
2006-09-21 20:42 ` Lennart Sorensen
2006-09-21 21:17 ` Sean
2006-09-21 21:17 ` Sean
2006-09-21 21:41 ` Dax Kelson
2006-09-21 21:50 ` Bob Copeland
2006-09-21 21:57 ` Sean
2006-09-21 21:57 ` Sean
2006-09-21 22:00 ` David Lang
2006-09-21 22:24 ` Dave Jones
2006-09-21 22:16 ` David Lang
2006-09-21 22:40 ` Dave Jones
2006-09-21 22:34 ` David Lang
2006-09-21 23:38 ` Sean
2006-09-21 23:38 ` Sean
[not found] ` <Pin e.LNX.4.63.0609211455570.17238@qynat.qvtvafvgr.pbz>
2006-09-21 22:25 ` Sean
2006-09-21 22:25 ` Sean
2006-09-21 22:20 ` David Lang
2006-09-21 21:40 ` Dax Kelson
2006-09-22 14:00 ` Lennart Sorensen
2006-09-21 21:43 ` H. Peter Anvin
2006-09-22 14:00 ` Lennart Sorensen
2006-09-22 16:13 ` H. Peter Anvin
2006-09-22 16:13 ` Jan Engelhardt
2006-09-22 16:33 ` H. Peter Anvin
2006-09-22 17:41 ` Johannes Stezenbach [this message]
2006-09-22 18:09 ` H. Peter Anvin
2006-09-22 18:19 ` Michael Tokarev
2006-09-22 18:26 ` H. Peter Anvin
2006-09-25 11:51 ` Paulo Marques
2006-09-25 15:47 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2006-10-02 3:35 Drew Scott Daniels
2006-10-02 3:32 ` Bernd Eckenfels
2006-10-02 3:35 ` Willy Tarreau
[not found] ` <Pi ne.LNX.4.63.0610012205280.28534@qynat.qvtvafvgr.pbz>
2006-10-02 5:11 ` David Lang
2006-10-02 5:49 ` Willy Tarreau
2006-10-02 15:16 ` Phillip Susi
2006-10-02 15:48 ` David Lang
2006-10-02 20:20 ` Phillip Susi
2006-10-02 20:12 ` David Lang
2006-10-02 20:35 ` Willy Tarreau
[not found] ` <2006 1002203527.GA585@1wt.eu>
2006-10-02 21:49 ` Sean
2006-10-02 21:49 ` Sean
2006-10-02 21:42 ` David Lang
2006-10-03 2:48 ` Willy Tarreau
2006-10-03 10:28 ` Jan Engelhardt
2006-10-03 18:24 ` Phillip Susi
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=20060922174137.GA29929@linuxtv.org \
--to=js@linuxtv.org \
--cc=dax@gurulabs.com \
--cc=hpa@zytor.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.