Michael Webb - Sun Microsystems wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
please respond directly to me as I am not on the alias.
I've built a number of zones for Sun Cluster deliveries so I know just
enough to get by.
I managed to zorch the /etc/zones~.xml files as well as the
On 10/31/07, Norm Jacobs [EMAIL PROTECTED] wrote:
Mike Gerdts wrote:
It seems as though printers.conf could point to localhost in the
master zone and the clones would then also point to their respective
selves. Is there something broken with that approach?
Not that we don't see it, but
Ping also seems weird.
I can ping boxes from the zone alright.
But I have big problems ping the zone.
box1 ping zone
65 packets transmitted, 46 packets received, 29% packet loss
round-trip (ms) min/avg/max/stddev = 0.807/9149./4.02e+04/1.17e+04
zone ping box1
51 packets transmitted, 51
Network can ping the zones and global zone
zones and global zone can't ping each other
:(
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
- I set the mount point as follows.
zfs set mountpoint=/zone/restricted/root/data zone/data
- I then added the dataset to the restricted zone using zonecfg. The full path
to the dataset is now /zone/restricted/root/zone/restricted/root/data. I am not
sure if that is what you intended, but it
In reviewing the current interfaces made available from
zones, it appears that ALL_ZONES and GLOBAL_ZONE
are still private interfaces - correct?
If so, if I'm forced to expose the existance of zones
through an API to kernel consumers and then somehow
map zone names into zoneid_t's. While
Howdy Claudio!
I am not sure what you are trying to do and I will take a stab at it.
The first thing to do is set up your network interface card (nic) for
the global zone.
Make sure you install nic normally and there is no need set routes.
Next you need to create network interfaces for your
There are some interesting ordering issues with respect to the steps
required for this configuration:
1. The dataset's mount point must be within the zone's root path for it
to be mounted read-write within that zone (you can't use lofs).
2. The dataset should not be mounted (by the global
