public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Rothwell <rothwell@holly-springs.nc.us>
To: adam.keys@HOTARD.engr.smu.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Development Setups
Date: 05 Oct 2001 00:36:53 -0400	[thread overview]
Message-ID: <1002256614.20235.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20011005041759.OPDP14306.femail26.sdc1.sfba.home.com@there>
In-Reply-To: <20011005041759.OPDP14306.femail26.sdc1.sfba.home.com@there>

On Fri, 2001-10-05 at 00:20, Adam Keys wrote:
> 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.

Here's what each developer was equipped with at my former place of
employment, back when they had money and all:

Two x86 machines, one workstation and one "blow up box".

Console on serial port, minicom logging to a file.

/usr/src on the "blow up box" nfs-mounted from workstation; 100MBit
ethernet

Used kdb sometimes.



  reply	other threads:[~2001-10-05  4:36 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 [this message]
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=1002256614.20235.6.camel@localhost.localdomain \
    --to=rothwell@holly-springs.nc.us \
    --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