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
> >> itself or a full new kernel patch ? Trying to identify the impact on
> >> environment (ie reboot vs no reboot)
> > I'm not sure about reboot vs. no reboot, but I believe the patch will be
> > to libzonecfg. The bug is simply a logic error in the library, in the
> > function which decides whether or not a device should be made available
> > to the zone, or not.
> > -dp
> If it's just libzonecfg, we should be able to get away with a very
> simple patch, no reboot etc.
> Should not be a KU.
I was able to get the database zone fixed here by recreating all raw
devices into /zones/db/dev/*dsk/ with mknod and the /devices entries in the
Unix Delivery Services - Solaris Managed Services (aka Zones)
UnitedHealth Group IT, Enterprise Shared Services
6150 Trenton Lane, MN013-N300, Plymouth, 55442, MN
zones-discuss mailing list