Fedora-Fr - Communauté francophone Fedora - Linux

Planet de Fedora-Fr : la communauté francophone autour de la distribution Linux Fedora

A propos

Cette page est actualisée toutes les heures.

Cette page est une sélection de blogs autour de Fedora. Fedora-Fr.org décline toute responsabilité au sujet des propos tenus par les auteurs des blogs de ce planet. Leurs propos sont leur entière responsabilité.

Le contenu de ce planet appartient à leurs auteurs respectifs. Merci de consulter leur blogs pour obtenir les licences respectives.

Mot-clefs : Général

GDM Fedora 9 et l'auto-login

Pierre-Yves Chibon

source.png

How to active the auto-login feature in GDM under Fedora 9

Comment activer l'auto-login de GDM sous Fedora 9

French version (English below)

Comme j'ai eu la question hier et que j'ai eu quelques minutes aujourd'hui (et il ne m'en a pas fallut tellement plus) ! Je me suis penché sur la question de l'auto-login dans GDM sous Fedora 9.

L'auto-login est une fonctionnalité qui pour des questions de sécurité est relativement discutée/soumise à controverse, faites y attention en l'utilisant !

La solution c'est de faite révélée assez simple et très facile à mettre en oeuvre, je vous la livre donc :-)

Attention, pareil qu'hier, ceci s'adresse à des personnes sachant comment faire pour revenir à la situation initiale en ligne de commande si besoin est !

  1. Aller dans le dossier /etc/gdm/
cd /etc/gdm
  1. Faire une copie de sauvegarde du fichier gdm.schemas
cp gdm.schemas gdm.schemas.sav
  1. Entrer dans le fichier gdm.schemas et trouver cette séquence:
<schema>
  <key>daemon/AutomaticLoginEnable</key>
  <signature>b</signature>
  <default>false</default>
</schema>
<schema>
  <key>daemon/AutomaticLogin</key>
  <signature>s</signature>
  <default></default>
</schema>
  1. La remplacer par :
<schema>
  <key>daemon/AutomaticLoginEnable</key>
  <signature>b</signature>
  <default>true</default>
</schema>
<schema>
  <key>daemon/AutomaticLogin</key>
  <signature>s</signature>
  <default>monUser</default>
</schema>

Et voila c'est tout :-) Ctrl+alt+retour pour tester et vous avez finis ;-)



English version

Since the question raised yesterday and I had few minutes today (it really did not take me more). I have looked at the auto-login feature in the GDM of Fedora 9.

The auto-login feature is quite controversy for security reason, please be aware of this while using it !

The solution is rather simple so there is the explanation:

Like yesterday watch out that you should be aware of what you are doing and you should know how to reverse the change you have made without graphical interface !

  1. Go to the folder /etc/gdm/
cd /etc/gdm
  1. Do a backup copy of the file gdm.schemas
cp gdm.schemas gdm.schemas.sav
  1. Open the file gdm.schema and find this piece of xml:
<schema>
  <key>daemon/AutomaticLoginEnable</key>
  <signature>b</signature>
  <default>false</default>
</schema>
<schema>
  <key>daemon/AutomaticLogin</key>
  <signature>s</signature>
  <default></default>
</schema>
  1. Change it to:
<schema>
  <key>daemon/AutomaticLoginEnable</key>
  <signature>b</signature>
  <default>true</default>
</schema>
<schema>
  <key>daemon/AutomaticLogin</key>
  <signature>s</signature>
  <default>myUser</default>
</schema>

There you go, ctrl+alt+backspace to test !

Enjoy ! ;-)

Changer le GDM de Fedora 9

Pierre-Yves Chibon

source.png

How to change F9's gdm background

Comment changer le fond d'écran gdm de F9

French version

Les amateurs de la personnalisation au maximum de Fedora ont sans doute été déçut par Fedora 9 qui intégrant la dernière version de gdm lors de sa sortie a perdu la possibilité de personnalisé son fond d'écran.

Aujourd'hui et quelques recherches plus tard j'ai trouvé comment faire et je vous livre la méthode clé en main

Attention, ceci s'adresse à des personnes sachant comment faire pour revenir à la situation initiale en ligne de commande si besoin est !

  1. Trouver l'image

(Ça je vous laisse faire)

  1. Crée un dossier qui contiendra l'image:
mkdir /usr/share/backgrounds/myTheme
  1. Y déposer vos images aux différentes résolutions
cp /home/user/undossier/vers/monImage.800.png /usr/share/backgrounds/myTheme
cp /home/user/undossier/vers/monImage.1280.png /usr/share/backgrounds/myTheme
cp /home/user/undossier/vers/monImage.1600.png /usr/share/backgrounds/myTheme
cp /home/user/undossier/vers/monImage.1920.png /usr/share/backgrounds/myTheme
  1. Écrire le fichier xml myTheme.xml pour afficher les images
<background>
<static>
<duration>86400.0</duration>
<file>
        <!-- Eeepc size --> <!-- 5:3 -->
        <size width="800" height="480">/usr/share/backgrounds/myTheme/monImage.800.png</size>
        <!-- Odd resolution but apparently popular --> <!-- 5:4 -->
        <size width="1280" height="1024">/usr/share/backgrounds/myTheme/monImage.1280.png</size>
        <!-- Standard 4:3 -->
        <size width="1600" height="1200">/usr/share/backgrounds/myTheme/monImage.1600.png</size>
        <!-- Widescreen 16:10 -->
        <size width="1920" height="1200">/usr/share/backgrounds/myTheme/monImage.1920.png</size>
 </file>
 </static>
 </background>
  1. Restaurer le context SELinux pour éviter des problèmes
restorecon -r /usr/share/background/myTheme
  1. Vérifier les contextes par ls -Z et en cas de besoin
chcon -R system_u:object_r:usr_t:s0 myTheme/
  1. Ensuite on va dire à gdm de prendre en compte ce theme:
  2. D'abord copie de sauvegarde
cp /etc/gconf/gconf.xml.defaults/%gconf-tree.xml /etc/gconf/gconf.xml.defaults/%gconf-tree.xml-old
  1. Changer le fichier de gdm
