Moving from rawhide to F16alpha

Well the test laptop was stable until today when updates seem to have caused all kinds of issues.. and then I realized the issue was that rawhide moved from F16->F17. I think I am going to reinstall the laptop to being F16 alpha later this week and see how it progresses over the span of the week. Once we get to the betas I will jump back to rawhide to see if I can cause the laptop to burn out again :).

Currently the 3.0 kernels and systemd are fighting over system locks. As can be seen by this bugzilla, I am not sure who is winning.


Boot Times are Important.. sort of

Adam W was at CLS and has been going over ideas he ran into. One of them was a talk by Dan Allen of Mojave Linux on speeding up boot times of Jboss.

While I agree that starting times do matter for laptops and such.. for servers they are really a joke. Mainly because all of Linux could start up in 10 seconds, but the real wait is all the BIOS/EFI startups which Linux has no power over. Two weeks ago, I spent the week with Kevin Fenzi inventorying old hardware and installing new hardware at the Red Hat/Fedora Phoenix bunker. Most of our time was spent waiting.. (average of 4 minutes per server.. the newer the server, the longer the time) for a tiny period of time when we could enter a keystroke to enter some BIOS menu. Go too soon and they keyboard buffer is overrun, wait to long and you have 1-3 more minutes waiting until you can press it. For one server, we spent close to an hour trying to get all the menus gone through so we could actually get to the point of running Linux on it. And even after going into the menus and turning on "fast" boot options, the servers still take 2-4 minutes to get to a grub prompt.

And yes during those times we were going on yak shaving expeditions or trying to figure out how many prime numbers were below a googol.. but for the most part an even long RHEL-5 boot time with all the trimmings is stunningly fast compared to getting the server to booting. Until that problem is really solved, I think most boot time arguments are going to just go over server administrator heads.

This slowness is a primary reason why Infrastructure uses virtual machines everywhere. We can reboot a virtual machine in far less time than it takes for the real hardware version to think about rebooting. In the virtual server case, slow services are more detectable. I can no longer reboot a box, get in the car, go the coffee house, come back wait for the coffee to cool and then be at a Grub prompt. I might get to the door when the prompt is waiting for me.