WARNING 3B1 ATTFixDisk breaks HDB

[Robert J. Granvin]

>I received AT&T 3.51 Fix Disk ver 1.0 Fix 1014.
>
>I installed it on one of my 3B1s with:
>
>HoneyDanBear UUCP

Only this is significant.

>I installed the whole works...there are 8 fixes.
>
>uucp stopped.

Of course it will.

HDB is not a supported package, and the fixdisk only cures problems
with the stock UUCP.  I'm very likely wrong on this, but I think it
may make note of that in the descriptions section for that fix, and
tell you not to install this fix if you are running HDB.

>I uninstalled HDB and HDB administration.

Not actually necessary, as I believe only uucico was replaced.  

>During the latter process, all control stopped.
>I hit reset and after 2 Fsck dumps got to the
>place where I should get a login:  No login.
>Let the machine sit and it gave out some "panic double bus errors"

This is something different.  I can't see how uucp/uucico/whatever
would cause this, and I know for a fact that Fixdisk 1.0 is not
damaging in and of itself.

Here, I'd say, you had a "fluke".  Fixdisk 1.0 isn't to blame, unless
you made an installation that was clearly marked as something not to
do.  However, I don't recall anything from Fixdisk 1.0 that was that
ingrained to cause panics.

>I just reinstalled everything.

One solution, but may have been drastic.

>I conclude that the fix disk is not a wise thing to do if you are
>lucky enough to have HDB Uucp.

ERROR!

The fixdisk solves some definately significant (and insignificant)
problems.  If you ever plan on installing (the future) Fixdisk 2.0,
it's possible that you'd be required to install Fixdisk 1.0 first.

However, to expand on the next statement:

>If I get up the courage {and strength} I may try again leaving Uucp
>off of the fix list.

The fixdisk provides 8 fixes.  Each fix has a description of the
repairs (short yes, but a description none-the-less) and asks you
whether you want to install each fix. 

You are forced to make a yes/no decision.

The installation also warns you on other fixes that if you do not have
certain packages or features installed to NOT install that particular
fix. 

In the case of the UUCP fix, if you use HDB, do not install this fix.
Installing the other fixes just isn't going to do you any harm, and
just may do you some good.

No matter what you do, it's always good form to read everything that's
made available to you, and consider what you have in that process.
Having installed Fixdisk 1.0 on many machines, all of different
configurations, and having watched it run for a couple of eons, I know
for a fact that 1.0 isn't a problem in and of itself.

>However, I keep remembering an old political slogan "If it ain't broke
>do'n fix it"

And if you don't fix it, you won't improve it.

"Broke" is relative.

I found I had real problems with stock 3.51.  Fixdisk 1.0 repaired them.
To me, 3.51 is broke, and 3.51a (incorrect term :-) is "less broke".
Fixdisk 2.0 will be even a lot more "less broke", and in many respects
"really wayfar fixed up" (Even though some of it may not actually be
apparent.  Neat how that works, huh? :-)

As far as the fixdisks go, having had some external involvement, I can
see the work that goes in to repairing something either exceedingly
obscure or best described by the phrase "blah blah is broke."

The work involved to fix some things, some things that people out
there are seeing today, and a large number of people aren't (yet :-),
is not trivial.  I'm never squeamish to complain about AT&T support
when it's bad, but in this area, I know for a fact that it's quite
exceptional (and it's not widely seen).  Good job, folks!  (You know
who you are).

-- 
________Robert J. Granvin________        INTERNET: rjg at sialis.mn.org
____National Computer Systems____          BITNET: rjg%sialis.mn.org at cs.umn.edu
__National Information Services__            UUCP: ...amdahl!bungia!sialis!rjg
 "Insured against Aircraft, including self-propelled missiles and spacecraft."