From: Jesper Juhl <jesper.juhl@gmail.com>
To: Nico Schottelius <nico-kernel@schottelius.org>
Cc: 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:22:22 +0200 [thread overview]
Message-ID: <9a8748490510151322w25063287u567ecb698037fc4d@mail.gmail.com> (raw)
In-Reply-To: <20051015200245.GM12774@schottelius.org>
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. You don't have to build a kernel on the same
machine that is later supposed to run it.
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.
[snip]
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-10-15 20:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 12:21 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 [this message]
2005-10-15 20:38 ` Nico Schottelius
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=9a8748490510151322w25063287u567ecb698037fc4d@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=evil@g-house.de \
--cc=kernel-obri@chaostreff.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-kernel@schottelius.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
all inboxes | Powered by JetHome®