Distributions
Fedora
Installation
- Installation du driver nVidia propriétaire
- Installation du plugin Flash
- Installation de MediaTomb
- Installation de la virtualisation KVM - Qemu
- Installation de Clamav
- Installation des codecs pour l'audio et la video
- Installation du joystick
- Installation du Chromium
- Configurer sendmail avec un relais gmail
- Post-configuration de Thunderbird
- Post-configuration d' Apache
- Emulateur Wine
- Bascule de Netfilter/Iptables à Firewalld
- Modifier le nom d'hôte
- Installation de boinc
Gestion des problèmes
- Reconstruction de la base RPM
rm -f /var/lib/rpm/__db* && rpm --rebuilddb
Systemd
SELinux
- Comprendre SELinux
DVD-Rip
- Utiliser Mencoder pour extraire et encoder un DVD
- Utiliser Mencoder pour extraire et encoder la piste audio d'une video
- Matroska
Graphismes
Dépôts Additionnels
RPM Fusion
- Nom : RPM Fusion
- Public : Pour tous (indispensable)
- Description : RPM Fusion fournit de nombreux logiciels très utiles qui ne peuvent être inclus au sein du Projet Fedora pour une raison ou une autre. Il existe une distinction entre libre (free) et non-libre (nonfree).
- URL : http://rpmfusion.org/
- Support : http://bugzilla.rpmfusion.org/
- Architecture(s) : i386, x86_64
- Parcourir : http://download1.rpmfusion.org/
La section libre contenant des programmes dont la licence est compatible avec le Projet Fedora mais ayant une partie de code soumise à des brevets logiciels (interdit dans le logiciel libre au États-Unis).
La section non-libre contenant les programmes redistribuables mais ayant une licence propriétaire
Remarque(s) : Ce dépôt a le même cycle de vie que la distribution, c'est-à-dire qu'il reste accessible mais inactif pour une version N un mois après la sortie de la version N+2. Il est distinct du Projet Fedora mais respecte les mêmes règles d'empaquetage (hormis les restrictions sur les licences). Ce dépôt est la réunion des dépôt livna, dépôt freshrpms et du dépôt Dribble. Il est possible de garder ces dépôts bien que l'ensemble des paquets soient sensés être mis à jours, seul <paquet>libdvdcss</paquet> qui permet de lire les DVD du commerce reste sur le dépôt livna.
Configuration automatique pour Fedora 17, 18 et 19
RPM Fusion libre
yum install --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
RPM Fusion nonlibre (suppose que le dépôt « libre » précédent a été ajouté)
yum install --nogpgcheck http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm
Configuration automatique pour Rawhide
RPM Fusion libre
# yum install --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-rawhide.noarch.rpm
RPM Fusion nonlibre (suppose que le dépôt libre précédent a été ajouté)
# yum install --nogpgcheck http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-rawhide.noarch.rpm
Fedora Remix
The Remix is a distribution comprised of software packages from the Fedora ARM project, plus a small number of additional packages that are modified from the Fedora versions or which cannot be included in Fedora due to licensing issues – in particular, the libraries for accessing the VideoCore GPU on the Raspberry Pi.
What is the Raspberry Pi Fedora Remix?
The Remix is a distribution comprised of software packages from the Fedora ARM project, plus a small number of additional packages that are modified from the Fedora versions or which cannot be included in Fedora due to licensing issues – in particular, the libraries for accessing the VideoCore GPU on the Raspberry Pi.
The SD card image for the Remix includes a little over 640 packages, providing both text-mode and graphical interfaces (LXDE/XFCE) with an assortment of programming languages, applications, system tools, and services for both environments. There are over 16,000 software packages available from the Fedora ARM repositories which can be easily installed using the Internet to customize your system to meet your needs and interests (again, using either command-line or graphical tools).
Some of the highlights of the software included in the SD card image:
- Programming languages: python, perl, ruby, bash
- Version control: git
- System administration tools (command line and/or graphical) for configuring various aspects of the system including the network, date/time, users, and printers
- Command-line and graphical tools for installing/removing/updating software
- ssh (secure remote login) and printer services
- Graphical applications: word processing (AbiWord), spreadsheets (Gnumeric), image editing (GIMP), and web browsing (Firefox)
- Editors for programming: vim (text mode) and gedit with plugins for file management, terminal, and python console (graphical mode)
The installer automates the process of downloading the image, decompressing it, and installing it onto an SD card.
yum install fedora-arm-installer
To use it:
- Plug in an SD card.
- Click on the refresh (circle-arrow) buttons to get a list of images and current mirrors and a list of available destination devices.
- Select the image you wish to download (r1) – or, if you’ve already downloaded an image, click Browse to select the file.
- Select the SD card device you wish to write to (Caution! Make sure you don’t write to the wrong device, and make sure the SD card does not contain important data – the selected device will be overwritten!).
- Click Install.
When the installer is done, you’ll have a 1.6 GB image installed on the SD card.
First Boot
For your first boot, this is the recommended system configuration:
- HDMI or DVI-D monitor connected to the HDMI output.
- USB keyboard (and, optionally, mouse) on the USB port.
- Ethernet connection to a DHCP-managed, IPv4 network.
- SD card inserted.
The first time the system boots, the SD card image will be resized to completely fill the card, and then the system will go through a first boot process, prompting you to:
- Set the root (master) password for the system.
- Create a user account and set a password for that account. You should use this account to login to the system.
- Select the system timezone.
- Choose either text or graphical mode as the default for booting.
The system will then start up. If there is no input device (keyboard/mouse) connected during boot, the system will skip these configuration steps and boot directly into character mode interface; the SSH server will be started, and you can login with the default root password of “fedoraarm”.
The Kernel
The Kernel provided in the Remix image is the Raspberry Pi 3.1.9 kernel from GitHub, with a combined Fedora/ Raspberry Pi configuration file. This configuration includes the devices in the System-on-a-Chip, modular support for most USB devices and optional network features, and kernel features expected by Fedora packages, including IPv6.
Raspberry Pi Libraries
The Raspberry Pi proprietary libraries, headers, and utilities, included in /opt/vc in the Debian image, are installed into regular system locations in the Fedora Remix image (/usr/lib for libraries, /usr/include for headers, and /usr/bin and /usr/sbin for utilities). This reflects the fact that these files are part of the core distribution and not a third-party add-one.
The source code for the demonstration multimedia apps is contained in the /usr/share/vc-demo-source directory. Instructions for compiling and using these apps is on the Raspberry Pi Fedora Remix wiki documentation (see link, below).
Repositories
The kernel, GPU firmware, start-up scripts, and proprietary libraries/headers/demo source are all provided by RPM packages. This software, along with all of the Fedora packages, can be installed/removed/reinstalled/updated from online software repositories. This means that if new GPU firmware or multimedia libraries become available, they can be installed with a simple update command (“yum update”) or a mouse click on the graphical software updater.
The Remix is distributed as four separate pieces, carried by three separate mirror networks:
- The SD card image files are being mirrored by the Raspberry Pi community’s mirror network.
- The Velocix content delivery network is mirroring the installer program plus the Raspberry Pi-specific remix package repositories.
- The Fedora mirror network is mirroring the Fedora ARM package repositories.
Many thanks to Liam Fraser and the sites comprising the three mirror networks.
The Future of the Raspberry Pi Fedora Remix
The Fedora ARM project is hard at work building Fedora 17, which we hope to release concurrently with the PC versions in May. This should be the most complete Fedora ARM release produced to date.
Students in the SBR600 course at Seneca College are working to on an improved version of the Remix incorporating files from Fedora ARM 17, and this will also be released in May.
The Fedora ARM project has the goal of achieving primary architecture status during the Fedora 18 development cycle — which means that, from that point on, the ARM build of Fedora will receive the same priority and be released on the same schedule as the PC (x86) versions.
As this project progresses, we anticipate moving most of the Raspberry Pi specific software packages into the main Fedora ARM project, except where prevented by licensing issues. More Information
Release notes, information on where/how to get help or to get involved, FAQ about the Remix, and more are on the Seneca CDOT wiki at http://cdot.senecac.on.ca/raspberrypi.
A Quick Word on Trademarks
This software distribution is counted as a “Fedora Remix” in the terminology of the Fedora project because it contains software not found in the Fedora package collection. Please do not refer to the Remix as “Fedora” or use the Fedora infinity logo or wordmark in conjunction with the remix – please refer to it as a “Fedora Remix” and use the secondary mark in accordance with the Fedora Trademark Guidelines. (Note that we have specific approval to use the Secondary Mark with a modified colour scheme to match the Raspberry Pi logo).
Website
http://www.raspberrypi.org/archives/805
CentOS
Différences entre deux versions
CentOS 6 et CentOS 7
- Le firewall est maintenant géré par le daemon Firewalld qui est une surcouche à iptables, ebtables, etc...
- Systemd remplace les traditionnels sysVinit et Upstart
- Systemd est le daemon principal de pid 1
- Journalctl est l'utilitaire de visualisation des logs systèmes
- Hostnamectl est l'utilitaire de gestion de nom d'hôte
- Localectl est l'utilitaire de gestion de langue et de disposition clavier
- Timedatectl est l'utilitaire de gestion de la date/heure et du fuseau horaire
- NetworkManager est maintenant la norme (bien que l'ancien système fonctionne encore) et supporte les bridges.
- Partitions en RAM (tmpfs) pour les points de montage /tmp, /run (lien /var/run -> /run), etc ... Le contenu de ces répertoire ne survit donc pas à un redémarrage.
Le stockage temporaire <path>/var/tmp</path> doit être utilisé pour les donn"es temporaires nécessitant de survivre au redémarrage.
Dépôts Additionnels
CentOS 5
- RpmForge
- i386
wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm && yum localinstall --nogpgcheck rpmforge-release-0.5.2-2.el5.rf.i386.rpm
- x86_64
wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm && yum localinstall --nogpgcheck rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
- i386
- Epel
wget http://mir01.syntis.net/epel/5/i386/epel-release-5-4.noarch.rpm && yum localinstall --nogpgcheck epel-release-5-4.noarch.rpm
- Percona
wget http://www.percona.com/downloads/percona-release/percona-release-0.0-1.x86_64.rpm
- b2pweb
- LAN:
rpm -Uvh http://koji.b2pweb.com/packages/b2pweb-release/1.3.0/1.el5.centos/noarch/b2pweb-release-1.3.0-1.el5.centos.noarch.rpm
- Cloud:
rpm -Uvh http://koji.b2pweb.com/packages/b2pweb-release/1.3.0/1.el5.centos/noarch/b2pweb-release-prod-1.3.0-1.el5.centos.noarch.rpm
- LAN:
- vbox
wget http://download.virtualbox.org/virtualbox/rpm/el/virtualbox.repo -O /etc/yum.repos.d/virtualbox.repo
- spacewalk-client
wget http://spacewalk.redhat.com/yum/2.0-client/RHEL/5/i386/spacewalk-client-repo-2.0-3.el5.noarch.rpm && yum localinstall --nogpgcheck spacewalk-client-repo-2.0-3.el5.noarch.rpm
CentOS 6
- RpmForge
- i686
wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.i686.rpm && yum localinstall --nogpgcheck rpmforge-release-0.5.2-2.el6.rf.i686.rpm
- x86_64
wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm && yum localinstall --nogpgcheck rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
- i686
- Epel
wget http://mirrors.ircam.fr/pub/fedora/epel/6/i386/epel-release-6-8.noarch.rpm && yum localinstall --nogpgcheck epel-release-6-8.noarch.rpm
- Percona
wget http://www.percona.com/downloads/percona-release/percona-release-0.0-1.x86_64.rpm
- b2pweb
- LAN:
rpm -Uvh http://koji.b2pweb.com/packages/b2pweb-release/1.3.0/1.el6/noarch/b2pweb-release-1.3.0-1.el6.noarch.rpm
- Cloud:
rpm -Uvh http://koji.b2pweb.com/packages/b2pweb-release/1.3.0/1.el6/noarch/b2pweb-release-prod-1.3.0-1.el6.noarch.rpm
- LAN:
- vbox
wget http://download.virtualbox.org/virtualbox/rpm/el/virtualbox.repo -O /etc/yum.repos.d/virtualbox.repo
- spacewalk-client
wget http://spacewalk.redhat.com/yum/2.0-client/RHEL/6/i386/spacewalk-client-repo-2.0-3.el6.noarch.rpm && yum localinstall --nogpgcheck spacewalk-client-repo-2.0-3.el6.noarch.rpm
CentOS 7
- Epel
rpm -Uvh http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-2.noarch.rpm
- b2pweb
- LAN:
rpm -Uvh http://koji.b2pweb.com/packages/b2pweb-release/1.4.0/1.el7.centos/noarch/b2pweb-release-1.4.0-1.el7.centos.noarch.rpm
- Cloud:
rpm -Uvh http://koji.b2pweb.com/packages/b2pweb-release/1.4.0/1.el7.centos/noarch/b2pweb-release-prod-1.4.0-1.el7.centos.noarch.rpm
- LAN:
- Rpmforge
rpm -Uvh http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.3-1.el7.rf.x86_64.rpm
Installation de Java et Ant
Ant 1.8.2
rpm -Uvh http://mirrors.dotsrc.org/jpackage/6.0/generic/free/RPMS/jpackage-release-6-3.jpp6.noarch.rpm yum install ant ant-contrib
