[Info-vax] Reloading device drivers on x86-64 VMS

VAXman- at SendSpamHere.ORG VAXman- at SendSpamHere.ORG
Mon Mar 9 09:30:32 EDT 2015


In article <mdige0$qqm$1 at speranza.aioe.org>, hb <end.of at inter.net> writes:
>On 03/08/2015 06:37 PM, Stephen Hoffman wrote:
>> On 2015-03-08 18:31:43 +0000,   VAXman-  @SendSpamHere.ORG said:
>>
>>> In article <mdhkh6$8vd$1 at dont-email.me>, "Craig A. Berry"
>>> <craigberry at nospam.mac.com> writes:
>>>> On 3/8/15 8:17 AM, Stephen Hoffman wrote:
>>>>
>>>>> But yes, it'd be very nice to have the ability to unload and reload
>>>>> drivers.
>>>>
>>>> Shareable images too, while you're at it, but that's a different topic.
>>>
>>> ???  You already can.
>>
>> That's very likely a reference to reloading shareable images within the
>> context of a running process and the image activator, not a running system.
>> AFAIK, the image activator doesn't support that, short of restarting the
>> process or performing some undocumented and unsupported and inner-mode
>> hackery.
>> The simple expedient of finding and deleting the associated virtual
>> address space won't likely produce the expected results, either.
>
>Looks like (and was confirmed in another reply) dlopen() and friends, so 
>it is in the context of a running main image.
>
>There is no code in the image activator to do this: you have to wait for 
>image rundown to free up the resources.
>
>Removing and adding a shareable image with the install utility should 
>work, no matter whether it is installed /resident or with shared address 
>space: which is more or less a system context.

OK.  If I'm understanding this, he wants a way to activate a shareable image
(a la LIB$FIND_SYMBOL) and then, deactivate it?

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.



More information about the Info-vax mailing list