#whenallyouhaveisahammer #unholycomputing #ididabadthing #hardwarehacking #hardwaregore #cursedcomputing
"I had to reboot my car charger to make it work again" and other phrases that shouldnβt make sense but they do.
People complain if I put Microsoft Bob on #macos9, or when I destroy a #retrocomputing DVD drive. But out there in the real world people are building things like this and nobody bats an eye.
That's right, a Linux distro where NodeJS is the entire userland. And they call it "lightweight"... compared to...?!?!
"thanks" @nixCraft for making me aware of this.
Your eyes are not deceiving you... I got an Apple TV 1st Gen, the only x86 based model (it uses a Pentium M as its CPU) booting Windows XP Service Pack 3! For reals!
This was possible through a small security flaw in the Apple TV's firmware and boot process... while the Apple TV looks for a boot.efi file on its boot partition and has it load a Mach-O binary to be able to boot, it doesn't actually care about the actual contents of the file! So by that note, you can wrap a kernel or bootloader from another OS into a Mach-O file and name it mach_kernel, and the Apple TV won't care and will happily boot it! So after this little escapade of cursed computing, you know Linux is next! π
More deets are in this video, along with a link to grab a premade disk image from the Internet Archive!
https://youtu.be/v2w5MmiRHUo
The entire project was done by distrohopper39b, who chronicles his work on the project from beginning to end here:
Wait, the first generation Apple TV can actually boot Windows XP now??
https://github.com/DistroHopper39B/NTATV
Hmmmm... I think the last part of the spell I need to do some *extremely* cursed things to the Apple TV has been revealed!
Let's try a certain cursed Linux distro on it, shall we??
I wounder if we'll soon see #IE11 for #Linux as peak #CursedComputing sooner than later...

So it turns out you can monitor Windows hosts from Netdata just fine, provided you just use the windows prometheus exporter, and tell another agent on some unix system on the network to fetch that as jobs, and tag them as Virtual Nodes so they show up as their own machine in the dashboard.
It is: a bit cursed, but also nice.
Today I learned that dependency manage in Perl using a floating point numbers to compare version strings
I'm still processing the implications of this failure message, but I feel the need to scream into the void.
EDIT: Turns out its a bit more sane than that, mark Gardner explains it here: https://social.sdf.org/@mjgardner/110495135782384907
@[email protected] No, #Perl module versions are not floating point numbers, they are treated as strings, e.g., 1.200 is not 1.2: https://metacpan.org/pod/CPAN::Meta::Spec#Version-Formats The strings can be either a decimal or at least three integer components preceded by a βvβ (sometimes called βsemantic versioningβ). Any author can choose how they want to set versions. Test2::API is part of Test::Simple, and its author very sensibly just increments the version like an odometer using Version::Next: https://metacpan.org/pod/Version::Next