From: Jeff Dike <jdike@karaya.com>
To: adam.keys@HOTARD.engr.smu.edu.karaya.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Development Setups
Date: Fri, 05 Oct 2001 09:53:13 -0500 [thread overview]
Message-ID: <200110051453.JAA01618@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Thu, 04 Oct 2001 23:20:06 EST." <20011005041759.OPDP14306.femail26.sdc1.sfba.home.com@there>
adam.keys@engr.smu.edu said:
> 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.
Not really. The latest UML is sometimes pretty far ahead of what's in the
-ac tree, but it usually works fine. So, if you're interested in the generic
kernel, and not UML itself, that shouldn't be a problem. And currently,
the -ac tree is pretty close to my CVS.
Also, the latest patches usually go pretty cleanly into the -linus pre kernels,
so getting those running in UML shouldn't be hard.
> Usermode would not be suitable for driver development either.
This is just because no one has written the code to do it. It is perfectly
possible to do hardware device driver development in UML. Various USB people
have started trying to do USB driver development under UML, for example.
Jeff
next prev parent reply other threads:[~2001-10-05 13:35 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 [this message]
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=200110051453.JAA01618@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=adam.keys@HOTARD.engr.smu.edu.karaya.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox