From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) From: Rui Carmo In-Reply-To: <20180213162522.GB15332@wopr> Date: Tue, 13 Feb 2018 17:01:35 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180213162522.GB15332@wopr> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] There is no fork Topicbox-Message-UUID: cfa627c6-ead9-11e9-9d60-3106f5b1d025 > On 13 Feb 2018, at 16:25, Kurt H Maier wrote: >=20 > On Tue, Feb 13, 2018 at 03:10:34PM +0000, Rui Carmo wrote: >>=20 >> The main issue for me is putting together a build environment on top = of KVM or Linux, which isn=E2=80=99t covered in the FQA. >>=20 >=20 > What is a "build environment"? The FQA contains an entire chapter > (3.3.1) on installing to qemu on linux. If a complete installation is > not sufficeint to create a "build environment," can you help us > understand what is missing? A full build environment (the way I=E2=80=99m used to having it) = comprises the end-to-end automation for creating a full build, triggered = by an external code repository and (when possible) doing automated = testing. I understand that you might be used to manually bootstrap things, 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). 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. R.=