Language Selection

English French German Italian Portuguese Spanish

BlueWhite64 Linux pre-11.0-beta

Filed under
Linux
Reviews
-s

Bluewhite64 is an unofficial port of the world famous Slackware Linux distribution built and optimized for the x86_64 architecture. When I first heard of bluewhite64 I was quite anxious to test it. With the release of pre-11.0-beta on July 3rd this seemed like the perfect time.

As stated, pre-11.0-beta was available at the time of our testing and downloading was swift. md5sums checked out and the install went well. The installer is the exact same installer found in Slackware as far as I can see. There may have been some differences in the available packages, but otherwise it contained the same steps presented in the familiar Slackware installer. It does stop during package install and ask for the 2nd cd, then precedes.

First boot went like clockwork as well. The only errors listed were insignificant or concerning extraneous aspects, such as chown /proc/usb/001/002 fails because it didn't exist. I say insignificant because the usb peripherals worked fine. An xorg configuration file is present, if a bit on the conservative side, and a "startx" brings up the KDE 3.5.3 desktop (if chosen as default during install).

The KDE 3.5.3 desktop is a complete but default environment. It sits in xorg 6.9.0 and comes with gcc 3.4.6 and all the KDE applications available from the KDE developers. They are listed as per usual in KDE structured menus. Every application tested seemed to function as designed here except krita that was listed in the menu but would not open. Kooka did fine with my detected and autoconfigured scanner. Also among the full compliment of Kapps is The GIMP.

        

There existed a kernel bug that affects sound and nvidia driver installation, so I headed on over to kernel.org, downloaded linux-2.6.17.2, and built it using Bluewhite's configuration file as a starting point. Not present (or overlooked on my part) in /usr/src/linux-2.6.16.22, but found as /boot/config-generic-2.6.16.22. cp /boot/config-generic-2.6.16.22 /usr/src/linux-2.6.17.2/.config and then make menuconfig. One could probably skip the menuconfig and just do a make oldconfig if they didn't wish to take out a lot of the support developers include for a wider user-base. Kernel configurations can be a bit scary to a new user, but as you go through the menus, you know your sound card or graphics chip. My advice in this case to new users is to not mess with the filesystems, net stuff, block devices, or anything that sounds greek to you. But there's no reason you can uncheck all the hardware you know you don't have. After the configuration (menuconfig), just type make. Next, type make modules_install. The next step might require some thought, but most people can just type make install and boot their new kernel.

        

At that point I had working sound and not only did arts stop complaining, but my multimedia applications blared to life. BlueWhite64 comes with Juk, Amarok, and KsCD for your musical inclinations as well as gxine, noatun, and kaboodle for your viewing pleasure. It also has KAudioCreator for cdripping. I had no trouble with audio cds, avis, or mpegs.

        

Browsing can be handled through Seamonkey 1.0.2, Firefox 1.5.0.4, or Konqueror 3.5.3. Also included, but perhaps not seen in the menu are lynx and links. The browsers function really well and the fonts look good, but there is no flash or java included. Other net apps include gaim, Pan, Thunderbird, NmapFE, gFTP, and XChat.

        

Office applications are handled in the most part by Koffice.

        

If KDE is not your favorite, you also have the choice of xfce4 4.2.3.2. Like KDE it is found in almost its default configuration.

    

All in all it was a good system. It was an easy install and required no configuration (subsequent releases will probably not need the user to upgrade the kernel), although I did tweak my xorg.conf. My usb devices worked out of the box and sound came right up after the kernel upgrade without further configuration. The included apps make for a wonderful foundation and most are of the latest release. The stability wasn't compromised for these bleeding edge improvements. No application or system crashes occurred. However, I didn't notice an amazing speed increase. It seemed to be a bit faster, but not as I imagined. This may be in part to my choice of filesystem. I chose ext3 while the installer seemed to want to default to xfs. Perhaps choosing reiserfs or xfs would have made a difference. Don't get me wrong, there was no delay in any menu operations or window repainting and apps opened promptly enough. It just didn't leave any burn marks as experienced with kubuntu.

If you'd like to try BlueWhite64, it can be downloaded from one of the mirrors listed here. You can keep abreast of developments at BlueWhite64's homepage here. If you are a fan of Slackware and have a 64 bit machine, you owe it to yourself to give Bluewhite64 a try.

Can we have ONE review without an Ubuntu reference?

In any case... when I upgrade my lappy to a Turion, I'm definitely doing this. Hopefully, I can finally create that 64-bit Slackware-based livecd I've been talking about.

re: ubuntu reference

