From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <72b2e52f91c8aca547d99b56e9b1f046@hamnavoe.com> To: 9fans@9fans.net From: Richard Miller <9fans@hamnavoe.com> Date: Wed, 19 Feb 2014 09:05:40 +0000 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Raspberry Pi image Topicbox-Message-UUID: bc5c3daa-ead8-11e9-9d60-3106f5b1d025 > 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