18:09:41Krystofthanks! The reasonably lo-tech solution of taking my "hard drive" (if you can call an nvme thing a hard drive: it resembles no hard drive I have ever seen) and putting it into an enclosure has given me access to the data
18:09:58Krystofafter some messing around with cryptsetup and lvm on the one remaining computer in the house :)
18:17:47flip214Krystof: just call it "flash memory" or "ssd"... and it's not that wrong, I guess, it's still harder than a 5ΒΌ" floppy ;)
2:57:49occwhen I (apropos "cpuid") , it prompts sb-x86-64-asm::cpuid , what's it ?
2:58:49occpress M-. on sb-x86-64-asm::cpuid has no action.
3:20:26occfound a project in github related to cpuid, https://github.com/froydnj/cpuid , but it can't be compiled, there is an undefined function SB-VM::MAKE-EA. how to solve it ?
3:37:19hayleyIf referring to https://github.com/froydnj/cpuid/blob/master/x86-64-vm.lisp#L25-L27 that's just a silly thing to do in a VOP; in general MAKE-EA is now EA though.
3:46:37hayleyocc: Here is the gist of it in one file: https://plaster.tymoon.eu/view/3736#3736 And the SB-X86-64-ASM::CPUID is just a symbol that the assembler uses.