[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Upgrading



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 5 Jan 1999 15:02:13 +0000 (GMT), Nidge Jones wrote:

>Having read up on this a little, am I correct in saying that I will be able
>to do this without breaking everything?

    Well, maybe not everything...

>I am concearned about the LIB6c stuff, and what upgrading will mean to my
>old (LIB5) non-debian packages. Will they still work, or will I end up
>breaking everything from trying to change to 2.0 ?

    However, Hamm does have the old libc5 libraries available for you to
install so the stuff you have compiled (or was compiled) with it will still
run.  I use rar extensively here and it is a libc5 program, no problems at
all.

>I am most concearned about this upgrade, I don't want to be left with a box
>of broken bits, followed by a long night of tape restores.

    I've never gone through that upgrade since I started with Hamm.  However,
I don't think "a long night of tape restores" would be a wise response if
things do break.  If things break you're looking at two options.

1: A long night of reinstalling from tape.

2: A long night of installing from scratch.

    Personally, I've gone through several Slackware installs, one Red Hat
install, one Stampede install, one FreeBSD install and two Debian installs
(one on a laptop).  If I were given those choices, I'd take the latter since
at least then the upgrade would be over and done with.  I find that fresh
installs are a lot less painless than trying to cobble together everything
from backups.  There are exceptions, mind you, but at that level of breakage,
there aren't many.  ;)

- -- 
         Steve C. Lamb         | I'm your priest, I'm your shrink, I'm your
         ICQ: 5107343          | main connection to the switchboard of souls.
- -------------------------------+---------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.0 (C) 1997 Pretty Good Privacy, Inc

iQA/AwUBNpIvjHpf7K2LbpnFEQL9cQCgpfCKss6IwGSU/4iOcTqQS0ZsulQAoIOy
nhcvOZf8bSkk67hErwAFxPRU
=gV4X
-----END PGP SIGNATURE-----



Reply to: