On Fri, 21 Jul 2017, Ryan Zezeski wrote:
; I couldn't find any specific instructions for moving to bloody so I kind
; of made them up based on the previous omnios upgrade instructions. I
; went ahead and set the signature-policy to ignore and now I'm good.
Sorry for the delay, timezone
I couldn't find any specific instructions for moving to bloody so I kind
of made them up based on the previous omnios upgrade instructions. I
went ahead and set the signature-policy to ignore and now I'm good.
On Fri, Jul 21, 2017, at 08:54 PM, Dan McDonald wrote:
> In the past, bloody was never
Oops, should've read more carefully.
YES, bloody isn't signed. I often create an alternat BE First, mount it, then
use "pkg -R" to keep the original stable BE safe.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Jul 21, 2017, at 7:11 PM, Ryan Zezeski wrote:
>
In the past, bloody was never signed. Has CE changed that policy?
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Jul 21, 2017, at 7:11 PM, Ryan Zezeski wrote:
>
> Hey everyone,
>
> I've been trying to reproduce this but can't seem to get my omniosce
> onto
Hey everyone,
I've been trying to reproduce this but can't seem to get my omniosce
onto bloody. I see the following:
root@midgar:~# pkg unset-publisher omnios
Updating package cache 1/1
root@midgar:~# pkg set-publisher -P --set-property
On Fri, 21 Jul 2017, Jim Klimov wrote:
; Hi all,
;
; I have an OmniOS bloody box that was last running 151023. Yesterday I updated
it to latest available original omnios from May 15 or so, and updated that BE
to omniosce bloody. Between the two, zone shutdown stopped working for me (both
Hi all,
I have an OmniOS bloody box that was last running 151023. Yesterday I updated
it to latest available original omnios from May 15 or so, and updated that BE
to omniosce bloody. Between the two, zone shutdown stopped working for me (both
ipkg and lx), with the ce variant claiming that