<scoffs> Why Noooo! You should know better than that. Silly you! Big Grin

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

Comment viewing options

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

More in Tux Machines

Netrunner Rolling 2019.04 released

Like its cousin, the Debian based version, Netrunner Rolling also ships a dark Look and Feel theme including the Kvantum theme engine. Using the Kvantum Theme engine plus the Alpha-Black Plasma Theme allowed us to create a more 3D-looking design. Moving the mouse into the lower right corner now visibly activates the “Minimize all Windows to show Desktop” function by a light glow. For those who prefer the classic look, going back to the well-known LNF is a three-button click and explained under “Tips” in our current Readme Section. Read more Also: Debian-Based Netrunner Linux Gets April 2019 Release with New Look and Feel

Android Leftovers

Server: Cloudwashing by SUSE and Openwashing by Red Hat

  • Why Hybrid Cloud is About to Get a Whole Lot Easier
    It seems like analysts, vendors and IT decision makers have been talking about “hybrid cloud” for the longest time. The concept has been around for at least a decade – and that’s a really long time in the IT industry. Is it still important? Absolutely. Almost every piece of cloud market research I read shows the majority of enterprises are focusing on a hybrid cloud strategy. Why? Because they all need increased agility, innovation and productivity, better cost optimization and improved customer experience.
  • The Open Organization guide to Red Hat Summit 2019 [Ed: The 'Open Organization' slant in Red Hat Summit 2019 with Microsoft CEO as keynote because it's all about money, not "open" or "free" (just proprietary and expensive]
    When Red Hat CEO Jim Whitehurst published The Open Organization in 2015, he didn't just release a book. He catalyzed a global conversation about the ways open principles are reshaping organizational culture and design.
  • Developing distributed applications and services for tomorrow: a proof of concept
    Innovation is accelerating across the automobile industry, bringing advances in the in-vehicle experience. Connected vehicle technologies are opening up new business models and providing a whole range of new software and data-driven services. When it comes to new software and data-driven services, the possibilities are immense. But there is one trend many use cases have in common: they are becoming more distributed. To provide a great user experience, connected in-vehicle services often need to integrate increasingly diverse data.

Security: Updates, One Year With Spectre, Purism Librem Key and Lanner’s 'Security Appliances' With Back-Doored Chips

  • Security updates for Tuesday
  • A year with Spectre: a V8 perspective
    On January 3, 2018, Google Project Zero and others disclosed the first three of a new class of vulnerabilities that affect CPUs that perform speculative execution, dubbed Spectre and Meltdown. Using the speculative execution mechanisms of CPUs, an attacker could temporarily bypass both implicit and explicit safety checks in code that prevent programs from reading unauthorized data in memory. While processor speculation was designed to be a microarchitectural detail, invisible at the architectural level, carefully crafted programs could read unauthorized information in speculation and disclose it through side channels such as the execution time of a program fragment. When it was shown that JavaScript could be used to mount Spectre attacks, the V8 team became involved in tackling the problem. We formed an emergency response team and worked closely with other teams at Google, our partners at other browser vendors, and our hardware partners. In concert with them, we proactively engaged in both offensive research (constructing proof-of-concept gadgets) and defensive research (mitigations for potential attacks).
  • The Purism Librem Key
    The Librem Key is a new hardware token for improving Linux security by adding a physical authentication factor to booting, login and disk decryption on supported systems. It also has some features that make it a good general-purpose OpenPGP smart card. This article looks at how the Librem Key stacks up against other multi-factor tokens like the YubiKey 5 and also considers what makes the Librem Key a unique trusted-computing tool. Purism is a new player in the security key and multi-factor authentication markets. With the introduction of the Librem Key, Purism joins the ranks of other players—such as Yubico, Google, RSA and so on—in providing hardware tokens for multi-factor authentication. In addition, like the YubiKey 5 series, the Librem Key also provides OpenPGP support with cryptographic functions that take place securely on-key. This allows users to generate and use GnuPG public and private keys without exposing any secret key material to the host computer where the USB device is attached. The Librem Key is based on the German-manufactured Nitrokey Pro 2, but it has been modified to focus on "trusted boot" when used with Purism's Linux laptops. (I take a closer look at what the trusted boot process is and how the Librem Key fits into that process, later in this article.)
  • Atom-based network security appliances focus on industrial control
    Lanner’s Apollo Lake based “LEC-6041” and Bay Trail “LEC-6032” are Linux-supported network security appliances for industrial control monitoring with up to 7x GbE ports, including SFP ports, plus magnetic isolation and extended temp support.