Re: [Server-devel] XS-0.6 -

2009-10-10 Thread Martin Langhoff
On Sat, Oct 10, 2009 at 3:59 AM, Sameer Verma sve...@sfsu.edu wrote: On Wed, Oct 7, 2009 at 5:37 AM, Martin Langhoff martin.langh...@gmail.com wrote: 65d0816e002fe83f4e0130b6a92577377b9fd2e3  OLPC-School-Server-0.6-i386.iso c872907f1f696ea7bb1bb6e95319fa27e62ce76c  

Re: [Server-devel] XS-0.6 -

2009-10-10 Thread Martin Langhoff
On Sat, Oct 10, 2009 at 10:57 AM, Martin Langhoff martin.langh...@gmail.com wrote: We probably need a procedure to dump-and-recreate the Moodle DB because now it is half-there and it probably won't init correctly any more.

Re: Images partitioned right? Good USB drives? (Re: Woodhouse on flash storage)

2009-10-10 Thread Sascha Silbe
On Sat, Oct 10, 2009 at 02:46:17AM +0100, Martin Dengler wrote: Nope (SoaS) - that'll waste your partition table in favour of whatever I copied from my dsd-inspired make-fake-device partition table script[1]. I'd love patches. From that script: NUM_HEADS=16 NUM_SECTORS_PER_TRACK=62 That

Re: rpmbuild macro for libgcc.a location?

2009-10-10 Thread Mitch Bradley
Working on an OLPC package (olpc-bios-crypto, which has a reasonable chance of being upstreamable when it stabilizes)... we keep appending -L lines to make it build in different releases / distros. Is there an rpm macro that points to the location of libgcc.a? Or an elegant way to get it?

Re: Images partitioned right? Good USB drives? (Re: Woodhouse on flash storage)

2009-10-10 Thread Mitch Bradley
You can get the erase block size from SD cards - it's in the Card Specific Data structure - but I don't know of any standard way to get it for USB mass storage devices. Sascha Silbe wrote: On Sat, Oct 10, 2009 at 02:46:17AM +0100, Martin Dengler wrote: Nope (SoaS) - that'll waste your

Re: Images partitioned right?

2009-10-10 Thread James Cameron
On Sat, Oct 10, 2009 at 12:19:56AM -0400, Mikus Grinbergs wrote: p.s. I have been cautioned to avoid guessing when I do not *know*. But from using a large number of external USB devices with XO-1s, my guess is that the XO system is sensitive to the 'timings' presented by those USB