Help

Mon Oct 7 12:41:29 EDT 2013

You can unsubscribe yourself at the bottom of this page

http://lists.laptop.org/listinfo/devel

Gonzalo

On Mon, Oct 7, 2013 at 1:08 PM, Anderson, Nicole A <NAnderson at winona.edu>wrote:

> Unsubscribe me from this list please.
>
> > On Oct 7, 2013, at 11:01 AM, "devel-request at lists.laptop.org" <
> devel-request at lists.laptop.org> wrote:
> >
> > Send Devel mailing list submissions to
> >    devel at lists.laptop.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >    http://lists.laptop.org/listinfo/devel
> > or, via email, send a message with subject or body 'help' to
> >    devel-request at lists.laptop.org
> >
> > You can reach the person managing the list at
> >    devel-owner at lists.laptop.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Devel digest..."
> >
> >
> > Today's Topics:
> >
> >   1. Android on the XO-4 (Sameer Verma)
> >   2. Re: Android on the XO-4 (Walter Bender)
> >   3. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 (James Cameron)
> >   4. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4
> >      (Yioryos Asprobounitis)
> >   5. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 (James Cameron)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Sun, 6 Oct 2013 11:03:05 -0700
> > From: Sameer Verma <sverma at sfsu.edu>
> > To: "Devel's in the Details" <devel at lists.laptop.org>,    John Gilmore
> >    <gnu at toad.com>
> > Subject: Android on the XO-4
> > Message-ID:
> >    <CAFoGK8EjcHHG5UFBLpzCBQO838JaguXRiuEaP9+Fv98EaVAgUA at mail.gmail.com>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > I was at the Internet Archive for some work on Pathagar
> > (https://github.com/PathagarBooks/pathagar). Also there that afternoon
> > was John Gilmore (cc'd). We got to talking about the XO-4, Android,
> > HTML5, etc. A bit of doodling on Physics, and John put together a two
> > cylinder engine, complete with a rocker arm :-) He also suggested the
> > possibility of CyanogenMod on the XO-4 as a starting point.
> >
> > If there is any interest in this, please submit a proposal for the
> > upcoming OLPC SF summit
> > http://www.olpcsf.org/CommunitySummit2013/proposal
> >
> > John,
> >
> > If you are in town Oct 18-20, we'd love to have you there.
> > http://olpcsf.org/summit
> >
> > cheers,
> > Sameer
> > --
> > Sameer Verma, Ph.D.
> > Professor, Information Systems
> > San Francisco State University
> > http://verma.sfsu.edu/
> > http://commons.sfsu.edu/
> > http://olpcsf.org/
> > http://olpcjamaica.org.jm/
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Sun, 6 Oct 2013 15:29:10 -0400
> > From: Walter Bender <walter.bender at gmail.com>
> > To: Sameer Verma <sverma at sfsu.edu>
> > Cc: Devel's in the Details <devel at lists.laptop.org>,    John Gilmore
> >    <gnu at toad.com>
> > Subject: Re: Android on the XO-4
> > Message-ID:
> >    <CADf7C8tYNdp-Hv-RXHo54X=9cSForWQq33Dgy+rLN03wSExQXw at mail.gmail.com>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Not sure this helps us get around the Marvel bottleneck, but worth
> > investigating.
> >
> > -walter
> >
> >> On Sun, Oct 6, 2013 at 2:03 PM, Sameer Verma <sverma at sfsu.edu> wrote:
> >> I was at the Internet Archive for some work on Pathagar
> >> (https://github.com/PathagarBooks/pathagar). Also there that afternoon
> >> was John Gilmore (cc'd). We got to talking about the XO-4, Android,
> >> HTML5, etc. A bit of doodling on Physics, and John put together a two
> >> cylinder engine, complete with a rocker arm :-) He also suggested the
> >> possibility of CyanogenMod on the XO-4 as a starting point.
> >>
> >> If there is any interest in this, please submit a proposal for the
> >> upcoming OLPC SF summit
> >> http://www.olpcsf.org/CommunitySummit2013/proposal
> >>
> >> John,
> >>
> >> If you are in town Oct 18-20, we'd love to have you there.
> >> http://olpcsf.org/summit
> >>
> >> cheers,
> >> Sameer
> >> --
> >> Sameer Verma, Ph.D.
> >> Professor, Information Systems
> >> San Francisco State University
> >> http://verma.sfsu.edu/
> >> http://commons.sfsu.edu/
> >> http://olpcsf.org/
> >> http://olpcjamaica.org.jm/
> >> _______________________________________________
> >> Devel mailing list
> >> Devel at lists.laptop.org
> >> http://lists.laptop.org/listinfo/devel
> >
> >
> >
> > --
> > Walter Bender
> > Sugar Labs
> > http://www.sugarlabs.org
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Mon, 7 Oct 2013 10:54:45 +1100
> > From: James Cameron <quozl at laptop.org>
> > To: Yioryos Asprobounitis <mavrothal at yahoo.com>
> > Cc: OLPC Devel <devel at lists.laptop.org>
> > Subject: Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4
> > Message-ID: <20131006235445.GC19250 at us.netrek.org>
> > Content-Type: text/plain; charset=iso-8859-1
> >
> > On Fri, Oct 04, 2013 at 10:32:17PM -0700, Yioryos Asprobounitis wrote:
> >>> Does not boot if the files are unpacked onto internal eMMC and no
> >>
> >>> external SD card is present.? Workaround: edit olpc.fth to ensure
> >>> mmcblk0 is used regardless.
> >> Thanks for the suggestion.
> >> However, we do not want to affect the original XO OS.
> >
> > Don't worry about that.
> >
> > 1.  for laptops in deployments where this is important, the laptops
> > are locked and won't be able to install your build,
> >
> > 2.  the OLPC OS is very easily reinstalled, insert USB drive, hold
> > down four keys, press power button,
> >
> > 3.  external media such as SD card and USB drives are not always
> > available, but internal media is always available,
> >
> >> That is also why we do not provide zd images that would be easier to
> >> install.  People that want it in the internal eMMC? should know how
> >> to do it too ;)
> >
> > For people who want to try your build, you have made it harder for
> > them, for (in my opinion) no good reason.
> >
> > You need not use zd images.  A simple Forth script would do fine.
> >
> > ok d# 4096 fat32-partition int
> > ok copy u:\fd-arm.sfs int:\fd-arm.sfs
> > ok mkdir int:\boot
> > ok copy u:\boot\initrd.4 int:\boot\initrd.4
> > ok copy u:\boot\vmlinuz.4 int:\boot\vmlinuz.4
> > ok copy u:\boot\olpc.fth int:\boot\olpc.fth
> > ok bye
> >
> > Can also copy out members from within .zip file using Open Firmware.
> >
> > If you wanted to set up a barrier to booting from internal storage,
> > there are probably more logical methods.
> >
> > --
> > James Cameron
> > http://quozl.linux.org.au/
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Sun, 6 Oct 2013 21:34:51 -0700 (PDT)
> > From: Yioryos Asprobounitis <mavrothal at yahoo.com>
> > To: James Cameron <quozl at laptop.org>
> > Cc: OLPC Devel <devel at lists.laptop.org>
> > Subject: Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4
> > Message-ID:
> >    <1381120491.16660.YahooMailNeo at web163405.mail.gq1.yahoo.com>
> > Content-Type: text/plain; charset=iso-8859-1
> >
> >
> >> 3.? external media such as SD card and USB drives are not always
> >> available, but internal media is always available,
> >>
> >>> That is also why we do not provide zd images that would be easier to
> >>> install.? People that want it in the internal eMMC? should know how
> >>> to do it too ;)
> >>
> >> For people who want to try your build, you have made it harder for
> >> them, for (in my opinion) no good reason.
> >>
> >> You need not use zd images.? A simple Forth script would do fine.
> >>
> >> ok d# 4096 fat32-partition int
> >> ok copy u:\fd-arm.sfs int:\fd-arm.sfs
> >> ok mkdir int:\boot
> >> ok copy u:\boot\initrd.4 int:\boot\initrd.4
> >> ok copy u:\boot\vmlinuz.4 int:\boot\vmlinuz.4
> >> ok copy u:\boot\olpc.fth int:\boot\olpc.fth
> >> ok bye
> >
> > Thanks you for the script.
> > However this would imply that you already
> > have expanded the tarball in a stick and then you copy over instead of
> > just booting from it. So is hard to see how is any easier for the user.
> >
> >> Can also copy out members from within .zip file using Open Firmware.
> >
> > What would be interesting is to download
> > the the zipped file in the internal card and then have
> > forth do the rest. Is it possible to read the file from
> int:\home\olpc\Downloads\file.zip, keep it in RAM, format int and write
> back from RAM?
> >
> > Though, come to think of it you may not need any of these. Could use
> alt-boot (assuming is empty) and existing partitions. Fatdog does not
> really care what else is in the partitions.
> > The challenge in this case is the fatdog-xo olpc.fth to know which
> device and setting we boot from and act accordingly in all possible
> scenarios.
> >
> >> If you wanted to set up a barrier to booting from internal storage,
> >> there are probably more logical methods.
> >
> > Suggestions are welcome as always ;)
> > Best
> >
> >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Mon, 7 Oct 2013 17:05:54 +1100
> > From: James Cameron <quozl at laptop.org>
> > To: Yioryos Asprobounitis <mavrothal at yahoo.com>
> > Cc: OLPC Devel <devel at lists.laptop.org>
> > Subject: Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4
> > Message-ID: <20131007060554.GG19250 at us.netrek.org>
> > Content-Type: text/plain; charset=iso-8859-1
> >
> > On Sun, Oct 06, 2013 at 09:34:51PM -0700, Yioryos Asprobounitis wrote:
> >>
> >>> 3.? external media such as SD card and USB drives are not always
> >>> available, but internal media is always available,
> >>>
> >>>> That is also why we do not provide zd images that would be easier to
> >>>> install.? People that want it in the internal eMMC? should know how
> >>>> to do it too ;)
> >>>
> >>> For people who want to try your build, you have made it harder for
> >>> them, for (in my opinion) no good reason.
> >>>
> >>> You need not use zd images.? A simple Forth script would do fine.
> >>>
> >>> ok d# 4096 fat32-partition int
> >>> ok copy u:\fd-arm.sfs int:\fd-arm.sfs
> >>> ok mkdir int:\boot
> >>> ok copy u:\boot\initrd.4 int:\boot\initrd.4
> >>> ok copy u:\boot\vmlinuz.4 int:\boot\vmlinuz.4
> >>> ok copy u:\boot\olpc.fth int:\boot\olpc.fth
> >>> ok bye
> >>
> >> Thanks you for the script.
> >> However this would imply that you already
> >> have expanded the tarball in a stick and then you copy over instead of
> >> just booting from it. So is hard to see how is any easier for the
> >> user.
> >
> > Yes, because you used a container format with no firmware support.
> > Why didn't you use .zip?
> >
> >>> Can also copy out members from within .zip file using Open Firmware.
> >>
> >> What would be interesting is to download
> >> the the zipped file in the internal card and then have
> >> forth do the rest. Is it possible to read the file from
> >> int:\home\olpc\Downloads\file.zip, keep it in RAM, format int and
> >> write back from RAM?
> >
> > The versioned filesystem of OLPC OS makes this impractical.
> >
> >> Though, come to think of it you may not need any of these. Could use
> alt-boot (assuming is empty) and existing partitions. Fatdog does not
> really care what else is in the partitions.
> >> The challenge in this case is the fatdog-xo olpc.fth to know which
> device and setting we boot from and act accordingly in all possible
> scenarios.
> >>
> >>> If you wanted to set up a barrier to booting from internal storage,
> >>> there are probably more logical methods.
> >>
> >> Suggestions are welcome as always ;)
> >
> > Detecting that olpc.fth was loaded from internal storage and then
> > terminating with a message is probably more appropriate.
> >
> > --
> > James Cameron
> > http://quozl.linux.org.au/
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > Devel mailing list
> > Devel at lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
> >
> >
> > End of Devel Digest, Vol 92, Issue 5
> > ************************************
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20131007/1f5f31a2/attachment.html>