Community Blogs

Virt-install&Virt-manager at Xen 4.0-rc8 ( pvops) Dom0 on top Ubuntu Karmic Koala Server

The final target of this post is to demonstrate how flexible is Ubuntu Karmic Koala Server environment. Build Xen 4.0-rc8 and the most recent stable pvops kernel ( with DRM support). Loading Xen Instance followed by install Ubuntu's Libvirt environment, providing utility virt-install for creating PV and HVM DomUs, virt-manager completely functional to manage any DomU been built via virt-install. Finally HVM image created by beta version Ubuntu 10.04 Lucid Lynx is utilized to bring up Ubuntu 10.04 Lucid Lynx PV DomU, regardless standard trick with "pygrub"  due to Lucid grub2 notation set root='(/dev/sda,1)' instead of  Karmic's set root=(hd0,1) doesn't work any longer. Xen's 4.0-rc8 "pygrub" was not ready to parse such unexpectedness First install required packages:

apt-get install libcurl4-openssl-dev xserver-xorg-dev python2.6-dev mercurial gitk build-essential libncurses5-dev uuid-dev gawk gettext texinfo bcc bridge-utils iasl

Second – build Xen from source

# cd /usr/src
# hg clone
# cd xen-unstable.hg
Set in
PYTHON = python
# make install-xen
# make install-tools
# make install-stubdom

Now checkout and build pvops kernel

# git clone git:// linux-2.6-xen
# cd linux-2.6-xen
# git checkout -b xen/stable-2.6.32.x origin/xen/stable-2.6.32.x

Notice :-

# git checkout origin/xen/master -b xen/master

will result building the most recent 2.31.12 version of pvops kernel. Branch above , actually is not required to be checked out . It’s default branch of "git clone".However, APIC rework has been committed for

# make menuconfig
and tune kernel to support Xen in Dom0

# make -j4
# make modules_install install
# mkinitramfs -o /boot/initrd-

Tuning results Xen packages to be placed into /usr/local/lib/python2.6/dist-packages
due to Changeset 19594 in xen-3.4-testing.hg. Otherwise, Xen packages would go to /usr/lib/python2.6/site-packages, which is not default location for python 2.6 on Ubuntu 9.10 ( vs F12 ). Thus you won’t be able to start xend in Dom0. Add entry to /boot/grub/grab.cfg:-

