Language Selection

English French German Italian Portuguese Spanish

Login

Enter your Tux Machines username.
Enter the password that accompanies your username.

More in Tux Machines

Server: Ubuntu 19.10 Release Schedule, IBM LinuxONE III with Ubuntu and SUSE on Cloud Foundry Foundation and More LF

  • Ubuntu 19.10 Release Schedule and Expected Features

    This is a continually updated article to inform you about Ubuntu 19.10 release date, features and other important things associated with it. The development for Ubuntu 19.10 is nearing its end and it’s time to look at what new features and improvement this new release brings. Ubuntu 19.10 is an important release because it will set the course of development for Ubuntu 20.04 LTS (long term support). I have always felt that the LTS version release takes a lot of features from its predecessor. In other words, Ubuntu 19.10 will be a glimpse of the features you would be getting in Ubuntu 20.04.

  • Announcing the new IBM LinuxONE III with Ubuntu

    Enterprises today need the most secure, and flexible system to support their initiatives, and for that system to grow and evolve for tomorrow. The latest LinuxONE system was designed to support mission-critical initiatives and allow enterprises to be innovative as they design and scale their environment. LinuxONE III provides features for advanced data protection and privacy, enterprise resiliency and scalability, and cloud enablement and integration. Reliability and continuity are critical to the success of any business. With this release, they’ll benefit from up to 10:1 consolidation for key workloads, and up to 190 cores and 40TB of memory. And with 99.999%* availability and up to 7.4x better resilience, enterprises can confidently run and scale their business-critical workloads. The new LinuxONE III provides the highest levels of availability and scalability, so business-critical workloads run flawlessly, recover quickly, and grow seamlessly.

  • Project Quarks: Native Cloud Foundry for Kubernetes

    At the recent Cloud Foundry Summit EU in the Netherlands, Vlad Iovanov of SUSE gave a keynote demo of Project Quarks, the project that integrates Cloud Foundry and Kubernetes, by packaging the Cloud Foundry Application Runtime as containers instead of virtual machines. Vlad explains the current capabilities of Quarks, with a look at its future as a Kubernetes Operator. It’s a fairly technical topic, but Vlad uses creative diagrams and an understandable demo to show the power of Quarks. Cloud Foundry Foundation has posted all recorded talks from CF Summit EU on YouTube. Check them out if you want to learn more about what is happening in the Cloud Foundry world! I’ll be posting more SUSE Cloud Application Platform talks here over the coming days. Watch Vlad’s talk below...

  • Broad Deployment Of Cloud Foundry Almost Double In Just 2 Years

    As businesses embark on their digital transformation journey, developers are driving innovation across cloud native environments for building into the future. According to a recently released report by Cloud Foundry Foundation, 45 percent of user respondents describe their Cloud Foundry use as “broad” compared to 30 percent in 2018 and 24 percent in 2017. The report also revealed that 39 percent of developers are deploying applications in less than one day. What points out towards a healthy and growing community of developers is the fact that almost one in five respondents started using Cloud Foundry in just the last 12 months.

  • The Linux Foundation to Host Open Source Project for Drone Aviation Interoperability

    The Linux Foundation today announced it will host the InterUSS Platform Open Source Project to enable trusted, secure and scalable interoperability between UAS Service Suppliers (USSs) that advances safe, equitable and efficient drone operations. Initial contributors include both industry and regulatory organizations Wing, AirMap, Uber and the Swiss Federal Office of Civil Aviation (FOCA). Similar to the evolution of cities, our skies are becoming busier with traffic. In an effort to unleash innovation and ensure safety, aviation regulators around the world are implementing UAS Traffic Management (UTM, also referred to as U-Space) to support rapidly increasing and highly diverse drone operations. Under UTM, a set of USSs (also known as U-Space Service Providers orUSPs) assist drone operators to conduct safe and compliant operations. USSs can provide service in overlapping airspace and share data when required to support services such as a strategic deconfliction of flight plans and remote identification and industry is developing standards for this data sharing through organizations such as ASTM International. The InterUSS Project provides a forum for collaboration and development of standards-compliant, open source implementations that facilitate communication in the UTM/U-Space environment.

