"sugarize" tool and Tux Paint

[Albert Cahalan]

I wrote a tool to make normal X programs to run under sugar.
As a demo, it runs a logo program.

http://dev.laptop.org/~albert/xlogo-1.xo
http://dev.laptop.org/git?p=users/albert/sugarize;a=summary

How it works: A launcher program places Sugar's incompatible command
arguments into the environment, along with LD_PRELOAD pointing at
a shared library. The launcher then starts up the program by calling
execlp() with the arguments that the program actually needs. As the
program is starting up, the dynamic linker ("man ld.so") forces the
shared library into the program. The shared library intercepts calls
into libX11. From that intercepted function the shared library is
able to set various Sugar-specific window properties before the app
becomes visible. This lets activity switching work, gets the donut
icon right, etc.

A slightly newer version is included in the Tux Paint activity.
http://wiki.laptop.org/go/Tux_Paint
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

[EMAIL PROTECTED]

[Roman Czyborra]

1. Project name : ucs
2. Existing website, if any : http://czyborra.com/yudit/
3. One-line description : the cheapest available unicode support

4. Longer description   : we configure a multilingual text input system
: using stable and flexible xterm/braille/console
: alpine/lynx/yudit/yudit2
unifont/ucs-fonts/freefont
: and scripts and put the source code into a wiki
: and compile the object code so it can be
traced with gdb

5. URLs of similar projects : too many to mention

6. Committer list
   Please list the maintainer (lead developer) as the first entry. Only list
   developers who need to be given accounts so that they can commit to your
   project's code repository, or push their own. There is no need to list
   non-committer developers.

  Username   Full name SSH2 key URLE-mail
     - --
   #1 czyborra Roman Czyborra http://czyborra.com/.ssh/ [EMAIL PROTECTED]
   #2
   #3
  ...

   If any developers don't have their SSH2 keys on the web, please attach them
   to the application e-mail.

7. Preferred development model

   [X] Central tree. Every developer can push his changes directly to the
   project's git tree. This is the standard model that will be familiar to
   CVS and Subversion users, and that tends to work well for most projects.

   [ ] Maintainer-owned tree. Every developer creates his own git tree, or
   multiple git trees. He periodically asks the maintainer to look at one
   or more of these trees, and merge changes into the maintainer-owned,
   "main" tree. This is the model used by the Linux kernel, and is
   well-suited to projects wishing to maintain a tighter control on code
   entering the main tree.

   If you choose the maintainer-owned tree model, but wish to set up some
   shared trees where all of your project's committers can commit directly,
   as might be the case with a "discussion" tree, or a tree for an individual
   feature, you may send us such a request by e-mail, and we will set up the
   tree for you.

8. Set up a project mailing list:

   [ ] Yes, named after our project name
   [X] Yes, named [EMAIL PROTECTED]
   [] No

   When your project is just getting off the ground, we suggest you eschew
   a separate mailing list and instead keep discussion about your project
   on the main OLPC development list. This will give you more input and
   potentially attract more developers to your project; when the volume of
   messages related to your project reaches some critical mass, we can
   trivially create a separate mailing list for you.

   If you need multiple lists, let us know. We discourage having many
   mailing lists for smaller projects, as this tends to
   stunt the growth of your project community. You can always add more lists
   later.

9. Commit notifications

   [X] Notification of commits to the main tree should be e-mailed to the list
   we chose to create above
   [] A separate mailing list, -git, should be created for commit
   notifications
   [] No commit notifications, please

10. Shell accounts

   As a general rule, we don't provide shell accounts to developers unless
   there's a demonstrated need. If you have one, please explain here, and
   list the usernames of the committers above needing shell access.

   I am very much used to working with a shell because that allows me
to   debug and fix tricky problems.  I am a considerate soul and use
the resources responsibly.  I am not familiar or not content with all
the tools that exist to circumvent shell access.  I can give you shell
access to my machine(s) as well.

11. Translation
   [X] Set up the laptop.org Pootle server to allow translation
commits to be made
   [ ] Translation arrangements have already been made at ___

12. Notes/comments:

Eventually we need to broaden and wed the ucs supports in alpine,
lynx, xpdf, mozilla, openoffice and jre, add video frame and voip
streaming support to audacity, and make the wireless routing
active+passive so that each XO-1 can act as a cheap repeater and a
free hardware- or name-addressed IPv6 communication ether can grow
into the universe.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: I got a developer key -- now what? :)

[Mitch Bradley]

M. Edward (Ed) Borasky wrote:
> Chris Ball wrote:
>   
>> Hi,
>>
>>> I signed up for a developer key, so I have one now. But what can I
>>> do with it?
>>
>> You can do anything that you'd expect to do with a standard laptop;
>> install any operating system, and flash a new BIOS.
>>
>>> How can I be sure I'm not going to nuke the XO beyond all recovery?
>>> Is there some kind of documentation on what's risky and what's
>>> safe?
>>
>> You're safe no matter what you do to the NAND, because the firmware can
>> flash a new NAND image from USB.  If you want to be sure of not bricking
>> it, you should avoid flashing firmware that isn't signed by OLPC.
>>
>> - Chris.
>> 
>
> Ah ... OK. I have the procedure for flashing the NAND, but I haven't
> seen one for flashing the firmware. Is that documented somewhere?
>   

It is documented on the release page for each firmware version.  See the 
Installation section of:

http://wiki.laptop.org/go/OLPC_Firmware_q2d07


> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>   

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: attempt to access beyond end of device

[Charles Galpin]

On Dec 28, 2007, at 12:31 PM, Charles Galpin wrote:

> Hi All, first time poster, happy to be part of this community
>
> How I got here: I downloaded an olpc image, expanded it to 2G using
> gpartd per the wiki, wrote it to a USB stick, booted my XO off it,
> added dome dev tools and started building the kernel (slowly :) ).
> Despite having 400M free, I started getting these messages in the logs
> and finally the kernel compile (using rpmbuild) failed.
>
> Any idea what has gone wrong?  Did I perhaps make the image larger
> than my USB stick? How can I tell if this is the case?

Just for the archives, this was indeed the problem. I ran fdisk to see  
the size of the actual image on the USB disk and it was smaller than  
the size when running the image under parallels.

My kernel compile failed due to the lack of the glibc-headers rpm.

charles
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Java question

[Cay Horstmann]

I am trying to find out how to run Java GUI applications on the OLPC. I
installed Java by downloading and executing

jre-6u3-linux-i586-rpm.bin

It works--if I ssh -X into the machine from a Linux box, I can
successfully run Java Web Start applications such as

/usr/java/jre1.6.0_03/bin/javaws http://www.horstmann.com/violet/violet.jnlp

But when I try the same from the terminal activity, I just get a screen
filled with "Java Application Window" (which would normally appear as
the title decoration of the main window).

Similarly, when I place a JAR file onto the OLPC (such as
ResourceTest.jar from Core Java vol. 1 ch. 10), it runs beautifully when
I ssh -X into the machine, but when I execute it on the machine itself,
I get a blank screen.

I suppose this has something to do with the window manager on the OLPC.
Is there any way to overcome this?

Thanks,

Cay


-- 

Cay S. Horstmann | http://horstmann.com | mailto:[EMAIL PROTECTED]

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: I got a developer key -- now what? :)

[M. Edward (Ed) Borasky]

Chris Ball wrote:
> Hi,
> 
>> I signed up for a developer key, so I have one now. But what can I
>> do with it?
>
> You can do anything that you'd expect to do with a standard laptop;
> install any operating system, and flash a new BIOS.
> 
>> How can I be sure I'm not going to nuke the XO beyond all recovery?
>> Is there some kind of documentation on what's risky and what's
>> safe?
> 
> You're safe no matter what you do to the NAND, because the firmware can
> flash a new NAND image from USB.  If you want to be sure of not bricking
> it, you should avoid flashing firmware that isn't signed by OLPC.
> 
> - Chris.

