On Wed, 20 Jun 2012 00:40:38 -0700 Dan Mashal wrote: > Again, I go with a "If it aint broke don't fix it" mentality into > things. > > In my daily life I'm a sysadmin. Figuring out how to do something on > RHEL 5 vs RHEL 6 vs CentOS 5 vs CentOS 6 vs Fedora 13 Fedora 14 > Fedora 15 Fedora 16 Fedora 17 Fedora 18 and what's different between > each and every single one is annoying in every day life at work. > Yeah, it is annoying, but rejecting a change *only* because it is change isn't a strong argument. With such reasoning there wouldn't be PCs in the first place (and btw. steam engine also works, doesn't it, yet trains are now using diesel, if they are not using electricity)... Still I think the changes between Fedora/Red Hat releases are small compared to differences between Fedora/Debian/(Open)Suse or between various M$ operating systems... So either deal with it or decrease the number of concurrently "supported" releases to sane number. You know, people who use Fedora (especially those that contribute) often multi-boot and, frankly, menu like the following one (the kernel versions are semi-random picks of sane numbers out of my head) isn't exactly helpful: * Fedora (kernel-3.6.0-1.fc17) * Fedora (kernel-3.5.7-46.fc17) * Fedora (kernel-3.5.7-42.fc17) * Fedora (kernel-3.6.0-1.fc16) * Fedora (kernel-3.5.7-46.fc16) * Fedora (kernel-3.5.7-42.fc16) * CentOS (kernel-2.16.31.4-35.el5) * CentOS (kernel-2.16.31.3-30.el5) * CentOS (kernel-2.16.31.2-21.el5) * Microsoft Windows * Memtest IMHO it is broken and always was (at the very least it always annoyed the hell out of me that fedora release number wasn't present). But still, currently it is more broken, because grub2-mkconfig writes sub-menued items, while kernel rpm updates grub2 still using the above method, which leads to combination of sub-menus and non-sub-menued items... Cheers, Martin _______________________________________________ design-team mailing list design-team@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/design-team
