Aller au contenu | Aller au menu | Aller à la recherche

Logiciel Libre | Free Software

Fil des billets - Fil des commentaires

dimanche 8 juillet 2012

Tomboy SSH sync issues

When trying to synchronise your Tomboy notes using SSHfs to a location you know already contains your notes, you may get this error:

fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option

From what I understand, Tomboy expects an empty directory to start synchronising notes, and if your directory is non-empty (for instances, you've reinstalled your system and are setting up your Tomboy instance to start syncing from that directory again), Tomboy will complain and refuse to sync.
It will, however give you the solution (“use the 'nonempty' mount option“) but not tell you how to do so.

It turns out you can add options to the “Folder Path (optional):” box, just do as if you were on the command line: -o option whatever, or in this case -o nonempty
You can also specify a port on which to connect using SSH, if you're using a non-standard port.

So, for me, the three fields in the Tomboy sync look like this:

Username: thisisabore
Folder Path (optional): /home/thisisabore/sync/notes/ -o nonempty

And there, Tomboy will now download your notes, and prompt you everytime there's a conflict between the local and distant notes.

Now, I just have to go through all the differences between these… oh, what fun.

samedi 7 avril 2012

Oh PulseAudio, you are an interesting little beast

So, one can record anything going through PulseAudio (and therefore really, any sound being played back on Ubuntu or Debian) very simply.

Of course, this comes as no surprise.
After all, everything is a copy on a computer, no matter how many layers of impracticality you add for a user (cumbersome flash players à la myspace, silly DRM, etc.) to prevent them from accessing that copy.

No, what's great here is how simple it is to dump the sound being played back, once you look into it.

Without any further ado, here is how to dump anything being played back as mp3, Ogg Vorbis or the almighty FLAC:

mp3: parec -d alsa_output.pci-0000_00_1b.0.analog-stereo.monitor | lame -r -V0 - test.mp3

Ogg Vorbis: parec -d alsa_output.pci-0000_00_1b.0.analog-stereo.monitor | oggenc --raw -q 8 -o test.ogg -

FLAC: parec -d alsa_output.pci-0000_00_1b.0.analog-stereo.monitor | flac --force-raw-format --endian=little --channels=2 --sample-rate=44100 --sign=signed --bps=16 -o test.flac -

parec is the command to record from a PulseAudio device, and -d the flag to specify which device to record from (this must be an input device, and will vary from system to system) We then pipe the data (using the pipe symbol | ) to an encoder, either lame for mp3, or oggenc for ogg vorbis.

For lame, we specify the data is coming in raw format (-r) and we ask the sound to be encoded in V0 quality (~256 KBps). We tell it to use the stdin input (represented by single dash -) and to output to a file called test.mp3.

For oggenc, we specify the data is coming in raw format with the —you guessed it— --raw flag and ask for a quality of 8 (out of 10) with the -q 8 flag. We also request an output file named test.ogg with -o test.ogg, and tell it to use stdin as the input file (to use the data piped through with the |) with the final -.

For flac, things are a little more complicated, as flac demands more information when you encode from stdin. You have to specify the endianness of the data coming in with --endian=little (I tried both big or little, you want little), the number of channels (1 for mono, 2 for stereo, 6 for 5.1 etc.) with --channels=2, the sample rate (44 100 KHz is what CDs use, DVDs are usually 48 000) with --sample-rate=44100, --sign to “Set the sign of samples (the default is signed)” (yes, I'm quoting from the manual, no idea what this does) and finally, the number of bits per second, which is 16 on CDs (hence --bps=16). We then ask for the data to be written to an external file called test.flac with -o test.flac and tell flac to get its input data from stdin (and therefore from parec through the pipe) with the final dash.

That's it.

Neat, eh?

lundi 19 septembre 2011

Deluge et “possible SYN flooding on port 688x. Sending cookies” de la mort.

Mise à jour : ça ne marche pas en fait, le message apparaît toujours. Ça m'apprendra tiens.

Mini billet pour partager une solution toute bête.
Si vous utilisez Deluge (un client Bit Torrent qu'il est plutôt pas mal) sur un serveur sans interface graphique, vous pouvez être confronté à une nuée de messages kernel: [timestamp] possible SYN flooding on port 688x. Sending cookies. Nuée telle qu'elle rendent le terminal de votre serveur inutilisable vu que le message est répété pleeeiiin de fois.

Lire la suite...

jeudi 6 mai 2010

Éclair, Flan and other french pâtisseries for free software geeks

As many of my fellow Android geeks may not be versed in the art of French pâtisserie, I thought I would clear the situation as to what exactly on Earth are an éclair and a flan, and show their superiority to the atrocity (from à pretentious French point of view) known as a donut.

After all, it only seems right to have my sweet tooth and FLOSS meet.
(Thank you, I'll be here all week)

Without any further ado, here are a some pictures of an éclair and a flan, together, in glorious sugary harmony:

Lire la suite...