vim /etc/gconf/gconf.xml.defaults/%gconf-tree.xml

À la ligne 6622 (faites une recherche sur waves) changer:

<stringvalue>/usr/share/backgrounds/waves/waves.xml</stringvalue>

par

<stringvalue>/usr/share/backgrounds/myTheme/myTheme.xml</stringvalue>

Voila il ne vous reste plus qu'à redémarrer votre serveur graphique (ctrl+alt+retour) et à profiter de votre nouveau fond d'écran pour voter gdm :-)



Sources:
FedoraForum
HackTux



English version

Those who like to personalize their Fedora at maximum must have been disappointed by Fedora 9 which by included the latest version of gdm available when it came out lost the possibility to change the background picture on the gdm.

After few research I found the way to change it.

Watch out that you should be aware of what you are doing and you should know how to reverse the change you have made without graphical interface !

  1. Find the picture

(That's your job ! ;-) )

  1. Create the folder that will contain the pictures
mkdir /usr/share/backgrounds/myTheme
  1. Copy the pictures in there at the different resolutions
cp /home/user/undossier/vers/myPicture.800.png /usr/share/backgrounds/myTheme
cp /home/user/undossier/vers/myPicture.1280.png /usr/share/backgrounds/myTheme
cp /home/user/undossier/vers/myPicture.1600.png /usr/share/backgrounds/myTheme
cp /home/user/undossier/vers/myPicture.1920.png /usr/share/backgrounds/myTheme
  1. Write the file myTheme.xml to configure the display of the pictures
<background>
<static>
<duration>86400.0</duration>
<file>
        <!-- Eeepc size --> <!-- 5:3 -->
        <size width="800" height="480">/usr/share/backgrounds/myTheme/monImage.800.png</size>
        <!-- Odd resolution but apparently popular --> <!-- 5:4 -->
        <size width="1280" height="1024">/usr/share/backgrounds/myTheme/monImage.1280.png</size>
        <!-- Standard 4:3 -->
        <size width="1600" height="1200">/usr/share/backgrounds/myTheme/monImage.1600.png</size>
        <!-- Widescreen 16:10 -->
        <size width="1920" height="1200">/usr/share/backgrounds/myTheme/monImage.1920.png</size>
 </file>
 </static>
 </background>
  1. Restore the SELinux context to avoid problem
restorecon -r /usr/share/background/myTheme
  1. Check those via ls -Z and if needed run
chcon -R system_u:object_r:usr_t:s0 myTheme/
  1. Now we are going to explain to gdm which theme to take into account:
  2. First backup !
cp /etc/gconf/gconf.xml.defaults/%gconf-tree.xml /etc/gconf/gconf.xml.defaults/%gconf-tree.xml-old
  1. Then we change the gdm file:
vim /etc/gconf/gconf.xml.defaults/%gconf-tree.xml

At row 6622 (search on waves) change:

<stringvalue>/usr/share/backgrounds/waves/waves.xml</stringvalue>

to

<stringvalue>/usr/share/backgrounds/myTheme/myTheme.xml</stringvalue>

There we go, restart your X and enjoy your new gdm theme !! ;-)



Sources:
FedoraForum
HackTux

R2spec nouvelle version !

Pierre-Yves Chibon

rpm.pngsource.png

R2spec, the latest release, full of features !

R2spec, une nouvelle version pleine de surprises !

English version

There is the latest version of R2spec, I have been working quite a bit on it with the suggestion of faceface from #R on irc.freenode.net to improve this software. Therefore the changelog for this new release is quite long and the list of features added seems also important.

The principle is still the same: make R packages as simple as possible.

Seems there are mainly two sources of libraries for R (Bioconductor and the CRAN) I added two options (--bioc and --cran) that add the Source0 and the URL in the spec file if it has not been defined by the --url option.

From that I aslo considered the case of the noarch packages, it now looks for *.c, *.C, *.cp, *.cpp, *.f and *.F files, if it does not find any it consider the package as noarch and thus adapt the specfile for that.

It also offers the possibility to move the source to %_topdir (defined in ~/.rpmmacros) so that you can directly run the rpmbuild -ba once you have made the small correction advised on the spec file.

That's the main features added, you can see below the changelog for this new release and you can always test and give feed back, report bugs and suggest enhancement on the trac of the R2spec project

The RPMs and sources are available on the git of the R2spec project.

Thanks for your attention ;-)


French version

Voici la dernière version de R2spec, j'ai pas mal bossé dessus notamment grâce aux suggestions de faceface de #R sur irc.freenode.net. Le programme c'est pas mal améliorer et le journal des changements sur cette version est donc plutôt long.

Le but de ce programme est toujours le même, rendre la création de paquet de bibliothèque R le plus simple possible.

Puisqu'il y a majoritairement deux sources pour les bibliothèques R (Bioconductor et le CRAN) j'ai ajouté deux options (--cran et --bioc) qui permettent de définir les Source0 et URL du fichier spec s'ils n'ont pas été déjà définis par l'option --url.

J'ai aussi pris en compte le cas des paquets noarch en cherchant dans les sources des fichiers *.c, *.C, *.cp, *.cpp, *.f et *.F. S'il n'en trouve aucun le paquet est considéré comme noarch et le fichier spec est donc modifié en conséquence.

Cette version offre aussi la possibilité de déplacer le tarball dans le %_topdir (définis dans le ~/.rpmmacros) pour que l'on puisse faire facilement rpmbuild -ba une fois que l'on a fais les petits changements recommandé dans le fichier spec.

Voila pour les principales fonctionnalités ajoutées dans cette version. Ci-dessous ce trouve le changelog et bien entendu bugs, demande d'amélioration et retour sur son fonctionnement sont les bienvenus ici ou sur le trac du projet R2spec.

Les RPMs et le sources sont disponible sur le git du project R2spec.

Merci et bon dimanche ! ;-)



