RE: FC2 on Intel 440GX (was FC1 on Intel 440GX)

From: MW Mike Weiner (5028) (MWeiner_at_ag.com)
Date: 05/31/04

  • Next message: jli_at_mail.ratio-it.nl: "Installing Fedora 2"
    Date: Mon, 31 May 2004 15:07:37 -0400
    To: "For users of Fedora Core releases" <fedora-list@redhat.com>
    
    

    On Behalf Of Florin Andrei
    > If i had to rebuild the installer boot disk again for FC2 i'd be
    pissed.
    > :-)

    > Luckily, all you have to do is enter "linux acpi=force" at the FC2
    installer boot prompt.

    > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=107880

    > Don't upgrade, but backup/reinstall. It's your only chance to clean up
    the cruft.

    > Also, just look at the mailing list archives and see all those horror
    stories from people who choose to upgrade instead > of doing a clean
    reinstall. Like: "i upgraded to FC2, and now my Gnome menus are all
    mangled". Doh, you reap what you
    > sow. ;-)

    > Upgrade seems to be used as the lazy one's path, instead of being a
    last-chance method (when, for really _objective_
    > reasons, backup and reinstall from scratch is impossible).
    > The only things that i carry over from one version to another,
    unchanged, are a few application's directories
    > (Evolution) and files (Mozilla bookmarks, Gaim nicknames caches), etc.
    The rest gets rebuilt from scratch.

    > In an ideal world (people knowing what they do, etc.), upgrade would
    be used like 100 times less often than it is now.

    Well fortunately for me, these are SERVER installs, and as such, I do
    not care about gnome/kde and the like. All I care about are
    server-related pieces and as such, those UPGRADE fine almost 100% of the
    time with limited nuances. Besides, in my specific case there is no
    CRUFT on the box, as it was a CLEAN install of FC1 to begin with, and
    all I did was yum upgrade the box to FC2, any CRUFT left over is very
    very minimal if not non-existant. And when you are doing over 500
    servers, backups are just not feasible, nor a good way to spend my time
    - if I loose a box, I simply DD another working server to a new disk,
    and whala that bad box is back up and happy - I have a saying ["... Look
    ma' NO BACKUPS!!!" mweiner@ag.com].

    Anyway, the intent of the initial email was NOT to begin a thread on the
    proper way to install/upgrade/update an OS, as there are as many methods
    to perform this as for any given instance of one's needs. I was merely
    probing to see if Greg Wildman had a chance to upgrade or even "think"
    about re-doing his original work. Agreed, there is no real need provided
    the acpi=force option works 100% of the time - I will soon see.

    Michael Weiner

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

  • Next message: jli_at_mail.ratio-it.nl: "Installing Fedora 2"

    Relevant Pages

    • Re: BSD Installer as a replacement for sysinstall?
      ... > without having to muck around with the internals of the installer. ... There are links to a binary updater project and a sysinstall replacement ... That's not to say there's no value in just replacing ... distribution sets to upgrade. ...
      (freebsd-current)
    • Re: gcc updates
      ... This breaks all of the C code I have written for the final phases of the processing chain. ... I assume a similar scheme would allow me to upgrade from F8 to F9. ... It then downloads the anaconda installer, and places an entry in grub that allows selection of an upgrade fedora item. ... This work is quite disk and processor intensive, yet I never saw any kernel or other issues during about two months, and in trimming 100GB of mpeg data. ...
      (Fedora)
    • Re: OE will not send after upgrade / restore
      ... > will not be able to apply Office updates. ... > Windows Installer version 1.0 to Windows Installer version 1.1. ... After a bad upgrade we ran the restore. ...
      (microsoft.public.office.setup)
    • Re: OE will not send after upgrade / restore
      ... > will not be able to apply Office updates. ... > Windows Installer version 1.0 to Windows Installer version 1.1. ... After a bad upgrade we ran the restore. ...
      (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
    • Re: OE will not send after upgrade / restore
      ... > will not be able to apply Office updates. ... > Windows Installer version 1.0 to Windows Installer version 1.1. ... After a bad upgrade we ran the restore. ...
      (microsoft.public.windowsxp.newusers)