BSD News 21/03/2016

Last week in BSD

Releases:SoloBSD, FreeBSD, HardenedBSD
Other news: BSDSec, PC-BSD, FreeBSD, HardenedBSD, FreeBSD Foundation, OpenBSD, DragonFly BSD, BSDnow,


BSDSec



Releases 

FreeBSD 10.3-RC3 Available

The third Release Candidate build for the FreeBSD 10.3 release cycle is now available. ISO images for the amd64, armv6, i386, ia64, powerpc, powerpc64 and sparc64 architectures are available on most of our FreeBSD mirror sites.


New stable release: HardenedBSD-stable 10-STABLE v42.2

HardenedBSD-10-STABLE-v42.2 - https://github.com/HardenedBSD/hardenedBSD-stable/releases/tag/HardenedB...


RELEASE: SoloBSD 10.3-PRERELEASE-v42.2

There is a new build of SoloBSD 10.3-PRERELEASE based on the latest HardenedBSD stable branch version 42.2
You can grab it from Here. (45.7 Mb)
root password: solobsd



News 

FreeBSD Not a Linux Distro

 In this session George Neville-Neil presents the history of FreeBSD.


Call For Artists: New Icon Theme

Source: Call For Artists: New Icon Theme
Since the founding of the Lumina desktop project, one of the most common questions I get asked is: “I am not a programmer, but how can I help out?” Well today I would like to open up a new method of contributing for those of you that are graphically-inclined: the creation of a brand new icon theme for the Lumina desktop!
This new icon theme will adhere to the FreeDesktop specifications[1] for registering an icon theme, and the good news is that I have already handled all the administrative setup/framework for you so that all you need to do to contribute is basically just send in icon files!
Here are the highlights for the new theme:
  1. Included within the main Lumina source repository
  2. All icons will be licensed under the Creative Commons Attribution 4.0 International Public License. This is comparable to the 3-clause BSD license, but specifically for static images/files (whereas the BSD license is for source code).
  3. This will be a high-contrast, high-resolution, fully-scalable (SVG) theme.
  4. The general concept is a white foreground, with a black outline/shadow around the icon, and colorized emblems/overlays for distinguishing between similar icons (“folder” vs “folder-network” for instance). We are going for a more professional/simple look to the icons since tiny image details generally do not scale as well across the range we are looking at.
The details on how to contribute an icon to the theme are listed on the repository page as well, but here is the summary:
  1. Icons which are still needed are listed in the TODO.txt files within each directory.
  2. Submit the icon file via git pull request
  3. Add an entry for your icon/submission to the AUTHORS file (to ensure each contributor gets proper credit for their work)
  4. Remove the icon from the appropriate TODO.txt file/list
If you are not familiar with git or how to send git pull requests, feel free to email me the icon file(s) you want to contribute and I can add them to the source tree for you (and update the AUTHORS/TODO files as necessary). Just be sure to include your full name/email so we can give you the proper credit for your work (if you care about that).

As an added bonus since we don’t have any actual icons yet (just the general guidelines), the first contributor to send in some icons will get to help decide the overall look-n-feel of the icon theme!

[1] FreeDesktop Specifications
  • Theme Registration: https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html
  • Icon Names: https://specifications.freedesktop.org/icon-naming-spec/latest/ar01s04.html

 

NetBSD: Happy 23rd Birthday, src!

And so it began...

revision 1.1
date: 1993-03-21 10:45:37 +0100; author: cgd; state: Exp;
branches: 1.1.1;

Initial revision

and we continue this legacy.
 

Introducing a New Website and Logo for the Foundation


The FreeBSD Foundation is pleased to announce the debut of our new logo and website, signaling the ongoing evolution of the Foundation identity, and ability to better serve the FreeBSD Project. Our new logo was designed to not only reflect the established and professional nature of our organization, but also to represent the link between the Project and the Foundation, and our commitment to community, collaboration, and the advancement of FreeBSD.

