From: Tim Moore <timothymoore@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Development Setups
Date: Sat, 13 Oct 2001 13:38:53 -0700 [thread overview]
Message-ID: <3BC8A65D.246AAC0B@bigfoot.com> (raw)
In-Reply-To: <20011005041759.OPDP14306.femail26.sdc1.sfba.home.com@there>
> I was thinking of starting with a modern machine for developing/compiling on,
> and then older machine(s) for testing. This way I would not risk losing data
I use the 'fast/slow' model for app server development. The fastest
machine is used to build kernels for the slower test machine(s)
regardless of architecture or latest/greatest hardware. Most results
can be scaled once you understand interactions. NFS w no_root_squash is
useful provided a secure LAN.
rgds,
tim.
--
prev parent reply other threads:[~2001-10-13 20:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 4:20 Development Setups Adam Keys
2001-10-05 4:36 ` Michael Rothwell
2001-10-05 8:02 ` David Woodhouse
2001-10-06 0:27 ` journaling and devel [was Re: Development Setups] Pavel Machek
2001-10-13 20:30 ` Steve Lord
2001-10-05 9:50 ` Development Setups Riley Williams
2001-10-05 11:22 ` Alan Cox
2001-10-05 14:53 ` Jeff Dike
2001-10-05 17:15 ` Andrew Ebling
2001-10-06 11:38 ` Adrian Cox
2001-10-13 20:38 ` Tim Moore [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=3BC8A65D.246AAC0B@bigfoot.com \
--to=timothymoore@bigfoot.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.