Submit a proposal to speak at Open Source Summit North America taking place August 29-31, in Vancouver, B.C., and share your knowledge and expertise with 2,000+ open source technologists and community members. Proposals are being accepted through 11:59pm PDT, Sunday, April 29.
This year’s tracks/content will cover the following areas:
Need relief for your DNS headaches? First, it helps to understand how the domain name system works under the hood.
DNS is the Internet’s phonebook. Whenever you type in or click a human-readable web link (such as hpe.com), your web browser calls on a domain name system (DNS) resolver to resolve its corresponding Internet Protocol (IP) address.
DNS is essential. Without it, there is no Internet. Period. End of statement.
DNS is not just for browsers, though. If it runs on the Internet—Slack, email, you name it—DNS works behind the scenes to make sure all the application requests hook up with the appropriate Internet resources.
Following the release of Linux kernel 4.16, Linus Torvalds has said that the next kernel will be version 5.0. Or maybe it won’t, because version numbers are meaningless.
The announcement — of sorts — came in Torvalds’ message over the weekend about the first release candidate for version 4.17. He warns that it is not “shaping up to be a particularly big release” and questions whether it even matters what version number is slapped on the final release.
He says that “v5.0 will happen some day. And it should be meaningless. You have been warned.”
Looking for a way to get the most out of your Raspberry Pi? Running a project that just needs something more? Odd as it may seem, Linux might be the problem, so why not consider a non-Linux operating system? Several have been released, or adapted, for use on the Raspberry Pi.
1. Plan 9
Released as an open-source operating system in 1992, Plan 9 has a small footprint and is targeted at developers. Its lightweight presence makes it ideal for the Raspberry Pi.
A descendent of UNIX, Plan 9 is easy to install on the Pi, much like any other compatible operating system. Simply download the disk image, and write it to the microSD card.
Raise your hand if you’ve always wanted to try Gentoo Linux but never did because you didn’t have either the time or the skills to invest in such a challenging installation. I’m sure there are plenty of Linux users out there not willing to admit this, but it’s okay, really; installing Gentoo is a challenge, and it can be very time consuming. In the end, however, installing Gentoo will result in a very personalized Linux desktop that offers the fulfillment of saying, “I did it!”
So, what’s a curious Linux user to do, when they want to experience this elite distribution? One option is to turn to the likes of Redcore Linux. Redcore does what many have tried (and few have succeeded in doing) in bringing Gentoo to the masses. In fact, Sabayon Linux is the only other distro I can think of that’s truly succeeded in bringing a level of simplicity to Gentoo Linux that many users can enjoy. And while Sabayon is still very much in active development, it’s good to know there are others attempting what might have once been deemed impossible:
Making Gentoo Linux easy
Instead of building your desktop piece by piece, system by system, Redcore (like Sabayon) brings a much more standard installation to the process. Unlike Sabayon (which gives you the options of a GNOME, KDE, Xfce, Mate, or Fluxbox editions), Redcore offers a version that ships with two possible desktop options: The LXQt desktop and Openbox. The LXQt is a lightweight desktop that offers plenty of configuration options and performs quite well on older hardware, whereas Openbox is a very minimalist take on the desktop. In fact, once you log into the Openbox desktop, you’ll be left wondering if something had gone wrong (until you right-click on the desktop to see the solitary menu).
If you’re looking for a more modern take on the desktop, neither LXQt or Openbox will be what you’re looking for. However, there is no doubt the combination of a rolling-release Gentoo-lite system that uses the LXQt and Openbox desktops will perform quite well.
The official description of the distribution is:
Redcore Linux is a distribution based on Gentoo Linux (stable + some unstable) and a continuation of, now defunct, Kogaion Linux. Kogaion Linux itself was a distribution based initially on Sabayon Linux, and later on Gentoo Linux and it was developed by RogentOS Development Group since 2011. Ghiunhan Mamut (aka V3n3RiX) himself joined RogentOS Development Group in January 2014.
If you know much about how Gentoo is structured, Redcore Linux is built from Gentoo Linux stage3. Stage3 a tarball containing a populated directory structure from a basic Gentoo system that contains no kernel, only binaries and libraries essential for bootstrapping. On top of stage3, the Redcore developers add a kernel, a bootloader and a few other items (such as dbus and Dracut), as well as configure the init system (OpenRC).
With all of that out of the way, let’s see what the installation of Redcore is like and how well it can serve as your desktop distribution.
Installation
As you’ve probably expected, the installation of Redcore is incredibly simple. Download the live ISO image, burn it to a CD/DVD or USB, insert the installation media, boot the device, log into the desktop (live username/password is redcore/redcore) and click the installer icon on the desktop. The installer used by Redcore is Calamares, which means the installation is incredibly easy and, in an instant, familiar (Figure 1).
Figure 1: The Redcore-branded Calamares installer.
Everything with Calamares is automatic. In other words, you won’t have to manually partition your drive or select individual packages for installation. You should be able to start and finish a Redcore installation in five or ten minutes. Once the installation completes, reboot and log in with the username/password you created during installation.
Usage
Upon login, you can select between LXQt and Openbox. I highly recommend against using Openbox. Why? Because nothing will open from the menu. I was actually quite surprised to find the Openbox desktop fairly unusable upon installation. With that in mind, select the LXQt option and be done with it.
Upon logging in, you’ll be greeted by a fairly straight-forward desktop. Click on the menu button (bottom right of screen) and search through the menu hierarchy to launch an application. The list of installed applications is fairly straightforward, with the exception of finding Steam and Wine pre-installed. You might be surprised, considering Redcore is a rolling distribution, that many of the user-crucial applications are out of date. Take, for instance, LibreOffice. Redcore ships with 5.4.5.1. The Still release of LibreOffice is currently at 5.4.6. Opening the Sisyphus GUI (front end for the Sisyphus package manager) and you’ll see that LibreOffice is up to date (according to the package manager) at 5.4.5.1 (Figure 2).
Figure 2: The Sisyphus GUI package manager.
If you do see packages available for upgrade (which you might), click the upgrade button and allow the upgrade to complete. Considering this is a rolling release, you should be up to date. However, you can search through Sisyphus, locate new packages to install, and install them with ease. Installation with the Sisyphus front end is quite user-friendly.
That default browser
You won’t find a copy of Firefox or Chrome installed on Redcore. Instead, QupZilla serves as the default browser. When you do open the default browser (or if you click on the Ask for help icon on the desktop) you will find the preconfigured home page to be the recorelinux freenode.net page. Instead of being greeted by a hand-crafted application, geared toward helping new users, one must choose a nickname and venture into the world of IRC. Although one might be inclined to think that does new users a disservice, one must consider the type of “new” user Redcore will be serving: These aren’t going to be new-to-Linux users. Instead, Redcore knows its users and knows many of them are already familiar with IRC. That means users don’t have to turn to Google to search for answers. Instead, they can chat with other users and even developers to solve their problems. This, of course, does depend on those users (who might be capable of answering questions) actually be logged into the redcorelinux channel on freenode.
That default theme
I’m going to make a confession here. I’ve never understood the whole “dark theme” preference. I do understand that taste is a subjective issue, but my taste tends to lean toward the lighter themes. That’s not a problem. To change the theme for the LXQt desktop, open the menu, type desktop in the search field, and then select Customize Look and Feel. In the resulting window (Figure 3), you can select from the short list of theme options.
Figure 3: Changing the desktop theme in Redcore.
That target audience
So who is Redcore’s best target audience? If you’re looking to gain the benefit of Gentoo Linux, without having to go through the exhausting “get up to speed” and installation process required to compile one of the most challenging operating systems on the planet, Redcore might be what you’re looking for. It’s a very simplified means of enjoying a Gentoo-less take on Gentoo Linux. Of course, if you’re looking to enjoy Gentoo with a more modern desktop, I would highly recommend Sabayon. However, the LXQt lightweight desktop will certainly give life to old hardware. And Recore does this with a bit of Gentoo style.
Learn more about Linux through the free “Introduction to Linux” course from The Linux Foundation and edX.
This week in Linux and open source news, OpenContrail SDN becomes Tungsten Fabric, a new open source tool aims to improve the Linux gaming experience, and more! Stay in the open source know with our handy weekly news digest!
1) “This move is intended to expand the open source SDN developer community to bring about quicker development and to attract new users.”
3) “MEF worked with The Linux Foundation and ETSI to develop an NFV and SDN certification to focus on related knowledge and skills. Meantime, MEF published specs for its Presto APIs.”
Collaborating on freely available code enables companies and programmers to pool resources to solve common problems and avoid reinventing the wheel. Companies build competing products and services from these open source foundations that they might never have been able to build otherwise.
But the open source revolution has been slow to come to the hardware world. A number of open source gadgets and circuit boards have been released in recent years, but while it’s possible to run a laptop or server on nothing but open source software, the inner workings of our gadgets remain proprietary.
An open source chip architecture called RISC-V could soon help change that. Chip maker Nvidia and storage company Western Digital have both announced plans to use RISC-V chips in their core products, …
I started using Linux three years ago while attending university, and I was fascinated to discover a different desktop environment. My professor introduced me to the Ubuntu operating system, and I decided to dual-boot it along with Windows on my laptop the same day.
Within three months, I had completely abandoned Windows and shifted to Fedora after hearing about the RPM Package Manager. I also tried running Debian for stability, but in early 2017 I realized Arch Linux suits all my needs for cutting-edge packages. Now I use it along with the KDE desktop and can customize it according to my needs.
Is it a replacement for Android and Chrome OS? Good question. It’s not clear what Google plans for it. We do know it runs on Google’s high-end, Chrome-OS powered Pixelbook. You can also install it on Acer Switch 12 and Intel NUC and, eventually, on a Raspberry Pi 3. …
First, it’s built on the Zircon micro-kernel. Besides the microkernel, it includes a small set of userspace services, drivers, and libraries. These are used to boot the system, talk to hardware, load userspace processes and run them, and not much more.
A hardware-rooted chain of trust verifies the integrity of every relevant component in the cloud platform, giving you security automation that flexibly integrates into the DevOps pipeline. A true chain of trust would start in the host chip firmware and build up through the container engine and orchestration system, securing all critical data and workloads during an application’s lifecycle.
Hardware is the ideal foundation because it is rooted in silicon, making it difficult for hackers to alter.
The chain of trust would be built from this root using the measure-and-verify security model, with each component measuring, verifying and launching the next level. This process would extend to the container engine, creating a trust boundary, with measurements stored in a Trusted Platform Module (TPM) on the host.
