Language Selection

English French German Italian Portuguese Spanish


BSD News: BSDCan and DragonFlyBSD

Filed under
    BSDCan 2019 Trip Report: Mark Johnston

    Thanks to the FreeBSD Foundation, I was able to make the trip from Toronto to Ottawa to attend BSDCan 2019 and the FreeBSD developer summit. Following the conference, I also made it to a small hackathon held at the University of Waterloo. I work from home, which can create a sense of isolation despite the ability to easily communicate with colleagues over the Internet; conferences are thus an important way to recharge my enthusiasm for working on FreeBSD. This year’s BSDCan was not a disappointment: I attended a number of interesting talks, collaborated on some designs for future projects, and helped review and debug some code.

  • DragonFlyBSD Gets Fix To Be Able To Boot AMD Zen 2 Processors

    Separate from the Linux boot issue affecting AMD Ryzen 3000 (Zen 2) processors that has been attributed to RdRand, DragonFlyBSD is the first BSD at least we've seen getting a separate fix to be able to boot these new AMD processors.

    DragonFlyBSD lead developer Matthew Dillon who has been mesmerized by the AMD Threadripper performance for the past year now has his hands on new Zen 2 hardware. But it turns out the current DragonFlyBSD releases can't boot with these processors due to a separate problem from what we've seen on the Linux side.

FreeBSD 11.3

Filed under
  • FreeBSD 11.3-RELEASE Announcement

    The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 11.3-RELEASE. This is the fourth release of the stable/11 branch.

  • FreeBSD 11.3-RELEASE Available

    FreeBSD 11.3-RELEASE is now available. Please be sure to check the Release Notes and Release Errata before installation for any late-breaking news and/or issues with 11.3. More information about FreeBSD releases can be found on the Release Information page.

  • FreeBSD 11.3-RELEASE Release Notes

    This document contains the release notes for FreeBSD 11.3-RELEASE. It describes recently added, changed, or deleted features of FreeBSD. It also provides some notes on upgrading from previous versions of FreeBSD.

    This distribution of FreeBSD 11.3-RELEASE is a release distribution. It can be found at or any of its mirrors. More information on obtaining this (or other) release distributions of FreeBSD can be found in the “Obtaining FreeBSD” appendix to the FreeBSD Handbook.

    All users are encouraged to consult the release errata before installing FreeBSD. The errata document is updated with “late-breaking” information discovered late in the release cycle or after the release. Typically, it contains information on known bugs, security advisories, and corrections to documentation. An up-to-date copy of the errata for FreeBSD 11.3-RELEASE can be found on the FreeBSD Web site.

    This document describes the most user-visible new or changed features in FreeBSD since 11.2-RELEASE. In general, changes described here are unique to the 11.3-STABLE branch unless specifically marked as MERGED features.

    Typical release note items document recent security advisories issued after 11.2-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, or contributed software upgrades. They may also list changes to major ports/packages or release engineering practices. Clearly the release notes cannot list every single change made to FreeBSD between releases; this document focuses primarily on security advisories, user-visible changes, and major architectural improvements.

  • FreeBSD 11.3 Officially Released With Random Improvements, Updated Components

    FreeBSD 11.3 brings a number of updated user-space applications, libxo support has been enabled for various applications, XZ 5.2.4 has been updated, a Lua loader has been merged, LLVM Clang 8.0 is now available along with other LLVM 8.0.0 components, various networking driver updates, a ZFS file-system fix, and other changes. And, yes, there is a random driver update for improving the performance during the expensive task of reseeding the pool.

OPNsense 19.7 RC1 released

Filed under


For four and a half years now, OPNsense is driving innovation through
modularising and hardening the open source firewall, with simple
and reliable firmware upgrades, multi-language support, HardenedBSD
security, fast adoption of upstream software updates as well as clear
and stable 2-Clause BSD licensing.

We thank all of you for helping test, shape and contribute to the project!
We know it would not be the same without you.

Download links, an installation guide[1] and the checksums for the images
can be found below as well.

Read more

Project Trident 19.06 is Released, which added a lot of changes from upstream FreeBSD and TrueOS

Filed under

