Are you still working on VOS using a 80 column by 24 line view? Get with the flow and see the big picture.
I recently revised our notes on how to port open-source code to VOS and OpenVOS. This new revision is about 30% longer and contains much more detailed information.
Stratus has offered ports of open-source, POSIX-based software to its VOS customers for many years.
I am often asked whether a particular open-source package can be ported to some release of VOS or OpenVOS (“VOS”, for short).
If you have used the POSIX shell (“bash”) on VOS, then you know that you can run various POSIX commands and use all of the nifty tricks that bash provides, such as input and output redirection.
I wrote the following remarks about conducting effective pre-production testing for my “VOS Corner” column in the Stratus User Group newsletter for December, 1996. They are still relevant today, almost 13 years later.
I enjoy meeting our VOS and OpenVOS customers. Customers ask me where we are headed with VOS/OpenVOS, and colleagues ask me where we should go with VOS/OpenVOS. I’ve often said that I get my best ideas from our customers.
Recently a number of VOS and OpenVOS customers have switched from using the standard ftp client (ftp.pm) to the secure ftp client (sftp.pm).
I have just uploaded a port of the GNU indent command to the VOS anonymous FTP site. This command adds or removes whitespace from a C program to make the appearance conform to a set of standards.
I’ve been doing some research into handling XML (Extensible Markup Language) data on VOS and OpenVOS, and I thought it would be useful to share what I learned with a wider audience.