Ah ... OK. I have the procedure for flashing the NAND, but I haven't
seen one for flashing the firmware. Is that documented somewhere?
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Unofficial Debian+XFCE build

[Jake Beard]

I've installed this per your instructions, but it doesn't seem to be
working. I have three questions:
1. The build appears to take up a bit over 400MB on disk. Were you aware of
this?
2.  /versions/boot/alt seems to point to
/version/pristine/f7b6242983ab837d642bacbffe32cc8. Doing ln -sf
/versions/pristine/debian /versions/boot/alt  as root did not change the
link. I also wasn't able to rm or mv it, and i didn't want to mess with it
too much, so I just made a new simlink called /versions/boot/alt-deb. I hope
this isn't a problem.
3.  I can't seem to boot the alternate image. Holding the O gamepad key on
startup doesn't seem to do anything, whereas the other cheat codes do seem
to work. I tried booting the image manually at the prompt by using
boot disk:\versions\pristine\debian\boot\olpcrd.img, as well as
disk:\versions\boot\alt-deb
Unfortunately, no matter what I do, it seems to boot into the normal olpcrd
image.

I'd appreciate any guidance you can offer. Please let me know. Thanks.

Jake


On Dec 28, 2007 9:24 PM, Andres Salomon <[EMAIL PROTECTED]> wrote:

> On Fri, 28 Dec 2007 16:15:36 -0500
> Ivan Krstić <[EMAIL PROTECTED]> wrote:
>
> > While waiting for the servers to finish churning last night, I put
> > together an UNOFFICIAL Debian "etch" 4.0 + XFCE4 build for the XO. It
> > includes Firefox, Thunderbird, a suite of development tools (python,
> > git, gcc, gdb, flex, bison, automake, autoconf, libtool), a music
> > player (XMMS), IRC client (irssi) and a graphical wireless AP
> > selector. The entire build takes up 250MB of flash. I optimized the
> > Firefox window layout to give you maximum screen estate, and
> > configured a number of keyboard shortcuts. Feedback welcome. Standard
> > disclaimer applies.
> >
>
> Are there source/binary packages somewhere?   I'm not sure if you've seen
> my apt repository, it has a few packages (including an xorg driver)..
>
> http://queued.mit.edu/~dilinger/sid/
>
> Lack of time has kept me from giving it much love, unfortunately.
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: I got a developer key -- now what? :)

[Chris Ball]

Hi,

   > I signed up for a developer key, so I have one now. But what can I
   > do with it?
   
You can do anything that you'd expect to do with a standard laptop;
install any operating system, and flash a new BIOS.

   > How can I be sure I'm not going to nuke the XO beyond all recovery?
   > Is there some kind of documentation on what's risky and what's
   > safe?

You're safe no matter what you do to the NAND, because the firmware can
flash a new NAND image from USB.  If you want to be sure of not bricking
it, you should avoid flashing firmware that isn't signed by OLPC.

- Chris.
-- 
Chris Ball   <[EMAIL PROTECTED]>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

I got a developer key -- now what? :)

[M. Edward (Ed) Borasky]

I signed up for a developer key, so I have one now. But what can I do
with it? How can I be sure I'm not going to nuke the XO beyond all
recovery? Is there some kind of documentation on what's risky and what's
safe?
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: licensing: GPLv2, v3, and Apache

[David W Hogg]

Thanks to all who responded.  Perhaps surprisingly, these emails
clarified some of the issues for me.  Will ponder and license,
hopefully soon.  Then I will apply for git hosting and etc.

On Dec 28, 2007 6:37 PM, John Gilmore <[EMAIL PROTECTED]> wrote:
> > > about the *technical* reasons and differences.
>
> > Apache or GPLv2 is fine. Anything that is GPL-compatable will be acceptable.
>
> Gnash is GPLv3, and it's on the OLPC.  The latest versions of many
> other GNU programs are GPLv3 too, and will also make it into later
> OLPC releases as it gets rebased on later Fedora releases.
>
> Most "GPLv2" licensed software actually says "GPLv2 or any later
> version".  This allows such software to be linked with, and/or
> converted to, later versions of the license.  The Linux kernel is one
> of the few GPL programs that has stuck with GPLv2-only -- and it
> will probably not stay that way for the next hundred years.
>
> I negotiated with a lot of companies as co-founder of Cygnus, which
> develops and supports free software for companies that use it.  (It's
> now part of Red Hat.)  Licensing your code under Apache, GPLv2,
> GPLv2+, or GPLv3+ protects the "Four Freedoms" of its users and
> developers; see http://www.gnu.org/philosophy/free-sw.html .  The
> practical difference is that later, people who modify GPL software
> can't take it proprietary.
>
> Often companies will improve free software, for their own use and the
> use of their customers.  The GPL is the argument that makes their
> lawyers and managers let go of the improvements, rather than
> reflexively making them proprietary because that's what they learned
> in law school.  See http://www.gnu.org/philosophy/pragmatic.html .
> Cygnus argued to every customer that freeing their changes is a good
> business practice, reduces later maintenance costs, reduces market
> fragmentation, etc.  But "The license on the underlying software
> *requires* it" is the argument that carried the day every time.
>
> Any version of the GPL will do; I use the latest (and allow my
> software to be relicensed to later versions) because it's the best.
> GPLv3 isn't US-centric; it allows linking with software licensed under
> similar non-GNU licenses; and it disallows DRM that would prevent
> users from removing restrictions that somebody has inserted in it.
> (While DRM on music has started falling out of the market this year,
> it's still alive and kicking on proprietary software, video, digital
> television, and anywhere else that a monopoly wants control over its
> competitors and its customers.)
>
> You can never tell where your software will end up.  I wrote the code
> that became GNU Tar, which now exists in every system that uses rpms
> or debs, including the OLPC.  I am happy that it's been GPL since 1988,
> and is now GPLv3+.
>
> John
>



-- 
David W. Hogg - associate professor, NYU - http://cosmo.nyu.edu/hogg/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: licensing: GPLv2, v3, and Apache

[Bernardo Innocenti]

John Gilmore wrote:

> Don't forget SimCity, which is shipped on the laptop in the Library,
> and is GPLv3+.

As we discussed on IRC, the XO bundles would need to carry
around at least the license, copyright and author information
in the .info file.


> (Also, info is actually GPLv3+; I'm filing a bug about that now.)

File it in Fedora's bugzilla: info is unchanged from our upstream.

-- 
 \___/
 |___|   Bernardo Innocenti - http://www.codewiz.org/
  \___\  One Laptop Per Child - http://www.laptop.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

joyride image Jffs2 on usb ?

[fr�ffffffffffe9d�ffffffffffe9ric]

Hello

On the latest build

http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/latest/devel_jffs2/

There is a file that ends with jffs2.usb

Does it mean that you can use jffs2 on usb ?

I tried to dd it to my usb , but the olpc won t boot
it

Anyone knows how to use it ?

Anyone knows how to make one ?

I have searched the web and I found this file is
present since built 1470 , but I haven t been able to
find anything else

Thanks

Frederic Pouchal


  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Unofficial Debian+XFCE build

[Andres Salomon]

On Fri, 28 Dec 2007 16:15:36 -0500
Ivan Krstić <[EMAIL PROTECTED]> wrote:

> While waiting for the servers to finish churning last night, I put  
> together an UNOFFICIAL Debian "etch" 4.0 + XFCE4 build for the XO. It  
> includes Firefox, Thunderbird, a suite of development tools (python,  
> git, gcc, gdb, flex, bison, automake, autoconf, libtool), a music  
> player (XMMS), IRC client (irssi) and a graphical wireless AP  
> selector. The entire build takes up 250MB of flash. I optimized the  
> Firefox window layout to give you maximum screen estate, and  
> configured a number of keyboard shortcuts. Feedback welcome. Standard  
> disclaimer applies.
> 

Are there source/binary packages somewhere?   I'm not sure if you've seen
my apt repository, it has a few packages (including an xorg driver)..

http://queued.mit.edu/~dilinger/sid/

Lack of time has kept me from giving it much love, unfortunately.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: licensing: GPLv2, v3, and Apache

[Jeffrey Kesselman]

BTW... 'free' is a vauge and funny term.

I'd argue that BSD and Apache are much freer then GPL because they
push no terms upon the users.  Others would probably argue that GPL is
"more free' because what it pushes on the users is that they must in
term make their code free.

Its all in how you look at it and where your politics lie.  I've
honestly always been somewhat uncomfortable with the coercive nature
of GPL. though in the specific case of the PD server it matched
exactly what I wanted.

JK

On Dec 28, 2007 7:41 PM, Jeffrey Kesselman <[EMAIL PROTECTED]> wrote:
> On Dec 28, 2007 6:37 PM, John Gilmore <[EMAIL PROTECTED]> wrote:
> >
> > I negotiated with a lot of companies as co-founder of Cygnus, which
> > develops and supports free software for companies that use it.  (It's
> > now part of Red Hat.)  Licensing your code under Apache, GPLv2,
> > GPLv2+, or GPLv3+ protects the "Four Freedoms" of its users and
> > developers; see http://www.gnu.org/philosophy/free-sw.html .  The
> > practical difference is that later, people who modify GPL software
> > can't take it proprietary.
>
> Well this has some otehr practical implications.  You might actually
> want to support proprietary development for various reasons.
>


-- 
~~ Microsoft help desk says: reply hazy, ask again later. ~~
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: licensing: GPLv2, v3, and Apache

[Jeffrey Kesselman]

On Dec 28, 2007 6:37 PM, John Gilmore <[EMAIL PROTECTED]> wrote:
>
> I negotiated with a lot of companies as co-founder of Cygnus, which
> develops and supports free software for companies that use it.  (It's
> now part of Red Hat.)  Licensing your code under Apache, GPLv2,
> GPLv2+, or GPLv3+ protects the "Four Freedoms" of its users and
> developers; see http://www.gnu.org/philosophy/free-sw.html .  The
> practical difference is that later, people who modify GPL software
> can't take it proprietary.

Well this has some otehr practical implications.  You might actually
want to support proprietary development for various reasons.

We licensed the Project Darkstar server under GPL because we want the
server technology itself to remain totally open and any improvements
be contributed back to the community.  However we licensed the client
API code BSD because we want the industry to feel free to write
commercial games with it.

We also are  looking at dual licensing because some commercial users
*want* a commercial license for variosu business reasons.  Keep that
in mind, no matter what kind of license you release the code under,
you retain all rights (assumign you don't actually give them away).
Including the right to license it under other terms any time you like.

This is the big difference between an Open Source license and a Public
Domain release.  The latter gives away all rights and anybody can do
anything with it.

Myself, I used to write a lot of Public Domain code.  Now, I write a
lot of BSD licensed code because its almost as free but lets me hold
on to the final rights.
-- 
~~ Microsoft help desk says: reply hazy, ask again later. ~~
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: licensing: GPLv2, v3, and Apache

[John Gilmore]

> > Only one or two pieces of software on the laptop are presently GPLv3
> Specifically,
>  # rpm -qa --queryformat '%{name} %{license}\n' | grep GPLv3 | sort
> espeak GPLv3+
> gnash GPLv3+
> gnash-plugin GPLv3+
> info GPLv3

Don't forget SimCity, which is shipped on the laptop in the Library,
and is GPLv3+.

(Also, info is actually GPLv3+; I'm filing a bug about that now.)

John

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Devel Digest, Vol 22, Issue 123 (licencia)

[Fiorella Haim]

Estaré fuera de la oficina hasta el 15 de enero. Por consultas, por favor 
contactar a Albana Nogueira o a Ana Hernández. ([EMAIL PROTECTED], [EMAIL 
PROTECTED])

I´ll be out of the office until January 15. Please contact Albana Nogueira or 
Ana Hernández ([EMAIL PROTECTED], [EMAIL PROTECTED]) if you need a faster 
reply. 
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: licensing: GPLv2, v3, and Apache

[John Gilmore]

> > about the *technical* reasons and differences.

> Apache or GPLv2 is fine. Anything that is GPL-compatable will be acceptable.

Gnash is GPLv3, and it's on the OLPC.  The latest versions of many
other GNU programs are GPLv3 too, and will also make it into later
OLPC releases as it gets rebased on later Fedora releases.

Most "GPLv2" licensed software actually says "GPLv2 or any later
version".  This allows such software to be linked with, and/or
converted to, later versions of the license.  The Linux kernel is one
of the few GPL programs that has stuck with GPLv2-only -- and it
will probably not stay that way for the next hundred years.

I negotiated with a lot of companies as co-founder of Cygnus, which
develops and supports free software for companies that use it.  (It's
now part of Red Hat.)  Licensing your code under Apache, GPLv2,
GPLv2+, or GPLv3+ protects the "Four Freedoms" of its users and
developers; see http://www.gnu.org/philosophy/free-sw.html .  The
practical difference is that later, people who modify GPL software
can't take it proprietary.

Often companies will improve free software, for their own use and the
use of their customers.  The GPL is the argument that makes their
lawyers and managers let go of the improvements, rather than
reflexively making them proprietary because that's what they learned
in law school.  See http://www.gnu.org/philosophy/pragmatic.html .
Cygnus argued to every customer that freeing their changes is a good
business practice, reduces later maintenance costs, reduces market
fragmentation, etc.  But "The license on the underlying software
*requires* it" is the argument that carried the day every time.

Any version of the GPL will do; I use the latest (and allow my
software to be relicensed to later versions) because it's the best.
GPLv3 isn't US-centric; it allows linking with software licensed under
similar non-GNU licenses; and it disallows DRM that would prevent
users from removing restrictions that somebody has inserted in it.
(While DRM on music has started falling out of the market this year,
it's still alive and kicking on proprietary software, video, digital
television, and anywhere else that a monopoly wants control over its
competitors and its customers.)

You can never tell where your software will end up.  I wrote the code
that became GNU Tar, which now exists in every system that uses rpms
or debs, including the OLPC.  I am happy that it's been GPL since 1988,
and is now GPLv3+.

John
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

NAND FLASH wear-out

[Mitch Bradley]

>
>> I would hate to fill up my 1GB and use all my flash write cycles...
>> 

The probability of wearing out NAND FLASH is much less than people seem 
to think.

The part is rated for 100,000 *erase* cycles per block.  There are 64 
independently-writable 2K pages per block.  Writing doesn't count in the 
wear calculation - just erasing.

Suppose that you pick one block and use it exclusively.  You write one 
page, then write another page, etc, and when you have filled all 64 
pages, you erase the block and start over.

What would it take to wear out that block over the 5-year design 
lifetime of the XO?

100,000 erases / 5 years / 365 days / 24 hours = 2.3 erases/hour.  So 
you can erase the same block every 26 minutes, 24 hours a day, 365 days 
per year, for 5 years before the block is likely to wear out.

But there are 64 pages per block, and you only have to erase after they 
are all written.  26 minutes * 60 secs/min / 64 pages = 24 seconds.   So 
you have to write a page every 24 seconds to wear out that block.

Obviously, if you have a very stupid application that is pounding on one 
block and writing/erasing it as fast as it can, or a filesystem layout 
that has a very bad hot-spot, then you could wear out a block much 
faster.  But even then, if it is possible to spare-out a worn out block, 
you wouldn't be likely to lose enough blocks over 5 years to make a 
significant dent in the device's overall capacity.

Let's look at this another way - how long would it take to wear out the 
entire device if you really tried?  The typical erase time for a block 
is 2 ms, so if you never wrote, just erased over and over, you could do 
100,000 erases in 200 seconds.  There are 8192 erase blocks in a 1 GB 
NAND FLASH, so you could wear out the whole thing in 1.6 million seconds 
= 19 days.  So you could wear out the device intentionally.  But that is 
just erasing, not writing.

If you write all the pages before erasing, it takes typically 0.2 mS to 
write a page, so writing all the pages of a block then erasing takes (64 
* 0.2 mS) + 2 mS = 15 mS.  So it would take 140 days to wear out the 
device by continuous writing/erasing.   Continuous writing/erasing 
doesn't happen in any realistic workload, because most applications 
don't write data then immediately discard it.

Oh, by the way, 100,000 cycles may be pessimistic.  That is the data 
sheet rating, but I have heard that single-level NAND FLASH (like the 
ones we use) are coming in at more like 1 million erase cycles typical 
these days.

The bottom line is that NAND wear-out is not likely to be an issue.  
JFFS2 does a good job of spreading out writes, and even if it only did a 
half-hearted job, that would probably be good enough.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Unofficial Debian+XFCE build

[Jake Beard]

Cool :)

Jake

On Dec 28, 2007 4:15 PM, Ivan Krstić <[EMAIL PROTECTED]> wrote:
> While waiting for the servers to finish churning last night, I put
> together an UNOFFICIAL Debian "etch" 4.0 + XFCE4 build for the XO. It
> includes Firefox, Thunderbird, a suite of development tools (python,
> git, gcc, gdb, flex, bison, automake, autoconf, libtool), a music
> player (XMMS), IRC client (irssi) and a graphical wireless AP
> selector. The entire build takes up 250MB of flash. I optimized the
> Firefox window layout to give you maximum screen estate, and
> configured a number of keyboard shortcuts. Feedback welcome. Standard
> disclaimer applies.
>
>
> How to install
> --
>
> 1. download the following two files to a USB stick:
>
>  
>  
>
> 2. get a developer key, disable security
> 3. boot the normal build, switch to tty1 (ctrl+alt+f1), become root
> 4. mount the USB key if not automounted; let's say it's mounted at /
> media/KEY
> 4. # cd /versions/pristine; tar xf /media/KEY/etch-xfce.tar
> 5. # cd /home/olpc; tar xf /media/KEY/etch-xfce-home.tar
> 6. # cp -rl /versions/pristine/debian /versions/run/debian
> 7. # /usr/sbin/setattr -R --iunlink /versions/run/debian
> 8. # ln -s /versions/pristine/debian /versions/boot/alt
> 9. # sync
> 10. Power off the XO. Power on and immediately hold the 'O' game key
> (right hand side of the screen.
>
> Boot should now proceed to a blue-background login screen. Log in as
> user 'olpc' with password 'olpc' -- that user has sudo access. Give
> XFCE a bit of time to load, and voila! Use the keyboard shortcuts
> below for some of the most useful options. Note that Firefox can take
> up to 15-20s to load after you start it, and you won't see a progress
> indication on the screen; that's expected. Also, you don't need to
> hold the 'O' key to boot into Debian next time; it'll be the default.
> Holding the key will get you back to the regular Sugar build.
>
>
> Keyboard shortcuts
> --
>
> - Ctrl+alt+w -- wireless AP picker
> - Ctrl+alt+t -- xterm (also alt+`)
> - Ctrl+alt+f -- firefox
> - Ctrl+alt+b -- thunderbird
> - Ctrl+alt+x -- xmms
>
> Enjoy,
>
> --
> Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Unofficial Debian+XFCE build

[Ivan Krstić]

On Dec 28, 2007, at 4:17 PM, ffm wrote:
> Can this be installed to an external hard disk and be booted off of?

With a bit of work.

> I would hate to fill up my 1GB and use all my flash write cycles...

If you keep the Sugar build in place and add this one, you'd only fill  
up about half the flash. If you remove the Sugar build, you're down to  
a quarter. And don't worry about running out of write/erase cycles;  
you'll have to work quite hard to do that with JFFS2.

--
Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Unofficial Debian+XFCE build

[ffm]

Can this be installed to an external hard disk and be booted off of?
I would hate to fill up my 1GB and use all my flash write cycles...

-ffm

On Dec 28, 2007 4:15 PM, Ivan Krstić <[EMAIL PROTECTED]>
wrote:

> While waiting for the servers to finish churning last night, I put
> together an UNOFFICIAL Debian "etch" 4.0 + XFCE4 build for the XO. It
> includes Firefox, Thunderbird, a suite of development tools (python,
> git, gcc, gdb, flex, bison, automake, autoconf, libtool), a music
> player (XMMS), IRC client (irssi) and a graphical wireless AP
> selector. The entire build takes up 250MB of flash. I optimized the
> Firefox window layout to give you maximum screen estate, and
> configured a number of keyboard shortcuts. Feedback welcome. Standard
> disclaimer applies.
>
>
> How to install
> --
>
> 1. download the following two files to a USB stick:
>
> 
> 
> >
> 
> 
> >
>
> 2. get a developer key, disable security
> 3. boot the normal build, switch to tty1 (ctrl+alt+f1), become root
> 4. mount the USB key if not automounted; let's say it's mounted at /
> media/KEY
> 4. # cd /versions/pristine; tar xf /media/KEY/etch-xfce.tar
> 5. # cd /home/olpc; tar xf /media/KEY/etch-xfce-home.tar
> 6. # cp -rl /versions/pristine/debian /versions/run/debian
> 7. # /usr/sbin/setattr -R --iunlink /versions/run/debian
> 8. # ln -s /versions/pristine/debian /versions/boot/alt
> 9. # sync
> 10. Power off the XO. Power on and immediately hold the 'O' game key
> (right hand side of the screen.
>
> Boot should now proceed to a blue-background login screen. Log in as
> user 'olpc' with password 'olpc' -- that user has sudo access. Give
> XFCE a bit of time to load, and voila! Use the keyboard shortcuts
> below for some of the most useful options. Note that Firefox can take
> up to 15-20s to load after you start it, and you won't see a progress
> indication on the screen; that's expected. Also, you don't need to
> hold the 'O' key to boot into Debian next time; it'll be the default.
> Holding the key will get you back to the regular Sugar build.
>
>
> Keyboard shortcuts
> --
>
> - Ctrl+alt+w -- wireless AP picker
> - Ctrl+alt+t -- xterm (also alt+`)
> - Ctrl+alt+f -- firefox
> - Ctrl+alt+b -- thunderbird
> - Ctrl+alt+x -- xmms
>
> Enjoy,
>
> --
> Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Unofficial Debian+XFCE build

[Ivan Krstić]

While waiting for the servers to finish churning last night, I put  
together an UNOFFICIAL Debian "etch" 4.0 + XFCE4 build for the XO. It  
includes Firefox, Thunderbird, a suite of development tools (python,  
git, gcc, gdb, flex, bison, automake, autoconf, libtool), a music  
player (XMMS), IRC client (irssi) and a graphical wireless AP  
selector. The entire build takes up 250MB of flash. I optimized the  
Firefox window layout to give you maximum screen estate, and  
configured a number of keyboard shortcuts. Feedback welcome. Standard  
disclaimer applies.


How to install
--

1. download the following two files to a USB stick:

 
 

2. get a developer key, disable security
3. boot the normal build, switch to tty1 (ctrl+alt+f1), become root
4. mount the USB key if not automounted; let's say it's mounted at / 
media/KEY
4. # cd /versions/pristine; tar xf /media/KEY/etch-xfce.tar
5. # cd /home/olpc; tar xf /media/KEY/etch-xfce-home.tar
6. # cp -rl /versions/pristine/debian /versions/run/debian
7. # /usr/sbin/setattr -R --iunlink /versions/run/debian
8. # ln -s /versions/pristine/debian /versions/boot/alt
9. # sync
10. Power off the XO. Power on and immediately hold the 'O' game key  
(right hand side of the screen.

Boot should now proceed to a blue-background login screen. Log in as  
user 'olpc' with password 'olpc' -- that user has sudo access. Give  
XFCE a bit of time to load, and voila! Use the keyboard shortcuts  
below for some of the most useful options. Note that Firefox can take  
up to 15-20s to load after you start it, and you won't see a progress  
indication on the screen; that's expected. Also, you don't need to  
hold the 'O' key to boot into Debian next time; it'll be the default.  
Holding the key will get you back to the regular Sugar build.


Keyboard shortcuts
--

- Ctrl+alt+w -- wireless AP picker
- Ctrl+alt+t -- xterm (also alt+`)
- Ctrl+alt+f -- firefox
- Ctrl+alt+b -- thunderbird
- Ctrl+alt+x -- xmms

Enjoy,

--
Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: closed lists

[David Woodhouse]

On Fri, 2007-12-28 at 12:50 -0500, Ivan Krstić wrote:
> On Dec 28, 2007, at 12:37 PM, Bernardo Innocenti wrote:
> > Are our spam filters good enough to make our lists
> > open for posting by non-members?
>
> The only spam filter good enough for that is Dave Woodhouse.  
> Inspecting every e-mail by hand. Spammers quake at the very thought.
> 
> (No.)

Spam filtering for lists isn't so hard. You already have an outstanding
offer from me to take over all mail operation.

-- 
dwmw2

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Need recommendation for compatible wireless hardware

[Carol Lerche]

Does someone know of a USB  wireless card/device that incorporates the
Marvell chipset and is compatible with the olpc driver?  I am trying to
provision a "school server" on conventional hardware to support the four xos
that I will be placing in a school.  I have just discovered that the xos
will not connect to the internet and mesh simultaneously unless they
themselves are pretending to be a school server.

(I note, btw that the Netgear WGT624 is supported by the openwrt project and
appears to have this chipset...wouldn't it be nice to have a compatible,
cheap commercial access point that could be used with conventional server
hardware just by reflashing?  Perhaps someone knows a friendly soul in that
project.)

Carol Lerche

-- 
"Always do right," said Mark Twain. "This will gratify some people and
astonish the rest."
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Official signed ship.2 build 654

[Ivan Krstić]

On Dec 28, 2007, at 12:36 PM, Ivan Krstić wrote:
> Now available here:
> 


This build has been retracted due to a QA issue. If you have obtained  
a copy of this build, you are not advised to use it. We apologize for  
the inconvenience.

--
Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: closed lists

[Ivan Krstić]

On Dec 28, 2007, at 12:37 PM, Bernardo Innocenti wrote:
> Are our spam filters good enough to make our lists
> open for posting by non-members?


The only spam filter good enough for that is Dave Woodhouse.  
Inspecting every e-mail by hand. Spammers quake at the very thought.

(No.)

--
Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Anyone built mtpaint?

[Jeffrey Kesselman]

Hey all,

Quick question.  I need a bit more then rgbpaint will give me for game
development, but
gimp seems way too heavy for the OLPC  (yum install gimp ended up
blowing up with out of memory, never mind the app itself.)

Has anyone done a build of mtpaint for the OLPC I could snag?

Thanks

JK

-- 
~~ Microsoft help desk says: reply hazy, ask again later. ~~
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: licensing: GPLv2, v3, and Apache

[Bernardo Innocenti]

Ivan Krstić wrote:

> Only one or two pieces of software on the laptop are  
> presently GPLv3-licensed.

Specifically,

 # rpm -qa --queryformat '%{name} %{license}\n' | grep GPLv3 | sort
 espeak GPLv3+
 gnash GPLv3+
 gnash-plugin GPLv3+
 info GPLv3

The number will increase slightly when/if we refresh our
packages with the latest upstream versions:

 binutils GPLv3+
 cpio GPLv3+
 jwhois GPLv3
 rsync GPLv3+

-- 
 \___/
 |___|   Bernardo Innocenti - http://www.codewiz.org/
  \___\  One Laptop Per Child - http://www.laptop.org/

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

closed lists

[Bernardo Innocenti]

Replying to cross-posts results in this annoying
moderation stuff.

Are our spam filters good enough to make our lists
open for posting by non-members?


[EMAIL PROTECTED] wrote:

> Your mail to 'Localization' with the subject
> 
> Re: [sugar] Update.1 schedule & trac usage... ***Please Read**
> 
> Is being held until the list moderator can review it for approval.
> 
> The reason it is being held:
> 
> Post by non-member to a members-only list
> 
> Either the message will get posted to the list, or you will receive
> notification of the moderator's decision.  If you would like to cancel
> this posting, please visit the following URL:

-- 
 \___/
 |___|   Bernardo Innocenti - http://www.codewiz.org/
  \___\  One Laptop Per Child - http://www.laptop.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Official signed ship.2 build 654

[Ivan Krstić]

Now available here:
 

The only difference from 653 is the inclusion of OFW Q2D07:

[EMAIL PROTECTED]:~/source/olpc/utils> ./diffbuildlog.py build653.log  
build654.log
Comparing 654 to baseline 653...
654 version change for bootfw: q2d06-0 -> q2d07-0
654 version change for olpcrd: 0.37-0 -> 0.39-0
Done, 357 packages unchanged.

Cheers,

--
Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

attempt to access beyond end of device

[Charles Galpin]

Hi All, first time poster, happy to be part of this community

How I got here: I downloaded an olpc image, expanded it to 2G using  
gpartd per the wiki, wrote it to a USB stick, booted my XO off it,  
added dome dev tools and started building the kernel (slowly :) ).  
Despite having 400M free, I started getting these messages in the logs  
and finally the kernel compile (using rpmbuild) failed.

Any idea what has gone wrong?  Did I perhaps make the image larger  
than my USB stick? How can I tell if this is the case?

In short I just want to setup a dev env that I can do things like  
build the kernel, add modules, and do other development.  I have  
access to 2G USB sticks and a 4G sdhc card.

tia, and happy holidays!
charles

excerpt from /var/log/messages:

Dec 28 11:51:25 localhost kernel: [38337.373588] attempt to access  
beyond end of device
Dec 28 11:51:25 localhost kernel: [38337.401787] sda: rw=1,  
want=4080239, limit=3999377
Dec 28 11:51:25 localhost kernel: [38337.429688] attempt to access  
beyond end of device
Dec 28 11:51:25 localhost kernel: [38337.457752] sda: rw=1,  
want=4128927, limit=3999377
Dec 28 11:51:25 localhost kernel: [38337.485608] attempt to access  
beyond end of device
Dec 28 11:51:25 localhost kernel: [38337.513431] sda: rw=1,  
want=4145359, limit=3999377

Kernel build output at point of failure:

   CHK include/linux/version.h
   CHK include/linux/utsrelease.h
fs/udf/balloc.c: In function 'udf_table_new_block':
fs/udf/balloc.c:747: warning: 'goal_eloc.logicalBlockNum' may be used  
uninitialized in this function
fs/udf/super.c: In function 'udf_fill_super':
fs/udf/super.c:1359: warning: 'ino.partitionReferenceNum' may be used  
uninitialized in this function



make[4]: *** sound/core/seq/instr/.built-in.o.cmd: Input/output  
error.  Stop.
make[3]: *** [sound/core/seq/instr] Error 2
make[2]: *** [sound/core/seq] Error 2
make[1]: *** [sound/core] Error 2
make: *** [sound] Error 2
+ exit 1
error: Bad exit status from /var/tmp/rpm-tmp.92705 (%build)


RPM build errors:
 Bad exit status from /var/tmp/rpm-tmp.92705 (%build)



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] Update.1 schedule & trac usage... ***Please Read**

[Bernardo Innocenti]

Jim Gettys wrote:
> I guess there may have been misunderstanding: since the beginning of
> December (or maybe before), only things intended for Update.1 and issues
> approved for fixing in Update.1 needing testing were supposed to be
> loaded into joyride.

I heard this also from C.Scott.  It's not a problem for me
because I can keep developming in my own xtest builds, but
where are the other developers supposed to integrate their
work and make it available for testing?

The moment Dennis creates the release tag in koji, nothing
happening on the trunk can disturb the release branch, so
we could keep it open for development during code freeze.

We already have a few independent teams working on
subprojects with independent schedules.  We need to set
a policy that supports this development model if we want
it to scale up: the number of contributors is likely to
grow very quickly over the next months.

-- 
 \___/
 |___|   Bernardo Innocenti - http://www.codewiz.org/
  \___\  One Laptop Per Child - http://www.laptop.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

New ship.2 build 655

[Build Announcer Script]

http://xs-dev.laptop.org/~cscott/olpc/streams/ship.2/build655/

-kernel.i586 0:2.6.22-20071121.7.olpc.af3dd731d18bc39
+kernel.i586 0:2.6.22-20071228.bernie15.olpc.af3dd

--
 This email was automatically generated
 Aggregated logs at http://dev.laptop.org/~bert/ship.2-pkgs.html
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [PATCH] [XoIRC] Make default nicks more meaningful (#5385)

[Phil Bordelon]

Simon McVittie wrote:
> On Sat, 22 Dec 2007 at 18:36:49 -0600, Phil Bordelon wrote:
>> By default, XoIRC uses the username when another nick is not
>> provided.  Alas, for every XO, this is 'olpc'.  This makes for
>> rather a mess in the IRC channels.
> 
>> This patch instead generates a more-meaningful nick:
> 
>> * It takes up to 11 alphabetic characters from the user's Sugar
>>   nick;
>> * it appends a hyphen; and
>> * it adds the last four hexadecimal digits of the MD5 hash of
>>   the user's public key.
> 
> If you instead chose the *first* few hex digits of the *SHA-1* of the user's
> public key, it'd match the beginning of the XO's default userIDs in the normal
> activity sharing/chat mechanism, which may be useful if you're trying to sort
> out network issues.

Simon,

Thanks for the feedback!  Attached is a patch which does just that, instead
of the previous MD5 stuff.  I wasn't aware that SHA1 wasn't the way to go,
but that's an easy change.


Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

diff -ur XoIRC.activity/purk/irc.py XoIRC.activity.nickfix/purk/irc.py
--- XoIRC.activity/purk/irc.py	2007-12-06 22:26:30.0 -0600
+++ XoIRC.activity.nickfix/purk/irc.py	2007-12-28 11:16:23.660205389 -0600
@@ -43,8 +43,34 @@
 try:
 nicks = [conf.get('nick')] + conf.get('altnicks',[])
 if not nicks[0]:
-import getpass
-nicks = [getpass.getuser()]
+
+# We're going to generate a nick based on the user's nick name
+# and their public key.
+import sugar.profile
+import hashlib
+
+user_name = sugar.profile.get_nick_name()
+pubkey = sugar.profile.get_pubkey()
+m = hashlib.sha1()
+m.update(pubkey)
+hexhash = m.hexdigest()
+
+# Okay.  Get all of the alphabetic bits of the username:
+user_name_letters = "".join([x for x in user_name if x.isalpha()])
+
+# If that came up with nothing, make it 'XO'.  Also, shorten it
+# if it's more than 11 characters (as we need 5 for - and the
+# hash).
+if len(user_name_letters) == 0:
+   user_name_letters = "XO"
+if len(user_name_letters) > 11:
+   user_name_letters = user_name_letters[0:11]
+
+# Finally, generate a nick by using those letters plus the first
+# four hash bits of the user's public key.
+user_nick = user_name_letters + "-" + hexhash[0:4]
+
+nicks = [user_nick]
 except:
 nicks = ["mrurk"]
 return nicks
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Toolbar in OLPCGames

[Mike C. Fletcher]

Ross Andrews wrote:
...
> Thank you, this is exactly the sort of response I was looking for!  
>   
Happy to help.
> This seems to work:
>
>  def build_toolbar(self):
>  toolbar=super(Activity, self).build_toolbar()
>  helpbut = ToolButton('activity')#Stock help icon
>  helpbut.set_tooltip(_("Foo!"))
>  helpbut.connect('clicked', self.help_button_pressed)
>  toolbar.insert(helpbut, -1)
>  helpbut.show()
>  toolbar.show()
>  return toolbar
>
> So I can communicate with the Pygame part of the code through  
> something like this:
>
>  def toolbar_button_pressed(self, button):
>  pygame.event.post(pygame.event.Event(pygame.USEREVENT))
>
> And Pygame can just pick it up the next time it goes through the event  
> loop.
>   
Precisely, you can also add a dictionary-of-properties after the
pygame.USEREVENT variable to communicate more information to your Pygame
code...

pygame.event.post(pygame.event.Event(pygame.USEREVENT, dict(
foo='bar',pos=(23,45

and so on.
> Only other question I have is that some (most) activities have more  
> than one toolbar, there's a tabbed pane sort of thing and toolbars  
> above it, so that the activity-related toolbar (sharing, save to  
> journal, etc) is separate from the stuff specific to your game, er,  
> activity. So how do I make one of those tab thingies?
>   
Turns out this is what the (newer-than-the-original-olpcgames-code)
"toolbox" class is:

   
http://www.vrplumber.com/sugar-docs/sugar.activity.activity.html#ActivityToolbox

will need to alter the PygameActivity class to use this instead of
ActivityToolbar around lines 97-99 in olpcgames/activity.py, will likely
need to return the toolbox instead of the toolbar as well (which means
you'll get a different object type out of that customisation point :( ,
maybe create a higher-level customisation point for the toolbox
creation, but that seems a bit over-engineered).  I doubt there are that
many activities using the customisation point yet, maybe just change the
API now and patch them.

Would be nice if we could avoid the tabs when there's no extra toolbars
defined (save screen real-estate), will have to experiment with that to
see if it works out-of-box or requires some hackery.

I'm thinking we'll also have the self.set_toolbox( x ) call happen in
the __init__ method so that whatever you return from build_toolbar will
be set as the toolbar.

Good luck,
Mike

-- 

  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://www.vrplumber.com
  http://blog.vrplumber.com

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: licensing: GPLv2, v3, and Apache

[Ivan Krstić]

On Dec 28, 2007, at 11:22 AM, David W Hogg wrote:
> Is there are requirement that
> OLPC items be GPLv3, or can they be GPLv2 and/or Apache?

There's absolutely no such requirement. We will accept any GPL- 
compatible license, but generally prefer one of {GPL, MIT, BSD}. I'm  
an OLPC core developer, and actively _discourage_ the use of the GPLv3  
license as being overly restrictive -- though I speak only for myself,  
and my opinions are by no means to be interpreted as the official  
position of OLPC. Only one or two pieces of software on the laptop are  
presently GPLv3-licensed.

> no choice, why, and if there *is* choice, why should I choose one over
> the other, from a development and/or technical standpoint?

This is a difficult question with no simple answer. Fundamentally, the  
issue is to figure out which particular flavor of freedom you  
subscribe to; there are some good resources out there that go into  
these issues at great length. As a first pass, take a look at:

 

Cheers,

--
Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: licensing: GPLv2, v3, and Apache

[Asheesh Laroia]

On Fri, 28 Dec 2007, ffm wrote:

> Apache or GPLv2 is fine. Anything that is GPL-compatable will be acceptable.

Just to be clear, the Apache License v2 is only compatible with GPLv3:

  Apache License, Version 2.0

 This is a free software license, compatible with version 3 of the GPL.

 Please note that this license is not compatible with GPL version 2,
 because it has some requirements that are not in the older version.
 These include certain patent termination and indemnification
 provisions.

http://www.fsf.org/licensing/licenses/#SoftwareLicenses

This is a trivial and largely unimportant nitpick.

-- Asheesh.

-- 
If God had intended Man to Smoke, He would have set him on Fire.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: licensing: GPLv2, v3, and Apache

[ffm]

Apache or GPLv2 is fine. Anything that is GPL-compatable will be acceptable.

-ffm

On Dec 28, 2007 11:22 AM, David W Hogg <[EMAIL PROTECTED]> wrote:

> Dear developers,
>
> Since I am *loving* my G1G1 (yes I recovered it from the brick I made
> it yesterday), I am inspired to finally get my planetarium software
> properly licensed and put into the git repository, with the hope that
> someday it will be part of the large menu of applications along the
> bottom bar.  That brings me to license.  Is there are requirement that
> OLPC items be GPLv3, or can they be GPLv2 and/or Apache?  If there is
> no choice, why, and if there *is* choice, why should I choose one over
> the other, from a development and/or technical standpoint?
>
> I don't want to start a hell-storm of philosophy; I, too have strong
> opinions about licensing and IP and etc and etc; I just want to know
> about the *technical* reasons and differences.
>
> David
>
> ps. My software is a simple, tiny, fast, and child-readable-hackable
> planetarium described here:
>
> http://howdy.physics.nyu.edu/index.php/OLPC_planetarium
>
> pps. Email me if you want to try it
>
> --
> David W. Hogg - associate professor, NYU - http://cosmo.nyu.edu/hogg/
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

licensing: GPLv2, v3, and Apache

[David W Hogg]

Dear developers,

Since I am *loving* my G1G1 (yes I recovered it from the brick I made
it yesterday), I am inspired to finally get my planetarium software
properly licensed and put into the git repository, with the hope that
someday it will be part of the large menu of applications along the
bottom bar.  That brings me to license.  Is there are requirement that
OLPC items be GPLv3, or can they be GPLv2 and/or Apache?  If there is
no choice, why, and if there *is* choice, why should I choose one over
the other, from a development and/or technical standpoint?

I don't want to start a hell-storm of philosophy; I, too have strong
opinions about licensing and IP and etc and etc; I just want to know
about the *technical* reasons and differences.

David

ps. My software is a simple, tiny, fast, and child-readable-hackable
planetarium described here:

http://howdy.physics.nyu.edu/index.php/OLPC_planetarium

pps. Email me if you want to try it

-- 
David W. Hogg - associate professor, NYU - http://cosmo.nyu.edu/hogg/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] Update.1 schedule & trac usage... ***Please Read**

[Marco Pesenti Gritti]

On Dec 28, 2007 5:12 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> I'd recommend not closing the bugs until you ask for approval for update
> (are finished with the set of bugs), rather than doing so immediately on
> each bug.

Perfect, that's what I was asking for.

> But waiting to close until after testing in an update.1 build
> hasn't worked out for anyone.

Agreed, I can't count how much time I wasted because of this :)

> We're also going to go through a diff of packages at code freeze and
> make sure nothing slips through the cracks that is fixed in joyride but
> didn't get into update.1.

Yup, sounds good.

Marco
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] Update.1 schedule & trac usage... ***Please Read**

[Jim Gettys]

I'd recommend not closing the bugs until you ask for approval for update
(are finished with the set of bugs), rather than doing so immediately on
each bug.  But waiting to close until after testing in an update.1 build
hasn't worked out for anyone.

We're also going to go through a diff of packages at code freeze and
make sure nothing slips through the cracks that is fixed in joyride but
didn't get into update.1.
 - Jim

On Fri, 2007-12-28 at 17:08 +0100, Marco Pesenti Gritti wrote:
> On Dec 28, 2007 4:14 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> > I guess there may have been misunderstanding: since the beginning of
> > December (or maybe before), only things intended for Update.1 and issues
> > approved for fixing in Update.1 needing testing were supposed to be
> > loaded into joyride.  As such, there should be no cherry picking of
> > fixes needed, when you are at a completed state.
> 
> I don't mean cherry picking of single fixes/git commits, but cherry
> picking of packages from joyride to Update.1.
> 
> My understanding of the process is:
> 
> 1 rwh fix bug A in sugar
> 2 tomeu fix bug B in sugar
> 3 tomeu builds a sugar package with bug A and bug B fixes in it.
> 4 the package goes in joyride and tomeu test it out
> 5 tomeu request ApprovalForUpdate
> 6 marco or jg approves the package
> 7 dgilmore tag (in other words cherry pick) the package for Update.1
> 
> With this process, if ticket A and ticket B are closed *before* 5, it
> will be hard to track which packages needs to be tagged for Update.1
> (and likely that we will miss some of them).
> 
> Marco
-- 
Jim Gettys
One Laptop Per Child


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] Update.1 schedule & trac usage... ***Please Read**

[Marco Pesenti Gritti]

On Dec 28, 2007 4:14 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> I guess there may have been misunderstanding: since the beginning of
> December (or maybe before), only things intended for Update.1 and issues
> approved for fixing in Update.1 needing testing were supposed to be
> loaded into joyride.  As such, there should be no cherry picking of
> fixes needed, when you are at a completed state.

I don't mean cherry picking of single fixes/git commits, but cherry
picking of packages from joyride to Update.1.

My understanding of the process is:

1 rwh fix bug A in sugar
2 tomeu fix bug B in sugar
3 tomeu builds a sugar package with bug A and bug B fixes in it.
4 the package goes in joyride and tomeu test it out
5 tomeu request ApprovalForUpdate
6 marco or jg approves the package
7 dgilmore tag (in other words cherry pick) the package for Update.1

With this process, if ticket A and ticket B are closed *before* 5, it
will be hard to track which packages needs to be tagged for Update.1
(and likely that we will miss some of them).

Marco
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] Update.1 schedule & trac usage... ***Please Read**

[Jim Gettys]

I guess there may have been misunderstanding: since the beginning of
December (or maybe before), only things intended for Update.1 and issues
approved for fixing in Update.1 needing testing were supposed to be
loaded into joyride.  As such, there should be no cherry picking of
fixes needed, when you are at a completed state. 

The approval for update step allows us to know when testing has been
completed for the particular issues, and allow the update.1 to generally
not regress (even though it would not necessarily have every fix present
in joyride). When testing of one or more bugs has completed, you can ask
for it to go into update.1; it is fine if this happens multiple times.
  - Jim



On Fri, 2007-12-28 at 11:17 +0100, Marco Pesenti Gritti wrote:
> On Dec 27, 2007 5:02 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> > Predictably, lots of people are on vacation, making the following
> > problem critical, as it is difficult for me to query people individually
> > on status as it might be at other times:
> >
> > Trac's (current) workflow is poor: we've had no good way to see what
> > bugs are "fixed" even if not in an update.1 build.  Noah Kantrowitz is
> > working on fixing this for us. There are much better workflow facilities
> > now available in trac, so we can have an "in QA state" and an "incoming
> > bug, not yet confirmed" state to help both QA and initial triage.  This
> > should help future releases, but I suspect changing horses now would be
> > unwise.
> >
> > But this problem, in concert with people being out on vacation, means I
> > lack good insight on key bugs left to fix for Update.1.  And a few more
> > nasty bugs have surfaced, of the variety that need some
> > implementation/testing (e.g. filling nand).
> >
> > So I think we need to slip Update.1 a week or two.
> >
> > 1) As a stop-gap measure for the Update.1 release (until we have the
> > better workflow available) to help the visibility of bugs left for
> > Update.1, *PLEASE* go through your bugs, and if you have *tested* them
> > as fixed in Joyride, please close the bugs.  The "verified" flag should
> > only be you've also verified it fixed in an Update.1 build.  Once we do
> > hit real code freeze, we can use the verified flag to let us all go
> > systematically through the more serious bugs to see if they've remained
> > fixed in the Release candidate builds we intend to ship.
> 
> Do you still want us to cherry pick packages into Update.1 (after
> ApprovalForUpdate) or is Update.1 going to be branched from Joyride at
> the time of the freeze?
> 
> If we are going to cherry pick, I think tickets should be closed only
> *after* a distro ticket to get the new package in Update.1 is opened.
> 
> Marco
-- 
Jim Gettys
One Laptop Per Child


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Question about button mapping in Browse handheld mode

[Jake Beard]

This looks like the most likely candidate:
http://dev.laptop.org/ticket/2249
Unfortunately, the last time it was touch was three months ago. Is
anyone doing any work on this?
Please let me know. Thanks.

Jake

On Dec 28, 2007 6:19 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:
> there's a bug filed in trac, assigned to the browse-activity
> component, which discusses key mappings in handheld mode.  I'm reading
> mail on my cellphone, so I can't look it up for you know, but it
> shouldn't be hard to find from http://dev.laptop.org/
>   --scott
>
>
> On 12/27/07, Jake Beard <[EMAIL PROTECTED]> wrote:
> > Hi,
> > My apologies for the cross-post. I've asked about this on sugar list,
> > but didn't receive a response, so I thought I'd try here.
> >
> > I cannot seem to get the button mapping for Browse handheld mode to
> > work according to the behavior listed here:
> > http://wiki.laptop.org/go/Browse#Button_Mapping
> >
> > For me, the D-Pad seems to pan up, down, left and right, and the
> > gampad buttons appear to map to page up, page down, go to the top of
> > the page and go to the bottom of the page, even when in handheld mode.
> > Are the button mappings listed on the wiki currently implemented, or
> > just planned for later on?
> > I'm using a recent joyride. I'd appreciate it if anyone could help me
> > determine what is going on.
> > Thanks.
> >
> > Jake
> > ___
> > Devel mailing list
> > Devel@lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
> >
>
>
> --
>  ( http://cscott.net/ )
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [PATCH] [XoIRC] Make default nicks more meaningful (#5385)

[Simon McVittie]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, 22 Dec 2007 at 18:36:49 -0600, Phil Bordelon wrote:
> By default, XoIRC uses the username when another nick is not
> provided.  Alas, for every XO, this is 'olpc'.  This makes for
> rather a mess in the IRC channels.
> 
> This patch instead generates a more-meaningful nick:
> 
> * It takes up to 11 alphabetic characters from the user's Sugar
>   nick;
> * it appends a hyphen; and
> * it adds the last four hexadecimal digits of the MD5 hash of
>   the user's public key.

If you instead chose the *first* few hex digits of the *SHA-1* of the user's
public key, it'd match the beginning of the XO's default userIDs in the normal
activity sharing/chat mechanism, which may be useful if you're trying to sort
out network issues.

In the XMPP/Jabber backend, the account Sugar currently tries to create is the
hex SHA-1 of the public key, plus "@", plus the server name. In the
link-local ("Bonjour") backend, Sugar uses the first few hex digits of
the SHA-1 of the public key (I forget how many - I think it's 6 or 8?)
plus "@" and the XO's hostname (which defaults to xo-11-22-33 if the MAC
address is xx:xx:xx:11:22:33).

Simon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: OpenPGP key: http://www.pseudorandom.co.uk/2003/contact/ or pgp.net

iD8DBQFHdPiaWSc8zVUw7HYRAuxnAKCOqP2SNxN834x18t2MxVdQ+8cdowCfWsEv
13CP6SDIgcKyGgYjc6zrzyI=
=9l2p
-END PGP SIGNATURE-
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Question about button mapping in Browse handheld mode

[C. Scott Ananian]

there's a bug filed in trac, assigned to the browse-activity
component, which discusses key mappings in handheld mode.  I'm reading
mail on my cellphone, so I can't look it up for you know, but it
shouldn't be hard to find from http://dev.laptop.org/
  --scott

On 12/27/07, Jake Beard <[EMAIL PROTECTED]> wrote:
> Hi,
> My apologies for the cross-post. I've asked about this on sugar list,
> but didn't receive a response, so I thought I'd try here.
>
> I cannot seem to get the button mapping for Browse handheld mode to
> work according to the behavior listed here:
> http://wiki.laptop.org/go/Browse#Button_Mapping
>
> For me, the D-Pad seems to pan up, down, left and right, and the
> gampad buttons appear to map to page up, page down, go to the top of
> the page and go to the bottom of the page, even when in handheld mode.
> Are the button mappings listed on the wiki currently implemented, or
> just planned for later on?
> I'm using a recent joyride. I'd appreciate it if anyone could help me
> determine what is going on.
> Thanks.
>
> Jake
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>


-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] Update.1 schedule & trac usage... ***Please Read**

[Marco Pesenti Gritti]

On Dec 27, 2007 5:02 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> Predictably, lots of people are on vacation, making the following
> problem critical, as it is difficult for me to query people individually
> on status as it might be at other times:
>
> Trac's (current) workflow is poor: we've had no good way to see what
> bugs are "fixed" even if not in an update.1 build.  Noah Kantrowitz is
> working on fixing this for us. There are much better workflow facilities
> now available in trac, so we can have an "in QA state" and an "incoming
> bug, not yet confirmed" state to help both QA and initial triage.  This
> should help future releases, but I suspect changing horses now would be
> unwise.
>
> But this problem, in concert with people being out on vacation, means I
> lack good insight on key bugs left to fix for Update.1.  And a few more
> nasty bugs have surfaced, of the variety that need some
> implementation/testing (e.g. filling nand).
>
> So I think we need to slip Update.1 a week or two.
>
> 1) As a stop-gap measure for the Update.1 release (until we have the
> better workflow available) to help the visibility of bugs left for
> Update.1, *PLEASE* go through your bugs, and if you have *tested* them
> as fixed in Joyride, please close the bugs.  The "verified" flag should
> only be you've also verified it fixed in an Update.1 build.  Once we do
> hit real code freeze, we can use the verified flag to let us all go
> systematically through the more serious bugs to see if they've remained
> fixed in the Release candidate builds we intend to ship.

Do you still want us to cherry pick packages into Update.1 (after
ApprovalForUpdate) or is Update.1 going to be branched from Joyride at
the time of the freeze?

If we are going to cherry pick, I think tickets should be closed only
*after* a distro ticket to get the new package in Update.1 is opened.

Marco
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel