The landscape of Linux is vast and varied. And, if you’re considering migrating to the open source platform or just thinking about trying a new distribution, you’ll find a world of possibilities.
Luckily, Jack Wallen has reviewed many different Linux distributions over the years in order to make your life easier. Recently, he has compiled several lists of distributions to consider based on your starting point. If you’re brand-new to Linux, for example, check out his list of distributions that work right out of the box — no muss, no fuss.
Jack also has lists of the best distros for developers, distros that won’t break the back of your old hardware, specialized distros for scientific and medical fields, and more. Check out Jack’s picks and see if one of these distributions is right for you.
To further simplify things, Jack breaks down his best distro choices in this article into the following categories: sysadmin, lightweight, desktop, distro with more to prove, IoT, and server. These categories should cover the needs of just about any Linux user.
In this article, Jack highlights three distributions for anyone to use, without having to put in a lot of extra time for configuration or problem solving.
Here Jack shares his picks for development efforts. Although each of these five distributions can be used for general development (with maybe one exception), they each serve a specific purpose.
Jack looks at four distributions that will make your aging machines relevant again.
These four specialized distributions are tailored to the needs of scientific and medical communities.
Learn more about Linux through the free “Introduction to Linux” course from The Linux Foundation and edX.
Achieving effective security takes constant discipline and effort on everyone’s part – not just one team or group within a company. That was Mårten Mickos’s message in his keynote speech appropriately titled, “Security is Everyone’s Responsibility,” at The Linux Foundation’s recent Open Source Leadership Summit (OSLS).
Mickos, CEO of HackerOne, which he described as a “hacker-powered security company,” told the audience that $100 billion has been spent on cybersecurity, yet, “Half of the money is wasted. We’ve been buying hardware and software and machines and walls and all kinds of stuff thinking that that technology and [those] products will make us secure. But that’s not true.”
Read more at The Linux Foundation
Continuous delivery is becoming a standard, if you implement the right process you get a predictable deployment. When a change is made in the code, most of the time the build, test, deploy and monitor steps are followed. This is the base for anyone willing to apply automation to their release process.
If a failure is detected during the monitoring phase, then an operator has to verify and rollback the failing release to the previous known working state. This process is time consuming and not always truthful since it requires someone to keep an eye on the monitoring dashboard and react to it.
If the team is well structured and applies the devops way of working, then there will be someone on duty who receives an alert when something goes wrong. Alerts are triggered based on metrics, but still, after receiving the alert, the person on duty has to turn on their laptop (if not on-site), take a look at the graph, think for a moment, realise that the issue is coming from the last release and decide whether or not there is a need to roll back.
Read more at Container Solutions
