Quand nos ancêtres ont-ils commencé à manger de la viande régulièrement ? Des dents fossilisées pourraient apporter des réponses
(Permalink)
Je lisais un commentaire qui résume bien la situation du point de vue de Sam Altman, le PDG de OpenAI :
Si vous ne me laissez pas voler votre travail sous copyright, alors je ne pourrais pas fabriquer cette chose qui détruira tous vos emplois et fera de moi un multi-milliardaire.
S'il promet d'arroser ses copains, je présume qu'il pourra entraîner ce qu'il veut sur ce qu'il veut. La justice n'étant là quasiment que pour protéger les intérets des riches.
— Liens directs
Comment et pourquoi le système politique actuel nous ment et nous agresse.
Un très bon résumé de 45 min tout de même.
— Liens directs
Le gars encore imbu de sa personne nous refait des siennes, c'est plus fort que lui.... Chassez le naturel, il revient au galop.
Il faut toujours qu'il la ramène sur tous les sujets, à croire que le mec a la science infuse ^^
— Permalink
I just had to try and recover a couple files that a buggy program replaced with empty files instead of their actually updated content. Context is an EXT4 FS, on a secondary data partition (and even disk, but that's unrelated).
Linked post is interesting, but a bit over-doing it: no need to actually back the journal up in my case (tho I did it), nor unmount the partition to use either tool.
Additionally the linked article talks about deleted files, whereas here I wanted to recover previous versions of the content of existing files. I guess this requires the program not having rewritten the same blocks, but in my case the program both writes to a temp file first and then renames over (although it happily replaced with an empty file), and wrote a 0-bytes file which likely wouldn't overwrite anything. Anyway, for this use case, the key is the -b
option to give it a time frame that does not include the faulty rename.
So, basically what I did:
sudo debugfs -R "dump <8> $HOME/sdb1.journal" /dev/sdb1
sudo ext4magic /dev/sdb1 -a $(date -d "-2hours" +%s) -b $(date -d "-45minutes" +%s) -f relative/path/to/files/ -j ~/sdb1.journal -l
sudo ext4magic /dev/sdb1 -a $(date -d "-2hours" +%s) -b $(date -d "-45minutes" +%s) -f relative/path/to/files/ -j ~/sdb1.journal -r -d RECOVERY/
At this point I had the files in their state from 45 minutes ago, validated the recovery and remounted read-write. Done.
This was surprisingly easy, thanks to journaling FS :)
To be fair, having the lost data outside the root or home FSes helped a lot, not only because of random applications potentially writing stuff if any mutable data is stored there (/home, /var/run, /tmp and whatnot), but I could also easily install the tools I missed straight away without risks of overwriting precious data blocks.
Matos pour de l'IoT.
— Permalink