Language Selection

English French German Italian Portuguese Spanish

Neptune 5.1

Filed under
GNU
Linux
Debian

We are proud to announce version 5.1 of Neptune .

This update represents the current state of Neptune 5 and renews the ISO file so if you install Neptune you don't have to download tons of Updates.

The Calamares Installer now handles also installing hyphentation, thesaurus and spellecheck for the choosen localization.

Main changes in this version are the update of Plasma to version 5.12.4 and KDE Frameworks to version 5.44. Besides that we also updated our default icon theme to include some new icons and Plasma Discover got some minor fixes and a slightly improved UI now featuring a refresh button in the Update dialog.

Knetworkmounter should work like usual again and Enlightenment fans should be able to install their beloved desktop in version 0.22.

Read more

What’s New in Neptune OS 5.x

  • What’s New in Neptune OS 5.0

    Neptune OS 5.0 the Linux distribution focused on KDE plasma has been release. This release uses the latest KDE Plasma 5.12 desktop environment along with the KDE Applications 17.12 and KDE Frameworks 5.43.0 software suites. It also promises new ways to run the latest software versions.

    Neptune OS 5.0 ships not only with the latest and greatest Plasma LTS release but also features our known Neptune Artwork with beautiful designs for all applications no matter if GTK+2, GTK+3 or Qt4 or Qt5 applications. Combined with our Icon Theme this provides a truly marvelous user experience.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Reducing sysadmin toil with Kubernetes controllers

Kubernetes is a platform for reducing toil cunningly disguised as a platform for running containers. The element that allows for both running containers and reducing toil is the Kubernetes concept of a Controller. [...] The canonical example of this in action is in how we manage Pods in Kubernetes. A Pod is effectively a running copy of an application that a specific worker node is asked to run. If that application crashes, the kubelet running on that node will start it again. However, if that node crashes, the Pod is not recovered, as the control loop (via the kubelet process) responsible for the resource no longer exists. To make applications more resilient, Kubernetes has the ReplicaSet controller. The ReplicaSet controller is bundled inside the Kubernetes controller-manager, which runs on the Kubernetes master node and contains the controllers for these more advanced resources. The ReplicaSet controller is responsible for ensuring that a set number of copies of your application is always running. To do this, the ReplicaSet controller requests that a given number of Pods is created. It then routinely checks that the correct number of Pods is still running and will request more Pods or destroy existing Pods to do so. By requesting a ReplicaSet from Kubernetes, you get a self-healing deployment of your application. You can further add lifecycle management to your workload by requesting a Deployment, which is a controller that manages ReplicaSets and provides rolling upgrades by managing multiple versions of your application's ReplicaSets. Read more

Android Leftovers

Server: IBM, LAMP and Kubernetes

  • A HATS For Many Occasions
    IBM gives customers plenty of options when it comes to its Rational Host Access Transformation software, including several modes of operation, different runtime options, and support for different operating systems in screen modernization engagements. With last week’s launch of HATS version 9.7, the development and deployment options got even wider. Regardless of which downstream options a HATS customer ultimately chooses, it all starts out basically the same on the front side of the sausage machine: Customers come to HATS because they have a 5250 (or 3270 or VT100) application that they want to transform, but they don’t want to go through the hassle, expense, and risk of modifying the IBM i, z/OS, or Unix application’s source code.
  • Six top skills that you should acquire in 2019
    There is a growing demand for the fullstack development skill set, which is the ability to develop tech both on the front-end/client side and back-end/server side. As you can’t learn all, select combinations like MEAN or LAMP stack.
  • Kubernetes and the Enterprise
    The reason we were having this conversation was around SUSE’s Cloud Application Platform (CAP). This is our Kubernetes focused Cloud Foundry distribution. And as part of the Kubernetes focus, we have been supporting and running SUSE CAP on Azure’s AKS for the last year or so. The conversation continued with observations that Kubernetes was clearly the future across IT. Yet to date, Cloud Foundry still has a good following with the large enterprise. And the thinking was that the Cloud Foundry approach really helped the large enteprise work with their applications, even if the applications were purely ‘container’ applications. Cloud Foundry makes the container-side of managing your ‘container’ application transparent. This approach ultimately lowers the tasks, breadth of tooling, and knowledge you have to surround Kubernetes with. It was with this thought, that a light-bulb went on.

today's howtos