<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>I see your point, but I would bet heavily against my even having received a
cubox by end of day on wed. On the other hand, I can probably source the
disks and enclosures locally. At this point the onus is on you and Jon to
get to where xsce will install, so I’ll live with your call as to when that is
no longer realistic.</DIV>
<DIV> </DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">Tim</DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=georgejhunt@gmail.com
href="mailto:georgejhunt@gmail.com">George Hunt</A> </DIV>
<DIV><B>Sent:</B> Monday, January 06, 2014 5:04 PM</DIV>
<DIV><B>To:</B> <A title=jon.nettleton@gmail.com
href="mailto:jon.nettleton@gmail.com">Jon Nettleton</A> </DIV>
<DIV><B>Cc:</B> <A title=server-devel@lists.laptop.org
href="mailto:server-devel@lists.laptop.org">XS Devel</A> ; <A
title=tim@timmoody.com href="mailto:tim@timmoody.com">Tim Moody</A> ; <A
title=holt@laptop.org href="mailto:holt@laptop.org">A Holt</A> ; <A
title=curtathompson@gmail.com href="mailto:curtathompson@gmail.com">Curt
Thompson</A> </DIV>
<DIV><B>Subject:</B> Re: [XSCE] Re: [Server-devel] a kernel for our solidrun
protos?</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV dir=ltr>Jon,
<DIV> </DIV>
<DIV>When I compiled the kernel that Rabeeh made available on github for the
Cubox, I discovered that the XSCE 0.5 ansible install errors out because
iptables, and ajenti, do not install because of missing modules. In attempting
to modify the .config file (roughly 2000 lines long) I had very slow and painful
success.</DIV>
<DIV> </DIV>
<DIV>I'm afraid that the window for addressing this sort of problem before we
leave for Haiti is closing. Will we decide to purchase enclosures, hard
disks, etc, until we have some confidence that the XSCE software will run on the
Cubox's we have?</DIV>
<DIV> </DIV>
<DIV>It seems clear to me that we will not be able to count on having time
to work on kernel issues once we get to Haiti. </DIV>
<DIV> </DIV>
<DIV>Can we all agree on a deadline, by which time we decide to go or no go for
using Cubox on this Haiti trip? My proposal is Jan 8. That will give us 10 days
to order, and receive accessory disks, enclosures.</DIV>
<DIV> </DIV>
<DIV>Jan 8 is 2 days from now!</DIV>
<DIV> </DIV>
<DIV>What do others think?</DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Fri, Jan 3, 2014 at 9:37 PM, Adam Holt <SPAN
dir=ltr><<A href="mailto:holt@laptop.org"
target=_blank>holt@laptop.org</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV dir=ltr>Thanks Sameer, fyi George's XO-4 should arrive by Tues.<BR>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>
<DIV>
<DIV class=h5>On Fri, Jan 3, 2014 at 9:31 PM, Sameer Verma <SPAN
dir=ltr><<A href="mailto:sverma@sfsu.edu"
target=_blank>sverma@sfsu.edu</A>></SPAN> wrote:<BR></DIV></DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV>
<DIV class=h5>
<DIV>On Fri, Jan 3, 2014 at 3:47 PM, George Hunt <<A
href="mailto:georgejhunt@gmail.com"
target=_blank>georgejhunt@gmail.com</A>> wrote:<BR>> On our skype call
Thursday, Jon suggested using the XO4 config file as a<BR>> base for
getting all the needed kernel capability. And James suggested<BR>>
looking at the upstream kernel conf. In any case I'll need to
understand,<BR>> and merge in, whatever special conig Rebeeh put in for
the SOC in the Cubox.<BR>><BR>> I won't have an XO4, until it arrives
next week. (Adam agreed to send me<BR>> one, if I'd build it up to XSCE
for Haiti later this month). So here comes a<BR>>
request:<BR>><BR>> Can I ask someone to email me the XO4 /boot/conf*
file. I'm not at home, and<BR>> I didn't bring an ARM XO with me to
California. I would love to get XSCE to<BR>> load, without erroring out,
on a Cubox.<BR>><BR><BR></DIV>George,<BR>If you are close by, you can
borrow mine until Adam's XO-4 arrives.<BR><SPAN><FONT
color=#888888><BR>Sameer<BR></FONT></SPAN></DIV></DIV>
<DIV>
<DIV>
<DIV>
<DIV class=h5><BR>> Do we need to start thinking about eSata interfaces.
I happen to have an<BR>> eSata enclosure from Startech, and a eSata
cable. But I didn't find any<BR>> reference that looked like the
kernel was recognizing an eSata interface. I<BR>> searched the config I'm
using. There were "SATA" config lines which were not<BR>>
enabled.<BR>><BR>> Jon, what hardware have you been using? Maybe I can
get you to email or post<BR>> your config
file.<BR>><BR>><BR>><BR>><BR>> On Thu, Jan 2, 2014 at 12:16
AM, James Cameron <<A href="mailto:quozl@laptop.org"
target=_blank>quozl@laptop.org</A>> wrote:<BR>>><BR>>> On
Thu, Jan 02, 2014 at 12:00:43AM -0500, George Hunt wrote:<BR>>> >
Right now XSCE server software does not load, because some of
the<BR>>> > kernel networking userland (rtnetfilter) interfaces are
not enabled.<BR>>><BR>>> Speculation: the configuration changes
between the upstream Linux<BR>>> kernel and the Fedora Linux kernel
are what you may need to add.<BR>>> Looking at the kernel
configuration (/boot/config*) of a Fedora kernel<BR>>> may give useful
data.<BR>>><BR>>> --<BR>>> James Cameron<BR>>>
</DIV></DIV><A href="http://quozl.linux.org.au/"
target=_blank>http://quozl.linux.org.au/<SPAN class=HOEnZb><FONT
color=#888888><BR clear=all><BR>-- <BR></FONT></SPAN></A>
<DIV class=im>
<DIV dir=ltr><A href="http://quozl.linux.org.au/" target=_blank>Unsung
Heroes of OLPC, interviewed live @ </A><A href="http://unleashkids.org"
target=_blank>http://unleashkids.org</A>
!</DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV></DIV></DIV></BLOCKQUOTE></DIV>
<DIV> </DIV></DIV></DIV></DIV></DIV></BODY></HTML>