Microblogi: A very long article Wikipedia article on the orientation of toilet paper [7. kes klo 22:52] [V]

Keskiviikko, 30. marraskuuta 2011

Le donjon de Naheulbeuk, volume 6

Käännös: [ Google ]

Kategoriat: [ Kirjat/Sarjakuvat/Naheulbeuk ]

ISBN: 9782353251704

© Amazon.fr

Sixième volume du donjon de Naheulbeuk, publié en 2009. Les aventuriers reviennent à Boulgourville et reçoivent leur récompense, mais en perdent la plus grande partie en taxes diverses et en remboursement de dettes. On leur annonce aussi que par leur faute, Gontran Théogal a maintenant toutes les statuettes (sauf qu'en fait non parce qu'on lui en a juste volé une) et pourra s'en servir pour lancer le sortilège qui permettra le retour de Dlul et plongera la Terre de Fangh dans l'oubli éternel.

[ Postattu 30. marraskuuta 2011 klo 21.07 | ei kommenttia | ]

Retour aux sources

Käännös: [ Google ]

Kategoriat: [ Kirjat/Sarjakuvat/Aquablue ]

ISBN: 9782756012636

© Amazon.fr

Douzième volume d'Aquablue. Nao revient sur Aquablue après avoir trouvé des traces de l'antique civilaisation d'Aquablue en Antarctique. Avec une équipe de recherche, il étudie la faune de la planète, et trouve une concordance génétique avec celle de la Terre. La nouvelle est ébruitée par des journalistes, et le gouvernement de la Terre décide de changer la loi qui interdisait l'exploitation d'Aquablue, afin de permettre aux humains d'aller s'installer « sur leur planète d'origine ». Les patrons de la Texec se frottent les mains.

[ Postattu 30. marraskuuta 2011 klo 21.02 | ei kommenttia | ]

Tiistai, 29. marraskuuta 2011

L'énigme Banks

Käännös: [ Google ]

Kategoriat: [ Kirjat/Sarjakuvat/Golden City ]

ISBN: 9782756025186

© Amazon.fr

Neivième volume de la série Golden City. L'attaque contre Golden City avait été commandité par Irina Banks pour mettre la main sur les quatre personnes qui avaient tenté de la tuer cinq ans plus tôt (à la suite de quoi elle s'était fait passer pour morte). En parallèle, les enfants sont à nouveau réunis, et grâce à l'argent caché par le père de Loli, ils partent à la recherche de Banks (qui a disparu en tentant de protéger Golden City contre une torpille venant d'on ne sait où).

[ Postattu 29. marraskuuta 2011 klo 20.54 | ei kommenttia | ]

Perjantai, 25. marraskuuta 2011

Moles Stocking Filler

Käännös: [ Google ]

Kategoriat: [ Olut/Moles ]


“Chestnut coloured, gruity, malty, well hopped bitter… brewed with English Maris Otter malted barley, some roasted barley and Fuggles and Golding Variety hops.”

Just another ale. Contains barley.

Moles Brewery, Melksham, Wiltshire, England. 4.7% alcohol.

[ Postattu 25. marraskuuta 2011 klo 21.26 | ei kommenttia | ]

Keskiviikko, 23. marraskuuta 2011

Boules de poils (1)

Käännös: [ Google ]

Kategoriat: [ Kirjat/Sarjakuvat/Troy ]

ISBN: 9782302016293

© Amazon.fr

Quinzième volume de Trolls de Troy publié en 2011. Pour se protéger d'une attaque de trolls, deux marchands volant en dragon réduisent par magie tout ce qui se trouve en dessus d'eux. Les trolls partent alors à la recherche des marchands afin qu'ils réduisent le reste du monde aussi. Ils sont d'abord attrapés par deux escrocs et enchantés (sauf Waha), parviennent à s'échapper et à retrouver leur amie humains Trollane pour lui demander de les aider à retrouver les marchands. Attaqués par des gardes alors qu'ils étaient en train de convaincre les marchands de leur redonner leur taille normale, seul Roken est agrandi, et tous finissent par s'échapper sur un dragon qui transporte un colis précieux vers Eckmül.

[ Postattu 23. marraskuuta 2011 klo 21.00 | ei kommenttia | ]

Sunnuntai, 20. marraskuuta 2011

Harviestoun Mr Sno'Balls

Käännös: [ Google ]

Kategoriat: [ Olut/Harviestoun ]


“brewed with pale and crystal malts with a touch of roast barley. The hop additions are Challenger for bitterness and Styrian for its floral citrus aroma.”

Quite sweet, not too bitter. Not convinced about the floral citrus aroma, I found it had more of a kind of a very fresh red fruit nuance. Contains barley and wheat.

Harviestoun Brewery, Alva, Clackmannanshire, Scotland. 4.5% alcohol.

[ Postattu 20. marraskuuta 2011 klo 20.23 | ei kommenttia | ]

Torstai, 17. marraskuuta 2011

