From: Gerd Knorr <kraxel@bytesex.org>
To: Steve Schmidtke <steve_schmidtke@hotmail.com>
Cc: User-mode-linux-devel@lists.sourceforge.net, uml@uxu.ch
Subject: [uml-devel] Re: [PATCH] uml_router: cleanup #2
Date: Tue, 30 Nov 2004 11:32:55 +0100 [thread overview]
Message-ID: <20041130103255.GB5593@bytesex> (raw)
In-Reply-To: <BAY24-F18CD7435AB94FE5A10013283BE0@phx.gbl>
> Patch 11 turns on the packet queue for the tuntap driver. For technical
> reasons, it's just too much work to implement on the current sockunix
> driver.
Guess thats the "one socket for all umls" thingy? You can create a new
socket for every uml instance connecting, at least with protocol v3 (not
sure about the older ones, but I think support for them can be dropped
without breaking anything by now ...).
> Patch 14 is a fun little UDP packet driver inspired by Felix M?ri for
> connecting multiple UMLs together. It's inherently unsecure so you must
> uncomment the driver in the makefile if you want to play with it.
Why this? Compile time options are evil. Runtime option which is off
by default is perfectly fine IMHO.
Gerd
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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-11-30 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 5:11 [uml-devel] [PATCH] uml_router: cleanup #2 Steve Schmidtke
2004-11-30 10:32 ` Gerd Knorr [this message]
2004-11-30 13:27 ` [uml-devel] " Blaisorblade
2004-11-30 17:51 ` Steve Schmidtke
2004-11-30 17:44 ` Steve Schmidtke
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=20041130103255.GB5593@bytesex \
--to=kraxel@bytesex.org \
--cc=User-mode-linux-devel@lists.sourceforge.net \
--cc=steve_schmidtke@hotmail.com \
--cc=uml@uxu.ch \
/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.