No. This may be addressed in the future. However, the filesystem can be LOFS-mounted into the local zone, and, if necessary, the global zone can export the same filesystem via NFS so that other computers can also access those files. [August 2005] See similar questions...

The LinkGear is shipped with an NFS server and can be used to access the target filesystem. Because the nfs server is not enabled by default, a few steps are necessary. First, connect the LinkGear to the network. In this example the eth1 port is used. The default setting for eth1 is a static IP address of 192.168.0.1. There is also, as shipped, a dhcp server running on eth1. If your setup requires a different IP address or eth1 configured as a dhcp client, see Appendix B in the Startup Guide. See similar questions...

That depends on the settings used when the package was created. See the Packaging sections at docs.sun.com. See similar questions...

Some versions of the Linux NFS code only accept mount requests from a privileged port; try # mount -o -P linuxbox:/blah /mnt See similar questions...

Sun workstations running SunOS 4.X only accept mount requests from a privileged port; try # mount -o -P sunbox:/blah /mnt The most frequent problem is not understanding the correct format of /etc/exports. Please review exports(5) and the NFS entry in the Handbook, especially the section on configuring NFS. See similar questions...

Yes, but there is no guarantee it will always work. There are no restrictions in the software which limit where the source data is located. However, CD-R requires a continuous stream of data as it is writing, and a busy network could interfere with performance. Also remember, the greater the recording speed the greater the sustained data transfer rate the drive requires. It is easy to test using a Dummy Write. Slow down the write speed and increase the buffer size. See similar questions...

Some versions of the Linux NFS code only accept mount requests from a privileged port; try # mount -o -P linuxbox:/blah /mnt See similar questions...

The Solaris Zones feature set provides the global zone administrator with the ability to allow a non-global zone to access a raw device. There are many situations where this will be the best approach to solve a problem. There are even situations which require such use. First, however, it is important to stress that there are usually other solutions that do not require direct device access. Let's discuss this first. See similar questions...

there is only one TCP/IP stack, the complete network information must be configured from the Global zone. The Global zone administrator can add one (or more) default route for each subnet, the kernel will make sure that the right one is used for each non-global zone depending on its IP & netmask. See similar questions...

Not yet but it will be eventually. A Sun engineer has started working on this. More information. If you can live with an unsupported procedure, have a look at this lab. See similar questions...

Snoop works by talking to the “DLPI” interface that itself contacts the appropriate NIC drivers. To implement the network isolation feature of non-global zones, access to DLPI and the lower levels interfaces is disallowed. See similar questions...

Yes. Just use the “ifconfig” command from the Global zone. Don’t forget to also update the non-global zone’s configuration if you want the change to be persistent. See similar questions...

Yes! And no… The reource capping feature of Solaris Resource Management allows one to set an upper bound to the amount of RAM used by a certain project. By creating projects inside a non-global zone and setting the rcap.max-rss project parameter, you can limit the amount of memory used by all the processes belonging to that project. So it is not a zone-aware feature but it can be used within non-global zones through the use of projects. See similar questions...

You get NFS timeouts because you are using soft mounts. Normally, mounts are hard, which requires the client to continue attempts to reach the server forever. A soft mount allows the client to stop trying an operation after a period of time. A soft timeout may cause silent data corruption if it occurs during data or metadata transmissions, so you should only use soft mounts in the cases where client responsiveness is more important than data integrity. See similar questions...

On Solaris 10 systems, the traditional open configuration is installed. On SX systems, the limited networking configuration is installed. You can switch the zone to either networking configuration by using the netservices command, or enable and disable specific services by using SMF commands. [September 2006] See similar questions...

Yes, as long as it doesn’t require the exporting of a new disk device to the non-global zone. See Question 2.5 & Question 3.7 See similar questions...

Configurable only from the Global zone. A restriction is that IPFilter cannot be used to restrict access between 2 non-global zones. The loopback interface is used for that purpose and IPFilter cannot be used to inspect packets goign through that interface. See question 3.2. Starting with Solaris 10 06/06, Zfs is available as a standard supported feature. A siple HOWTO document describes few of the possibilities of integrating Solaris Zones & ZFS. Read the document or go to the sun. See similar questions...

Yes! The standard Resource Management features have been extended to zones. The Fair Share Scheduler is a scheduling class controlling the proportion of CPU time that a certain entity may use. The administrator of the Global zone is in charge of setting the new ressource control zone.cpu-shares to assign a number of shares to each non-global zone ( the Global zone is assigned 1 share by default ). See similar questions...

Yes! The Resource Management model being hierarchical, the first thing to do is to assign a number of shares to each non-global zone ( See 5.1 ). Within the non-global zone, the non-global zone administrator may now create projects in the standard way to differentiate between workloads running in the same non-global zone. Resource contention between these workloads can be resolved by assigning FSS shares to the projects. See similar questions...