From: Chris McGee <newton688@gmail.com>
To: raingloom@protonmail.com,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Raspberry Pi 3 B+ image of 9front
Date: Sat, 5 Jan 2019 16:49:49 -0500 [thread overview]
Message-ID: <CAOk9ws0hh11vyu8NTipJvh58zYR0dt+AUdiyyJ+YS-POyTbreQ@mail.gmail.com> (raw)
In-Reply-To: <E0SfRnIcA2vUrNv95TzFTkJIWAFasOZwPCAjmMEsmj8mXtRExEE6hxv5xe5mKdrLFy4aW0K9Me7caZZyM4GXtlAN__z7B_3F6Ud9KsQqqV8=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
I have been intending to try out the new raspberry pi updates too for
9front, but haven't had the chance yet.
A couple of years ago I was building the sd-card images for my raspberry
pis by using qemu to bring up an x86 install of 9front and doing a
cross-compile within to build the new disk image. Here's a script that I
used after the manual 9front install to do that plus a bunch of other
things that you probably don't care about. It does need significant cleanup
and updates.
https://github.com/sirnewton01/rpi-9front/blob/master/postsetup.rc
I'm hoping that it is at least some help to others.
Chris
On Sat, Jan 5, 2019 at 12:10 PM Raingloom <raingloom@protonmail.com> wrote:
> Has anyone made one? I'm trying to put one together but the Plan 9 disk
> tools are... well they are quite different to what I'm used to. I managed
> to build the kernel and the userspace (with CONF=rpi2, which is afaik the
> correct one for rpi3 too?) and am trying to mirror the partitioning of the
> image by Richard Miller (at least more or less, I'll probably have to
> change things for HJFS) and combine the contents from that and a 9front VM.
> Is that a good way to go ahead?
>
>
[-- Attachment #2: Type: text/html, Size: 1688 bytes --]
next prev parent reply other threads:[~2019-01-05 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 17:08 Raingloom
2019-01-05 21:49 ` Chris McGee [this message]
2019-01-05 19:13 cinap_lenrek
[not found] <2ECD349844717870DA8862A351DA2ED6@felloff.net>
2019-01-05 22:44 ` Raingloom
2019-01-05 23:37 cinap_lenrek
2019-01-06 0:48 ` Raingloom
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=CAOk9ws0hh11vyu8NTipJvh58zYR0dt+AUdiyyJ+YS-POyTbreQ@mail.gmail.com \
--to=newton688@gmail.com \
--cc=9fans@9fans.net \
--cc=raingloom@protonmail.com \
/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).