Tag Archives: linux

Viperr Linux Keeps Crunchbang Alive with a Fedora Flair | Linux.com

Do you remember Crunchbang Linux? Crunchbang (often referred to as #!) was a fan-favorite, Debian-based distribution that focused on using a bare minimum of resources. This was accomplished by discarding the standard desktop environment and using a modified version of the Openbox Window Manager. For some, Crunchbang was a lightweight Linux dream come true. It was lightning fast, easy to use, and hearkened back to the Linux of old.

However, back in 2015, Philip Newborough made this announcement:

For anyone who has been involved with Linux for the past ten years or so, I’m sure they’ll agree that things have moved on. Whilst some things have stayed exactly the same, others have changed beyond all recognition. It’s called progress, and for the most part, progress is a good thing. That said, when progress happens, some things get left behind, and for me, CrunchBang is something that I need to leave behind. I’m leaving it behind because I honestly believe that it no longer holds any value, and whilst I could hold on to it for sentimental reasons, I don’t believe that would be in the best interest of its users, who would benefit from using vanilla Debian.

Almost immediately, developers began their own efforts to keep Crunchbang alive. One such effort is Viperr. Viperr is a Fedora respin that follows in the footsteps of its inspiration by using the Openbox window manager. By merging some of the qualities that made Crunchbang popular, with the Fedora distribution, Viperr creates a unique Linux distribution that feels very much old school, with a bit of new-school technology under the hood.

The one thing to keep in mind is that Viperr development is incredibly slow. At the moment, the most recent stable release is Viperr 9, based on Fedora 24. I read in the forums that, as of 2017, work was started on Viperr 10, but it’s still in alpha. So using Viperr might seem a bit of a mixed bag. After installing, I ran an update to find the running kernel at 4.7.5. That’s a pretty old kernel (relatively speaking). Even still, Viperr is a worthwhile distribution that might appeal to users looking for a lightweight Linux akin to Crunchbang.

Let’s install Viperr and see what gives this distribution its bite.


We’ve reached the point in Linux where walking through an installation is almost pointless—the installs are that easy. That being said, if you’ve installed Fedora or CentOS, you’ve installed Viperr. The Anaconda Installer makes installing any distribution incredibly simple. It’s all point and click, with a minimal of user interaction and steps. The only difference with Viperr is the post-Anaconda installation. Once you’ve completed the installation and rebooted the system, you’ll be greeted with a terminal window, in which a post-install script is run (Figure 1).

That script will first prompt you for your user password (created during the installation). Once you’ve authenticated, it will ask you a number of questions regarding software to be installed. During the run of the script, you can have LibreOffice installed (Figure 2), as well as other applications.

You will also be asked if you want to include the free and non-free Fusion repo. This repository is filled with software that Fedora or Red Hat doesn’t want to ship (such as Audacity, MPlayer, Streamripper, MythTV, GStreamer, Bombono-DVD, Xtables, Pianobar, LiVES, Telegram-Desktop, Ndiswrapper, VLC, some games, and more). It’s not a huge number of titles, but there are some items many Linux users consider must-haves.

Once the script completes its run, you can close out the terminal and start using Viperr.


As you probably expect, using Viperr is incredibly simple. The combination of the Openbox window manager and Conky giving a real-time read-out on system resources (Figure 3) is certainly a throwback to old-school Linux that many users will appreciate.

Click on the Viperr start button to gain access to all of the installed applications. Open an application and use it. That start menu, however, isn’t the only route to starting applications. If you right-click anywhere on the desktop, you gain access to the same menu (Figure 4).

I’ve always been a big fan of this type of menu system, as it makes interacting with that main menu incredibly efficient.

If you want to bring Viperr even further into the new world order, you can open up a terminal window and install Flatpak with the command sudo yum install flatpak (or sudo dnf install flatpak). Once you’ve installed Flatpak, you’ll find even more software can be installed, via Flathub.

Updates needed

Obviously, the one glaring problem is that Viperr is way out of date. However, you could go through the process of doing a distribution upgrade, via the dnf command. To do this, you would first have to install the DNF plugin with the command:

sudo dnf install dnf-plugin-system-upgrade

Once that command completes, you can upgrade from a base of Fedora 24 to 25 with the command:

sudo dnf system-upgrade download --releasever=25

When that command completes, reboot with the command:

sudo dnf system-upgrade reboot

The above command does take some time to complete (I had 2339 packages to upgrade), but it will eventually land you back on your Viperr desktop. I successfully completed that upgrade (which upgraded the kernel to 4.13), but I didn’t continue with the process to upgrade from 25 to 26 and then 26 to 27. Theoretically, it could work.

Outside of that, you’d be hard-pressed to find anything really wrong with a lightweight distribution like Viperr. It’s a fast, reliable throwback to a distribution so many users quickly fell in love with. With Crunchbang long gone, for those longing to return to the days of a more basic version of the operating system, Viperr fits that bill to a tee.

How to Connect Wi-Fi from Linux Terminal Using Nmcli Command | Linux.com

There are several command-line tools for managing a wireless network interface in Linux systems. A number of these can be used to simply view the wireless network interface status (whether it is up or down, or if it is connected to any network), such as iw, iwlist, ipifconfig and others.

And some are used to connect to a wireless network, and these include: nmcli, is a command-line tool used to create, show, edit, delete, enable, and disable network connections, as well as control and display network device status.

First start by checking the name of your network device using the following command. From the output of this command, the device name/interface is wlp1s0 as shown.

Read more at Tecmint

Microsoft Releases a Linux-Based OS » Linux Magazine

Microsoft has announced a new project that is going to be powered by the venerable Linux kernel. At the RSA 2018 Conference, the company shed some light on Microsoft Azure Sphere, a new platform to help create secured, Internet-connected microcontroller (MCU) devices.

Microsoft Azure Sphere is an end-to-end-solution, all the way from Azure Cloud to actual chips found on the targeted IoT device. Microsoft Azure Sphere is comprised of three components: Azure Sphere certified microcontrollers (MCUs); Azure Sphere OS; and Azure Sphere Security Service.

Azure Sphere OS is a custom OS aimed at security and agility. “Unlike the RTOSes common to MCUs today, our defense-in-depth IoT OS offers multiple layers of security. It combines security innovations pioneered in Windows, a security monitor, and a custom Linux kernel to create a highly-secured software environment and a trustworthy platform for new IoT experiences,” wrote Galen Hunt, Partner Managing Director, Microsoft Azure Sphere.

Developers can use Microsoft Visual Studio Tools to write applications for Azure Sphere. These tools include application templates, development tools and the Azure Sphere software development kit (SDK).

Visual Studio is not exclusive anymore to Windows. Microsoft open sourced a version of Visual Studio called Visual Studio Code, which is available for Linux.

The news was not surprising, Microsoft Azure team is is extremely pro-Linux and open source. Not only does Linux run on more than 50% Azure machines, the company has been using Linux to build components of cloud such as Azure Cloud Switch (ACS) and SONiC. None of these are distributed as Linux distro, but it’s about to change with Azure Sphere OS, which is a Linux distribution.

Since Sphere OS will be running on devices that will be shipped, can we safely say that Microsoft has literally become a Linux vendor?

Source: https://azure.microsoft.com/en-us/blog/introducing-microsoft-azure-sphere-secure-and-power-the-intelligent-edge/

Source link

Cloud Foundry for Developers: Definitions | Linux.com

In the first article in our series on the Cloud Foundry for Developers training course, we explained what Cloud Foundry is and how it’s used. We continue our journey here with a look at some basic terms. Understanding the terminology is the key to not being in a constant state of bewilderment, so here are the most important terms and concepts to know for Cloud Foundry. 

Command Line Interface (CLI)

The Cloud Foundry command line interface is a locally installed program that simplifies interaction with a Cloud Foundry instance. The CLI exposes functions (like pushing an app) via the command line, and executes REST calls against a Cloud Foundry target. For more information, see cloudfoundry/cli on GitHub.


A target is a Cloud Foundry installation or endpoint you want to interact with, e.g. by logging in to get information, configuring something, or deploying your application. This endpoint is a standard REST API, and the core API is consistent across all Cloud Foundry distributions. It takes the form of a standard URL, requires login credentials, and your organization and space.


That is you! Human users have their own user accounts in a Cloud Foundry instance. Humans users must have organization roles and space roles, with the organization role assigned first. There are also application users, and both human and application users authenticate through the User Account and Authentication (UAA) Server. For more information on users, visit Cloud Foundry Documentation: User Accounts.


A Cloud Foundry organization logically segregates tenants in a Cloud Foundry instance. The separation is purely logical, and there is no physical segregation. While the use of organizations is required, the method of segregation is arbitrary and left to the end user. Common use cases are for different business units, projects, or even companies (this is common in a hosted CF public cloud). To learn more, visit Cloud Foundry Documentation:Orgs.


An organization is divided into spaces. Applications and service instances are always scoped to a space, and every organization must contain at least one space. Spaces have roles, and these roles apply only to their spaces. Like organizations, the method of separation is left to the end user. You can use spaces for different applications, projects, or lifecycle steps, such as development, testing, and production. To learn more, visit Cloud Foundry Documentation:Spaces.

Quota Plan

Quota plans are logical resource limits for organizations and spaces. A quota plan is a named set of memory, service, and instance usage quotas, for example a set that includes 4GB of memory, 20 services, and 20 routes named “quota1”. Quota plans are not assigned per-user, but rather per organization, so everyone in the organization has the same quota plan. You may create any number of quota plans per account, but assign only one at a time. Spaces may also have quotas, but this is not required. To learn more, visit Cloud Foundry Documentation: Creating and Modifying Quota Plans.


Users are assigned to roles in organizations and spaces. Roles grant granular capabilities to a user. Role names are logical and attempt to convey scope, as well as the capabilities they provide: for example, Admin, Org Manager, Space Developer, and so on.

As a developer, you need the Space Developer role to deploy applications. To learn more, visit Cloud Foundry Documentation:Roles.

In the next blog, we’ll learn about the architecture of Cloud Foundry.

The information in this series is based on the Cloud Foundry for Developers (LFD232) training course from Cloud Foundry and The Linux Foundation. You can download a sample chapter from the course here.

Red Hat Enterprise Linux 7.5 Released » Linux Magazine

Red Hat has released Red Hat Enterprise Linux (RHEL) 7.5, which has a strong focus on hybrid cloud. As the market is evolving, so is Red Hat. In 2014, Red Hat signalled a shift in focus from datacenters to mobile and cloud. Red Hat acquired companies like FeedHenry and Core OS to strengthen its mobile and cloud portfolio.

Now the cash cow of Red Hat, RHEL, is reflecting their changing focus. RHEL 7.5 offers enhanced security and compliance controls, in addition to better integration with Microsoft Windows infrastructure both on-premise and in Microsoft Azure.

Companies are mixing environments – spanning across on-prem, public cloud and private cloud. RHEL 7.5 tries to reduce the complexity, especially in terms of security, that comes with such a hybrid environment. Red Hat Enterprise Linux 7.5 has enhanced software security controls to mitigate risk while also complementing, rather than hindering, IT operations.

Red Hat said that a major component of these controls is security automation through the integration of OpenSCAP with Red Hat Ansible Automation. This is designed to enable the creation of Ansible Playbooks directly from OpenSCAP scans which can then be used to implement remediations more rapidly and consistently across a hybrid IT environment. Sensitive data can also now be better secured across varied environments with enhancements to Network-Bound Disk Encryption that support automatic decryption of data volumes.

RHEL 7.5 also comes with production ready container solutions. RHEL 7.5 comes with full support for Buildah, an open source utility designed to help developers create and modify Linux container images without a full container runtime or daemon running in the background.

RHEL 7.5 is available for multiple architectures including x86, IBM Power, IBM z Systems, and 64-bit Arm. While RHEL is available for subscription there is 30 day evaluation version that can be downloaded and used for free.

Sources: https://www.redhat.com/en/about/press-releases/red-hat-strengthens-hybrid-clouds-backbone-latest-version-red-hat-enterprise-linux


Source link