10 years, time to change

It has been 10 years since I joined a small company called MandrakeSoft at that time.

When I first arrived, I was asked "What do you want to work on ?" and I said "I don't know, I use GNOME at home..." and you know the story ;)

Now is a good time to change, so I'm leaving Mandriva at the end of this month (I'm already off, so don't search me on irc / mail ).

It has been a pleasure to work everybody in Mandriva company and community.

GUADEC, PACS

and since yesterday, I have a PACS (name of civil union in France) with my beloved girlfriend (now, my wife) !

Mandriva Linux 2010 Spring Beta 1 released : with GNOME 2.30 and GNOME-Shell

 Time has came for first beta release for 2010 Spring version of Mandriva Linux.  It's now available through 32 and 64 DVD isos, as well as live-CD isos for GNOME and KDE on public mirrors

• 2010 Spring planning
• Detailed information about Beta1 release

This release is including GNOME 2.30 (released on April 1st) and a preview edition of GNOME-Shell, which will be part of GNOME 3 (which is planned for release on september 2010). Of course, KDE 4.4.2 is also available, as well as various updates for many programs in the distribution.

As usual all your feedbacks are really important to help in improving global quality of distribution. You can report improvements proposals and/or bugs in Mandriva Bugzilla.

Enjoy!

Nokia N900 : not impressed either

No, Cody you aren't alone (but I can't comment on your blog, it asks to login and I don't have an account on blogs.gnome.org) : I have the same feeling regarding Nokia N900 and I'm not impressed by a "already obsolete" product (or should I say platform), by Nokia own words (but not expressed in that way) . The good point is the money they injected in free software companies isn't lost and morphed in improvement in various projects (Telepathy, etc..) but that's it.

I'm much more impressed by Palm Pre and I'm waiting for it to be available in Europe.

Boot splash evolution in Mandriva Linux

For some time, I've been working on adding Plymouth support for our next Mandriva Linux 2010 release, as graphical boot splash and I thought it could be interested to do a recap of the various solutions we used in our distribution over the years.

Mandriva Linux (Linux-Mandrake then) was one of the first Linux distributions to ship with a graphical boot :

• in 2000 (yes, 9 years ago !!), for Linux-Mandrake 7.2, we integrated Aurora (written by Egil Möller who joined Mandrakesoft to work on it at that time), allowing users to control and follow boot with keyboard and mouse, before X was started. 
• in 2002, we switched to Bootsplash, which was kernel based and allowed also to polish VT (a nice touch).
• in 2008, we switched to Splashy, mostly because Bootsplash was becoming deprecated by Splashy and could not run on non-x86 platform and was a pain to maintain in kernel.
  
• yesterday, we switch to Plymouth. It will be available for the first time in Mandriva Linux 2010 beta (available tomorrow). 

Why did we switched to Plymouth :

• it supports Kernel Mode-Setting, which reduces screen flickering, permits smooth transitions between boot phase and X startup. 
• it still works on VESA framebuffer. For chipsets not yet supporting KMS, we can still have graphical boot, so no feature regression.
  
• Plymouth is much more customizable than Splashy, allowing nice UI effects.
• It has a nice and simple script language (from Charlie Brej) : you don't need to code in C to write a theme. I was able to write a theme which looks like our current splashy theme in about a day (discovering the language at the same time and with examples from Charlie).
  
• Plymouth authors are extremely responsive and inclusive : I got commit privileges only two days after sending my first patches (and after my fd.o account was fixed ;)
• We are not alone to use Plymouth : our Fedora friends were the first to integrate it and we can share our experiences and expertises in graphical boot, thus improving the entire Linux ecosystem.
  

