On 2017-04-01 20:18:18 +0000, Kerry Main said:
Yes, you know; the sorts of folks that some "enterprise software
developers" have a well-deserved reputation of dumping poorly-written
and variously cryptic documentation for?
That can be the sorts of folks that cannot locate the documentation
because they searched for the common term, as is this case. As
started this thread, BTW.
The sorts of folks that are better served by using common phrases in
the documentation. That's when the documentation remains necessary,
and the developers haven't reduced or eliminated chunks of the
documentation, because the developers have provided tools that just
> Perhaps that is the reason for this disagreement here.
If that's why you think we're disagreeing, no. We're apparently
disagreeing because I'm suggesting an opportunity to improve the
associated documentation. That when eliminating the documentation is
> IPS/IDS devices are NOT purchased by end users. These devices starting
> price ranges are not for home or even small businesses i.e. $10-20K+.
Just who is an end user of the documentation or the product varies, of
course. In this thread, it was an OpenVMS user seeking information
on an OpenVMS feature — one commonly referred to as a firewall, and was
unable to do so.
That price range is probably an order of magnitude high, BTW.
As for hardware solutions? Entry prices for very nice commercial
systems are under US$200. That includes embedded IDS, IPS and VPN
server features and capabilities — where many vendors are headed, of
course — subscription services for features and updates. Slightly
further up and still under US$1000, redundant high-availability
features, higher bandwidth, more VPNs, and other such. As I
mentioned earlier, I'm deploying these devices for even small sites and
For those that need it, this trend is continuing, and fully-remote
configuration and provisioning are also available as well — the on-site
folks need to plug the device in, and the rest is remote. Established
policies and configuration settings, firmware upgrades and the rest
are all fetched and verified by the device. Automatically. This one
is a bit more expensive, at just under US$700.
All available. Now.
I'm rolling out managed switches for sites too, as the prices on those
are cratering as well. But I digress.
Again, my comments are that "firewall" is a commonly-accepted and
widely-used term, and — if y'all want to layer in a bunch of acronyms
for specific features — have at. But failure to reference a common
term in end-user documentation is a simple and easily-correctable error
in the documentation. Best to use acronyms in products and
documentation with some care, as folks just aren't reading
documentation the same way folks used to, too. The way many of us once
read the OpenVMS doc set from end-to-end.
Using "host-based volume shadowing" (HBVS) is a similarly poor idea, as
it utterly obfuscates one of the remaining and powerful differentiators
for OpenVMS, too. Users know this as mirroring or RAID-1. But I
As for writing and updating documentation, that's better written for
the actual end-users now and going forward, and to adopt clarity and
simplicity where possible, with reviews and end-user tests, and to use
the terms that end-user folks — such as the one that started off this
thread — expect. Documentation filled with cryptic acronyms and
arcane terms — and utterly lacking references to common terms — isn't
that. Not when it can be made simpler. Same for user interfaces,
There are certainly examples where simplicity lacks in OpenVMS, whether
in the documentation or its structure or navigation, or in the user
interfaces, or even in some parts of OpenVMS itself. Migration to and
use of common terminology is likely one. Overhauling the existing
clustering configuration implementation is another. Updating that
quarter-century-old robust OpenVMS programming document mentioned
else-thread is certainly yet another. These among the many projects
on the VSI list for OpenVMS.
Pure Personal Opinion | HoffmanLabs LLC