From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 14 Feb 2016 17:26:10 +0100 From: tlaronde@polynum.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20160214162610.GA489@polynum.com> MIME-Version: 1.0 User-Agent: Mutt/1.5.24 (2015-08-30) Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [9fans] plan9.ini: ipconfig and bootargs Topicbox-Message-UUID: 842da1a2-ead9-11e9-9d60-3106f5b1d025 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. The problem is that the gateway is taken as _another_ ip address for the interface! and that the mask is taken as the "node" serving the root filesystem! "fs" not being taken into account. Only: bootargs=tcp!gbe 192.168.1.2 works... Is the ip/ipconfig embedded in boot reduced as to not take all the options? (I don't need them; but the wiki page is the wrong; and I wonder if I'm doing something wrong or if there is indeed something changed since the page was written...) -- Thierry Laronde http://www.kergis.com/ http://www.arts-po.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C