From: Jeff Dike <jdike@addtoit.com>
To: steven james <pyro@linuxlabs.com>
Cc: Henrik Nordstrom <hno@marasystems.com>,
linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] uml-patch-2.6.0-test1
Date: Fri, 15 Aug 2003 15:45:01 -0400 [thread overview]
Message-ID: <200308151945.h7FJj1IW003586@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Sun, 27 Jul 2003 15:26:30 EDT." <Pine.LNX.4.21.0307271522230.12132-100000@ucontrol.mobiledns.com>
pyro@linuxlabs.com said:
> I got networking going (at least for the switch daemon) by commenting
> out dev->hard_header = uml_net_hard_header;
I also got rid of the other do-nothing procedures in that chunk of code.
The 2.6 UML will have a working network in the next release.
Jeff
prev parent reply other threads:[~2003-08-15 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 21:48 uml-patch-2.6.0-test1 Jeff Dike
2003-07-26 21:57 ` [uml-devel] uml-patch-2.6.0-test1 Henrik Nordstrom
2003-07-27 0:34 ` Jeff Dike
2003-07-27 19:26 ` steven james
2003-08-15 19:45 ` Jeff Dike [this message]
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=200308151945.h7FJj1IW003586@ccure.karaya.com \
--to=jdike@addtoit.com \
--cc=hno@marasystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pyro@linuxlabs.com \
--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;
as well as URLs for NNTP newsgroup(s).