All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: The NeverGone <never@delfin.klte.hu>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: UML (user-mode-linux) kernel-2.6.x
Date: Sun, 11 Jan 2004 14:48:19 -0800	[thread overview]
Message-ID: <4001D2B3.6040702@tupshin.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401112343450.2033@localhost>

The NeverGone wrote:

>On Sun, 11 Jan 2004, Tupshin Harper wrote:
>  
>
>>You didn't answer any of my questions. I'm forced to believe that the
>>guest is either not properly patched, not properly rebuilt, or not
>>actually the version that you're running. Not much I can suggest other
>>than to recheck those things.
>>
>>On the odd chance that 2.6.1-mm2 reintroduces a new version of this
>>problem that the mentioned patch doesn't fix, you could try the host
>>running stock 2.6.1.
>>
>>Also, I inadvertently referred to stock 2.4.23, but of course you would
>>have had to apply a large uml patch to it in order to compile it at all.
>>Did you? If so, which patch, from where?
>>    
>>
>
>Hi...
>
>But everything works on 2.4.24...!
>
>  
>
With host 2.4.24, yes. With host 2.6.x, you NEED to apply the patch to 
the guest. Why is this not clear?

-Tupshin

  reply	other threads:[~2004-01-11 22:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 21:31 UML (user-mode-linux) kernel-2.6.x The NeverGone
2004-01-11 21:56 ` Tupshin Harper
2004-01-11 22:06   ` The NeverGone
2004-01-11 22:10     ` Tupshin Harper
2004-01-11 22:15       ` The NeverGone
2004-01-11 22:33         ` Tupshin Harper
2004-01-11 22:45           ` The NeverGone
2004-01-11 22:48             ` Tupshin Harper [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-11 15:47 The NeverGone
2004-01-11 18:21 ` Tupshin Harper

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=4001D2B3.6040702@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=never@delfin.klte.hu \
    /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.