Trident Project have announced the release of Project Trident 19.06 on July 28, 2019, which added a lot of changes from upstream FreeBSD and TrueOS.

Project Trident is a desktop-focused rolling release operating system based on TrueOS. It uses the Lumina desktop as well as a number of self-developed utilities to provide an easy-to-use system that both BSD beginners and advanced system administrators.

This release brings a lot of new packages and updated most of the existing packages to latest available version.

Not only package updates also, they made few of changes in the base package.

Read more

FreeBSD turns 26

Filed under

The FreeBSD operating system is continuing to make progress, 26 years after it got its name. Among the areas where work is being done is on improved support for RISC-V, FUSE filesystem updates, C runtime changes, and security improvements. FreeBSD Day is celebrated on June 19, in recognition of the date in 1993 when the name FreeBSD was coined for a fork of the 386BSD project. The first official release of FreeBSD did not occur until November 1, 1993, however.

Ahead of FreeBSD Day, the project released its quarterly report for the first quarter of 2019, outlining some of its ongoing efforts. In addition to the quarterly report, the executive director of the FreeBSD Foundation provided LWN with some insights into the state of the project and the foundation that supports it.

Read more

OpenBSD Is Now My Workstation

Filed under

Why OpenBSD? Simply because it is the best tool for the job for me for my new-to-me Lenovo Thinkpad T420. Additionally, I do care about security and non-bloat in my personal operating systems (business needs can have different priorities, to be clear).

I will try to detail what my reasons are for going with OpenBSD (instead of GNU/Linux, NetBSD, or FreeBSD of which I’m comfortable using without issue), challenges and frustrations I’ve encountered, and what my opinions are along the way.

Disclaimer: in this post, I’m speaking about what is my opinion, and I’m not trying to convince you to use OpenBSD or anything else. I don’t truly care, but wanted to share in case it could be useful to you. I do hope you give OpenBSD a shot as your workstation, especially if it has been a while.

Read more

BSD: NetBSD Google Summer of Code and How to Configure FreeNAS

Filed under
  • Porting Wine to amd64 on NetBSD, first evaluation report

    This report was written by Naveen Narayanan as part of Google Summer of Code 2019.

    I have been working on porting Wine to amd64 on NetBSD as a GSoC 2019 project. Wine is a compatibility layer which allows running Microsoft Windows applications on POSIX-complaint operating systems. This report provides an overview of the progress of the project during the first coding period.

  • NetBSD Is Seeing Better Wine Support Thanks To Google Summer of Code

    One of the interesting Google Summer of Code projects on the BSD front this year is porting Wine to run on AMD64 (x86_64) under NetBSD.

    NetBSD has been running Wine to some extent on i386 but this effort has been about getting a Wine 64-bit port running nicely with 32-bit Windows program compatibility.

  • DIY Open Source NAS: How to Configure FreeNAS

    Here are some of the more essential configuration options to get you going with FreeNAS.

BSD: FreeBSD 11.3 RC3 and NetBSD on Old Computers

