Language Selection

English French German Italian Portuguese Spanish

BSD

FreeBSD 12 Runs Refreshingly Easy On AMD Ryzen 9 3900X - Benchmarks Against Ubuntu 18.04 LTS

Filed under
Graphics/Benchmarks
BSD
Ubuntu

While newer Linux distributions have run into problems on the new AMD Zen 2 desktop CPUs (fixed by a systemd patch or fundamentally by a BIOS update) and DragonFlyBSD needed a separate boot fix, FreeBSD 12.0 installed out-of-the-box fine on the AMD Ryzen 9 3900X test system with ASUS ROG CROSSHAIR VIII HERO WiFi motherboard.

[...]

I also attempted to try DragonFlyBSD with its latest daily ISO/IMG following the Zen 2 fix this week by Matthew Dillon. Unfortunately, even with the latest daily ISO I ran into a panic at boot time. So as a result, today are just some FreeBSD 12.0 vs. Ubuntu 18.04 benchmarks for reference. Matthew Dillon did have some interesting comments in our forums about his (great) experiences with these new CPUs, some limitations, and about the original DragonFlyBSD issue.

Read more

Project Trident 19.07 Available

Filed under
BSD

This is a packages update with some important bugfixes from upstream TrueOS.

Read more

BSD News: BSDCan and DragonFlyBSD

Filed under
BSD
    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
BSD
  • 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 https://www.FreeBSD.org/releases/ 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
Security
BSD

opnsense

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
BSD

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
BSD

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
BSD

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
BSD
  • 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
BSD
  • 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
    system.
    
    Installer images and memory stick images are available here:
    
        https://download.freebsd.org/ftp/releases/ISO-IMAGES/11.3/
    
    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:
    
        https://www.freebsd.org/releases/11.3R/relnotes.html
    
    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):
    
        https://download.freebsd.org/ftp/releases/VM-IMAGES/11.3-RC3/
    
    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:
    
        https://wiki.freebsd.org/arm64/QEMU
    
    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
    continuing.
    
    	# 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.

Syndicate content

More in Tux Machines

today's leftovers

  • Linux Weekly Roundup #35

    Hello and welcome to this week's Linux Roundup and what a wonderful week we had! We have plenty of Linux Distro releases and LibreOffice 6.3 RC1. The Linux distros with releases this week are Q4OS 3.8, SparkyLinux 5.8, Mageia 7.1, ArcoLinux 19.07.11, Deepin 15.11, ArchBang 2107-beta, Bluestar 5.2.1, Slackel 7.2 "Openbox" and Endeavour OS 2019.07.15. I looked at most of these Linux Distros, links below, I will look at some of them in the new week and some I will unfortunately not have a look at, for download links and more, please visit distrowatch.com Well, this is this week's Linux Roundup, thank you so much for your time! Have a great week!

  • Full Circle Magazine: Full Circle Weekly News #140
  • Christopher Allan Webber: ActivityPub Conf 2019

    That's right! We're hosting the first ever ActivityPub Conf. It's immediately following Rebooting Web of Trust in Prague. There's no admission fee to attend. (Relatedly, the conference is kind of being done on the cheap, because it is being funded by organizers who are themselves barely funded.) The venue, however, is quite cool: it's at the DOX Centre for Contemporary Art, which is itself exploring the ways the digital world is affecting our lives. If you plan on attending (and maybe also speaking), you should get in your application soon (see the flier for details). We've never done one of these, and we have no idea what the response will be like, so this is going to be a smaller gathering (about 40 people). In some ways, it will be somewhere between a conference and a gathering of people-who-are-interested-in-activitypub. As said in the flier, by attending, you are agreeing to the code of conduct, so be sure to read that.

