Language Selection

English French German Italian Portuguese Spanish

FreeBSD 12.0 Faces A Minor Setback But Still Should Be Out Ahead Of Christmas

Filed under
BSD

The big FreeBSD 12.0 release still is expected to happen in December but will be a bit later than originally planned.

The FreeBSD release engineering team has decided that a fourth beta is warranted before branching the FreeBSD 12 code and moving onto the release candidate phase. There already has been a number of alpha releases and three betas, but due to a boot time issue and allowing more time for ARM/ARM64 builds to complete, a fourth beta has been penciled into the schedule.

Read more

Also: malloc.conf replaced with a sysctl

More in Tux Machines

Fedora 29 release retrospective

Some of the Fedora Spins and Labs were not included in the compose that was declared gold. With a few notable exceptions, Spins intentionally do not block releases. However, from a user-friendliness standpoint, it is nice to have all of the Spins available. Some of the missing Spins failed to build due to broken packages, while others (e.g. the ppc64le Cloud image) happened to have a transient failure during the compose that eventually shipped. We identified two separate avenues to address this issue. The first is raising the visibility of failed Spin builds prior to the release so that Spin maintainers have time to address this issue. František Zatloukal suggested having a member of the Spins SIG track Release Engineering Pague issues to that they will see build failures and can notify the appropriate Spin owner(s). However, the Spins SIG may not be active enough to support this. The second is decoupling Spins from the main release process such that they can be published in a more-self service manner. This may take the form of Spin maintainers marking their spin “Go” or of providing a self-service build and publishing system for non-blocking deliverables. In subsequent discussion with Release Engineering, we determined that the Fedora Program Manager will send a list of failing Spins and Labs to owners at the Freeze points for Fedora 30. Work to provide an automated notification system based on Pungi notifications will be considered for Fedora 31 and beyond. Similarly, Release Engineering is already planning how a self-service platform might be developed for Fedora 31. Read more

Getting started with software-defined networking

Software-defined networking (SDN) is a dynamic, manageable, cost-effective, and adaptable networking technology suitable for the high-bandwidth, dynamic nature of today’s applications. By using an SDN architecture, an IT operations team can control network traffic in complex networking topologies through a centralized panel, rather than handling each network device, such as routers and switches, manually. Rapidly growing mobile content, server virtualization, and hybrid cloud services are some of the trends leading the networking industry to reconsider network architectures. The traditional networking architecture is built mainly on multiple layers of network switches in a hierarchical topology. But it’s harder to address rapidly increasing application workloads from multiple and hybrid infrastructures (like the cloud) in a hierarchical architecture. Read more

today's howtos

Sailfish 3 Day Celebration

The third generation of Sailfish OS is here, and we call it Sailfish 3! After months of hard work to get Sailfish 3 out in the wild, we have now released this rather big update to Sailfish powered devices. With that said, we surely wanted to celebrate the occasion and arranged two events: one in Helsinki, and another one in Berlin. Thanks to all of you who attended! Below a short description what happened, and what the mood was like. Read more Also: Smaller Raspberry Pi 3 Model A+ Announced with 5GHz Wi-Fi and 1.4GHz CPU for $25