Fedora 11 delivered our heavenly right to say…
Oops. I really meant Apollo 11 delivered…
But it’s not July 20 anymore, so about Fedora 11:
- Overall, no big problems
- Fedora Project slipped their final release schedule a couple of weeks, so I didn’t get started trying Fedora 11 until mid-June.
- VMware Server 1.0.x still doesn’t work with the 2.6.29 kernel(s) in Fedora 11. It appears that a one line kernel change is needed (assuming VMware doesn’t fix directly). However, I’ve never built a linux kernel before, and my first attempts have failed.
- The nastiest surprise, for me, was confusion about BIND. I’m used to Fedora putting BIND in a chroot’d jail. Fedora 11 seems to eschew actually doing this, but provides the /var/named/chroot directory hierarchy as if the jail still exists. I don’t find anything in the release notes about any of the BIND changes, and the additional DNSSEC support in BIND 9.6 threw me off temporatily, since I don’t know much about DNSSEC. It took me a couple of hours to sort everything out, and my current solution is a bit clumsy, but seems to work.
There are other awkward aspects, such as the need for a /boot ext3 partition when trying to use ext4 for the rest of the filesystems, but these are adequately documented in the release notes, so not big problems for me.
I put Fedora 11 on my primary mail/web/DNS server yesterday, and all seems OK so far. (This post is stored on that server.) But the machine that depends on VMware Server is still running Fedora 10.