Messages in this thread |  | | Subject | Re: Development Setups | From | Andrew Ebling <> | Date | 05 Oct 2001 18:15:22 +0100 |
| |
> 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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |