On Nov 7, 2007, at 9:09 PM, Albert Cahalan wrote:
Using standard directories is not scribbling all over
the filesystem!
This anti-compatibility attitude needs to stop. It's really
hurting OLPC, needlessly making the goals harder to
achieve. Breaking compatibility is something to be done
as a
On 11/8/07, Ivan Krstić [EMAIL PROTECTED] wrote:
On Nov 7, 2007, at 9:09 PM, Albert Cahalan wrote:
Using standard directories is not scribbling all over
the filesystem!
This anti-compatibility attitude needs to stop. It's really
hurting OLPC, needlessly making the goals harder to
I sympathize with Albert's point here: we should be no more incompatible
than we have to be... Just because we have to break some things,
doesn't mean we have to break everything.
- Jim
On Thu, 2007-11-08 at 10:42 -0500, Albert Cahalan wrote:
On 11/8/07, Ivan
I have a pango cairo question.
Can someone help me to understand why my variable todisk can be False in
sugar-jhbuild, but has to be True on an xo? It would be nice to avoid
writing to disk on the xo. Thanks.
def createCountdownPng( self, num ):
todisk = True
w = 55
On Nov 8, 2007 5:20 PM, Ivan Krstić [EMAIL PROTECTED] wrote:
Bitfrost is not a general Linux distribution security mechanism.
Sugar is not a general Linux desktop environment. These things are
designed with different goals in mind, for a different purpose, and
behave differently than the
On Thu, 2007-11-08 at 18:11 +0100, Bert Freudenberg wrote:
On Nov 8, 2007, at 18:09 , Marco Pesenti Gritti wrote:
Though applications backwards compatibility just doesn't make sense in
this context. We consciously broke it with the high level design, both
of the user experience and of the
On Nov 8, 2007, at 11:33 AM, Jim Gettys wrote:
Heh. You are way too young
It takes a long time to become young! On the upside, my work did not
give rise to xorg.conf ;)
Marcus Leech wrote:
My first Unix machine had 128K of MOS memory, and we supported about
10-15 interactive users on
On 11/8/07, Marco Pesenti Gritti [EMAIL PROTECTED] wrote:
In some cases though it's better to break than to keep a fake
compatibility with something which is designed for a different use
case. That way the error is explicit and the activity author knows it
needs to be fixed. And I agree with
On 11/8/07, Albert Cahalan [EMAIL PROTECTED] wrote:
The XO /tmp is **exactly** like a SunOS /tmp. It's in RAM.
Well, one difference: it was common to have only 8 MB.
Since when is SunOS the standard? The FHS has no such wording or requirement:
Hey all,
Following up on the message I sent earlier, I ended up getting the
emulated networking working using VMWare instead of Qemu.
It is still interesting though to figure out while sharing activities
works in VMWare and not Qemu
Josh
___
On Thu, 2007-11-08 at 12:00 -0500, Ivan Krstić wrote:
On Nov 8, 2007, at 11:33 AM, Jim Gettys wrote:
Heh. You are way too young
It takes a long time to become young! On the upside, my work did not
give rise to xorg.conf ;)
Nor did mine. I will take no blame for that abortion, and
11 matches
Mail list logo
