About Linux Distributions - Owl River · binary RPMs, different from OpenSuSE (the SuSE beta) which...

ibm.comibm.com/open/open || || ibm.comibm.com/linux/linux

Linux Distributions

Linux, Open Standards ConsultantIBM Corporation

What they are, how they work, which one to choose

Avi Alkalay <Avi Alkalay <[email protected]@br.ibm.com>>+55-11-2132-2327+55-11-2132-2327


What is a Linux Distribution

Ecosystem

A set of packaged software (as RPM files) with the distro's digital signature

An installation program, which is by himself one of

the packaged software

People that build value networks with SW and HW vendors, community, etc

( )( )( )


What are RPM Packages

A core OS technology created to ease software management

Similar to a ZIP file, plus meta-information like sw version, description, installation date, etc

Responsible for sw installation, deinstallation and upgrades

Makes consistency checks for different components inter-relations and dependencies

Provides automatic execution of custom scripts before and after a sw is (de)installed

Provides file corruption check mechanism


“The Best Linux Distribution”


Fact 1: All Enterprise* Linux distributions are excellent

Fact 2: All Enterprise Linux distributions fulfill real world needs

*Talking about Red Hat Enterprise Linux and SLES


Fact 3: To choose a Linux distribution is more like to

choose a tomato sauce

(it is more related to personal taste and proximity to you, than to the quality of the product)


1. Which distro provider I have closer commercial relations with ?

2. Which distro I like more ?

3. Who has best price ?

4. Which distro is recommended by the ISV sw and IHV hw of some specific project ?

5. Unless you know what you are doing, be responsible and use an Enterprise distribution

Important Things to Think About


Fact 4: To use at most 2 distributions is not a bad thing

There are not big technical differences between them. A RHEL sysadmin can handle SLES too, and vice-versa

Diversity provides choice, and make providers fight for you, in quality and in price

The magic number is 2. Not 1. Not 3.


Whats the best distro ?

Instead of asking:

What is the best distribution for my company and my specific project ?

Start thinking about:


What Customers look for on Enterprise Distributions ?

1. A partner available now and in the long term, to transfer operational risks

2. Fast access to quality updates

3. Large set of compatible HW and ISV sw

4. Availability of pre-tested complex solutions ecosystem

They look for 'support', which really means:


Popular DistributionsAspects of Red Hat, SuSE, Fedora, OpenSuse, Debian, etc


SLES RHEL↑ ↓

↔ Stick with what already works ↔

↓ ↑

↓ ↑

↓ ↑

↓ Not all source packages available to the public ↑ All source packages available to the public

↑ ↓

↔ ↑ Strong ecosystem established

↔ ↔

Include Java, Flash and other popular no-cost closed-source software

Strict policy to include only Open Source and patent-free software

Include last stable innovations from the Open Source world

Uncommon interpretation of standards like the FHS, LSB, jpackage

Common sense strict conformance to Linux standards, including jpacakge

Naming conventions (packages, folders, filenames, etc) have some “SuSE” signature

Naming conventions are generic and Red Hat-independent

Different source packages (kernel, libc, etc) for different architectures

Same source packages across all platforms, with intelligent build system

Unified, componentized and more complete configuration tools via YaST, for TUI and GUI

Small separate configuration tools for the generic situations, mostly for GUI

Building an ecosystem of ISVs, IHVs and users

Company: High level products like mail server, firewall, etc, plus Novell closed-source products, including Java MW

Company: PostreSQL, Java MW, and infrastructural products like GFS, Cluster System, Directory Server, all OSS

↑ favorable ↓ unfavorable ↔ goot to know


SuSE and Red Hat testbed for next enterprise versions

Same flavor of their mother “E” distributions

Available only on some platforms (ia32, x86_64)

Not commited to build an ecosystem of ISVs and IHVs

Not commited to stability

Open development and testing with community help

OpenSuSE and Fedora Linux


CentOS LinuxA very special Linux distribution


Fact: CentOS is byte-identical to Red Hat Enterprise Linux


Made possible because Red Hat has in their strategy that all they write must be Open Source, including build process, integration, debugging methods, etc. So...

...to be Open Source means to be reproducible

Available on all platforms (ia32, x86_64, ia64, s390x, ppc)

Binary RHEL-ready hw drivers, are technically CentOS-ready too

ISV sw for RHEL behaves exactly the same on CentOS

Coherent version numbersCentOS 3.2 equals to RHEL 3 update 2

CentOS Aspects


But how CentOS does that ?

Answer is in the core of how the RPM technology works, and on how RHEL

source-packages are deployed


RPM: The Raw Source Code

The base original thing to start with Collection of sources in C, C++, documentation, etc Published with a version number on the sw home page Use to be difficult to compile, and needs customizations


Apache Web Server source code being distributed on his web site: generic and not flavored to any distribution

RPM: The Raw Source Code

GZipped TAR is an archive format similar to ZIP, but better

Includes all Apache source in C language, documentation etc


RPM: The Distribution-specific Patches

Modifications to the original source code Distribution bug fixes Distribution specific addons, additional sources, plugins Backports of advanced, next-generation features


RPM: The RPM Specification (spec) File

Package summary, description, version, release, etc The pre-install, post-install, etc scripts How to integrate patches and sources, and compile all Where to install the compiled files on the filesystem


RPM: The Source-RPM File

SOURCE RPM

All three components grouped in one distributable file Source-RPMs are automatic cooking machines They contain, in open formats, all the flavor a distribution

wants to give to certain software


RPM: Source-RPM Files

Use to be freely distributable under GPL license

RHEL 4AS updated Apache (httpd), Kernel and other source-RPMs: freely available on Red Hat's FTP server


RPM: The Build Proccess

rpmbuild

SOURCE RPM

A standard single rpmbuild command generates the installable RPM file

No logic, customization, brain or magic is needed in this step

rpmbuild –-rebuild some-package.src.rpm


RPM: The Generated RPM File

rpmbuild

SOURCE RPM

The RPM file is generated with distro's digital signature

The usable RPM file use to be not freely-distributable on commercial distributions


SuSE is a commercial distribution which doesn't provide binary RPMs, different from OpenSuSE (the SuSE beta) which provides RPMs

Some binary RPMs freely available from a free distribution: OpenSuSE

RPM: The Generated RPM File


rpmbuild CentOS' RPM

=

RPM: Designed to Rebuild on Any System

rpmbuild

SOURCE RPM

Red Hat's RPM

Code tunning and change cycle


1. A partner available now and in the long term to transfer operational risks↓Not provided by CentOS

2. Fast access to quality updates↔A few hours delay compared to RHEL

3. Large set of compatible HW and ISV SW↑Technically inherited from RHEL, but informal

4. Access to pre-tested complex solutions ecosystem↑Technically inherited from RHEL, but informal

CentOS and our Support Chart

Customers look for these 'support' aspects:


Linux, Open Standards ConsultantIBM Corporation

Avi Alkalay <Avi Alkalay <[email protected]@br.ibm.com>>11-2132-232711-2132-2327

Thank You !


Sobre a Apresentação➢ Sumário

Linux e Padrões Abertos estão mudando a forma como empresas compram e usam tecnologia. A apresentação mostra a relação entre tecnologias como Linux, Java, XML, HTML, etc, o comprometimento da IBM com sua evolução, caminhos estratégicos, e como clientes estão tendo sucesso com seu uso. Linux no desktop, vantagens e desvantagens, verdades e mitos.

➢ Summary :: An Open Source techie guy in the corporate worldAvi Alkalay is an Open Source techie guy that the destiny made him work at the IBM Linux Impact Team, dealing with the heavy corporate clients. So he had to learn how to talk about Linux and Open Source with more responsability, leaving the religious aspects of the technology at home. From this experience, he learned how to effectively sell Linux, Open Source and Open Standards solutions, best practices, what open source techie guys can and cannot say to customers, when the Open Source model works and when it doesn't (from a business perspective), and how to increase Linux popularity inside corporations, not only in the infrastructure side of the IT, but also in the core business, ERPs, etc, and also a mature vision of the status of Linux as a corporate desktop.

➢ ApresentadorAvi Alkalay é consultor de Linux e Padrões Abertos na IBM. É ativo na comunidade Open Source, contribuindo software para diversos projetos. Trabalhou com praticamente todas as tecnologias da Internet, desde a sua alvorada, atuando hoje como arquiteto em soluções de e-business, e ajudando clientes a migrarem seus processos p/ Padrões Abertos.

➢ Apresentador (outra opção)Consultor de Linux e Open Source. Expert em soluções baseadas em Linux e padrões abertos, tendo ajudado clientes a migrarem para tal, considerando aspectos culturais, comerciais, e tecnológicos de seus contextos. Contribui para a comunidade de Software Livre com idéias e código, tendo um amplo conhecimento de seu dinamismo, vantagens e desafios. É membro do grupo de desenvolvimento de Linux no Desktop interno da IBM, com foco em interfaces com o usuário. Foi responsável pela segurança corporativa de Internet da IBM Brasil, e atualmente empenha-se na evangelização do uso racional de Padrões Abertos.


RPM: The Whole Process

rpmbuild

SOURCE RPM


Players do Desktop Linux

About Linux Distributions - Owl River · binary RPMs, different from OpenSuSE (the SuSE beta) which...

Documents

Transcript of About Linux Distributions - Owl River · binary RPMs, different from OpenSuSE (the SuSE beta) which...