The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Fedora Core 1 to Fedora Core 2 Upgrade

Discussion in 'General Discussion' started by [iG], Aug 7, 2004.

  1. [iG]

    [iG] Member

    Joined:
    Oct 16, 2002
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    As we have decided to go down the Fedora Path, instead of the RHEL path, we now have to contend with Fedora's really short release cycle.

    To comprehend this, we will be writing how-to's for those interested to continually migrate their Systems to the newest Fedora Core releases.

    Fedora Core 1 EOL's very soon, and to that end, we have prepared a painless upgrader to upgrade Fedora Core 1 systems to Fedora Core 2.

    If any mods/admins view this thread, could they please sticky it.


    The main advantages of this upgrade include

    - 2.6.7 Kernel, bringing more security and speed to Systems (Especially P4's/Xeon's with Hyperthreading)
    - Python 2.3
    - RPM 4.3
    - GLibc 2.3.3

    and countless package upgrades providing new features and security enhancements.

    Since Fedora Core 1 uses an older version of Python & RPM, if you try to use Yum to update your system (i.e. upgrade the fedora-release package, and try to

    yum upgrade) things will break.

    To that end, we have provided 2 base package upgrades that will update your system's base components (RPM, Python, GLibc etc) to make the remainder of the

    upgrade easy.

    Note: Before you start bashing away at your keyboard, there is a FULL command listing below to make the upgrade process fully automated, so just read below,

    but dont skip anything as it is important.


    Firstly, you need to download base package update, which can be found here http://files.oktagone.net/fedora/fc1tofc2upgrade/base.tar.bz2 (~81MB)

    If anyone has any queries as to exactly what this package contains, here is the list of files.

    The second package is a Xfree to xorg-x11 transition pack. Since Xfree has screwed up their Distribution licensing now, Fedora and most other respectable

    *nix distro's have moved from Xfree to xorg.

    The package can be grabbed from http://files.oktagone.net/fedora/fc1tofc2upgrade/xfree.tar.bz2 (~30MB)

    File contents


    The next step is to clean up the dependancies that yum will have problems with. Dont worry about removing these rpm's below because yum will simply reinstall

    them.

    rpm -e exim --force

    Next, you want to get a new yum.conf so you have a "reliable" and stable update source.

    Grab our tested yum.conf - http://files.oktagone.net/fedora/fc1tofc2upgrade/yum.conf

    Now, we are ready to use yum. It's sexy and easy. Just type yum update, and Yum will download all the headers, and RPM's as needed. Remember to press Y once

    the deps testing is done. If you have any errors and yum cannot complete due to package conflicts, please paste them so i can debug why this happens, and

    give you a solution.

    When yum is complete, you will need to perform a reboot to boot into the new kernel you have aquired. Before doing this, it's important to check

    /boot/grub/grub.conf to see that the new kernel (2.6.7-1.494.2.2) is there.

    Your grub.conf should look something like this

    default=0
    failsafe=1
    timeout=10
    splashimage=(hd0,0)/grub/splash.xpm.gz
    title Fedora Core (2.6.7-1.494.2.2)
    root (hd0,0)
    kernel /vmlinuz-2.6.7-1.494.2.2 ro root=LABEL=/1
    initrd /initrd-2.6.7-1.494.2.2.img
    title Fedora Core (2.4.22-1.2197.nptl)
    root (hd0,0)
    kernel /vmlinuz-2.4.22-1.2197.nptl ro root=LABEL=/1
    initrd /initrd-2.4.22-1.2197.nptl.img


    (Note: The failsafe line isnt necessary if you dont have it).

    If it looks good, exit your text editor, and reboot.

    If all went to plan, your box should be back up in a few minutes.

    Once its live again, there's a few things you need to do to fix up services.

    First, you want to tell cPanel to use Yum now instead of APT, so we run

    touch /var/cpanel/useyum


    Then, we want to fix exim, since YUM installs a standard Fedora version of it, which wont work with cPanel.

    Simply grab the cPanel Exim RPM from here - and install it.
    http://updates.cpanel.net/exim-cpan...rite_mailman2_maskedmailtrap_exiscan.i386.rpm

    rpm -Uhv exim* --force is the command you'll need to use, since exim is allready installed, and may conflict with a package called "setup"

    Then, rebuild Apache using /scripts/easyapache. Option 4 is reccomended.

    Now, your all done!

    Go into WHM, and check your services stats. Everything should be running, and your system is now running the latest, fully updated Fedora Core 2.

    If anyone needs help with this upgrade feel free to PM me, however any problems should be posted below so that others can benefit from your feedback.

    Thanks!


    COMMAND OUTPUT

    Step 1: Setup Directory and get required files.
    mkdir upgrade
    cd upgrade
    wget http://files.oktagone.net/fedora/fc1tofc2upgrade/base.tar.bz2
    wget http://files.oktagone.net/fedora/fc1tofc2upgrade/xfree.tar.bz2

    Step 2: verify the MD5's by typing
    md5sum base.tar.bz2
    md5sum xfree.tar.bz2

    Step 3: Extract RPM's and upgrade them
    tar -xvjpf base.tar.bz2
    tar -xvjpf xfree.tar.bz2
    rpm -Uhv base/*.rpm
    rpm -Uhv xfree/*.rpm

    Step 4: Fix Deps and run yum
    rpm -e exim --force
    wget http://files.oktagone.net/fedora/fc1tofc2upgrade/yum.conf -O /etc/yum.conf
    yum update

    Step 5: Check boot stuff
    nano /boot/grub/grub.conf

    Step 6: Reboot
    reboot -n

    Step 7: Fix Exim / Apache
    touch /var/cpanel/useyum
    rpm -Uhv http://updates.cpanel.net/exim-cpan...rite_mailman2_maskedmailtrap_exiscan.i386.rpm --force
    /scripts/easyapache


    (end)
     
  2. haze

    haze Well-Known Member

    Joined:
    Dec 21, 2001
    Messages:
    1,550
    Likes Received:
    3
    Trophy Points:
    38
    Rather than uninstalling exim, would it not be a better idea to add it to yums skiplist ?
     
  3. picoyak

    picoyak Well-Known Member

    Joined:
    Jun 10, 2004
    Messages:
    72
    Likes Received:
    0
    Trophy Points:
    6
    Thanks, iG for the how-to! :) I was actually wondering just how I'd handle that move.

    I'm assuming that the only probs you saw are covered in the instructions above? Just curious, do you think it matters at all what ver cpanel we're currently at?

    I'm due to upgrade exim anyhow, just as soon uninstall it.

    I'm gonna give this a go tomorrow most likely. Thanks again!
     
  4. residenta

    residenta Registered

    Joined:
    Jun 12, 2004
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    I thought I'd bite the bullet and upgrade while server usage was low and I had a helpful how-to. :) Thanks kindly.

    However, I've gotten stuck. Here's what's happened so far...

    Installing Packages:

    # rpm -Uhv base/*.rpm
    warning: base/authconfig-4.6.2-1.i386.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2
    error: Failed dependencies:
    /usr/bin/python2.2 is needed by (installed) redhat-config-mouse-1.1.2-1
    /usr/bin/python2.2 is needed by (installed) redhat-config-network-tui-1.3.10-1
    /usr/bin/python2.2 is needed by (installed) redhat-config-nfs-1.1.3-1
    /usr/bin/python2.2 is needed by (installed) redhat-config-samba-1.1.4-1
    /usr/bin/python2.2 is needed by (installed) redhat-config-securitylevel-1.2.11-1
    /usr/bin/python2.2 is needed by (installed) redhat-config-bind-2.0.0-18
    /usr/bin/python2.2 is needed by (installed) redhat-config-date-1.5.25-1
    /usr/bin/python2.2 is needed by (installed) redhat-config-keyboard-1.1.5-2
    /usr/bin/python2.2 is needed by (installed) redhat-config-kickstart-2.4.2-1
    /usr/bin/python2.2 is needed by (installed) redhat-config-language-1.0.16-1
    /usr/bin/python2.2 is needed by (installed) redhat-config-rootpassword-1.0.6-2
    /usr/bin/python2.2 is needed by (installed) redhat-config-soundcard-1.0.8-2
    /usr/bin/python2.2 is needed by (installed) redhat-config-users-1.2.4-1
    libtcl8.3.so is needed by (installed) expect-5.39.0-96.1

    # rpm -Uhv xfree/*.rpm
    warning: xfree/chkfontpath-1.10.0-1.i386.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2
    error: Failed dependencies:
    libc.so.6(GLIBC_2.3.4) is needed by xorg-x11-6.7.0-2

    I'm not sure if those were OK or not since it was noted that dependencies would be fixed. So I moved along...

    # rpm -e exim --force
    rpm: only installation, upgrading, rmsource and rmspec may be forced

    So I removed the force, "rpm -e exim" and got a couple more failed dependency messages but I lost the exact response.

    I then got the provided yum.conf and ran yum update...

    # yum update
    Gathering header information file(s) from server(s)
    Server: Fedora Core 1 - i386 - Base
    retrygrab() failed for:
    http://mirror.oktagone.com/pub/fedora/linux/core/1/i386/os/headers/header.info
    Executing failover method
    failover: out of servers to try
    Error getting file http://mirror.oktagone.com/pub/fedora/linux/core/1/i386/os/headers/header.info
    [Errno 4] IOError: HTTP Error 404: Not Found

    Help! What can I do from here? I'm using cPanel 9.4.1-R64.
     
  5. haze

    haze Well-Known Member

    Joined:
    Dec 21, 2001
    Messages:
    1,550
    Likes Received:
    3
    Trophy Points:
    38
  6. picoyak

    picoyak Well-Known Member

    Joined:
    Jun 10, 2004
    Messages:
    72
    Likes Received:
    0
    Trophy Points:
    6
    from the looks of things, at the point where we'd run 'yum update', shouldn't we be dealing with $releasever 2 at that point?

    From the links you posted, you're looking toward
    /pub/fedora/linux/core/1/$basearch/os/

    Shouldn't it be
    /pub/fedora/linux/core/2/$basearch/os/ ?

    Not sure exactly how to deal with that, or where $releasever comes from in the yum process. Just throwing out ideas. But by url, mirror.oktagone.com/pub/fedora/linux/core/2 does exist, while mirror.oktagone.com/pub/fedora/linux/core/1 does not.
     
  7. [iG]

    [iG] Member

    Joined:
    Oct 16, 2002
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Hi Guys,

    Clarifying,

    If you have any "redhat-config-XXX" RPM's installed, you'll need to rpm -e them.

    For example,

    rpm -e redhat-config-mouse-1.1.2-1 redhat-config-network-tui-1.3.10-1 redhat-config-nfs-1.1.3-1 redhat-config-samba-1.1.4-1 redhat-config-securitylevel-1.2.11-1 redhat-config-bind-2.0.0-18 redhat-config-date-1.5.25-1 redhat-config-keyboard-1.1.5-2 redhat-config-kickstart-2.4.2-1 redhat-config-language-1.0.16-1 redhat-config-rootpassword-1.0.6-2 redhat-config-soundcard-1.0.8-2 redhat-config-users-1.2.4-1.

    It is safe to remove thse, as Yum will reinstall them later if needed.

    This is part of the "base.tar.bz2" package - it contains the "fedora-version-2" RPM, which will tell yum your $releasever is 2.

    I would NOT RECCOMEND using that howto; we have tried it twice on different boxes, and it causes HUGE problems with RPM/Pythin incompatibilities. In one instance, Yum had completed the upgrade, but when i did a rpm -q package, there was both the original, and new versions installed. (I.e. i had Fedora Core 1 & 2 installed together). Nightmare!

    If anyone else is having probs, let me know and i'll try to resolve them.
     
  8. picoyak

    picoyak Well-Known Member

    Joined:
    Jun 10, 2004
    Messages:
    72
    Likes Received:
    0
    Trophy Points:
    6
    Thanks for the clarification, iG

    Not to be a pain, or make this more complicated than need be, but since you did mention potential probs with python, my first step for me produces the same result as with residenta....

    Code:
    rpm -Uvh --test base/*.rpm
    
    warning: base/authconfig-4.6.2-1.i386.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2
    error: Failed dependencies:
            /usr/bin/python2.2 is needed by (installed) redhat-config-date-1.5.25-1
            /usr/bin/python2.2 is needed by (installed) redhat-config-language-1.0.16-1
            /usr/bin/python2.2 is needed by (installed) redhat-config-mouse-1.1.2-1
            /usr/bin/python2.2 is needed by (installed) redhat-config-network-tui-1.3.10-1
            /usr/bin/python2.2 is needed by (installed) redhat-config-nfs-1.1.3-1
            /usr/bin/python2.2 is needed by (installed) redhat-config-securitylevel-1.2.11-1
            /usr/bin/python2.2 is needed by (installed) redhat-config-bind-2.0.0-18
            /usr/bin/python2.2 is needed by (installed) redhat-config-keyboard-1.1.5-2
            /usr/bin/python2.2 is needed by (installed) redhat-config-kickstart-2.4.2-1
            /usr/bin/python2.2 is needed by (installed) redhat-config-rootpassword-1.0.6-2
            /usr/bin/python2.2 is needed by (installed) redhat-config-users-1.2.4-1
            /usr/bin/python2.2 is needed by (installed) redhat-config-samba-1.1.4-1
            /usr/bin/python2.2 is needed by (installed) redhat-config-soundcard-1.0.8-2
    hmmm... what about python here? ...
    Code:
    rpm -qa | grep -i python
    
    gnome-python2-2.0.0-2
    rpm-python-4.2.1-0.30
    python-devel-2.2.3-7
    gnome-python2-canvas-2.0.0-2
    python-docs-2.2.3-7
    mod_python-3.0.4-0.1
    python-2.2.3-7
    gnome-python2-bonobo-2.0.0-2
    python-optik-1.4.1-1
    gnome-python2-gtkhtml2-2.0.0-2
    libxml2-python-2.6.6-3
    python-tools-2.2.3-7
    libxml2-python-2.6.6-3
    python-tools-2.2.3-7
    Know that I have not begun this upgrade yet, just testing the process step-by-step.

    Any other thoughts on this? Meanwhile I'll look to resolve that dependency, I guess.

    EDIT - I found this oddity in /usr/bin ...

    Code:
    ls -la /usr/bin/python*
    -rwxr-xr-x  2 root root 800436 Oct 15  2003 /usr/bin/python*
    lrwxrwxrwx  1 root root      6 Jun  9 00:18 /usr/bin/python2 -> python*
    -rwxr-xr-x  2 root root 800436 Oct 15  2003 /usr/bin/python2.2*
    Why in the world would there by a symlink python2->python ??? :confused:
     
    #8 picoyak, Aug 9, 2004
    Last edited: Aug 9, 2004
  9. [iG]

    [iG] Member

    Joined:
    Oct 16, 2002
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    You need to remove all of those redhat-config RPM's.

    I pasted code above to rpm -e them.
     
  10. picoyak

    picoyak Well-Known Member

    Joined:
    Jun 10, 2004
    Messages:
    72
    Likes Received:
    0
    Trophy Points:
    6
    I'm awake now :D
     
  11. icanectc

    icanectc Well-Known Member

    Joined:
    Mar 10, 2003
    Messages:
    344
    Likes Received:
    0
    Trophy Points:
    16
    I am trying this on a test Fedora Core 1 Server and we get the following:

    root@ptr [/upgrades]# rpm -Uhv base/*.rpm
    error: Failed dependencies:
    pygtk2-libglade is needed by authconfig-gtk-4.6.2-1 //Was resolved by installing pygtk2-libglade

    root@ptr [/upgrades]# rpm -Uhv xfree/*.rpm
    error: Failed dependencies:
    libc.so.6(GLIBC_2.3.4) is needed by xorg-x11-6.7.0-2
    /usr/bin/ttmkfdir is needed by xorg-x11-truetype-fonts-6.7.0-2
    /usr/bin/ttmkfdir is needed by xorg-x11-xfs-6.7.0-2

    This was resolved by installing rpm ttmkfdir for Fedora

    however at YUM install we get:
    Resolving dependencies
    ......Unable to satisfy dependencies
    Package mod_python needs httpd >= 2.0.40, this is not available.
    Package mod_python needs httpd-mmn = 20020903, this is not available. // Resolved by rpm -e mod_python
     
    #11 icanectc, Aug 9, 2004
    Last edited: Aug 9, 2004
  12. [iG]

    [iG] Member

    Joined:
    Oct 16, 2002
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    rpm -e mod_python :)
     
  13. icanectc

    icanectc Well-Known Member

    Joined:
    Mar 10, 2003
    Messages:
    344
    Likes Received:
    0
    Trophy Points:
    16
    Yum completed successfully

    checked grub..
    Rebooted and viola the server never came back up...

    When i got home from the office it was stuck trying to load the new kernel. erroring out.. a hard reboot solved the problem... For those that use NOCS you have have to request your server be manually rebooted.


    named started ok Aug 9 21:52:32 ptr named[32650]: invalid command from 127.0.0.1#33570: bad auth Aug 9 21:52:32 ptr named[32650]: shutting down Aug 9 21:52:32 ptr named[32650]: stopping command channel on 127.0.0.1#953 Aug 9 21:52:32 ptr named[32650]: stopping command channel on ::1#953 Aug 9 21:52:32 ptr named[32650]: no longer listening on 127.0.0.1#53 Aug 9 21:52:32 ptr named[32650]: no longer listening on 207.234.147.140#53 Aug 9 21:52:32 ptr named[32650]: no longer listening on 207.234.150.249#53 Aug 9 21:52:32 ptr named[32650]: no longer listening on 207.234.150.250#53 Aug 9 21:52:32 ptr named[32650]: no longer listening on 207.234.150.251#53 Aug 9 21:52:32 ptr named[32650]: no longer listening on 207.234.150.252#53 Aug 9 21:52:32 ptr named[32650]: no longer listening on 207.234.150.253#53 Aug 9 21:52:32 ptr named[32650]: no longer listening on 207.234.150.254#53 Aug 9 21:52:32 ptr named[32650]: exiting Aug 9 21:52:32 ptr named: named shutdown succeeded Aug 9 21:52:33 ptr named[353]: starting BIND 9.2.3 -u named -t /var/named/chroot Aug 9 21:52:33 ptr named[353]: using 1 CPU Aug 9 21:52:33 ptr named[353]: loading configuration from '/etc/named.conf' Aug 9 21:52:33 ptr named: named startup succeeded Aug 9 21:52:33 ptr named[353]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 9 21:52:33 ptr named[353]: listening on IPv4 interface eth0, 207.234.147.140#53 Aug 9 21:52:33 ptr named[353]: listening on IPv4 interface eth0:1, 207.234.150.249#53 Aug 9 21:52:33 ptr named[353]: listening on IPv4 interface eth0:2, 207.234.150.250#53 Aug 9 21:52:33 ptr named[353]: listening on IPv4 interface eth0:3, 207.234.150.251#53 Aug 9 21:52:33 ptr named[353]: listening on IPv4 interface eth0:4, 207.234.150.252#53 Aug 9 21:52:33 ptr named[353]: listening on IPv4 interface eth0:5, 207.234.150.253#53 Aug 9 21:52:33 ptr named[353]: listening on IPv4 interface eth0:6, 207.234.150.254#53 Aug 9 21:52:33 ptr named[353]: command channel listening on 127.0.0.1#953 Aug 9 21:52:33 ptr named[353]: command channel listening on ::1#953 Aug 9 21:52:33 ptr named[353]: running

    to resolve this we sshed into the box and ran: named -u named -g

    This seemed to resolve our DNS woes. However restarting the service from WHM screws everything up. Any idea how to fix that?

    Now when restarting the service in SSH we get this:
    Error reloading bind on ptr: rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid.

    I am not sure which key they are talking about but the WHM key is alive and working well I can WHM into the box using the IP just not the FQDN.
    BIND IS ACTING REALLY WEIRD Its connecting or I should say trying to connect to some weird stuff running named -u named -g

    it works the minute i exit it stops listening and the sites go down. I let it sit there and it starts to print out:
    lame server resolving 'www.abarine.com' (in 'abarine.com'?): 194.250.249.14#53
    Aug 09 22:34:38.678 lame server resolving 'www.abarine.com' (in 'abarine.com'?): 194.250.249.14#53
    Aug 09 22:34:38.791 lame server resolving 'www.abarine.com' (in 'abarine.com'?): 194.2.0.2#53
    Aug 09 22:34:38.792 lame server resolving 'www.abarine.com' (in 'abarine.com'?): 194.2.0.2#53


    I dont even know what website that it... Never heard of it in my entire life. the named.conf file in etc looks perfect.. What the heck is going on?

    We resolved this by pico -w /etc/sysconfig/named and commenting out 'ROOTDIR=' lines. so that everythign in named is basically commented out. Bind is working like a champ :)
     
    #13 icanectc, Aug 9, 2004
    Last edited: Aug 9, 2004
  14. [iG]

    [iG] Member

    Joined:
    Oct 16, 2002
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
  15. residenta

    residenta Registered

    Joined:
    Jun 12, 2004
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Based on previous posts, it appears that the solution to resolving failed dependencies is to either erase or install packages. How do you know which way to go?

    For me, when installing the base package, in addition to all the redhat-config packages, I also get.

    Code:
    libtcl8.3.so is needed by (installed) expect-5.39.0-96.1
    I'm assuming that since expect is part of the base package, i'd need to install libtcl8.3.so. Correct?

    And for the xorg package, I get

    Code:
    libc.so.6(GLIBC_2.3.4) is needed by xorg-x11-6.7.0-2
    Again, I would follow the same logic and assume that libc.so.6 will need to be installed.

    Now, when trying to erase the exim package I get...

    Code:
    smtpdaemon is needed by (installed) fetchmail-6.2.0-8
    smtpdaemon is needed by (installed) mutt-1.4.1-5
    Do I erase fetchmail and mutt packages?

    Lastly, if I have to install a package, do I install the package for fedora 1 or 2?
     
  16. foxboy

    foxboy Well-Known Member

    Joined:
    Sep 20, 2003
    Messages:
    66
    Likes Received:
    0
    Trophy Points:
    6
    i did it too.
    It went without trouble, until i reached exim. Installing exim via your RPM works, but when i try to install it using /scripts/exim4 it all breaks.

    it's just as in the other topic about exim not working. it's missing db-devel and error's out on extracting libperl.so or something like that.

    see: http://forums.cpanel.net/showthread.php?t=27967&highlight=exim+fedora for more info.

    How can i fix this?
     
  17. icanectc

    icanectc Well-Known Member

    Joined:
    Mar 10, 2003
    Messages:
    344
    Likes Received:
    0
    Trophy Points:
    16
    hmm let me see if exim breaks on this test system.
     
    #17 icanectc, Aug 12, 2004
    Last edited: Aug 12, 2004
  18. foxboy

    foxboy Well-Known Member

    Joined:
    Sep 20, 2003
    Messages:
    66
    Likes Received:
    0
    Trophy Points:
    6
    it does work, but /scripts/exim4 doesn't work.
    So when a new version of exim comes out, i can't upgrade.

    ---
    yum didn't show any upgrades, but up2date did (on the same servers :S) so i upgraded perl, and now it al works like a charm. I even upgraded to 5.8.4 after that and it still works :D
     
    #18 foxboy, Aug 12, 2004
    Last edited: Aug 12, 2004
  19. icanectc

    icanectc Well-Known Member

    Joined:
    Mar 10, 2003
    Messages:
    344
    Likes Received:
    0
    Trophy Points:
    16
    That's funny on this test core 2 machine there is no up2date script to update to that version of perl it has .3 though.
     
    #19 icanectc, Aug 13, 2004
    Last edited: Aug 13, 2004
  20. icanectc

    icanectc Well-Known Member

    Joined:
    Mar 10, 2003
    Messages:
    344
    Likes Received:
    0
    Trophy Points:
    16
    CentOS is an awesome OS. I agree. But some people like to use Fedora hehe I think they like the way it sounds. But this guide was really good for people to upgrade to the Core 2 on Fedora. I vote for sticky :)
     
Loading...

Share This Page