From: jlnance@unity.ncsu.edu
To: Jeff Dike <jdike@karaya.com>, linux-kernel@vger.kernel.org
Subject: Re: uml-patch-2.5.49-1
Date: Tue, 26 Nov 2002 09:14:09 -0500 [thread overview]
Message-ID: <20021126141409.GA4589@ncsu.edu> (raw)
In-Reply-To: <200211260517.AAA05038@ccure.karaya.com>
Hi Jeff,
Sounds like you are doing some good things with UML. I particularly
like the fact that gdb will be easier to use.
On Tue, Nov 26, 2002 at 12:17:07AM -0500, Jeff Dike wrote:
> I welcome any comments on it. The /proc/mm write semantics are less than
> ideal - I especially would like suggestions for improvements.
I think /proc/mm would be better implemented as /dev/mm. It seems to
have a lot more functionality associated with it than most /proc files.
Thanks,
Jim
next prev parent reply other threads:[~2002-11-26 14:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 5:17 uml-patch-2.5.49-1 Jeff Dike
2002-11-26 14:14 ` jlnance [this message]
2002-11-26 18:33 ` uml-patch-2.5.49-1 Jeff Dike
2002-11-27 2:29 ` uml-patch-2.5.49-1 H. Peter Anvin
2002-11-27 4:06 ` uml-patch-2.5.49-1 Jeff Dike
2002-11-27 4:30 ` uml-patch-2.5.49-1 H. Peter Anvin
2002-11-27 5:08 ` uml-patch-2.5.49-1 Jeff Dike
[not found] <200211260517.AAA05038@ccure.karaya.com.suse.lists.linux.kernel>
2002-11-26 5:57 ` uml-patch-2.5.49-1 Andi Kleen
2002-11-26 6:07 ` uml-patch-2.5.49-1 Patrick Finnegan
2002-11-26 6:10 ` uml-patch-2.5.49-1 Andi Kleen
2002-11-26 7:02 ` uml-patch-2.5.49-1 Patrick Finnegan
2002-11-26 16:45 ` uml-patch-2.5.49-1 Rik van Riel
2002-11-26 18:29 ` uml-patch-2.5.49-1 Jeff Dike
2002-11-26 19:37 ` uml-patch-2.5.49-1 Andreas Dilger
2002-11-26 21:07 ` uml-patch-2.5.49-1 Jeff Dike
[not found] <20021126061021.GA17959@wotan.suse.de.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.44.0211260159440.7540-100000@ibm-ps850.purdueriots.com.suse.lists.linux.kernel>
2002-11-26 7:08 ` uml-patch-2.5.49-1 Andi Kleen
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=20021126141409.GA4589@ncsu.edu \
--to=jlnance@unity.ncsu.edu \
--cc=jdike@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.