Sysadmin Appreciation Day, IBM and Fedora

  • Gift ideas for Sysadmin Appreciation Day

    Sysadmin Appreciation Day is coming up this Friday, July 26. To help honor sysadmins everywhere, we want you to share your best gift ideas. What would be the best way a team member or customer could show their appreciation for you? As a sysadmin, what was the best gift you've ever received? We asked our writers the same question, and here are their answers: "Whilst working in the Ubuntu community on Edubuntu, I took it upon myself to develop the startup/shutdown sound scheme, which became the default in Ubuntu for, from what I can understand, the next decade. Whilst people had a love-hate relationship with my sound scheme, and rightly so, I had a love-hate relationship with my sound card during the development. At the time I had recorded all my sound samples using one sample rate, but my new sound card, as my motherboard had exploded a few days earlier, did not support it. I had two choices, resample all my samples (which I didn't really want to do) or buy a new sound card.

  • Red Hat OpenStack Platform with Red Hat Ceph Storage: Radosbench baseline performance evaluation

    Red Hat Ceph Storage is popular storage for Red Hat OpenStack Platform. Customers around the world run their hyperscale, production workloads on Red Hat Ceph Storage and Red Hat OpenStack Platform. This is driven by the high level of integration between Ceph storage and OpenStack private cloud platforms. With each release of both platforms, the level of integration has grown and performance and automation has increased. As the customer's storage and compute needs for footprints have grown, we have seen more interest towards running compute and storage as one unit and providing a hyperconverged infrastructure (HCI) layer based on OpenStack and Ceph. [...] Continuing the benchmarking series, in the next post you’ll learn performance insights of running multi-instance MySQL database on Red Hat OpenStack Platform and Red Hat Ceph Storage across decoupled and hyperconverged architectures. We’ll also compare results from a near-equal environment backed by all-flash cluster nodes.

  • The State of Java in Flathub

    For maintainers of Java-based applications in Flathub, it's worth noting that even if you consume the Latest OpenJDK extension in your application, users will not be broken by major updates because OpenJDK is bundled into your Flatpak. The implication of this for users is that they won't see updates to their Java version until the application maintainer rebuilds the application in Flathub. If you maintain a Java-based Flatpak application on Flathub, you can consume the latest version of your chosen OpenJDK stream (either LTS or Latest) simply by rebuilding; the latest version of that OpenJDK steam will be pulled in automatically.

  • Fedora Magazine: Contribute at the Fedora Test Week for kernel 5.2

    The kernel team is working on final integration for kernel 5.1. This version was just recently released, and will arrive soon in Fedora. This version has many security fixes included. As a result, the Fedora kernel and QA teams have organized a test week from Monday, Jul 22, 2019 through Monday, Jul 29, 2019. Refer to the wiki page for links to the test images you’ll need to participate. Read below for details.

