From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 bitsy port and Inferno ipaq1110
Date: Mon, 18 Jul 2022 23:19:23 -0400 [thread overview]
Message-ID: <A47FD1BAF7E3BA00D582A09D81CA3585@eigenstate.org> (raw)
In-Reply-To: <16581978960.18Ae6baD.8813@composer.9fans.topicbox.com>
Quoth me@larbob.org:
> https://9p.io/wiki/plan9/installation_on_ipaq/index.html
>
> https://doc.cat-v.org/inferno/4th_edition/inferno_ports
>
> Anyone have more info on the 9 and especially Inferno iPAQ ports? I
> can find mentions of the Inferno port in Vita Nuova's sources as well
> as in various articles but not much actual documentation on getting it
> up. I'm interested in getting these ports up on an iPAQ.
>
It used to live in /sys/src/9/bitsy.
it was removed from 9front in 2016:
term% bind -ac /dist/plan9front /
term% git/log -n1 /sys/src/9/bitsy
Hash: 76e4f7caf9440f3ebb667b801fa55f5bc1c4be08
Author: cinap_lenrek <cinap_lenrek@felloff.net>
Date: Thu May 5 10:32:15 -0400 2016
remove unmaintained bitsy (ipaq) kernel
but you can get it out of history:
term% git/query 76e4f7caf9440f3ebb667b801fa55f5bc1c4be08~
8d9a94a66ed80605cb21be1a091a9b6fe02bd023
term% @{cd / && git/fs}
term% mkdir oldkernel
term% dircp /.git/fs/object/8d9a94a66ed80605cb21be1a091a9b6fe02bd023/tree/sys/src/9 oldkernel
In the bitsy directory, there's a file called 'Booting101'
with instructions on how to get it up and running.
There are a lot of changes to the port/ directory, so updating
the bitsy code to a modern 9front will be a bit of work, but it
is probably doable.
good luck.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T410c4ca213693efc-Ma5642b6d35559dca24ad22a8
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-07-19 3:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 2:31 me
2022-07-19 3:19 ` ori [this message]
2022-07-19 3:34 ` [9fans] " me
2022-07-19 6:21 ` David du Colombier
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=A47FD1BAF7E3BA00D582A09D81CA3585@eigenstate.org \
--to=ori@eigenstate.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).