[Server-devel] [XSCE] Re: a kernel for our solidrun protos?

[Tim Moody]

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.

Tim

From: George Hunt 
Sent: Monday, January 06, 2014 5:04 PM
To: Jon Nettleton 
Cc: XS Devel ; Tim Moody ; A Holt ; Curt Thompson 
Subject: Re: [XSCE] Re: [Server-devel] a kernel for our solidrun protos?

Jon, 

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.

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?

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. 

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.

Jan 8 is 2 days from now!

What do others think?



On Fri, Jan 3, 2014 at 9:37 PM, Adam Holt <holt at laptop.org> wrote:

  Thanks Sameer, fyi George's XO-4 should arrive by Tues.




  On Fri, Jan 3, 2014 at 9:31 PM, Sameer Verma <sverma at sfsu.edu> wrote:

    On Fri, Jan 3, 2014 at 3:47 PM, George Hunt <georgejhunt at gmail.com> wrote:
    > On our skype call Thursday, Jon suggested using the XO4 config file as a
    > base for getting all the needed kernel capability. And James suggested
    > looking at the upstream kernel conf.  In any case I'll need to understand,
    > and merge in, whatever special conig Rebeeh put in for the SOC in the Cubox.
    >
    > I won't have an XO4, until it arrives next week. (Adam agreed to send me
    > one, if I'd build it up to XSCE for Haiti later this month). So here comes a
    > request:
    >
    > Can I ask someone to email me the XO4 /boot/conf* file. I'm not at home, and
    > I didn't bring an ARM XO with me to California. I would love to get XSCE to
    > load, without erroring out, on a Cubox.
    >


    George,
    If you are close by, you can borrow mine until Adam's XO-4 arrives.

    Sameer


    > Do we need to start thinking about eSata interfaces. I happen to have an
    > eSata enclosure from Startech, and a eSata cable.  But I didn't find any
    > reference that looked like the kernel was recognizing an eSata interface. I
    > searched the config I'm using. There were "SATA" config lines which were not
    > enabled.
    >
    > Jon, what hardware have you been using? Maybe I can get you to email or post
    > your config file.
    >
    >
    >
    >
    > On Thu, Jan 2, 2014 at 12:16 AM, James Cameron <quozl at laptop.org> wrote:
    >>
    >> On Thu, Jan 02, 2014 at 12:00:43AM -0500, George Hunt wrote:
    >> > Right now XSCE server software does not load, because some of the
    >> > kernel networking userland (rtnetfilter) interfaces are not enabled.
    >>
    >> Speculation: the configuration changes between the upstream Linux
    >> kernel and the Fedora Linux kernel are what you may need to add.
    >> Looking at the kernel configuration (/boot/config*) of a Fedora kernel
    >> may give useful data.
    >>
    >> --
    >> James Cameron
    >> 
    http://quozl.linux.org.au/

    -- 

    Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org !
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/server-devel/attachments/20140106/3f6e0d05/attachment.html>