Language Selection

English French German Italian Portuguese Spanish

Come on in the Water's Fine

Filed under
Linux
Reviews
-s

Ark Linux 2005.2 rc3 was released a day or two ago and offered the new KDE 3.5 beta2 packages. I was interested in taking a look. After some doing I have an Ark install and am suffering from mixed feelings.

The install was almost a deal breaker. I wanted to install Ark Linux on my /dev/hda12 partition so I boot up an unique looking graphical environment that asked me for my Language, Keyboard, and Timezone, to which I answered. Then next was "what type of install?" On my main harddrive I have a bsd partition on hda1 and hda2 is an extended filesystem with many linux partitions mostly of ext3 and reiserfs. My choices during that attempt were Express and Expert. The others were grayed out. Express clearly states it will take over the whole drive so I most assuredly didn't want that one, and "expert" is usually the classification I pick anyway. Well, I don't know what I was doing wrong, but I just could not find where to set /dev/hda12 as "/". I thought I was and yet the next screen would always say it was installing on /dev/hda5 (the first linux partition on disc). I don't know, I've been installing various Linuxes for over 5 years now, and I just couldn't figure that one out. If anyone knows where I went wrong, please sing out. So anyway, I hooked up this other old Maxtor 10 gig harddrive that someone recently gave me. It consisted of a fat16 and two ntfs filesystems. I booted up the install disc and just pressed Express and whoopee, we were on our way. It did its thing and offered to let me play tetris. I passed on that as I figured it'd just slow down the install, but how nice of it to offer.

After a little while I got a message to let it reboot and I did. A nice splash/progress screen displayed for me while the system booted. It's a lovely seascape looking off a cliff on a beautiful sunny day. That was an unique start up I thought. It was accompanied by a rather tasteful progress bar. My first boot was a total lockup. It had detected my nvidia 6800 chipset and set "nv" as the driver. With no root accessibility until you get into the graphical user environment, init 3 was useless. I fortunately had a livecd hanging around, so I booted it and edited the xorg.conf file for vesa. That got me in.

The next boot I was auto-logged into kde. A KDE 3.5 no less.

KDE 3.5 has been covered basically in one of my SUSE stories, but this version seemed more like KDE default. SUSE had put in their various custom touches. This implementation of it seemed rather nice as well. It was fast and pretty and stable. Ark adds a few of their own customized graphics to the mix, uses the plastic windec and features the redglass cursor theme. I don't know if it's a KDE issue or an Ark issue, but system sound didn't work in KDE, until I configured them to use "play" instead of arts.

Ark has a strange philosophy on root and even its regular user account. I had been to their site earlier and read how to get back the usual functionality of root by using the konsole in the superuser mode provided in the menu and re-set the root password. Not a difficult task for someone who had seen the documentation.

Speaking of documentation, I had also seen where Ark provides nvidia drivers and their suggested procedure. Ark uses apt-get and a KDE-centric version of synaptic call kynaptic. They suggest using apt-get at the commandline for installing those drivers and I did as documented. apt-get update; apt-get install nvidia; nvidia-enable. The drivers were installed, but I think there was some niggle with the nvidia-enable step. Seems the xorg.conf file wasn't edited properly. The Load "glx" had been added back but the Driver was still listed as vesa. The xorg.conf.nvidia-enable was a mirror copy of the original xorg.conf. I edited it for nvidia and checked for a modprobe/modules.conf type file. I found a /etc/modprobe.conf file that did have some nvidia configuration at the end. Upon reboot I did get X, but it was still using vesa. I rechecked my xorg file to assure my changes were saved, they were. Then I checked lsmod to see if the nvidia drivers were loaded, they weren't. Well, I cheated and just put /sbin/modprobe nvidia in the /etc/rc.local file. Next reboot all was well.

Ark's claim to fame is their gorgeous Mission Control. Much like Mandriva's, SUSE's, or PCLOS's Control Center, it can help the user configure their system. It has hardware configuration modules and links to kynaptic and many other kcontrol modules for configuring your desktop.

        

As stated previously, Ark uses apt-get to install and uninstall its rpm packages. The kynaptic front-end is tidy and uncluttered, yet attractive and functional. I tested it with several packages and it worked as advertised. In fact, Ark comes with some of their software repositories already setup. That's a really convenient touch.

        

Ark delivers a 2.6.14 kernel and of course KDE 3.5 beta2. X is version 6.8.99.900 (6.9.0 RC 0) from 01 August 2005 + cvs. That nv bug is still present in this release, but hopefully they'll update to the newer cvs where it's fixed before final. They state on their site that they will be including KDE 3.5 final and will be releasing their full version at about the same time as KDE's release. Gcc isn't installed by default, but 3.4.5 version is available through apt-get/kynaptic. The kernel source is available as well. Ark ships with an OpenOffice.org 2.0beta that functioned really well. Xawtv and firefox are available through apt-get, but xmms isn't.

Ark doesn't come with a lot of extra goodies either. I couldn't watch simple mpegs from gamespot (the sound worked tho) while java and flash tests didn't work. However, flash is available through apt-get and there are docs on how to install/enable it as well as java on their wiki doc site: Enable Flash. Using Java.

        

Their site states:

Ark Linux is designed to:

  • be easy to learn and use

  • include all tools and applications the typical desktop user will need
  • be a technically sane development environment

It might be easy to install for someone who only has windows installed, but for someone with other systems they'd like to retain, ease of use is not how I'd describe it. After system install the nvidia driver installation doesn't go smoothly either. Those points aside, the rest is a breeze.

I think the all-the-tools-needed statement might not be entirely true as well. Where as all the KDE applications are available as well as OpenOffice, aren't browser plugins pretty much typical?