We did not make this decision lightly.  We are proud of the Beastie in the Business Suit and the history he encompasses. That is why you’ll still see him make an appearance on occasion. However, as the Foundation’s reach and objectives continue to expand, we must ensure our identity reflects who we are today, and where we are going in the future. From spotlighting companies who support and use FreeBSD, to making it easier to learn how to get involved, spread the word about, and work within the Project, the new site has been designed to better showcase, not only how we support the Project, but also the impact FreeBSD has on the world. The launch today marks the end of Phase I of our Website Development Project. Please stay tuned as we continue to add enhancements to the site.

We are also in the process of updating all our collateral, marketing literature, stationery, etc with the new logo. If you have used the FreeBSD Foundation logo in any of your marketing materials, please assist us in updating them. New Logo Guidelines will be available soon. In the meantime, if you are in the process of producing some new literature, and you would like to use the new Foundation logo, please contact our marketing department to get the new artwork.

Please note: we've moved the blog to the new site. See it here.




IPv6 errata for 5.7/5.8, pledge errata for 5.9

Errata patches were recently issued for an IPv6 bug that affects users of both OpenBSD 5.7 and 5.8, as well as a patch for pledge in the upcoming 5.9 release. Quoting the patch:
Insufficient checks in IPv6 socket binding and UDP IPv6 option processing allow a local user to send UDP packets with a source (IPv6 address + port) already reserved by another user.
Users that don't use IPv6 are not affected by this issue. Users who are using IPv6 should apply the patch, rebuild their kernel and reboot.
Though not officially released, unrelated an errata patch was issued for 5.9 on the same day:
Incorrect path processing in pledge_namei() could result in unexpected program termination of pledged programs.
Just as a heads up, you'll want to apply this one after installing 5.9 when it hits. Seasoned users know it's always good to check the errata page after doing an install.
Head over to the 5.7 errata or 5.8 errata pages to make sure you're all up to date.


AsiaBSDCon OpenBSD papers

This year's AsiaBSDCon has come to an end, with a number of OpenBSD-related talks being presented. Two developers were also invited to the smaller "bhyvecon" event to discuss vmm(4) and future plans.

  • Antoine Jacoutot ([email protected]) - OpenBSD rc.d(8) (slides | paper)
  • Henning Brauer ([email protected]) - Running an ISP on OpenBSD (slides)
  • Mike Belopuhov ([email protected]) - Implementation of Xen PVHVM drivers in OpenBSD (slides | paper)
  • Mike Belopuhov ([email protected]) - OpenBSD project status update (slides)
  • Mike Larkin ([email protected]) - OpenBSD vmm Update (slides)
  • Reyk Floeter ([email protected]) - OpenBSD vmd Update (slides) Videos will likely be uploaded later on. And finally, you can usually find most of the OpenBSD-related presentations at openbsd.org/papers. Future conferences can also be seen at openbsd.org/events.html.

  • Multiple card slots accessible in DragonFly

    If you somehow have a device with multiple SD/MMC card slots, you can now access all of them under DragonFly.  (Apparently done to make a tablet run DragonFly better, going by IRC conversation)

    The Tokyo Debrief | BSD Now 133

    This week on BSDNow, Allan and I are back from AsiaBSDCon & we have an interview with Brad Davis about the new “Packaging Base” call-for-testing. We’ll be sharing our thoughts and stories on how the week went, along with updating you on the latest news.

    World rebuild needed for DragonFly 4.5

    DragonFly BSD Digest by Justin Sherrill
    If you are running bleeding-edge DragonFly, Sepherosa Ziehau has made some networking changes that both reduce CPU usage in high-traffic situations and change some underlying network structures.  This means a full buildworld is needed on your next update.
    If you’re using DragonFly 4.4.x or older, you are unaffected.

    Code stuff


    Interesting articles


    SHARE

    Jan Hovancik

    software developer - guitar player - poetry lover