Debian and Ubuntu Leftovers

  • Bootstrappable Debian BoF

    Greetings from DebConf 19 in Curitiba! Just a quick reminder that I will run a Bootstrappable Debian BoF on Tuesday 23rd, at 13.30 Brasilia time (which is 16.30 UTC, if I am not mistaken). If you are curious about bootstrappability in Debian, why do we want it and where we are right now, you are welcome to come in person if you are at DebCon or to follow the streaming.

  • Candy Tsai: Outreachy Week 6 – Week 7: Getting Code Merge

    You can’t overhear what others are doing or learn something about your colleagues through gossip over lunch break when working remotely. So after being stuck for quite a bit, terceiro suggested that we try pair programming. After our first remote pair programming session, I think there should be no difference in pair programming in person. We shared the same terminal, looked at the same code and discussed just like people standing side by side. Through our pair programming session, I found out that I had a bad habit. I didn’t run tests on my code that often, so when I had failing tests that didn’t fail before, I spent more time debugging than I should have. Pair programming gave insight to how others work and I think little improvements go a long way.

  • about your wiki page on I/O schedulers and BFQ
    Hi,
    this is basically to report outdated statements in your wiki page on
    I/O schedulers [1].
    
    The main problematic statement is that BFQ "...  is not ideal for
    devices with slow CPUs or high throughput I/O devices" because too
    heavy.  BFQ is definitely more sophisticated than any of the other I/O
    schedulers.  We have designed it that way to provide an incomparably
    better service quality, at a very low overhead.  As reported in [2],
    the execution time of BFQ on an old laptop CPU is 0.6 us per I/O
    event, against 0.2 us for mq-deadline (which is the lightest Linux I/O
    scheduler).
    
    To put these figures into context, BFQ proved to be so good for
    "devices with slow CPUs" that, e.g., Chromium OS migrated to BFQ a few
    months ago.  In particular, Google crew got convinced by a demo [3] I
    made for them, on one of the cheapest and slowest Chromebook on the
    market.  In the demo, a fast download is performed.  Without BFQ, the
    download makes the device completely unresponsive.  With BFQ, the
    device remains as responsive as if it was totally idle.
    
    As for the other part of the statement, "...  not ideal for ...  high
    throughput I/O devices", a few days ago I ran benchmarks (on Ubuntu)
    also with one of the fastest consumer-grade NVMe SSDs: a Samsung SSD
    970 PRO.  Results [4] can be summarized as follows.  Throughput with
    BFQ is about the same as with the other I/O schedulers (it couldn't be
    higher, because this kind of drives just wants the scheduler to stay
    as aside as possible, when it comes to throughput).  But, in the
    presence of writes as background workload, start-up times with BFQ are
    at least 16 times as low as with the other I/O schedulers.  In
    absolute terms, gnome-terminal starts in ~1.8 seconds with BFQ, while
    it takes at least 28.7 (!) seconds with the other I/O schedulers.
    Finally, only with BFQ, no frame gets lost in video-playing
    benchmarks.
    
    BFQ then provides other important benefits, such as from 5x to 10X
    throughput boost in multi-client server workloads [5].
    
    So, is there any chance that the outdated/wrong information on your
    wiki page [1] gets updated somehow?  If I may, I'd be glad to update
    it myself, after providing you with all the results you may ask.
    
    In addition, why doesn't Ubuntu too consider switching to BFQ as
    default I/O scheduler, for all drives that BFQ supports (namely all
    drives with a maximum speed not above ~500 KIOPS)?
    
    Looking forward to your feedback,
    Paolo
    
    
  • Should Ubuntu Use The BFQ I/O Scheduler?

    The BFQ I/O scheduler is working out fairly well these days as shown in our benchmarks. The Budget Fair Queueing scheduler supports both throughput and low-latency modes while working particularly well for consumer-grade hardware. Should the Ubuntu desktop be using BFQ by default? [...] But in addition to wanting to correct that Wiki information, Paolo pops the question of why doesn't Ubuntu switch to BFQ as the default I/O scheduler for supported drives. Though as of yet, no Ubuntu kernel developers have yet commented on the prospect of switching to BFQ.

Devices With Linux Support

  • Quest Releases KACE SDA & SMA Updates

    The update to 7.0 for KACE Systems Deployment Appliance is primarily about bringing a scope of endpoint management capabilities with new support for Linux devices to the table.

  • Rugged, Kaby Lake transport computer has a 10-port LAN switch with PoE

    Axiomtek’s Linux-ready “tBOX400-510-FL” transportation system has a 7th Gen Intel CPU and a 10-port managed switch with 8x M12-style 10/100Mbps PoE and 2x GbE ports. The rugged system also has 3x mini-PCIe slots and dual swappable SATA drives. Axiomtek has launched a fanless, Kaby Lake-U based transportation computer with a choice of power supplies designed for in-vehicle, marine, or railway applications. The rugged tBOX400-510-FL features a Qualcomm-driven, Layer 2 managed PoE switch with support for IP surveillance and video management applications. “Customers can connect IP cameras directly without installing an extra PoE switch, minimizing overall deployment costs and installation space onboard,” stated Axiomtek product manager Sharon Huang.