Christine Tran wrote:
zonecfg doesn't know about every option on every filesystem, bundled
and unbundled, that is available on Solaris. zoneadm does some
basic validation of fs entries but it too does not know about all
of the special options each filesystem might have.
Well, is this worth at
Jerry Jelinek wrote On 08/18/06 17:21,:
It is in the man page I just looked at (mount_tmpfs(1M)).
Oy, sorry, I just looked at mount(1M).
zonecfg doesn't know about every option on every filesystem, bundled
and unbundled, that is available on Solaris. zoneadm does some
basic validation of
Christine Tran wrote:
Hi,
I came across a zone example that looks like this:
fs:
dir: /tmp
special: swap
raw not specified
type: tmpfs
options: ["size=1024"]
Hmm ... I think I know what the person is trying to do,
Hi,
I came across a zone example that looks like this:
fs:
dir: /tmp
special: swap
raw not specified
type: tmpfs
options: ["size=1024"]
Hmm ... I think I know what the person is trying to do, give the zone
its own
Hello Brian,
Wednesday, July 26, 2006, 8:31:06 PM, you wrote:
BK> With the performance boosts included in recent solaris versions I'm
BK> told that there's not much of a difference between handing the database
BK> raw devices vs. using a filesystem anymore.
BK> To test this out, my customer woul
Hi there -
Thanks for all the responses; Just for the benefit of others,
below is the compiled responses for differentiating
sparse and whole root zones:
Basically, to look for the four default inherit-pkg-dir in the zonepath
/lib
/platform
/sbin
/usr
~ In case of a