Version 2.5.0 -- 31th Aug 2008
-Features added 
  * Add a file INSTALL 
  * Add the --bioc option for bioconductor packages 
      - Fill the source0 if -s is not used
      - Fill the url
  * Add the --cran option for cran packages
      - Fill the source0 if -s is not used
      - Fill the url
  * Add %define BioC for the Bioconductor release of Bioconductor packages
  * Add check if the package is noarch or not
  * Add oportunity to copy the source in the %_topdir defined in .rpmmacros
  * Add a parameter in the config file for the version on Bioconductor used
  * Add a Spec class to write the spec file
  * Add a Noarch class that inherit the Spec class and handle the noarch package case
  * Ask what to do if the specfile is alreay in the current working directory

-Bugs correction
  * Catch the Description in the file DESCRIPTION when it is on several lines
  * Catch the Depends and Suggests when they are on several lines
  * Now it does load the info from the config file
  * Fix some layout in this file

French Fedora Documentation

Pierre-Yves Chibon

Presentation of the French Community Documentation on Fedora

Présentation de la documentation Fedora en français -- (pas de version française de cet article).

English version

From our talk with Max, couples of weeks ago one idea that come up was to advertise a bit more on the French community documentation that we've been writing for 4 years. To do so, I just want to introduce it to you quickly with this post.

This documentation is hosted on the fedora-fr server under the url http://doc.fedora-fr.org. Therefore, It has no link with the official Fedora Project (and clearly claims it).

= The principle =

This documentation is powered by mediawiki. The writers are people from the community that one day chose to write something about a subject or a problem they have been busy with.

When you want to contribute the rules are pretty simple. You subscribe to the French documentation mailing-list, show up, present yourself with few words (giving your first and last name) and from this presentation the admin of the documentation opens you an account on the wiki.

The first and last name are mandatory in the document since all the accounts are of the type 'FirstNameLastName'. This is also in order that people contribute under their name not their nickname. What we want to achieve here is that people that get involved feels they are involving themselves not an anonymous, but as the person they are. We consider it as a personal involvement.

One of the first thing you should do when you have an account is filling your user's page with few words to introduce yourself.

Once you are a member of the team and you have your account, you can directly correct the articles for minor changes (typo, spelling mistakes...), however for major changes on the structure of an article or to suggest a new article you first have to show up in the mailing list: "Hey dude, I would like to write something about that, I am thinking to use the following structure, any advice ?"

This helps to discuss a bit more the content of some articles, it also allows to control the content of the documentation but as you will see later the content of the documentation is rather broad and the number of suggestions that have been refused since I am in the team (January 2007) is really low (I can't remember any actually...), and when it happens it is because it is considered that there is already enough howto available on the net and the subject is not clearly related to Fedora.

If there are no remarks against your proposal you can start to write your article directly, you have to set the template "In progress" and to add it to the corresponding table. For the layout there are clear guidelines on how to write an article in order to keep a coherent structure overall the documentation.

When the article is finished, you ask for a review by removing it from the table "In progress" and adding it to the table "Waiting for review". There someone picks it up, corrects the spelling, can ask question if he does not understand or wants more. At the end, He is the one that publish the article and remove it from the table.

To conclude about the principles let's summary them:

  • Involving yourself (give your first and last name), is the only constraint to register
  • Present yourself in your user's page
  • Major change and new articles are presented and debated on the mailing list
  • Use the guideline when you are writing
  • Do not forget to add it in the right table and to use the right categories.

= The documentation =

I introduced you the main principle to become a member of the French documentation team, the main idea was to explain you how it works here before introducing you what are the results of this organization.

The results are:

  • 84 members
  • 316 pages
  • 27 categories

That's for the figures. But more than the figure what's interesting are the contents.

Here follows some of the pages that attract lot's of people:

There are also some documentation about other subjects:

I should not forget to speak about the large category of the wiki about the games ! Those 35 articles explain what are the games available and how to install them (they do not explain how you should enjoy them ;-)" class="smiley )

There is also a pdf version of the documentation for offline use when you are in the train trying to set up your wireless :-D" class="smiley (Thanks Pascal for that !)

= Conclusion =

I tried to introduce you some of the main features of this documentation and the principle that we used to set it up. Basically it is a documentation made by users for users, it quite often relies on subject/question that have been seen often on our forum (and I could say: "so often that at the end someone want to write something about it in order to not keep repeating himself").

We do realize that we are lucky with the team of people we have there. I should point out people like Nicolas who wrote most of the documentation about the configuration of the wireless cards or Hervé who was there at the beginning and gave us very good article on subject like GRUB, or Patrice who's knowledge on real time processing is so high that we had trouble to find people able to review his article before publication ;-)" class="smiley There are too many people so that I can't mention them all (I apologize to those that I did not) but I can't do but mention Johan who is the leader of the French documentation, he is the one that keep bothering everyone on the mailing list in order to obtain this result of quantity and quality ! Thanks ! ;-)" class="smiley

So there I am, I hope you did not get bored. As I explained my goal was just to introduce what the French community has been writing for the past years. If you are interesting in the content I would guess that google translate is probably not perfect and would need some work to make something out of it, but at least it gives you an idea :-D" class="smiley

Thanks for reading me up to there ! Enjoy your reading !! :-D" class="smiley

I also would like to thank Thomas the French community leader whose help is also really appreciated :D

French Fedora Documentation

Pierre-Yves Chibon

Presentation of the French Community Documentation on Fedora

Présentation de la documentation Fedora en français -- (pas de version française de cet article).

English version

From our talk with Max, couples of weeks ago one idea that come up was to advertise a bit more on the French community documentation that we've been writing for 4 years. To do so, I just want to introduce it to you quickly with this post.

This documentation is hosted on the fedora-fr server under the url http://doc.fedora-fr.org. Therefore, It has no link with the official Fedora Project (and clearly claims it).

= The principle =

This documentation is powered by mediawiki. The writers are people from the community that one day chose to write something about a subject or a problem they have been busy with.

When you want to contribute the rules are pretty simple. You subscribe to the French documentation mailing-list, show up, present yourself with few words (giving your first and last name) and from this presentation the admin of the documentation opens you an account on the wiki.

The first and last name are mandatory in the document since all the accounts are of the type 'FirstNameLastName'. This is also in order that people contribute under their name not their nickname. What we want to achieve here is that people that get involved feels they are involving themselves not an anonymous, but as the person they are. We consider it as a personal involvement.

One of the first thing you should do when you have an account is filling your user's page with few words to introduce yourself.

