Someone earlier stated that this was also broken in SXDE-- as far as
I know that is *not* the case. One of the reasons this has been a
troublesome area is that in Nevada the /dev zones implementation is
radically different from S10, due to the existence of the "devnames"
project in Nevad
Hi,
On Solaris 10 8/07, I have an exclusive-IP non-global zone running alongside
several zones that share a physical interface. The interface used by the
exclusive-IP zone and the interface used by the shared zones are on separate
networks.
I'd like to have a network common to all and only th
On 10/1/07, EndaO'Connor <[EMAIL PROTECTED]> wrote:
>
> Dan Price wrote:
> > On Mon 01 Oct 2007 at 02:10PM, Gael wrote:
> >
> >> Thanks for the answer Dan, will the relief be a replacement for the
> binary
> >> itself or a full new kernel patch ? Trying to identify the impact on
> our
> >> environm
Dan Price wrote:
> On Mon 01 Oct 2007 at 02:10PM, Gael wrote:
>
>> Thanks for the answer Dan, will the relief be a replacement for the binary
>> itself or a full new kernel patch ? Trying to identify the impact on our
>> environment (ie reboot vs no reboot)
>>
>
> I'm not sure about reboot
On Mon 01 Oct 2007 at 02:10PM, Gael wrote:
> Thanks for the answer Dan, will the relief be a replacement for the binary
> itself or a full new kernel patch ? Trying to identify the impact on our
> environment (ie reboot vs no reboot)
I'm not sure about reboot vs. no reboot, but I believe the patch
Thanks for the answer Dan, will the relief be a replacement for the binary
itself or a full new kernel patch ? Trying to identify the impact on our
environment (ie reboot vs no reboot)
Regards.
On 10/1/07, Dan Price <[EMAIL PROTECTED]> wrote:
>
> On Mon 01 Oct 2007 at 01:14PM, John Chase wrote:
On Mon 01 Oct 2007 at 01:14PM, John Chase wrote:
>
> This has just been escalated as a P1 bug in 8/07.
>
Indeed. And please accept our apologies that this bug slipped out. This
was a case where a late performance fix wound up impacting correctness.
We're still assessing why our test suite (and
This is CR 6608977 "Can't add device to non-global zone in S10 update 4"
It is escalated and sustaining is working on a IDR.
Note that anybody with update 3 or lower could have introduced
this problem to their system by installing 120011-14. Unfortunately
no version below -14 was ever released.
This has just been escalated as a P1 bug in 8/07.
-JOhn
Gael wrote:
Hello,
Glad to see I'm not crazy, noticed the same issue following a few
upgrades this week end and working on a case with Sun support. I was
able to cpio the devices from the global zones for all except two (all
are r
Hello,
Glad to see I'm not crazy, noticed the same issue following a few upgrades
this week end and working on a case with Sun support. I was able to cpio the
devices from the global zones for all except two (all are raw devices)
Regards
On 10/1/07, Konstantin Gremliza <[EMAIL PROTECTED]> wrote:
Hi,
a collegue of mine mentioned a problem in both Solaris 10 >= 11/06
and Solaris Express 09/07.
Setting a device match in zonecfg like
this works fine:
zonecfg> add device
zonecfg:device> set match=/dev/*dsk/c6t0d0s*
zonecfg:device> end
But
zoneadm -z zone boot
wont create the necessa
11 matches
Mail list logo
