From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 13 Feb 2018 10:12:42 -0800 From: Kurt H Maier To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20180213181242.GA26808@wopr> References: <20180213162522.GB15332@wopr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] There is no fork Topicbox-Message-UUID: cfaa5c88-ead9-11e9-9d60-3106f5b1d025 On Tue, Feb 13, 2018 at 05:01:35PM +0000, Rui Carmo wrote: >=20 > A full build environment (the way I=E2=80=99m used to having it) compri= ses 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? > triggered by an external code repository=20 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. > 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? > I understand that you might be used to manually bootstrap things,=20 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=E2=80=99s 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.=20 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. > Fortunately, I have access to machines with nested virtualisation, so I= might be able to get Plan9 running inside QEMU inside a modern Linux ker= nel with fair performance - but that does not preclude the need to automa= te things. I'm still trying to understand why you'd even need nested virtualization. khm