9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "James A. Robinson" <jim.robinson@gmail.com>
To: "9fans@9fans.net" <9fans@9fans.net>
Subject: [9fans] raspberry pi root over tcp
Date: Thu, 24 Nov 2016 17:48:14 +0000	[thread overview]
Message-ID: <CAPd04b5OE9kAk2++cHOQyxY8JuyWOsZfnPhu4-NRgYpO8T+6Xw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

Hi folks,

I can boot a raspberry pi using its local fossil, and I can
mount a remote fileserver using 9fs once it is booted. Next,
I wanted to try and mount the filesystem as the pi's root.

Based on this

http://man.cat-v.org/plan_9/8/plan9.ini
http://man.cat-v.org/plan_9/8/boot

I tried using the following to mount the root off a 9atom
file server I have running on 10.0.1.200:

bootargs=tcp!10.0.1.200!564

Per the discussion I had with folks here earlier, I've set
the same host owner, password, and secstore on both
machine.  I want this raspberry pi to act as an auth
server.  I had originally intended for it to be a standalone
auth server, but based on input from folks I want to see
whether or not I can mount the auth server's root from
the fileserver.

Upon trying to boot the pi prompted for root, selected the
default (tcp) after 5 seconds, and then threw this:

panic: boot process died: undefined instruction: pc 0x605c

before rebooting itself.  I won't get a chance to dig into it
until later this weekend, but wanted to ask if anyone had
seen this themselves and knew what  I was doing wrong.


Jim

[-- Attachment #2: Type: text/html, Size: 1767 bytes --]

             reply	other threads:[~2016-11-24 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 17:48 James A. Robinson [this message]
2016-11-24 18:58 ` Steve Simon
2016-11-24 19:11 ` Richard Miller
2016-11-25 17:05   ` James A. Robinson

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=CAPd04b5OE9kAk2++cHOQyxY8JuyWOsZfnPhu4-NRgYpO8T+6Xw@mail.gmail.com \
    --to=jim.robinson@gmail.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).