From: David du Colombier <0intro@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go on Plan 9?
Date: Tue, 26 Jan 2016 23:32:32 +0100 [thread overview]
Message-ID: <CANUoZoFnuFh051Ra2mZDB2O+0tUnYMKfYpP-2P65WFHBz01XbA@mail.gmail.com> (raw)
In-Reply-To: <CAA43vkUHJDu9z_XLLN4M__-2U4T=usC5DU7Jbg8sTGK60SP-Rg@mail.gmail.com>
> I'm looking at the directions in a (cached copy) of
> http://plan9.bell-labs.com/wiki/plan9/Staying_up_to_date/index.html...
>
> Is that still valid? What's the canonical procedure these days for updating
> a system?
>
> If that's roughly correct ... I'm running a single Plan 9 machine, combined
> CPU and fileserver ... I run that command as the bootes user on the system
> console?
This is a bit more complicated because of two reasons:
1. The plan9.bell-labs.com server is currently down.
2. Your system is too old, and running the new binaries will require
a new kernel with the nsec syscall.
I think the easiest for you would be to apply this patch:
% hget http://9legacy.org/9legacy/patch/9fs-9p.io.diff | ape/patch -p0
Then, install the new kernel binaries to get the new nsec syscall:
% 9fs sources
% 9fat:
% cp /n/sources/plan9/386/9pcf /n/9fat
% cp /n/sources/plan9/386/9pccpu /n/9fat
% hget http://www.9legacy.org/download/kernel/9pccpuf >/n/9fat
% unmount /n/9fat
Then, reboot your machine to run the new kernel.
Finally, update your system:
% /usr/glenda/bin/rc/pull
--
David du Colombier
next prev parent reply other threads:[~2016-01-26 22:32 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 21:44 Sean Caron
2016-01-26 22:05 ` Skip Tavakkolian
2016-01-26 22:16 ` Sean Caron
2016-01-26 22:32 ` David du Colombier [this message]
2016-01-26 22:40 ` David du Colombier
2016-01-27 1:40 ` Sean Caron
2016-01-27 1:52 ` Skip Tavakkolian
2016-01-27 2:24 ` Sean Caron
2016-01-27 4:04 ` lucio
2016-01-27 6:25 ` David du Colombier
2016-01-27 13:45 ` Charles Forsyth
2016-01-26 22:19 ` David du Colombier
2016-01-26 21:52 sl
2016-01-26 22:03 ` Kenny Lasse Hoff Levinsen
2016-01-26 22:29 ` sl
2016-01-26 22:38 ` David du Colombier
2016-01-27 1:29 ` Matthew Veety
2016-04-12 0:59 Chris McGee
2016-04-12 19:01 ` Skip Tavakkolian
2016-04-12 19:21 ` Chris McGee
2016-04-12 19:50 ` Dave MacFarlane
2016-04-12 21:26 ` Skip Tavakkolian
2016-04-13 0:18 ` Chris McGee
2016-04-12 21:44 ` sl
2016-04-13 2:50 ` Skip Tavakkolian
2016-04-13 2:59 ` Chris McGee
2016-04-13 7:27 ` lucio
2016-04-13 9:10 ` Richard Miller
2016-04-13 9:10 ` Richard Miller
2016-04-13 13:08 ` Chris McGee
2016-04-13 13:46 ` Richard Miller
2016-04-13 14:00 ` Chris McGee
2016-04-13 14:32 ` Kenny Lasse Hoff Levinsen
2016-04-13 14:32 ` Charles Forsyth
2016-04-13 14:39 ` Richard Miller
2016-04-13 14:42 ` Charles Forsyth
2016-04-13 14:46 ` Richard Miller
2016-04-13 14:46 ` Charles Forsyth
2016-04-13 14:52 ` lucio
2016-04-13 16:12 ` Richard Miller
2016-04-13 7:21 ` lucio
2016-04-13 7:34 ` lucio
2016-04-13 20:38 ` Skip Tavakkolian
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=CANUoZoFnuFh051Ra2mZDB2O+0tUnYMKfYpP-2P65WFHBz01XbA@mail.gmail.com \
--to=0intro@gmail.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).