Language Selection

English French German Italian Portuguese Spanish

The Linux Server Tournament

Filed under
Linux

In the interest of full disclosure, I am one of the Business Edition Linux Project team members. My greater interest is Linux use in the business place in general and in small business use specifically.

As part of a situational review for seeing how the BEL servers work with other distro based Linux servers on a given LAN, I thought I would write a less biased, hopefully more general discussion of the process and results of how each distro in the review performs individually and collaboratively.

The four distros used in this current test (there may likely be future tests using other distros) are BEL Server Basic, OpenSuse 11, Ubuntu server 8.04 and CentOS 5.

This entry is the "preface" to the overall review. The computers used will all be x86 based machines on an ethernet connection.

The server roles will be basic, common roles used in a small business.

* File/Print server using both NFS and SAMBA as well as CUPS
* Mail Server PostFix/Dovecot
* DHCP/DNS
* LDAP/authentication ( kerberos )
* Web server

The objective is not to determine which distro is "better" or "worse" but to find the best ways of implementing various Linux distro servers in the most productive manner.

To find nuances and perhaps provide some tips/hints for both the BEL Project and now the Linux community at large in a multiple distro server collaboration/implementation.

One of the biggest "complaints" we see is about the abundance of distros that are available. I am one who believes that is not a problem but instead a plethora of options in which certain distros are optimized for a certain area or level of performance. In that light, if distro A is optimized as a web server and performs best in that situation, why not use it as such and use distro B which has been optimized as a top notch file server platform, or area in which the devs have "tweaked" it to perform best?

By bringing these various distros together in one LAN, we want to obtain as much information about collaborative implementation between Linux distros. How well do they play together? What steps are necessary, if any, to make it as least complicated as possible?

Tune in next time when we begin to install and assign roles to our chosen four.

More in Tux Machines

Slackware Live Edition – on its way to 1.0?

Last week the second Beta of the upcoming Slackware 14.2 was released. My goal was to have a new Beta of my liveslak ready by that time, so that I could provide new ISO images to test the Slackware Beta2 on a live medium. Unfortunately, there was an attack of the flu in my team at work and things got a bit busier than usual. There was a plus side to this: some last moment bug fixes which could be applied to my scripts – the result of having more evenings available to test. Therefore the new release is not labeled “0.5.0” but “0.5.1” Read more

Leftovers: KDE

  • Cantor migrating to Phabricator: which tools our contributors must to use
    Projects and software developed by KDE community are going to migrate for a new tool to manage our code, commits, reviews, tasks, and more. This tool is Phabricator and you can visit the instance for KDE projects in this address. Since November 2015 we are migrating Cantor to Phabricator. After our first successful review code some days ago, I decided to write a post about which tools our contributors must to use while the migration process is not finished.
  • Kdenlive's sprint report
    Last week-end, Vincent and me met in Lausanne for a Kdenlive sprint. One of our goal was to merge Gurjot Singh Bhatti's GSoC work on curves for keyframes. This was more work than expected and we spent many hours trying fix the curves and make keyframes behave correctly. Not much time was left for sleep, but we still managed to get outside to make a group (!) picture in the woods above Lausanne.
  • Jekyll 3.x
    I’ve found three different types of transition issues (it is cool to look at these in a project I do not upgrade on a daily basis like Plasma and the rest of the KDE software).
  • kdev-python on Windows: try it!
    I spent the last two or three days playing around with KDE on Windows, with the aim of getting my Python language plugin for KDevelop to run there. In the end, it wasn’t that hard to get this to work — not as hard as I would have expected it to be, anyways.

Manjaro ARM launched

Hi community, wonderful news in regard of architecture expanding within Manjaro Linux. It all started with a simple post on our developers mailing list. Somebody wants to do Manjaro for ARM … Just after one month of development our first alpha release is now ready. So what is this all about? Manjaro Arm is a project aimed to bring you the simplicity and customability that is Manjaro to ARM devices. These devices are growing in numbers and can be used for any number of applications. Most famous is the Raspberry Pi series and BeagleBoard series. Read more

Plasma 5.5.4 and Calligra Suite 2.9.11 now available

The 4th update for KDE's Plasma 5.5.x series is now available to all Chakra users. According to the release schedule, unless new issues occur, this will be the last update for this series before 5.6 gets released next month. Plasma 5.5.4 as usually includes a month's translations and bugfixes, with the authors highlighting the improvements for handling multi-screen setups. The Calligra Suite also receives a bugfix update to version 2.9.11, which mainly provides fixes for krita and kexi. Read more