Filed under
  • FreeBSD 11.3-RC3 Now Available
    The third RC build of the 11.3-RELEASE release cycle is now available.
    Installation images are available for:
    o 11.3-RC3 amd64 GENERIC
    o 11.3-RC3 i386 GENERIC
    o 11.3-RC3 powerpc GENERIC
    o 11.3-RC3 powerpc64 GENERIC64
    o 11.3-RC3 sparc64 GENERIC
    o 11.3-RC3 armv6 BANANAPI
    o 11.3-RC3 armv6 BEAGLEBONE
    o 11.3-RC3 armv6 CUBIEBOARD
    o 11.3-RC3 armv6 CUBIEBOARD2
    o 11.3-RC3 armv6 CUBOX-HUMMINGBOARD
    o 11.3-RC3 armv6 RPI-B
    o 11.3-RC3 armv6 RPI2
    o 11.3-RC3 armv6 PANDABOARD
    o 11.3-RC3 armv6 WANDBOARD
    o 11.3-RC3 aarch64 GENERIC
    Note regarding arm SD card images: For convenience for those without
    console access to the system, a freebsd user with a password of
    freebsd is available by default for ssh(1) access.  Additionally,
    the root user password is set to root.  It is strongly recommended
    to change the password for both users after gaining access to the
    Installer images and memory stick images are available here:
    The image checksums follow at the end of this e-mail.
    If you notice problems you can report them through the Bugzilla PR
    system or on the -stable mailing list.
    If you would like to use SVN to do a source based update of an existing
    system, use the "releng/11.3" branch.
    A summary of changes since 11.3-RC2 includes:
    o Regression fix in mountd(8) (PR 238725)
    o Regression fix in NAT64LSN.
    A list of changes since 11.2-RELEASE is available in the releng/11.3
    release notes:
    Please note, the release notes page is not yet complete, and will be
    updated on an ongoing basis as the 11.3-RELEASE cycle progresses.
    === Virtual Machine Disk Images ===
    VM disk images are available for the amd64, i386, and aarch64
    architectures.  Disk images may be downloaded from the following URL
    (or any of the FreeBSD download mirrors):
    The partition layout is:
        ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
        ~ 1 GB  - freebsd-swap GPT partition type (swapfs GPT label)
        ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)
    The disk images are available in QCOW2, VHD, VMDK, and raw disk image
    formats.  The image download size is approximately 135 MB and 165 MB
    respectively (amd64/i386), decompressing to a 21 GB sparse image.
    Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
    loader file is needed for qemu-system-aarch64 to be able to boot the
    virtual machine images.  See this page for more information:
    To boot the VM image, run:
        % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt  \
    	-bios QEMU_EFI.fd -serial telnet::4444,server -nographic \
    	-drive if=none,file=VMDISK,id=hd0 \
    	-device virtio-blk-device,drive=hd0 \
    	-device virtio-net-device,netdev=net0 \
    	-netdev user,id=net0
    Be sure to replace "VMDISK" with the path to the virtual machine image.
    === Amazon EC2 AMI Images ===
    FreeBSD/amd64 EC2 AMIs are available in the following regions:
      eu-north-1 region: ami-07d990eaeb497323d
      ap-south-1 region: ami-001b7b067fd8e781d
      eu-west-3 region: ami-01052697e06e3a45e
      eu-west-2 region: ami-0cfee448feeb2a851
      eu-west-1 region: ami-0ce7400d6a08a9862
      ap-northeast-2 region: ami-0b16c2014116bd358
      ap-northeast-1 region: ami-0818328d0efcec703
      sa-east-1 region: ami-077fc22d100770c52
      ca-central-1 region: ami-0c414f2c140fd13cb
      ap-southeast-1 region: ami-0f5fe631ff1d2578a
      ap-southeast-2 region: ami-06bf072735d282208
      eu-central-1 region: ami-0a1cbb609ac331456
      us-east-1 region: ami-05a73406ad7ece248
      us-east-2 region: ami-0a21294420f709f19
      us-west-1 region: ami-0bb877ce5c712ad4f
      us-west-2 region: ami-0a231251af9d35604
    === Vagrant Images ===
    FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
    be installed by running:
        % vagrant init freebsd/FreeBSD-11.3-RC3
        % vagrant up
    === Upgrading ===
    The freebsd-update(8) utility supports binary upgrades of amd64 and i386
    systems running earlier FreeBSD releases.  Systems running earlier
    FreeBSD releases can upgrade as follows:
    	# freebsd-update upgrade -r 11.3-RC3
    During this process, freebsd-update(8) may ask the user to help by
    merging some configuration files or by confirming that the automatically
    performed merging was done correctly.
    	# freebsd-update install
    The system must be rebooted with the newly installed kernel before
    	# shutdown -r now
    After rebooting, freebsd-update needs to be run again to install the new
    userland components:
    	# freebsd-update install
    It is recommended to rebuild and install all applications if possible,
    especially if upgrading from an earlier FreeBSD release, for example,
    FreeBSD 11.x.  Alternatively, the user can install misc/compat11x and
    other compatibility libraries, afterwards the system must be rebooted
    into the new userland:
    	# shutdown -r now
    Finally, after rebooting, freebsd-update needs to be run again to remove
    stale files:
    	# freebsd-update install
  • FreeBSD 11.3-RC3 Available

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

  • Cameron Kaiser: And now for something completely different: NetBSD on the last G4 Mac mini (and making the kernel power failure proof)

    I'm a big fan of NetBSD. I've run it since 2000 on a Mac IIci (of course it's still running it) and I ran it for several years on a Power Mac 7300 with a G3 card which was the second incarnation of the Floodgap gopher server. Today I also still run it on a MIPS-based Cobalt RaQ 2 and an HP Jornada 690. I think NetBSD is a better match for smaller or underpowered systems than current-day Linux, and is fairly easy to harden and keep secure even though none of these systems are exposed to the outside world.

Shows: Test and Code, Bad Voltage, Ubuntu Podcast, Choose Linux and BSD Now 304

Filed under
  • Test and Code: 79: Fixing misinformation about software testing

    Some information about software testing is just wrong.
    I'm not talking about opinions. I have lots of opinions and they differ from other peoples opinions. I'm talking about misinformation and old information that is no longer applicable.

    I've ran across a few lateley that I want to address.

  • 2×54: Well Baffled

    [00:27:50] This past weekend has seen a bit of dancing about whether Ubuntu will drop 32-bit libraries from the archive, ending up with a statement from Canonical about it saying they aren’t going to (and Valve have responded saying that they’ll continue to support Steam on Ubuntu, although that was after we recorded the show)

  • Bad Voltage Season 2 Episode 54 Has Been Released:
  • Ubuntu Podcast from the UK LoCo: S12E12 – Nemesis

    This week we’ve been at the Snapcraft Summit in Montreal, we bring you some command line love and go over all your feedback.

    It’s Season 12 Episode 12 of the Ubuntu Podcast! Alan Pope, Mark Johnson and Martin Wimpress are connected and speaking to your brain.

  • Regolith, Rosa, and Antsy Alien Attack | Choose Linux 12

    Two new hosts join Joe to talk about a nice i3 implementation and an amazing arcade game written in Bash.

    Plus a new segment called Distrohoppers, and a useful hidden feature of GNOME.

  • Prospering with Vulkan | BSD Now 304

    DragonflyBSD 5.6 is out, OpenBSD Vulkan Support, bad utmp implementations in glibc and FreeBSD, OpenSSH protects itself against Side Channel attacks, ZFS vs OpenZFS, and more.

Glen Barber: Statement regarding employment change and roles in the [FreeBSD] Project

Filed under

Dear FreeBSD community:

As I have a highly-visible role within the community, I want to share
some news.  I have decided the time has come to move on from my role
with the FreeBSD Foundation, this Friday being my last day.  I have
accepted a position within a prominent company that uses and produces
products based on FreeBSD.

My new employer has included provisions within my job description that
allow me to continue supporting the FreeBSD Project in my current
roles, including Release Engineering.

There are no planned immediate changes with how this pertains to my
roles within the Project and the various teams of which I am a member.

FreeBSD 11.3 and 12.1 will continue as previously scheduled, with no
impact as a result of this change.

I want to thank everyone at the FreeBSD Foundation for providing the
opportunity to serve the FreeBSD Project in my various roles, and their
support for my decision.

I look forward to continue supporting the FreeBSD Project in my various
roles moving forward.


Read more

Also: FreeBSD's Release Engineering Lead Departs The Foundation

Syndicate content

More in Tux Machines

Audiocasts/Shows: Linux in the Ham Shack and Linux Headlines

  • LHS Episode #302: The End of Kenwood

    Welcome to Episode 302 of Linux in the Ham Shack. In this short topic episode, the hosts discuss the potential end of Kenwood in the amateur radio market, emcom in Montucky, Storm Area 51, HF on satellites, a huge update for PulseAudio, the Linux 5.3 kernel and much more. Thank you for listening and have a fantastic week.

  • 09/19/2019 | Linux Headlines

    Fresh init system controversy at the Debian project, a more scalable Samba, and a big release for LLVM. Plus GitHub's latest security steps and a new version of OBS Studio.

Android Leftovers

When Diverse Network ASICs Meet A Unifying Operating System

And it has also been a decade since switch upstart Arista Networks launched its Extensible Operating System, or EOS, which is derived from Linux. [...] The cross-platform nature of ArcOS, coupled with its ability to run in any function on the network, could turn out to be the key differentiator. A lot of these other NOSes were point solutions that could only be deployed in certain parts of the network, and that just creates animosity with the incumbent vendors that dominate the rest of the networking stack. Given the mission-critical nature of networking in the modern datacenter, it costs a great deal to qualify a new network operating system, and it can take a lot of time. If ArcOS can run across more platforms, qualify faster, and do more jobs in the network, then, says Garg, it has a good chance of shaking up switching and routing. “That totally changes the business conversation and the TCO advantages that we can bring to a customer across the entirety of their network.” Read more

Server: Kubernetes/OpenShift, OpenStack, and Red Hat's Ansible

  • 9 steps to awesome with Kubernetes/OpenShift presented by Burr Sutter

    Burr Sutter gave a terrific talk in India in July, where he laid out the terms, systems and processes needed to setup Kubernetes for developers. This is an introductory presentation, which may be useful for your larger community of Kubernetes users once you’ve already setup User Provisioned Infrastructure (UPI) in Red Hat OpenShift for them, though it does go into the deeper details of actually running the a cluster. To follow along, Burr created an accompanying GitHub repository, so you too can learn how to setup an awesome Kubernetes cluster in just 9 steps.

  • Weaveworks Named a Top Kubernetes Contributor

    But anyone who knows the history of Weaveworks might not be too surprised by this. Weaveworks has been a major champion of Kubernetes since the very beginning. It might not be too much of a coincidence that Weaveworks was incorporated only a few weeks after Kubernetes was open sourced, five years ago. In addition to this, the very first elected chair of the CNCF’s Technical Oversight Committee, responsible for technical leadership to the Cloud Native Foundation was also headed up by our CEO, Alexis Richardson(@monadic) (soon to be replaced by the awesome Liz Rice (@lizrice) of Aqua Security).

  • Improving trust in the cloud with OpenStack and AMD SEV

    This post contains an exciting announcement, but first I need to provide some context! Ever heard that joke “the cloud is just someone else’s computer”? Of course it’s a gross over-simplification, but there’s more than a grain of truth in it. And that raises the question: if your applications are running in someone else’s data-centre, how can you trust that they’re not being snooped upon, or worse, invasively tampered with?

  • Red Hat OpenStack Platform 15 Enhances Infrastructure Security and Cloud-Native Integration Across the Open Hybrid Cloud

    Red Hat, Inc., the world's leading provider of open source solutions, today announced the general availability of Red Hat OpenStack Platform 15, the latest version of its highly scalable and agile cloud Infrastructure-as-a-Service (IaaS) solution. Based on the OpenStack community’s "Stein" release, Red Hat OpenStack Platform 15 adds performance and cloud security enhancements and expands the platform’s ecosystem of supported hardware, helping IT organizations to more quickly and more securely support demanding production workloads. Given the role of Linux as the foundation for hybrid cloud, customers can also benefit from a more secure, flexible and intelligent Linux operating system underpinning their private cloud deployments with Red Hat Enterprise Linux 8.

  • Red Hat Ansible Automation Accelerates Past Major Adoption Milestone, Now Manages More Than Four Million Customer Systems Worldwide

    Red Hat, Inc., the world's leading provider of open source solutions, today announced that more than four million customer systems worldwide are now automated by Red Hat Ansible Automation. Customers, including Energy Market Company, Microsoft, Reserve Bank of New Zealand and Surescripts all use Red Hat Ansible Automation to automate and orchestrate their IT operations, helping to expand automation across IT stacks. According to a blog post by Chris Gardner with Forrester Research, who was the author of The Forrester Wave™: Infrastructure Automation Platforms, Q3 2019, "Infrastructure automation isn’t just on-premises or the cloud. It’s at the edge and everywhere in between."1 Since its launch in 2013, Red Hat Ansible Automation has provided a single tool to help organizations automate across IT operations and development, including infrastructure, networks, cloud, security and beyond.