Supposons que vous êtes (sous GNU/Linux ou unix, sous un terminal avec pour shell bash ou un autre similaire) dans le répertoire (ou “dossier”) /current/ , que /current/existant/ existe déjà et que vous voulez créer les répertoires /current/existant/new_dir_0/ , /current/existant/new_dir_0/sub_dir_1/ , /current/existant/new_dir_0/sub_dir_1/sub_sub_dir_2/ en une seule ligne…
Read more »
Je dois avouer que depuis que j’utilise Linux, les gros bugs sont assez rares… Là j’ai eu le droit à un écran restant noir suite à une courte absence. En fait il s’agissait d’un petit plantage de l’économiseur d’écran…
Voilà un peu comment le truc s’est facilement arrangé de façon assez propre, sans toucher au bouton power pour rien:
Read more »
Votre curiosité vous pousse à vous renseigner sur ce qui s’est réellement passé pour en arriver à de telles aberrations?
Si vous comprenez l’anglais, et que vous souhaitez le récit de quelqu’un plutôt bien placé dans le processus, pourquoi ne pas jeter un coup d’oeil ici?
(Franchement on peut commencer à douter sérieusement de la crédibilité des organismes de normalisation, surtout qu’on peut se demander combien se taisent dans ce genre de situations pour chaque personne qui ose parler…)
En tout cas vrai ou faux standard, je n’utilise pas!
Cet article est plus un exemple du principe général d’utiliser tar dans une session ssh pour extraire un fichier envoyé compressé sur le serveur plutôt qu’un ensemble de fichiers décompressés via FTP.
Le titre ne veut pas dire que je destine ce blog à devenir le support non officiel des mutualisés chez ovh ou à fournir une référence détaillée sur pmwiki. Il indique juste les circonstances dans lesquelles l’exemple a été testé, sachant que dans d’autres cas des manipulations supplémentaires peuvent être à faire.
En bref, pmwiki est un système de wiki à la fois simple et léger, et n’utilisant pas de base de données.
Voici de manière détaillée la méthode que j’ai appliqué dans mon exemple précis, sachant que l’intérêt du post est plus d’illustrer mon post précédent:
/chemin-archive/ssh login@ftp.domaine.tld, puis ensuite le mot de passe (ou autre méthode d’authentification) cd /chemin-archive/ ; tar -xvvf ./pmwiki-latest.tgzrm ./pmwiki-latest.tgz), déplacer le répertoire à l’endroit voulu s’il est ailleur avec mv, etc…logout à la fin, et surtout avant on oublie pas que l’on est sur le serveur… (Ça doit être particulièrement ennuyeux des fois un sudo shutdown -h now quand on a les droits sur une machine distante…)Notes:
man nom_de_la_commande). Selon les cas il peut être préférable de les consulter en local, sur votre session ssh, ou via le web…nano ou vim en ssh quand c’est installé, modification du fichier et transfert, etc…Pour ceux qui ne le savant pas, tar est, de façon simplifiée, le programme de référence pour manipuler quantité d’archives (compressées ou non) sous Linux et Unix en général.
Certains pensent probablement qu’avec toutes les belles applications graphiques qui existent, la manipulation de tar devient un truc superflu réservé aux geeks barbus avec une curiosité (informatique) débordante…
En fait pas tant que ça! Il y a encore des cas où ce programme peut véritablement vous être utile. Par exemple lorsque vous avez un serveur pour votre hébergement offrant FTP et SSH.
En résumer, plutôt que de passer 1 heure à uploader un dossier décompressé, vaut mieux passer 5 minutes à uploader le fichier compressé et 10 de plus pour se connecter en ssh et comprendre la page man de tar. En fait pour beaucoup on peut supprimer les 10 minutes de plus, parce que c’est pas si compliqué que ça…
Ceci dit en local sur mon propre pc, plus d’une fois je les ai utilisés ces belles interfaces graphiques!
UPDATE : exemple d’utilisation sur ce post
After doing any migration from a weblog system to another, one may probably want to avoid loosing visits, right?
It’s quite easy to put messages in your old blog to say that the url of your blog has changed. The problem is that it’s not enough.
Regular viewers may access your blog through feeds. If you just post a note as another regular post and that they hadn’t the time to read it when you had post it, they may just skip it and never read your new articles.
One smart thing to do may be to redirect systematically all people trying to access your old feed to your new feed (not by a simple notice that have to be read, but by using a clean and real web redirection).
Under blogger, it’s just easy to do that: you have a feature to use another source to provide your feeds. Even if the feature was probably created with other ideas in mind (maybe allowing blogger users to use their feedburner feeds), you can use it to provide your new feed to people trying to access your old feed. Below is the exact method :
There are many reasons to be interested in Free / Open Source Software (FOSS). Basically there are two kinds of reasons:
Of course, one should not forget that a programmer is also an user. The goal of this article is to explain a little the reasons that could explain that a programmer could be interested in open source, even in a world where a large place is given to money.
First, it is interesting to explain the term “Free / Open Source Software” (FOSS). This term combines two facts into one term about the software being considerate:
In term of facts, the difference between the terms “free software” and “open source software” is often so subtle that most people wouldn’t be able to give a beginning of an explanation about it : most of the difference in the use of the terms is about philosophy.
However, this difference betweens the two terms does have its importance. Important figures of Free / Open Source Software have written about this and if you’re interested to understand, I would recommend this two links:
If you don’t know very well who are these two key figures, I’d suggest some reading about them two : understanding their philosophy is a key.
In the rest of this article, I’ll simply refer to “Free / Open Source Software” by FOSS without indicating each time subtle (or not) differences between the two way of viewing the things. I’ll rather focus on what makes a big deal: the difference between FOSS and proprietary and closed software. I’ll try to focus on it from a programmer’s point of view (although FOSS is interesting for users too).
There are many reasons for a programmer to be interested in FOSS. These reasons concerns many different aspects about FOSS:
Freedom and Social Aspect:
As Richard Stallman explained it in the GNU Manifesto, it’s natural for humans to share what they can and it should remains natural for programmers (who are users too) to share programs, without any legal barrier. Introducing barriers to prevent humans to share what they can is neither natural nor desirable.
Right for programmers to make money:
Many points about that are covered in the GNU Manifesto too. Although Richard Stallman presented some solutions to solve what may seems first to be an intrinsic problem, he didn’t covered everything (the GNU Manifesto was written some time ago). In the facts, it seems that a lot of companies have found their way to gain money making free software. Here are some facts to consider:
So companies are able to make money with free software, so it’s easily possible to pay programmers to do the job.
Recognition/Reputation:
Doing major contributions in FOSS is clearly a way of getting recognition. Whether this recognition is a goal in itself or is seen as a way to get new better opportunities to get money, a lot of programmer contributing to FOSS are driven by the hope of getting recognized, and this hope is often realistic: FOSS offers huge opportunities for that. It’s a more open field than some other ones totally unrelated to computers (becoming a recognized artist for example is not as simple…).
By the way I’d recommend another document : Producing Open Source Software (link to appropriate chapter but the whole is interesting) by Karl Fögel.
A way to learn:
The FOSS community being more open for programmers, it’s easier for programmers to get a chance to contribute in a way they will communicate with other people interested and learn a lot. That’s another important point too.
Receiving something and giving something:
That’s a fact: humans are more inclined to give something to other people who bring them something too (whether it is consciously perceived as an exchange or not). Programmers are humans too and are not an exception to this rule. In fact, even if they have no insurance to give a “gift” to people who have “given” them interesting or useful software before, they feel as they received something from the community and then give something back to the community.
Having a real interest in what you do:
That’s a fact: people who are really interested in what they do are likely to try to do their best to improve things in their field. This is not limited to software or computer science. Great mathematicians and physicists work in this way too. FOSS is just a far more appropriate way than closed software to contribute.
“The world is full of fascinating problems waiting to be solved.” and “No problem should ever have to be solved twice.”:
These sentences came from paragraph titles of an interesting document of Eric Raymond : How To Become A Hacker (Warning: if you think that an hacker is someones who breaks other’s computer, you’re totally wrong. Please read Eric’s document before showing any concerns about that).
By reading the two quoted sentences, it’s quite obvious that FOSS is just more appropriate for that. There is just less useless barrier with FOSS to reuse what has already been done when needed to do more, to use it as a way to do what has never been done before.
Is that all?
Clearly not! Above are some important points among what I perceived, there are many others. Reading all linked document may help you to think on the subject and you may enjoy that people may share something that is not code: interesting documents.
Un petit tuyau qui n’a rien de technique ni de nouveau, que je fournis tant que j’y pense (ça fait depuis pas mal de temps que je l’utilise et beaucoup connaissent déjà le truc), tout simplement parce que beaucoup l’ignorent et que c’est terriblement pratique…
Si vous avez une souris à bouton central (ou molette), sachez que vous pouvez ouvrir dans la plupart des cas un lien dans un nouvel onglet en faisant un clic du bouton central (ou de la molette) sur le lien en question (sous Firefox). C’est un gain de temps considérable par rapport à un clic droit puis à la sélection de “ouvrir dans un nouvel onglet”.
Encore une raison supplémentaire à mon gout de préférer les vraies souris à un touchpad…
Wordpress is a high quality software, and seems to produce w3c compliant xhtml… But…. Sometimes things may fail on your blog, in particular after an import of blogger posts!
I had to correct a post in the “edit html” mode to make the home page of the blog correct, and I’ll have to check all in order to be sure to comply with w3c standards. I know, a lot of people doesn’t care at all about standards, but the web wouldn’t be what it is without them. It’s the key to be able to read pages today and tomorrow, with the software of your choice, on the platform of your choice.
EDIT (update, on the same day): if I forgot nothing, all fixes should have been done, so don’t hesitate to tell me in case a page fail to pass the w3c checker!
Note: at the time you’re reading the post, maybe the theme would not be the same as now… Who knows?
I tried to look quickly for a new theme for my blog, and although there may be lot of themes, it’s not easy to choose… There are some obvious characteristics of a theme and some which aren’t…
Among first visual aspect, here are some of my criteria :
Among general quality, I have other ones:
Well do you think it’s too easy with so little criteria… In fact, after trying I discovered than I do have more criteria:
And here the problem comes, it seems that I have to much criteria, at least too much to make the search easy… Maybe I’ll consider writing a theme myself… Who knows?
