public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@list.ru>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Mateusz Viste <mateusz@viste-family.net>,
	linux-msdos@vger.kernel.org,
	dosemu-devel <dosemu-devel@lists.sourceforge.net>
Subject: Re: DOSemu networking made easy
Date: Tue, 25 Jun 2013 00:42:15 +0400	[thread overview]
Message-ID: <51C8AF27.4060002@list.ru> (raw)
In-Reply-To: <87sj07i8lv.fsf@xmission.com>

24.06.2013 23:58, Eric W. Biederman пишет:
> Stas Sergeev <stsp@list.ru> writes:
>
>> Aha, thanks for an explanation!
>> Now I've started to understand what is this all about. :)
>> Lets add dosemu-devel and Eric Biederman into CC.
>> The beginning is here:
>> http://marc.info/?l=linux-msdos&m=137207433306065&w=2
> I can see the appeal, of unprivileged NAT.
>
> I don't think I have run any network facing applications in DOS.
>
> Does the slirp code make any pretense of supporting IPv6?  Or is it the
> same code I used in college  20 years ago?
You mean proxying the dosemu's IPv4 packets
by the use of IPv6? May be interesting for the
future, but IMHO IPv4 is not going to disappear
any time soon so why do we care at that stage.

My concern is also why there is no slirp packages
in most distros including fedora it seems. Very
few mentioning in google, not to say no docs -
pure nothing, or at least nothing googlable.
Last release like 10 years ago etc... This makes
me really sceptical, may became a maintenance burden.
But, as long as it works...
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-06-24 20:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 11:36 DOSemu networking made easy Mateusz Viste
2013-06-24 13:23 ` Stas Sergeev
2013-06-24 13:50   ` Mateusz Viste
2013-06-24 15:00     ` Stas Sergeev
2013-06-24 15:38       ` Mateusz Viste
2013-06-24 16:12         ` Stas Sergeev
2013-06-24 19:58           ` Eric W. Biederman
2013-06-24 20:42             ` Stas Sergeev [this message]
2013-06-24 22:04               ` Mateusz Viste
2013-06-25  7:03                 ` Stas Sergeev
2013-06-25  7:33                   ` Mateusz Viste
2013-06-25  8:27                     ` Eric W. Biederman
     [not found]                       ` <87zjue8ujo.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2013-06-25 11:43                         ` Stas Sergeev
2013-06-25  9:48                     ` Stas Sergeev
2013-06-25 11:16                       ` Eric W. Biederman
2013-06-25 13:30                       ` Mateusz Viste
2013-06-24 21:47             ` Mateusz Viste
2013-06-24 23:43               ` Eric W. Biederman
2013-06-25  6:49                 ` Mateusz Viste
     [not found]                   ` <8fbd00db-16cc-4fd2-8135-0c3c99fcc3a6-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2013-06-25  7:47                     ` Eric W. Biederman
2013-06-25  7:13                 ` Stas Sergeev
2013-06-25  7:57                   ` Eric W. Biederman
2013-06-25  9:45                     ` Stas Sergeev
2013-06-24 14:40   ` Mateusz Viste

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=51C8AF27.4060002@list.ru \
    --to=stsp@list.ru \
    --cc=dosemu-devel@lists.sourceforge.net \
    --cc=ebiederm@xmission.com \
    --cc=linux-msdos@vger.kernel.org \
    --cc=mateusz@viste-family.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