Re: Running Xen rumprun unikernels non-interactively (eg. piping rumprun -i to logger or systemd)
- From: Antti Kantee <pooka@xxxxxx>
- To: Anil Madhavapeddy <anil@xxxxxxxxxx>, rumpkernel-users <rumpkernel-users@xxxxxxxxxxxxx>, David Scott <Dave.Scott@xxxxxxxxxx>, Richard Mortier <richard.mortier@xxxxxxxxxxxx>, Thomas Gazagnaire <thomas.gazagnaire@xxxxxxxxxxxx>, "Magnus Skjegstad (University of Cambridge)" <magnus.skjegstad@xxxxxxxxxxxx>
- Date: Thu, 06 Aug 2015 18:23:27 +0000
On 06/08/15 15:35, Martin Lucina wrote:
That said, I wonder if -i should not be called -i. Enabling the use of
interactive mode non-interactively is, um, weird ;)
That is a little odd. Something like "-n" would be closer to what the ssh
Well, the "-i" was inspired by "docker run -i" when I wrote the rumprun
script. I guess we could implement a "-n" which, at present, would do
exactly the same thing, just be documented differently. Not sure if it's
Well, well, welcome back to development ;)
IMHO, non-i is a poor default. It assumes a preference towards script
writers and launch tools instead of those doing interactive development.
I'd think people writing scripts can type the -n once. I'm not sure
why I have to type it every time on the command line.
Admittedly, I haven't played enough with docker to know for sure, but my
impression is that you start the guest, then log into it to do things.
Assuming the previous is true, I'm not convinced that the docker default
mode is applicable for us.
We definitely won't implement two options. We figure out the
perceivably correct option, and go with it. The worst kind of software
results from using switches and toggles as a substitute for development
time decision making. That said, both -i & -n would be impossible
anyway they require different defaults.
Other related posts: