Re: WARNING:DO NOT UPGRADE TO CORE 4

From: Timothy Murphy (tim_at_birdsnest.maths.tcd.ie)
Date: 07/13/05

  • Next message: Ezra Nugroho: "Re: Finding ports and services" 
    To: fedora-list@redhat.com
Date: Wed, 13 Jul 2005 18:34:22 +0100

    Les Mikesell wrote:

    >> Consider the possibility that an installation might not work on machine
    >> X, but an upgrade might.
    >
    > Then you've created a totally unique situation where the reason it works
    > at all is likely because you have bits and pieces of some unrelated
    > version still running. That might work for you, but if you have
    > problems no one else will understand them or be able to help.

    How can one have "bits and pieces of some unrelated version still running"
    if you do a clean install?

    I'm not actually asking for your help,
    I'm simply pointing out that your dogmatic assertion
    that installation is always better than upgrade
    is not true, giving as a counter-example
    the fact that I have a machine where the first did not work,
    and the second did.

    The reason for this - although this is not strictly relevant -
    is that recent versions of Fedora run mkinitrd when installing their kernel.
    This has to determine in some way which modules should be included in initrd
    and in my case it includes the wrong scsi driver.
    There are various ways in which I can counter-act this,
    but the simple fact is that a clean install does not work -
    it leaves a machine which will not boot.

     
    >> Also consider the possibility that it might make more sense
    >> to keep /home on a separate partition, and leave this alone even if
    >> installing.
    >
    > That's a reasonable approach, as is backing it up and restoring. You
    > probably want the backup anyway in case you make a mistake involving
    > the partitions.

    It's not an either-or situation.
    You implied that you deleted /home ,
    and I'm pointing out that that was a silly thing to do.

    > Historically, Linux kernels have solved most of their hardware issues
    > somewhere around X.X.20. If don't use anything unusual you might not
    > notice this. I see that firewire might be fixed in 2.6.12...

    This seems to me complete nonsense.
    There are many hardware issues for Linux remaining,
    eg problems with RAID, graphics, 11g WiFi, many USB devices, etc, etc,
    I suspect there always will be such problems,
    as new hardware devices come out. 

    -- 
Timothy Murphy  
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Ezra Nugroho: "Re: Finding ports and services"

    Relevant Pages

    • Re: fp98 mess
      ... purchase an upgrade of FrontPage 2003. ... The reason for the upgrade is that: ... You need to do a custom install and install only the FP ...
      (microsoft.public.frontpage.client)
    • Re: fp98 mess
      ... If planning to upgrade, there is no reason to install the prior version, as you only need to have ... FrontPage Resources, WebCircle, MS KB Quick Links, etc. ...
      (microsoft.public.frontpage.client)
    • Re: Retailer copy of XP?
      ... > I did some work for a friend and his brother. ... I have not had much reason to use ... install an Upgrade version of XP overtop of an illegal version. ... In fact if you use an Upgrade version, even to do a clean install, ...
      (microsoft.public.windowsxp.basics)
    • Re: WARNING:DO NOT UPGRADE TO CORE 4
      ... >> Then you've created a totally unique situation where the reason it works ... You don't with a new install. ... Some bugs aren't found until someone tries the combination of things ...
      (Fedora)
    • Re: fp98 mess
      ... And it's much cleaner install that way! ... | FrontPage Resources, WebCircle, MS KB Quick Links, etc. ... purchase an upgrade of FrontPage 2003. ... The reason for this is ...
      (microsoft.public.frontpage.client)