From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <201008312019.52547.0intro@gmail.com> References: <1aed5215dbf1142433aaa801b6585199@brasstown.quanstro.net> <201008312019.52547.0intro@gmail.com> Date: Tue, 31 Aug 2010 12:52:14 -0700 Message-ID: From: David Leimbach To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=0016363b83f8e650b1048f23ead8 Subject: Re: [9fans] plan 9 on the guruplug Topicbox-Message-UUID: 4bff5670-ead6-11e9-9d60-3106f5b1d025 --0016363b83f8e650b1048f23ead8 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Aug 31, 2010 at 11:19 AM, David du Colombier <0intro@gmail.com>wrote: > > Looking over my notes it appears the only thing I had to do to prevent > the > > crash was enable my fossil FS's listening capabilities. Now the guruplug > > gets a kernel and an FS every time. > > Yes, if you don't make fossil listening on port 564/tcp, this error appear. > It is a common oversight, when you are not accustomed to enable > unencrypted connection to 9P. > That's why I kept asking over and over again if there was a good way for me to test that I set my CPUFSAUTH server up properly before I started asking questions about the Sheevaplug port. > > > I'm probably going to plan 9 wikify my notes either tonight or tomorrow. > > I am probably the author of the documentation you find on some french > Plan 9 website. I didn't think it was worth writing it on the Plan 9 wiki > at > the time, but I encourage you to do it now as it will be obviously helpful > to others. > > Yes it was very helpful to me to see a boiled down list of steps that make this work. The only difference I think I have from your notes is my TFTP U-Boot string is a lot shorter and seems to work ok. I think the Sheeva/Guru platform is very interesting to work with. It'd be even more so if anyone ever makes U-SNAP capable appliances. Also their is an announced DisplayPlug that comes with either HDMI or a touchscreen interface that could make for a nice Plan 9 terminal for some programs potentially. I could see having these all over my house at some point. Dave > -- > David du Colombier > > --0016363b83f8e650b1048f23ead8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Aug 31, 2010 at 11:19 AM, David = du Colombier <0int= ro@gmail.com> wrote:
> Looking over my notes it appears the only thing I ha= d to do to prevent the
> crash was enable my fossil FS's listening capabilities. =A0Now the= guruplug
> gets a kernel and an FS every time.

Yes, if you don't make fossil listening on port 564/tcp, this err= or appear.
It is a common oversight, when you are not accustomed to enable
unencrypted connection to 9P.

That'= s why I kept asking over and over again if there was a good way for me to t= est that I set my CPUFSAUTH server up properly before I started asking ques= tions about the Sheevaplug port.
=A0

> I'm probably going to plan 9 wikify my notes either tonight or tom= orrow.

I am probably the author of the documentation you find on some french=
Plan 9 website. I didn't think it was worth writing it on the Plan 9 wi= ki at
the time, but I encourage you to do it now as it will be obviously helpful<= br> to others.


Yes it was very helpful to me to see a= boiled down list of steps that make this work. =A0 The only difference I t= hink I have from your notes is my TFTP U-Boot string is a lot shorter and s= eems to work ok.

I think the Sheeva/Guru platform is very interesting to= work with. =A0It'd be even more so if anyone ever makes U-SNAP capable= appliances. =A0Also their is an announced DisplayPlug that comes with eith= er HDMI or a touchscreen interface that could make for a nice Plan 9 termin= al for some programs potentially.

I could see having these all over my house at some poin= t.

Dave
=A0
--
David du Colombier


--0016363b83f8e650b1048f23ead8--