9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Raspberry Pi image
Date: Wed, 19 Feb 2014 09:05:40 +0000	[thread overview]
Message-ID: <72b2e52f91c8aca547d99b56e9b1f046@hamnavoe.com> (raw)
In-Reply-To: <E3477753-6D77-4A8D-BE00-C408BE5822FF@fb.com>

> But how this image was produced? just mk in the sys/src/9/bcm/
> official plan9 distribution or do you have a custom plan9?

The 9pi image is very standard Plan 9.  Libraries, command binaries
and kernel are all built from distribution sources with
  cd /sys/src && mk install
  cd /sys/src/9/bcm && mk install
For the first, you need to link with the '-f' flag to get hardware
floating point.  That could be done by editing mkfiles, but since I
build for other arm systems from the same sources, I do it by setting
up aliases in my shell environment before running mk -
  fn 5l { /$cputype/bin/5l -f $* }
  fn pcc { /$cputype/bin/pcc -f $* }

The rest of the image is the same as the standard distribution for any
architecture, with x86 binaries and libraries removed, and these small
changes in config files to make an easier introduction for new users
running as 'glenda':

1. The /rc/bin/termrc.local script will optionally start up networking
using the command defined in cmdline.txt variable ipconfig=

2. The /usr/glenda/bin/rc/riostart script adds a console output window
to prevent console messages from messing up the rio desktop

3. The /rc/bin/replica/pull script filters x86 binaries from the update
log, so the replica/pull command won't add them all in again




      parent reply	other threads:[~2014-02-19  9:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 10:23 Ramakrishnan Muthukrishnan
2014-02-18 10:29 ` Richard Miller
2014-02-18 11:56   ` Ramakrishnan Muthukrishnan
2014-02-18 20:18   ` Grant R. Mather
2014-02-18 21:05     ` Richard Miller
2014-02-18 22:25       ` Yoann Padioleau
2014-02-19  0:13         ` Shane Morris
2014-02-19  0:19           ` Jacob Todd
2014-02-19 10:00           ` Richard Miller
2014-02-19 10:14             ` Shane Morris
2014-02-20  1:24               ` erik quanstrom
2014-02-20 15:47               ` Steven Stallion
2014-02-20 15:55                 ` erik quanstrom
2014-02-20 15:57                 ` David du Colombier
2014-02-20 15:57                 ` Charles Forsyth
2014-02-19 10:55             ` Ramakrishnan Muthukrishnan
2014-02-19  9:05         ` Richard Miller [this message]

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=72b2e52f91c8aca547d99b56e9b1f046@hamnavoe.com \
    --to=9fans@hamnavoe.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).