public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel@schottelius.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Nico Schottelius <nico-kernel@schottelius.org>,
	Christian Kujau <evil@g-house.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Daniel Aubry <kernel-obri@chaostreff.ch>
Subject: Re: Some problems with 2.6.13.4
Date: Sat, 15 Oct 2005 22:38:24 +0200	[thread overview]
Message-ID: <20051015203824.GN12774@schottelius.org> (raw)
In-Reply-To: <9a8748490510151322w25063287u567ecb698037fc4d@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]

Jesper Juhl [Sat, Oct 15, 2005 at 10:22:22PM +0200]:
> On 10/15/05, Nico Schottelius <nico-kernel@schottelius.org> wrote:
> [snip]
> > Could we somehow debug this differently or do I have to install
> > 2.6.13.2 and 2.6.13.1, too? It would take simply hours until it is
> > finished here.
> >
> 
> If you have another, faster, machine available you could build the
> kernel(s) on that one.


Actually, one of my fastest machines is this one:

bruehe2# cat /proc/cpuinfo 
[...]
model name      : Pentium III (Katmai)
cpu MHz         : 551.280
[...]

And one, which has a not-so-good connection to me.

> You don't have to build a kernel on the same
> machine that is later supposed to run it.

That's clear :-)

> Also, if you have more than one machine (even if they are not
> especially fast) then you can use distcc (http://distcc.samba.org/) to
> distribute the build over multiple machines which can speed up a build
> a great deal.

distcc will fail here, because of different gccs and different distributions
(ever tried to use gentoo and distcc in the same distcc-network? It's a real
pain).

Thanks for the hints anyway,

Nico

-- 
Latest project: cconfig (http://nico.schotteli.us/papers/linux/cconfig/)
Open Source nutures open minds and free, creative developers.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2005-10-15 20:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 12:21 Some problems with 2.6.13.4 Nico Schottelius
2005-10-15 15:05 ` Christian Kujau
2005-10-15 15:40   ` Nico Schottelius
2005-10-15 20:02     ` Nico Schottelius
2005-10-15 20:22       ` Jesper Juhl
2005-10-15 20:38         ` Nico Schottelius [this message]
2005-10-15 21:03           ` Paolo Ornati
2005-10-24 16:27           ` Kalin KOZHUHAROV
2005-10-16 11:19       ` Nico Schottelius

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=20051015203824.GN12774@schottelius.org \
    --to=nico-kernel@schottelius.org \
    --cc=evil@g-house.de \
    --cc=jesper.juhl@gmail.com \
    --cc=kernel-obri@chaostreff.ch \
    --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