From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 26 Jan 2016 23:32:32 +0100 Message-ID: From: David du Colombier <0intro@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Go on Plan 9? Topicbox-Message-UUID: 7ffb2d66-ead9-11e9-9d60-3106f5b1d025 > 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