Re: [OmniOS-discuss] Unexpected BE name after upgrade to r151020

2017-01-02 Thread Bob Friesenhahn
After some consideration, I realize that it could be difficult to know an appropriate boot environment name since all that is known is the publisher setting. It is necessary to download something from the new publisher in order to know a better default naming. Perhaps what is needed is a

[OmniOS-discuss] Unexpected BE name after upgrade to r151020

2017-01-02 Thread Bob Friesenhahn
Today I upgraded from r151018 to r151020 using the lipkg zones procedure described at https://omnios.omniti.com/wiki.php/Upgrade_to_r151020 The upgrade seems to be successful and the /etc/release file in the global and non-global zones says r151020. However, I was surprised that the default

Re: [OmniOS-discuss] ms.omniti.com Publisher tuntap manifest missing

2017-01-02 Thread Volker A. Brandt
[Happy New Year everyone!] Hi Dale! > Just closing the loop on this - the tuntap driver is now part of > OmniOS-proper, from 014 onwards. As such, the tuntap package in the > ms.omniti.com repo has been removed, and I've corrected the issue you > reported. That's nice. While you are there,