OpenVOS Blog

As the system administrator for a VOS system you typically could care less about what other hosts are on the local subnet. You care about the gateways that are configured and of course any local hosts that communicate with your system but the other hosts are below your radar. There are, however, 2 very good reasons for knowing who your network neighbors are.

FTP transfer times painfully high, Interactive login response time way too long, getting 1 mbps out of your 100 mbps network. While I always prefer to blame the network I have to admit that sometimes it is not the network.

A fresh port of Apache now containing PHP and a port of MySQL are now available.

How can you tell which open-source packages can be ported to VOS or OpenVOS? Read on…

I have recently reorganized the Open-Source files on the VOS anonymous FTP site to make it easier to find programs that have been ported to a specific platform.

Packet_monitor can be a very powerful diagnostic tool, but only if used with the correct arguments. This post will describe which arguments to use to use in order to get the most diagnostic bang per packet.

We've centralized the collected wisdom of the Stratus software engineers who have ported open-source code.

By default the start_stcp command macro will start the stcp_inetd, ftpd, telnetd, and snmpd processes. The only one required by VOS is telnetd. The others are safe to stop if you are not using them.

More and more security and network administrators are prohibiting the use of telnet. Unfortunately, the Stratus RSN requires that the Stratus module run a telnet server. That, however, does not mean that you cannot meet the spirit, if not the letter, of the telnet restriction.

In speaking with people about SSH I have discovered that there is significant confusion between the release and protocol versions. This is my attempt to explain the differences.