Once you are a member of the team and you have your account, you can directly correct the articles for minor changes (typo, spelling mistakes...), however for major changes on the structure of an article or to suggest a new article you first have to show up in the mailing list: "Hey dude, I would like to write something about that, I am thinking to use the following structure, any advice ?"

This helps to discuss a bit more the content of some articles, it also allows to control the content of the documentation but as you will see later the content of the documentation is rather broad and the number of suggestions that have been refused since I am in the team (January 2007) is really low (I can't remember any actually...), and when it happens it is because it is considered that there is already enough howto available on the net and the subject is not clearly related to Fedora.

If there are no remarks against your proposal you can start to write your article directly, you have to set the template "In progress" and to add it to the corresponding table. For the layout there are clear guidelines on how to write an article in order to keep a coherent structure overall the documentation.

When the article is finished, you ask for a review by removing it from the table "In progress" and adding it to the table "Waiting for review". There someone picks it up, corrects the spelling, can ask question if he does not understand or wants more. At the end, He is the one that publish the article and remove it from the table.

To conclude about the principles let's summary them:

  • Involving yourself (give your first and last name), is the only constraint to register
  • Present yourself in your user's page
  • Major change and new articles are presented and debated on the mailing list
  • Use the guideline when you are writing
  • Do not forget to add it in the right table and to use the right categories.

= The documentation =

I introduced you the main principle to become a member of the French documentation team, the main idea was to explain you how it works here before introducing you what are the results of this organization.

The results are:

  • 84 members
  • 316 pages
  • 27 categories

That's for the figures. But more than the figure what's interesting are the contents.

Here follows some of the pages that attract lot's of people:

There are also some documentation about other subjects:

I should not forget to speak about the large category of the wiki about the games ! Those 35 articles explain what are the games available and how to install them (they do not explain how you should enjoy them ;-)" class="smiley )

There is also a pdf version of the documentation for offline use when you are in the train trying to set up your wireless :-D" class="smiley (Thanks Pascal for that !)

= Conclusion =

I tried to introduce you some of the main features of this documentation and the principle that we used to set it up. Basically it is a documentation made by users for users, it quite often relies on subject/question that have been seen often on our forum (and I could say: "so often that at the end someone want to write something about it in order to not keep repeating himself").

We do realize that we are lucky with the team of people we have there. I should point out people like Nicolas who wrote most of the documentation about the configuration of the wireless cards or Hervé who was there at the beginning and gave us very good article on subject like GRUB, or Patrice who's knowledge on real time processing is so high that we had trouble to find people able to review his article before publication ;-)" class="smiley There are too many people so that I can't mention them all (I apologize to those that I did not) but I can't do but mention Johan who is the leader of the French documentation, he is the one that keep bothering everyone on the mailing list in order to obtain this result of quantity and quality ! Thanks ! ;-)" class="smiley

So there I am, I hope you did not get bored. As I explained my goal was just to introduce what the French community has been writing for the past years. If you are interesting in the content I would guess that google translate is probably not perfect and would need some work to make something out of it, but at least it gives you an idea :-D" class="smiley

Thanks for reading me up to there ! Enjoy your reading !! :-D" class="smiley

I also would like to thank Thomas the French community leader whose help is also really appreciated :D

French Fedora Documentation

Pierre-Yves Chibon

Presentation of the French Community Documentation on Fedora

Présentation de la documentation Fedora en français -- (pas de version française de cet article).

English version

From our talk with Max, couples of weeks ago one idea that come up was to advertise a bit more on the French community documentation that we've been writing for 4 years. To do so, I just want to introduce it to you quickly with this post.

This documentation is hosted on the fedora-fr server under the url http://doc.fedora-fr.org. Therefore, It has no link with the official Fedora Project (and clearly claims it).

= The principle =

This documentation is powered by mediawiki. The writers are people from the community that one day chose to write something about a subject or a problem they have been busy with.

When you want to contribute the rules are pretty simple. You subscribe to the French documentation mailing-list, show up, present yourself with few words (giving your first and last name) and from this presentation the admin of the documentation opens you an account on the wiki.

The first and last name are mandatory in the document since all the accounts are of the type 'FirstNameLastName'. This is also in order that people contribute under their name not their nickname. What we want to achieve here is that people that get involved feels they are involving themselves not an anonymous, but as the person they are. We consider it as a personal involvement.

One of the first thing you should do when you have an account is filling your user's page with few words to introduce yourself.

Once you are a member of the team and you have your account, you can directly correct the articles for minor changes (typo, spelling mistakes...), however for major changes on the structure of an article or to suggest a new article you first have to show up in the mailing list: "Hey dude, I would like to write something about that, I am thinking to use the following structure, any advice ?"

This helps to discuss a bit more the content of some articles, it also allows to control the content of the documentation but as you will see later the content of the documentation is rather broad and the number of suggestions that have been refused since I am in the team (January 2007) is really low (I can't remember any actually...), and when it happens it is because it is considered that there is already enough howto available on the net and the subject is not clearly related to Fedora.

If there are no remarks against your proposal you can start to write your article directly, you have to set the template "In progress" and to add it to the corresponding table. For the layout there are clear guidelines on how to write an article in order to keep a coherent structure overall the documentation.

When the article is finished, you ask for a review by removing it from the table "In progress" and adding it to the table "Waiting for review". There someone picks it up, corrects the spelling, can ask question if he does not understand or wants more. At the end, He is the one that publish the article and remove it from the table.

To conclude about the principles let's summary them:

  • Involving yourself (give your first and last name), is the only constraint to register
  • Present yourself in your user's page
  • Major change and new articles are presented and debated on the mailing list
  • Use the guideline when you are writing
  • Do not forget to add it in the right table and to use the right categories.

= The documentation =

I introduced you the main principle to become a member of the French documentation team, the main idea was to explain you how it works here before introducing you what are the results of this organization.

The results are:

  • 84 members
  • 316 pages
  • 27 categories

That's for the figures. But more than the figure what's interesting are the contents.

Here follows some of the pages that attract lot's of people:

There are also some documentation about other subjects:

I should not forget to speak about the large category of the wiki about the games ! Those 35 articles explain what are the games available and how to install them (they do not explain how you should enjoy them ;-)" class="smiley )

