When I decided to use Fedora Rawhide, I knew to expect some packages to be broken. I could live with that since the broken packages come only once in a while, and I knew I could fix most errors. In general, Fedora Rawhide is quite usable.
I also use Debian Lenny/SID, and some broken packages also occur in SID. Same banana. That is what you get when you live in the bleeding edge. The reason I made this post is to warn others who might also be using Rawhide. Pablo Manalastas *** --- Mhac Janapin <[EMAIL PROTECTED]> wrote: > And these kind of things makes me think twice > regarding a Fedora install. > :-) No flaming intended, just stating a fact of > life. > > On 7/15/07, ralph bacolod <[EMAIL PROTECTED]> > wrote: > > > > so this is a pre-compiled kernel? and a > development kernel to boot! > > > > > > On Sat, Jul 14, 2007 at 11:30:07PM -0700, Pablo > Manalastas wrote: > > > In my Yahoo blog: > > > > > > http://blog.360.yahoo.com/blog-0OCENX4haau1oA38TsiK4DP2YLk-?cq=1&p=89 > > > > > I mentioned an error in the latest release of > the > > > kernel for Fedora Rawhide. Here is the post: > > > > > I am running Fedora Rawhide, the latest > development > > > release, which is Fedora version 7.89. > Yesterday, I > > > installed the latest kernel update, which is > > > 2.6.23-0.15.rc0.git1.fc8. So > > > vmlinuz-2.6.23-0.15.rc0.git1.fc8 was installed > in > > > /boot, and the modules were installed in > > > /lib/modules/2.6.23-0.15.rc0.git1.fc8/. However, > when > > > you do the command > > > > > uname -r > > > > > you get the version/release number > > > 2.6.22-0.15.rc0.git1.fc8. That is 2.6.22 and not > > > 2.6.23. > > > > > So during boot up, there were so many modules > that > > > were not loaded, as the kernel could not find > them, > > > since they were expected to be in > > > /lib/modules/2.6.22-0.15.rc0.git1.fc8. Why did > the > > > Fedora kernel developers release such an > incorrectly > > > compiled kernel? > > > > > Of course there is an easy fix. Just create a > symbolic > > > link /lib/modules/2.6.22-0.15.rc0.git1.fc8 to > > > /lib/nodules/2.6.23-0.15.rc0.git1.fc8, and > reboot, and > > > the problem is solved. What about the version > > > numberings in the kernel and the modules, > themselves? > > > I wonder why the link works when it does not fix > the > > > internal version numbers. > > > > > In the meantime, I am waiting for the next > kernel > > > update. > > _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
