[Info-vax] Error running MariaDB

[Stephen Hoffman]

On 2020-10-12 10:01:49 +0000, hb said:

> On 10/10/20 12:45 AM, Stephen Hoffman wrote:
>> On 2020-10-09 15:48:40 +0000, hb said:
>> 
>>> On 10/9/20 5:16 PM, Stephen Hoffman wrote:
>>>> On 2020-10-09 10:18:54 +0000, hb said:
>>>> 
>>>>> Anyway, ANALYZE/IMAGE does not compare the GSMATCH found in the image 
>>>>> with the GSMATCH in the shareable on the system. It also does not try 
>>>>> to find out whether all the references to the shareable image can be 
>>>>> resolved from the shareable on the system, usually found in SYS$SHARE.  
>>>>> So ANALYZE/IMAGE can't detect this problem.
>>>> 
>>>> Fodder for enhancement, then: Analyze better.
>>> 
>>> Or use a different tool:
>> 
>> That wasn't a request for alternative tooling.
> 
> Maybe I don't understand, wouldn't be the first time. What should be 
> enhanced and analyzed better?

Because clearly that the image under analysis won't work on the local 
system is somehow completely irrelevant to the image analysis being 
performed?

For many of us, ANALYZE /IMAGE is a tool used as a pre-flight for the 
sometimes-less-than-helpful image activator. To look for corrupt 
images, and for the particular issues with images that won't launch. 
The lesser-known DCL symbols are handy for scripting the pre-flight 
checks, too. This because ANALYZE /IMAGE is what we have for file(1), 
short of loading bintools or ilk or of creating our own tooling akin to 
the image-shimming shimmer tool I wrote a while back.

It's also interesting seeing references to GSMATCH in this thread in 
parallel to another thread discussing where GSMATCH usage has been 
effectively deprecated within OpenVMS itself, too.

This whole area is archaic, and filled with arcane and tribal knowledge 
and tribal tooling. With weird logical names that blow up some images, 
and that are needed for other images. With no preferences and settings 
support. No image signing. Requiring home-grown quota and compatibility 
checks, which inevitably get omitted. Sandboxing and isolation and 
integrity checks are missing. The whole area has endured ~forty years 
of incremental hackery, and the resulting aggregation is overdue for an 
overhaul. Because ~nobody understands the wrinkles and the limits and 
the weird that is lurking here, and there's ~no documentation. What doc 
does exist for various aspects of—but not all of—this area is scattered 
all over; in DCL, in system services, in the IDSM, in the C docs, in 
the Java docs, etc. (And yes, I know about polyglot 
files—self-extracting zip files are one of the "better-known" polyglot 
files encountered on OpenVMS.) But again, I do not expect to see image 
activation and the current morass overhauled. Getting ANALYZE /IMAGE to 
report "nope, not gonna work here" would be a stretch.



-- 
Pure Personal Opinion | HoffmanLabs LLC