that
zones on a TX system are essentially an implementation detail, and
can't be used to create independent Solaris environments.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA
the 'ipf' module plumbed atop the 'aggr0' driver, so
you'll have a single stream.
If you were to use the older Sun Trunking solution, it would work only
if there were a single IP stream plumbed for the trunk.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1
within a zone, but could be used for other things.
For the shared IP address(es), packets are distinguished by the IP
security label option. Each zone has a label, and the label on the
packet maps it to a particular zone.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun
-global zone.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss mailing list
'vera1': $ANYTHING operation is invalid for zones in
state 'mounted'
zoneadm: zone 'vera1': call to zoneadmd failed
Try unmount.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington
issue here.)
Are you looking for someone to file the RFE, or are you planning to
visit bugs.opensolaris.org?
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757
between the zones without hitting the
NIC/wire.
huh?
Perhaps the right question in response is: what problem are you
seeing, and what are you trying to do?
It's quite unclear to me what would prompt a question about lofs that
looks like the above.
--
James Carlson, KISS Network
-administrable)
like the host name.
Instead, I think we need a way to ask the system (perhaps a new
ioctl?) whether a given known IP address represents a local address or
a remote one.
Or just fix the deadlock. ;-}
Seems like the kernel has to help out here.
I agree.
--
James Carlson, KISS Network
Steffen Weiberle writes:
PS. I was impressed with the linearity of ifconfig going through 8K
interfaces.
This is due to the work of the SolarMAX project, which converted the
kernel ipif database from a linear list to AVL trees.
--
James Carlson, KISS Network[EMAIL
and installation does fail on that...
In that case, whole root zones are probably the way to go, along with
making sure there isn't already a CR filed against the package in
question.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1
appear to be working.
It sounds to me like you need to talk to the group that supports
mpxio, rather than install or zones.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803
Jesus Cea writes:
Is there any plan to support live upgrade on machines with Solaris
zones?
Yes. The project code name is Zulu.
If affirmative, any timetable?.
I don't think we can share that at this time, but it's soon. The
plan is to have it in one of the S10 updates.
--
James Carlson
(such as the -b option) is
supported, unless somehow explicitly disclaimed.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
install crapped out. Possibly $ZONEPATH/lu is involved then.
As Enda said, I got around it by running a 'zoneadm -z myzone unmount'.
It is indeed internal. If you see it, then that's a bug.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive
' Filesystem Standard.
With this manpage originated by Sun we may get software vendor to fix their
software for beeing usable in local zones.
In the meantime, using whole-root zones where such software is
required is probably the least troublesome workaround.
--
James Carlson, KISS Network
loopback.
You need a network interface to do that.
Fortunately, it doesn't need to be a real interface. Doing something
like this should work:
# ifconfig ip.tun0 plumb 192.168.0.1 192.168.0.2 up
# ifconfig ip.tun0:1 plumb 192.168.0.2 192.168.0.1 zone test up
--
James Carlson, KISS Network
to is the UUID, then this is a
known problem. It's CR 6379341, which is fixed in Solaris 10 Update
06/06, and patches 122662-02 (SPARC) and 122663-05 (x86).
It's nothing to be worried about; the updates correct the problem, and
the software knows how to deal with it.
--
James Carlson, KISS Network
Stephen Hahn writes:
* James Carlson [EMAIL PROTECTED] [2006-10-05 13:47]:
Dan Price writes:
On Thu 05 Oct 2006 at 07:16PM, Alan Burlison wrote:
Someone using Solaris 10 Zones for hosting provision, cool to see
^^
[...]
Probably something to discuss
with upgrade.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss mailing list
appears to be CR 6367840 -- fixed in Nevada, but not S10.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
zonecfg:test:net set physical=bge1
zonecfg:test:net end
zonecfg:test verify
zonecfg:test commit
zonecfg:test exit
# zoneadm -z test reboot
The second case:
# ifconfig bge0:1 unplumb
# ifconfig bge1:1 10.12.13.14 netmask + broadcast + zone test up
--
James Carlson, KISS Network[EMAIL
remove the -b.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss mailing
Erik Nordmark writes:
James Carlson wrote:
I don't think that argument works on two counts. First, exclusive-IP
behavior does not offer complete IP isolation, because you can't (for
instance) install your own copy of Firewall-1 or Cisco VPN into a
non-global exclusive-IP zone
Erik Nordmark writes:
James Carlson wrote:
Erik Nordmark writes:
But the key thing to me is the consistency between where things can be
observed and where they can be modified.
We already have RFEs filed against other utilities because they don't
show non-global zone activity (see
is controlled by the proc_zone privilege. Normally, only a user
with all privileges will have this ability unless modified via RBAC.
Thanks. ;-}
I _knew_ it wasn't as simple as killing a process in the global zone.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun
Peter Baer Galvin writes:
Hi, any update on the status of the Zulu project!? thanks.
It integrated into build 53. Work is continuing now on cleaning up
some related bugs and backporting for S10.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network
the ability to
print them out.
Other than that, it should be just as it was before, except that you
can now live-upgrade a system with non-global zones.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS
.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss mailing list
zones
that file system is mounted?
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones
this support to Live Upgrade, so that
all the upgrade mechanisms are supported.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
to be no difference among those numbers, as it's
the same stack being driven in the same code paths. Zones are not an
emulation layer.
It's puzzling that you're seeing a difference at all.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive
Jeff Victor writes:
Yes, I did. As I said in that msg, don't read too much into those numbers.
You went and read too much into them, didn't you? :-)
Yeah, ok, I'm like that. ;-}
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive
state, in which all file systems are mounted, but no
processes are running in the zone. I can probably make the design
document that describes scratch zones public if you need it.
--
James Carlson, KISS Network[EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss mailing list
zones
. But, if you do, then propose an ACR for detached zones
project and have at it.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
(perhaps with Zones
extensions) to do that, or zonecfg if I'm interested in the start-time
configuration of the zone.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757
inside the zone.
Use 'zonecfg' instead.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
believe that they have talked about the problem, though I don't
(immediately) see a related project on opensolaris.org. It definitely
needs their input.
See also CR 4963321.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W
. (others can then
attach to it in order to hopefully influence its priority)
I cited the RFE in my previous message -- it's CR 4963321.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212
Jeremy Teo writes:
I cited the RFE in my previous message -- it's CR 4963321.
James, would you mind sharing the rest of the info in CR 4963321?
b.o.o. says see comments :)
Wretched, I know.
I'll see what I can do with it.
--
James Carlson, Solaris Networking [EMAIL PROTECTED
of circumstances. ;-}
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss
and associated configuration
files are inaccessible from within a non-global zone, and thus have no
effect there.
I think things may be different in TX zones, though.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781
case hasn't been solved.
I don't think it's a special problem that's particular to allowing
non-global zones to be NFS servers.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA
the system too much after having
interrupted a packaging change.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss mailing list
zones-discuss
and dependency tree aware of distributed applications --
and the usage of the new feature would be independent of (though
perhaps useful for) Zones.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212
this is a nobrainer.
We can even have dependencies between smf services across zones.
I agree there's likely a real need for this. I'm just wary that it'll
leak into places where it's _not_ the right answer.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1
requestor wanted. He wanted
multiple addresses on the same interface. Fortunately, I think that
works just by using the same 'physical' for multiple 'add net'
sections.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781
there, that won't work), and the NFS server hasn't been
virtualized (meaning that you can't yet have an NFS server in a
non-global zone).
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA
this.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss mailing list
zones-discuss
isn't the only one; there's also
lsof and probably ntop as well) would be a _very_ nice thing to have.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N
(pidentd isn't the only one; there's also
lsof and probably ntop as well) would be a _very_ nice thing to have.
Yep. But defining an interface is hairy, specially considering locking
and performance.
*sigh*
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1
complicated mechanism for causing it. A simple
nslookup something badIP works as well.
If it's that easy to encounter, then this needs to be looked at much
more urgently. I've bumped up the priority of this bug to P2.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems
) to expose the features you need. I assume that the
reason you're not doing this is that delivery of Install updates on
which this new feature depends would be more difficult. Is that
right?
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive
capability.
I didn't see it on that roadmap, but ok ...
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
that (if it is a problem) you can at least detect it and
fail out.
I will add some material
explaining this assumption to the proposal.
OK.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212
packaging database will live, among other
important zone-private things.
Did you add this to the zone configuration on your own (if so, why?),
or did some script do it for you (if so, what script?)?
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive
on
opensolaris.org and the mercurial change log is not terribly
revealing.
It's an open case, so everything ought to be there. I'll drop a line
to the ARC discuss list.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442
-global zones..
Sure. Ipf rules specified for the global zone apply to all 'regular'
(non-exclusive) non-global zones as well.
The rules themselves don't have a way to filter based on Zone ID or
name, but you can still filter based on address.
--
James Carlson, Solaris Networking [EMAIL
answer is to go with some VM-like solution, such as
Xen, LDOMS, Domains, or VMware.
All this allows is filtering between zones the global zones ipf rules..
Yes; that's what the loopback intercept is for.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1
larry lancaster writes:
when i use zones, can I migrate then without havign to reboot my machine?
Is ohter words is the zone migration static or live?
The zone itself must be shut down in order to migrate, but the machine
itself doesn't need to be rebooted.
--
James Carlson, Solaris
, but it's worth some thought.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss
products, not on the Zones feature itself.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
that you find elsewhere may not necessarily work.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
Dan Price writes:
On Thu 26 Jul 2007 at 05:04PM, James Carlson wrote:
Here's a code snippet :
ZONECMD=${PKG_INSTALL_ROOT}/usr/bin/zonename
That's the broken part. That should be just:
ZONECMD=/usr/bin/zonename
I'm lacking context here, slightly, but...
Isn't it also
the ip-type
property in zonecfg(1M).
(Are you running an OpenSolaris-based distribution? If so, then if
you have a recent enough build, you should already have this feature.)
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W
suggest that a single virtualization
group would be a good way to start.
In fact, other than a possibly excessive list of community group
leaders and core contributors, I find it a little hard to understand
why separate CGs would be helpful here.
--
James Carlson, Solaris Networking
. Just create a directory
and export it into the desired non-global zones via lofs.
The alternative is to choose some other means for sharing files --
such as (for example) a web, ftp, ssh, or rsync server running in the
non-global zone.
--
James Carlson, Solaris Networking [EMAIL
) to carry the same bits twice -- once as packages
(for regular upgrades of global-zone-only systems) and then again as a
set of patches (for Ashanti upgrades of systems with non-global
zones). It wasn't sustainable.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun
Mike Gerdts writes:
On 8/16/07, James Carlson [EMAIL PROTECTED] wrote:
Previously (in S10u1 through S10u3) the upgrade mechanism consisted of
some tricky patch-based work, from a project code-named Ashanti.
The problem with that mechanism is that it required the distribution
medium (DVD
zonecfg:blue:fs set special=/export/blue-itp-configuration
zonecfg:blue:fs set type=lofs
zonecfg:blue:fs end
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N
, and that a common community
would serve no useful purpose.
I don't quite agree, but in our last OGB meeting, we did approve the
LDoms community proposal.
Going ahead with a virtualization community that _doesn't_ involve
LDoms seems much more feasible to me.
--
James Carlson, Solaris Networking
.
The only ones in favor of the broader community were the other groups,
such as Xen:
http://mail.opensolaris.org/pipermail/ogb-discuss/2007-August/002234.html
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442
of overlap are. If anything, the zones project was the odd man
out, since they virtualize at a different level of the stack than Xen and
LDoms.
Even with Zones, I'd expect software packaging, install, and
maintenance issues to be shared (at least in part) with the other
groups.
--
James Carlson
refused
What's the status of svc:/network/shell:default in that zone?
Did you perhaps configure zone2 and forget to go through sysid?
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212
. In general, you ought not be using them
anymore. Try ssh instead.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
[EMAIL PROTECTED] writes:
It is enabled but uninitialized.
Aha.
That almost certainly means that you need to log into the console of
that zone and answer the questions that sysidtool is asking.
You can look at svcs -x to find out more about the state of the zone
services.
--
James Carlson
time zone) are what's blocking it from booting up.
Once you've done that, it'll boot up correctly.
Alternatively, you can make sure that you use a sysidcfg file when you
install the zone. There are references to this in the documentation ...
--
James Carlson, Solaris Networking
Damien Carbery writes:
If someone inside Sun would like to poke around the machine (it's in Dublin),
I can provide the login details.
This is a zlogin bug (actually, several bugs). I'm writing up the CR
now.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun
to hold network interface
'qfe2'.: Invalid argument
zoneadm: zone 's8-zone-ose005': WARNING: unable to hold network interface
'hme0'.: Invalid argument
That's expected.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox
there will not be mirrored into the zone, because lofs
doesn't cross mount points.
There currently isn't a mechanism that will do exactly what the
original poster asked. The individual mounts would need to be
replicated in each zone.
--
James Carlson, Solaris Networking [EMAIL PROTECTED
-1.8.1.txt
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss mailing list
[EMAIL PROTECTED] writes:
Are you sure? lofs generally missors the entire tree below the
mountpoint and not just the toplevel mount.
Doh; I tried with nfs mounts. You're right.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive
.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss mailing list
zones
, which is why I generally recommend
against /etc/netmasks. It may have been an ok interface 20 years ago,
but with CIDR, it's mostly a defect looking for a place to happen.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1
address. That's why they say NOXMIT when you configure them.
The global zone has 192.168.200.14 configured on bge0
You need to give your zones access to bge0 if you want them to
transmit there. You give access by assigning an address on that
interface.
--
James Carlson, Solaris Networking
/#cfg_io
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-discuss mailing list
to delete the inherit-pkg-dir entries to create a whole root
zone.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
. Quite a few changes have gone into
OpenSolaris-based distributions that haven't gotten back (and may
never get back) to S10.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA
is with the design of the driver. If it uses GLDv3, then
zoneadmd can issue a special new ioctl to move the link into the
zone. If it doesn't use GLDv3, then that doesn't work.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1
.
But non-GLDv3 drivers can also be modified (with some difficulty) to
support the feature, and that's what's being done for 'ce.'
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington
Ihsan Zaghmouth writes:
James Carlson wrote:
There is an interesting support issue for Trunking and/or Aggregation
that needs to be addressed
to support of ce and ge by GLDV3.
Indeed.
Solaris Trunking 1.3 does support ce and ge, unlike Solaris 10
Aggregation (dladm).
Since dladm
bridging works, so how do zones cause problems?
Or what problems do you specifically see?
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781
bits are set -- and that can be placed into a non-global zone.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
the first obvious step.
Is it perhaps Indiana? If so, then you should be contacting that
project team directly.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757
to schedule another connection
attempt.
Any time the dependency lines on the graph extend outside the confines
of the box, we need to be very careful. Networking is _not_ the same
as system design, and SMF addresses only the latter.
--
James Carlson, Solaris Networking [EMAIL
running?
If you're using Solaris 10, you should be contacting Sun's support
group instead. (I believe IP Instances went into Solaris 10 Update 4,
but, unlike OpenSolaris, some Ethernet drivers are not supported, and
you may need patches for others.)
--
James Carlson, Solaris Networking
. But
since you're not using OpenSolaris, you should be working with your
local support folks on that rather than an OpenSolaris-related mailing
list.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS
worked.
I strongly disagree that we should be offering any sort of routing is
ready checkpoint or SMF dependency. It'd be misleading at best, and
would result in a new class of unsolvable failure modes.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun Microsystems / 35
Ellard Roush writes:
James Carlson wrote:
That point in time is as soon as your application can start. It need
not have any dependencies at all.
Here is the other point that needs to be clarified.
This is not an application.
Applications do not start until much later.
We have to get
1 - 100 of 182 matches
Mail list logo
