All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Lee <nj.lee@plumtree.co.nz>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] [alydar@users.sourceforge.net: Re: user-mode-linux: upgrade hangs at "NET4: Linux TCP/IP 1.0 for NET4.0"]
Date: Mon, 19 Jul 2004 17:05:19 +1200	[thread overview]
Message-ID: <20040719050519.GE23215@stateless> (raw)

----- Forwarded message from Allen Chan <alydar@users.sourceforge.net> -----

From: Allen Chan <alydar@users.sourceforge.net>
To: 260111@bugs.debian.org
Subject: Re: user-mode-linux: upgrade hangs at "NET4: Linux TCP/IP 1.0 for NET4.0"
Date: Mon, 19 Jul 2004 00:20:59 -0400
Cc: nic@plumtree.co.nz

Confirming results from Nicolas Lee, the same 2.4.26-2um-1 guest 
kernel that failed earlier with the 2.6.6-1-k7 host kernel with the 
skas3 patch now works if the output from the command line is piped to 
"tee".

This guest kernel also appears to work if on the command line, the 
stdout is redirected to a file, or if it is piped to anything that 
does not require additional user interaction (i.e., piping to "cat" 
works, but piping to "more" caused some other, probably unrelated, 
problems).


----- End forwarded message -----


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
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:[~2004-07-19  5:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040719050519.GE23215@stateless \
    --to=nj.lee@plumtree.co.nz \
    --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 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.