1lx(5)                 Standards, Environments, and Macros                lx(5)
2
3
4

NAME

6       lx - Linux branded zone
7

DESCRIPTION

9       The lx brand uses the branded zones framework described in brands(5) to
10       enable Linux binary applications to run unmodified on a machine with  a
11       Solaris Operating System kernel.
12
13
14       The  lx  brand  includes the tools necessary to install a CentOS 3.x or
15       Red Hat Enterprise Linux 3.x distribution inside a non-global zone. The
16       brand  supports  the  execution of 32-bit Linux applications on x86/x64
17       machines running the Solaris system in either 32-bit or 64-bit mode.
18
19   Supported Linux Distributions
20       The lx brand emulates the system call interfaces provided by the  Linux
21       2.4.21  kernel,  as  modified by Red Hat in the RHEL 3.x distributions.
22       This kernel provides the system call interfaces consumed by  the  glibc
23       version 2.3.2 released by Red Hat.
24
25
26       In  addition,  the lx brand partially emulates the Linux /dev and /proc
27       interfaces.
28
29   Configuration and Administration
30       The lx brand supports the whole root non-global zone model. You  cannot
31       use the inherit-pkg-dir resource with the lx brand. All of the required
32       linux packages are installed into the private file systems of the zone.
33
34
35       The zonecfg(1M) utility is used to configure an lx branded zone. Once a
36       branded zone has been installed, that zone's brand cannot be changed or
37       removed. The zoneadm(1M) utility is used to  report  the  zone's  brand
38       type  and  administer the zone. The zlogin(1) utility is used to log in
39       to the zone.
40
41   Application Support
42       The lx zone only supports user-level Linux applications. You cannot use
43       Linux  device drivers, Linux kernel modules, or Linux file systems from
44       inside an lx zone.
45
46
47       You cannot add any non-standard Solaris devices to a  Linux  zone.  Any
48       attempt  to do so will result in a zone that zonecfg(1M) will refuse to
49       verify.
50
51
52       You cannot run Solaris applications inside an lx zone.  Solaris  debug‐
53       ging  tools such as DTrace (see dtrace(1M)) and mdb (see mdb(1)) can be
54       applied to Linux processes executing inside the  zone,  but  the  tools
55       themselves must be running in the global zone. Any core files generated
56       are produced in the Solaris format, and such files can only be debugged
57       with Solaris tools.
58

ATTRIBUTES

60       See attributes(5) for a description of the following attributes:
61
62
63
64
65       ┌─────────────────────────────┬─────────────────────────────┐
66       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
67       ├─────────────────────────────┼─────────────────────────────┤
68       │Availability                 │SUNWlxr, SUNWlxu             │
69       ├─────────────────────────────┼─────────────────────────────┤
70       │Interface Stability          │Evolving                     │
71       └─────────────────────────────┴─────────────────────────────┘
72

SEE ALSO

74       mdb(1),  zlogin(1),  zonename(1), dtrace(1M), zoneadm(1M), zonecfg(1M),
75       brands(5), zones(5), lx_systrace(7D)
76
77
78
79SunOS 5.11                        29 Jul 2009                            lx(5)
Impressum