| DistroWatch Weekly
|DistroWatch Weekly, Issue 62, 16 August 2004
Welcome to this year's 32nd edition of DistroWatch Weekly. Having survived a power blackout generated by an approaching typhoon, your intrepid web site maintainer has yet more exciting stories for you...
Yellow Dog Bites Back
Apple announced the availability of OS X 10.3.5 on August 10. However, OS X is not the only operating system that can run on the Macintosh, and on August 13 (Friday the 13th) Yellow Dog Linux decided to bite back by releasing version 4.0 RC2. YDL users were no doubt relieved - indeed, they were starting to get rather anxious as approximately 11 months had lapsed since the release of 3.0.1 (the current stable version). According to Yellow Dog developers, the reason for the long delay had much to do with the unsettled state of Red Hat/Fedora, upon which YDL is based. As regular readers of DistroWatch should know, Red Hat has undergone major changes in the past year, moving their product line into the commercial Red Hat Enterprise Linux while spinning off the freebie download version into the rapidly-developing Fedora project.
Yellow Dog Linux is a commercial product sold by Terra Soft Solutions, and the latest version 4.0 is available for download through YDL.net Enhanced (3.01 can can be obtained from free mirrors). Yellow Dog's drawcard is that it is unique among Linux distros - it is the only one designed exclusively to run on Macs (or more accurately, the PowerPC processor). Yes, there are other Linux distros that have been ported to PowerPC (Debian and Gentoo come to mind), plus NetBSD and OpenBSD, but only Yellow Dog has bet the ranch on the Mac architecture. So far the bet has paid off, as YDL has been around for five years now and appears to have the lead among Linux-on-Mac fans. YDL 4.0 RC2 will probably be the last release candidate - Yellow Dog developers are predicting that they'll have the final stable release ready for downloading in about another week.
This is probably as good a place as any for me to ask a question that has been fermenting in the back of my head for awhile. I don't own a Macintosh, but I am curious to know how the Linux/BSD experience on PowerPC stacks up when compared to the Intel x86 world. For those of you who own both a PowerPC and x86 box, what differences do you find when running Linux and/or BSD on these machines? Any advantages/disadvantages between the two? Inquiring minds want to know. And let it be stated that this is just a question, not a troll - I've actually been admiring some of those nice-looking iBooks and PowerBooks that I see in the shopping malls.
New Steganography Tool
In last week's Tips, Tricks and Hints, we discussed steganography, the art and science and hiding text messages in unexpected places (ie. inside of graphic, audio and video files). Now there is a new steganographic tool for hiding top-secret data inside of executable files. Hydan is the brainchild of Rakan El-Khalil, a computer science student at Columbia University in New York. El-Khalil revealed his new creation at CodeCon, a non-commercial IT conference held at a San Francisco nightclub.
The ability to place hidden messages inside of an executable binary is not a trivial accomplishment. In the case of graphic, audio and video files, the hidden text slightly impairs the visual or audio output, but so slightly that it's seldom noticeable. However, executable code is much less forgiving - normally, changing even one byte of binary code is enough to cause a program to crash. Yet Hydan not only manages to allow the binary to run properly, it even manages to contain the hidden payload without changing the executable file's original size. This seemingly impossible task is viable thanks to redundancies in x86 instruction code. That is to say, there are places where two instructions are the same, so it should be possible to replace one of them. However, such redundancies are far less common in executable binaries than in graphic, audio or video files. As a result, Hydan can only hide one byte of a text message in about 110 bytes of executable code. By comparison, other steganography programs such as Outguess can hide one byte of message in 17 bytes of a .jpeg file.
Hydan encrypts messages using the blowfish algorithm with a user-supplied passphrase. Though steganography is mostly used to hide information that some people would rather not share with the world, Hydan has some other functions: it can be used to embed a watermark or a digital signature in an executable file. Hydan is open source and will run on Linux and *BSD, but there is also a version for Windows.
Debian Installer RC1
The new Debian installation program RC1 (Release Candidate 1) for "Sarge" was released on 07 August. Download links can be found here. There is even a review of the new installer over at Linux.com.
It's seldom that publishing an installation program would make headlines, but in the case of Debian it's a monumental event. It has been a long time coming, as work on the installer began about four years ago. Debian "Woody" was released on 19 July, 2002, and many had anticipated that a new installer would be available then, but they were disappointed. The next release of Debian (code-named "Sarge") is anticipated for September, though that is not engraved in stone. The difficulty of creating an easy-to-use installer for Debian has much to do with the fact that Debian runs on 11 different architectures (alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, sparc, s390), and the developers have been adamant that the installation experience should be the same everywhere. This, apparently, is easier said than done.
In terms of packaged software, Debian is the largest of all distros, with over 16,000 packages in the "unstable" branch. However, the number of users actually running "pure" Debian may be much smaller than the super-sized package collection indicates. Rather, many people are using Debian-based distros (Knoppix, Xandros, Lindows, etc) which conveniently are compatible with Debian's monumental package collection.
The reason for this state of affairs is that Debian has long been notorious for its difficult-to-use installation program. Indeed, the current installer is so bad that it has given a significant boost to a whole cottage industry of Debian-based distros which tout "easy installation" as a major drawcard. Just how much the new and much-improved installation program will impact these other Debian-based distros remains to be seen. Of course, there is more to a distro than just its installer (easy-to-use system administration tools, for example).
One thing for certain - with the upcoming release of Sarge and the new installer, this is an exciting time for Debian users.
Linux at the Olympics
Friday the 13th marked the official (if inauspicious) start of the Athen's 2004 Olympics. Spectators can expect to see a lot of running, jumping and hitting balls with various objects - all in all, a very non-geeky event, though we'd venture to guess that some of the athletes have an unconfessed weakness for pizza deliveries.
That having been said, Linux will make a small but significant splash at this year's summer Olympics thanks to the BBC. According to this article, the British Broadcasting Corporation will use Linux to improve the speed and accuracy of rendering real time results. Leading the charge are British techies who have installed a bank of Linux computers at the International Broadcasting Centre (IBC) in Athens. The machines will receive real-time results in XML format, and then use SQL databases to store the data, which will then be piped to Macs running Linux apps that will render 3D graphics.
The Athens Olympics are likely just the first step. Jon Hanford, senior systems analyst at BBC, says that the system is being battle-tested at the Olympics, and if successful will likely be used at future sporting events. So next time you see a gymnast flexing his or her biceps in stunning 3D, remember the Linux developers who made it all possible. Now if we could only get some of those Olympic stars to wear DistroWatch T-shirts...
Linux Trademark Battle - Blasts from the Past
Though now mostly forgotten (if not forgiven), back in the bubble days of 1996, Linux Torvalds (with the help of his friends) fought a year-long legal battle to gain control of the "Linux" trademark. Linus - not being a trademark kind of guy - had neglected to register the name Linux with the US Patent and Trademark Office (USPTO). That proved to be a costly mistake when an individual by the name of William R. Della Croce, Jr. came out of the woodwork and started demanding 10% royalties on sales from businesses marketing Linux products. Della Croce, it seems, had registered the "LINUX" trademark for a computer operating system. This is despite the fact he was not a developer and was in no way associated with Linux. Details of the fiasco are outlined here.
A year later, a legal settlement was reached and Linus regained control of the Linux name. For the young software developer from laid-back Finland, the whole twisted nightmare was a rude introduction to the US legal system. An old article from Linux Journal explains how the case was resolved.
Unfortunately, the more things change, the more they stay the same - now somebody else is trying to register the Linux name (this time in Australia). However, it's unlikely that this case will get very far. Basically, what's happening is that a company calling itself Linux Australia Pty Ltd has been trying to register its name as a trademark, so far unsuccessfully. Australia's answer to the USPTO, IP Australia, has apparently heard of Linux and seems pretty sure that it wasn't invented Down Under. Another complicating factor is the existence of Linux Australia, Inc, an Aussie open-source organization that has been using the name as an unregistered trademark. Linux Australia has gotten in touch with Linux Torvalds and asked him to legally reassert possession of the Linux name. More details of this convoluted story can be found here.
What a world we live in. Before you know it, somebody will start trademarking common everyday English words like "windows" and "outlook".
Crippled XP At Discount Prices
Faced with high software prices, customers in at least some parts of the world have lately been deciding that they can do without Windows XP (or at least legally-licensed copies). Full-priced legal CDs containing Windows XP plus Office carry a combined price tag of nearly US$600. In wealthy countries that may be affordable (for most), but in developing countries it represents months of hard-earned wages. Not surprisingly, many of the non-wealthy decide that their best bet is to run pirated software.
The traditional response from the software industry has been to get their governments (usually the US government) to push, pull and issue dire threats of economic sanctions against the offending country for IPR violations. The traditional response from the offending countries has been fake compliance, with high-profile "crackdown cleanup" campaigns. Photos of seized pirate CDs being incinerated in front of approving Western software execs are front-page news in developing country newspapers. Occasionally they throw a few fake Rolex watches and Gucci handbags into the bonfire as well. After the execs head back to their five-star hotels or the airport, the street vendors unpack their newly-pressed Windows/Office CDs and flog them off to locals and tourists alike for US$2 a piece.
Of course, there is another option - the citizens of developing countries could run open source software. And increasingly, this is what they are choosing to do. Aside from costing nothing and being perfectly legal, they gain a few bonuses - freedom from viruses and "product activation", as well as the chance to cultivate a local pool of programming talent.
After bravely holding prices as high as possible for as long as possible, Microsoft finally decided to blink when sales of Linux went through the roof in Thailand. In order to stem the flood of defections, late last year Microsoft threw in the towel and dropped the price of the Thai edition of WinXP+Office to US$37, which is only about 6% of its former cost. Not surprisingly, the new bargain basement prices did not go unnoticed by other developing nations, and they too started demanding a discount.
Caught between a penguin and a hard place, Microsoft announced last week that, starting from October, it would offer a crippled version of Windows officially called "Windows XP Starter Edition." Unofficially, users are calling it "XP-Lite". Among the great new features it offers are lower-resolution graphics, fewer networking capabilities and reduced multitasking. A Microsoft press release called XP-Lite "a low-cost introduction to the Microsoft Windows XP operating system designed for first-time desktop PC users in developing countries." Aside from Thailand, Indonesia and Malaysia will qualify for the cut-rate deal, and there have been suggestions that Singapore be included too (though it is hardly a "developing country"). Other lucky winners in the software sweepstakes may include China and India, but Microsoft seems as yet undecided about this.
No sooner was the ink dry on the digital announcement than IT research firm Gartner published a report recommending that users "steer away" from the new XP-Lite. The Gartner analysts suggested that users would likely find the disabled features "frustrating", and concluded that the ironic result might actually be to increase piracy of Windows XP and Office.
It remains to be seen whether or not consumers in Asia will prefer XP-Lite or Linux. In Thailand, Linux has already gained an enthusiastic following, and Thai geeks are insisting that they won't be seduced by budget Windows. As others have pointed out, Microsoft's sudden generosity has nothing to do with altruism, but rather competition. If the Linux threat recedes, it's hard to believe that software prices won't rise again. A little competition can be a good thing.
|Released Last Week
A new version of GeeXboX, a Linux-based multimedia player, has been released: "Here
comes again the GeeXboX. This 0.98 edition is a key point in our
roadmap. Indeed, this latter does not really come with many new
features (but some new useful things whenever) but fixes a huge
number of annoying bugs. Most of all, this release will probably be the
last time you see GeeXboX looks like it. We've plan to work harder than
ever to bring you next time a new OS, like you've never seen, still
keeping it as simple to use as it ever been. So just stay tuned :-)" Read the full announcement on the distribution's home page, in French or in English. Download: geexbox-0.98-fr.iso (6.07MB) or geexbox-0.98-en.iso (5.96MB).
K12LTSP 4.1.0 has been released: "K12LTSP
4.1.0 is finally available for your downloading pleasure. This release
was a long time in coming, 144 days since the last release. K12LTSP
4.1.0 is the combination of Fedora Core 2 and LTSP 4.1.
The hard work of these two projects shows in this release, this is the
fastest, most refined release of K12LTSP to date. We owe the Fedora and
LTSP projects a big thank-you." Read the full announcement including the changelog. Download: K12LTSP-4.1.0-disc1.iso (623MB), K12LTSP-4.1.0-disc2.iso (649MB) ,K12LTSP-4.1.0-disc3.iso (649MB), and K12LTSP-4.1.0-disc4.iso (621MB).
tinysofa classic server 1.1
tinysofa classic server 1.1 (Rio) is now generally available. "Rio
overhauls the tinysofa classic server product line, adding Native POSIX
Threads Library support to the kernel and glibc, Exec-Shield support to
the kernel, replacing the SWUP updater with APT as the primary advanced
package management tool, designating vsftpd as the only FTP server
shipped, adding dovecot and tftp to the base package set, implementing
'thought process compatibility' with the tinysofa enterprise server
product line and much more." Download: Rio.i586.iso (356MB) and Rio.src.iso (324MB) via BitTorrent. Md5sums can be found on traditional FTP sites.
tinysofa enterprise server 2.0
tinysofa enterprise server 2.0 (Odin) is now generally available. "Odin
is a next generation operating system which showcases the latest in
open source technology in a fast, stable, securely configured and
easily manageable form. Odin features: The Linux 2.6.8 kernel, SELinux
support, APT as an advanced package management tool, a turn key ASP.NET
solution using components from the Mono project, the next generation
PHP 5 environment, high availability features such as DRBD, UCARP and
PostgreSQL replication, the latest development tools and languages" including automake 1.9, bash 3.0 and tcl 8.4.7! Download: Odin.i386.iso (691MB) and Odin.src.iso (703MB) via BitTorrent. Md5sums can be found on traditional FTP sites.
blackPanther OS 4.0
(formerly known as blackPanther-Linux) is a Hungarian Linux
distribution based on Mandrakelinux. Version 4.0 of blackPanther has
been released: "First CD there is ISO format, other 4CDs only in FTP, source and RPM format available." If you understand Hungarian you can read the full announcement here. Download: CD1-blackPanther4.0final.iso (527MB).
A new version of the Inside Security Rescue Toolkit INSERT has been released. From the changelog: "v1.2.14
(the one-year-anniversary release). Bugfix: libpcap0.8 was missing (for
tcpdump). The following packages/programs were updated: fwlogwatch,
clamav, avscan, smbmount, rkhunter; p0f - a passive OS fingerprinting
tool was added; the ability to create boot floppies (mkfloppy.bat and
mkfloppy.sh was removed (the files didn't fit on a floppy anymore, this
should be re-added ASAP); a bug with the 'toram' boot option was fixed.
Now all files are being copied to the RAM disk...." Download from here: INSERT-1.2.14_de.iso (49.0MB) or INSERT-1.2.14_en.iso (49.0MB).
Development and unannounced releases
DistroWatch database summary
- Number of Linux distributions in the database: 315
- Number of BSD distributions in the database: 7
- Number of discontinued distributions: 32
- Number of distributions on the waiting list: 84
|Tips, Tricks and Hints
Steganography provides a useful way to secure your bank account or credit card numbers, but it's not really a practical form of encryption if you've got a large quantity of data to conceal. If, for example, you're a politician and you've got hundreds (or thousands) of incriminating emails that you'd like to keep secret, trying to bury them one at a time inside of your family digital photo album would be a painstaking task to say the least (and it would be equally painstaking trying to retrieve the data, or search through it). Aside from that, some of the data you wish to hide may include naughty photos or videos, and steganography wouldn't be of much help since it's designed for hiding text.
The solution to this problem is to place all the scandalous files on an encrypted partition. A clever algorithm and a passphrase are used to encrypt the partition. This is a nearly bulletproof solution, but be forewarned that if you forget the passphrase, you can kiss the data goodbye unless you've backed it up to someplace else in an unencrypted format.
Linux provides two unrelated packages for making encrypted partitions, Cryptoloop and loop-AES (note that these are Linux-only - the BSDs have their own separate encryption schemes). However, it's been claimed that Cryptoloop has certain weaknesses, and it was recently discussed on Kerneltrap that Cryptoloop was being replaced with dm-crypt in the 2.6 kernel. For that reason and others, this article will focus on loop-AES.
Unfortunately, installing loop-AES is not as simple as grabbing an RPM or source tarball - it requires a kernel module and patched util-linux. More devout geeks may rise to the challenge, but it's a complicated mess and I'm not going to cover how to do it in this brief article. The good news is that more and more distros are including loop-AES by default - if your distro doesn't, give the developers some pressure to do so. In my opinion, it's a killer feature, and every desktop distro should have it.
The easiest way to find out if you've got loop-AES installed is to search for the loadable Linux kernel module "loop.o" on 2.4 kernels, or "loop.ko" on 2.6 kernels. An easy way to do this is with the "locate" command. If you're unfamiliar with "locate", note that it depends on a database that you create first create by running "updatedb" (you must be root to do so). You only need to run "updatedb" just once, though you may want to run it periodically (once a week) to rebuild the database as the files on your computer change. Most Linux systems will run "updatedb" as a weekly cron job, but that won't necessarily work if your computer isn't turned on just after midnight. Anyway, run "locate loop.o loop.ko" - here are the results that I obtained:
locate loop.o loop.ko
As you can see, I have the necessary modules, so I'm in business. I'm running Knoppix 3.4, and I've also found the drivers on recent versions of Xandros, Mepis and Libranet. I have Slackware on one on my hard disk partitions, and it does not have loop-AES enabled by default. I have not checked the other 310 distros that are in the DistroWatch database (this is not a feature we normally monitor, but maybe we should). I'd be very interested in hearing from others to learn whether or not loop-AES is enabled in their favorite distros.
At this point, it's worth pointing out that there are two ways to use loop-AES. One way is take an unused partition on our hard drive (perhaps /dev/hda3) and encrypt it. The other way is just to make an encrypted BIGFILE and place it on a partition that we are already using. With this in mind, let's get down to the actual details.
You need a spare partition if you want to encrypt it because all the data will be destroyed. If you aren't already intimately familiar with your partition table, there are a few tools which will let you peek at it. One is "sfdisk" - you must be root to run it, and it's a dangerous tool if you start monkeying around with all it's capabilities, so just stick to the "-l" option. Read the sfdisk man page if you want to know more, otherwise, as root do the following:
Disk /dev/hda: 4865 cylinders, 255 heads, 63 sectors/track
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 13562- 13563- 6835626 a6 OpenBSD
/dev/hda2 13562+ 42632- 29070 14651280 a5 FreeBSD
/dev/hda3 42632+ 43604 973- 489982+ 82 Linux swap
/dev/hda4 43605 77544 33940 17105760 5 Extended
/dev/hda5 43605+ 55223- 11619- 5855661 83 Linux
/dev/hda6 55223+ 61040- 5818- 2931831 83 Linux
/dev/hda7 61041+ 77544 16504- 8317984+ 83 Linux
As you can see from the above, /dev/hda1 and /dev/hda2 are occupied by OpenBSD and FreeBSD respectively, so let's forget those. I had originally hoped to use /dev/hda3, but I see that's it's occupied as my swap partition, so that's out too. My /dev/hda4 is an "extended partition" - never mess with that. The only possible candidates are /dev/hda5, /dev/hda6 and /dev/hda7. But wait, I might be using those too - better check with the "df -h" command:
Filesystem Size Used Avail Use% Mounted on
/dev/hda7 7.9G 3.1G 4.4G 42% /
/dev/root.old 17M 7.9M 8.3M 49% /initrd
/dev/hda6 2.8G 546M 2.1G 21% /home
Good thing I checked - /dev/hda7 is my root partition, and /dev/hda6 is /home. So the only spare partition I've got is /dev/hda5. Actually, I've got an old Linux distro installed there, but it's not important so I'm going to nuke it. We will use the losetup command, which is used to set up and control loop devices. So, without further ado:
losetup -e AES128 -T /dev/loop0 /dev/hda5
This command will link /dev/hda5 to the first virtual peripheral /dev/loop0. You will be asked to enter a password - 20 characters or more is recommended. Once you've done that, create an ext2 filesystem on /dev/loop0:
mkfs -t ext2 /dev/loop0
Now we must detach the partition from the specified loop device:
losetup -d /dev/loop0
Now, create a new directory which will be used to mount this partition:
The last step is to edit file /etc/fstab. Before you do this, make a backup copy (a wise move whenever you edit an important system configuration file:
cp /etc/fstab /etc/fstab.original
OK, go ahead and add this line to /etc/fstab:
/dev/hda5 /sleaze ext2 defaults,noauto,loop=/dev/loop0,encryption=AES128 0 0
Now you may mount /dev/hda5 to /sleaze whenever you like (you'll need to be root to do that, or else set up sudo). Anytime you attempt to mount it, you'll be asked for the password (not the root password, but that big long 20-character password which you'd better not forget). Whenever the partition is not mounted, the data will be inaccessible, and thus safe from prying eyes.
Finally, note that my encrypted partition could have been placed on a removable device such as a USB card or keyring (/dev/sda1) or even on a floppy (/dev/fd0), but not a CDR.
As already mentioned, loop-AES can be used to create an encrypted BIGFILE rather than an encrypted partition. The main advantage is that you won't need a spare partition on your hard drive. From what I've read, you should be able to back up the BIGFILE to a CDR, but I have not had much luck with this.
For the purpose of this experiment, I'll create a 100MB BIGFILE. Before I begin, let's see how much empty space I have available on my mounted partitions. This is best done with the "df -h" command:
/dev/hda7 7.9G 2.5G 5.0G 34% /
/dev/root.old 17M 7.9M 8.3M 49% /initrd
/dev/hda6 2.8G 546M 2.1G 21% /home
I've got more space in my "/" partition than anyplace else, so I could put my BIGFILE in /root, or create a new user in /home and put in there. Since it will require root privileges to access anyway, I'll put it in /root but there is no reason why I must. I need to perform the following steps to create my BIGFILE and set it up as a loop device:
dd if=/dev/zero of=/root/BIGFILE bs=4k count=2560
losetup -e AES128 -T /dev/loop1 /root/BIGFILE
mkfs -t ext2 /dev/loop1
losetup -d /dev/loop1
You can do all of the above without any explanation, but most of you would probably like to know what's going on. The math in the first line: "bs" means "block size" and "count" means "how many blocks". Always use a block size of 4k, but you can vary the count according to the size you want the encrypted file to be: "4k x 256 = 1024k" which is 1MB, but I want 10MB so I multiply 256 times 10 to get 2560.
Also note above that I used "/dev/loop1", not /dev/loop0 - the only reason for this is that I've already populated /dev/loop0 with the encrypted partition I created earlier. Yes, you can indeed have both an encrypted partition and an encrypted BIGFILE at the same time. In fact, you can have up to eight encrypted partitions and/or BIGFILEs (/dev/loop0 to /dev/loop7).
Finally, I add a line to /etc/fstab so that I can mount /root/BIGFILE onto its mount point /secret:
/root/BIGFILE /secret ext2 defaults,noauto,loop=/dev/loop1,encryption=AES128 0 0
It only remains for me to mount the encrypted BIGFILE:
Ideally, it would be nice if I could back up the encrypted data to a CDR (while still keeping it encrypted). Articles I've read indicate that BIGFILE could be burned to a CDR, but my own experiments with this failed. I'd be interested if others have been more successful. However, backing up to my removable USB hard drive worked just fine.
That's all for this week.
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 0, value: US$0.00)
|Linux Foundation Training
|• Issue 717 (2017-06-19): SharkLinux, combining commands in the shell, Debian 9 flavours released, OpenBSD improving kernel security, UBports releases first OTA update|
|• Issue 716 (2017-06-12): Slackel 7.0, Ubuntu working with GNOME on HiDPI, openSUSE 42.3 using rolling development model, exploring kernel blobs|
|• Issue 715 (2017-06-05): Devuan 1.0.0, answering questions on systemd, Linux Mint plans 18.2 beta, Yunit/Unity 8 ported to Debian|
|• Issue 714 (2017-05-29): Void, enabling Wake-on-LAN, Solus packages KDE, Debian 9 release date, Ubuntu automated bug reports|
|• Issue 713 (2017-05-22): ROSA Fresh R9, Fedora's new networking features, FreeBSD's Quarterly Report, UBports opens app store, Parsix to shut down, SELinux overview|
|• Issue 712 (2017-05-15): NixOS 17.03, Alpha Litebook running elementary OS, Canonical considers going public, Solus improves Bluetooth support|
|• Issue 711 (2017-05-08): 4MLinux 21.0, checking file system fragmentation, new Mint and Haiku features, pfSense roadmap, OpenBSD offers first syspatch updates|
|• Issue 710 (2017-05-01): TrueOS 2017-02-22, Debian ported to RISC-V, Halium to unify mobile GNU/Linux, Anbox runs Android apps on GNU/Linux, using ZFS on the root file system|
|• Issue 709 (2017-04-24): Ubuntu 17.04, Korora testing new software manager, Ubuntu migrates to Wayland, running Nix package manager on alternative distributions|
|• Issue 708 (2017-04-17): Maui Linux 17.03, Snaps run on Fedora, Void adopts Flatpak, running Android apps on GNU/Linux, Debian elects Project Leader|
|• Issue 707 (2017-04-10): PCLinuxOS 2017.03, Canonical stops Unity development, OpenBSD on a Raspberry Pi, setting up a VPN for privacy|
|• Issue 706 (2017-04-03): Super Grub2 Disk, Snap packages of deepin applications, Subgraph OS routes network traffic for one application, announcements from Linux Mint|
|• Issue 705 (2017-03-27): Minimal Linux Live, sharing control of the operating system, new KaOS features, Uplos32 provides 32-bit fork of PCLinuxOS|
|• Issue 704 (2017-03-20): ToarusOS 1.0.4, Linux Mint's security record, Debian starts Project Leader election, Ubuntu 12.04 reaches end-of-life|
|• Issue 703 (2017-03-13): SolydXK 201701, CloudReady, Solus announces new features, KDE Connect sends text messages from desktop, openSUSE's YaST module for Let's Encrypt|
|• Issue 702 (2017-03-06): Fatdog64 Linux, elementary OS bundled with new netbook, Haiku announces new features, security and the size of a distro's development team|
|• Issue 701 (2017-02-27): OBRevenge 2017.02, Mageia 6 delays, NetBSD reproducible builds, questions about swap space, trying to steam video on a Raspberry Pi|
|• Issue 700 (2017-02-20): RaspBSD, Debian replaces Icedove with Thunderbird, Fedora's licensing guidlines, tips for switching shells, finding battery charge, getting IP address and killing processes|
|• Issue 699 (2017-02-13): Clear Linux, GhostBSD network utility ported to FreeBSD, Ubuntu coming to Fairphone, elementary OS crowd funding an app store|
|• Issue 698 (2017-02-06): Solus 2017.01.01, comparing containers with portable applicatins, Tails dropping 32-bit support, Debian Stretch enters freeze|
|• Issue 697 (2017-01-30): Subgraph OS 2016.12.30, running Ubuntu on an Android phone, Arch Linux phasing out 32-bit support, Linux Mint testing updated LMDE media|
|• Issue 696 (2017-01-23): GoboLinux 016, remotely running desktop applications, Solus adopting Flatpak, KDE neon using Calamares, TrueOS tests OpenRC|
|• Issue 695 (2017-01-16): Zorin OS 12, Peppermint team fixes installer bug, Debian refreshes Jessie media, Ubuntu improves low graphics mode, Exciting things coming in 2017|
|• Issue 694 (2017-01-09): MX Linux 16, Fedora considers systemd security features, DragonFly BSD to support massive swap space, Ubuntu Touch roadmap, Puppy's newsletter, sudo's password prompt|
|• Issue 693 (2017-01-02): Comparing small distros, fig language, video driver comparsion, Debian+PIXEL, Wayland on FreeBSD|
|• Issue 692 (2016-12-19): Bodhi Linux 4.0.0, Cappsule containers, Calculate's new Utilities package, Solus and Ubuntu MATE build new application menu|
|• Issue 691 (2016-12-12): SalentOS 1.0, openSUSE improves YaST, Fedora considers slower release cycle, KDE neon gets LTS branch|
|• Issue 690 (2016-12-05): Fedora 25, Ubuntu adopts rolling HWE kernel, running Android apps on GNU/Linux, Haiku working toward EFI support|
|• Issue 689 (2016-11-28): openSUSE 42.2, Fedora's upgrade path, plans for Korora 25, transitioning from PC-BSD to TrueOS, Webconverger's reproducible builds|
|• Issue 688 (2016-11-21): Endless OS 3.0.5, KDE neon fixes security hole, FreeBSD's Quarterly Status Report, Rolling release trial #2 concludes|
|• Issue 687 (2016-11-14): NAS4Free 10.3.0.3, Fedora gains MP3 playback, budgie-remix becomes Ubuntu Budgie, Ubuntu flavours compared, Rolling release trial #2|
|• Issue 686 (2016-11-07): FreeBSD 11.0, rolling release trial #2, Debian announces supported architectures, Simplicity switching to antiX base, farewell to Mythbuntu|
|• Issue 685 (2016-10-31): elementary OS 0.4, SUSE gains ARM support, Mint improves language support, Dirty COW explained, Rolling release trial #2|
|• Issue 684 (2016-10-24): Ubuntu 16.10, Linux popularity in different markets, Fedora runs on Raspberry Pi, Ubuntu features live kernel patching|
|• Issue 683 (2016-10-17): Refracta 8.0, making packages for distributions, Alpine switches to LibreSSL, 386BSD website publishes classic code|
|• Issue 682 (2016-10-10): KDE neon 20160915, Android-x86 6.0, Fedora warns of update bug, HandyLinux drops English translation, LXQt benchmarks|
|• Issue 681 (2016-10-03): OpenBSD 6.0, DragonFly BSD to support LibreSSL in ports, systemd denial of service bug, upgraded Mintbox Mini|
|• Issue 680 (2016-09-26): Uruk GNU/Linux 1.0, blocking applications at the firewall, Lenovo controversy, Ubuntu running on the Nextcloud Box|
|• Issue 679 (2016-09-19): OpenMandriva 3.0, 32-bit vs 64-bit performance, openSUSE updates, KaOS unveils first run wizard|
|• Issue 678 (2016-09-12): Apricity 07.2016, Mageia adopts DNF, KDE neon to use Wayland, FreeBSD updates Linux compatibility, creating cron jobs|
|• Issue 677 (2016-09-05): Peppermint OS 7, Manjaro updates leadership, TrueOS becomes rolling release, organizing files, creating torrents|
|• Issue 676 (2016-08-29): Korora 24, Fedora 25 to use Wayland by default, Linux turns 25, PC-BSD becomes TrueOS, finding software licensing information|
|• Issue 675 (2016-08-22): Gentoo LiveDVD "Choice Edition", moreutils, Ubuntu improves terminal convergence, MATE packaged for Openindiana, FreeBSD improves video support|
|• Issue 674 (2016-08-15): Zenwalk Linux 8.0, Ubuntu phone follow-up, Lubuntu transitioning to LXQt, Steam running on FreeBSD|
|• Issue 673 (2016-08-03): noop linux and EasyNAS, Debian's GnuPG switch, Fedora "Flock", using "nice"|
|• Issue 672 (2016-08-01): Ubuntu Phone 15.04, Solus embraces rolling release model, interview with Jane Silber, FreeBSD Quarterly Report|
|• Issue 671 (2016-07-25): Slackware 14.2, Point Linux 3.2, OpenBSD disables usermount, KaOS releases significant changes, Fedora 22 reaches end of life.|
|• Issue 670 (2016-07-18): Linux Lite 3.0, Bodhi team plans 4.0.0, pfSense changes licensing, running software across distributions, Linux Mint upgrade path|
|• Issue 669 (2016-07-11): Linux Mint 18, proving a system is secure, LibreSSL in FreeBSD, Ubuntu plans phasing out 32-bit, pfSense status report|
|• Issue 668 (2016-07-04): Fedora 24, Linux Mint plans for 18.1, FreeBSD and DragonFly BSD improve their file systems, comparing Flatpak, Snap and AppImage|
|• Issue 667 (2016-06-27): GeckoLinux 421, Fedora supports Flatpak, Solus unveils new features, running GNU/Linux on tablets|
|• Issue 666 (2016-06-20): Comparing more live update methods, Ubuntu's snap packages, Antergos drops 32-bit media, GeckoLinux unveils Rolling edition, learning Linux resources|
|• Full list of all issues|