From: "Tiwei Bie" <tiwei.btw@antgroup.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: richard@nod.at, anton.ivanov@cambridgegreys.com,
johannes@sipsolutions.net, linux-um@lists.infradead.org
Subject: Re: [PATCH 0/3] um: Remove legacy network transport support
Date: Mon, 05 May 2025 22:03:48 +0800 [thread overview]
Message-ID: <bfa07f4d-16a3-476b-9314-b8052ec198b1@antgroup.com> (raw)
In-Reply-To: <CAMuHMdUhWUhHczDG4ihB0cgUG9TTMo6Naszw6oogROnRCrOmKA@mail.gmail.com>
Hi Geert,
On 2025/5/5 17:20, Geert Uytterhoeven wrote:
> Hi Tiwei,
>
> On Sat, 3 May 2025 at 07:17, Tiwei Bie <tiwei.btw@antgroup.com> wrote:
>> Tiwei Bie (3):
>> um: Remove obsolete legacy network transports
>> um: vector: Eliminate the dependency on uml_net
>> um: Remove legacy network transport infrastructure
>
> Thanks for your series!
>
>> arch/um/drivers/slirp_kern.c | 120 ---
>> arch/um/drivers/slirp_user.c | 124 ---
>
> It's been a while I used UML, but slirp is what allowed me to run
> UML on a machine at work where I only had normal user access, and do
> root-only things like running Wireshark (then called Ethereal ;-), and
> install and run apps that were not available on the physical machine.
> Do the newer networking options support using networking on a machine
> where you do not have root access?
Yeah, transport like vde supports using networking without root access:
(on host) $ ./linux vec0:transport=vde,vnl=slirp:// ...
(in uml) $ dhclient vec0
PS. I set up vde by installing vdeplug and libvdeplug-slirp on debian 12.
Regards,
Tiwei
>
> Gr{oetje,eeting}s,
>
> Geert
>
prev parent reply other threads:[~2025-05-05 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 5:17 [PATCH 0/3] um: Remove legacy network transport support Tiwei Bie
2025-05-03 5:17 ` [PATCH 1/3] um: Remove obsolete legacy network transports Tiwei Bie
2025-05-03 13:25 ` Anton Ivanov
2025-05-03 5:17 ` [PATCH 2/3] um: vector: Eliminate the dependency on uml_net Tiwei Bie
2025-05-03 13:26 ` Anton Ivanov
2025-05-05 9:12 ` Geert Uytterhoeven
2025-05-05 13:56 ` Tiwei Bie
2025-05-03 5:17 ` [PATCH 3/3] um: Remove legacy network transport infrastructure Tiwei Bie
2025-05-03 13:26 ` Anton Ivanov
2025-05-05 9:20 ` [PATCH 0/3] um: Remove legacy network transport support Geert Uytterhoeven
2025-05-05 14:03 ` Tiwei Bie [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=bfa07f4d-16a3-476b-9314-b8052ec198b1@antgroup.com \
--to=tiwei.btw@antgroup.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=geert@linux-m68k.org \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).