Why does open-vm-tools-x not load all extensions it depends on?

[Ulysses_]

This must be happening with other extensions too.  What happens when open-vm-tools-x tries to use one of its features that is implemented in one of the extensions it depends on, and which is not loaded by default? 

Does the missing extension get loaded quietly?  Or does it just fail in a user-unfriendly manner?

[gerald_clark]

If an application depends ( requires ) on other extensions, they will be in the dep file and will be loaded when the application loads.
If the application trys to use an optional ( not required ) extension, it is up to the user to be sure it is loaded onboot.

[Ulysses_]

Then why doesn't the open-vm-tools-x extension get marked as ondemand, but only its required extensions are silently treated as ondemand?

[gerald_clark]

If you think something is not working properly, state specifically what the problem is.
If you do not understand the difference between on demand, and dependencies, I suggest
you spend some more time reading the online docs and the wiki. Then ask specific questions.

[Ulysses_]

I should avoid using proprietary tc terms like on demand and on boot because they distract from the essence of things.  Put simply, what is the benefit of allocating memory to a software function when that memory is not enough for the function to operate.  

It's like defining a C local variable outside the function where it is used so it is taking up stack space that could be free for other uses.

[gerald_clark]

You still have not clearly stated a question.
How much memory do you have?
Are you loading into filesystem insteadof loop mounting?
What exactly do you think is being allocated that you don't have enough memory for?

[Ulysses_]

How much memory do you have?

2 GB.  But the memory available to TC is not fixed, TC runs in VM's.  And it is desirable to run as many TC VM's as possible within the 2 GB minus the host's usage.

Are you loading into filesystem insteadof loop mounting?

I'm doing what TC does by default. Probably loop mounting.

What exactly do you think is being allocated that you don't have enough memory for?

I think a VM with open-vm-tools-x allocates memory for this extension, and therefore has less memory available for browsing or other tasks.

Maybe we ought to wait for danielbarnes who knows what is going on in this extension. I'm now guessing he's doing things this way because frequently used features of open-vm-tools-x work stand-alone (without the required extensions), and these features are needed during the boot (eg the Virtual line in xorg.conf) so it makes sense to load the extension without loading its required extensions.

[gerald_clark]

The info file lists some optional features, and the extensions that must be preloaded if you wish to use them.

[danielibarnes]

I don't have a clear understanding of your issue. What are you are trying to do that you cannot? If something doesn't work please give me step-by-step details to reproduce any problems.

[Ulysses_]

I don't have a clear understanding of your issue. What are you are trying to do that you cannot? If something doesn't work please give me step-by-step details to reproduce any problems.

Can't reproduce the predicted issue because I do not know what usage would cause all of this extension's required extensions to be loaded.  The predicted issue is an out-of-memory failure of, for example, a diskless browser appliance (no swap).

[gerald_clark]

It is a bit difficult to answer undefined hypothetical questions.
Can we close this?

[danielibarnes]

Then why doesn't the open-vm-tools-x extension get marked as ondemand, but only its required extensions are silently treated as ondemand??

I have not observed this, but neither did I test for it. If it does occur, then it must be a generic issue and not particular to any one extension. The "onboot" property of an extension must be propagated to its dependencies. Anything else is a defect. If I discover something, I will post to the 3.6 rc thread or elsewhere in the TCB bug section.

[Ulysses_]

The "onboot" property of an extension must be propagated to its dependencies. Anything else is a defect.

That's useful info.  This browser appliance here looks otherwise and it's only default installs of extensions plus a xorg configure and no other messing with, and what you see when you select OnBoot in AppsAudit is in the attachment:

[danielibarnes]

It looks otherwise, but it will load open-vm-tools-x and its dependencies as expected.

Here is my test:
1) Boot tinycore with "base norestore" options.
2) Load Xlibs.tcz as "OnDemand."
3) Load open-vm-tools-x.tcz as "Onboot."
4) Observe that Xlibs.tcz is automatically loaded as expected even though it appears in the "OnDemand" list.

[gerald_clark]

When tce-load loads an extension, it loads dependencies first based on the dep file.
Each of those dependencies have their dependencies loaded . . . etc.
It makes no difference whether it is onboot or ondemand.
There is no property to be propagated.