From: Steven Hanley <sjh@wibble.net>
To: Gabriel Paubert <paubert@iram.es>,
Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: problem with compressing the kernel
Date: Wed, 28 Jun 2000 22:43:15 +1000 [thread overview]
Message-ID: <3959F2E3.5361A5D9@wibble.net> (raw)
In-Reply-To: Pine.HPX.4.10.10006281352560.5670-100000@gra-ux1.iram.es
> Not in the compilation, but since when do you use
> cvs/rsync/bitkeeper/whatever ?
cvs since Tridge showed it to me a few years ago and how to use it well,
thus I used to get kernel source from samba.anu.edu.au's cvs tree often
(depending on what was using said source for), as for rsync, since I
started using ppc as Paul keeps his kernels on linuxcare.com.au
available over rsync. Anyway I was just using them as current examples
where gzip and bzip2 are not required, just as you used the fact
generally kernel's are obtained in tar.{gz,bz2} format as an argument
for needing the appropriate tool. I still would say the Changes file is
not out of date or anythng (as you previously suggested) as there is no
requirement for gzip or bzip2 to build the kernel from source, this is
what the file claims to cover. However this is just being picky.
> The official source tree (the mirrors of ftp.kernel.org) is still only
> available as gz and more recently with bz2. So historically gzip has been
> a prerequisite to look at the kernel source and build your kernel, that's
> all what I claimed (did you use Linux and build your kernels from
> ftp.funet.fi in 1995 ?).
well until recently I only had x86 boxes, but admittedly the argument is
academic as you wont find a linux box on which you compile kernels (ie
not some small embedded system, etc etc) without gzip installed.
--
sjh@wibble.net http://wibble.net/~sjh/
Look Up In The Sky
Is it a bird? No
Is it a plane? No
Is it a small blue banana?
YES
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-28 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 3:49 problem with compressing the kernel Rolf Liu
2000-06-28 6:19 ` Steven Hanley
2000-06-28 7:33 ` Wolfgang Denk
2000-06-28 7:55 ` Gregorio Gervasio Jr.
2000-06-28 9:05 ` Gabriel Paubert
2000-06-28 11:45 ` Steven Hanley
2000-06-28 12:27 ` Gabriel Paubert
2000-06-28 12:43 ` Steven Hanley [this message]
2000-06-28 12:41 ` Wolfgang Denk
2000-06-28 12:18 ` Tony Mantler
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=3959F2E3.5361A5D9@wibble.net \
--to=sjh@wibble.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
/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;
as well as URLs for NNTP newsgroup(s).