From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <eb0d09b6523a613cb9ce83971b640e88@proxima.alt.za>
To: 9fans@9fans.net
Date: Sun, 18 Aug 2013 19:56:39 +0200
From: lucio@proxima.alt.za
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] Experiments in the wild
Topicbox-Message-UUID: 71bfbbc8-ead8-11e9-9d60-3106f5b1d025

I have a MikroTik 411 that will soon be deployed as a Wi-Fi link to
the Internet and in the absence of any other manner to mess with it
until then, I decided to see how far a Plan 9 installation would go:


	Plan 9
	cpu0: 680MHz mips 24k be v3.5 rev 0, no fpu
	cpu0: 16 tlb entries, using 4K pages
	cpu0: l1 i cache: 512 sets 4 ways 32 bytes/line
	cpu0: l1 d cache: 256 sets 4 ways 32 bytes/linecaches configured as write-through
	256M memory: 53M kernel data, 203M user, 1227M swap
	#l0: atheros71xx: 1Gbps port 0X1A000000 irq 5: d4ca6d7df1ce
	#l1: atheros71xx: 1Gbps port 0X19000000 irq 4: d4ca6d7df1cf

It stops there, but there are enough lies in the above to accept that
verdict.

Still, it shows promise, given that this is 9rb created from the
distribution.  I don't think I have the know-how to fix it (I may do
at least some digging, though), but I thought others may find this at
least interesting.

In passing, having to build the user space for MIPS, I found that it
helps if /mips/bin/contrib is writable by the builder: it is not
created by default, but it comes in handy for those of us who may have
something that will be installed in it.

++L