Last week in BSD
Releases: noneOther news:BSDSec, NetBSD, FreeBSD, BSDnow, OpenBSD, PC-BSD, Hammer2, OPNsense,
BSDSec
News
Virginia BSD Assembly | BSD Now 105
It's already our two-year anniversary! This time on the show,
we'll be chatting with Scott Courtney, vice president of infrastructure
engineering at Verisign, about this year's vBSDCon. What's it have to
offer in that’s different in the BSD conference space? We'll find out.
Coming Soon to OpenBSD/amd64: A Native Hypervisor
Earlier today, Mike Larkin (mlarkin@)
published
a teaser for something he's been working on for a while. Then a little later in the day, an announcement appeared on tech@:
The song is available in mp3 and ogg formats, with lyrics mainly about the LibreSSL story (remember this?), but as the song notes point out,
Read more...
In July we cleaned up the repository so it can be converted easily; since then we've been working on the infrastructure and details of the conversion. The main tasks are now finished. We have set up a server for it which hosts a preliminary git conversion (on wip.pkgsrc.org) of the CVS repository, created a mailing list for the commit messages, pkgsrc-wip-changes, and prepared a list of authors for the conversion.
We've also provided a conversion of pkgsrc-wip based on data from July so that it can be tested on (nearly) live data. If you are interested in beta-testing the setup, send a suggestion for a username and an SSH public key to me. Details on how to test are on the NetBSD wiki but will probably change some more over time.
We still need help for the conversion: if you are or were a wip contributor, please let me know by September 15 what name and email to use for the conversion from CVS to git. This conversion will not be done again, so after that date, the commit data will be final.
TL;DR - a native hypervisor is coming. stay tuned.Read more...
For the last few months, I've been working on a hypervisor for OpenBSD. The idea for this started a few years ago, and after playing around with it from time to time, things really started to take shape around the time of the Brisbane hackathon earlier this year. As development accelerated, the OpenBSD Foundation generously offered to fund the project so that I could focus on it in more earnest.
OpenBSD 5.8's third song announced
he third of the expected four OpenBSD 5.8 release songs, A Year in the Life, has been released.The song is available in mp3 and ogg formats, with lyrics mainly about the LibreSSL story (remember this?), but as the song notes point out,
The pattern of LibreSSL development is a pattern that has repeated itself many times in OpenBSD -- a decision is made by a few people to do something, followed by action, and letting the world share it if they like it (such as with OpenSSH).Bob Beck's full announcement reads:
Read more...
pkgsrc-wip migrating to NetBSD.org, git
If everything goes as planned, the pkgsrc-wip CVS repository will be converted to git and hosted on NetBSD.org by end of September.In July we cleaned up the repository so it can be converted easily; since then we've been working on the infrastructure and details of the conversion. The main tasks are now finished. We have set up a server for it which hosts a preliminary git conversion (on wip.pkgsrc.org) of the CVS repository, created a mailing list for the commit messages, pkgsrc-wip-changes, and prepared a list of authors for the conversion.
We've also provided a conversion of pkgsrc-wip based on data from July so that it can be tested on (nearly) live data. If you are interested in beta-testing the setup, send a suggestion for a username and an SSH public key to me. Details on how to test are on the NetBSD wiki but will probably change some more over time.
We still need help for the conversion: if you are or were a wip contributor, please let me know by September 15 what name and email to use for the conversion from CVS to git. This conversion will not be done again, so after that date, the commit data will be final.
New Release Schedule for PC-BSD
The PC-BSD team has always been dedicated to bringing you the
best graphical BSD desktop possible. We received some great feedback
after our last release cycle that made us rethink our release schedule.
In the past, we tracked FreeBSD major releases, and also added our own quarterly updates that tended to add in a good bit of code for new features and utilities. Going forward, PC-BSD releases will track FreeBSD releases only, such as 10.2 -> 11.0 -> 11.1. Once the code base is frozen for a major release, an update can be pushed out to EDGE users who wish to act as advanced users and beta testers for the updates. During that several week testing period, if something goes wrong we’ll count on EDGE users to help report issues so that we can
quickly get those bugs fixed during the code freeze. After the several week testing period, we can release the update for PRODUCTION users, once we are confident that the kinks are worked out and EDGE users are happy.
We’re also changing the way the EDGE and PRODUCTION branches work a little bit. EDGE packages will now only be built with the ‘stable’ branch of PC-BSD code, to avoid radical changes that could break functionality to the PC-BSD tool-chain. This also allows us to focus our QA and testing on the new 3rd party packages themselves.
However, all packages that are built on FreeBSD -CURRENT will include PC-BSD’s ‘master’ branch, and are considered bleeding edge. These images will continue to be rolled monthly and are only intended for advanced users or developers who can debug and otherwise help fix issues as they arise.
The PRODUCTION package branch will be switching to a monthly update schedule instead of quarterly. The PC-BSD tool-chain will also be based upon “stable”, which will not radically change between releases. We are hoping this change will balance between the need for stability and bringing in the latest packages / security updates to end users in a timely manner.
In the past, we tracked FreeBSD major releases, and also added our own quarterly updates that tended to add in a good bit of code for new features and utilities. Going forward, PC-BSD releases will track FreeBSD releases only, such as 10.2 -> 11.0 -> 11.1. Once the code base is frozen for a major release, an update can be pushed out to EDGE users who wish to act as advanced users and beta testers for the updates. During that several week testing period, if something goes wrong we’ll count on EDGE users to help report issues so that we can
quickly get those bugs fixed during the code freeze. After the several week testing period, we can release the update for PRODUCTION users, once we are confident that the kinks are worked out and EDGE users are happy.
We’re also changing the way the EDGE and PRODUCTION branches work a little bit. EDGE packages will now only be built with the ‘stable’ branch of PC-BSD code, to avoid radical changes that could break functionality to the PC-BSD tool-chain. This also allows us to focus our QA and testing on the new 3rd party packages themselves.
However, all packages that are built on FreeBSD -CURRENT will include PC-BSD’s ‘master’ branch, and are considered bleeding edge. These images will continue to be rolled monthly and are only intended for advanced users or developers who can debug and otherwise help fix issues as they arise.
The PRODUCTION package branch will be switching to a monthly update schedule instead of quarterly. The PC-BSD tool-chain will also be based upon “stable”, which will not radically change between releases. We are hoping this change will balance between the need for stability and bringing in the latest packages / security updates to end users in a timely manner.
Code stuff
Interesting articles
System Health – whats next?!Wallpaper of the week
from https://picasaweb.google.com/105984357030495096879/FreeBSDWallpaper#5337214990788962386
0 comments:
Post a Comment