Transformers: Revenge of the Fallen

Käännös: [ Google ]

Kategoriat: [ TV/Elokuvat/Transformers ]



The Fallen is a Decepticon that has been hiding far away in the solar system and wants to find the key to a device, hidden somewhere on Earth, that would destroy the sun and produce energon. The Decepticons are chasing Sam because he got infused with a bit of the All Spark, has visions of symbols (of the language of the Primes) that can lead him to the key and is now the only one who can actually find the key. The autobots are protecting Sam, but Optimus Prime is killed. Sam then looks for the key that should allow to ressuscitate Optimus. They finally locate the key in Egypt. After a long battle for the control of the device (located at the top of a pyramid), Sam manages to save Optimus Prime while the army destroys the device.

[ Postattu 17. marraskuuta 2011 klo 22.28 | ei kommenttia | ]

Perjantai, 11. marraskuuta 2011

Traffic Shaping

Käännös: [ Google ]

Kategoriat: [ ATK ]

I have an asymetrical ADSL connecion (1024 kbps downstream, 512 kbps upstream) and when I'm downloading a large file, SSH connections become unresponsive. After a bit of reading, I found one traffic shaping script that allows to keep responsive interactive SSH connections, at the cost of a slightly limited download speed. The explanations are from the Linux advanced routing and traffic control howto, in the cookbook chapter.

The explanations goes like this:

“ISPs know that they are benchmarked solely on how fast people can download. Besides available bandwidth, download speed is influenced heavily by packet loss, which seriously hampers TCP/IP performance. Large queues can help prevent packet loss, and speed up downloads. So ISPs configure large queues.

These large queues however damage interactivity. A keystroke must first travel the upstream queue, which may be seconds (!) long and go to your remote host. It is then displayed, which leads to a packet coming back, which must then traverse the downstream queue, located at your ISP, before it appears on your screen.

This HOWTO teaches you how to mangle and process the queue in many ways, but sadly, not all queues are accessible to us. The queue over at the ISP is completely off-limits, whereas the upstream queue probably lives inside your cable modem or DSL device. You may or may not be able to configure it. Most probably not.

So, what next? As we can't control either of those queues, they must be eliminated, and moved to your Linux router. Luckily this is possible.

Limit upload speed By limiting our upload speed to slightly less than the truly available rate, no queues are built up in our modem. The queue is now moved to Linux.

Limit download speed This is slightly trickier as we can't really influence how fast the internet ships us data. We can however drop packets that are coming in too fast, which causes TCP/IP to slow down to just the rate we want. Because we don't want to drop traffic unnecessarily, we configure a 'burst' size we allow at higher speed.”

It really does wonders, on the condition that you set the DOWNLINK speed to 800 kbps (80% of my downlink) and the UPLINK to 440 kbps (85% of my uplink). I tried with 900 kpbs instead of 800, and it didn't work. One day, I will take the time to think about the why, but for now I'm just happy that it works properly.

Next step: try to get this to work on the ADSL modem/router (luckily running linux and accessible with ssh) instead of the desktop.

[ Postattu 11. marraskuuta 2011 klo 22.09 | ei kommenttia | ]

Torstai, 10. marraskuuta 2011

20,000 Leagues under the Sea

Käännös: [ Google ]

Kategoriat: [ TV/Elokuvat ]



1868. In the South Pacific, ships are destroyed by a mysterious monster. Prof. Arronax is investigating the mystery when his ship is attacked by the monster. It is actually a submarine named the Nautilus, whose captain, Nemo, enventually decides to take in the professor and the two other survivors of the attack. Nemo and his crew live exclusively from products of the sea, and together they fight against everything that is used for making war, thus saving the lives of the thousands who would have been killed by the destroyed hardware. As the Nautilus reaches its base, it is ambushed by British forces (directed to the island by messages-in-a-bottle sent by one of the companions of Arronax) and Nemo is mortally wounded. He then decides to sink the Nautilus and his whole crew with him. Arronax and his companions manage to escape just in time.

[ Postattu 10. marraskuuta 2011 klo 20.46 | ei kommenttia | ]

Keskiviikko, 2. marraskuuta 2011

Git in a (Very Small) Nutshell

Käännös: [ Google ]

Kategoriat: [ ATK/Git ]

