From: Adam Keys <adam.keys@engr.smu.edu>
To: linux-kernel@vger.kernel.org
Subject: Development Setups
Date: Thu, 4 Oct 2001 23:20:06 -0500 [thread overview]
Message-ID: <20011005041759.OPDP14306.femail26.sdc1.sfba.home.com@there> (raw)
As a budding kernel hacker looking to cut my teeth, I've become curious about
what types of setups people hack the kernel with. I am very interested in
descriptions of the computers you hack the kernel with and their use patterns.
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?
Instead of having separate machines, there is the possibility of using the
Usermode port. As I understand it this lags behind the -ac and linus kernels
so it would be hard to test things like the new VM's. Usermode would not be
suitable for driver development either. Again, thoughts on this mode of
development?
Which brings me to the final question. Is there any reason to choose
architecture A over architecture B for any reason besides arch-specific
development in the kernel or for device drivers?
AKK
--
Adam K. Keys
<adam.keys@HOTARD.engr.smu.edu> (Remove the HOTARD to email me)
next reply other threads:[~2001-10-05 4:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 4:20 Adam Keys [this message]
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
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=20011005041759.OPDP14306.femail26.sdc1.sfba.home.com@there \
--to=adam.keys@engr.smu.edu \
--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
all inboxes | Powered by JetHome®