Language Selection

English French German Italian Portuguese Spanish

Alpine Linux 2 review

Filed under
Linux

Alpine Linux is a distribution designed primarily for use as a router, firewall and application gateway. The latest stable version, Alpine Linux 2.0, was released last week (August 17, 2010). This review is the first for this distribution on this site, and also marks its first listing in the Firewall & Router category.

Installation: Installation of Alpine Linux to hard disk is via a text-based interface. The setup-disk script takes care of the completed automated installation, and the whole process takes less than two minutes. By default, the script creates the following partitions (test installation on an x86 computer with a 250 GB hard drive):

/boot of 100 MB
swap of about 1 GB
/ takes up the rest of the disk space

Ext3 is the default file system. Alpine uses the OpenRC initialization and daemon management script, the same system used by Gentoo. Incidentally, the maintainer of OpenRC has given up on the project. There are several setup- script that you need to use to make the system usable.

rest here




More in Tux Machines

Corporate Desktop Linux

A business doesn’t need a fleet of GNU/Linux guys to run IT. A few will do because one person can easily manage thousands of PCs with FLOSS. There are no licences to count, no networking limitations, no CPUs to count, … They just have to run the software any way that makes sense. Read more

Open-Source Radeon 2D Performance Is Better With Ubuntu 14.10

In this article are graphics card tests going back to the Radeon HD 4870 and even going back that far are 2D improvements with Ubuntu 14.10. However, most interesting is the Radeon HD 7000 series and newer where GLAMOR is used for 2D acceleration rather than UXA. GLAMOR leverages OpenGL for 2D acceleration and with X.Org Server 1.16 the GLAMOR support went from being an independent library to a highly-optimized implementation within the X.Org Server. Ubuntu 14.10 uses X.Org Server 1.16.0 along with Mesa 10.3.0, Linux 3.16, and xf86-video-ati 7.4.0. Read more

What if… KDE Started using Client-Side Decorations?

The main technical challenges faced by KDE developers is ensuring application consistency will continue to work under various form-factors. When Kwin (the KDE window manager) controls window borders, it can quickly and gracefully adapt to multiple form-factors. For example, in Plasma active space is at such a premium KDE can hide window decorations and embed them into the workspace itself. The other technical challenge is protocol and cross-enviornment consistency. It’s known that CSD-enabled applications can look extremly awkward when window borders are wrapped around an application not designed to use them. In addition, protocols for drawing CSDs on Linux are a mish-mash at best, and CSD code tends to be far less portable to other desktop environments. Compounding that, KDE has additional features (such as window tabbing) which are inherently incompatible with the feature. Read more

GNOME: A WEEKEND HACK

I’ve been working on making GtkInspector use a different display connection. This helps isolating it from some of the changes you can trigger from inside the inspector UI. Then I thought, why not use a different backend ?! We did enough work on GDK backend separation that it could almost work. But since we didn’t add API to actually connect to specific backends (users and applications get some control with GDK_BACKEND and gdk_set_allowed_backends()), nobody has ever used multiple backends in the same process. And things that don’t get used don’t work. So some fixes were necessary. Read more