Security Leftovers

  • Security updates for Wednesday

    Security updates have been issued by CentOS (firefox and kernel), Debian (thunderbird), Fedora (curl), openSUSE (curl and python-Werkzeug), Oracle (kernel and thunderbird), Red Hat (rh-nginx114-nginx), SUSE (curl, ibus, MozillaFirefox, firefox-glib2, firefox-gtk3, openldap2, openssl, openssl1, python-urllib3, and util-linux and shadow), and Ubuntu (linux, linux-aws, linux-azure, linux-lts-trusty, linux-lts-xenial, linux-oracle, linux-raspi2, linux-snapdragon, and wpa).

  • SGX and security modules

    Software Guard Extensions (SGX) is a set of security-related instructions for Intel processors; it allows the creation of private regions of memory, called "enclaves". The aim of this feature is to work like an inverted sandbox: instead of protecting the system from malicious code, it protects an application from a compromised kernel hypervisor, or other application. Linux support for SGX has existed out-of-tree for years, and the effort of upstreaming it has reached an impressive version 22 of the patch set. During the upstreaming discussion, the kernel developers discovered that the proposed SGX API did not play nicely with existing security mechanisms, including Linux security modules (LSMs).

  • GitHub acquires Semmle to help developers spot security vulnerabilities [Ed: Company in NSA PRISM pretends to care about security (and also, Microsoft now uses GitHub to change people's code without asking the developers)]

    Software hosting service GitHub has acquired Semmle, a code analysis platform that helps developers discover security vulnerabilities in large codebases.

today's howtos

LWN Articles About Linux (Kernel): Linux Plumbers Conference, Staging, Linux Conference North America, Stable Statistics

  • Topics from the Open Printing microconference

    On day two of the 2019 Linux Plumbers Conference, two of the principals behind the Open Printing project led the very first Open Printing microconference. Project leader Till Kamppeter and program manager Aveek Basu described the current state of printing on Linux and some of the plans for the future, including supporting scanning for multi-function devices. The picture they painted was rosy, at least for printing, which may not quite match the experience of many Linux users. As with many projects, though, Open Printing is starved for contributors—something that was reflected in the sparse attendance at the microconference. Basu began by pointing out that some attendees had likely printed their boarding passes from Linux, which highlights the importance of printing for Linux. People use it for bank documents, transport tickets, and more. He has been at Lexmark for 11 years, working on printing for Linux, macOS, and other Unix-based systems. Kamppeter said that he has been the Open Printing leader since 2001. The idea of the project is to do everything possible to make printing "just work" with Linux and other operating systems; the goal is "plug and print".

  • What happens to kernel staging-tree code

    The staging tree was added to the kernel in 2008 for the 2.6.28 development cycle as a way to ease the process of getting substandard device drivers into shape and merged into the mainline. It has been followed by controversy for just about as long. The recent disagreements over the EROFS and exFAT filesystems have reignited many of the arguments over whether the staging tree is beneficial to the kernel community or not. LWN cannot answer that question, but we can look into what has transpired in the staging tree in its first eleven years to see if there are any conclusions to be drawn there. The core idea behind the staging tree is that it is open to code that does not live up to the normal standards for inclusion into the kernel. Once a driver is added there, it is available to anybody who is brave enough to try to make use of it, but the real purpose is to allow developers to improve the code to the point that it is ready to go into the kernel proper. It serves as an easy place for new developers to try out simple changes and, when it works well, it helps the kernel to gain hardware support that might otherwise languish out-of-tree indefinitely.

  • The USB debugging arsenal

    At the 2019 Embedded Linux Conference North America, which was held in San Diego in August, Krzysztof Opasiak gave a presentation on demystifying the ways to monitor—and even change—USB traffic on a Linux system. He started with the basics of the USB protocol and worked up into software and hardware tools to observe, modify, and fuzz the messages that get sent. Those tools are part of the arsenal that is available to those interested in looking deeply into USB. Opasiak works in Poland for what he called a "small Korean company" (Samsung). He noted that it is not that easy to sniff USB traffic and that the ways to do so are not well known. But "there are no dragons"; nothing bad will happen if you do so. In some ways, USB is like the internet and some of the same tools can be used for both.

  • 5.3 Kernel development cycle statistics

    It's that time of the development cycle again: work on the 5.3 kernel is winding down with an expected final release date of September 15. Read on for LWN's traditional look at where the code in 5.3 came from in this relatively busy development cycle. As of this writing, 14,435 non-merge changesets have been pulled into the mainline repository for 5.3; these changes were contributed by 1,846 developers