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