From: sl@9front.org
To: 9fans@9fans.net
Subject: Re: [9fans] There is no fork
Date: Tue, 13 Feb 2018 19:31:42 -0500 [thread overview]
Message-ID: <55C3BBA4253327283CC4441E39D17C19@5ess.inri.net> (raw)
In-Reply-To: A7E3F87F-1271-4A69-BEC9-3C333B1C0579@gmail.com
>> 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.
>
> The main issue for me is putting together a build environment on top
> of KVM or Linux, which isn’t covered in the FQA.
>
> I can’t build 9front on a Pi (well, not in productive amounts of
> 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).
>
> Since I’m a staunch supporter of CI/CD I’d love to automate the
> process from committing code to building a burnable image, and dipping
> into 9front from “outside” to run the requisite commands 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
next reply other threads:[~2018-02-14 0:31 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 0:31 sl [this message]
2018-02-14 7:18 ` Rui Carmo
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 14:37 sl
2018-02-13 14:15 sl
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
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
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=55C3BBA4253327283CC4441E39D17C19@5ess.inri.net \
--to=sl@9front.org \
--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).