menuentry "Xen 4.0-rc8 / Ubuntu 9.10 kernel pvops" {
insmod ext2
set root=(hd1,8)
multiboot (hd1,8)/boot/xen.gz
module (hd1,8)/boot/vmlinuz- dummy=dummy root=/dev/sdb8 ro console=tty0
module (hd1,8)/boot/initrd-

Reboot system and install libvirt environment :-

Two steps in procedure bellow make Xen default Hypervisor on Ubuntu 9.10.
First is commenting out (xend-unix-server yes) in /etc/xen/xend-config.sxp , second export variable export VIRSH_DEFAULT_CONNECT_URI="xen:///"
in root’s .bashrc.

Then run:-

# apt-get install ubuntu-virt-server ubuntu-virt-mgmt

Now you should be able to install Ubuntu 10.04 Lucid Server HVM via virt-install :-

# virt-install -n LucidSRV -r 1024 --hvm --vnc -f /dev/sda8 -c /home/boris/Lucid.iso --debug

Start up LucidSRV HVM via virt-manager and scp to Dom0 vmlinuz-2.6.32-16-server and initrd.img-2.6.32-16-server

File bellow may be used for command :-

# virsh define Lucid-def.xml


<domain type='xen' id='3'>
<cmdline>root=/dev/xvda1 ro </cmdline>
<clock offset='utc'/>
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/sda8'/>
<target dev='xvda' bus='xen'/>
<interface type='bridge'>
<mac address='00:16:3e:04:6b:5a'/>
<source bridge='eth0'/>
<script path='/etc/xen/scripts/vif-bridge'/>
<target dev='vif3.0'/>
<console type='pty' tty='/dev/pts/1'>
<source path='/dev/pts/1'/>
<target port='0'/>
<input type='mouse' bus='xen'/>
<graphics type='vnc' port='5900' autoport='yes'/>

At this point Lucid Server PV DomU may be started via virt-manager.

Runtime snapshots


Systems Administrator Creed

This is my server.  There are many like it, but this one is mine.  My server is my best friend.  It is my life. I must master it as I master my life.  My server, without me is useless. Without my server, I am useless.  I must configure my server true.  I will...


My server and myself know that what counts in this war is not the packets we drop, the noise of our fans, nor the power we consume. We know that it is the data that counts. We will backup...


My server is human, even as I, because it is my life. Thus, I will learn it as a brother. I will learn its weakness, its strength, its parts, its accessories, its I/O and its slots. I will keep my server clean and ready, even as I am clean and ready. We will become part of each other. We will...


Before God I swear this creed:  My server and myself are defenders of the command prompt, we are the masters of our enemy.  We are the saviors of my life.  So be it, until every server is patched and there is no enemy, but uptime.



Accessing VMWare Server 2 with vSphere Client (the unsupported way)

As many of you already discovered there's no official Linux client for accessing VMWare Server 2.x, the only thing VMWare suggests you to do is to use internal web interface based on a Tomcat webserver.
This web interface is ugly and slow, not so reliable if you plan a clean and fast administration, as alternative you can use the good and efficient Virtual Infrastructure Client (VIC).

Again: VIC is only available for Windows platform and no Linux (or OS-X) client is available now, you can run it on top of WINE libs but it's still not a linux native client.
VMWare promised a lot of time ago a "planned version" for Linux but nobody have already seen it (planned with no expected date...) so we're still waiting for it.

Now vSphere architecture is out, new vSphere Client replaces Virtual Infrastructure Client and guess what ? vSphere Client doesn't support officially VMWare Server, this makes me really upset and after reading different posts even from their community forum (like this) I was really trying to find a different way to access my server installations or move to a totally different product (VirtualBox, KVM, ...)

But after some TCPDUMP traces, a lot of different retries and some Google searches  I've solved my problem and I'll hope this article may help someone else as well.

When you try to connect vSphere to VMWare server you need to insert your credentials and the host name/IP, I've started with (the old way used with VIC),, and so on...
Finally I've discovered this form: seems to be the right one.

At the first connection you need to install a certificate in your Windows machine, second step is to retrieve from server "a generic installer", so you can choose to "Save the Installer" or "Run the Installer";

both options drives you to a generic error like:

"The required client support files cannot be retrieved from the server"
"The login process will now exit"
"Details: The server could not interpret the client's request. (404 not found)"


But what kind of support files do you need, where are there ? Here's a link with some useful and legal files in it

Now what you should do after downloading these support files ?
Just unrar these files into your vSphere Client installation folder, something like
"Program FilesVMWareInfrastructureVirtual Infrastructure Client" (x86 32bit)
"Program Files (x86)VMwareInfrastructureVirtual Infrastructure Client" (x86 64bit)
you'll finally have a directory named "2.5" inside this root folder, now run your vSphere Infrastructure Client again, after inserting your credentials you'll see
the entire login process like in the past with VIC (so "loading inventory form",
"loading classes", and so on...) and the new shiny Client interface is now connected
to VMWare Server as in the past.


This is just a trick to have authentication running again and have access to your
legitimate VMWare Server installation, I'll hope they're really working on this
promised linux client capable of connecting to VMWare Server.
At the moment I'm quite skeptic because this new client relies on Microsoft Windows .NET 3.x Framework and Windows J# redistributable package, as a programmer these are not my preferred tools if I'm planning to have a cross platform program because I'm totally depending on .NET (or Mono) and MS libs.
If you're running a big business you don't really need it, you just purchase vSphere (new ESX) and you're set, but if you really need "bare metal emulation" and you can't afford vSphere, VMWare Server is still the best reliable solution for it, yeah I know Virtual Box/KVM/XEN and others are growing fast but on bare metal VMWare is still the best (from my point of view)



I hope this process may help someone else and I'll look forward for your comments to this post

Andrea (Ben) Benini


Access VMWare Server 2 remote virtual machine without web interface

I've spent a lot of time doing something else and I left the blog alone for a while.

This new entry is related to VMWare Server v2.0 and Virtual Infrastructure Client on Linux.
Many of you already know there's no Virtual Infrastructure Client available on a linux client, so it's quite a mess if you'd like to control a VMWare server if you don't want the ugly web interface available with it.

Personally I don't like WebInterface, it's ugly and very slow, here's where Virtual Infrastructure Client (VIC) comes out, unfortunately this is only available for Windows machines. VMWare promised a lot of time ago a version available for linux but nobody have already seen it working or available.

I'm quite upset about lack of support for linux users so I've installed the windows client on linux with WINE emulation. It works fine, even with WINE, but it's clearly a Windows application and it's not native.

Few days ago I've discovered I can use VMWare Player  v2.x and use it to control Virtual Machines consoles even on a remote VMWare Server. If you run VMWare Player (v2.5.3.x on my Gentoo box) you can only choose local virtual machines so you cannot select remote machines running on a remote host without some sort of network share. if you run local help you can see:

~$ vmplayer --help
vmplayer [OPTION...] <Virtual machine config file>

Help Options:
-?, --help Show help options

Application Options:
-v, --version Display the program version
-L, --list-stock-ids Display the list of registered stock IDs
-X, --fullscreen Start in fullscreen mode
-U, --unity Start in Unity mode
-k, --no-kiosk-warning Suppress the warning that appears when a Kiosk Mode ACE is started
-K, --no-kiosk-mode Force a Kiosk Mode ACE to start outside of Kiosk Mode

 But, if you launch it with this command:

~$ vmplayer -h

Where "" is obviously the IP Address of the remote VMWare Server machine and 8333 is the remote port for VIC control (TCP Default)

When you run it you can see:

Just input your remote username and password and you'll see the list of remote virtual machines available:

 Open one of the machines and use it. You cannot administer or manage remote filestore or create new virtual machines like VIC does but at least you can use them. You've full access to the remote machine console without VIC and without web access.

Hope it helps someone


Andrea (Ben) Benini




mod_rewrite with Fedora 10 and ISPConfig for WordPress

This relates to Fedora 10 and ISPConfig 3.0.1 set up as described in this HowtoForge post One of my colleagues recently got interested in offering our clients Wordpress as a content management system, so he's been trying it out. Yesterday he found out that if he wanted to change the permalink style in Wordpress he needed write access to .htaccess, which he didn't have because the user rights haven't been set up very well there. So I gave him write access by using
chown apache:apache .htaccess
Unfortunately this resulted in a 500 Interal Server Error. Looking at the error log for the website I tried this for it let me know that RewriteEngine directives were not allowed in the .htaccess. Since I didn't want to mess with the base configurations of ISPConfig I started looking around for other options. Eventually I found that I had to add something similar to this to the Apache directives field under options under the website's settings
<IfModule mod_rewrite.c>
<Directory /var/www/[sitename]/web/>
Options +FollowSymLinks
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
Of course [sitename] should be replaced with the name of your website. It all works after I restarted the apache server myself, but I do not know if that is completely necessary. Also it might take a few seconds before ISPConfig finishes editing the configuration file.

RAID: Installing grub on the other Disks

So, you've followed my previous blog: Replacing faulted drive on Linux software RAID (MDTOOLS), you already know how to swap a faulty drive with a new one, but what happens if you need to substitute primary disk where your Computer makes boot ?

After adding a new disk to your raid chain it's a good idea to make it bootable as well by installing grub on MBR. When boot drive in your raid array becomes faulty all you've to do is to power off your machine, substitute your faulty drive and boot your computer again. If you've properly set bios boot sequence to iterate between primary, secondary, ... you can boot your raid array again, second or third HD makes the boot because you've installed grub on it, pretty easy and straightforward, this contributes to have a bulletproof system.

How to install grub on other disks ?

First enter grub console:

~# grub
Probing devices to guess BIOS drives. This may take a long time.


GNU GRUB  version 0.97  (640K lower / 7168K upper memory)
[ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]
grub> root (hd1,0)
grub> setup (hd1)
grub> quit

Where HD1 means second disk (grub starts counting from 0), HD2 means third disk and so on

If you've your boot partition inside a drive array as well it becomes easy to swap disks and replace them when faulty, here's an example:

boba:~# fdisk -l /dev/sda
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003272d
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          12       96358+  fd  Linux raid autodetect
/dev/sda2              13          73      489982+  fd  Linux raid autodetect
/dev/sda3              74         681     4883760   fd  Linux raid autodetect
/dev/sda4             682       38913   307098540   fd  Linux raid autodetect

take a look at my fstab:

boba:~# cat /etc/fstab
# /etc/fstab: static file system information.
# proc /proc proc defaults 0 0
/dev/md2 / ext3 errors=remount-ro 0 1
/dev/md0 /boot ext2 defaults 0 2
/dev/mapper/storage-storage /home xfs defaults 0 2
/dev/md1 none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0

As you can see my /dev/md0 is the boot partition, /dev/sda1 is a part of it, it doesn't matter if you're using RAID1,5,6,10,...

With this hint you can boot your machine again, even if your primary disk has gone 

Hope it helps


Andrea (Ben) Benini



Open Source Security Solutions

A report on the state of security has been released today by the Sans Internet Storm Center , the two main threats posed to an organisation are the threat of targetted "spear phishing" against Client Desktops and attacks against web applications.

Most here at would be familiar with the threat of the malware against Windows Desktops, this report highlights the fact that other client applications are being targeted; Adobe Reader and Quicktime are good examples. Of course running Linux on your desktop lowers the risk of these attack vectors considerably.

Another area where Linux based open source solutions excel is in security vulnerability assessment tools. Use of these tools will help to find security vulnerabilities within your web server and web applications. Once the vulnerabilities are found they can be fixed or remediated.

Here are some tools to get you started:

Nmap for port scanning of your system(s). Shows you open ports on your server and holes in your firewall.
OpenVas for server vulnerability scanning of your servers. It checks for listening ports / services and then tries to confirm if services are vulnerable to exploitation using a db of thousands of vulnerabilities.
Nikto is web service scanner that does a thorough analysis of your web server. Looks for scripts and server misconfigurations that are a security threat.
SQLiX performs SQL Injection Testing that can find vulnerable web application applications. This is a popular attack vector for web application attacks.
OSSEC  is a Host based intrusion detection system that is easy to setup and use.

These tools are all high quality and just a sample of the powerful open source security tools that are available.

About the Author: Peter runs the popular online open source security tool scanning site Where various security scanning tools are made available for free to assist in the securing of internet based servers.

Replacing faulted drive on Linux software RAID (MDTOOLS)

Here's a very quick HOWTO for Linux Software RAID, these notes are maded for replacing a faulty disk with a new one.

When you've a software RAID configuration with linux you've planned to survive to hardware failures, when these failures happen you need to replace the faulty drive with a new one and inform your RAID configuration of it.

First take a look at your current RAID config by running the command:

~# cat /proc/mdstat
Personalities : [raid1]
  md1 : active raid1 sda2[2](F) sdb2[1]
     70645760 blocks [2/1] [_U]
  md0 : active raid1 sda1[0] sdb1[1]
     9767424 blocks [2/2] [UU]
  unused devices:


This shows raid md1 has drive sda2 stopped with a fault.
As my config shows I've two disks with software RAID1, sda2 is marked as faulty (letter F) and block device is not present in the RAID ("_" instead of "U"). First thing to do is to replace the drive, power off the machine if you don't have hotswap drives

Then you need to inform your configuration about the new drive, first remove your previous block device (from raid md1 in my case):

~# mdadm /dev/md1 -r /dev/sda2
mdadm: hot removed /dev/sda2

Then add your new partitioned block device:

~# mdadm /dev/md1 -a /dev/sda2
mdadm: re-added /dev/sda2

Now you will see it regenerate your RAID chain in mdstat:

~# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sda2[2] sdb2[1]
70645760 blocks [2/1] [_U]
[>....................] recovery = 0.3% (268800/70645760) finish=21.8min speed=53760K/sec
md0 : active raid1 sda1[0] sdb1[1]
9767424 blocks [2/2] [UU]
unused devices:

When finished you'll have a working config


Hope it helps





Instalando y configurando LAMP en Fedora

 LAMP Fedora

Ahora que ya tenemos nuestro servidor FTP funcionando, supongo que querréis algo más. ¿Tal vez, un servidor LAMP? Pues sí. Es lo que vamos a hacer. Instalaremos y configuraremos un servidor completo con httpd, mysqld y php. Pero antes, ¿qué es un servidor LAMP?

El acrónimo LAMP se refiere a un conjunto de subsistemas de software necesarios para alcanzar una solución global, en este caso configurar sitios web o Servidores dinámicos con un esfuerzo reducido.

En las tecnologías LAMP esto se consigue mediante la unión de las siguientes tecnologías:

  • Linux, el sistema operativo;
  • Apache, el servidor web;
  • MySQL, el gestor de bases de datos;
  • Perl, PHP, o Python, lenguajes de programación.


Para empezar instalaremos todos los paquetes que necesitamos. Abrimos una terminal y nos logueamos como root.

su -

yum install httpd php php-gd mysql-server php-mysql phpMyAdmin

Ahora, ya con todos los paquetes instalados, empezaremos a configurar nuestro servidor. Vamos a seguir un orden, asi que empezaremos por Apache, el servidor web. En fedora viene muy bien configurado por defecto y a no ser que necesitemos optimizar al máximo nuestro equipo no lo tocaremos. De todos modos, si queréis leer el archivo de configuración, se encuentra en /etc/httpd/conf/httpd.conf

Lo siguiente será establecer una contraseña para el usuario root de mysql. Para ello abrimos una terminal y escribimos.

mysql -u root

USE Mysql;

UPDATE user SET password=password(’escribimos_aquí_la_contraseña’) WHERE user=’root’;


Nota: Si te devuelve un error al internar cambiar la contraseña prueba a escribir el comando manualmente, ya que al copiar de wordpress la comilla simple (’) puede transformarla en comilla doble (”)

Ahora con los datos de mysql configuraremos PHPMyAdmin. Abrimos de nuevo una terminal y escribimos.

Si usas Gnome | su -c ‘gedit /etc/phpMyAdmin/’

Si usas KDE | su -c ‘kwrite /etc/phpMyAdmin/’

Buscaremos las líneas donde pone:

$cfg['Servers'][$i]['user']= ”;
$cfg['Servers'][$i]['password']= ”

Y lo dejaremos de la siguiente manera:

$cfg['Servers'][$i]['user']= ‘root’;
$cfg['Servers'][$i]['password']= ‘contraseña_de_mysq’

Ahora que ya tenemos todo configurado iniciaremos los servicios necesarios para que funcione nuestro servidor. A diferencia de el servidor FTP que sólo requiere uno, nuestro servidor LAMP requiere dos. Además también hay que abrir los puertos en el cortafuegos. Para ello vamos a Sistema – Administración – Cortafuegos y en servicios confiables seleccionamos WWW. Aplicamos y cerramos. Ahora abrimos una terminal y escribimos lo siguiente:

su -

service httpd start

service mysqld start

Como todos los servicios también podremos pararlos.

su .

service httpd stop

service mysqld stop

O reiniciarlos. Esto es necesarios cada vez que cambiamos algo en los archivos de configuración.

su -

service httpd restart

service mysqld restart

Por último, si queremos que estos servicios se inicien durante el arranque tan sólo tenemos que escrbir:

su -

chkconfig httpd on

chkconfig mysqld on

Con este servidor que acabamos de instalar y configurar podremos instalar cualquier CMS como Drupal o WordPress. Sólo hay que tener tres datos en cuenta, la carpeta donde deberemos crear nuestra web es en /var/www/html. Además mientras no se haya ningún archivo llamado index se mostrará una web de prueba de Fedora. Y por último, nuestro servidor será accesible localmente escribiendo en el navegador la dirección html://

Fuente | El blog de Iyan


Instalando y configurando VSFTPD en Fedora

 Servidor FTP

Instalar y configurar un servidor usando Fedora es una tarea sencilla y bastante entretenida. A lo largo de dos post explicaré paso a paso cómo instalar un servidor completo, tanto FTP como HTTP. Pero antes de empezar, ¿qué es un servidor?

En informática, un servidor es un tipo de software que realiza ciertas tareas en nombre de los usuarios. El término servidor ahora también se utiliza para referirse al ordenador físico en el cual funciona ese software, una máquina cuyo propósito es proveer datos de modo que otras máquinas puedan utilizar esos datos.


En la primera parte explicaré como instalar VSFTPD (Very Secure FTP Daemon), considerado como la opción más segura para crear un servidor de este tipo. Algunos ejemplos de servidores que usan VSFTPD:


Para empezar, instalaremos los paquetes que necesitamos. Para ello nos logueamos como root y escribimos:

su -

yum install vsftpd

Ahora ya tendremos nuestro servidor FTP instalado. A continuación lo configuraremos y ya podremos empezar a compartir datos con él. Vsftpd tiene dos archivos de configuración, ambos guardados en /etc/vsftpd/

En primer lugar abriremos el archivo vsftpd.conf, donde se encuentran la mayoría de las opciones que podremos modificar.

su -

Si usas Gnome | gedit /etc/vsftpd/vsftpd.conf

Si usas KDE | kwrite /etc/vsftpd/vsftpd.conf

Os recomiendo que leáis con calma todos los parámetros y los modifiquéis para que se adpaten a vuestras necesidades. A continuación citaré los más importantes a tener en cuenta.

Parámetro anonymous_enable

Si el valor es YES cualquier persona podrá acceder al servidor. Si es NO, sólo los usuarios autentificados podrán acceder.

Parámetro local_enable

Con esta opción podemos permitir la entrada a usuarios locales o no

Parámetro write_enable

Si queremos permitir la escritura en nuestro servidor, escribiremos YES. Si por el contrario, queremos que sea de solo lectura, pondremos NO.

Parámetro ftpd_banner

Aquí escribiremos un mensaje que será mostrado cada vez que un usuarios accede al servidor.

Parámetro anon_max_rate

Se utiliza para determinar la máxima velocidad de transferencia a los usuarios anónimos. Se utilizan los bytes por segundo como unidad.

Parámetro max_clients

Aquí podremos determinar el número máximo de conexiones simultáneas a nuestro servidor FTP.

Parámetro max_per_ip

Igual que el anterios pero para limitar las conexiones que usen la misma IP. Lo lógico es poner el mismo tope que el anterior parámetro. Esto nos servirá para limitar el número de conexiones simultáneas de personas que usen un mismo Proxy, por ejemplo.

Ahora que ya tenemos todo configurado (estos son los parámetros básicos, pero hay muchos más) sólo tenemos abrir los puertos en el cortafuegos y arrancar el servidor. Para ello vamos a Sistema – Administración – Cortafuegos y en servicios confiables seleccionamos FTP. Aplicamos y cerramos.

Ahora abrimos una terminal, nos logueamos como root y escribimos:

su -

service vsftpd start

Además si querermos que arranque durante el arranque, escribimos:

su -

chkconfig vsftpd on

Listo!! Ya tenemos en marcha nuestro servidor FTP. Para comprobar que funciona, abrimos el navegador y escrbimos en la direccion:

Ahora sólo queda empezar a compartir archivos. Para ello tened en cuenta que la carpeta en la que hay que guardar los archivos para que sean visibles en nuestro servidor es /var/ftp

Fuente | El blog de Iyan



tail -f vs less +F

When I was fist seen this command, I was thinking ohhhh god why I haven't seen this command long time back, this could have make my life much more easier.

tail -f /var/log/messages

The main advantages of tail -f is that, you can monitor logs real time it will keep on appending logs as it goes, but what if I have found one error and want to look back what went wrong, I have to quit the tail and open the file in VI or with less.
There comes the advantage of less +F, you can monitor logs real time it will keep on appending logs as it goes, and if I found error I can execute ctrl+c to stop appending real time log and can go back and check what went wrong, once I verified and can again start appending log by executing capital F
less +F /var/log/messages

This does the same thing as tail -f but it will also show the entire file, just press ctrl + c to navigate around the log file. When you want to view the log in real time again just type a capital F.
Page 4 of 8

Who we are ?

The Linux Foundation is a non-profit consortium dedicated to the growth of Linux.

More About the foundation...

Frequent Questions

Join / Linux Training / Board