segui i sogni

Posted on by
2

questo post lo dedico a Carlo e Fabiana, una coppia di amici conosciuta tramite il blog di lui e alcuni post comuni sul blog di Fuggetta
dopo aver, come tutti, combattuto contro i mulini a vento in Italia, hanno preso 2 biglietti di sola andata per Londra… lui project manager nell’information technology, lei gestione risorse umane per una nota casa di moda, entrambi con la passione per la fotografia

Il vecchio blog di Carlo non parla più delle sue idee, ma é una delle sue idee… Carlo & Fabiana fanno, ci credono, scendono in strada e fotografano… FChouse.com diventa The Round Peg Photography, e poi the London Boudoir … una passione, diventata lavoro

ecco un video, del dietro le quinte, della campagna per un’azienda di intimo che hanno recentemente realizzato… complimenti ragazzi 😉

http://www.londonboudoirphotography.com/2012/05/enamore-underwear-campaign-by-london-boudoir-photography/

mdns aka bonjour on linux

Posted on by
Reply

k, if you need to scan your network for a printer or an apple time machine, what you are looking for is anything the apt catalog as “mdns”

xxxx@xxxx:~$ mdns-scan
+ xxxxxx [c4:17:fe:xx:xx:xx]._workstation._tcp.local
+ 50-xx-xx-xx TimeCapsule._sleep-proxy._udp.local
+ NZ+LP45QU62ENs7oU3SC+xxxxxxxxxxxxx._acp-sync._tcp.local
+ TimeCapsule._airport._tcp.local
+ TimeCapsule._afpovertcp._tcp.local
+ TimeCapsule._smb._tcp.local
+ TimeCapsule._adisk._tcp.local
^Cowsing ...

p.s. aka “avahi”, aka “zeroconf”

temperature

Posted on by
2

fatemi capire… sin l’altro giorno, si moriva di caldo… con un vento gelido, per cui si girava comunque con l’impermeabile per non venir messi KO a letto (sudi > vento gelido > no buono)

oggi, ci sono 26°C … e’ tutto il giorno che sudo come non so che… ho levato la maglietta a maniche lunghe e nonostante fossi con una sola t-shirt crepavo cmq di caldo

ora, incuriosito sono andato a vedermi le statische dei cambi di temperature stagionali tra Berlino, Bergamo e San Francisco… cosa ne salta fuori? che a Berlino abbiamo quasi 35°C di sbalzo tra la minima di -5°C (a cui non credo molto, visto che l’inverno scorso avevamo ~ -20°C) e una massima di +30°C (estate scorsa erano quasi 35°C, questi paiono dati del 2007)

cmq, andando a vedere invece la California, siamo a uno sbalzo termico tra +6°C (minima invernale) e +18°C (massima estiva), per un soli 12°C di differenza… oltre a piovere quasi nulla (notare come Bergamo sia tra i 3 il posto piu’ piovoso)

…se non fosse per i terremoti che affliggono la California, per i casini col visto, per il sistema sociale inesistente, e per gli affetti che rimarrebbero lontani in Europa, sarebbe da prendere e andare subito

 

src: http://www.climate-charts.com/

jenkins msysgit publickey

Posted on by
Reply

literally… how to waste half a day digging for help on the internet
… and solving thanks to an issue had long time ago

k, you need to have your damn windows project building via Jenkins…
…if you work on SVN things are pretty easy, since the SCM is handled via an SVN Java library: you get your Jenkins Service installed using the Java Web Start functionality provided by Jenkins, and after having your fight with Visual Studio Express 2008 (“call vcvarsall.bat x86” & set VCTOOLS, VCTOOLSINC, WINDOWSSDKDIR) and QT, you are ready to go

now, you decide it is time to move to git + public ssh key authentication… *pray* … loudly

you need msysgit & tortoisegit, install them but don’t install msysgit on its default path… put it in c:git or nothing will work if you have it under C:Program Files (x86) … the tool doesn’t love those nice spaces in the path… you’ll waste ur time fiddling with it

secondly… ensure you have c:gitbin in the general PATH, and not only c:gitcmd … despite of what you’ll find on forums, to me git.exe was working, while git.cmd was not… up to you

then… you need to tell msysgit who is going to handle the private ssh key… set an environment variable as GIT_SSH with “tortoiseplink.exe”, ensure you have the bin folder of the TortoiseGit project in your PATH

then you need to tell the system which ssh key to use… and here starts the pain… since git.exe and tortoiseplink.exe gets shipped with no debug logging, or barely NOTHING…

I suggest you have a dedicated user to the Jenkins’ activities… named “jenkins” for example. Try to checkout the project via the UI integrated in Explorer by TortoiseGIT, just to be sure the keys are ok, and the git server is reachable. Taken that out of the equation… open up a cmd console and do the same commands by hand… git clone git://whatever … git pull… git status … all ok? I doubt…

At this stage, you realise that you have no way to specify the ssh key, the only way is to install “pageant” from the Putty project… u add the key to it, as ur beloved ssh-agent, and you think you are done… WRONG!
Jenkins won’t be able to use it… you think that forcing the service to run with “jenkins” credentials would solve… WRONG! it won’t see or have the scope to see the “pageant”, so you are back to ground zero…

…than I got the flash! Years ago I got nuts with Putty, cause it had somehow cached some options, like an ssh key, as default settings… At this stage I fired up Putty (I had to download it, only some components are coming down with TortoiseGit) and select the Default Profile, LOAD it… go to the ssh settings, select the key you’ve previously use (and converted with putty keygen) to be used with TortoiseGit, and SAVE

Stop “pageant” and try by command line all the git you did before… works? good… now try the same from Jenkins…. TADA!!!!!! Well done…