On Thu, Sep 01, 2011 at 12:01:13PM -0400, Genes MailLists wrote:
On 09/01/2011 09:44 AM, Josh Boyer wrote:
> (Yes, we are aware of the fact that some people want to stick with F14
> to avoid Gnome3. That's outside of the scope of the kernel and we
> really don't want to discuss it here.)
Rather, I think it is the fear of systemd not yet being reliable (on
F15 anyway), especially for network coupled services being started at
boot without human interaction, that is likely the bigger concern. This
is slowing F15 adoption on non-desktop/server type setups.
Testing systemd on laptop/desktop - gives folks the opportunity to
explore how well systemd is working and to enjoy the newer kernels.
Since we're not supporting upstart in F15, it does make sense to try
and move 2.6.40 onto F14 to hold folks until they get more comfortable
(presumably F16) that systemd will be trustworthy for standalone boxes.
systemd is supported on F15. There was an update released for it
Anyway, that's beyond the scope of the kernel. There's nothing we can
do about whatever reason people have for sticking with F14, unless that
reason is something broken in a newer kernel (which they probably
wouldn't know if they're sticking with F14, but I digress.)
It seems feasable so to me, but does require updates to mdadm,
module-init-tools, procps and Mesa (and maybe more). If I remember
rightly, I needed those to test newer kernel on F14.
And microcode_ctl. Those are the minimums to be safe, although the
whole point of calling it 2.6.40 was to avoid the versioning
I'm also concerned about the older xorg stack with the newer drivers,
but that might just be my unfamiliarity with how intertwined they are.
Also, 184.108.40.206 is running beautifully for me on F15 - auto sched is
rather brilliant - esp when compiling -j8 (or whatever) .. thank you!
Great, glad it's working well for you.