public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Ebling <kernelhacker@lineone.net>
To: adam.keys@HOTARD.engr.smu.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Development Setups
Date: 05 Oct 2001 18:15:22 +0100	[thread overview]
Message-ID: <1002302124.1034.5.camel@kernighan> (raw)
In-Reply-To: <20011005041759.OPDP14306.femail26.sdc1.sfba.home.com@there>
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 
> if I oops or somesuch.  Alternately, is there a common practice of using lilo 
> to create development and testing kernel command lines?  Is this a useful 
> thing to do or is it too much of brain drain to switch between hacking and 
> testing mindsets?

I like the two box strategy and have written a detailed description of
how to set it up (right down to the wiring diagram for the serial
cables):

http://www.kernelhacking.org/docs/2boxdebugging.txt

This will become part of the forthcoming kernelhacking-HOWTO...

Feedback on this document from anyone would be very much appreciated
from anyone :)

happy hacking,

Andy



  parent reply	other threads:[~2001-10-05 17:13 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 [this message]
2001-10-06 11:38   ` Adrian Cox
2001-10-13 20:38 ` Tim Moore

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=1002302124.1034.5.camel@kernighan \
    --to=kernelhacker@lineone.net \
    --cc=adam.keys@HOTARD.engr.smu.edu \
    --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