From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 13 Apr 2010 00:19:32 -0600
To: "Skip Tavakkolian" <9nut@9netics.com>, <ebo@sandien.com>, <9fans@9fans.net>
From: "EBo" <ebo@sandien.com>
Message-ID: <twig.1271139572.16961@swcp.com>
In-Reply-To: <43c85712dd833ad7544f72b7c66a3b2e@9netics.com>
References: <twig.1271136039.93205@swcp.com>
Subject: Re: [9fans] 9vx patch to read environment var PLAN9
Topicbox-Message-UUID: 00a291ce-ead6-11e9-9d60-3106f5b1d025

Skip Tavakkolian <9nut@9netics.com> said:

> > What?  The findroot code reads:
>
> read the code again; findroot doesn't come into play.

it most certainly does!

in main...

	if(!bootboot){
		if(localroot == nil && (localroot = findroot()) == nil)
			panic("cannot find plan 9 root; use -r");

So, if you do not specify localroot (via -r) then it uses findroot.  Findroot
first checks the cwd, and then two hardcoded paths.  This means that unless
the program is run from the 9vx's associated Plan 9 root, or the programs were
installed in "/Users/rsc/9vx" or "/home/rsc/plan9/4e", then you are requiring
all users on a system to run 9vx with -r and know where that root is always.

Is it unreasonable to expect that an invocation of "9vx" to actually run?

  EBo --