Mallory_Ringess
Joined 5 months ago
Joined 5 months ago
The real question is why you seem to be so credulous when it comes to this company. Do you extend this trust to other similar companies or is it only reserved for this specific company? I ask this because you're not the first person who seems to consider this company to be almost above criticism even though they've shown to be just like other companies in all respects. When Jobs was still around this stance was supposedly caused by his 'reality distortion field' but he has been gone for a long time and given that Cook has the charisma of an accountant this can no longer be the reason. What makes them so special to some even though their claims have been punctured many times over?
Block and cover [2], block and cover. For the rest, live on.
[1] https://anathem.fandom.com/wiki/Bulshytt
[2] Yes, I sometimes just cover them with my hand if I happen to use a device without functional content blocking.
This post here does not seem to be like that. I suspect he's really planning on taking a hiatus from the 'net, something like a sabbatical at least. I do think he'll eventually return to the 'net in some form and he might even become active in whatever the free software world has morphed into by then but he does seem to have positive plans for the future. He's starting a magazine centred around an Orthodox Christian community, something which can provide the same type of fulfilment as working on free software projects can.
0: create an empty VM called osmuseum with 4 cores, 8192 MB of memory, no drives, OS type Linux 6.x - 2.6 kernel using whatever vmid fits your schedule
1: unzip the relevant part of the distribution:
unzip virtual_os_museum-2026.05.19-lite.zip virtual_os_museum-2026.05.19-lite/VirtualOSMuseum.utm/*
2: convert the drive images in the Data directory to something understood by qemu-img: qemu-img convert Data/host_x86.vdi Data/host_x86.raw
qemu-img convert Data/guest_images.vdi Data/guest_images.raw
3: import these images to whatever Proxmox storage you want to use for this VM. The host_x86 image is 250 MB, guest_images is 5 TB. Both are sparse images so they won't take up more space than actually required. I'm using 700 as vmid and ext-lvm for storage, change these to what fits your installation: qm importdisk 700 Data/host_x86.raw ext-lvm
qm importdisk 700 Data/guest_images.raw ext-lvm
4: attach these images to scsi0 (host_x86) and scsi1 (guest_images) in the vm Hardware settings page5: set the scsi0 drive as bootable in the vm Options settings page and move it up in the boot order (e.g. ide2, scsi0, net0)
6: boot the vm and change the network configuration in /etc/network/interfaces to fit your needs. In my case I changes the address for br0 to a free address on a local network segment, corrected the broadcast, network mask, gateway and dns-nameservers parameters to fit my network and restarted the networking service (service networking restart)
7: Things should now work, you may want to reboot the vm but it should not be necessary.
Meet the new net, superficially the same as the old net
How to tackle the bug backlog? It is fairly simple, we wind back the clock on network services all the way to the dawn of the 'net, replacing known-insecure things like telnet, ftp and finger with heavily audited alternatives based around ssh etc. The rule is that only audited software is allowed access to the 'new net'. Of course none of those newfangled agents and models are audited not can they be audited in any real sense of the word so unfortunately for SamA they're banished to the 'old net'. The idea would be to get the 'new net' up and running quickly and move critical services which need to be network-reachable there. It needs to be bilt in such a way that even when one of SamA's toys gets access to the 'new net' it can't do much, or anything. The 'new net' could be compared to a 'mission critical API' to essential services, useable by all who need to have access but technically off-limits to SamA's creations. They are available on the 'old net' where all bets are off and which no longer can be used to interface with critical services 'cause they're not connected and can not be connected.
Now all that's needed is to find a way how to implement this without bugs, without handing the ultimate control mechanism to power brokers, without loosing too much real functionality, without ... well, many problems. When the enemy is inside the gates half-measures tend not to work, best find him and lop his head off. Better be careful where you stick your neck, SamA.