[Info-vax] New filesystem mentioned

[Dave Froble]

On 5/15/2019 1:28 PM, Bob Koehler wrote:
> In article <qbetnh$7kv$2 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>> On 2019-05-14, Bob Koehler <koehler at eisner.nospam.decuserve.org> wrote:
>>> In article <qbebro$6ji$1 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>>>>
>>>> Yes, but those are all filesystem driver issues. I don't see what is
>>>> required in the on-disk structure itself to support VMS style clustering.
>>>
>>>     These are filesystem internals issues.  Not at the device driver
>>>     level, but at the ACP or XQP level.
>>>
>>
>> I said nothing about device drivers.
>>
>> I talked about filesystem drivers.
>>
>> The filesystem specific code in the XQP would be implemented as
>> a filesystem driver in a modular system (which is exactly what
>> happens on Linux).
>>
>> If you look at how Linux works, you will see that what is a monolithic
>> mass of code on VMS, which cannot be changed or added to by an end-user,
>> is actually a nicely modular and layered architecture on Linux.
>
>     OK, but it still has to inlude code to call the DLM.
>

"Has to" ??

Well, only if locking is required.

Regardless, using a tool such as DLM does not imply that the tool (DLM) 
is part of the XQP, filesystem, etc.

Since there is a likelyhood of there being a MOVL somewhere in the code, 
should that imply that Macro-32 is part of whatever is using it?


-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486