Wow! I’ve been thinking about how a WebAssembly runtime in CloudABI would be an awesome “write once, run everywhere” thing… turns out the Cranelift developers are already looking into CloudABI! Awesome!
Cool ARM laptop news that I missed somehow:
- the cause of custom EFI binaries not running on Windows-on-Snapdragon laptops was found: it was alignment. Now GRUB works. (Still, Qualcomm firmware is very weird, you’re always in a hypervisor, the ACPI implementation has some very strange quirks and uses PEPs.)
- the Panfrost driver for Mali GPUs now runs Weston!
The best Cloud-to-Butt replacement I’ve seen yet, thanks to this page:
Butthole was released in 2016 for Firefox to make Buttflare captchas less painful
Looks like NetBSD is already working on the EC2 AArch64 instances! My attempt at running FreeBSD there failed: for mysterious reasons, the system reboots just after the last
Trying to do anything system-level on EC2 is incredibly frustrating. There is STILL no read-write access to the serial console, because Bezos doesn’t believe in debugging or something >_<
Also, about the ARM instances themselves. I am happy to see a big player enter the ARM space. And with custom (Annapurna) chips, even. (Though they’d have much better performance if they just bought some Ampere eMAGs or Cavium ThunderX2s.)
But what’s up with that price? Did anyone at AWS ever look at Scaleway’s pricing page?! On-demand pricing for a single core EC2 ARM instance is almost 20 bucks per month! While Scaleway offers four ThunderX cores for three euros per month!! Sure sure Scaleway is not a big player and doesn’t have a huge ecosystem and is getting close to being out of stock on these ARM instances.. but still, 1/4 the cores for 5x the price.
(Spot pricing is better of course.)
what’s this? :)
Another weird LLVM mystery solved!
So, I was porting LDC to FreeBSD/aarch64, wondering why global constructors (you know, the before-
main() code you can make in C using an
__attribute__ thingy) aren’t running… but only when the executable is linked with LLD. Turns out:
.init_arrayis the only supported way to do constructors on AArch64
and everything in general is moving towards
.init_array— but the default in LLVM is still to emit
clang has code to enable
.init_arraywhen appropriate, ldc did not
and the reason it all worked fine with bfd and gold is that these linkers SILENTLY convert
.init_array. For PERFORMANCE REASONS.
It’s almost 2019, so using a SATA SSD as the boot drive for your main development OS is not cool anymore… and I was running out of space on this 128gb one, so I bought an NVMe drive to replace it. Yay.
Because I don’t have anything with two or more M.2 slots and I was too lazy to find/make a bootable FreeBSD USB drive, moving the system involved inserting the new drive into another machine (server) and using ZFS replication to copy the data. (And forgetting to set
bootfs on the pool, of course.)
But the fun part was that my 10G network card stopped working. Moving the card into the middle slot (from the bottom one) fixed it. Reported a FreeBSD bug.
The weirdest discovery of the day though was that MSI mainboards persist the “above 4G” PCIe setting across CMOS clears. What in the actual heck. This is the setting that breaks display output on most GPUs (funnily enough, mine did display non-EFI things such as the network card’s boot prompt and the glitchy way FreeBSD displays the console when booting on UEFI with the EFI framebuffer disabled). It’s a setting you very much need to clear.
Finally got around to actually trying out ZeroTier. It’s pretty awesome!
Okay, it has a couple downsides:
- it’s not automatically a mesh network, you have to designate a node as a “moon” to make it pass traffic between other nodes (that couldn’t punch holes through NAT)
- the Android client is not open source and doesn’t have UI to tell it to orbit a moon
But other than that… the simplicity is lovely. No screwing around with config files, restarts and whatnot. Just a very small & easy set of admin commands. And automatic IP address assignment (especially 6PLANE) is amazing.
Raptor has revealed pricing for their POWER9 “cloud” VPS. Almost AWS levels of complicated pricing. And it’s expensive. Starting with 10$ per month for just 1 core and 256mb (!) RAM…