9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] problems installing the plan9 distribution on fileserver
Date: Wed, 26 Mar 2003 21:23:54 -0500	[thread overview]
Message-ID: <200303270223.h2R2Nsv03287@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 26 Mar 2003 20:35:28 EST." <Pine.GSU.4.44.0303262027150.3185-100000@adore.lightlink.com>

>  My adventures with Plan 9 continue... thanks to the people who helped me
> get past the initial fileserver configure stage... I've managed to create
> & ream the main filesystem, and with some digging through online
> documentation my auth/cpu & fileserver are now talking to each other.
> 
>  I've managed to mount the fileserver onto the auth/cpu server directory
> tree, as listed in the "Installing a Plan 9 File Server" document.
> However, when I get to the following command:
> 
>  wrap/inst -ovr /n/$FILESERVER plan9.9gz
> 
>  I get the following error message:
> 
>  wrap/inst: '/bin/wrap' directory entry not found
> 
>  This has me utterly baffled. I take it I am supposed to have this utility
> installed on the auth/cpu server from the install, but it does not seem to
> be there.
> 
>  I've tried searching for it:
> 
>  du -a . | grep wrap    (also for inst, no luck on either)
> 
>  I am running Plan 9 4th edition "current-as-of-2-weeks-ago" (x86) ...
> currently doing another pull to see if perhaps something is missing.
> 
>  Any suggestions? Unless I am completely off-base on this, it just seems I
> am missing a utility I should have... as I think everything else is
> communicating as it should.
> 
>  Thanks in advance.

Argh, I've been meaning to fix that.  Basically, wrap/* no longer
exists; that functionality has been taken over by the replica tools.

I'm a little surprised your du -a /root | grep inst didn't see
/root/dist/replica/inst; that's on sources, but maybe it's not making
it into the installation logs or something.  Anyway, I'd do a pull, and
if /dist/replica/inst doesn't exist, copy it off of sources by hand.
Then you can do:

	9fs sources
	bind /n/sources/plan9 /n/dist
	srv $FILESERVER
	mount -c /srv/$FILESERVER /n/inst
	replica/pull -v /dist/replica/inst

Which will populate /n/inst with the current version of the system from
sources.  You might want to wait a while though; rsc is pushing out
some changes to namespace and some other stuff that (I don't think)
have hit sources yet, but which will be backwards incompatible.  It's
worth it to wait so you avoid the incompatibility.

	- Dan C.



  reply	other threads:[~2003-03-27  2:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27  1:35 Matthew Haas
2003-03-27  2:23 ` Dan Cross [this message]
2003-03-27  3:15   ` Matthew Haas
2003-03-27  3:32     ` Dan Cross
2003-03-27  3:47       ` Russ Cox

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=200303270223.h2R2Nsv03287@augusta.math.psu.edu \
    --to=cross@math.psu.edu \
    --cc=9fans@cse.psu.edu \
    /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).