10-26-2010
Quote:
Originally Posted by
blicki
However, using LOFS to share one dataset into two local zones can be risky as hell, if both zones work on same data (read-write)
This doesn't make sense. Having multiple processes accessing the same file in r/w mode might be risky regardless of whether the file system is local or not and regardless of the accessing processes running on the same kernel or not. You can lofs mount in read-only mode should you want to avoid that specific issue. On the other hand, it is extremely common to have NFS, cifs or lofs shares in r/w mode and this definitely serves a purpose. File locking is the usual way to avoid multiple processes concurrently accessing the same file.
Quote:
Therefore I would use second opinion only.
You really shouldn't. This is not supported (see NOTES in the mount_nfs manual page). It is well know to create kernel deadlocks, which are much "riskier as hell" than the previous solution you discarded.
Bug ID: 6811806 automounter should prevent zone-to-global-zone mounts
9 More Discussions You Might Find Interesting
1. Solaris
I'm logged into a non-global zone server. How would I find out what the global zone server name is from there? (1 Reply)
Discussion started by: soupbone38
1 Replies
2. IP Networking
Hello,
I have a few Ubuntu 9.10 laptops I'm trying to learn NFS sharing with. I am just experimenting on this right now, so no harsh words about the security of what I'm playing with, please ;)
Below are the configs
/etc/exports on host
/home/woodnt/Homeschool... (2 Replies)
Discussion started by: Narnie
2 Replies
3. Solaris
Hi,
I have Global zone and 2 users: root and app.
I know password root and app. When a user app log - putty displays
Access denied
Using keyboard-interactive authentication.
In file /etc/security/policy.conf
I set CRYPT_DEFAULT=2a
And in file /etc/ssh/sshd_config
I set PermitRootLogin... (1 Reply)
Discussion started by: bieszczaders
1 Replies
4. Solaris
Hi Guys,
My requirement is I have file called /opt/orahome/.profile in non global zone.
PATH=/usr/bin:/usr/ucb:/etc:/usr/sbin:/usr/local/bin:/usr/openwin/bin:.
export PATH
PS1="\${ORACLE_SID}:`hostname`:\$PWD$ "
export PS1
EDITOR=vi
export EDITOR
ENV=/opt/orahome/.kshrc
export ENV... (1 Reply)
Discussion started by: vijaysachin
1 Replies
5. Solaris
Hi guru
Could any one help me by letting me know, how to see global hostname by logging in non global zones
Regards (2 Replies)
Discussion started by: girish.batra
2 Replies
6. Solaris
Hello Admins,
Does anyone has any idea on how to assign no. of cpu and memory to non-global zones on solaris 10.....
We have few zones in our environment. We wanted to assign memory and no of cpu's ..(e.g. 4Gb / 2 CPU's)
Thanks... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
7. Shell Programming and Scripting
Heyas
At home i have 1 nas with 3 shares, of which i used to mount 2 of them using a script with hardcoded password and username in it.
EDIT: Turns out, its not the script, but 'how i access' the nas share.. (-o user=XY,password=... VS. -o credentials=...).
Figured about credential files,... (0 Replies)
Discussion started by: sea
0 Replies
8. Solaris
Hi all - not really a problem as such, but just hoping someone can shed some light.
We point rexplorer to multiple Global zones and it works as expected. However, each Non-Global zone get around a hundred of root su'ing to root messages, i.e.:
SU 07/14 03:02 + ??? root-root
SU 07/14 03:02 +... (5 Replies)
Discussion started by: dlam
5 Replies
9. Solaris
Issue is : We have Solaris Global with 12 Zones and some have 15 Zones. All the OS version are10.
Is it possible to apply patch at Zone level instead of patching at Global level? Please let me know. (10 Replies)
Discussion started by: baladelaware73
10 Replies
UEFI(8) BSD System Manager's Manual UEFI(8)
NAME
UEFI -- Unified Extensible Firmware Interface bootstrapping procedures
DESCRIPTION
The UEFI Unified Extensible Firmware Interface provides boot- and run-time services to operating systems. UEFI is a replacement for the
legacy BIOS on the i386 and amd64 CPU architectures, and is also used on arm64 and ia64.
The UEFI boot process loads system bootstrap code located in an EFI System Partition (ESP). The ESP is a GPT or MBR partition with a spe-
cific identifier that contains an msdosfs(5) FAT file system with a specified file hierarchy.
Partition Scheme ESP Identifier
GPT C12A7328-F81F-11D2-BA4B-00A0C93EC93B
MBR 0xEF
The UEFI boot process proceeds as follows:
1. UEFI firmware runs at power up and searches for an OS loader in the EFI system partition. The path to the loader may be set by an
EFI environment variable. If not set, the default is /EFI/BOOT/BOOTX64.EFI. The default UEFI boot configuration for FreeBSD
installs boot1.efi as /EFI/BOOT/BOOTX64.EFI.
2. boot1.efi locates the first partition with the type freebsd-ufs, and from it loads loader.efi.
3. loader.efi loads and boots the kernel, as described in loader(8).
The vt(4) system console is automatically selected when booting via UEFI.
FILES
/boot/boot1.efi
First stage UEFI bootstrap
/boot/boot1.efifat
msdosfs(5) FAT file system image containing boot1.efi for use by bsdinstall(8) and the bootcode argument to gpart(8).
/boot/loader.efi
Final stage bootstrap
/boot/kernel/kernel
default kernel
/boot/kernel.old/kernel
typical non-default kernel (optional)
SEE ALSO
vt(4), msdosfs(5), boot(8), gpart(8)
HISTORY
UEFI boot support first appeared in FreeBSD 10.1.
AUTHORS
UEFI boot support was developed by Benno Rice <benno@FreeBSD.org>, Ed Maste <emaste@FreeBSD.org>, and Nathan Whitehorn
<nwhitehorn@FreeBSD.org>. The FreeBSD Foundation sponsored portions of the work.
CAVEATS
EFI environment variables are not supported by loader(8) or the kernel.
boot1.efi loads loader.efi from the first FreeBSD-UFS file system it locates, even if it is on a different disk.
boot1.efi cannot load loader.efi from a ZFS(8) file system. As a result, UEFI does not support a typical root file system on ZFS configura-
tion.
BSD
October 17, 2014 BSD