linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-user@lists.sourceforge.net
Cc: Bernhard Schauer <schauer@acousta.at>,
	user-mode-linux-devel@lists.sourceforge.net,
	Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-user] Re: [uml-devel] Re: Problems about fork-not-clone
Date: Tue, 12 Jul 2005 18:16:49 +0200	[thread overview]
Message-ID: <200507121816.49410.blaisorblade@yahoo.it> (raw)
In-Reply-To: <42D3778A.20703@acousta.at>

On Tuesday 12 July 2005 09:55, Bernhard Schauer wrote:
> Blaisorblade wrote:
> > There's a bit of misunderstanding: SKAS0 is a patch for UML only, not an
> > host patch. It's numbered "0" because it has "0" dependencies, or because
> > it does not depend on host SKAS patch (nor SKAS1, nor SKAS2, nor SKAS3).

> Sorry for that, I should have read about it - especially before writing.

> _IMO:_

> In any case it should be in the kernel mainline, or in other words:

> A mainline kernel should run without any patches required whether SKAS0
> nor reverted fork-not-clone.

> If this specific failure is caught by reverted fork-not-clone patch this
> is THE correction and should also be in mainline kernel.
> If SKAS0 is better than TT mode, TT mode could be replaced with 2.6.14.

Don't worry, I make the same kind of reasoning, so fork-not-clone will be 
reverted for now, until it's made to work on newer systems... and TT mode and 
SKAS0 mode are not incompatible, so SKAS0 will not be dropped so early (for 
now I consider 2.6.14 early, yes).

There were some problems about TT mode which appeared unsolvable on newer 
distros, and that was a reason to drop TT mode, but I just solved them, so 
there's no hurry in dropping it.
-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it



-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2005-07-12 16:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1119527920.4679.15.camel@FC3-bernhard-1.acousta.local>
     [not found] ` <1119614544.4643.9.camel@FC3-bernhard-1.acousta.local>
     [not found]   ` <20050624134118.GA4117@ccure.user-mode-linux.org>
2005-07-04 16:53     ` [uml-devel] Problems about fork-not-clone (was: Re: [uml-user] UML exits after "tracing thread pid") Blaisorblade
2005-07-07 11:59       ` [uml-devel] " Jeff Dike
2005-07-07 18:31         ` Blaisorblade
2005-07-11  7:48         ` Bernhard Schauer
2005-07-11 21:21           ` Blaisorblade
2005-07-12  7:53             ` Rob Landley
2005-07-12  8:04               ` Rob Landley
2005-07-12  9:33                 ` Bernhard Schauer
2005-07-12 15:57                   ` Blaisorblade
2005-07-12 18:54                   ` Rob Landley
2005-07-13 13:36                     ` Blaisorblade
2005-07-12  7:55             ` [uml-devel] Re: Problems about fork-not-clone Bernhard Schauer
2005-07-12 16:16               ` Blaisorblade [this message]
2005-07-15  3:05                 ` [uml-user] " Michael Richardson

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=200507121816.49410.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=schauer@acousta.at \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@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