When I started to use git and read the man pages, I was sorely missing a brief description of how Git's features and concepts relate. Now that I finally understand (at least, I think) how Git works, I wrote this document. It's not a tutorial (the existing ones are good enough that I don't need to write another one), but rather a summary of how Git's main features relate to the jargon used in the man pages.

Saving your changes

Let's say you have a set of files in your working tree. Git works by saving a full copy (snapshot) of this set; this is called a commit. When you want to make a new commit using Git, you first need to tell Git which files are going to be part of this commit. You do this with the git add my_file command. The files are then added to the index, which is the list of files that are going to compose the commit. You then run git commit, which creates a new commit based on the files listed in the index. You are also prompted for a message that describes the commit. The message is structured with a heading (the first line of the message) separated by an empty line, from the body of the message. Lines starting with a hash symbol are comments and are not recorded into the message.

Adding a new file to the index and creating a commit containing this file has the side effect of letting Git track this file. If you want to create a commit composed of all the tracked files, you can run git commit -a, which implicitely adds all the tracked files to the index before creating a new commit.

A commit is identified by a SHA1 hash of its content, e.g, cdf18108b03386e1b755c1f3a3feaa30f9529390. Any non-ambiguous prefix of that hash can be used as a commit ID e.g., cdf1810.

The add/commit mechanism allows to split a set of changes into multiple commits (you create a commit for a subset of your files, then you create another commit for the rest of your files).

Creating a new repository

For a new project

The command git init creates a repository in the current directory (a .git directory that holds all the data necessary for Git to work). You can then add the files you need to have under version control (using git add, wildcards such as '*' are accepted) and create the initial commit with git commit.

Copying an existing repository

To copy an existing repository, use the git clone command. Most services that offer source code as Git repositories indicate the necessary Git command line to run.

Finding a commit

To view a summary of the changes that have happened in the repository, you can use git log; the top of the list is the most recent commit. To view the succession of changes (as diffs) that were made, use git log -p.

Git does its best not to lose anything you have recorded. The command git reflog shows a log of how the tip of branches have been updated, even if you have done acrobatic things.


When you make changes to your working tree and create a new commit, Git links the new commit to the commit that represents the state of the working directory before the changes (called in this context the parent of the new commit). The chain composed of the new commit, its parent, its parent's parent and so on, is called a branch. The name of the default branch is “master”. The most recent commit in a branch is called its HEAD.

A branch is nothing more than a name and the commit identifier of its tip; this is called a ref. For example refs/heads/master is the ref for the master branch. Finding the commits that compose the branch is a simple matter of following the tip's parent, and the parent's parent, and so on.

If you can decide to fork your work at some point, create a new branch by running git branch new_branch. This command creates the branch, but does not switch to that branch (changes and commits will still be appended to the current branch). To effectively change branch, you need to checkout the HEAD of the new branch by running git checkout new_branch. From this point on, changes and commits will be appended to the new branch.


If at some point it is necessary to merge the content of e.g., the new branch into the “master” branch, you need to checkout “master” and then run git merge new_branch.

If Git doesn't know how to merge two branches, it complains about conflicts and lets the user edit the incriminated files by hand. This is done by choosing, in sections of these files indicated with <<<<<< and >>>>>>> markers, which variant is to be retained. Once the editing has been made, the changes need to be committed (with git commit -a).

Checking out

You can checkout any commit with git checkout and thus have your working directory reflect the state of the repository at any point in time. When you do that, you are not on any branch anymore, which will cause various warning messages (such as “You are in 'detached HEAD' state”) and cause Git to behave in a way you may not expect (that is, if you don't understand properly yet how Git works). To go back to a “normal” situation, just run git branch master (or any other branch that exists). To prevent going into detached HEAD state, use git checkout -b new_branch to create a new branch that starts at <commit>.

If you have made local changes, Git won't let you checkout another branch. You must either commit them or reset the working tree before being allowed to do the checkout.


The command git reset allows to do multiple things. One of its most common use (git reset --hard) is to cancel all changes you have made to the working tree since the last commit.

If you specify a commit ID after git reset, it will move the HEAD of the current branch back to that commit, which becomes the new HEAD; all commits after this point are removed from the branch (but not from the repository! You can always restore the old HEAD by finding its commit ID with git reflog).

Working with remote repositories

Pull (and Fetch)

Some time after you have cloned a public repository, you may want to update your local copy so that it mathtches the latest version available at the original repository. This update is done with with git pull. When the repository was cloned, Git had created a remote (a link to the source repository) called by default “origin”. Below the hood, git pull calls git fetch to retrieve the commits from all the relevant branches on “origin”, and then calls git merge to merge those changes with the local current branch.

Note that refs/remotes/origin/master is the ref to the master branch at “origin”, but it is actually a branch stored locally that reflects the “master” branch on the “origin” repository. This kind of ref is used for specifying what remote branch is tracked by what local branch when using git fetch. Typically, +refs/heads/:refs/remotes/origin/ indicates that e.g., the local branch “master” tracks the remote branch “origin/master” (“*” represents a wildcard).


If you have writing permissions on the remote repository, you can send your changes using git push (it defaults to the “origin” remote). Note that the HEAD of the branch to which you push changes must be the parent of your changes. If this is not the case, the push will fail and you will be asked to first pull from the remote repository to get the latest version, fix potential conflicts and only then push your changes.

It is also important to remember that you cannot normally push to a repository that has a working tree. The remote repository must have been created with the git init --bare command.

[ Postattu 2. marraskuuta 2011 klo 08.36 | ei kommenttia | ]