via doo thx

Une surcouche pour utiliser selenium-webdriver

[07:27] < torkelo>| matejz: I have managed to get about 140~ bytes per measurement (ES) asyd
[07:27] < matejz>| and was thinking of using it for metrics as well aviau
[07:27] < torkelo>| which is 12x the size requirement of Graphite (12 bytes per measurement)

[10:16] < torkelo> | agree, if you store more than 100 000 metrics/s I think ES is not a good option. But for short term performance logging the new metric features for flat_white
percentile and moving average, etc are looking very good

Nice trick !

notify-send --hint int:transient:1

De cette façon les notifs ne restent pas indéfiniment

• https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version

via skunnyk

En parlant de chiffrement, j'ai release ça il y a quelques temps.. C'est crade et vite fait mais ça a le mérite de faire les choses simplement.

via skunnyk

A quick note, there are actually 3 modes, not two when it comes to the drivers in use:

HVM: unmodified kernel and drivers using software emulated devices
PV-HVM: unmodified kernel with paravirtualized (Xen specific) disk and network drivers
PV: modified kernel and drivers

For a Xen guest/DomU you can do a very basic uname and lsmod with a grep to list the modules in use:

uname -a
lsmod | grep xen

If uname -a lists a kernel with the string "xen" in it, then you have a modified kernel and it's likely a PV guest, and you will see output from the lsmod command to confirm it. If you have output from the grep on lsmod but no sign of a modified kernel then you are PV-HVM. Without any sign of either, it's a straight HVM.

Note: Generally you can do more with VMs that have the PV tools installed, so that can be quite an obvious pointer, however you can fake the presence of the PV tools to allow suspend/resume etc. so you cannot rely on that in general.

via Doo