> The main and probably most major issues outstanding are the
> kernel/boot process - so
> kernel/initscripts/olpcrd/initscripts/upstart/rainbow collection of
> stuff.... of which I have no real idea about. Updates?

It's pretty trivial to disable Rainbow, whereas it's not trivial to
get maintainers of half a dozen packages to adopt patches that let
them deal with Rainbow.  So if you want F11 to work on OLPC, disabling
Rainbow's UID fiddling in the version of Sugar that ships in F11 is
the obvious short-term cure.

Some of the initscript changes related to the bizarre idea of running
the "anti-theft" process as pid 1 so it couldn't be killed by root.
This required changing "init" so it didn't run as pid 1.  This is
trivial to fix by running the anti-theft process (which is a no-op
loop on most OLPCs anyway, and should in a sane world merely exit) on
some other pid, and running init where it belongs.

It looks like perhaps the kernel changes have slipped right through
the F11 schedule.  Is it seriously likely that the F11 kernel
maintainers would adopt a pile of OLPC patches that aren't in the
upstream kernel, between the Beta and the Final F11 releases?  Had
these changes been adopted (by Fedora or by the Linux kernel) early in
the release cycle, they could've been well tested to make sure they
don't introduce any problems into non-OLPC hardware.  But now, it
appears that F11 won't be able to suspend on OLPC, which makes it
almost useless for laptop use (as opposed to developer use when the
laptop is sitting on a desk with permanent AC power).  Such is the
price of firing all of your kernel developers.

Even the bug report that tracks the kernel power management changes
has fallen into disarray (the Fedora "Bug Zapper" zapped it in November
and nobody has bothered to fix it since):


Devel mailing list

Reply via email to