Skip to main content

Progrès ou non

 Allez un petit billet pour faire le bilan des choses sur lesquelles, j'ai travaillé ou non depuis que j'ai ouvert ce blog.


En premier lieu maintenant que je suis fibré, je retravaille sur la mise en ligne d'un serveur perso. Il sera donc à la maison, je l'ai déjà fait dans les années 2000 au cul d'une ligne ADSL. J'ai donc trouvé mon serveur se sera mon "pie 3b+", il tournera sous FreeBSD. Il me faut le réinstaller, 16 Go de disque n'est pas suffisant pour mes besoins - malheureusement la carte 128 Go que je possède et qui fonctionne bien dans mon téléphone refuse de booter le pie - pas de message d'erreur et je n'ai pas de câble console/série pour voir s’il se passe quelque chose. J'ai l'intention d'y déplacer mon blog jeux. Celui-ci est hébergé par free, mais sans ssl, avec une super vieille version de dotclear. Donc un OS propre et à jour, et assez de disque pour cela.


Les deux AUF1 que je projetais de monter sont toujours dans leur boîte, j'ai vraiment pas réussi à dégager du temps sans dérangement pour avancer dessus. Il en va de même de la peinture de mes figurines.


C'est sans parler de mes projets d'installer une infra virtuelle pour refaire une infra avec Agent. J'aime ansible de moins en moins. Ni de mon envie d'apprendre le mongol.

Labels:

Comments

Unknown said…
Agent ? keskecè?
10:38 AM
Ludovic Hirlimann said…
Agent ce petit truc qui force ton infra a être comme ton code (comme dans puppet et salstack) !!
6:31 AM
Post a Comment

Popular posts from this blog

Firefox OS's story from a mozilla insider not working on the project

  I clearly remember, but can't date it. I was working for Mozilla messaging at the time ( momo ), being the QA lead for Thunderbird. It was at the end of one of the Mozilla All-hands, maybe in 2011 or 2012. At one of the ending keynotes, we were introduced to Boot 2 Gecko. A hack that would let US - Mozilla own the platform to run a mobile browser on. At the time, the iPhone was going strong and Google was trying to catch up with Android. MeeGo had been in development at Nokia for a while but was going nowhere even when Intel tried to help. Blackberry was slowly starting to die. In the Silicon Valley everything was about mobile, mobile, mobile and the emerging South Easter Asian market, where people would skip computers and use smartphones to join the internet revolution. We were struggling with Chrome and the massive investment by Google to take market share. Our Firefox port on Android was having loads of issues. We were denied by Apple's policies to be present on iPhones....
3 comments
Read more

Key signing party at fosdem 2024

I'm organizing a GnuPG key signing party in order to bolster our web of trust , since there is no official ksp this year. I have organized a few in the past using tools like biglumber (website is gone, if someone know of a replacement or where the source code of site is, I might end up running one again) and others tools . I've also run once the KSP at FOSDEM and helped running it a few other times.    === Details below === When, Where   We'll meet in front of the infodesk stand in building K around 12:00 Sunday Feb 4th 2024. I'll have a sing of some sort with KSP and or Key Signing Party . Once enough participants show up we will move outside to proceed with the party. What to Bring Warm cloths as the party will happen outside this year, like in the good old days. I hope it won't rain, but it might. Piece of papers with your fingerprint written on them. Each piece should look like below:  $ gpg --fingerprint 34246C61F792FBCC1F23BFF296BD1F38FEA32B4D pub ...
Post a Comment
Read more

Are mozilla's fork any good?

To answer that question, we first need to understand how complex, writing or maintaining a web browser is.  A "modern" web browser is : a network stack, and html+[1] parser,  and image+[2] decoder, a javascript[3] interpreter compiler, a User's interface, integration with the underlying OS[4], And all the other things I'm currently forgetting.   Of course, all the above point are interacting with one another in different ways. In order for "the web" to work, standards are developed and then implemented in the different browsers, rendering engines. In order to "make" the browser, you need engineers to write and maintain the code, which is probably around 30 Million lines of code[5] for Firefox. Once the code is written, it needs to be compiled [6] and tested [6]. This requires machines that run the operating system the browser ships to (As of this day, mozilla officially ships on Linux, Microslop Windows and MacOS X - community builds for *BSD do ex...
Post a Comment
Read more