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.

After the non-global zone has been installed, all kind of typical identity information needs to be provided. It can be done in two ways: Interactively : the Global zone administrator boots the zone for the first time. A “sysidtool” process ( the same that the one used for a standard installation ) is then launched inside the non-global zone. The administrator needs then to connect to the non-global zone console using the “zlogin -C my-zone” command.

Start the Active Directory Sites and Services Manager (Start - Programs - Administrative Tools - Active Directory Sites and Services Manager)

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.

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.

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.

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.

Some servers have no facility for this; you may be able to adjust your monitor to correct somewhat. Later versions of XFree86 allow these server options: gamma f set gamma value (0.1 < f < 10.0) Default: 1.0 -rgamma f set gamma value for red phase -ggamma f set gamma value for green phase -bgamma f set gamma value for blue phase

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.

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

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.

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 ).

Yes! First create a processor set that contains some of your CPUs ( be careful, you still need some CPU time for the Kernel! ). Then create a resource pool and bind the processor set to it. Finally bind your non-global zone to the same resource pool. All the processes running in your non-global zone will then run on the CPUs you selected by creating the processor set.

You can configure your own default search index in the Preference section, please note that this setting will not apply to all but specific accounts. For information about other personalized settings, please refer to Preference of the Search Guide.

The alternative is to create a boot image (either a simple NFS kernel with root over NFS or a full 16MB image with kernel and a small root filesystem, possibly NFS mounting things like /usr), dial the appliance up, and save that boot image into /dev/hd0 (gunzip <boot.image.gz >/dev/hd0). Beware: If you fuck it up, the device will never boot again, unless you rig up an IDE drive as described above. Some more detailed directions of this process are available at http://www.digitron.

By passing the JVM the http.proxyHost and http.proxyPort system properties, as described in the Action tasks section of the user manual.

On this page, we'll try to answer some of the more frequently asked questions about roses that we've heard from our customers. When you're faced with uncertainty about what to do with your roses, read as much as you can about roses and ask your gardenings friends for advice. But most importantly, relax -- remember, you're doing this because you want to! Taking care of roses is alot like taking care of anything -- you have to pay attention to them so you know when something is not quite right.

The numbers for all the countries/cities and necessary settings are all pre-configured in the program. Prior to using, you will need to set your username and password in the dialer. Once the dialer has successfully been installed, open the software and click on 'Options' > 'User Info'. Enter your username and password. You can also download the iPassConnect Pocket Guide for step-by-step instructions on using the service.

Click the link to download a data sheet that describes the procedure for configuring shop@home.pro to use the Global Commerce system. Global Commerce Data Sheet..