> [sent off list to reduce amount of spam]
> Please cease this off-topic. It has nothing to do with the subject
> debated. If you want to talk over a beer, then please go to a pub. If
> you want to compare your pe^w^w^w embedded systems, then please
> find an appropriate media for that.
Documents on embedded systems, now that we have a solid definition of
what an embedded system actually is, is quite important and minimizing
storage/ram usage of resources whilst accessing those docs is of great
importance. Expecting a workstation or even a server to have the latest
mix of documents for the variety of codes and hardware found in a
heterogeneous cluster, is an unreasonable stretch, and often leads to
mismatches, imho. Imagine a variety of embedded systems that morph in a
different cluster matrix, dozens or hundreds of times a day. The
admins, programmers or users with larger codes may need a deep read on
the docs sporadically' but in a time-critical manner. They do not want
or need extraneous or irrelevant docs in the pool. Heterogeneous
clusters are now all the rage in clusters, particularly, for HPC.
Current, accurate and minimized docs are keenly important for all
embedded systems, particularly if they can
receive codes or binaries dynamically and morph.
As embedded systems venues of deployment morph, dynamically, their
interned documentation should be "auto adjusted" like the system
software despite being on identical hardware particularly since the
embedded clusters grow more complex with the latest codes and hi level
language codes on top of these embedded clusters. That is, in the role
they (dynamically play) as well in how individual software is used on
otherwise identical hardware can change rapidly. Lofty goals, yes, but
since the subject of local documentation on embedded systems came up,
naturally it is quite reasonable to seek the fastest possible diverse
usage with the least footprint on resources.