Fedora Live CD for Sugar
by Greg DeKoenigsberg
I have:
* A livecd for Fedora 10 devel (rawhide) that allows a Sugar 0.82 boot
option via GDM. We're missing activites, but as those make their way into
rawhide for F10, we will close these gaps quickly.
* A kickstart file that can be used by any Fedora user to generate such an
image trivially.
So. Where shall we host them? Somewhere in Fedora-land, or somewhere in
Sugar-land?
--g
15 years, 6 months
python performance-related issues in Sugar (was Re: Meeting minutes from yesterday)
by Tomeu Vizoso
On Fri, Sep 19, 2008 at 4:55 PM, Greg Dekoenigsberg <gdk(a)redhat.com> wrote:
>
> * Python bloat. Tomeu will send me a note regarding best practices on
> cutting bloat out of python/pygtk apps, and gdk will send around to various
> Python gurus.
Sorry to be so late.
Some performance related issues in Sugar where Python plays a role:
- Activity (and other processes) startup time: mostly due to import
time, loading tons of modules that we never actually use but that get
referenced by real dependencies. This means loading tons of data into
memory (code, comments, etc) plus executing tons of module
initialization code. Lazy loading would help here, but if I understood
correctly, it's unsafe at least in python 2.5.
- Memory usage: the same dependencies creep happen, python processes
don't share python code, resulting in lots of duplication.
We are using a python launcher hack that preloads some modules in a
python interpreter and then forks every time a process is requested.
This saves some startup time and makes python processes save a good
chunk of memory, but introduces subtle bugs all across the
dependencies because modules were initialized in an environment very
different from where they execute later.
So, the Sugar developers would like to know if any other usage of
python in the desktop has found these issues and what the conclusions
are. Could you please share your experiences?
Thanks,
Tomeu
15 years, 6 months
Re: [IAEP] Fedora Live CD for Sugar
by Marco Pesenti Gritti
On Sun, Sep 28, 2008 at 5:25 PM, <s.boutayeb(a)free.fr> wrote:
> Quoting "C. Scott Ananian" <cscott(a)cscott.net>:
>
>> On Thu, Sep 25, 2008 at 4:16 PM, David Farning <dfarning(a)gmail.com> wrote:
>> > On Thu, Sep 25, 2008 at 11:56 AM, Greg Dekoenigsberg <gdk(a)redhat.com>
>> wrote:
>
>> > Once we have a live CD is it hard to generate a a live usb with
>> > persistence. I was able to get a ubuntu live usb going with two partitions
>> > one for storing the cd and another for dynamatic storage.
>> >
>
> Maybe the following tutorial :
> "USB Pendrive Linux install from Linux"
> ( http://www.pendrivelinux.com/2007/05/16/usb-pendrivelinux-install-tutorial/ )
> gives some hints.
>
> From the tutorial : "Installation is simple and just requires copying the .img
> to a USB device and then creating a live-rw partition if you wish to store your
> changes."
On a fedora system is just matter of:
/usr/bin/livecd-iso-to-disk [--reset-mbr] [--noverify]
[--overlay-size-mb <size>] <isopath> <usbstick device>
And there is this for windows:
https://fedorahosted.org/liveusb-creator
Marco
15 years, 6 months
Work items: Fedora on XO testing plan
by Greg DeKoenigsberg
So I've just concluded a meeting with James Laska to figure out the plan.
Here's what we've got so far, with owners. Comments welcome.
Note: we hope to have some of these knocked out by next Tuesday, and the
remainder by next Friday.
1. (jlaska) We will identify a number of high-level testing tasks that
teams will take on. Examples so far: camera support (does the new F10
webcam stuff work with the XO cam?), power management, wireless (weird
drivers upstream?), display/xrandr (does turning the XO sideways do
something crazy?). There will be others, and we will share them when
we've got a first draft.
2. (jkatz?) We need bulletproof docs that allow our testers to
easily put the latest images onto their SD cards.
3. (gdk) Figure out and communicate exactly what spin we're using. i.e.
GNOME. :)
4. (jlaska) Identify the dates for testable release candidates, and sync
those as best as possible to anticipated F10 snapshot releases.
5. (gdk) Build a team structure on the wiki that is time-based, so that
testers can commit to a 4-hour block anytime during the week and join a
team that will work with them. Also identify additional roles like
triagers and leaders which will entail broader responsibility, and recruit
specifically for those roles.
6. (gdk) Further qualify leads by other criteria: having an SD writer
(duh), having a second computer (for transferring images and communicating
on irc, etc.), understanding bugzilla, etc.
7. (jlaska) Identify and document workflow for Fedora-on-XO bugs (use
tracking bugs? how to verify "closed rawhide" bugs? etc.)
--g
15 years, 6 months
Re: Fedora Live CD for Sugar
by Greg DeKoenigsberg
On Thu, 25 Sep 2008, David Farning wrote:
> On Thu, Sep 25, 2008 at 11:56 AM, Greg Dekoenigsberg <gdk(a)redhat.com>
> wrote:
>
> I have:
>
> * A livecd for Fedora 10 devel (rawhide) that allows a Sugar
> 0.82 boot option via GDM. We're missing activites, but as
> those make their way into rawhide for F10, we will close
> these gaps quickly.
>
> * A kickstart file that can be used by any Fedora user to
> generate such an image trivially.
>
>
> Once we have a live CD is it hard to generate a a live usb with
> persistence. I was able to get a ubuntu live usb going with two
> partitions one for storing the cd and another for dynamatic storage.
I was inarticulate.
What I have is, in fact, a Live image, capable of being written to a USB
key with persistence enabled.
Fedora build tools basically make it trivial to build and maintain such
images with default tools.
--g
15 years, 6 months
Package splits between Fedora mainline and OLPC
by Peter Robinson
Hi All,
Reviewing the mail that was sent back in August over the last couple
of weeks I've made a number of updates to Robin's wiki page and filed
a number of Fedora bugs or added the bugs to the wiki where needed as
there's quite a bit of cross over in what I want to achieve for the
Fedora Mini SIG.
https://www.redhat.com/archives/fedora-olpc-list/2008-August/msg00036.html
Now what I'd like to be able to do is work out what the status of the
current fork list is. Of the packages listed in the posting above alot
of them still have a OLPC cvs branch but I suspect that will hang
around even when its merged back into the mainline.
So is someone able to regenerate the split report so we can see where
we are? Even if they don't have time to deal with the merging back in
I can probably compare specs and file tickets linked against the
tracking bug to get them merged if the spec files are essentially the
same.
Cheers,
Peter
15 years, 7 months
Fedora kernel on XO progress -- initrd is loaded in the wrong by place by OpenFirmware
by Jeremy Katz
After going down a few more dead ends than I would have preferred, I've
figured out the root cause of the problems booting the Fedora kernel on
the XO. The base problem is that OFW always loads the initrd at
0x800000 which, while it used to be okay, isn't a safe assumption with
current kernels. With the Fedora kernel images for example, this ends
up being smack in the middle of the .bss and thus things explode.
The correct thing to do with an initrd (according to
Documentation/boot/x86/i386/boot.txt and manual verification with hpa)
is to first check the value of initrd_addr_max (0x22c) in the header of
the bzImage. initrd_addr_max is defined as the maximum safe address for
a byte of the initrd, so you want to load the ramdisk at
initrd_addr_max-len(ramdisk)+1. This then will make OFW's kernel
loading match that of all the other bootloaders used on x86. It might
also be worth checking some of the other newer things (especially the
kernel_alignment field), but I've got no indication of them causing any
problems at all right now with anything that anyone is actually doing in
practice.
Unfortunately, I have nowhere near the forth-fu to whip up a patch to
fix the ramdisk load location. But I'm pretty sure that with such a
patch, a standard Fedora kernel should be able to boot just fine on the
XO hardware which would be a really big win for being able to run any of
the variety of Fedora live images. Mitch -- any chance you could take a
look or give me pointers in the correct direction?
Thanks,
Jeremy
15 years, 7 months
Re: Fedora kernel on XO progress -- initrd is loaded in the wrong by place by OpenFirmware
by Jeremy Katz
On Mon, 2008-09-22 at 11:23 -1000, Mitch Bradley wrote:
> Here is the patch, assuming that the ramdisk memory is not subtracted
> from the available memory size:
[snip]
> I tested it working with a stock OLPC build.
>
> You can put that patch in olpc.fth . I'll incorporate it into the next
> OFW release.
Awesome, and I've tested it with a Fedora kernel and it works there
also. Thanks for the quick turnaround and the ability to just stick the
patch into the olpc.fth file is awesome. For a "screenshot"...
Fedora release 9.91 (Rawhide)
Kernel 2.6.27-0.329.rc6.git2.fc10.i686 on an i586 (/dev/ttyS0)
localhost.localdomain login: root
Last login: Tue Sep 23 01:20:19 on ttyS0
[root@localhost ~]# dmesg |grep OLPC
OLPC board with OpenFirmware CL1 Q2E17 Q2E
OLPC board revision preC200000 (EC=52)
PCI: Using configuration type OLPC
Now to fixing the new things which popped up and are more firmly in the
realm of kernel bugs... :-)
Jeremy
15 years, 7 months
