asciilifeform: The youth: ‘Nonsense! You don't suppose the Germans are going to encourage Fascism in this country, do you? They don't want to breed up a race of warriors to fight against them. Their object will be to turn us into slaves. That's why I'm a pacifist. They'll encourage people like me.’
asciilifeform: Orwell: ‘Do you really want to see your children grow up Nazis?’
asciilifeform: must add also that the possibility of emulating a reasonably unix-capable computer is relatively recent. in university 'operating systems' courses in '99 folks were still rebooting actual pc, with floppy, 500 times a day. in 2006 - qemu.
asciilifeform: that we tried to fire and somehow surprised
asciilifeform: because 4) we have a rusted-solid 'luger' from 1941
asciilifeform: and 3) static builds never really worked for items of any complexity
asciilifeform: but none of it changes the fundamentally bowel-loosening fact of discovering that 1) extant linuxen are incompatible in eldritch ways 2) that impact bitcoind build
asciilifeform: mircea_popescu: sometimes, you can take the contents of the emulator and - if it exists and you have it in your collection - run it on physical iron
asciilifeform: x86_64 contains specific provisions for running a process in 'short' (x86) mode
asciilifeform: mircea_popescu: the short version of the difference is that a 'hypervisor' emulates -certain- instructions, that are understood to modify the global state of the machine in ways which would allow the guest os to monopolize the hardware (e.g., write a block to the disk at index I) whereas an emulator emulates -all- instructions executed by the guest
asciilifeform: actually the rub with hypervisor is that the 'guest' -can- affect the 'host' quite often.