There is also a pdf version of the documentation for offline use when you are in the train trying to set up your wireless :-D" class="smiley (Thanks Pascal for that !)

= Conclusion =

I tried to introduce you some of the main features of this documentation and the principle that we used to set it up. Basically it is a documentation made by users for users, it quite often relies on subject/question that have been seen often on our forum (and I could say: "so often that at the end someone want to write something about it in order to not keep repeating himself").

We do realize that we are lucky with the team of people we have there. I should point out people like Nicolas who wrote most of the documentation about the configuration of the wireless cards or Hervé who was there at the beginning and gave us very good article on subject like GRUB, or Patrice who's knowledge on real time processing is so high that we had trouble to find people able to review his article before publication ;-)" class="smiley There are too many people so that I can't mention them all (I apologize to those that I did not) but I can't do but mention Johan who is the leader of the French documentation, he is the one that keep bothering everyone on the mailing list in order to obtain this result of quantity and quality ! Thanks ! ;-)" class="smiley

So there I am, I hope you did not get bored. As I explained my goal was just to introduce what the French community has been writing for the past years. If you are interesting in the content I would guess that google translate is probably not perfect and would need some work to make something out of it, but at least it gives you an idea :-D" class="smiley

Thanks for reading me up to there ! Enjoy your reading !! :-D" class="smiley

I also would like to thank Thomas the French community leader whose help is also really appreciated :D

French Fedora Documentation

Pierre-Yves Chibon

Presentation of the French Community Documentation on Fedora

Présentation de la documentation Fedora en français -- (pas de version française de cet article).

English version

From our talk with Max, couples of weeks ago one idea that come up was to advertise a bit more on the French community documentation that we've been writing for 4 years. To do so, I just want to introduce it to you quickly with this post.

This documentation is hosted on the fedora-fr server under the url http://doc.fedora-fr.org. Therefore, It has no link with the official Fedora Project (and clearly claims it).

= The principle =

This documentation is powered by mediawiki. The writers are people from the community that one day chose to write something about a subject or a problem they have been busy with.

When you want to contribute the rules are pretty simple. You subscribe to the French documentation mailing-list, show up, present yourself with few words (giving your first and last name) and from this presentation the admin of the documentation opens you an account on the wiki.

The first and last name are mandatory in the document since all the accounts are of the type 'FirstNameLastName'. This is also in order that people contribute under their name not their nickname. What we want to achieve here is that people that get involved feels they are involving themselves not an anonymous, but as the person they are. We consider it as a personal involvement.

One of the first thing you should do when you have an account is filling your user's page with few words to introduce yourself.

Once you are a member of the team and you have your account, you can directly correct the articles for minor changes (typo, spelling mistakes...), however for major changes on the structure of an article or to suggest a new article you first have to show up in the mailing list: "Hey dude, I would like to write something about that, I am thinking to use the following structure, any advice ?"

This helps to discuss a bit more the content of some articles, it also allows to control the content of the documentation but as you will see later the content of the documentation is rather broad and the number of suggestions that have been refused since I am in the team (January 2007) is really low (I can't remember any actually...), and when it happens it is because it is considered that there is already enough howto available on the net and the subject is not clearly related to Fedora.

If there are no remarks against your proposal you can start to write your article directly, you have to set the template "In progress" and to add it to the corresponding table. For the layout there are clear guidelines on how to write an article in order to keep a coherent structure overall the documentation.

When the article is finished, you ask for a review by removing it from the table "In progress" and adding it to the table "Waiting for review". There someone picks it up, corrects the spelling, can ask question if he does not understand or wants more. At the end, He is the one that publish the article and remove it from the table.

To conclude about the principles let's summary them:

  • Involving yourself (give your first and last name), is the only constraint to register
  • Present yourself in your user's page
  • Major change and new articles are presented and debated on the mailing list
  • Use the guideline when you are writing
  • Do not forget to add it in the right table and to use the right categories.

= The documentation =

I introduced you the main principle to become a member of the French documentation team, the main idea was to explain you how it works here before introducing you what are the results of this organization.

The results are:

  • 84 members
  • 316 pages
  • 27 categories

That's for the figures. But more than the figure what's interesting are the contents.

Here follows some of the pages that attract lot's of people:

There are also some documentation about other subjects:

I should not forget to speak about the large category of the wiki about the games ! Those 35 articles explain what are the games available and how to install them (they do not explain how you should enjoy them ;-) )

There is also a pdf version of the documentation for offline use when you are in the train trying to set up your wireless :-D (Thanks Pascal for that !)

= Conclusion =

I tried to introduce you some of the main features of this documentation and the principle that we used to set it up. Basically it is a documentation made by users for users, it quite often relies on subject/question that have been seen often on our forum (and I could say: "so often that at the end someone want to write something about it in order to not keep repeating himself").

We do realize that we are lucky with the team of people we have there. I should point out people like Nicolas who wrote most of the documentation about the configuration of the wireless cards or Hervé who was there at the beginning and gave us very good article on subject like GRUB, or Patrice who's knowledge on real time processing is so high that we had trouble to find people able to review his article before publication ;-) There are too many people so that I can't mention them all (I apologize to those that I did not) but I can't do but mention Johan who is the leader of the French documentation, he is the one that keep bothering everyone on the mailing list in order to obtain this result of quantity and quality ! Thanks ! ;-)

So there I am, I hope you did not get bored. As I explained my goal was just to introduce what the French community has been writing for the past years. If you are interesting in the content I would guess that google translate is probably not perfect and would need some work to make something out of it, but at least it gives you an idea :-D

Thanks for reading me up to there ! Enjoy your reading !! :-D

I also would like to thank Thomas the French community leader whose help is also really appreciated :D

Train station...

Pierre-Yves Chibon

Comment reconnais-t-on un gare où il y a du vent ???

How do you recognize a windy train station ???

Somewhere in the Netherland -- Quelque part aux Pays-Bas

DSC00042-3.jpeg

Train station...

Pierre-Yves Chibon

Comment reconnais-t-on un gare où il y a du vent ???

How do you recognize a windy train station ???

