Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

lx(5) [opensolaris man page]

lx(5)							Standards, Environments, and Macros						     lx(5)

lx - Linux branded zone DESCRIPTION
The lx brand uses the branded zones framework described in brands(5) to enable Linux binary applications to run unmodified on a machine with a Solaris Operating System kernel. The lx brand includes the tools necessary to install a CentOS 3.x or Red Hat Enterprise Linux 3.x distribution inside a non-global zone. The brand supports the execution of 32-bit Linux applications on x86/x64 machines running the Solaris system in either 32-bit or 64-bit mode. Supported Linux Distributions The lx brand emulates the system call interfaces provided by the Linux 2.4.21 kernel, as modified by Red Hat in the RHEL 3.x distributions. This kernel provides the system call interfaces consumed by the glibc version 2.3.2 released by Red Hat. In addition, the lx brand partially emulates the Linux /dev and /proc interfaces. Configuration and Administration The lx brand supports the whole root non-global zone model. All of the required linux packages are installed into the private file systems of the zone. The zonecfg(1M) utility is used to configure an lx branded zone. Once a branded zone has been installed, that zone's brand cannot be changed or removed. The zoneadm(1M) utility is used to report the zone's brand type and administer the zone. The zlogin(1) utility is used to log in to the zone. Application Support The lx zone only supports user-level Linux applications. You cannot use Linux device drivers, Linux kernel modules, or Linux file systems from inside an lx zone. You cannot add any non-standard Solaris devices to a Linux zone. Any attempt to do so will result in a zone that zonecfg(1M) will refuse to verify. You cannot run Solaris applications inside an lx zone. Solaris debugging tools such as DTrace (see dtrace(1M)) and mdb (see mdb(1)) can be applied to Linux processes executing inside the zone, but the tools themselves must be running in the global zone. Any core files generated are produced in the Solaris format, and such files can only be debugged with Solaris tools. ATTRIBUTES
See attributes(5) for a description of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWlxr, SUNWlxu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
mdb(1), zlogin(1), zonename(1), dtrace(1M), zoneadm(1M), zonecfg(1M), brands(5), zones(5), lx_systrace(7D) SunOS 5.11 19 Sep 2006 lx(5)

Check Out this Related Man Page

brands(5)						Standards, Environments, and Macros						 brands(5)

brands - alternate operating environments for non-global zones DESCRIPTION
The branded zone (BrandZ) framework extends the Solaris Zones infrastructure described in zones(5) to include the creation of brands, which provide non-global zones that contain non-native operating environments. The term "brand" can refer to a wide range of operating environments. All brand management is performed as extensions to the current zones structure. Every zone is configured with an associated brand. The brand type is used to determine which scripts are executed when a zone is installed and booted. In addition, a zone's brand is used to properly identify the correct application type at application launch time. The default is the native brand. A branded zone will support exactly one brand of non-native binary, which means that a branded zone provides a single operating environ- ment. Once a zone has been assigned a brand, that brand cannot be changed or removed. BrandZ extends the zones tools in the following ways: o A brand is an attribute of a zone, set at zone create time. o The zonecfg tool (see zonecfg(1M)) is used to set a zone's brand type and configure the zone. o The zoneadm tool (see zoneadm(1M)) is used to report a zone's brand type and administer the zone. Device Support The devices supported by each zone are documented in the man pages and other documentation for that brand. The zones infrastructure detects any attempt to add an unsupported device and issues a warning to the administrator. If the administrator chooses to add an unsupported device despite that warning, that device might or might not work as expected. The configuration will be untested and unsupported. ATTRIBUTES
See attributes(5) for a description of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWzoneu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
mdb(1), zlogin(1), zonename(1), dtrace(1M), in.rlogind(1M), sshd(1M), zoneadm(1M), zonecfg(1M), kill(2), priocntl(2), getzoneid(3C), ucred_get(3C), getzoneid(3C), proc(4), attributes(5), lx(5), native(5), privileges(5), zones(5), lx_systrace(7D), crgetzoneid(9F) SunOS 5.11 13 Feb 2009 brands(5)
Man Page

Featured Tech Videos