From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Wed, 2 Jul 2008 22:12:15 +0200 From: hiro <23hiro@googlemail.com> To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <20080702180723.809C21E8C26@holo.morphisms.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080702180723.809C21E8C26@holo.morphisms.net> Subject: Re: [9fans] pull in 9vx Topicbox-Message-UUID: d7059e4e-ead3-11e9-9d60-3106f5b1d025 On 7/2/08, Russ Cox wrote: > If you give 9vx a full Plan 9 distribution, you can use > pull to update it just like any other distribution. > Early copies of 9vx had a /dist/replica/client/plan9.db > but it didn't match all the files I'd deleted to cut the > size of the archive down. In 0.12 I deleted the plan9.db > too, so that pull wouldn't try to run. > > If you want to run pull, you should start with a full tree. > I have posted one at http://pdos.csail.mit.edu/~rsc/plan9.tar.bz2 > You should be able to run pull successfully if you use > that tree as your root. > > You can also start with a stock Plan 9 CD, if you know how > to extract it into your local file system, but you will need > to populate /dist/replica/client appropriately and also > copy /dist/replica/network from a 9vx tree, since I haven't > gotten those changes back into the distribution yet. > > > Russ > > > I got crazy permissions here?! $ tar jxf plan9.tar.bz2 tar: plan9/mnt/exportfs/16: Cannot mkdir: Permission denied tar: plan9/mnt/exportfs/1: Cannot mkdir: Permission denied tar: plan9/mnt/exportfs/10: Cannot mkdir: Permission denied ... tar: plan9/mnt/exportfs/9: Cannot mkdir: Permission denied tar: plan9/mnt/cons/cons: Cannot mkdir: Permission denied tar: plan9/mnt/cons/consctl: Cannot mkdir: Permission denied tar: Ignoring unknown extended header keyword `SCHILY.dev' tar: Ignoring unknown extended header keyword `SCHILY.ino' tar: Ignoring unknown extended header keyword `SCHILY.nlink' tar: Ignoring unknown extended header keyword `SCHILY.dev' ... tar: Ignoring unknown extended header keyword `SCHILY.nlink' tar: Error exit delayed from previous errors