Somewhere in the Netherland -- Quelque part aux Pays-Bas

DSC00042-3.jpeg

Train station...

Pierre-Yves Chibon

Comment reconnais-t-on un gare où il y a du vent ???

How do you recognize a windy train station ???

Somewhere in the Netherland -- Quelque part aux Pays-Bas

DSC00042-3.jpeg

Train station...

Pierre-Yves Chibon

Comment reconnais-t-on un gare où il y a du vent ???

How do you recognize a windy train station ???

Somewhere in the Netherland -- Quelque part aux Pays-Bas

DSC00042-3.jpeg

R2spec-2.3

Pierre-Yves Chibon

rpm.pngsource.png

Small update with some code improvement in arguments management

Petite mise à jour avec quelques optiomisation du code dans la gestion des arguments

English version (Français ci-dessous)

I have made few changes on my project R2spec, changing the arguments/options management from getopt to OptionParser. It works nicely and save quite some code, there is the two versions:

First version

def getArgument():
       try:
               opts, args = getopt.getopt(sys.argv1:, "u:s:", "url=", "source=")
       except getopt.GetoptError:

print USAGE sys.exit(1)

       url = None
       source = None
       for option, argument in opts:
               if option in ("-u", "--url"):
                   url = argument
               if option in ("-s", "--source"):
                   source = argument

return (source,url)

New version

def getArgument():
        # Handle the parameters
        parser = OptionParser(version="%prog 2.3")
        parser.add_option("-u", "--url", dest="url", help="Url of the R library")
        parser.add_option("-s", "--source", dest="source", help="The source file (tarball) of the R library")
        (options, args) = parser.parse_args()

       return (options.source, options.url)

As you can see it improves quite the code ! In addition, it handles the --help and the --version by itself nothing to do !! \o/ :-p

Tester and feed back are always welcome ! :-)" class="smiley

The new version are available there:



French version

Je me suis occupé un petit peu ce week end et est fait quelques changements dans mon projet R2spec. J'ai notamment changé la gestion des arguments donnés du module getopt à OptionParser. Ça marche pas trop mal et améliore bien le code. Voici les deux version pour comparaison:

Première version

def getArgument():
       try:
               opts, args = getopt.getopt(sys.argv1:, "u:s:", "url=", "source=")
       except getopt.GetoptError:

print USAGE sys.exit(1)

       url = None
       source = None
       for option, argument in opts:
               if option in ("-u", "--url"):
                   url = argument
               if option in ("-s", "--source"):
                   source = argument

return (source,url)

Nouvelle version

def getArgument():
        # Handle the parameters
        parser = OptionParser(version="%prog 2.3")
        parser.add_option("-u", "--url", dest="url", help="Url of the R library")
        parser.add_option("-s", "--source", dest="source", help="The source file (tarball) of the R library")
        (options, args) = parser.parse_args()

        return (options.source, options.url)

Comme vous pouvez voir le code est pas mal améliorer ! En plus, plus de problème pour la création du --help ou du --version, ils sont crée directement, rien à faire !! \o/ :-p

Testeurs et commentaires sont les bienvenus :-)" class="smiley

Les nouvelles versions sont disponible ici:

R2spec-2.3

Pierre-Yves Chibon

rpm.pngsource.png

Small update with some code improvement in arguments management

Petite mise à jour avec quelques optiomisation du code dans la gestion des arguments

English version (Français ci-dessous)

I have made few changes on my project R2spec, changing the arguments/options management from getopt to OptionParser. It works nicely and save quite some code, there is the two versions:

First version

def getArgument():
       try:
               opts, args = getopt.getopt(sys.argv1:, "u:s:", "url=", "source=")
       except getopt.GetoptError:

print USAGE sys.exit(1)

       url = None
       source = None
       for option, argument in opts:
               if option in ("-u", "--url"):
                   url = argument
               if option in ("-s", "--source"):
                   source = argument

return (source,url)

New version

def getArgument():
        # Handle the parameters
        parser = OptionParser(version="%prog 2.3")
        parser.add_option("-u", "--url", dest="url", help="Url of the R library")
        parser.add_option("-s", "--source", dest="source", help="The source file (tarball) of the R library")
        (options, args) = parser.parse_args()

       return (options.source, options.url)

As you can see it improves quite the code ! In addition, it handles the --help and the --version by itself nothing to do !! \o/ :-p

Tester and feed back are always welcome ! :-)" class="smiley

The new version are available there:



French version

Je me suis occupé un petit peu ce week end et est fait quelques changements dans mon projet R2spec. J'ai notamment changé la gestion des arguments donnés du module getopt à OptionParser. Ça marche pas trop mal et améliore bien le code. Voici les deux version pour comparaison:

Première version

def getArgument():
       try:
               opts, args = getopt.getopt(sys.argv1:, "u:s:", "url=", "source=")
       except getopt.GetoptError:

print USAGE sys.exit(1)

       url = None
       source = None
       for option, argument in opts:
               if option in ("-u", "--url"):
                   url = argument
               if option in ("-s", "--source"):
                   source = argument

return (source,url)

Nouvelle version

def getArgument():
        # Handle the parameters
        parser = OptionParser(version="%prog 2.3")
        parser.add_option("-u", "--url", dest="url", help="Url of the R library")
        parser.add_option("-s", "--source", dest="source", help="The source file (tarball) of the R library")
        (options, args) = parser.parse_args()

        return (options.source, options.url)

Comme vous pouvez voir le code est pas mal améliorer ! En plus, plus de problème pour la création du --help ou du --version, ils sont crée directement, rien à faire !! \o/ :-p

Testeurs et commentaires sont les bienvenus :-)" class="smiley

Les nouvelles versions sont disponible ici:

R2spec-2.3

Pierre-Yves Chibon

rpm.pngsource.png

Small update with some code improvement in arguments management

Petite mise à jour avec quelques optiomisation du code dans la gestion des arguments

English version (Français ci-dessous)

I have made few changes on my project R2spec, changing the arguments/options management from getopt to OptionParser. It works nicely and save quite some code, there is the two versions:

First version

def getArgument():
       try:
               opts, args = getopt.getopt(sys.argv1:, "u:s:", "url=", "source=")
       except getopt.GetoptError:

