9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] plan9.ini: ipconfig and bootargs
Date: Sun, 14 Feb 2016 17:26:10 +0100	[thread overview]
Message-ID: <20160214162610.GA489@polynum.com> (raw)

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 <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                     http://www.arts-po.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



             reply	other threads:[~2016-02-14 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 16:26 tlaronde [this message]
2016-02-15 15:41 ` erik quanstrom
2016-02-15 16:46   ` tlaronde

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=20160214162610.GA489@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /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).