From: Steven Rostedt <rostedt@goodmis.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
"L. A. Walsh" <lkml@tlinx.org>
Subject: Re: i386 requires x86_64?
Date: Tue, 31 Jan 2006 08:17:33 -0500 [thread overview]
Message-ID: <1138713453.7088.15.camel@localhost.localdomain> (raw)
In-Reply-To: <9a8748490601310054w19e0fa1foc0cb8c65e337aadf@mail.gmail.com>
On Tue, 2006-01-31 at 09:54 +0100, Jesper Juhl wrote:
> On 1/31/06, L. A. Walsh <lkml@tlinx.org> wrote:
> > Generating a new kernel and wanted to delete the unrelated architectures.
> >
>
> Why bother deleting parts of the code?
> The kernel you build will only contain code for the architecture you
> build for anyway. Sure, the extra source takes up a little space on
> disk but if that bothers you you could just delete (or tar+bzip2) the
> entire source tree after you build and install your new kernel.
I still have 1G boxes (and even an 800Meg) HD boxes that I sometimes
develop on. And these things are not very fast either, so doing the tar
bzip2 is also slow. So I have deleted not only archs, but drivers that
I don't need to work on these and to keep the code there.
Now, I mainly do the development on a bigger and faster machine, and
only do the make install via nfs. But that wasn't always an option.
-- Steve
prev parent reply other threads:[~2006-01-31 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 3:10 i386 requires x86_64? L. A. Walsh
2006-01-31 3:31 ` Randy.Dunlap
2006-01-31 13:02 ` Steven Rostedt
2006-02-01 2:56 ` L. A. Walsh
2006-01-31 3:34 ` Nish Aravamudan
2006-01-31 8:54 ` Jesper Juhl
2006-01-31 13:17 ` Steven Rostedt [this message]
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=1138713453.7088.15.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.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;
as well as URLs for NNTP newsgroup(s).