Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
Sweet! This is all great news. On Fri, Jul 14, 2017 at 4:59 AM Tobias Oetiker wrote: > Our first release only contained userland updates (careful as we are) > the next one (r151022i) will also feature actual illumos things like > the loader. > > cheers > tobi > > - On Jul 14, 2017, at 3:48 AM, Paul B. Henson hen...@acm.org wrote: > > > On Fri, Jul 14, 2017 at 01:31:51AM +, Mini Trader wrote: > > > >> Can the new boot loader handle 4K drives with this release? > > > > The fix for illumos issue 8303 appears to have been commited to the > > r151022 branch of the omniosorg illumos-omnios repo on 7/8, and r151022h > > was released 7/12, so I'd guess yes. But it's just a guess :). Great to > > see backports hitting r151022 LTS code... > > > >> > > ## OmniOSce r151022h, 12th July 2017 > > > > ___ > > OmniOS-discuss mailing list > > OmniOS-discuss@lists.omniti.com > > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > -- > Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland > www.oetiker.ch t...@oetiker.ch +41 62 775 9902 > ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
Our first release only contained userland updates (careful as we are) the next one (r151022i) will also feature actual illumos things like the loader. cheers tobi - On Jul 14, 2017, at 3:48 AM, Paul B. Henson hen...@acm.org wrote: > On Fri, Jul 14, 2017 at 01:31:51AM +, Mini Trader wrote: > >> Can the new boot loader handle 4K drives with this release? > > The fix for illumos issue 8303 appears to have been commited to the > r151022 branch of the omniosorg illumos-omnios repo on 7/8, and r151022h > was released 7/12, so I'd guess yes. But it's just a guess :). Great to > see backports hitting r151022 LTS code... > >> > > ## OmniOSce r151022h, 12th July 2017 > > ___ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch t...@oetiker.ch +41 62 775 9902 ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
On Fri, Jul 14, 2017 at 01:31:51AM +, Mini Trader wrote: > Can the new boot loader handle 4K drives with this release? The fix for illumos issue 8303 appears to have been commited to the r151022 branch of the omniosorg illumos-omnios repo on 7/8, and r151022h was released 7/12, so I'd guess yes. But it's just a guess :). Great to see backports hitting r151022 LTS code... > > > ## OmniOSce r151022h, 12th July 2017 ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
Cool! Can the new boot loader handle 4K drives with this release? On Thu, Jul 13, 2017 at 6:51 PM Gary Gendel wrote: > This is very exciting. Thanks for the hard work to get things going. > > Gary > On 7/12/2017 11:32 AM, Tobias Oetiker wrote: > > # OmniOS Community Edition > > > > On April 21st 2017, OmniTI announced that they would suspend active > development of OmniOS and support contracts would not be renewed. > > > > While this announcement left many users stunned, others focused more on > the fact that OmniTI in their announcement also expressed the hope that > "the community" would take up further development of the OS. 14 weeks > later, OmniOS Community Edition is a reality. > > > > Andy Fiddaman (www.citrus-it.net), Tobias Oetiker (www.oetiker.ch) and > Dominik Hassler have spent some quality time setting up the systems and > procedures allowing us to take over maintenance and development of OmniOS. > In this endeavour we were supported by many. Special thanks to Stefan Husch > (www.qutic.com), Peter Tribble (www.petertribble.co.uk), Dan McDonald and > Theo Schlossnagle (www.circonus.com). > > > > We have forked the OmniOS repos and pulled in bugfixes and security > fixes that have been published since the release of OmniOS r151022. After > setting up our own package repository and updating the build > infrastructure, we are finally ready to go public. We are following the > established OmniOS release naming scheme by releasing > > > > > > ## OmniOSce r151022h, 12th July 2017 > > > > The new release contains the following fixes: > > > > - expat updated to version 2.2.1 (fixes CVE-2017-9233) > > - openssl updated to version 1.0.2l > > - curl updated to version 7.54.1 > > - bind updated to version 9.10.5-P3 > > - p7zip updated to fix CVE-2016-9296 > > - web/ca-bundle updated to include OmniOSce Certificate Authority > certificate > > > > `uname -a` shows omnios-r151022-f9693432c2 (no change in this release) > > > > Our work does not stop here though. First we are committed to quickly > releasing updates for r151022 as the need arises. We are also working > towards releasing r151024 on schedule. To that end, we have already updated > the bloody environment with all the latest goodies from upstream illumos > and joyent-lx repositories. > > > > OmniOS community edition hosts its sources on > https://github.com/omniosorg/ and if you want to get in touch, you can > find us on https://gitter.im/omniosorg/Lobby > > > > > > ## Release Schedule > > > > The intention is for new stable releases to continue to come out every > 26 weeks. Interim, "weekly" updates to stable follow a fixed schedule > denoted by letters, one per week. Weekly releases are made as needed, so > there may not be a release each week. The first release of a new stable > version is synonymous with weekly release "a", though the letter is not > used. > > > > During the intervals between stable releases, Bloody moves forward > rapidly, picking up changes from upstream illumos-gate and illumos-joyent > as well as updating various userland packages. In general, upstream merges > will be performed on a Thursday/Friday each week and weekly releases will > be published on a Monday. > > > > Bloody releases will be published on an ad-hoc basis but may be as > frequent as every week. > > > > Security fixes are excluded from the schedule and handled with priority > as they occur. > > > > > > ## How to Upgrade > > > > All OmniOS packages are signed and the pkg installer is configured to > only allow trusted sources for the core packages. In order to upgrade to > the new OmniOS community edition, you have to let your box know that the > updates will be coming from a new trusted source. This means you will have > to import our CA certificate into your system. > > > > 1. Get a copy of the new certificate > > > > ``` > > # /usr/bin/wget -P /etc/ssl/pkg \ > > https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem > > ``` > > > > 2. Check the certificate fingerprint > > > > ``` > > # /usr/bin/openssl x509 -fingerprint \ > > -in /etc/ssl/pkg/omniosce-ca.cert.pem -noout > > ``` > > > > `8D:CD:F9:D0:76:CD:AF:C1:62:AF:89:51:AF:8A:0E:35:24:4C:66:6D` > > > > > > 3. Change the publisher to our new repo > > > > ``` > > # /usr/bin/pkg set-publisher -P \ > > -G https://pkg.omniti.com/omnios/r151022/ \ > > -g https://pkg.omniosce.org/r151022/core/ omnios > > ``` > > > > 4. For each native zone (if you have any), run > > > > ``` > > # /usr/bin/pkg -R set-publisher -P \ > > -G https://pkg.omniti.com/omnios/r151022/ \ > > -g https://pkg.omniosce.org/r151022/core/ omnios > > ``` > > > > (get a list of all your zones by running `zoneadm list -cv` for the > ``, add `/root` to the PATH given in the list.) > > > > > > 5. Install the new ca-bundle containing our new CA > > > > ``` > > # /usr/bin/pkg update -rv web/ca-bundle > > ``` > > > > 6. Remove the CA file imported by hand > > > > ``` > > # rm /etc/ssl/pkg/omniosce-ca.cert.pem > > ``` >
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
This is very exciting. Thanks for the hard work to get things going. Gary On 7/12/2017 11:32 AM, Tobias Oetiker wrote: > # OmniOS Community Edition > > On April 21st 2017, OmniTI announced that they would suspend active > development of OmniOS and support contracts would not be renewed. > > While this announcement left many users stunned, others focused more on the > fact that OmniTI in their announcement also expressed the hope that "the > community" would take up further development of the OS. 14 weeks later, > OmniOS Community Edition is a reality. > > Andy Fiddaman (www.citrus-it.net), Tobias Oetiker (www.oetiker.ch) and > Dominik Hassler have spent some quality time setting up the systems and > procedures allowing us to take over maintenance and development of OmniOS. In > this endeavour we were supported by many. Special thanks to Stefan Husch > (www.qutic.com), Peter Tribble (www.petertribble.co.uk), Dan McDonald and > Theo Schlossnagle (www.circonus.com). > > We have forked the OmniOS repos and pulled in bugfixes and security fixes > that have been published since the release of OmniOS r151022. After setting > up our own package repository and updating the build infrastructure, we are > finally ready to go public. We are following the established OmniOS release > naming scheme by releasing > > > ## OmniOSce r151022h, 12th July 2017 > > The new release contains the following fixes: > > - expat updated to version 2.2.1 (fixes CVE-2017-9233) > - openssl updated to version 1.0.2l > - curl updated to version 7.54.1 > - bind updated to version 9.10.5-P3 > - p7zip updated to fix CVE-2016-9296 > - web/ca-bundle updated to include OmniOSce Certificate Authority certificate > > `uname -a` shows omnios-r151022-f9693432c2 (no change in this release) > > Our work does not stop here though. First we are committed to quickly > releasing updates for r151022 as the need arises. We are also working towards > releasing r151024 on schedule. To that end, we have already updated the > bloody environment with all the latest goodies from upstream illumos and > joyent-lx repositories. > > OmniOS community edition hosts its sources on https://github.com/omniosorg/ > and if you want to get in touch, you can find us on > https://gitter.im/omniosorg/Lobby > > > ## Release Schedule > > The intention is for new stable releases to continue to come out every 26 > weeks. Interim, "weekly" updates to stable follow a fixed schedule denoted by > letters, one per week. Weekly releases are made as needed, so there may not > be a release each week. The first release of a new stable version is > synonymous with weekly release "a", though the letter is not used. > > During the intervals between stable releases, Bloody moves forward rapidly, > picking up changes from upstream illumos-gate and illumos-joyent as well as > updating various userland packages. In general, upstream merges will be > performed on a Thursday/Friday each week and weekly releases will be > published on a Monday. > > Bloody releases will be published on an ad-hoc basis but may be as frequent > as every week. > > Security fixes are excluded from the schedule and handled with priority as > they occur. > > > ## How to Upgrade > > All OmniOS packages are signed and the pkg installer is configured to only > allow trusted sources for the core packages. In order to upgrade to the new > OmniOS community edition, you have to let your box know that the updates will > be coming from a new trusted source. This means you will have to import our > CA certificate into your system. > > 1. Get a copy of the new certificate > > ``` > # /usr/bin/wget -P /etc/ssl/pkg \ > https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem > ``` > > 2. Check the certificate fingerprint > > ``` > # /usr/bin/openssl x509 -fingerprint \ > -in /etc/ssl/pkg/omniosce-ca.cert.pem -noout > ``` > > `8D:CD:F9:D0:76:CD:AF:C1:62:AF:89:51:AF:8A:0E:35:24:4C:66:6D` > > > 3. Change the publisher to our new repo > > ``` > # /usr/bin/pkg set-publisher -P \ > -G https://pkg.omniti.com/omnios/r151022/ \ > -g https://pkg.omniosce.org/r151022/core/ omnios > ``` > > 4. For each native zone (if you have any), run > > ``` > # /usr/bin/pkg -R set-publisher -P \ > -G https://pkg.omniti.com/omnios/r151022/ \ > -g https://pkg.omniosce.org/r151022/core/ omnios > ``` > > (get a list of all your zones by running `zoneadm list -cv` for the > ``, add `/root` to the PATH given in the list.) > > > 5. Install the new ca-bundle containing our new CA > > ``` > # /usr/bin/pkg update -rv web/ca-bundle > ``` > > 6. Remove the CA file imported by hand > > ``` > # rm /etc/ssl/pkg/omniosce-ca.cert.pem > ``` > > 7. Finally update as usual > > ``` > # /usr/bin/pkg update -rv > ``` > > > ## About OmniOS Community Edition Association > > OmniOS Community Edition Association (OmniOSce) is a Swiss association, > dedicated to the continued support and release of OmniOS for the benefit of >
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
Thank you all for your efforts. Dan ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
Congratulations and thank you for your efforts!! On 12/07/2017 16:32, Tobias Oetiker wrote: > # OmniOS Community Edition > > On April 21st 2017, OmniTI announced that they would suspend active > development of OmniOS and support contracts would not be renewed. > > While this announcement left many users stunned, others focused more on the > fact that OmniTI in their announcement also expressed the hope that "the > community" would take up further development of the OS. 14 weeks later, > OmniOS Community Edition is a reality. > > Andy Fiddaman (www.citrus-it.net), Tobias Oetiker (www.oetiker.ch) and > Dominik Hassler have spent some quality time setting up the systems and > procedures allowing us to take over maintenance and development of OmniOS. In > this endeavour we were supported by many. Special thanks to Stefan Husch > (www.qutic.com), Peter Tribble (www.petertribble.co.uk), Dan McDonald and > Theo Schlossnagle (www.circonus.com). > > We have forked the OmniOS repos and pulled in bugfixes and security fixes > that have been published since the release of OmniOS r151022. After setting > up our own package repository and updating the build infrastructure, we are > finally ready to go public. We are following the established OmniOS release > naming scheme by releasing > > > ## OmniOSce r151022h, 12th July 2017 > > The new release contains the following fixes: > > - expat updated to version 2.2.1 (fixes CVE-2017-9233) > - openssl updated to version 1.0.2l > - curl updated to version 7.54.1 > - bind updated to version 9.10.5-P3 > - p7zip updated to fix CVE-2016-9296 > - web/ca-bundle updated to include OmniOSce Certificate Authority certificate > > `uname -a` shows omnios-r151022-f9693432c2 (no change in this release) > > Our work does not stop here though. First we are committed to quickly > releasing updates for r151022 as the need arises. We are also working towards > releasing r151024 on schedule. To that end, we have already updated the > bloody environment with all the latest goodies from upstream illumos and > joyent-lx repositories. > > OmniOS community edition hosts its sources on https://github.com/omniosorg/ > and if you want to get in touch, you can find us on > https://gitter.im/omniosorg/Lobby > > https://pkg.omniosce.org/r151022/core/ > ## Release Schedule > > The intention is for new stable releases to continue to come out every 26 > weeks. Interim, "weekly" updates to stable follow a fixed schedule denoted by > letters, one per week. Weekly releases are made as needed, so there may not > be a release each week. The first release of a new stable version is > synonymous with weekly release "a", though the letter is not used. > > During the intervals between stable releases, Bloody moves forward rapidly, > picking up changes from upstream illumos-gate and illumos-joyent as well as > updating various userland packages. In general, upstream merges will be > performed on a Thursday/Friday each week and weekly releases will be > published on a Monday. > > Bloody releases will be published on an ad-hoc basis but may be as frequent > as every week. > > Security fixes are excluded from the schedule and handled with priority as > they occur. > > > ## How to Upgrade > > All OmniOS packages are signed and the pkg installer is configured to only > allow trusted sources for the core packages. In order to upgrade to the new > OmniOS community edition, you have to let your box know that the updates will > be coming from a new trusted source. This means you will have to import our > CA certificate into your system. > > 1. Get a copy of the new certificate > > ``` > # /usr/bin/wget -P /etc/ssl/pkg \ > https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem > ``` > https://pkg.omniosce.org/r151022/core/ > 2. Check the certificate fingerprint > > ``` > # /usr/bin/openssl x509 -fingerprint \ > -in /etc/ssl/pkg/omniosce-ca.cert.pem -noout > ``` > > `8D:CD:F9:D0:76:CD:AF:C1:62:AF:89:51:AF:8A:0E:35:24:4C:66:6D` > > > 3. Change the publisher to our new repo > > ``` > # /usr/bin/pkg set-publisher -P \ >-G https://pkg.omniti.com/omnios/r151022/ \ >-g https://pkg.omniosce.org/r151022/core/ omnios > ``` > > 4. For each native zone (if you have any), run > https://pkg.omniosce.org/r151022/core/ > ``` > # /usr/bin/pkg -R set-publisher -P \ >-G https://pkg.omniti.com/omnios/r151022/ \ >-g https://pkg.omniosce.org/r151022/core/ omnios > ``` > > (get a list of all your zones by running `zoneadm list -cv` for the > ``, add `/root` to the PATH given in the list.) > > > 5. Install the new ca-bundle containing our new CA > > ``` > # /usr/bin/pkg update -rv web/ca-bundle > ``` > > 6. Remove the CA file imported by hand > > ``` > # rm /etc/ssl/pkg/omniosce-ca.cert.pem > ``` > > 7. Finally update as usual > > ```https://pkg.omniosce.org/r151022/core/ > # /usr/bin/pkg update -rv > ``` > > > ## Abou
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
Thanks for your work! I nearly lost hope for a ce edition. Gea @napp-it.org ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
Nice! On Jul 12, 2017 6:28 PM, "Volker A. Brandt" wrote: > Tobias Oetiker writes: > > We have forked the OmniOS repos and pulled in bugfixes and security fixes > > that have been published since the release of OmniOS r151022. After > setting > > up our own package repository and updating the build infrastructure, we > are > > finally ready to go public. We are following the established OmniOS > release > > naming scheme by releasing > > > > > > ## OmniOSce r151022h, 12th July 2017 > > Very nice work!! Well done guys. > > > Regards -- Volker > -- > > Volker A. Brandt Consulting and Support for Oracle Solaris > Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ > Am Wiesenpfad 6, 53340 Meckenheim, GERMANYEmail: v...@bb-c.de > Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 46 > Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt > > "When logic and proportion have fallen sloppy dead" > ___ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
Congratulations guys ! -Oorspronkelijk bericht- Van: Tobias Oetiker [mailto:t...@oetiker.ch] Verzonden: woensdag 12 juli 2017 17:32 Aan: omnios-discuss CC: SmartOs Discuss Onderwerp: [smartos-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h # OmniOS Community Edition On April 21st 2017, OmniTI announced that they would suspend active development of OmniOS and support contracts would not be renewed. While this announcement left many users stunned, others focused more on the fact that OmniTI in their announcement also expressed the hope that "the community" would take up further development of the OS. 14 weeks later, OmniOS Community Edition is a reality. Andy Fiddaman (www.citrus-it.net), Tobias Oetiker (www.oetiker.ch) and Dominik Hassler have spent some quality time setting up the systems and procedures allowing us to take over maintenance and development of OmniOS. In this endeavour we were supported by many. Special thanks to Stefan Husch (www.qutic.com), Peter Tribble (www.petertribble.co.uk), Dan McDonald and Theo Schlossnagle (www.circonus.com). We have forked the OmniOS repos and pulled in bugfixes and security fixes that have been published since the release of OmniOS r151022. After setting up our own package repository and updating the build infrastructure, we are finally ready to go public. We are following the established OmniOS release naming scheme by releasing ## OmniOSce r151022h, 12th July 2017 The new release contains the following fixes: - expat updated to version 2.2.1 (fixes CVE-2017-9233) - openssl updated to version 1.0.2l - curl updated to version 7.54.1 - bind updated to version 9.10.5-P3 - p7zip updated to fix CVE-2016-9296 - web/ca-bundle updated to include OmniOSce Certificate Authority certificate `uname -a` shows omnios-r151022-f9693432c2 (no change in this release) Our work does not stop here though. First we are committed to quickly releasing updates for r151022 as the need arises. We are also working towards releasing r151024 on schedule. To that end, we have already updated the bloody environment with all the latest goodies from upstream illumos and joyent-lx repositories. OmniOS community edition hosts its sources on https://github.com/omniosorg/ and if you want to get in touch, you can find us on https://gitter.im/omniosorg/Lobby ## Release Schedule The intention is for new stable releases to continue to come out every 26 weeks. Interim, "weekly" updates to stable follow a fixed schedule denoted by letters, one per week. Weekly releases are made as needed, so there may not be a release each week. The first release of a new stable version is synonymous with weekly release "a", though the letter is not used. During the intervals between stable releases, Bloody moves forward rapidly, picking up changes from upstream illumos-gate and illumos-joyent as well as updating various userland packages. In general, upstream merges will be performed on a Thursday/Friday each week and weekly releases will be published on a Monday. Bloody releases will be published on an ad-hoc basis but may be as frequent as every week. Security fixes are excluded from the schedule and handled with priority as they occur. ## How to Upgrade All OmniOS packages are signed and the pkg installer is configured to only allow trusted sources for the core packages. In order to upgrade to the new OmniOS community edition, you have to let your box know that the updates will be coming from a new trusted source. This means you will have to import our CA certificate into your system. 1. Get a copy of the new certificate ``` # /usr/bin/wget -P /etc/ssl/pkg \ https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem ``` 2. Check the certificate fingerprint ``` # /usr/bin/openssl x509 -fingerprint \ -in /etc/ssl/pkg/omniosce-ca.cert.pem -noout ``` `8D:CD:F9:D0:76:CD:AF:C1:62:AF:89:51:AF:8A:0E:35:24:4C:66:6D` 3. Change the publisher to our new repo ``` # /usr/bin/pkg set-publisher -P \ -G https://pkg.omniti.com/omnios/r151022/ \ -g https://pkg.omniosce.org/r151022/core/ omnios ``` 4. For each native zone (if you have any), run ``` # /usr/bin/pkg -R set-publisher -P \ -G https://pkg.omniti.com/omnios/r151022/ \ -g https://pkg.omniosce.org/r151022/core/ omnios ``` (get a list of all your zones by running `zoneadm list -cv` for the ``, add `/root` to the PATH given in the list.) 5. Install the new ca-bundle containing our new CA ``` # /usr/bin/pkg update -rv web/ca-bundle ``` 6. Remove the CA file imported by hand ``` # rm /etc/ssl/pkg/omniosce-ca.cert.pem ``` 7. Finally update as usual ``` # /usr/bin/pkg update -rv ``` ## About OmniOS Community Edition Association OmniOS Community Edition Association (OmniOSce) is a Swiss association, dedicated to the continued support and release of OmniOS for the benefit of all parties involved. The board of OmniOSce controls access
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
Tobias Oetiker writes: > We have forked the OmniOS repos and pulled in bugfixes and security fixes > that have been published since the release of OmniOS r151022. After setting > up our own package repository and updating the build infrastructure, we are > finally ready to go public. We are following the established OmniOS release > naming scheme by releasing > > > ## OmniOSce r151022h, 12th July 2017 Very nice work!! Well done guys. Regards -- Volker -- Volker A. Brandt Consulting and Support for Oracle Solaris Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim, GERMANYEmail: v...@bb-c.de Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 46 Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt "When logic and proportion have fallen sloppy dead" ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
On July 12, 2017 5:32:24 PM GMT+02:00, Tobias Oetiker wrote: ># OmniOS Community Edition > >On April 21st 2017, OmniTI announced that they would suspend active >development of OmniOS and support contracts would not be renewed. > >While this announcement left many users stunned, others focused more on >the fact that OmniTI in their announcement also expressed the hope that >"the community" would take up further development of the OS. 14 weeks >later, OmniOS Community Edition is a reality. > >Andy Fiddaman (www.citrus-it.net), Tobias Oetiker (www.oetiker.ch) and >Dominik Hassler have spent some quality time setting up the systems and >procedures allowing us to take over maintenance and development of >OmniOS. In this endeavour we were supported by many. Special thanks to >Stefan Husch (www.qutic.com), Peter Tribble (www.petertribble.co.uk), >Dan McDonald and Theo Schlossnagle (www.circonus.com). > >We have forked the OmniOS repos and pulled in bugfixes and security >fixes that have been published since the release of OmniOS r151022. >After setting up our own package repository and updating the build >infrastructure, we are finally ready to go public. We are following the >established OmniOS release naming scheme by releasing > > >## OmniOSce r151022h, 12th July 2017 > >The new release contains the following fixes: > >- expat updated to version 2.2.1 (fixes CVE-2017-9233) >- openssl updated to version 1.0.2l >- curl updated to version 7.54.1 >- bind updated to version 9.10.5-P3 >- p7zip updated to fix CVE-2016-9296 >- web/ca-bundle updated to include OmniOSce Certificate Authority >certificate > >`uname -a` shows omnios-r151022-f9693432c2 (no change in this release) > >Our work does not stop here though. First we are committed to quickly >releasing updates for r151022 as the need arises. We are also working >towards releasing r151024 on schedule. To that end, we have already >updated the bloody environment with all the latest goodies from >upstream illumos and joyent-lx repositories. > >OmniOS community edition hosts its sources on >https://github.com/omniosorg/ and if you want to get in touch, you can >find us on https://gitter.im/omniosorg/Lobby > > >## Release Schedule > >The intention is for new stable releases to continue to come out every >26 weeks. Interim, "weekly" updates to stable follow a fixed schedule >denoted by letters, one per week. Weekly releases are made as needed, >so there may not be a release each week. The first release of a new >stable version is synonymous with weekly release "a", though the letter >is not used. > >During the intervals between stable releases, Bloody moves forward >rapidly, picking up changes from upstream illumos-gate and >illumos-joyent as well as updating various userland packages. In >general, upstream merges will be performed on a Thursday/Friday each >week and weekly releases will be published on a Monday. > >Bloody releases will be published on an ad-hoc basis but may be as >frequent as every week. > >Security fixes are excluded from the schedule and handled with priority >as they occur. > > >## How to Upgrade > >All OmniOS packages are signed and the pkg installer is configured to >only allow trusted sources for the core packages. In order to upgrade >to the new OmniOS community edition, you have to let your box know that >the updates will be coming from a new trusted source. This means you >will have to import our CA certificate into your system. > >1. Get a copy of the new certificate > >``` ># /usr/bin/wget -P /etc/ssl/pkg \ >https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem >``` > >2. Check the certificate fingerprint > >``` ># /usr/bin/openssl x509 -fingerprint \ >-in /etc/ssl/pkg/omniosce-ca.cert.pem -noout >``` > >`8D:CD:F9:D0:76:CD:AF:C1:62:AF:89:51:AF:8A:0E:35:24:4C:66:6D` > > >3. Change the publisher to our new repo > >``` ># /usr/bin/pkg set-publisher -P \ > -G https://pkg.omniti.com/omnios/r151022/ \ > -g https://pkg.omniosce.org/r151022/core/ omnios >``` > >4. For each native zone (if you have any), run > >``` ># /usr/bin/pkg -R set-publisher -P \ > -G https://pkg.omniti.com/omnios/r151022/ \ > -g https://pkg.omniosce.org/r151022/core/ omnios >``` > >(get a list of all your zones by running `zoneadm list -cv` for the >``, add `/root` to the PATH given in the list.) > > >5. Install the new ca-bundle containing our new CA > >``` ># /usr/bin/pkg update -rv web/ca-bundle >``` > >6. Remove the CA file imported by hand > >``` ># rm /etc/ssl/pkg/omniosce-ca.cert.pem >``` > >7. Finally update as usual > >``` ># /usr/bin/pkg update -rv >``` > > >## About OmniOS Community Edition Association > >OmniOS Community Edition Association (OmniOSce) is a Swiss association, >dedicated to the continued support and release of OmniOS for the >benefit of all parties involved. The board of OmniOSce controls access >to the OmniOS CA. Current board members are: Tobias Oetiker >(President), Andy Fiddaman (Develop
Re: [OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
On Wed, 12 Jul 2017 17:32:24 +0200 (CEST) Tobias Oetiker wrote: > ``` > # /usr/bin/pkg update -rv > ``` > Maybe the update message should be changed? --- NOTE: Please review release notes posted at: http://omnios.omniti.com/ReleaseNotes --- -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -- /usr/games/fortune -es says: Alaska: A prelude to "No." pgp9Gyu7Wa64X.pgp Description: OpenPGP digital signature ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h
# OmniOS Community Edition On April 21st 2017, OmniTI announced that they would suspend active development of OmniOS and support contracts would not be renewed. While this announcement left many users stunned, others focused more on the fact that OmniTI in their announcement also expressed the hope that "the community" would take up further development of the OS. 14 weeks later, OmniOS Community Edition is a reality. Andy Fiddaman (www.citrus-it.net), Tobias Oetiker (www.oetiker.ch) and Dominik Hassler have spent some quality time setting up the systems and procedures allowing us to take over maintenance and development of OmniOS. In this endeavour we were supported by many. Special thanks to Stefan Husch (www.qutic.com), Peter Tribble (www.petertribble.co.uk), Dan McDonald and Theo Schlossnagle (www.circonus.com). We have forked the OmniOS repos and pulled in bugfixes and security fixes that have been published since the release of OmniOS r151022. After setting up our own package repository and updating the build infrastructure, we are finally ready to go public. We are following the established OmniOS release naming scheme by releasing ## OmniOSce r151022h, 12th July 2017 The new release contains the following fixes: - expat updated to version 2.2.1 (fixes CVE-2017-9233) - openssl updated to version 1.0.2l - curl updated to version 7.54.1 - bind updated to version 9.10.5-P3 - p7zip updated to fix CVE-2016-9296 - web/ca-bundle updated to include OmniOSce Certificate Authority certificate `uname -a` shows omnios-r151022-f9693432c2 (no change in this release) Our work does not stop here though. First we are committed to quickly releasing updates for r151022 as the need arises. We are also working towards releasing r151024 on schedule. To that end, we have already updated the bloody environment with all the latest goodies from upstream illumos and joyent-lx repositories. OmniOS community edition hosts its sources on https://github.com/omniosorg/ and if you want to get in touch, you can find us on https://gitter.im/omniosorg/Lobby ## Release Schedule The intention is for new stable releases to continue to come out every 26 weeks. Interim, "weekly" updates to stable follow a fixed schedule denoted by letters, one per week. Weekly releases are made as needed, so there may not be a release each week. The first release of a new stable version is synonymous with weekly release "a", though the letter is not used. During the intervals between stable releases, Bloody moves forward rapidly, picking up changes from upstream illumos-gate and illumos-joyent as well as updating various userland packages. In general, upstream merges will be performed on a Thursday/Friday each week and weekly releases will be published on a Monday. Bloody releases will be published on an ad-hoc basis but may be as frequent as every week. Security fixes are excluded from the schedule and handled with priority as they occur. ## How to Upgrade All OmniOS packages are signed and the pkg installer is configured to only allow trusted sources for the core packages. In order to upgrade to the new OmniOS community edition, you have to let your box know that the updates will be coming from a new trusted source. This means you will have to import our CA certificate into your system. 1. Get a copy of the new certificate ``` # /usr/bin/wget -P /etc/ssl/pkg \ https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem ``` 2. Check the certificate fingerprint ``` # /usr/bin/openssl x509 -fingerprint \ -in /etc/ssl/pkg/omniosce-ca.cert.pem -noout ``` `8D:CD:F9:D0:76:CD:AF:C1:62:AF:89:51:AF:8A:0E:35:24:4C:66:6D` 3. Change the publisher to our new repo ``` # /usr/bin/pkg set-publisher -P \ -G https://pkg.omniti.com/omnios/r151022/ \ -g https://pkg.omniosce.org/r151022/core/ omnios ``` 4. For each native zone (if you have any), run ``` # /usr/bin/pkg -R set-publisher -P \ -G https://pkg.omniti.com/omnios/r151022/ \ -g https://pkg.omniosce.org/r151022/core/ omnios ``` (get a list of all your zones by running `zoneadm list -cv` for the ``, add `/root` to the PATH given in the list.) 5. Install the new ca-bundle containing our new CA ``` # /usr/bin/pkg update -rv web/ca-bundle ``` 6. Remove the CA file imported by hand ``` # rm /etc/ssl/pkg/omniosce-ca.cert.pem ``` 7. Finally update as usual ``` # /usr/bin/pkg update -rv ``` ## About OmniOS Community Edition Association OmniOS Community Edition Association (OmniOSce) is a Swiss association, dedicated to the continued support and release of OmniOS for the benefit of all parties involved. The board of OmniOSce controls access to the OmniOS CA. Current board members are: Tobias Oetiker (President), Andy Fiddaman (Development), Dominik Hassler (Treasurer). ## About Citrus-IT Citrus IT is a UK company that provides a managed email service platform to companies around the world. F
