On Fri, 22 Sep 2006, Wee Yeh Tan wrote:
> I do think there is an overall saving at least on my side although I
> really need to ask the guys from the other groups to know for sure.
Here's one qay zones will save time: deployment. Instead of going
througha whole installation (seperate server), on
Mark,
Here's what my organisation did with zones.
We basically gave administrative privileges to the respective groups
to manage their own zones. This turns out a lot cleaner since there
is less overlap of responsibility and really improved turnaroud time
launching new services. So the groups
Mark Mulligan wrote:
Hi Community,
I was wondering if any customers had done an evaluation on the
administrative time or cost (same thing really) improved by using the
efficiencies of Solaris Containers vs. managing individual servers with
just one Solaris 10 global zone or one Solaris 8/9 in
Hi Community,
I was wondering if any customers had done an evaluation on the administrative
time or cost (same thing really) improved by using the efficiencies of Solaris
Containers vs. managing individual servers with just one Solaris 10 global zone
or one Solaris 8/9 instance. This is a hot
Andreas Koppenhoefer writes:
> > See filesystem(5) -- non-OS software shouldn't be
> > delivering to /usr/bin.
>
> Good pointer! I've googled several times looking for some definition about
> correct use of /usr, /opt, etc., but did not find much regarding solaris.
> Most documents are about Lin
> Can you describe how this software installs? Does it install files to
> /usr/bin directly?
It splatters over several existing directories unter /usr, mainly /usr/bin,
/usr/share/man, /usr/lib and others.
> If so, then I'd argue that the software isn't
> really Solaris-compatible, let alone c
Andreas Koppenhoefer writes:
> > There's one notable option you didn't list: create
> > /usr/foo (where 'foo' is the directory into which this software
> > installs) as a writable directory within the zone. To do this, just
> > use "add fs" to create either a lofs, ufs, or zfs mount.
>
> Right, t
> There's one notable option you didn't list: create
> /usr/foo (where 'foo' is the directory into which this software
> installs) as a writable directory within the zone. To do this, just
> use "add fs" to create either a lofs, ufs, or zfs mount.
Right, that's another workaround we already use f
Andreas Koppenhoefer writes:
> Usually we install local zones for our customer as sparse root. That is /lib,
> /platform, /sbin and /usr as inherit-pkg-dir.
>
> Now suppose our customer requires a software to be installed in a single zone
> below /usr. In the first step this is not possible sinc
[EMAIL PROTECTED] writes:
>Thanks for the reply. After I make configuration changes withing
> zonecfg, how do you 'make' the changes to the running local zone? For
You can either reboot the zone or use ordinary administrative commands
to do it. For example, "mount -F lofs -o ro /some/dir
Usually we install local zones for our customer as sparse root. That is /lib,
/platform, /sbin and /usr as inherit-pkg-dir.
Now suppose our customer requires a software to be installed in a single zone
below /usr. In the first step this is not possible since /usr is read-only.
I already know abo
11 matches
Mail list logo
