|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
OpenBSD 6.0
I was taking a look at the changes coming to 5.9, and there is a lot to look forward to. I was wondering if anyone has any insight as to what will be new for 6.0? Will this be a release with major upgrades coming?
|
|
|||
Will there be support for Skylake CPUs and chipsets?
USB 3.1 Gen 2? the one with over 10 G/s speed? Sata Express? |
|
|||
USB 3.1? Even Intel does not have this in theirs Platform Controller Hubs.
I think that USB 3.1 is not in particular interest among OpenBSD's developers. I think that generally high-performance use cases (I/O: USB 3.1, GPGPU such as OpenCL) for desktop/laptop PCs are not in particular interest among OpenBSD developers. |
|
||||
HOW TO SEE WHAT"S COMING BEFORE IT IS ANNOUNCED
For casual review, click on www.openbsd.org/plus.html from time to time. This is the OpenBSD -current Change Log. At this writing, it is empty, as developers have been putting finishing touches on the OpenBSD 5.9 Change Log at www.openbsd.org/plus59.html.
You can keep up with the actual changes themselves, too, by reading the CVS commit logs. There are several ways. The two most common:
|
|
|||
Quote:
Intel's Alpine-Ridge chipset is already in use by one of the world's largest manufacturer of motherboards. The chipset supports native USB 3.1 Gen 2. Quote:
I am hoping that there will be native support for Sata Express and PCIe NVMe in OpenBSD 6. "The future of technology is now." Last edited by betweendayandnight; 26th March 2016 at 04:48 PM. Reason: add details |
|
|||
Quote:
OpenBSD does not follow the model of X.Y(.Z), where X is a major upgrade, Y is a minor upgrade and Z is bugfixes. Every six months, OpenBSD simply adds 0.1 to the current version number. Is it confusing? Maybe. Is it going to change anytime soon? No. |
|
|||
Quote:
Quote:
|
|
|||
Changes in major and minor release numbers do not mean major and minor feature addition.
|
|
|||
In actual practice, I think @ibara's description more accurately reflects the distributed release. The convention described in the man page seems to be tailored to those updating their system via cvs.
Last edited by shep; 9th May 2016 at 09:11 PM. Reason: Clarity |
|
||||
Perhaps the man page could be improved for clarity. It describes "major" and "minor" release numbers, which led jjstorm to assume there may be a different development cycle for different components. But the Project uses a single development cycle, as described in the FAQ.
|
|
|