From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel hcking
Date: Fri, 11 Apr 2003 23:08:09 +0200 [thread overview]
Message-ID: <20030411210808.GT5242@lug-owl.de> (raw)
In-Reply-To: <20030411153711.GE25862@wind.cocodriloo.com>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
On Fri, 2003-04-11 17:37:11 +0200, Antonio Vargas <wind@cocodriloo.com>
wrote in message <20030411153711.GE25862@wind.cocodriloo.com>:
> On Fri, Apr 11, 2003 at 04:24:37PM +0100, John Bradford wrote:
> > > Also every time you makes changes in the kernel it must be hell to
> > > recompile the whole thing
> >
> > If you are testing kernels on a separate machine to the one you are
> > compiling on, and therefore not rebooting, it's not much of a problem
> > - with enough RAM, most or all of the kernel source will be cached,
> > and you can compile a kernel in three to five minutes on a fast
> > machine.
>
> John, you mean a "make clean && make bzImage" takes you only about 4
> minutes??? I would like to know more details about .config, machine
> specs, compiler and so on :)
Um, take 1.5GB RAM and one of those dual athlon boards and you'll even
do a full compile in <5min...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-11 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 15:07 kernel hcking Vikram Rangnekar
2003-04-11 15:17 ` Con Kolivas
2003-04-11 15:24 ` John Bradford
2003-04-11 15:37 ` Antonio Vargas
2003-04-11 16:00 ` John Bradford
2003-04-11 21:08 ` Jan-Benedict Glaw [this message]
2003-04-11 15:34 ` Antonio Vargas
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=20030411210808.GT5242@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.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