Technically sane development environment? There is no gcc installed by default. I guess if someone was gonna develop they'd know how to install it. They further claim "An extra highlight for developers is the addition of a compiler for the D programming language." I've never actually met anyone that uses that. Have you?

All in all, it's has some issues that make it not ideal for everyone. Once installed, it's a nice system. Good looks, adequate speed, and stable performance were delivered, but I'm not sure they meet all their claims. It's a fairly good foundation, but it would take some work to make myself at home.

Full rpmlist.
More Screenshots.

More in Tux Machines

Manjaro-Arm is Shutting Down

It is with deep regret that we are announcing that the Manjaro-Arm team is shutting down. I started this project a little over a year ago with no intent to become the sole maintainer. Read more

KDE and Qt

  • The Novelty of KDE Neon
    The good folks at KDE managed to engage a market of Linux desktop users underserved by other distribution models. Or, maybe it’s just me. KDE has a long history in the desktop ecosystem. It was the first Linux desktop I was exposed to back in 2006. Back then, it was on OpenSUSE and it was clean and functional. For some reason after that, installing KDE had never really appealed to me. I’ve tested it out briefly when poking around at what the OpenSUSE guys were doing and I’ve run Kubuntu for brief snippets. For years, I’ve been trying to find out what type of desktop user I am and which distro fits my needs.
  • Tracking KDE Frameworks and Qt
    The KDE-FreeBSD team bumped Qt to 5.7.1 and KDE Frameworks to 5.31.0 in official ports last week, so we’re fairly up-to-date in that department. On FreeBSD, we still fully support Qt4 next to Qt5, so some of the delay in getting this stuff in is due to some shuffling of install locations. In particular, we’ve added qt-chooser in this round of updates, so that qmake is qmake — and no longer qmake-qt4 or some other suffixed binary. We use qt-chooser to switch out one or the other. Checking that this doesn’t break anything else — or at least making sure that everything still compiles — is what took the most time this round of updates.
  • Simple Menu Launcher for KDE Plasma 5.9
    Following "United" theme, there is also "Simple Menu" launcher for KDE Plasma 5.9. It's minimal, a smaller form of full screen menu; it's also clean, showing all applications at once. Honestly, it's UI is similar to Pantheon Menu in elementary OS but including categories. If you like horizontal-oriented menu, Simple Menu is suitable for you. It's available to install from KDE Store. Thanks to Sho for creating Simple Menu.
  • A Simple KDE Twitter Plasmoid
    This KDE Twitter Plasmoids offers a simpler alternative to a desktop Linux twitter app like Choqok. See tweets, send tweets, and check mentions.
  • Telegram desktop client for flatpak #2
    Some time ago I posted a blog post about how I packed telegram desktop client for flatpak. I’ve been updating it since then in some reasonable intervals as I don’t have time to update it more often and mostly because the telegram client’s build system breaks my build quite oftenly. Recently I discovered that someone managed to patch telegram to use system Qt libraries instead of building own patched Qt and building linking it statically. After some time I managed to adjust those patches and make them work with my build which allows me to use Qt from KDE runtimes. Here are new instructions how to get this work:
  • Building the latest greatest for Android AArch64 (with Vulkan teaser)
    Let’s say you got a 64-bit ARM device running Android. For instance, the Tegra X1-based NVIDIA Shield TV. Now, let’s say you are also interested in the latest greatest content from the dev branch, for example to try out some upcoming Vulkan enablers from here and here, and want to see all this running on the big screen with Android TV. How do we get Qt, or at least the basic modules like QtGui, QtQuick, etc. up and running on there?
  • Qt Quick WebGL Streaming
    WebGL Streaming is optimized for Qt Quick and allows you to run remote Qt Quick applications in a browser.

SUSE Leftovers

  • OBS got the power!
    Old build workers, rack mounted Old build workers, rack mounted One year after introducing a new kind of Open Build Service worker machines, the “lambkins”, the openSUSE Build Service got a big hardware refresh. The new machines, sponsored by SUSE, are equipped with: 2,8GHz AMD Opteron Processors (6348) 256 GB RAM one 120 GB SSD Four of them are located in a chassis with a height of 2 units and run 12-16 workers on them (virtual machines, that are building packages). That new build power allowed us to remove some of old machines from the pool. The unified hardware makes the management of the machines a lot easier now, even if there are still the most powerful old machines left.
  • openSUSE Heroes December meeting – final results
    While we had some fun and good food and drinks, we also managed to discuss a lot during the three days in the Nuremberg headquarter. This was needed because this was the first time that the Heroes came together in their current form. In the end, we managed to do no coding and even (nearly) no administration – but instead we started to discuss our (internal and external) policies and work flows – and did some decisions regarding the next steps and the future of the openSUSE infrastructure.
  • New and improved Inqlude web site
    During last year's Summer of Code I had the honor of mentoring Nanduni Indeewaree Nimalsiri. She worked on Inqlude, the comprehensive archive of third party Qt libraries, improving the tooling to create a better structured web site with additional features such as categorization by topic. She did an excellent job with it and all of her code ended up on the master branch. But we hadn't yet made the switch to change the default layout of the web site to fully take advantage of all her work. As part of SUSE's 15th Hack Week, which is taking place this week, I took some time to change that, put up some finishing touches, and switch the Inqlude web site to the new layout. So here we are. I proudly present the new improved home page of Inqlude.

Benchmarks Of Ubuntu 17.04 Beta vs. Antergos, Clear Linux, openSUSE Tumbleweed

For those curious how Ubuntu 17.04 is shaping up, considering this week was the "beta" release for participating flavors, I decided to take a fresh Ubuntu 17.04 x86_64 daily ISO and see how its performance compares to Ubuntu 17.10, Clear Linux 13600, Antergos 17.2, and openSUSE Tumbleweed. Read more