| DistroWatch Weekly
|DistroWatch Weekly, Issue 553, 7 April 2014
Welcome to this year's 14th issue of DistroWatch Weekly!
One of the great benefits inherent in open source software is the way distributions can be customized. Users of open source operating systems do not need to bow to the idea of "one size fits all". This means people who want lots of features running on powerful hardware can find a matching operating system. Others, who are using older hardware and require efficiency, can find smaller distributions to suits their needs. This week we focus on a wide range of projects filling many different niches. We start with a review of Puppy Linux, a small, user-friendly distribution that targets lower-end hardware. In our News section this week we talk about openSUSE's new KDE software repositories, Ubuntu's future plans for their One file synchronization service and Slax's quest to find a new default desktop environment. DragonflyBSD, a powerful server operating system, may be going through some exciting changes this year. The project is looking at expanding its virtualization support and there are plans to release a new version of the advanced Hammer file system. We also cover an interview with a Gentoo developer and discuss pop-ups recently seen by Android users on this website. In our Tips and Tricks column this week, guest writer Richard White provides a tutorial for working with GNU Privacy Guard, a useful tool for securing private documents. As usual, we cover the distribution releases of the past week and look ahead to fun new developments to come. We wish you all a wonderful week and happy reading!
|Feature Story (by Jesse Smith)
First Impressions of Slacko Puppy 5.7
There were concerns last year when Barry Kauler announced he was retiring from the Puppy Linux project. People wondered how the Puppy project would do without the founder at the distribution's helm. Well, the good news for fans of the Puppy distribution is that there is an active community surrounding Puppy and the project is continuing to put out new releases. The most recent release of the distribution is Slacko Puppy 5.7. Slacko Puppy is an edition of Puppy Linux put together using packages from the Slackware distribution. This means Slacko Puppy is binary compatible with Slackware 14.0 and can use packages built for the Slackware and Salix distributions.
The latest version of Slacko Puppy is available in two 32-bit flavours. One build includes PAE support and the other does not, allowing Puppy to run on older hardware. Both download images are approximately 160MB in size. Booting from the Puppy media brings us to a graphical environment running atop Joe's Window Manager (JWM). An initial configuration screen appears, presenting us with a single, compact collection of options. From this window we can make initial adjustments to our preferred language, set our time zone, enable the distribution's firewall, adjust the resolution of our display and set a hostname. Once we look over the options and dismiss the configuration window, the distribution plays a barking sound, confirming the sound system works. Then a welcome screen appears, explaining where we can find local help files, how we can get on-line and we are offered a link to Puppy's control centre. The distribution's graphical user interface is presented in a traditional manner with an application menu, task switcher and system tray placed at the bottom of the screen. Several icons sit on the desktop, presenting us with short-cuts to Puppy's system installer, a web browser, e-mail client, productivity software and more. Sitting in the system tray we find icons for managing the firewall and network configuration.
Slacko Puppy 5.7 -- Accessing Puppy's documentation
(full image size: 487kB, resolution: 1280x1024 pixels)
Puppy can be installed a few different ways and on a variety of storage media. The distribution recommends installing Puppy using what is called the Frugal method. This essentially allows Puppy to be installed on the partition of another operating system and saves the user from the hassle of rearranging their hard drive partitions. Puppy may also be installed in a more traditional manner with the distribution getting a dedicated hard disk partition. I opted to use the latter method and found the Puppy system installer did a nice job of walking me through the steps. The graphical installer provides a short, quick method of getting Puppy onto the local hard disk. We set up partitions using the GParted partition manager, select whether we want a Full (traditional) or Frugal installation. We select the partition we want to use, the installer copies its files and, at the end, we are advised to manually run the GRUB boot loader setup wizard.
I ran into two problems during the install process. The first was that Puppy's installer claimed there was already an installation of the distribution on my hard drive (there was not). I was offered the choice of upgrading the non-existent installation or wiping it and performing a fresh installation. I took the latter option. The first time through the install process I ran the GRUB setup application in its basic mode. Upon rebooting the GRUB menu came up with three options (Puppy, Ubuntu and Windows), though only the first operating system in the list existed on the drive. None of the options would cause Puppy to boot. I launched Puppy from the live media again and re-ran the GRUB setup script in Expert mode. This time, when I rebooted the machine, selecting "Puppy" from the GRUB menu caused my local copy of Puppy to boot properly.
At least Puppy booted properly when I ran it in a virtual machine powered by VirtualBox. When I tried running Puppy on physical hardware the distribution was unable to boot. Puppy operated smoothly in the virtual environment. Programs opened quickly, the desktop was responsive and Puppy managed to get by with less than 100MB of memory. The only problem I had with Puppy when running in a virtual machine was with the mouse pointer. The Puppy mouse pointer did not integrate well with my host operating system's mouse pointer and this sometimes made clicking on buttons (particularly small ones) difficult.
Slacko Puppy 5.7 -- Managing software packages and system settings
(full image size: 328kB, resolution: 1280x1024 pixels)
Software management on Puppy is an unusual affair when compared against other Linux distributions. At first things seem similar with Puppy's graphical package manager giving us the ability to browse categories of software and see lists of packages matching our searches. Where Puppy's package management differs from many mainstream distributions is the steps we take once a package has been marked for installation. Puppy will give us the option of resolving dependencies or simply installing software without dependencies (which seems unlikely to be productive). Then we are asked to manually select a repository mirror from a list of servers. Slacko Puppy generally pulls software from Slackware repositories, providing us with a large range of packages. Each package download is then processed one at a time, each package resulting in a new console window opening to display its progress. If we are just downloading one or two packages this approach works well, but if we need twenty packages the steady flood of new console windows popping up prevents us from using the desktop for anything else while packages are downloading. I had mixed results using Puppy's package manager. Most of the time it worked, but I did run into a few instances of package dependencies not downloading or installing with errors. I also found, once new software had been installed, it could be challenging to hunt down the new item in Puppy's very full application menu.
Speaking of applications, Puppy comes with a lot of utilities. In fact, the tiny distribution packs a surprising amount of software into a tiny space. Puppy ships with the Firefox web browser and Sylpheed e-mail client. By default there was no Flash plugin for Firefox, but there is a program in the application menu which downloads and installs Adobe's Flash player. The AbiWord and Gnumeric productivity applications are featured, along with the XChat IRC client. The application menu contains a PDF viewer and a program which converts various document types to PDF files. The GNOME front-end to MPlayer is included and I found Puppy could play all multimedia files I threw at it. The distribution ships with disc burning software, a multimedia file converter, a handful of games, the Transmission bittorrent client and some drawing programs. We are given a calendar app, a calculator and a text editor. There are system administration utilities as well, including a log viewer and programs to display hardware information. There is a program for setting up the distribution's firewall and a task scheduler which appears to be a graphical front-end to the venerable cron daemon. In the background Puppy supplies the Linux kernel, version 3.4.
Slacko Puppy 5.7 -- Various desktop applications
(full image size: 192kB, resolution: 1280x1024 pixels)
One topic which tends to come up whenever Puppy is discussed is the project's approach to security, or perhaps its lack of security. The distribution is, by default, effectively a single-user system. When the distribution boots we are automatically logged into the system as the root (administrator) user. As the only user on the system has full control and there is no password to get in the way, Puppy has earned a reputation as either being quite convenient or reckless, depending on one's feelings toward recommended security practices. Personally, while running as the root user all the time makes me uncomfortable (mostly because one false keystroke or mouse click could wipe out a portion of my operating system), I will acknowledge that Puppy appears geared mostly toward being used as a live CD, not as a primary operating system. The distribution appears to be trying very hard to make things as easy for the user as possible. Apart from the lack of passwords or user restrictions, the distribution ships with icons on the desktop for popular end-user applications. These icons are labeled based on a task rather than with an application name. This should make it fairly easy for new users to locate the software they need. It is easier for a new user to find and select "email", "write" or "draw" than to understand the significance of "Thunderbird", "Kate" and "GIMP". Puppy's utilities also come with a lot of built-in documentation. The system installer, for instance, and the initial configuration wizard both give a good deal of on-screen explanation as to what they do and how the user should interact with these tools. I like this approach as it lowers the bar for using Puppy and saves the user from hunting for on-line assistance. In short, while Puppy's approach to user accounts is unusual, it does fit consistently with the project's other characteristics and user-friendly focus.
A few other thoughts stood out in my mind during my time with Slacko Puppy. One is that the organization of the application menu takes some adjustment if we are coming from another Linux distribution. The menu is organized differently and uses different names for categories of software. It is not hard to find most items, but there is a period of adjustment. Everything runs quickly on Puppy, the distribution runs surprisingly fast and most programs open almost instantly. I like Puppy's small memory footprint and I am regularly impressed by the amount of functionality Puppy can squeeze into such a small download image. Many of the default programs which come with Puppy seem to be selected for their small size rather than their popularity or functionality. Luckily, for us, if we need additional software it can usually be found in Puppy's package manager, which pulls from the full range of Slackware packages.
Puppy is an interesting distribution. It contains perhaps the best balance between functionality, friendliness and small size I have seen to date. The distribution appears to be more of a secondary operating system, something I would travel with on a thumb drive in my pocket, rather than a primary operating system that I would install on my desktop. Still, the distribution's small size and friendly nature are impressive and, had I older hardware I wanted to resurrect, Puppy would be on a short list of possible operating systems I would want to use.
* * * * *
Hardware used in this review
My physical test equipment for this review was a desktop HP Pavilon p6 Series with the following specifications:
- Processor: Dual-core 2.8GHz AMD A4-3420 APU
- Storage: 500GB Hitachi hard drive
- Memory: 6GB of RAM
- Networking: Realtek RTL8111 wired network card
- Display: AMD Radeon HD 6410D video card
|Miscellaneous News (by Jesse Smith)
New KDE packages coming to openSUSE, plans for DragonflyBSD's next release, Ubuntu announces the end of their One service, an interview with a Gentoo developer, an interview with Slax's lead developer and reported pop-up ad on DistroWatch
Good news for openSUSE users and fans of the KDE project! The openSUSE distribution will soon have access to multiple KDE software repositories which will help desktop users keep up to date with the latest developments in the KDE community. Raymond Wooninck announced the new options last week, saying: "With the release of KDE 4.12.4 (expected coming Tuesday), the openSUSE KDE:Release:xy Repositories will be consolidated into a single KDE:Current repository, where you can find the current KDE SC Release. We believe that with this step, it would be easier for people to track the current KDE SC release and stay up-to-date without the need to change repositories." The four repository options will include staying with the stable, traditional repositories which come with openSUSE, using a Current repository that is always up to date with the latest KDE releases and there are two testing repositories for people who like to keep on the cutting edge of desktop software development.
* * * * *
DragonflyBSD originally started as a fork of the FreeBSD operating system, but the project has developed some powerful technologies and a community of its own. Justin Sherrill has some ideas for changes and features that he wants to see in the next release of DragonflyBSD and he posted these concepts last week. Some of Sherrill's plans involve improving virtual machine support, an improved package management experience for the user and PAM support. Sherrill also put forward the idea of dropping 32-bit x86 builds of DragonflyBSD in the future. "I think we're on the edge of where it can be dropped. PC-BSD and FreeNAS are both dropping i386, for example. My instinct -- and this can certainly change -- is to say the earliest we'll drop it is for the 4.0 release, which will hopefully also be the first user-testable version of Hammer 2. That's two releases from now at the soonest."
* * * * *
In a move some suspected was a April Fools joke, Canonical announced last week that it is closing down the Ubuntu One storage service. "As of today, it will no longer be possible to purchase storage or music from the Ubuntu One store. The Ubuntu One file services will not be included in the upcoming Ubuntu 14.04 LTS release, and the Ubuntu One apps in older versions of Ubuntu and in the Ubuntu, Google, and Apple stores will be updated appropriately. The current services will be unavailable from 1 June 2014; user content will remain available for download until 31 July, at which time it will be deleted." Canonical has promised to release the code running Ubuntu One as open source software which would allow further competition and allow people to run their own One storage services.
* * * * *
Each month the Gentoo project publishes a newsletter in which one of the distribution's developers is interviewed. This week we hear from developer Tom Wijsman as he recounts his first experiences with Linux, what path guided him to work on Gentoo, his dream job and his views on Gentoo's strengths and weaknesses. "What I think Gentoo could use more is more manpower; what made Gentoo powerful is its community, and its community is formed by users who contribute. And to this extent the amount of contributions determine how powerful Gentoo becomes."
* * * * *
Czech website root.cz recently ran an interview with the Slax project's founder, Tomas Matejicek. Matejicek republished the interview, translated into English, on his blog. In the interview he talks about Slax's current development challenges, issues with Slax's default KDE desktop, the search for a new desktop environment and what makes for a good desktop interface. "[An] ideal desktop environment starts within few seconds (I mean two) and gives the user a simple way to run programs and switch between them. That's it, it's nothing special at all."
* * * * *
Last week DistroWatch published an article discussing the possibility of migrating our web host to Ubuntu Server from Debian. This article was intended to be light humour and our way of participating in the tradition of April Fools. The truth is we are quite happy with Debian and plan to stick with the venerable operating system. However, what was not a joke was the pop-up some Android users were seeing upon visiting DistroWatch. This pop-up, which suggested the user's mobile device was infected with a virus, caused some of our readers concern last week. Some people worried our website was infected with malware, others thought it was a misguided attempt by DistroWatch to scam our readership. The truth is the ad appears to have come from one of our ad partners and was only displayed to a handful of Android users visiting this site. We have worked to find the source of the malicious pop-up and are trying to get it removed from the advertising network in question. If you see notifications warning of a virus infection on this website, please close the pop-up and do not follow any links provided.
|Tips and Tricks (by Richard White)
File encryption with GNU Privacy Guard
Encryption ensures that files are stored in an encrypted form whether you are transmitting it over the Internet, backing it up on a server, carrying it on USB or on your laptop. Encrypting your data makes it unreadable to anyone but you or intended recipient, thus preventing unwanted access to it.
GPG (GNU Privacy Guard)
GPG stands for GNU Privacy Guard. It is a key-based encryption method which means that a pair of keys is used to encrypt and decrypt a
message so that it arrives securely. Initially, a user receives a public and a private key pair from a certificate authority. Any other user who wants to send an encrypted message can get the intended recipient's public key from the public directory. They use this key to encrypt the message, and then send it to the recipient. When the recipient gets the message, they decrypt it with their private key,
which no one else should have an access to.
GPG gives you the public key and the private key.
A public key is a key that you share with the public. It can be given to anyone you wish to received encrypted messages from. They would encrypt the message with your public key. They cannot decrypt their own message after they encrypt it. Only you, who hold the private key, can decrypt the message. A private key is your own personal password. Your private key will be used to decrypt messages encrypted in your public key, If you give someone your private key he can decrypt and read all your messages written in your public key.
Using GPG from the terminal
Today most Linux distributions include GPG by default. To find out if this is the case, open up a terminal and type:
$ gpg --version
You should get version number. If so, you don't need to do anything, if not you can install GPG from your distribution's repositories.
To use GPG to encrypt your communications, you need to create a key pair.
Launch your terminal and run the following command to get started:
$ gpg --gen-key
You will be prompted back with the following:
Please select what kind of key you want:
Select number 1, as it can be used for encryption and decryption, the second and third choices are only allowed to sign messages. To do so, press the number 1, and then press Enter.
(1) DSA and Elgamal (default)
(2) DSA (sign only)
(5) RSA (sign only)
You then will be prompted with the following:
1 DSA key-pair will have 1024 bits.
You will want to enter "2048" here, as recommended by GPG.
If you don't want your key to expire (for the next prompt, select 0).
Answer Yes if the information is correct, when prompted, and then enter your real name, your email address, and a comment (which is optional). If everything is correct, press "o" (for OK) and then Enter.
2 ELG-E keys may be between 1024 and 4096 bits long.
3 What key-size do you want? (2048)
After that, you will be asked to enter a pass-phrase. This process will be repeated. As usual, make a strong password which will be difficult to crack. Do not enter a name/address/birth date or word from a dictionary as your password.
After entering your pass-phrase, follow the instructions in the terminal:
We need to generate a lot of random bytes. It is a good idea to perform some other action (type on the keyboard, move the mouse, utilize the disk) during the prime generation; this gives the random number generator a better chance to gain enough entropy.
When you have successfully finished generating your key, you will see a message similar to the following one:
gpg: key 083C39A4 marked as ultimately trusted.
public and secret key created and signed.
Key servers are used to distribute your public key to other key servers so that other users can easily look up your name (or the e-mail address) in the database and find your public key to send encrypted messages to you. This eliminates the process of physically or insecurely giving your friend your public key, and allows others to be able to find you on the on-line database.
Uploading your public key to the key server:
$ gpg --send-keys --keyserver [keyservers.address.com] [yourpublicid]
You should replace keyservers.address.com with key server of your choice (or use mit.edu which syncs it with other servers) also replace yourpublicid with yours.
In the end it would look as follows:
$ gpg --send-keys --keyserver hkp://pgp.mit.edu 083C39A4
To Encrypt a File
If you wish to encrypt a file for your friend with his public key, run the command in the following format:
$ gpg -o encrypted_file.gpg --encrypt -r key-id original.file
-o encrypted_file.gpg = Output to the following filename.
--encrypt = Encrypting a file
-r = Recipient. KEY-ID would be your friends KEY-ID here.
original.file = The file that you will be encrypting.
To Decrypt a File
If someone has sent you a file that has been encrypted with your public key, you can decrypt it with following command:
$ gpg --decrypt filename.gpg
With GPG you can do a symmetric encryption where you encrypt a file with a pass-phrase. This is not a key based encryption. In symmetric cryptography, the same key is used for both encryption and decryption. This approach is simpler in dealing with each message, but it is less secure since the key must be communicated to recipient.
To encrypt a file with a pass-phrase, use:
$ gpg -c filename.txt
To decrypt this type of file, just use:
$ gpg filename.txt
You will be prompted for the pass-phrase and it will decrypt the file.
Clearsign a Document
Clearsigning is very similar to adding your signature to the bottom of a letter or an important document. It signifies that it actually comes from you. By clearsigning, it generates a SHA1 hash of the entire file's contents and adds the SHA1 sum to the bottom of the signature. If the file has been tampered with, the signature verification will fail, which can be used to spot the forgery.
If the user edits the file after it has been signed, the verification of the signature will also fail, because the SHA1 sum will not match the one of the actual content.
To clearsign a document or file, run the following:
$ gpg --clearsign filename.txt
Generating Revocation Key
A revocation key is used to revoke your public key if your private key has been compromised in any way, or you suspect that it may be compromised. To create a revocation key, run the command:
$ gpg --output revoke.asc --gen-revoke keyid
Keep the revocation key in a safe place, anyone who gets a hold of it can use it to disable your key. (You could use symmetric encryption on your revocation file.)
Tips for using GPG from terminal
To list the Keys you have imported into GPG, you can issue the following command:
$ gpg --list-keys
A list of the keys registered with your e-mail should appear (and since there should be only one, it will only list your key.) Then, you can obtain your KEY-ID and run the command above in order to submit it to the key servers.
To display the private or public keys on your key ring
$ gpg --list-public-keys # will list public keys
$ gpg --list-secret-keys # will lists private keys
$ gpg --import KEYFILE
Keyfile would be the filename of the public key in your home folder. (If it is not in your home folder, use the cd command to go to the proper directory first, and then run the above command.)
Exporting your Public Key
To export your public key in the ASCII Armored fashion, run the following command:
$ gpg --export -a > publickey.asc
* * * * *
About Richard White
Richard is technology enthusiast, on more than one occasion he was called a geek, he is also the author of three books, his most recent, Privacy in Digital Era is forthcoming in hardcover in May 2014. He is also the head editor and the driving force behind Digital Era website. The purpose of Digital Era is to present and give resources and tools to achieve and maintain anonymity, security and privacy. Richard regularly writes about privacy related issues and is hard at work on The Art of CLI, a collection of command line, open-source software. For more information on GNU Privacy Guard works and how to use graphical front-ends to the GPG software, you can find further reading on White's Digital Era website.
|Released Last Week
Michael Prokop has announced the release of Grml 2014.03, a Debian-based live CD with a collection of GNU/Linux software designed for system administrators and suited for administrative tasks including system rescue: "We just released Grml 2014.03 - Ponywagon. This Grml release provides fresh software packages from Debian testing (a.k.a. jessie). As usual it also incorporates up2date hardware support and fixes known bugs from the previous Grml release. New features: new boot option vlan; grml-debootstrap. Important Changes: forensic mode - the readonly boot option was renamed to read-only (caused by change in upstream's live-boot). Bits and bolts: Linux kernel is based on 3.13.6...." See the release announcement and release notes for further information and various links.
Trisquel GNU/Linux 6.0.1
Rubén Rodríguez Pérez has announced Trisquel GNU/Linux 6.0.1, an upgrade release of the Ubuntu-based distribution that uses strictly free software only (as defined by Free Software Foundation's guidelines): "This is an incremental upgrade release which includes all of the maintenance updates and bugfixes since the publication of Trisquel 6.0. Users that already have 6.0 installed don't need to reinstall. Just use the update manager or apt-get dist-upgrade. The 6.0.1 release comes with several new features and updates: Support for UEFI installation (amd64); Abrowser upgraded to v28, with improved Facebook integration; Linux-libre updated to 3.2.0-60, 3.5 and 3.11 branches available in the repositories; Added open-ath9k-htc firmware to the images; Added all free firmware files to the netinstall images so they can be used over wifi. Trisquel can now be installed on UEFI based computers by disabling the security system in the BIOS setup. We do not sign our kernels or boot managers as that would require us to request permission from Microsoft, something that shouldn't be needed in any case." Here is the release announcement.
Clonezilla Live 2.2.2-32
Steven Shiau has announced a new stable release of Clonezilla Live, a Debian-based live CD designed primarily for partition and disk imaging/cloning tasks: "This release of Clonezilla live (2.2.2-32) includes major enhancements and bug fixes. The underlying GNU/Linux operating system was upgraded; this release is based on the Debian Sid repository (as of 2014/Mar/31). Linux kernel was updated to 3.13.7-1. Partclone was updated to 0.2.70; an issue about restoring image file to raw format has been fixed; thanks to quaid for reporting this issue. Syslinux was updated to 6.03-pre9. Package drbl was updated to 2.8.6-drbl1, and clonezilla was updated to 3.9.49-drbl1. Two options were added to makeboot.sh: -L and -U; patch provided by Ceasar Sun. A boot parameter 'ocs_prompt_mode' was added so some of the prompt could be shown in TUI or CMD mode." See the entire release announcement for a full changelog.
John Martinson has announced the release of Robolinux 7.4.2, a user-friendly, Debian-based distribution featuring integrated virtualisation software (for running another operating system in an application window as a "guest"). From the distribution's download page on SourceForge: "What's new in Robolinux version 7.4.2? First, we updated our Robolinux Debian based operating system. Second, we are also announcing two new software programs: Robolinux Stealth VM Software for Linux Mint and Ubuntu operating systems! Since Robolinux invented 'Revolutionary Stealth VM' inside our Debian operating system we decided to create specific versions that work on all Linux operating systems so now anyone can run Windows XP or 7 inside Linux Mint or Ubuntu virus free! Please note the Robolinux Stealth VM for openSUSE and all RPM based operating systems will be available in April, 2014...." Check Robolinux web site as well as the project site for further information.
Jim Thompson has announced the release of pfSense 2.1.1, a free network firewall distribution based on FreeBSD with a customized kernel and third party free software packages for additional functionality: "I'm happy to announce the release of pfSense 2.1.1. The largest change is to close the following security issues / CVEs: FreeBSD-SA-14:01.bsnmpd / CVE-2014-1452; FreeBSD-SA-14:02.ntpd / CVE-2013-5211; FreeBSD-SA-14:03.openssl / CVE-2013-4353, CVE-2013-6449, CVE-2013-6450. Other than these, the em/igb/ixgb/ixgbe drivers have been upgraded to add support for i210 and i354 NICs. Some Intel 10Gb Ethernet NICs will also see improved performance." Follow the release announcement and the detailed release notes for further information.
* * * * *
Development, unannounced and minor bug-fix releases
|Upcoming Releases and Announcements
Summary of expected upcoming releases
New distributions added to waiting list|
- Wh1t3 C4t. Wh1t3 C4t is a Linux-based desktop operating system which offers GNOME and KDE desktop environments.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 14 April 2014. To contact the authors please send email to:
- Jesse Smith (feedback, questions and suggestions: distribution reviews, questions and answers, tips and tricks)
- Ladislav Bodnar (feedback, questions, suggestions and corrections: news, donations, distribution submissions, comments)
- Bruce Patterson (feedback and suggestions: podcast edition)
|Linux Foundation Training
|• Issue 802 (2019-02-18): Slontoo 18.07.1, NetBSD tests newer compiler, Fedora packaging Deepin desktop, changes in Ubuntu Studio|
|• Issue 801 (2019-02-11): Project Trident 18.12, the meaning of status symbols in top, FreeBSD Foundation lists ongoing projects, Plasma Mobile team answers questions|
|• Issue 800 (2019-02-04): FreeNAS 11.2, using Ubuntu Studio software as an add-on, Nitrux developing znx, matching operating systems to file systems|
|• Issue 799 (2019-01-28): KaOS 2018.12, Linux Basics For Hackers, Debian 10 enters freeze, Ubuntu publishes new version for IoT devices|
|• Issue 798 (2019-01-21): Sculpt OS 18.09, picking a location for swap space, Solus team plans ahead, Fedora trying to get a better user count|
|• Issue 797 (2019-01-14): Reborn OS 2018.11.28, TinyPaw-Linux 1.3, dealing with processes which make the desktop unresponsive, Debian testing Secure Boot support|
|• Issue 796 (2019-01-07): FreeBSD 12.0, Peppermint releases ISO update, picking the best distro of 2018, roundtable interview with Debian, Fedora and elementary developers|
|• Issue 795 (2018-12-24): Running a Pinebook, interview with Bedrock founder, Alpine being ported to RISC-V, Librem 5 dev-kits shipped|
|• Issue 794 (2018-12-17): Void 20181111, avoiding software bloat, improvements to HAMMER2, getting application overview in GNOME Shell|
|• Issue 793 (2018-12-10): openSUSE Tumbleweed, finding non-free packages, Debian migrates to usrmerge, Hyperbola gets FSF approval|
|• Issue 792 (2018-1203): GhostBSD 18.10, when to use swap space, DragonFly BSD's wireless support, Fedora planning to pause development schedule|
|• Issue 791 (2018-11-26): Haiku R1 Beta1, default passwords on live media, Slax and Kodachi update their media, dual booting DragonFly BSD on EFI|
|• Issue 790 (2018-11-19): NetBSD 8.0, Bash tips and short-cuts, Fedora's networking benchmarked with FreeBSD, Ubuntu 18.04 to get ten years of support|
|• Issue 789 (2018-11-12): Fedora 29 Workstation and Silverblue, Haiku recovering from server outage, Fedora turns 15, Debian publishes updated media|
|• Issue 788 (2018-11-05): Clu Linux Live 6.0, examining RAM consumpion, finding support for older CPUs, more Steam support for running Windows games on Linux, update from Solus team|
|• Issue 787 (2018-10-29): Lubuntu 18.10, limiting application access to specific users, Haiku hardware compatibility list, IBM purchasing Red Hat|
|• Issue 786 (2018-10-22): elementary OS 5.0, why init keeps running, DragonFly BSD enables virtual machine memory resizing, KDE neon plans to drop older base|
|• Issue 785 (2018-10-15): Reborn OS 2018.09, Nitrux 1.0.15, swapping hard drives between computers, feren OS tries KDE spin, power savings coming to Linux|
|• Issue 784 (2018-10-08): Hamara 2.1, improving manual pages, UBports gets VoIP app, Fedora testing power saving feature|
|• Issue 783 (2018-10-01): Quirky 8.6, setting up dual booting with Ubuntu and FreeBSD, Lubuntu switching to LXQt, Mint works on performance improvements|
|• Issue 782 (2018-09-24): Bodhi Linux 5.0.0, Elive 3.0.0, Solus publishes ISO refresh, UBports invites feedback, Linux Torvalds plans temporary vacation|
|• Issue 781 (2018-09-17): Linux Mint 3 "Debian Edition", file systems for SSDs, MX makes installing Flatpaks easier, Arch team answers questions, Mageia reaches EOL|
|• Issue 780 (2018-09-10): Netrunner 2018.08 Rolling, Fedora improves language support, how to customize Kali Linux, finding the right video drivers|
|• Issue 779 (2018-09-03): Redcore 1806, keeping ISO downloads safe from tampering, Lubuntu makes Calamares more flexible, Ubuntu improves GNOME performance|
|• Issue 778 (2018-08-27): GuixSD 0.15.0, ReactOS 0.4.9, Steam supports Windows games on Linux, Haiku plans for beta, merging disk partitions|
|• Issue 777 (2018-08-20): YunoHost 184.108.40.206, limiting process resource usage, converting file systems on Fedora, Debian turns 25, Lubuntu migrating to Wayland|
|• Issue 776 (2018-08-13): NomadBSD 1.1, Maximum storage limits on Linux, openSUSE extends life for 42.3, updates to the Librem 5 phone interface|
|• Issue 775 (2018-08-06): Secure-K OS 18.5, Linux is about choice, Korora tests community spin, elementary OS hires developer, ReactOS boots on Btrfs|
|• Issue 774 (2018-07-30): Ubuntu MATE & Ubuntu Budgie 18.04, upgrading software from source, Lubuntu shifts focus, NetBSD changes support policy|
|• Issue 773 (2018-07-23): Peppermint OS 9, types of security used by different projects, Mint reacts to bugs in core packages, Slackware turns 25|
|• Issue 772 (2018-07-16): Hyperbola GNU/Linux-libre 0.2.4, UBports running desktop applications, OpenBSD auto-joins wi-fi networks, boot environments and zedenv|
|• Issue 771 (2018-07-09): Linux Lite 4.0, checking CPUs for bugs, configuring GRUB, Mint upgrade instructions, SUSE acquired by EQT|
|• Issue 770 (2018-07-02): Linux Mint 19, Solus polishes desktop experience, MintBox Mini 2, changes to Fedora's installer|
|• Issue 769 (2018-06-25): BunsenLabs Helium, counting Ubuntu users, UBports upgrading to 16.04, Fedora CoreOS, FreeBSD turns 25|
|• Issue 768 (2018-06-18): Devuan 2.0.0, using pkgsrc to manage software, the NOVA filesystem, OpenBSD handles successful cron output|
|• Issue 767 (2018-06-11): Android-x86 7.1-r1, transferring files over OpenSSH with pipes, LFS with Debian package management, Haiku ports LibreOffice|
|• Issue 766 (2018-06-04): openSUSE 15, overview of file system links, Manjaro updates Pamac, ReactOS builds itself, Bodhi closes forums|
|• Issue 765 (2018-05-28): Pop!_OS 18.04, gathering system information, Haiku unifying ARM builds, Solus resumes control of Budgie|
|• Issue 764 (2018-05-21): DragonFly BSD 5.2.0, Tails works on persistent packages, Ubuntu plans new features, finding services affected by an update|
|• Issue 763 (2018-05-14): Fedora 28, Debian compatibility coming to Chrome OS, malware found in some Snaps, Debian's many flavours|
|• Issue 762 (2018-05-07): TrueOS 18.03, live upgrading Raspbian, Mint plans future releases, HardenedBSD to switch back to OpenSSL|
|• Issue 761 (2018-04-30): Ubuntu 18.04, accessing ZFS snapshots, UBports to run on Librem 5 phones, Slackware makes PulseAudio optional|
|• Issue 760 (2018-04-23): Chakra 2017.10, using systemd to hide files, Netrunner's ARM edition, Debian 10 roadmap, Microsoft develops Linux-based OS|
|• Issue 759 (2018-04-16): Neptune 5.0, building containers with Red Hat, antiX introduces Sid edition, fixing filenames on the command line|
|• Issue 758 (2018-04-09): Sortix 1.0, openSUSE's Transactional Updates, Fedora phasing out Python 2, locating portable packages|
|• Issue 757 (2018-04-02): Gatter Linux 0.8, the UNIX and Linux System Administration Handbook, Red Hat turns 25, super long term support kernels|
|• Issue 756 (2018-03-26): NuTyX 10.0, Neptune supplies Debian users with Plasma 5.12, SolydXK on a Raspberry Pi, SysV init development|
|• Issue 755 (2018-03-19): Learning with ArchMerge and Linux Academy, Librem 5 runs Plasma Mobile, Cinnamon gets performance boost|
|• Issue 754 (2018-03-12): Reviewing Sabayon and Antergos, the growing Linux kernel, BSDs getting CPU bug fixes, Manjaro builds for ARM devices|
|• Issue 753 (2018-03-05): Enso OS 0.2, KDE Plasma 5.12 features, MX Linux prepares new features, interview with MidnightBSD's founder|
|• Issue 752 (2018-02-26): OviOS 2.31, performing off-line upgrades, elementary OS's new installer, UBports gets test devices, Redcore team improves security|
|• Issue 751 (2018-02-19): DietPi 6.1, testing KDE's Plasma Mobile, Nitrux packages AppImage in default install, Solus experiments with Wayland|
|• Full list of all issues|
|Random Distribution |
rPath Linux was a Linux distribution built with the new Conary distributed software management system. Conary was designed, based on many years of Linux software packaging and distribution development experience, to automate many of the tasks that have made it difficult to build Linux distributions. rPath's mission was to provide system software that was easily tailored to suit unique application needs. rPath Linux, built with the Conary distributed software management system, was not only a distribution in its own right, but also a base technology explicitly designed to enable you to create purpose-built operating system images using the rBuilder Online technology.