From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: [9fans] updating 9pi
Date: Thu, 27 Dec 2012 20:44:27 +0000 [thread overview]
Message-ID: <fe25b8f621c262a4ae68fba05dd9ef3b@hamnavoe.com> (raw)
As a temporary measure until the raspberry pi kernel moves onto
sources, I've set up a repository that can be used with replica/pull
to keep up to date with 9pi kernel changes and essential usb driver
patches which haven't been applied to the main tree yet.
9pi SD card images earlier than 12 December 2012 had some incorrect
file ownership and permission settings, so if you installed a 9pi
fossil image before that date you should update it:
9fs sources
cp /n/sources/contrib/miller/rpi/dist/replica/9pi /dist/replica/
replica/pull -s/ /dist/replica/9pi
If you're using a raspberry pi only as a diskless terminal for an
existing Plan 9 network, you can use the same repository to install
and update just the 9pi kernel files:
replica/pull -v /dist/replica/9pi /sys/src/9/bcm
reply other threads:[~2012-12-27 20:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fe25b8f621c262a4ae68fba05dd9ef3b@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).