From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] RPi in QEMU
Date: Sat, 2 Sep 2023 16:17:20 +0100 [thread overview]
Message-ID: <e7595240f89b7dd0019ba6a20da500f8@hamnavoe.com> (raw)
In-Reply-To: <CAL_X0tBBnQoT0Q3WekjOpbQ_qGHtX3b2tqftO7feDg27j45RaQ@mail.gmail.com>
> The thing about 9legacy is I'm not sure what patches to pull and what is or
> isn't stable.... do you have any recommendations?
I've put a script in contrib/miller/build-9pi.rc which shows the complete
process of building (almost) the 9pi image from the 4th edition ISO. You
can look at that to see what 9legacy patches are applied.
The "almost" is because applying the patches each time the image is built
loses some useful metadata. The actual 9pi.img.gz on contrib is a "golden"
copy which I've been updating with individual patches since about 2012,
so the modification dates on source files can be used to see what has
changed an when.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T5da5467097e4eab2-M6e7469bcf7263ca55ec33053
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
prev parent reply other threads:[~2023-09-02 15:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 4:22 Don Bailey
2023-08-26 9:23 ` Philip Silva via 9fans
2023-08-26 11:39 ` hiro
2023-08-26 10:44 ` mkf
2023-08-26 11:48 ` hiro
2023-08-26 12:52 ` Philip Silva via 9fans
2023-08-26 19:38 ` Don A. Bailey
2023-08-31 18:47 ` Richard Miller
2023-09-01 2:11 ` Don Bailey
2023-09-01 8:18 ` Richard Miller
2023-09-01 8:47 ` fgergo
2023-09-01 8:56 ` quiekaizam via 9fans
2023-09-01 14:06 ` Richard Miller
2023-09-01 15:38 ` Don Bailey
2023-09-01 19:37 ` Richard Miller
2023-09-02 2:01 ` Don Bailey
2023-09-02 3:25 ` Don Bailey
2023-09-02 8:25 ` hiro
2023-09-02 15:20 ` Richard Miller
2023-09-14 11:52 ` adr via 9fans
2023-09-14 17:11 ` Richard Miller
2023-09-14 17:25 ` adr via 9fans
2023-09-02 15:17 ` Richard Miller [this message]
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=e7595240f89b7dd0019ba6a20da500f8@hamnavoe.com \
--to=9fans@hamnavoe.com \
--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).