From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eigenstate.org ([206.124.132.107]) by ewsd; Mon Jun 10 02:54:25 EDT 2019
Received: from eigenstate.org (localhost [127.0.0.1])
	by eigenstate.org (OpenSMTPD) with ESMTP id 1f66c0c2;
	Sun, 9 Jun 2019 23:54:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=eigenstate.org; h=
	message-id:to:cc:subject:date:from:in-reply-to:mime-version
	:content-type:content-transfer-encoding; s=mail; bh=+zfS1Qsyiyj7
	3ptT1jTGt2TeNfM=; b=X/nzPuXj3JhrDSrKiFhUW74ooGGq2+BbFi9O6AW0kWYG
	C2oVNwl8gr/AbKug6+17zfuwdzSZhatKK646tqLZUgAnQYO/uZ4kw3+TSRuMsDOP
	VERGvqqrxdf2QkClkiV4BDIIJ4yp1x6eWS38Ssz4Fylgxxc3xgHqPrA+aQ9BOV8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=eigenstate.org; h=message-id
	:to:cc:subject:date:from:in-reply-to:mime-version:content-type
	:content-transfer-encoding; q=dns; s=mail; b=cn7DwLPJEKnt6MwsNG0
	f2KOAqldpksnX6JqRgZ4VrtvHse0FsUOfQjJPsWxBWUXX8ozCUf6zNIUSr1iYkIP
	RTbr58+Kswy3vphOAQWlb0d/zS2+fLVXhiXncE5T6uKqFvbR5/0Loo+T0Tm6wz55
	hCTt1/woV3G93atVNY2OAWtY=
Received: from abbatoir.hsd1.ca.comcast.net (c-76-21-119-139.hsd1.ca.comcast.net [76.21.119.139])
	by eigenstate.org (OpenSMTPD) with ESMTPSA id b04c91c4 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Sun, 9 Jun 2019 23:54:23 -0700 (PDT)
Message-ID: <38380F4B369A482E09E63A993755A7B4@eigenstate.org>
To: skhds1@gmail.com, ori@eigenstate.org
CC: 9front@9front.org
Subject: Re: [9front] Need help with configuring the Internet
Date: Sun, 9 Jun 2019 23:54:22 -0700
From: ori@eigenstate.org
In-Reply-To: CAHZWWqo6W2XAKF93_zM_Vb2gc5JiLA-ja=jT4jiYJMjZFj3kig@mail.gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: structured markup strategy ORM over AJAX realtime-java STM generator 

> Thanks for your reply. It really answered everything I needed to get going.
> 
> Of course, things aren't working as expected, mostly
> due to me being more familiar to Linux environments.
> I'm trying out many things, but the two most hindering
> problems at this point is the different uses of "grep" and "export".
> 
> Starting with grep, what I mostly use is  :
> 
> grep -ri "keyword" ./
> 
> Now this obviously doesn't work here, so I read the manual and tried :
> 
> grep -i -e "keyword" ./

Plan 9 grep doesn't recurse. Pass it the list of files instead.

	grep foo `{walk -f .}

The utility script in /bin/g has also recently been modified to
grep recursively. However, if you don't have internet working yet,
you probably don't have the updated version.

> The second part, "export", is the real problem for me though,
> because I don't even know where to look in this case.
>
> Many scripts including ndbsetup and confignet seems to use the keyword "export".
> Usually in Linux, I would just be able to use it and it will set-up the
> environment variable for me. Plan9-based systems seems to be different,
> as just naively typing in command export (or using the scripts) returns
> 
> can't open export: 'export' directory entry not found
> 
> I've tried "man exportfs" (that's what google shows me at least), but
> I don't think
> that was what I was looking for. In this case, just a pointer to the manual
> that explains the export mechanism would be enough for me. A suggestion to
> read the Plan9 manual is also welcome :) I'm actually considering it since I
> seem to lack too much understanding of this system right now.

You don't need export.

Plan 9's shell, rc, exports environment variables by default.
However, it caches them when they are set, so that they're not
re-read on every use.

The `export` you see in /bin/inst is a shell function defined
in /bin/inst/defs:130, to work around the caching when child
scripts modify the environment. (On plan 9, this is possible.
On unix, this is not possible.)