From: Rui Carmo <rui.carmo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] There is no fork
Date: Tue, 13 Feb 2018 18:21:42 +0000 [thread overview]
Message-ID: <FD69A5A0-5D80-41DF-B702-F71589862C1E@gmail.com> (raw)
In-Reply-To: <20180213181242.GA26808@wopr>
> On 13 Feb 2018, at 18:12, Kurt H Maier <khm@sciops.net> wrote:
>
> On Tue, Feb 13, 2018 at 05:01:35PM +0000, Rui Carmo wrote:
>>
>> A full build environment (the way I’m used to having it) comprises the end-to-end automation for creating a full build,
>
> A full build of what? It's one command to rebuild the whole OS. Is
> that the goal?
Yes. And to deliver an image for the Pi, built on Intel systems.
>> triggered by an external code repository
>
> This pretty significantly reduces the scope of the problem, since only a
> couple of the forks use version control. This simplifies the task
> somewhat, at least.
I struggle to understand how version control is not more actively used.
>> and (when possible) doing automated testing.
>
> I think this is probably the most useful part of what you describe. Do
> you intend to write the tests?
At least the basic ones regarding whether the result boots, yes.
>> I understand that you might be used to manually bootstrap things,
>
> Please don't start making assumptions. I'm just trying to clarify what
> you're after.
>
>> but I tend to go for fully reproducible builds and that usually requires a minimal degree of automation. I did that for my Inferno builds for the Pi (which, alas, are now lost) and do rely on Linux tools for building, because that’s what I can host in the public cloud (which is also what I do for work).
>
> Plenty of us run Plan 9 on public cloud providers. There's even been
> some success on running it with crippled providers like AWS and GCE.
> Obviously, the task is easier when you use providers that offer full KVM
> services. We've had virtio drivers for a while, and it makes the job
> much easier.
Well, for full disclosure, I work at Microsoft. I do have extensive AWS and GCE experience, and hardly find them “crippled”. It’s just that the world has moved on and prioritised certain kinds of hardware virtualisation.
>> Fortunately, I have access to machines with nested virtualisation, so I might be able to get Plan9 running inside QEMU inside a modern Linux kernel with fair performance - but that does not preclude the need to automate things.
>
> I'm still trying to understand why you'd even need nested
> virtualization.
For using QEMU’s virtualization features inside Hyper-V.
R.
next prev parent reply other threads:[~2018-02-13 18:21 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 23:48 sl
2018-02-13 3:06 ` Lucio De Re
2018-02-13 9:31 ` Rui Carmo
2018-02-13 10:43 ` Lucio De Re
2018-02-13 11:05 ` hiro
2018-02-13 11:07 ` hiro
2018-02-13 11:13 ` hiro
2018-02-13 13:45 ` Lucio De Re
2018-02-13 14:35 ` hiro
2018-02-13 16:09 ` Lucio De Re
2018-02-13 15:10 ` Rui Carmo
2018-02-13 15:22 ` Lucio De Re
2018-02-13 16:25 ` Kurt H Maier
2018-02-13 17:01 ` Rui Carmo
2018-02-13 18:12 ` Kurt H Maier
2018-02-13 18:21 ` Rui Carmo [this message]
2018-02-13 19:10 ` Kurt H Maier
2018-02-13 23:37 ` Rui Carmo
2018-02-14 9:09 ` Steve Simon
2018-02-14 11:10 ` Lucio De Re
2018-02-14 11:32 ` hiro
2018-02-14 13:53 ` Ethan Grammatikidis
2018-02-13 19:14 ` hiro
2018-02-13 18:16 ` Steve Simon
2018-02-13 18:46 ` Bakul Shah
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 14:37 sl
2018-02-14 0:31 sl
2018-02-14 7:18 ` Rui Carmo
2018-02-13 14:15 sl
2018-02-10 2:48 Benjamin Huntsman
2018-02-10 4:24 ` Lucio De Re
2018-02-10 10:43 ` Ethan Grammatikidis
2018-02-10 4:43 ` Jens Staal
2018-02-10 10:46 ` hiro
2018-02-10 10:51 ` Ethan Grammatikidis
2018-02-10 11:59 ` hiro
2018-02-10 14:54 ` Ethan Grammatikidis
2018-02-10 12:03 ` as
2018-02-11 12:26 ` Giacomo Tesio
2018-02-11 13:48 ` Rui Carmo
2018-02-11 22:40 ` Lyndon Nerenberg
2018-02-11 23:48 ` Benjamin Huntsman
2018-02-12 0:20 ` Giacomo Tesio
2018-02-12 0:58 ` Benjamin Huntsman
2018-02-12 1:10 ` Ethan Grammatikidis
2018-02-12 8:33 ` Giacomo Tesio
2018-02-12 13:05 ` Ethan Grammatikidis
2018-02-12 13:39 ` Lucio De Re
2018-02-13 13:59 ` Ethan Grammatikidis
2018-02-12 15:21 ` Giacomo Tesio
2018-02-12 15:50 ` Chris McGee
2018-02-12 16:13 ` tlaronde
2018-02-12 18:51 ` Steve Simon
2018-02-12 20:40 ` Giacomo Tesio
2018-02-12 23:49 ` Benjamin Huntsman
2018-02-14 13:17 ` Ethan Grammatikidis
2018-02-14 13:57 ` Erik Quanstrom
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=FD69A5A0-5D80-41DF-B702-F71589862C1E@gmail.com \
--to=rui.carmo@gmail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).