From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Mon, 15 Feb 2016 07:41:37 -0800 To: 9fans@9fans.net Message-ID: In-Reply-To: <20160214162610.GA489@polynum.com> References: <20160214162610.GA489@polynum.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] plan9.ini: ipconfig and bootargs Topicbox-Message-UUID: 8482a97c-ead9-11e9-9d60-3106f5b1d025 On Sun Feb 14 08:30:20 PST 2016, tlaronde@polynum.com wrote: > Hello, > > When trying to re-install a Plan9 on a new node, being unable, with the > kernel compiled present on the CDROM image, to access a FAT or an iso > image of a root file system, I went to a combination of a minimal sketch > of a plan9 slice, with a 9fat made "by hand" (from an already installed > other OS---here NetBSD) and access at boot time a remote root > filesystem, for the installation, serves by another Unix node serving > 9P2000. > > The surprise is with the bootargs, in plan9.ini, supposed to configure > the network for the node, in order to access a remote root filesystem, > as in: > > fs=192.168.1.3 > # auth not used > auth=192.168.1.3 > bootargs=tcp!-g 192.168.1.1 gbe 192.168.1.2 255.255.255.0 > > what is after the '!' being supposed to be args to ip/ipconfig. here's what i have on my cpu server nobootprompt=il -g 10.1.10.1 ether /net/ether0 10.1.1.1 /112 nobootprompt is equivalent to bootargs - erik