On 11/21/2010 08:54 PM, Daniel Drake wrote:
> Hi,
>
> Simon has built new Fedora 14 images for XO-1 and XO-1.5, available here:
> http://build.laptop.org/F14/os2/
>
> These efforts are now official so we'll step towards making this into
> a proper release. There are still some pretty obvious issues
On 22 November 2010 08:03, Simon Schampijer wrote:
> I think we should add a Version field for F14 (e.g. 1.5/1.0 software Build
> F14). That field is set by the reporter of an issue. The milestone is set by
> the development team/maintainer to triage his work, when he thinks that
> issue can/will
On 22 November 2010 02:34, Mikus Grinbergs wrote:
> Used yum to install the 1121 kernel. Copied new /boot content into
> /versions tree. But booting still brings up the previous 1119 kernel.
>
> What I did here worked fine with all previous builds. What more needs
> to be done to accomplish a k
On 11/22/2010 10:08 AM, Daniel Drake wrote:
> On 22 November 2010 08:03, Simon Schampijer wrote:
>> I think we should add a Version field for F14 (e.g. 1.5/1.0 software Build
>> F14). That field is set by the reporter of an issue. The milestone is set by
>> the development team/maintainer to triag
On 22 November 2010 09:24, Simon Schampijer wrote:
> We have to do that at some point when we want to do a "serious" release. In
> any case, I think reporters should indicate a version. We should not abuse
> the milestone field to get that information.
If someone is doing that already for 10.1.3
On Mon, Nov 22, 2010 at 12:06 AM, Mikus Grinbergs wrote:
> XO-1 It keeps asking me over and over for a keyring password.
>
> What is this for ?
Its used by telepathy-mission-control so passwords aren't stored in
plain text files.
Regards,
Peter
> How can I nullify this function ?
>
> mikus
>
>
On 11/22/2010 10:59 AM, Daniel Drake wrote:
> On 22 November 2010 09:24, Simon Schampijer wrote:
>> We have to do that at some point when we want to do a "serious" release. In
>> any case, I think reporters should indicate a version. We should not abuse
>> the milestone field to get that informati
On 22 November 2010 10:32, Simon Schampijer wrote:
> Yes, we do triage bugs for 10.1.3. Until 10.1.3 is out in mid December I
> don't want to get into F14 triaging. However as I have to read all the bugs
> anyhow, as you mentioned, I can make sure the version field is set correctly
> in new incomi
On Mon, Nov 22, 2010 at 09:03:28AM +0100, Simon Schampijer wrote:
> I think we should add a Version field for F14 (e.g. 1.5/1.0 software
> Build F14).
I disagree. The version field is for formal releases. The reporter of
a bug may use "Development build as of this date" for the current F14
buil
On 11/22/2010 11:55 AM, James Cameron wrote:
> On Mon, Nov 22, 2010 at 09:03:28AM +0100, Simon Schampijer wrote:
>> I think we should add a Version field for F14 (e.g. 1.5/1.0 software
>> Build F14).
>
> I disagree. The version field is for formal releases. The reporter of
> a bug may use "Develo
On 11/22/2010 03:09 AM, Daniel Drake wrote:
> See /boot/README
> XO-1 is now using partitions.
/boot/README did not help me with my running XO-1 build os2, in which
the only available partition is the ubifs for root.
Have now written http://dev.laptop.org/ticket/10462
Thanks, mikus
OLPC build 10.1.3 - 354
=
The wake up on multicast packages build.
=Builds=
http://build.laptop.org/10.1.3/xo-1/os354
http://build.laptop.org/10.1.3/xo-1.5/os354
=Description of changes in this build=
==olpc-powerd==
* Better collaboration support when idle suspend is
On Mon, Nov 22, 2010 at 5:55 AM, James Cameron wrote:
> I disagree. The version field is for formal releases. The reporter of
> a bug may use "Development build as of this date" for the current F14
> builds.
Can we split "development build as of this date" into F11 and F14?
cheers,
m
--
m
from the department of opportunity-bearing-tradeoffs...
For XO-1.5 we build our OS images to be a bit "short" of the stated SD
card size, because different SD cards placed in mfg vary in exact
size.
That means we always have a bit of space left over. We could add an
init script that sets up a sma
Assuming OLPC isn't using TRIM support on the SD cards, writes to the
swap space are indistinguishable from writes to any other space on the
card. That means that writes to the swap "partition" could
potentially corrupt other data on the card, especially if it occurs
less than 30s before removal o
On Mon, Nov 22, 2010 at 11:32 AM, C. Scott Ananian wrote:
> just as well. Our superstitions about OLPC's no-swap configuration
> may well prove to be similarly unfounded.
Just to clarify -- side-to-side comparison in the past have shown a
significant improvement. We did get a specially bad-behav
On 22 November 2010 16:41, Martin Langhoff wrote:
> Just to clarify -- side-to-side comparison in the past have shown a
> significant improvement. We did get a specially bad-behaving kernel in
> our F7 builds in that regard, but even F9 builds have shown it to be
> better.
That was an XO-1 compar
As my own clarification: I wasn't dismissing possible performance
improvements (of any kind). I was just commenting on the old "lockup"
bugs, saying this might not actually be related to no-swap-space,
although it's possible memory pressure exacerbates the problem. For
performance issues, you hav
> Downsides
> - Increased SD card wear
For about two years now, I've been defining a swap partition on the
(external) "permanent" SD card I use with my XO-1 systems. So far, I
have never experienced any problems with that setup.
The advantage is to relieve "memory pressure". In particular, I am
On Mon, Nov 22, 2010 at 2:21 PM, Mikus Grinbergs wrote:
>> Downsides
>> - Increased SD card wear
>
> For about two years now, I've been defining a swap partition on the
> (external) "permanent" SD card I use with my XO-1 systems. So far, I
> have never experienced any problems with that setup.
A
On 22 November 2010 16:03, Martin Langhoff wrote:
> - XO-1 gets left alone in VM-lessness.
Regarding the issue where the XO-1 is brought to its knees and stops
responding (or just responds incredibly slowly) due to being
overloaded, 3 new possible options for solving this have cropped up in
the
On Mon, Nov 22, 2010 at 2:37 PM, Daniel Drake wrote:
> 3. Some people think swap will help. F14 images now run UBIFS which
4. Compcache has landed in 2.6.33
http://kernelnewbies.org/Linux_2_6_33#head-2d401df4d54a65a60c31ce7c591cf7660851cfd8
m
--
martin.langh...@gmail.com
mar...@laptop.org --
On Mon, Nov 22, 2010 at 07:50:52AM -0500, Martin Langhoff wrote:
> On Mon, Nov 22, 2010 at 5:55 AM, James Cameron wrote:
> > I disagree. ?The version field is for formal releases. ?The reporter of
> > a bug may use "Development build as of this date" for the current F14
> > builds.
>
> Can we spl
On Mon, Nov 22, 2010 at 11:03:26AM -0500, Martin Langhoff wrote:
> - Slightly longer first boot
> - Slightly more fragile first boot (can we make it failsafe?)
There's no reason to do this during boot. The new partition can be
added after boot, followed by mkswap and swapon.
--
James Cameron
> Assuming OLPC isn't using TRIM support on the SD cards, writes to the
> swap space are indistinguishable from writes to any other space on the
> card. That means that writes to the swap "partition" could potentially
> corrupt other data on the card, especially if it occurs less than 30s
> before
On Mon, Nov 22, 2010 at 6:43 PM, Mikus Grinbergs wrote:
> If "indistinguishable" is true, then there is as much wear to the SD
> card from one file-block written as there is from one swap-block
> written.
Yes.
> I have no measurements whatsoever - but my gut feel is that
> the majority of my SD
On Mon, Nov 22, 2010 at 05:43:18PM -0600, Mikus Grinbergs wrote:
> > Assuming OLPC isn't using TRIM support on the SD cards, writes to the
> > swap space are indistinguishable from writes to any other space on the
> > card. That means that writes to the swap "partition" could potentially
> > corru
>> Note: I'm using an external SD card. So if it fails before the OLPC
>> itself fails, I can at reasonable expense replace this swap device -- I
>> don't have to plan for a definite wear lifetime.
> Are you making regular backups?
Anything that needs to be preserved is copied to a central hard-
28 matches
Mail list logo
