Re: FC2 doubtful quality?

From: Jim Cornette (fc-cornette_at_sbcglobal.net)
Date: 06/23/04

  • Next message: Lonnie Santella: "RE: FC2 Frist boot after clean Install"
    Date: Wed, 23 Jun 2004 16:06:15 -0400
    To: tim@birdsnest.maths.tcd.ie, For users of Fedora Core releases <fedora-list@redhat.com>
    
    

    Timothy Murphy wrote:

    >Dexter Ang wrote:
    >
    >
    >
    >>So I guess developers were "pressured" to release on a deadline, hoping
    >>to fix most bugs through updates. As much as I'd personally love to help
    >>test and test until all bugs are stamped out, you can't avoid the fact
    >>that a lot of other people simply won't test until a "final" release is
    >>out.
    >>
    >>
    >
    >I'm not sure how typical I am,
    >but I haven't run any test releases because it has been said
    >that one cannot upgrade from a test release to a new FC release.
    >
    >
    Nothing is supported anyway. I have upgraded from test cycles to final
    releases several times. This may leave newer versions of programs on
    your machine that were not stable enough t be released with the final
    version of the distro. Hopefully, the program will become stable enough
    that the fonal release version will replace the not ready for release
    version.

    I have one system that is always paced with current rawhide packages.
    This system is surprisingly stable. In fact, my network cards both work
    on this environment.

    I have another version that is an install of FC1 and went through the
    test phase (FC1 to FC2) and is staying at current FC2 released packages.
    This upgraded environment has all of the multimedia related packages and
    is what I consider my main OS.

    The third version is a fresh install of FC2 and is pretty limp in that
    it does not have all of the multimedia related add-ons included. This
    evironment works great for things like dvd burning and the sound to be
    set to a decent default level.

    >It would simply be too time-consuming for me
    >to re-install FC whenever a new release comes out.
    >Perhaps I'm not very well organised,
    >but I would have to go through dozens of config files
    >to see which need to be copied, and which updated.
    >
    >
    If you are not running a lot of services, add-on programs and user
    related data seem to be the only major drawbacks. I've been held back by
    pre-existing config files on several occasions. I was unaware that CD
    burning worked on later versions of RHL. The hdx=ide-scsi addition to
    the boot loader from RHL 6.x series to RHL 7.x series never took place.
    Once I did a fresh install and found out that I no longer needed to boot
    into windows to burn CDs, I was happy with catching up.

    >So I would suggest to the Fedora administrators
    >that if it were possible to upgrade from test releases
    >there might be a lot more people willing to test.
    >
    The answer that you most likely will get is that this is unsupported.
    The good news is that other than progressively upgrading through the
    test cycle is not that bad. At least from my exposure to doing *the
    unsupported* betas to next release cycles.

    Disadvantages of upgrading throughout the OS cycle. New programs added,
    they will not be installed. Config or default application settings
    changes for the better, config files might be better with a new install.

    Advantages of clean installations. You will get newer packages that are
    included in the new version. You will get the latest configuration file
    defaults, which seem more sanely based.

    Good luck and have fun testing. Who knows what is supported anymore on
    an unsupported OS. It works great though, at least for me.

    Jim

    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Lonnie Santella: "RE: FC2 Frist boot after clean Install"

    Relevant Pages

    • Apt Gone Mad?-Or Is It Me?-Expert Help Needed
      ... So tried to upgrade OO to 2.0 but Apt refused to do so. ... Aptitude doesn't show anything but Wajig shows unmet dependency for kdelibs-data. ... The following packages are unused and will be REMOVED: agsync arson barcode brahms cdda2wav cddb digikam digikamimageplugins gmessage guarddog guidedog hotswap-gui hotswap-text i2e id3v2 kbarcode kbear kbiff kdebase-dev kdirstat kile kimdaba klog klogic kmymoney2 knetfilter knutclient komba2 kover kprof kpsk krusader ksimus ksimus-boolean ksimus-datarecorder ksimus-floatingpoint ksocrat ksocrat-data kvdr kvirc kvirc-data kvirc-doc kwavecontrol kxmleditor lesstif2 libdynamite libimlib2-dev libkonq4-dev libmimedir liborange ... ChatagnierL-Home:/temp# wajig install openoffice.org Reading Package Lists... ...
      (Debian-User)
    • Re: Redhat upgrade problem - packages fail rpm -Va
      ... > being owned by multiple packages, ... # rpm -V up2date ... {Only config files in verify error list. ... We can lean something from Microsoft's install process. ...
      (linux.redhat.install)
    • Re: Redhat upgrade problem - packages fail rpm -Va
      ... > being owned by multiple packages, ... # rpm -V up2date ... {Only config files in verify error list. ... We can lean something from Microsoft's install process. ...
      (comp.os.linux.setup)
    • Re: [opensuse] Architecture switch 32->64 bit (i386 to x86-64)
      ... A "simple" upgrade with Yast from 10.3 installmedia leads to lots of dependency problems when resolving the packages. ... I wanted to get my kernel to 64-bits. ... One rpm line shows 55 rpm packages I had to install at same ...
      (SuSE)
    • Re: Versions and Updates
      ... SuSE won't upgrade it via YOU for you. ... The same goes for KDE, Gnome, or any ... Gnome packages on their website. ... You're required to install lua from another website: ...
      (alt.os.linux.suse)