From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <55C3BBA4253327283CC4441E39D17C19@5ess.inri.net>
Date: Tue, 13 Feb 2018 19:31:42 -0500
From: sl@9front.org
To: 9fans@9fans.net
In-Reply-To: A7E3F87F-1271-4A69-BEC9-3C333B1C0579@gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] There is no fork
Topicbox-Message-UUID: d0044e6e-ead9-11e9-9d60-3106f5b1d025

>> Rui, please present any issues you had with the step-by-step
>> introductions in the fqa to us on the 9front mailinglist in a
>> designated thread.
>=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
> I can=E2=80=99t build 9front on a Pi (well, not in productive amounts o=
f
> time), and all the machines i have available with the requisite
> horsepower are in the public cloud (except for my iMac and a local KVM
> host that is already overburdened with my Windows development VM).
>=20
> Since I=E2=80=99m a staunch supporter of CI/CD I=E2=80=99d love to auto=
mate the
> process from committing code to building a burnable image, and dipping
> into 9front from =E2=80=9Coutside=E2=80=9D to run the requisite command=
s is going to
> be a time sink.

It sounds like you are saying you want to 1.) build Plan 9 on Linux,
using Linux tools, 2.) and test it by running the result in
QEMU/KVM/whatever hosted by Linux.

1.) is the wrong approach.  Just build inside Plan 9.

2.) is trivial and is covered in FQA3[0] and FQA5[1].  9front's fork
of drawterm[2] can run without graphics, and can be used to execute
single commands.

If this is really your aim, I think you can accomplish it with minimal
stress.

sl

[0] http://fqa.9front.org/fqa3.html

[1] http://fqa.9front.org/fqa5.html

[2] http://drawterm.9front.org