Mmm, It is true I am running a non-Ununtu kernel ...
Perhaps because the Ubuntu Xen kernel, certainly upto Gutsy, was simply too unstable to be of any use. I'm running ~ 20 Xen instances across 4 servers and spent a LONG TIME trying to make raw Ubuntu work. My eventual solution was to switch to a RH2.6.21 kernel, ALL of my problems have gone away and I now experience 100% uptime as opposed to continuous problems every day. If you're going to tell me that I can't run Ubuntu and use a recent alternative kernel when Ubuntu's kernel is a paper weight, then you're telling me I need to switch to Fedora - which given my investment in Ubuntu I'd rather not do. I can't think of any reason why it would not be possible to add a little flexibility into package upgrades to make them ever so slightly backwards compatible and give people a little wriggle room when Ubuntu is less than perfect (never happens obviously, but just in case ... ;-) ) Another example; they've put something rather nasty into rsync, so it generates lots of errors when you run the Gutsy version on a 2.6.21 kernel. Apparently the distro version RELIES on a specific feature in the 2.6.22 kernel ... Arhrhrhrhrhrh! Calling all programmers; don't let user-level applications fail just because someone adds "0.0.01" to a kernel version!! -- [hardy] "ip" broken https://bugs.launchpad.net/bugs/192294 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