print USAGE sys.exit(1)

       url = None
       source = None
       for option, argument in opts:
               if option in ("-u", "--url"):
                   url = argument
               if option in ("-s", "--source"):
                   source = argument

return (source,url)

New version

def getArgument():
        # Handle the parameters
        parser = OptionParser(version="%prog 2.3")
        parser.add_option("-u", "--url", dest="url", help="Url of the R library")
        parser.add_option("-s", "--source", dest="source", help="The source file (tarball) of the R library")
        (options, args) = parser.parse_args()

       return (options.source, options.url)

As you can see it improves quite the code ! In addition, it handles the --help and the --version by itself nothing to do !! \o/ :-p

Tester and feed back are always welcome ! :-)

The new version are available there:



French version

Je me suis occupé un petit peu ce week end et est fait quelques changements dans mon projet R2spec. J'ai notamment changé la gestion des arguments donnés du module getopt à OptionParser. Ça marche pas trop mal et améliore bien le code. Voici les deux version pour comparaison:

Première version

def getArgument():
       try:
               opts, args = getopt.getopt(sys.argv1:, "u:s:", "url=", "source=")
       except getopt.GetoptError:

print USAGE sys.exit(1)

       url = None
       source = None
       for option, argument in opts:
               if option in ("-u", "--url"):
                   url = argument
               if option in ("-s", "--source"):
                   source = argument

return (source,url)

Nouvelle version

def getArgument():
        # Handle the parameters
        parser = OptionParser(version="%prog 2.3")
        parser.add_option("-u", "--url", dest="url", help="Url of the R library")
        parser.add_option("-s", "--source", dest="source", help="The source file (tarball) of the R library")
        (options, args) = parser.parse_args()

        return (options.source, options.url)

Comme vous pouvez voir le code est pas mal améliorer ! En plus, plus de problème pour la création du --help ou du --version, ils sont crée directement, rien à faire !! \o/ :-p

Testeurs et commentaires sont les bienvenus :-)

Les nouvelles versions sont disponible ici:

R2spec-2.3

Pierre-Yves Chibon

rpm.pngsource.png

Small update with some code improvement in arguments management

Petite mise à jour avec quelques optiomisation du code dans la gestion des arguments

English version (Français ci-dessous)

I have made few changes on my project R2spec, changing the arguments/options management from getopt to OptionParser. It works nicely and save quite some code, there is the two versions:

First version

def getArgument():
       try:
               opts, args = getopt.getopt(sys.argv1:, "u:s:", "url=", "source=")
       except getopt.GetoptError:

print USAGE sys.exit(1)

       url = None
       source = None
       for option, argument in opts:
               if option in ("-u", "--url"):
                   url = argument
               if option in ("-s", "--source"):
                   source = argument

return (source,url)

New version

def getArgument():

# Handle the parameters parser = OptionParser(version="%prog 2.3") parser.add_option("-u", "--url", dest="url", help="Url of the R library") parser.add_option("-s", "--source", dest="source", help="The source file (tarball) of the R library") (options, args) = parser.parse_args()

       return (options.source, options.url)

As you can see it improves quite the code ! In addition, it handles the help and the version by itself nothing to do !! \o/ :-p

Tester and feed back are always welcome ! :-)" class="smiley

The new version are available there:



French version

Je me suis occupé un petit peu ce week end et est fait quelques changements dans mon projet R2spec. J'ai notamment changé la gestion des arguments donnés du module getopt à OptionParser. Ça marche pas trop mal et améliore bien le code. Voici les deux version pour comparaison:

Première version

def getArgument():
       try:
               opts, args = getopt.getopt(sys.argv1:, "u:s:", "url=", "source=")
       except getopt.GetoptError:

print USAGE sys.exit(1)

       url = None
       source = None
       for option, argument in opts:
               if option in ("-u", "--url"):
                   url = argument
               if option in ("-s", "--source"):
                   source = argument

return (source,url)

Nouvelle version

def getArgument():

# Handle the parameters parser = OptionParser(version="%prog 2.3") parser.add_option("-u", "--url", dest="url", help="Url of the R library") parser.add_option("-s", "--source", dest="source", help="The source file (tarball) of the R library") (options, args) = parser.parse_args()

       return (options.source, options.url)

Comme vous pouvez voir le code est pas mal améliorer ! En plus, plus de problème pour la création du help ou du version, ils sont crée directement, rien à faire !! \o/ :-p

Testeurs et commentaires sont les bienvenus :-)" class="smiley

Les nouvelles versions sont disponible ici:

Fedora & touchpad

Pierre-Yves Chibon

Some people like it so there is the trick

Certain l'aime donc voila comment faire

French version (English below)

Certaines personnes aiment qu'un tapotement sur le touchpad corresponde à un clique de souris. Sous fedora 9 ce comportement est par défaut annulé pour le remettre il faut donc procédé ainsi :

Rajouter une ligne pour le touchpad dans la section "ServerLayout" du xorg.conf:

InputDevice    "TouchPad" "CorePointer"

Rajouter une nouvelle section, correspondant au nouveau device :

Section "InputDevice"
  Driver      "synaptics"
  Identifier  "TouchPad"
  Option      "SendCoreEvents"
  Option      "Protocol" "auto-dev"
  Option      "SHMConfig" "on"
  Option      “TapButton1″ “1″
  Option      “TapButton2″ “2″
EndSection

Les options TapButton étant les plus importantes ;-)" class="smiley

Et un grand merci à notre amis Carlos de Fedora|Paris qui m'a communiqué l'astuce (que je n'utilise pas puisque je n'aime pas ça :-p) :-)" class="smiley



English version

Some people like that the touchpad on their laptop enable the tap as a click of the mouse. Under Fedora 9 this behavior is disable by default, so to change this there is the howto :

In the section "ServerLayout" of the xorg.conf add the new line :

InputDevice    "TouchPad" "CorePointer"

Create a new section for this device :

Section "InputDevice"
  Driver      "synaptics"
  Identifier  "TouchPad"
  Option      "SendCoreEvents"
  Option      "Protocol" "auto-dev"
  Option      "SHMConfig" "on"
  Option      “TapButton1″ “1″
  Option      “TapButton2″ “2″
