New Fedora Core 7 plan

fedora-logo-bubble
Bill Nottingham from Red Hat released a new plan for Fedora 7 that summarizes the most important topics. And again, I know exactly why I use Fedora: because Fedora is an evolving distribution dedicated to new technology and to good technology.

For example, the plan lists two topics dedicated to the init system: “10. Boot and shutdown speedup” is all about making the current init system a better place and providing a faster and better experience, while “11. Init system work” is about researching a replacement for init. Also the second topic will not bring any new code into Fedora 7 it will (hopefully) create the basis for a init replacement in Fedora 8. That could be Ubuntu’s upstart, btw.
Also the team plans to port Randr 1.2 back to X.Org 7.2 – that would mean that we get full monitor plug&play in X!
Other targets are a better integration of encrypted file systems, the integration of a real time kernel and “8. Rock Solid Wireless” which means in this case out-of-the-box support for all cards and all methods (WEP and WPA).

For me that is what Fedora is about: providing new technology, introducing this new technology to the Open Source community and showing what is possible. As you can see other distributions normally follow (NetworkManager, AIGLX, SELinux, ..) which is by the way one of the big, big advantages of the distribution model.

But of course there are also Fedora specific topics mentioned in this new plan: we will see different releases of Fedora 7 (Server, Gnome, KDE), the merge of the extras and the core build system to one rule-them-all build system, an improvement of the speed of yum/rpm and various other things.

Looks exciting – and I already look out for Fedora 8 and a possible init replacement – Ubuntu, come on, we need a good example here to convince our developers. Integrate upstart fully into Ubuntu and show that it is worth integrating it into Fedora!

4 thoughts on “New Fedora Core 7 plan”

  1. Hmm… I wonder why replacing init ? Why not improving it ? Mandriva already found a way to be SysV init compliant, LSB compliant and speed-up boot process by parallelizing initscripts.

  2. That sounds more like a replacement than like an improvement. Do you have more information about the way how they achieve the goals.
    However, one of the main problems of the SysV system is that it is not event driven but have a fixed set of scripts – that design is not suitable for today’s set ups and application areas.

  3. No, it’s an improvement.

    All initscripts may remain unchanged (and thus, your system will boot in the normal SysV init way) or you can use LSB tags to specify what is required when an initscript is launched. You have a mix of LSB-compliant initscripts and SysV-compliant initscripts without any problem (actually, even on Mandriva, not all scripts are LSB compliant).

    Here’s the beginning of an LSB-compliant script :

    #!/bin/bash
    #
    # Init file for OpenSSH server daemon
    #
    # chkconfig: 2345 55 25
    # description: OpenSSH server daemon
    #
    ### BEGIN INIT INFO
    # Provides: sshd
    # Required-Start: $network $remote_fs
    # Required-Stop: $network $remote_fs
    # Default-Start: 2 3 4 5
    # Short-Description: OpenSSH server daemon
    # Description: OpenSSH server daemon
    ### END INIT INFO

    $network and $remote_fs are “virtual services” which are launched once the network is up (for the first one) and remote filesystems are ready (for the second one).

    Here’s the way this system is working :

    1) Non-LSB services requires every service before them.
    2) _Every_ services after a non-LSB service require the aforementioned non-LSB service.
    3) LSB services requires only the service specified by the LSB tag. BUT they must comply with rule 2).

    Then you “plot” the dependency graph and run things that can be parallelized.

    References :

    http://archives.mandrivalinux.com/cooker/2006-01/msg00000.php
    http://archives.mandrivalinux.com/cooker/2006-01/msg01073.php
    http://refspecs.freestandards.org/lsb.shtml#LSB_3_1_0

Comments are closed.