Brian K. White wrote:
> Ah I know what that is.
>
> It's not really an MP5 thing, it's an old issue that was raised (at least)
> on a Legend beta testers mail list a few years ago.
>
> A long time ago some stuff that was originaly part of gnutools moved over to
> gwxlibs, and gwxlibs has been updated with several new versions since then,
> while gnutools never saw another new version (Publicly anyways. I did see a
> slightly newer version once and still have it installed on a box, and can
> use the box-to-box network install method in custom to install it on new
> boxes, but I have no idea how I got it in the first place!)
>
> The answer that was given on that mail list, and which I've done countless
> times since so it's ok, was to install gnutools first, and ignore the
> warning about missing dependancies during install. Then touch
> /tmp/gnutools.nocheck
> Then install whatever is the latest gwxlibs you can find (probably MP5 at
> this point)
Brian,
The gwxlibs on my system was installed by MP5 (or possibly updated by MP5
from mp4 and upd4).
The error condition that /tmp/gnutools.nocheck resolves is the incorrect
test in gnutools looking for MP1 or greater.
>
> Without the tmp file, the gwxlibs install won't proceed in a way that you
> can ignore like gnutools did.
> And I never can remember whether it's /tmp/gnutools.nocheck or
> /tmp/gwxlibs.nocheck, so I often just create both instead of trying one and
> getting the error 50% of the time.
I did try removing gwxlibs by selecting MP5 and then expanding it and select
gwxlibs component and "remove software." And as expected that did barf up
the things that depend upon gwxlibs. I then re-installed gnutools with the
/tmp/gnutools.nocheck and re-installed gwxlibs. Still no joy.
>
> And then I just happen to never do the custom fixup thing so the
> last-installed package wins and thats the end of the story. I expected an
> update to gnutools years ago that would have cleared this up naturally along
> the way.
Ooo.., a lot of people on c.u.s.m report that they don't use the custom
fixup thing. But I've used it. A lot. And rely on it. Generally following
the advice to run custom after fsck -o full after a crash or when
something is not working as expected. Then following it with
/tcb/bin/authck -av, integrity, and fixmog.
If I can't rely on it, I'm hosed. I do keep a report of what it plans to fix so
that if anything stops working, I can dig it out of the files with discrepancies.
Well, my system now won't boot cleanly (possible finger fumble when removing MP5
and got instead part of 5.0.7Hw). Reinstalling MP5 complained about corrupt
component and I had to check "ignore the component" to continue the MP5 installation.
After that, rebooting the system with the MP5 relinked kernel came up with a
lot of error messages and hung without getting to the login prompt.
A copy of the last good kernel just prior to the remove/re-install dance
was then copied to /stand as and the /dev directory from the October
2006 root only backup was copied over top of /dev. That was sad, the
boot up reported a corrupted kernel and even trying unix.safe at that
point resulted in screen of conflicting memory allocations.
I restored the kernel from the Oct 2006 backup and tried again and that would
boot with a long delay and get to a log in prompt. But logging in as root was
real slow and the message "user count exceeded, allowing root on tty01 for maintenance"
was displayed. However, no commands would work and they all failed with
"too many processes, unable to fork."
At this point I boot BackupEdge root only backup from Oct 2006, run divvy and
create new hd0root and restore the root file system. I had prepared for
this eventuality by creating a special backup of files I want to re-install
on the root that have changed after October 2006 exclusive of the work
on MP5 and gnutools-5.0.7Kj.
>
> If I knew how to take a loaded or installed package and extract it back out
> to VOL's pr pkgadd I'd try extracing out that newer version I have to see if
> that clears up the overlapping files at least.
> There was some reasonable reason why that version was never officially
> released, like it didn't fix some problem they knew about and wasn't enough
> of an update otherwise to be worth a release. I think it's almost not really
> an update at all so much as a repackaging.
>
> "that box" is really just a pair of hard drives I am preserving at the
> moment too, so I can't easily check any details right now. I have to find a
> box to boot the drives on first.
>
> Brian K. White brian@aljex.com http://www.myspace.com/KEYofR
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!
>
>
>
So at this point in time we don't have a sanctioned gnutools that
plays nice with gwxlibs from MP5.
Thanks for the response.
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670