Language Selection

English French German Italian Portuguese Spanish

Underground Desktop 021 - it rocks!

Yes, I am really excited about this one! Underground Desktop 021 might be an early development version, but it already works very well, and that despite using some really cutting edge features: Reiser4 as the only filesystem, KDE 3.5 as the only desktop, and the kernel is 2.6.14 with archck patchset. (Archck includes Con Kolivas' patches, plus support for a few new filesystems, for example Reiserfs4 and shfs, and a few other bits).

Underground is based on Arch Linux and it inherits all that is great about Arch - pacman for package management, optimisation for i686 architecture, and above all, my personal favourite: Arch's beautiful, simple and effective rc.config holding most of system settings.

Underground adds its own installer, which is very, very simple. Perhaps even too simple, because the only choice the user gets to make is the root password (and creating two partitions with cfdisk). Beware, Underground *will* install its Lilo in MBR, no questions asked! I believe Lilo is neccessary, because Grub has trouble booting Reiser4 partitions, and Underground uses Reiser4 whether you like that or not - no other choices are offered. I would also like to be able to add a non-root user during the installation, but that option is missing as well. However, it was easy enough to add a user later, with KDE user manager. Underground did a great job configuring my display, and initially got the network settings with DCHP. Again, it was simple to change them to static IP I wanted with KDE tools. The desktop includes a link to short, but useful Post Install Notes which mentions setting up the network as well as several useful steps required to bring the system up to speed in the multimedia department because video codecs, flash and Java are not installed by default. But they are easy to add with pacman, no other work required.

I am not usually too worried about booting speed, but I couldn't help noticing Underground gets from Lilo to the login screen remarkably quickly, even on my rather obsolete system (AMD 800Mhz, 256 Mb of RAM). From that point on, starting KDE does take a while, though my system might be to blame for that. In fact I think the booting process could be speeded up even further by disabling hardware detection and loading required modules through config files instead, but I don't think I will bother - it is quite fast enough for me.

This is an early development version, and there are some small glitches here and there. Initial installation had very ugly and jaggy fonts, but apparently the fix was already available, because running pacman -Syu fixed the problem before I had a chance to go on the forum to ask about it. I also noticed virtual consoles seem absent. And I would like more choices in KDM login screen - such as the menu to shutdown/reboot, and to select other window managers (KDE is the only choice out of the box, but I think there is E17 available in the repos, I still have to investigate this more closely).

But this really nitpicking for any system, let alone the second development version! I think Underground Desktop is quite amazing and I hope it will become more popular. In my book it fully deserves one of top spots on Distrowatch Smile

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.


I tried to install 020 to review, but the installer had problems. I saw on the forum where the developer said the bug seemed to be show up on systems with 2 hard drive installed. But when removing one, the installer hung at another spot soon after.

Yeah, I saw where he was gonna push out an updated version soon. I downloaded it and was gonna try to get to it this weekend. I'm so behind, what with having to work for a living and all. Tongue

The one I did review was pretty nice, but that was back when it was still based on Debian. I never find a reason why they decided to switch to arch.

Glad you liked it and thanks for the mini review.

You talk the talk, but do you waddle the waddle?

More in Tux Machines

Leftovers: BSD

Security Leftovers

  • Stop using SHA1 encryption: It’s now completely unsafe, Google proves
    Security researchers have achieved the first real-world collision attack against the SHA-1 hash function, producing two different PDF files with the same SHA-1 signature. This shows that the algorithm's use for security-sensitive functions should be discontinued as soon as possible. SHA-1 (Secure Hash Algorithm 1) dates back to 1995 and has been known to be vulnerable to theoretical attacks since 2005. The U.S. National Institute of Standards and Technology has banned the use of SHA-1 by U.S. federal agencies since 2010, and digital certificate authorities have not been allowed to issue SHA-1-signed certificates since Jan. 1, 2016, although some exemptions have been made. However, despite these efforts to phase out the use of SHA-1 in some areas, the algorithm is still fairly widely used to validate credit card transactions, electronic documents, email PGP/GPG signatures, open-source software repositories, backups and software updates.
  • on pgp
    First and foremost I have to pay respect to PGP, it was an important weapon in the first cryptowar. It has helped many whistleblowers and dissidents. It is software with quite interesting history, if all the cryptograms could tell... PGP is also deeply misunderstood, it is a highly successful political tool. It was essential in getting crypto out to the people. In my view PGP is not dead, it's just old and misunderstood and needs to be retired in honor. However the world has changed from the internet happy times of the '90s, from a passive adversary to many active ones - with cheap commercially available malware as turn-key-solutions, intrusive apps, malware, NSLs, gag orders, etc.
  • Cloudflare’s Cloudbleed is the worst privacy leak in recent Internet history
    Cloudflare revealed today that, for months, all of its protected websites were potentially leaking private information across the Internet. Specifically, Cloudflare’s reverse proxies were dumping uninitialized memory; that is to say, bleeding private data. The issue, termed Cloudbleed by some (but not its discoverer Tavis Ormandy of Google Project Zero), is the greatest privacy leak of 2017 and the year has just started. For months, since 2016-09-22 by their own admission, CloudFlare has been leaking private information through Cloudbleed. Basically, random data from random sites (again, it’s worth mentioning that every site that used CloudFlare in the last half year should be considered to having fallen victim to this) would be randomly distributed across the open Internet, and then indefinitely cached along the way.
  • Serious Cloudflare bug exposed a potpourri of secret customer data
    Cloudflare, a service that helps optimize the security and performance of more than 5.5 million websites, warned customers today that a recently fixed software bug exposed a range of sensitive information that could have included passwords and cookies and tokens used to authenticate users. A combination of factors made the bug particularly severe. First, the leakage may have been active since September 22, nearly five months before it was discovered, although the greatest period of impact was from February 13 and February 18. Second, some of the highly sensitive data that was leaked was cached by Google and other search engines. The result was that for the entire time the bug was active, hackers had the ability to access the data in real-time by making Web requests to affected websites and to access some of the leaked data later by crafting queries on search engines. "The bug was serious because the leaked memory could contain private information and because it had been cached by search engines," Cloudflare CTO John Graham-Cumming wrote in a blog post published Thursday. "We are disclosing this problem now as we are satisfied that search engine caches have now been cleared of sensitive information. We have also not discovered any evidence of malicious exploits of the bug or other reports of its existence."

Security Leftovers

  • Change all the passwords (again)
    Looks like it is time to change all the passwords again. There’s a tiny little flaw in a CDN used … everywhere, it seems.
  • Today's leading causes of DDoS attacks [Ed: The so-called 'Internet of things' (crappy devices with identical passwords) is a mess; programmers to blame, not Linux]
    Of the most recent mega 100Gbps attacks in the last quarter, most of them were directly attributed to the Mirai botnet. The Mirai botnet works by exploiting the weak security on many Internet of Things (IoT) devices. The program finds its victims by constantly scanning the internet for IoT devices, which use factory default or hard-coded usernames and passwords.
  • How to Set Up An SSL Certificate on Your Website [via "Steps To Secure Your Website With An SSL Certificate"]
  • SHA-1 is dead, long live SHA-1!
    Unless you’ve been living under a rock, you heard that some researchers managed to create a SHA-1 collision. The short story as to why this matters is the whole purpose of a hashing algorithm is to make it impossible to generate collisions on purpose. Unfortunately though impossible things are usually also impossible so in reality we just make sure it’s really really hard to generate a collision. Thanks to Moore’s Law, hard things don’t stay hard forever. This is why MD5 had to go live on a farm out in the country, and we’re not allowed to see it anymore … because it’s having too much fun. SHA-1 will get to join it soon.
  • SHA1 collision via ASCII art
    Happy SHA1 collision day everybody! If you extract the differences between the good.pdf and bad.pdf attached to the paper, you'll find it all comes down to a small ~128 byte chunk of random-looking binary data that varies between the files.
  • PayThink Knowledge is power in fighting new Android attack bot
    Android users and apps have become a major part of payments and financial services, carrying an increased risk for web crime. It is estimated that there are 107.7 million Android Smartphone users in the U.S. who have downloaded more than 65 million apps from the Google App Store, and each one of them represents a smorgasbord of opportunity for hackers to steal user credentials and other information.
  • Red Hat: 'use after free' vulnerability found in Linux kernel's DCCP protocol IPV6 implementation
    Red Hat Product Security has published details of an "important" security vulnerability in the Linux kernel. The IPv6 implementation of the DCCP protocol means that it is possible for a local, unprivileged user to alter kernel memory and escalate their privileges. Known as the "use-after-free" flaw, CVE-2017-6074 affects a number of Red Hat products including Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and Red Hat Openshift Online v2. Mitigating factors include the requirement for a potential attacker to have access to a local account on a machine, and for IPV6 to be enabled, but it is still something that will be of concern to Linux users. Describing the vulnerability, Red Hat says: "This flaw allows an attacker with an account on the local system to potentially elevate privileges. This class of flaw is commonly referred to as UAF (Use After Free.) Flaws of this nature are generally exploited by exercising a code path that accesses memory via a pointer that no longer references an in use allocation due to an earlier free() operation. In this specific issue, the flaw exists in the DCCP networking code and can be reached by a malicious actor with sufficient access to initiate a DCCP network connection on any local interface. Successful exploitation may result in crashing of the host kernel, potential execution of code in the context of the host kernel or other escalation of privilege by modifying kernel memory structures."

Android Leftovers