From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Subject:
 Re: [PATCH 0/8] Allow pasta to take a command to spawn instead of shell
Date: Thu, 01 Sep 2022 12:07:25 +0200
Message-ID: <20220901120725.0cf0f0d4@elisabeth>
In-Reply-To: <20220826045839.1112152-1-david@gibson.dropbear.id.au>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0904830095714664584=="

--===============0904830095714664584==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Fri, 26 Aug 2022 14:58:31 +1000
David Gibson <david(a)gibson.dropbear.id.au> wrote:

> When not attaching to an existing network namespace, pasta always
> spawns an interactive shell in a new namespace to attach to.  Most
> commands which can issue a shell in a modified environment can also
> issue other commands as well (e.g. env, strace).  We want to allow
> pasta to do the same.
> 
> Because of the way the non-option argument to pasta is currently
> overloaded, allowing this requires some other changes to the way we
> parse the command line.
> 
> David Gibson (8):
>   conf: Make the argument to --pcap option mandatory
>   conf: Use "-D none" and "-S none" instead of missing empty option
>     arguments
>   Correct manpage for --userns
>   Remove --nsrun-dir option
>   Move ENOENT error message into conf_ns_opt()
>   More deterministic detection of whether argument is a PID, PATH or
>     NAME
>   Use explicit --netns option rather than multiplexing with PID
>   Allow pasta to take a command to execute

Applied now with those small changes, thanks a lot.

-- 
Stefano


--===============0904830095714664584==--