TCP was designed to support end to end connections, that is, one host communicating directly with another host. Sure, there were bridges and routers in between, but those devices didn’t touch the TCP header or the payload.
When you contact customer support with a problem, the typical goal is to get it resolved FAST. I have observed that in many instances the initial contact with support coordination makes a fast resolution much less likely. This blog provides some tips to help speed up problem resolution.
“We just upgraded from a T1 (1.544 mbps) to a T3 (44.736 mbps) so why is it still taking 90 minutes to copy that file?”
Thank goodness for regression tests. There I was, earlier this week, feeling really good about some new code that I had written and (I thought) debugged.
Over the years we have added a number of UNIX® features to VOS. One of the simplest and most useful of these is the ability to use dot (“.”) and dot-dot (“..”) as pathnames.
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).
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.
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.