The following commands and features are unavailable on a Freedom server:
NFS. See the NFS service description in the previous section.
Mount. The mount command (and its alternative forms such as mount_nfs, mount_cd) cannot be used on a Freedom server and serves no purpose even if it could.
Kernel. Freedom products do not have their own kernel.
127.0.0.1 interface address. The 127.0.0.1 address of the network loopback device can be unpredictable inside of a Freedom account. Scripts and applications that are configured by default to bind to the 127.0.0.1 address (like RealServer) should be configured to point to the account’s actual IP address instead.
Physical Network Interface Manipulation. For security reasons as well as technological limitations, a Freedom server does not have the ability to directly manipulate the network interface on the machine. For this reason, features and applications that directly manipulate the network interface, such as those listed below, do not function on Freedom servers:
Ping. Although it can’t be done from inside a Freedom account, it can be done through the FATSI interface which runs on the physical box itself.
Traceroute. Although it can’t be done from inside a Freedom account, it can be done through the FATSI interface which runs on the physical box itself.
Packet based firewalls (ipfw). Firewall functions (via the ipfw command) cannot be used on a Freedom server because they require direct access to the network interface.
Additional IP addresses. All Freedom servers are limited to a single IP address due to technological limitations.
System Status Utilities. For security, as well as technological limitations, Freedom servers do not have access to some system status utilities, such as those listed below:
Top
Systat