EndSection

The option tap are obviously the most important one ;-)" class="smiley

A big thanks to Carlos from Fedora|Paris who gave me the trick (that I do not use since I do not like it :-p) :-)" class="smiley

Fedora & touchpad

Pierre-Yves Chibon

Some people like it so there is the trick

Certain l'aime donc voila comment faire

French version (English below)

Certaines personnes aiment qu'un tapotement sur le touchpad corresponde à un clique de souris. Sous fedora 9 ce comportement est par défaut annulé pour le remettre il faut donc procédé ainsi :

Rajouter une ligne pour le touchpad dans la section "ServerLayout" du xorg.conf:

InputDevice    "TouchPad" "CorePointer"

Rajouter une nouvelle section, correspondant au nouveau device :

Section "InputDevice"
  Driver      "synaptics"
  Identifier  "TouchPad"
  Option      "SendCoreEvents"
  Option      "Protocol" "auto-dev"
  Option      "SHMConfig" "on"
  Option      “TapButton1″ “1″
  Option      “TapButton2″ “2″
EndSection

Les options TapButton étant les plus importantes ;-)" class="smiley

Et un grand merci à notre amis Carlos de Fedora|Paris qui m'a communiqué l'astuce (que je n'utilise pas puisque je n'aime pas ça :-p) :-)" class="smiley



English version

Some people like that the touchpad on their laptop enable the tap as a click of the mouse. Under Fedora 9 this behavior is disable by default, so to change this there is the howto :

In the section "ServerLayout" of the xorg.conf add the new line :

InputDevice    "TouchPad" "CorePointer"

Create a new section for this device :

Section "InputDevice"
  Driver      "synaptics"
  Identifier  "TouchPad"
  Option      "SendCoreEvents"
  Option      "Protocol" "auto-dev"
  Option      "SHMConfig" "on"
  Option      “TapButton1″ “1″
  Option      “TapButton2″ “2″
EndSection

The option tap are obviously the most important one ;-)" class="smiley

A big thanks to Carlos from Fedora|Paris who gave me the trick (that I do not use since I do not like it :-p) :-)" class="smiley

Fedora & touchpad

Pierre-Yves Chibon

Some people like it so there is the trick

Certain l'aime donc voila comment faire

French version (English below)

Certaines personnes aiment qu'un tapotement sur le touchpad corresponde à un clique de souris. Sous fedora 9 ce comportement est par défaut annulé pour le remettre il faut donc procédé ainsi :

Rajouter une ligne pour le touchpad dans la section "ServerLayout" du xorg.conf:

InputDevice    "TouchPad" "CorePointer"

Rajouter une nouvelle section, correspondant au nouveau device :

Section "InputDevice"
  Driver      "synaptics"
  Identifier  "TouchPad"
  Option      "SendCoreEvents"
  Option      "Protocol" "auto-dev"
  Option      "SHMConfig" "on"
  Option      “TapButton1″ “1″
  Option      “TapButton2″ “2″
EndSection

Les options TapButton étant les plus importantes ;-)

Et un grand merci à notre amis Carlos de Fedora|Paris qui m'a communiqué l'astuce (que je n'utilise pas puisque je n'aime pas ça :-p) :-)



English version

Some people like that the touchpad on their laptop enable the tap as a click of the mouse. Under Fedora 9 this behavior is disable by default, so to change this there is the howto :

In the section "ServerLayout" of the xorg.conf add the new line :

InputDevice    "TouchPad" "CorePointer"

Create a new section for this device :

Section "InputDevice"
  Driver      "synaptics"
  Identifier  "TouchPad"
  Option      "SendCoreEvents"
  Option      "Protocol" "auto-dev"
  Option      "SHMConfig" "on"
  Option      “TapButton1″ “1″
  Option      “TapButton2″ “2″
EndSection

The option tap are obviously the most important one ;-)

A big thanks to Carlos from Fedora|Paris who gave me the trick (that I do not use since I do not like it :-p) :-)

Fedora & touchpad

Pierre-Yves Chibon

Some people like it so there is the trick

Certain l'aime donc voila comment faire

French version (English below)

Certaines personnes aiment qu'un tapotement sur le touchpad corresponde à un clique de souris. Sous fedora 9 ce comportement est par défaut annulé pour le remettre il faut donc procédé ainsi :

Rajouter une ligne pour le touchpad dans la section "ServerLayout" du xorg.conf:

InputDevice    "TouchPad" "CorePointer"

Rajouter une nouvelle section, correspondant au nouveau device :

Section "InputDevice"
  Driver      "synaptics"
  Identifier  "TouchPad"
  Option      "SendCoreEvents"
  Option      "Protocol" "auto-dev"
  Option      "SHMConfig" "on"
  Option      “TapButton1″ “1″
  Option      “TapButton2″ “2″
EndSection

Les options TapButton étant les plus importantes ;-)" class="smiley

Et un grand merci à notre amis Carlos de Fedora|Paris qui m'a communiqué l'astuce (que je n'utilise pas puisque je n'aime pas ça :-p) :-)" class="smiley



English version

Some people like that the touchpad on their laptop enable the tap as a click of the mouse. Under Fedora 9 this behavior is disable by default, so to change this there is the howto :

In the section "ServerLayout" of the xorg.conf add the new line :

InputDevice    "TouchPad" "CorePointer"

Create a new section for this device :

Section "InputDevice"
  Driver      "synaptics"
  Identifier  "TouchPad"
  Option      "SendCoreEvents"
  Option      "Protocol" "auto-dev"
  Option      "SHMConfig" "on"
  Option      “TapButton1″ “1″
  Option      “TapButton2″ “2″
EndSection

The option tap are obviously the most important one ;-)" class="smiley

A big thanks to Carlos from Fedora|Paris who gave me the trick (that I do not use since I do not like it :-p) :-)" class="smiley

Blog mis à jour

Fabien Nicoleau

Comme mes petits camarades, j'ai mis à jour mon blog. Il tourne donc sous dotclear 2.0. Comme d'habitude la mise à jour a été facile avec la documentation.

Fabien (eponyme)