So far, we are extremely happy of the result : Mandriva Linux 2010 beta looks very nice (even if plymouth for this beta doesn't feature text support, it does now on cooker).

We hope you will like it, so don't forget to test Mandriva Linux 2010 beta when it is released (and did I say it will have GNOME 2.27.90 in it too ? :)

GNOME 3.0 planning announced

After a lot of thinking


GNOME release team is happy to announce


planning for GNOME 3.0

Enjoy (other members of Release Team did blog about it too : Vincent, Lucas, Andre).

Now, back to work, folks !

Speedboot explained

For those of you not following Mandriva Linux development closely, we just released Mandriva Linux 2009 Spring Beta and this is our first release featuring speedboot feature, in its initial phase.



Booting fast, is it important ?
Boot time has been a hot topic for the past few months in Linux community, either by chip and SSD manufacturers who want to show how fast their hardware can go when software is fixed properly (Moblin fastboot) or even by distributions, mostly on Netbook and OEM, such as various Mandriva Linux based products, like Hercules eCafé, G-dium, TouchDiva which are using Mandriva finit.

However, most of those initiatives are focused on fixed hardware configuration and software install, which ease boot speed optimization according to system specifications.

Unfortunately, on a generic distribution where many features are available and might be enabled or not, based on user choices, not all optimisations can't be applied blindly.

This is why we have created speedboot for Mandriva Linux 2009 Spring.

What is speedboot ?

Speedboot is a specific boot time mode on a standard Mandriva Linux 2009 Spring where graphical system is started as early. This mode allows users to interact with their system much earlier than it was possible before, so they don't feel frustrated because their system isn't ready yet.

In Speedboot mode, some tasks are done very early in the boot process, other are delayed after graphical display manager has been displayed, and some tasks are ignored completely.

Speedboot has been designed to be transparent for our users : if system meets some criterias (not using network based authentication, not using encrypted partitions, ...), speedboot will be automatically enabled and used, with a fallback mecanism, in the event display manager could not be started properly, so standard (ie slow) boot would still be used to start display manager (for instance, if you boot on a new kernel and your dkms driver haven't been rebuilt yet). Of course, users will also have the possibility to completely disable speedboot if they don't like it.

But you are cheating, you are slowing boot process by running stuff in the background !!
I'm not sure it is cheating, but it is true we are deferring some tasks which used to be executed before display manager. It is a matter of perception for users. For years (since 2002), Mandriva have been starting display manager as soon needed services for X and display manager where running, to give a better user experience in the boot process, so some services (network, ssh server, etc..) were already being started in the background. We improved this system by using a parallel initscript system (prcsys) in 2006, allowing to reduce again boot time and in Mandriva Linux 2009.0, we tuned the system again and added readahead and preload, which, in most cases, reduced again boot time.

However, we also discovered those techniques didn't work everywhere : not everybody has a fast harddrive or SSD, so readhead could sometime slow boot time. Based on user configurations and system power, parallel initscript could sometime "clutters" initial boot time (since some services had no dependencies on other services, they were started early and precious CPU cycles (or IO) were used by them instead of the critical path for display manager startup.

So, we needed to find a path between a fully sequential system (à la finit) which can't be generalized on everybody system, and a fully parallel system (à la prcsys) which can't be optimized easily. We already did some of those optimisation for Mandriva 2009.0 and speedboot is the next step.

So, what do you really do in speedboot mode ?
We are still using standard initscripts, which have been modified a little to do the following :
- start udev almost immediatly after rc.sysinit is up, but do not do ask for coldplug events (this is what eat a lot of CPU on standard systems). Instead, ask udev to coldplug specific components which are needed for Xorg to start. And do this in the background
- check filesystems
- mount filesystems
 - in a new specially created runlevel (and in background) start display manager and its dependencies (syslog, dbus, hal, acpid)
- do some cleanups on various directories

- wait until display manager is up and running (with a timeout, just in case) and then continue the standard boot process in runlevel 5 (using prcsys to use parallel init)
- do not use readahead (nor sreadahead) : atm, I've been confusing on average harddisk and readahead doesn't help in that case, because we are already using too much IO on the disk and even idle IO are slowing the boot. I'll need to check on fast harddrive and SSD and maybe only enable readahead depending on the disk speed (but I'm not a fan of this, because it implies running a disk speed test at some point)

How can I test speedboot ?
That is quite simple : download Mandriva Linux 2009 Spring Beta release, install it and add speedboot to your kernel cmdline (either manually on in your grub / lilo configuration). Be aware speedboot can cause issues like changing kernel version (because it is started before dkms). Those issues will be fixed in future pre-releases of Mandriva 2009 Spring, as well as automatic activation of speedboot. Anyway, if you found issues, please fill bug reports on our bugzilla, against initscripts components or email cooker mailing list.

You lied, bootchart says my boot time is longer with speedboot than without
Well, unfortunately, bootchart is measuring the entire system boot time and with speedboot, we are favoring X early startup (what I call "perceived boot time") at the expense of total boot time (ie when all services are up and running). If you want to compare bootcharts with and without speedboot, look at timing for gdmgreeter (or kdmgreeter) startup. This will mean system is ready for login. On average, we found a gain of 10s, which means you can get graphical login available between 8s and 20s (this varies on your system specification). You can check some results here : you get kdm greeter in 12s instead of 23s. And you can also check the influence of using ext4 vs ext3, which isn't giving that much gain some people thought it would : just 1s with speedboot for kdm greeter.

But you are slowing the desktop login !

Yes, we might, but not that much. Possible solutions would be to start the various services with ionice / nice, but it is a little dangerous since they should be renice back to standard niceness once login is finished and you can't be sure to be able to do that without any leftover. Some people also suggested to us at command but this would not integrate transparently with initscripts provided by various services.

Why didn't use upstart ?
We tested it but it is still very young, changing a lot, breaking its configuration file between major releases and to be able to have a full event based system would require rewriting all initscripts to upstart format, without being sure we would have gain. So, for now, we are keeping with standard technologies, which are LSB compliant as a bonus.

We hope you will like speedboot and are waiting for your feedback, either on cooker mailing list or bugzilla.

Enjoy !