Yes, the same restrictions apply as with normal Solaris 10 Containers with regard to having enough CPU, memory, disk, etc. Thus, this tool a way to simultaneously consolidate and transition to newer hardware and OS technologies.

Yes, you can run PostgreSQL in a Solaris Container and this is described in the How To Guide available at http://www.sun.com/software/solaris/howtoguides/postgresqlhowto.jsp#3. This is an excellent way to improve the security of your PostgreSQL installation.

Some versions of the GTK+ library from www.sunfreeware.org appear to be buggy, causing Wireshark to drop core with a Bus Error. Un-install those packages, and try getting the 1.2.10 version from that site, or the version from The Written Word, or the version from Sun's GNOME distribution, or the version from the supplemental software CD that comes with the Solaris media kit, or build it from source from the GTK Web site. Update the GLib library to the 1.2.

No, because of the BrandZ translation layer every Container can be on its own distinct Solaris 8 patch revision.

No. While most applications will run in the new environment there are a few restrictions with Solaris 10 Migration Assistant that mean that a few applications will not run. The initial part of the Enterprise Migration Implementation Service will assist the customer in identifying any known issues. A large reason that Sun can support the Solaris 8 environments running in this way is due to the Binary Compatibility Guarantee and the resulting stability of our interfaces.

When I run Tethereal with the "-x" option, why does it crash with an error "** ERROR **: file print.c: line 691 (print_line): should not be reached.

Some versions of the GTK+ library from www.sunfreeware.org appear to be buggy, causing Ethereal to drop core with a Bus Error. Un-install those packages, and try getting the 1.2.10 version from that site, or the version from The Written Word, or the version from Sun's GNOME distribution, or the version from the supplemental software CD that comes with the Solaris media kit, or build it from source from the GTK Web site. Update the GLib library to the 1.2.

The UltraSPARCIII processor only runs a 64-bit Solaris kernel. If your driver is a 32-bit driver, you will need to recompile your code to produce a 64-bit driver to be able to run on an UltraSPARCIII based machine. Several whitepapers are available with information on writing 64-bit drivers. You do NOT need to recompile your 64-bit driver code to run on an UltraSPARCIII processor.

Some users have reported poor sound quality and other problems under Solaris 8. It is thought that this is due to the new mixer code in Solaris 8 (there are white papers etc available from Sunsolve). I've heard there are internal bug reports on the mixer code which may or may not be related. I'm now using Solaris 8 and have yet to experience any problems, so I don't know how to fix it! If anyone does find a problem and can supply patches, let me know.

Assuming that you need 4 star fuel and that your car does around twenty miles per gallon, a box of 8 x 945 ml containers will take you almost 4,000 miles, i.e. it will make around 900 litres of leaded 4 star fuel. TetraBOOST costs around 12p per treated litre to make leaded 4 star. In summer 2007, most 4 star fuel sold on forecourts cost between £1.40 and up to £1.69 per litre. Therefore, TetraBOOST can make considerable savings over leaded pump fuel and is very good value for money.

Yes. MiniVend supports multiple independent catalogs. There are users who run more than 500 catalogs on a single machine. The capacity is usually a function of how busy the catalogs are and how much memory and processor speed your system has.

Multiple applications can share a single system but still remain completely isolated from one another Allows a system administrator to create an environment that the Container Administrator can customize for the application

The other components are the resource management tools in the Solaris OS. They control the amount of resources an application receives, such as CPU cycles, physical memory, and network bandwidth. Resource management tools also help with measuring the usage of an application. This could be used for health monitoring and capacity planning, as well as billing and charge back.

They interact as if they are on different systems, through the network or shared disk. For example, if they interact through the network, the system knows that one Solaris Container is talking to another, so communications will go through the network stack. Communication between Solaris Containers is very fast because it never leaves the system or even hits the network interface card.

Yes. Solaris Zones and the Solaris resource management feature are both part of Solaris Containers and are designed to work together.

The amount of hardware resources used by the applications versus the amount available in the system. This includes the number and processing power of CPUs, memory size, NICs, HBAs, etc. What portion of the installed zones are actually in use. For example, you can create 100 zones, each ready to offer a web service, but only boot the 10 that you need this month. The unbooted zones take up disk space, but do not cause the use of any extra CPU power, RAM, or I/O.

Solaris Zones are part of a Solaris Container, delivering security, application fault, and namespace isolation. The addition of Solaris Zone functionality to Solaris Containers allows the creation of a Solaris Container that is fully customized for an application.

The Solaris Cluster software currently supports the resource management parts of Solaris Containers. An updated release of the Solaris Cluster software will support Solaris Zones.

Yes, with Solaris 10 8/07 you can use Solaris Live Upgrade for patching and upgrading systems with Solaris Containers. This offers two important operational advantages, particularly around patching. You can patch without taking the system offline because you patch a copy of the system. Patching Containers is a serial operation, so patching without taking the system off-line is a major advantage. After patching the copy, you then can boot from that copy.

Multiple keyboards and mice are supported in Solaris 10 update1 and later. See patches listed in USB General section of this FAQ.

job configurations can be loaded from disk files or from a central database which facilitates job deployment in a mixed environment.

The Solaris 8 Migration Assistant is a software and services offering that helps customers to accelerate the migration of application environments currently using Solaris 8 to new systems running Solaris 10. For more information, please visit the Solaris 8 Migration Assistant web site.

The Solaris 8 Migration Assistant currently supports all releases of Solaris 8, however later patch and update versions are preferred.

A - Solaris 8 certification objectives contain significant revisions from Solaris 7 objectives. The Solaris 8 certification objectives include entire new sections (examples: Editor, Remote Connection ), omit others (examples: LP Print Service, Print commands), and reorganize the content in still other chapters. In addition, between Solaris 7 and 8, objectives within chapters have been revised. For instance, an objective focusing on the 'man' command was added to the System Concepts section.

How does Qemu know to exit? I am emulating Linux on Linux, and no matter how I shutdown, Qemu doesn't exit on its own.

Although none of the developers think it is particularly relevant, this question comes up frequently enough in the mailing lists that it is answered here. www.openbsd.org and the main OpenBSD ftp site are hosted at a SunSITE at the University of Alberta, Canada. These sites are hosted on a large Sun system, which has access to lots of storage space and Internet bandwidth. The presence of the SunSITE gives the OpenBSD group access to this bandwidth. This is why the main site runs here.

Yes - Yes - there is now support for control of multiple robots on the same Zigbee radio channel using the communication protocol defined in http://www.surveyor.com/SRV_protocol.html. You'll need to run SRV-1 firmware versions dated 101206 or later to take advantage of this capability.

an integral part of the Solaris 10 Operating System, Solaris Containers isolate software applications and services using flexible, software-defined boundaries. A breakthrough approach to virtualization and workload management, Solaris Containers let many private execution environments be created within a single instance of the Solaris OS.

Solaris Containers provide security, application fault, and name space isolation. This means that once working in Solaris Containers, users cannot compromise or even see outside of their Solaris Containers other than the regular ways, such as through the network or shared file systems. The name space isolation allows Solaris Containers to have their own users, and even their own root user, who only has authority inside the root user's own Solaris Container.