From: Chris Wedgwood <cw@f00f.org>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Re: Why UML often does not build (was: Re: [PATCH] UML: Build fix for TT w/o SKAS)
Date: Thu, 28 Oct 2004 17:28:31 -0700 [thread overview]
Message-ID: <20041029002831.GD12434@taniwha.stupidest.org> (raw)
In-Reply-To: <200410290149.31665.blaisorblade_spam@yahoo.it>
On Fri, Oct 29, 2004 at 01:49:31AM +0200, Blaisorblade wrote:
> Yes, it was using SIGKILL instead of PTRACE_KILL; this gets broken
> by 2.6.9.
the problem here is that ptrace semantics are not well defined to
anything subtle can and will break from time to time
if we can get UML in a more suitable state and perhaps get some minor
QA stuff merged (a new make target using initramfs maybe?) we could
'encourage' people to test UML more often
> Well, I've seen Christoph Hellwig not particularly happy about us,
> see for instance:
>
> http://linux.bkbits.net:8080/linux-2.5/cset@41752cc9xdFXib-03VDV5akqKJZ-yA?nav=index.html|ChangeSet@-7d
well, he is right in this case
it's hard to find a balance between keeping it working for existing
UML users (which is what i'm trying to make sure is the case) and
doing cleanups which people such as hch point out really are needed
> Sending a patch requires at least proof-reading it and writing a
> meaningful changelog. Also, managing mails takes tons of time.
im happy to take any and all fixes w/o comments in any form for now if
you want to fire them off to me
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-10-29 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041027053602.GB30735@taniwha.stupidest.org>
[not found] ` <200410282104.30482.blaisorblade_spam@yahoo.it>
[not found] ` <20041028193329.GF851@taniwha.stupidest.org>
2004-10-28 20:54 ` [uml-devel] Why UML often does not build (was: Re: [PATCH] UML: Build fix for TT w/o SKAS) Blaisorblade
2004-10-28 21:42 ` [uml-devel] " Chris Wedgwood
2004-10-28 23:49 ` Blaisorblade
2004-10-29 0:28 ` Chris Wedgwood [this message]
2004-10-29 6:44 ` Werner Almesberger
2004-10-29 14:53 ` Blaisorblade
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=20041029002831.GD12434@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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