Language Selection

English French German Italian Portuguese Spanish

My Take On PocketLinux

Filed under
Linux
Reviews
-s

Distribution release PocketLinux 1.2 was announced on Distrowatch last night and Tuxmachines was excited to try it out. However, that excitement didn't last long. A smaller download of 370mb doesn't put it in my personal classification as a mini distro and in fact, I can't really see the point. If it's going to be small, then make it small enough to fit onto a 80mb cdr. If it's going to take a full cdr, why not use the space to include enough applications to make your distro attractive.

PocketLinux's claim to fame is its simplified Slackware installer and light version of KDE. However, the simplified installer really isn't any help as the newcomer who might be dissuaded by a Slackware install still must go through the most intimidating steps of cfdisking and/or setting up a root partition. The simplification of not having to pick applications might be welcome if it included at least gcc or the kernel sources. Further, they simplified it so much one doesn't even get to set up a normal user account or their internet connection specifics.

Upon boot, the internet connection is active however through probing and dhcp, then one finds KDE, KDE Light, openbox, or TWM to log into. The full version of KDE is at version 3.4.0 which is a little behind the curve by now and the light version was found to be way too light for my tastes. This might appeal to some whose machine specifications are running a little on the lowside as it uses OpenBox for the window manager and still provides a nice looking desktop. However, this reporter was becoming quite annoyed at the constant konqueror crashes. This occured in the full KDE or KDE Light.

Most of the expected system tools and programs seemed to be included, however it didn't seem to come with gcc. I find this rather inconvenient for a distro without a large repository of binary applications to install. All of this sits on top of a 2.4.29 kernel. 2.6 has been stable for quite some time now and is the standard for the desktop system. In addition, 2.4.29 isn't even the latest in the 2.4 series. Most of my other "extra" hardware was ignored as well, if you consider things like soundcard and tv card extras.

In comparing the full version to the light version of KDE, one can find they apparently met their goal of a scaled down desktop environment. In this first example of the settings/preference menus, one is quite limited in their choices. Kcontrol, ObConf, and panel configuration is included in the light version and that may be adequate for some.

    

I'm not so sure the same can be said for the tools menu however. One could speculate that menu to be quite inadequate.

    

For your consideration, further comparisons:

    

    

    

So, I would say Tuxmachines was a little disappointed with PocketLinux at this time. I find the simplifications haphazardly thought out and inadequate. Granted the light version was fast performing, however it wasn't very stable. I experienced enough crashes to dissuade anyone. And what's the advantage of a 370mb download?

Perhaps I'm missing the point of this distribution, but am not inclined to care as even if it was planned a little better, it's too far behind the current technology available from other vendors. Whereas any person who can hammer a distro together that will actually install and boot deserves some credit, I just don't really see the point or any advantages in PocketLinux. Perhaps as a livecd it'd make more sense.

Distroreviews has also published a review of PocketLinux. Although I haven't read it and can't say, perhaps he found it more pleasing.

More Screenshots in the gallery.

More in Tux Machines

Kernel Space: Linux, Graphics

  • Linux kernel bug delivers corrupt TCP/IP data to Mesos, Kubernetes, Docker containers
    The Linux Kernel has a bug that causes containers that use veth devices for network routing (such as Docker on IPv6, Kubernetes, Google Container Engine, and Mesos) to not check TCP checksums. This results in applications incorrectly receiving corrupt data in a number of situations, such as with bad networking hardware. The bug dates back at least three years and is present in kernels as far back as we’ve tested. Our patch has been reviewed and accepted into the kernel, and is currently being backported to -stable releases back to 3.14 in different distributions (such as Suse, and Canonical). If you use containers in your setup, I recommend you apply this patch or deploy a kernel with this patch when it becomes available. Note: Docker’s default NAT networking is not affected and, in practice, Google Container Engine is likely protected from hardware errors by its virtualized network.
  • Performance problems
    Just over a year ago I implemented an optimization to the SPI core code in Linux that avoids some needless context switches to a worker thread in the main data path that most clients use. This was really nice, it was simple to do but saved a bunch of work for most drivers using SPI and made things noticeably faster. The code got merged in v4.0 and that was that, I kept on kicking a few more ideas for optimizations in this area around but that was that until the past month.
  • Compute Shader Code Begins Landing For Gallium3D
    Samuel Pitoiset began pushing his Gallium3D Mesa state tracker changes this morning for supporting compute shaders via the GL_ARB_compute_shader extension. Before getting too excited, the hardware drivers haven't yet implemented the support. It was back in December that core Mesa received its treatment for compute shader support and came with Intel's i965 driver implementing CS.
  • Libav Finally Lands VDPAU Support For Accelerated HEVC Decoding
    While FFmpeg has offered hardware-accelerated HEVC decoding using NVIDIA's VDPAU API since last summer, this support for the FFmpeg-forked libav landed just today. In June was when FFmpeg added support to its libavcodec for handling HEVC/H.265 video decoding via NVIDIA's Video Decode and Presentation API for Unix interface. Around that same time, developer Philip Langdale who had done the FFmpeg patch, also submitted the patch for Libav for decoding HEVC content through VDPAU where supported.

Unixstickers, Linux goes to Washington, Why Linux?

  • Unixstickers sent me a package!
    There's an old, popular saying, beware geeks bearing gifts. But in this case, I was pleased to see an email in my inbox, from unixstickers.com, asking me if I was interested in reviewing their products. I said ye, and a quick few days later, there was a surprise courier-delivered envelope waiting for me in the post. Coincidentally - or not - the whole thing happened close enough to the 2015 end-of-the-year holidays to classify as poetic justice. On a slightly more serious note, Unixstickers is a company shipping T-shirts, hoodies, mugs, posters, pins, and stickers to UNIX and Linux aficionados worldwide. Having been identified one and acquired on the company's PR radar, I am now doing a first-of-a-kind Dedoimedo non-technical technical review of merchandise related to our favorite software. So not sure how it's gonna work out, but let's see.
  • Linux goes to Washington: How the White House/Linux Foundation collaboration will work
    No doubt by now you've heard about the Obama Administration's newly announced Cybersecurity National Action Plan (CNAP). You can read more about it on CIO.com here and here. But what you may not know is that the White House is actively working with the Linux and open source community for CNAP. In a blog post Jim Zemlin, the executive director of the Linux Foundation said, “In the proposal, the White House announced collaboration with The Linux Foundation’s Core Infrastructure Initiative (CII) to better secure Internet 'utilities' such as open-source software, protocols and standards.”
  • Why Linux?
    Linux may inspire you to think of coders hunched over their desks (that are littered with Mountain Dew cans) while looking at lines of codes, faintly lit by the yellow glow of old CRT monitors. Maybe Linux sounds like some kind of a wild cat and you have never heard the term before. Maybe you have use it every day. It is an operating system loved by a few and misrepresented to many.

RebeccaBlackOS 2016-02-08 Review. Why? Because it’s Friday.

These are the types of problems found in an independent distro build from scratch. I cannot understand how a system built on Debian could be this buggy and apparently have zero VM support which Debian comes with by default. I can take some solace in the fact that it was built by one person and that one person is a Rebecca Black fan but as far as a Linux Distribution is concerned there is not much here. Some could say “Well its not supposed to be taken as a serious Distribution.” True except it is listed and kept up with on DistroWatch therefor it should be held as a system ready distribution especially when it was not released as a beta or an RC. If this distribution is ever going to be considered a real platform it has a long way to go. I give it about as many thumbs down as the Rebecca Black Friday video. Read more

Android More Leftovers