df error for lofs file system in local zone.

Thread Tools Search this Thread
Operating Systems Solaris df error for lofs file system in local zone.
# 8  
Old 08-03-2009
Absolutely, I often do it. There is nothing specific. Just use the mount command.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

LOFS in Solaris zone, privileges

Hi all Can i check, if I have a lofs filesystem in my local zone (myzone) for - e.g. global-zone -> /db/myzone (/dev/dsk/c0t0d0s6 ufs) myzone-> /myzone (lofs filesystem) zonecfg -z myzone (add fs set dir=/myzone set special=/db/myzone set type=lofs )q1) If I have install... (0 Replies)
Discussion started by: javanoob
0 Replies

2. Solaris

Solaris zones - checking processes and lofs file system

Hi all, q1) If i am in a global-zone, is there any command or anyway to check if a particular process in "ps -ef" output is running in which zone ? q2) if i have created and mount a lofs filesystem/mountpoint for my non-global zone, can i say the following e.g. /dev/md/dsk/d60 /data --... (1 Reply)
Discussion started by: javanoob
1 Replies

3. Solaris

Obtaining system serial number from local zone

Hi, I need to install a license key for synergy which requires the server's serial number to be provided but since I'm installing it on a local zone, would the installation work? :wall: (4 Replies)
Discussion started by: thomas_j
4 Replies

4. Solaris

Covert Global zone to local zone

Dears, I would like to convert solaris 10 x86 and solaris 10 sparc (Global Zones) physical servers into Local zones. i found a document which seems to be helpful but i'm stuck @ the 1st step. to test this i want to do it 1st on x86 system running under vmware ESXi and if it succeeds i will... (1 Reply)
Discussion started by: mduweik
1 Replies

5. Solaris

Global zone name from local zone

How to check the global zone name from local zone. (6 Replies)
Discussion started by: fugitive
6 Replies

6. Solaris

/etc/system file in solaris Zone

Hi All, I am just new to the sun Solaris zone server. In the zone server the /etc/system file is missing. Please let me know what they are using instead of system file in Zone server. Please help me in this L Regards, Kalai (1 Reply)
Discussion started by: kalpeer
1 Replies

7. Solaris

LOFS file system

Hi All, Can you please help me in understanding the lofs file system or point me towards some link which can help ? Thanks (1 Reply)
Discussion started by: kumarmani
1 Replies

8. Solaris

Not able to ping global zone from local zone

Hi Gurus I am not able to ping the local zone from global zone when i am trying to ping i am getting below ICMP Host Unreachable from gateway zone ( for icmp from zone ( to sun1 ( However i can ping local zone from global please... (12 Replies)
Discussion started by: kumarmani
12 Replies

9. UNIX for Dummies Questions & Answers

how to mount a file system of a remote machine to local file system

Hi friends, In my case, there are serveral PCs running Linux in a LAN. I would like to to mount the directory /A_river of machine-A to the file system of another machine machine-B so that I can access files in that directory. I do not know how to do this. The situation is complicated by... (2 Replies)
Discussion started by: cy163
2 Replies
Login or Register to Ask a Question
zones(5)                                                Standards, Environments, and Macros                                               zones(5)

zones - Solaris application containers DESCRIPTION
The zones facility in Solaris provides an isolated environment for running applications. Processes running in a zone are prevented from monitoring or interfering with other activity in the system. Access to other processes, network interfaces, file systems, devices, and inter-process communication facilities are restricted to prevent interaction between processes in different zones. The privileges available within a zone are restricted to prevent operations with system-wide impact. See privileges(5). You can configure and administer zones with the zoneadm(1M) and zonecfg(1M) utilities. You can specify the configuration details a zone, install file system contents including software packages into the zone, and manage the runtime state of the zone. You can use the zlogin(1) to run commands within an active zone. You can do this without logging in through a network-based login server such as in.rlogind(1M) or sshd(1M). An alphanumeric name and numeric ID identify each active zone. Alphanumeric names are configured using the zonecfg(1M) utility. Numeric IDs are automatically assigned when the zone is booted. The zonename(1) utility reports the current zone name, and the zoneadm(1M) utility can be used to report the names and IDs of configured zones. A zone can be in one of several states: CONFIGURED Indicates that the configuration for the zone has been completely specified and committed to stable storage. INCOMPLETE Indicates that the zone is in the midst of being installed or uninstalled, or was interrupted in the midst of such a transition. INSTALLED Indicates that the zone's configuration has been instantiated on the system: packages have been installed under the zone's root path. READY Indicates that the "virtual platform" for the zone has been established. Network interfaces have been plumbed, file systems have been mounted, devices have been configured, but no processes associated with the zone have been started. RUNNING Indicates that user processes associated with the zone application environment are running. SHUTTING_DOWN Indicates that the zone is being halted. The zone can become stuck in one of these states if it is unable to tear DOWN down the application environment state (such as mounted file systems) or if some portion of the virtual platform cannot be destroyed. Such cases require operator intervention. Process Access Restrictions Processes running inside a zone (aside from the global zone) have restricted access to other processes. Only processes in the same zone are visible through /proc (see proc(4) or through system call interfaces that take process IDs such as kill(2) and priocntl(2). Attempts to access processes that exist in other zones (including the global zone) fail with the same error code that would be issued if the specified process did not exist. Privilege Restrictions Processes running within a non-global zone are restricted to a subset of privileges, in order to prevent one zone from being able to per- form operations that might affect other zones. The set of privileges limits the capabilities of privileged users (such as the super-user or root user) within the zone. The list of privileges available within a zone can be displayed using the ppriv(1) utility. For more informa- tion about privileges, see privileges(5). Device Restrictions The set of devices available within a zone is restricted, to prevent a process in one zone from interfering with processes in other zones. For example, a process in a zone should not be able to modify kernel memory using /dev/kmem, or modify the contents of the root disk. Thus, by default, only a few pseudo devices considered safe for use within a zone are available. Additional devices can be made available within specific zones using the zonecfg(1M) utility. The device and privilege restrictions have a number of effects on the utilities that can run in a non-global zone. For example, the eep- rom(1M), prtdiag(1M), and prtconf(1M) utilities do not work in a zone since they rely on devices that are not normally available. File Systems Each zone has its own section of the file system hierarchy, rooted at a directory known as the zone root. Processes inside the zone can access only files within that part of the hierarchy, that is, files that are located beneath the zone root. This prevents processes in one zone from corrupting or examining file system data associated with another zone. The chroot(1M) utility can be used within a zone, but can only restrict the process to a root path accessible within the zone. In order to preserve file system space, sections of the file system can be mounted into one or more zones using the read-only option of the lofs(7FS) file system. This allows the same file system data to be shared in multiple zones, while preserving the security guarantees supplied by zones. NFS and autofs mounts established within a zone are local to that zone; they cannot be accessed from other zones, including the global zone. The mounts are removed when the zone is halted or rebooted. Networking Zones can be assigned logical network interfaces, which can be used to communicate over the network. These interfaces are configured using the zonecfg(1M) utility. The interface is removed when the zone is halted or rebooted. Only logical interfaces can be assigned to a zone. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
zlogin(1), zonename(1), in.rlogind(1M), sshd(1M), zoneadm(1M), zonecfg(1M), getzoneid(3C), kill(2), priocntl(2), ucred_get(3C), get- zoneid(3C), proc(4), attributes(5), privileges(5), crgetzoneid(9F) SunOS 5.10 13 Apr 2004 zones(5)