Updating fedora core 2 to fedora core 3
We target for inclusion in the Fedora project after the OGo 1.0 release.
Quick Links: apt4rpm, yum, FC Core 3, FC Core 2, FC Core 1.
In general the regular RPM packages should work out of the box.
RPM installation procedures apply and you might want to use Kelley's RPM install script.
The complete directions to set up your source tree are thus: A pain in the butt but at least you only have to do this once after installing a new kernel-source RPM.
A posting by Dan Davis ([email protected]) on the Asterisk Developers Mailing List:"Fedora Core Two will work if you update with the new Fedora . Linux26"Instructions for getting zaptel to work with Fedora Core 2 using 2.6.7 kernel: Getting asterisk to work on fedora core 2 is no problem. The kernel (2.6.5) source code provided with Fedora Core 2 is missing some auto-generated components.
I had to comment out the "owner" lines in wcusb.c and xpp/xpp_usb.c. However, it wouldn't install properly since it was trying to install to /lib/modules/2.6.15-prep, not /usr/lib/2.6.15-1.2054_FC5.For SOPE 4.4 and OGo 1.0a the Fedora Core 3 are build on that platform.The later OGo 1.0a versions perform all the database setup and configuration automagically (unless you already did that), so you don't need to perform any further setup.I found that the easiest way to get around all those issues was to download a new kernel source code like 2.6.7 from Make sure it works by starting the script/etc/init.d/zaptel startdoing lsmod should show the wcfxs and zaptel module being installed. Hope all of this help, Jean-Yvesaddon: If you get errors about pivotroot not being able to mount root, and it dies while trying to run init."pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed"You are using the "ext3" filesystem for /boot.Changing "CONFIG_EXT3_FS=y" in the .config solves the problem.