Re: [indiana-discuss] OpenSolaris package repository update, development build 127, x86/x64/SPARC (15 new packages)

2009-11-16 Thread Chris Ridd
On 15 Nov 2009, at 21:18, Vikram Hegde wrote: > Hi, > > *If* the VM has a PCIE-PCI bridge and you disabled pcieb, then yes the system > will panic > but with a different stack trace. The stack trace that you are seeing > indicates some sort > of problem with path_to_inst. In the case of VMWare

Re: [indiana-discuss] NTP broken in snv_127

2009-11-16 Thread Tom Whitten
It probably would have been sufficient to "svcadm restart ntp" without adding the symlink. I suspect that the SMF property that controls the start method got changed in the manifest during the upgrade. Unfortunately, the manifest change does not get reflected in the repository until the manifest-

[indiana-discuss] IPS distro-import changes needed for X packages for nv_128

2009-11-16 Thread Alan Coopersmith
These changes in the X packages in Nevada build 128 will need updates to the IPS distro-import package definitions for those packages. As usual, this only lists the changes that need distro-import changes, the full list of X changes in these builds can be seen at: http://hub.opensolaris.org/bin/vi

Re: [indiana-discuss] NTP broken in snv_127

2009-11-16 Thread Gary Mills
> > It probably would have been sufficient to "svcadm > restart ntp" without > adding the symlink. I suspect that the SMF property > that controls the > start method got changed in the manifest during the > upgrade. > Unfortunately, the manifest change does not get > reflected in the repository >

Re: [indiana-discuss] NTP broken in snv_127

2009-11-16 Thread Tom Whitten
Gary Mills writes: > > > > It probably would have been sufficient to "svcadm > > restart ntp" without > > adding the symlink. I suspect that the SMF property > > that controls the > > start method got changed in the manifest during the > > upgrade. > > Unfortunately, the manifest change does not