Posts by cult@pony.social
(DIR) Post #AQ6ccmAlsI5CGR8kkq by cult@pony.social
2022-11-29T18:45:55Z
0 likes, 0 repeats
So here we are. The SCO v IBM lawsuit. Frankly, diving into that party is something for lawyers, not me. The adjacent lawsuits don't help. SCO alleged IBM violated copyright, IBM filed a countersuit, RedHat wanted an injunction against SCO, SCO claimed AutoZone was violating copyright by distributing linux and Daimler did something with Unix that SCO didn't like.In 2007 SCO lost the suit against Novell. The judge found that Novell owned the copyright and could force SCO to drop the suit. And that SCO owed Novell 95% of it's revenue generated by licensing Unix to Microsoft in the 90s. The judge didn't touch the SCO/IBM conflict.In 2008 the company filed for chapter 11 bankruptcy and reorganized. Their last product nearing into 2010 was capitalizing on hardware virtualization to run SCO Unix on modern hardware on top of ESXi hypervisors. In 2011 UniXis bought most of the company except the litigation rights. SCO renamed into TSG Group. The story of the SCO Group does not end here. The court case is revived after being put on hold because the company was out of money. In 2012 TSG filed to be liquidated. On November 8th, 2021, IBM paid 14 million $ to the trustees of the liquidation of TSG. After 18 years, the court case ends.BUT IT'S NOT OVER YET *jojo music begins playing*UniXis renames into Xinuos, which is the topic of the first tweet and files against IBM and RedHat in March 2021 on the District Court of the Virgin Islands, claiming IBM stole IP property conspired to illegally corner the market and crush competition.We arrive at November 14th 2022, when the Virgin Islands courts and New York courts (where IBM wanted this to happen) agree that litigating this on the Virgin Islands is silly.It has been 19 years and SCO is not done dying yet. Xinuos, who bought all of SCO, continues the fight against windmill giants.Thanks for the read.
(DIR) Post #AQuTzx1wUJsKumyzrM by cult@pony.social
2022-12-23T19:54:49Z
0 likes, 0 repeats
@thephd slams down a printed copy of the entire ISO C++ Standard 2017 EditionHi, big fan, can I have your signature?
(DIR) Post #AQuU2ynEOHoXFbXu1w by cult@pony.social
2022-12-23T20:11:40Z
0 likes, 0 repeats
@thephd I have printouts of both
(DIR) Post #AQuU2zKYOOT8ux8VyC by cult@pony.social
2022-12-23T20:37:28Z
2 likes, 1 repeats
@thephd :izzycrunch: I blame my university for enabling me with free print credit, that was entirely their mistake.
(DIR) Post #ARnzrrPvszlikerDg8 by cult@pony.social
2023-01-19T11:28:13Z
1 likes, 3 repeats
Public Service AnnouncementToday it's only 15 years left until the end of the (signed) 32bit UNIX Epoch. It is likely that the first devices that will be in active use in 2038 are beginning development now.The UNIX ecosystem is surely ready for larger than 32bit timestamps?evil, deep laughter
(DIR) Post #ARnzrtJcpPuadfvD7o by cult@pony.social
2023-01-19T11:30:04Z
0 likes, 1 repeats
https://redd.it/10fqx1tA list of 2k38-incompatible software as of today can be found in the above link. This list is 64bit software.
(DIR) Post #ASi8jtSBL81cKZgkOO by cult@pony.social
2023-02-15T06:29:59Z
1 likes, 2 repeats
Trade offeryou get: comfy snugglesI get: comfy snuggles
(DIR) Post #AU6VPvKY6WHkMNrtjs by cult@pony.social
2023-03-29T08:55:45Z
0 likes, 0 repeats
this is a big mood
(DIR) Post #AVvCtbZO60yhZsJ1Jw by cult@pony.social
2023-05-22T18:39:39Z
0 likes, 0 repeats
status: tummy ache sufferer
(DIR) Post #AWxPiaET95asIhtIlU by cult@pony.social
2023-06-22T18:04:16Z
1 likes, 0 repeats
Once again I'm sketching out a filesystem that I would like.One major new feature this time around is streaming replication. Literally ZFS send but constant. Imagine if you could replicate filesystems like you could databases. If your file server literally explodes you'd have 0 data loss.I also want to expand on ZFS dataset thing. But instead of making it explicit, make it implicit. Compression, replication, redundancy, etc should be configured on a per-inode level. If I want that sqlite databse to use RAID1 instead of RAID5, that'd be cool.Same for snapshots. Just allow snapshotting individual folders or even files.A basic bonus feature would be making the filesystem transactional internally and allow programs to transparently run in snapshots. Like, your backup tool doesn't need to be fancy, you just run it in a special namespace wrapper and it'll only see a consistent view of the filesystem. Possibly could do that down to individual files, ie, once you open a filehandle, you see a consistent read-only view until you close it.Deduplication should work both offline and online. Have a basic low-effectiveness but fast deduplication method at runtime but allow me to run a tool to deduplicate files manually (via the appropriate syscall). (Btrfs has this)Caching should be more flexible. Let me add an SSD as cache and stage writes for later in there, potentially respecting redundancy, ie, writes complete once it hits an SSD and an HDD, so you get read caching for free. Stuff like that (bcachefs has this)And lastly. I want to make it use fractal trees. Instead of writes going where they should be, all writes are journalled into the root tree node. As the system runs, these staged writes are moved down into lower nodes until they hit the leaves and get merged with the actual node. I think this approach could have huge benefits for Copy-on-Write safety that not even ZFS can offer.
(DIR) Post #AamQd7VHEVH8dl6uiO by cult@pony.social
2023-10-14T20:24:51Z
0 likes, 1 repeats
how do you pronounce clang? (this is a compiler question)
(DIR) Post #Ab4sVztzOgwBlOBt8i by cult@pony.social
2023-10-23T22:40:36Z
3 likes, 4 repeats
"can you move a 32bit register into a 16 bit?""technically if the 32bit register has a value that fits within 16bits the answer is yes"
(DIR) Post #Ab8cQWR8hS8kIPu4ae by cult@pony.social
2023-10-25T19:07:22Z
1 likes, 0 repeats
it should be a crime to post a big CVE announcement, give it a cool name and NOT give me a gadget to try it out with.LEMME BREAK MY STUFFFFFFFF
(DIR) Post #AbpJffBkafLjItJ0JE by cult@pony.social
2023-11-15T09:32:52Z
1 likes, 0 repeats
@thephd time to add a mastodon plugin that transparently compiles any code block it sees into WASM, executes it and previews the result
(DIR) Post #AdIN8xhwYWUFRdqF2O by cult@pony.social
2023-12-27T21:58:05Z
1 likes, 0 repeats
@thephd still holding out for LISP to make a comeback
(DIR) Post #AjtKavlTLwgog21Moq by cult@pony.social
2024-07-11T22:45:18Z
2 likes, 1 repeats
AMD and ARM (including Apple) keep winning on the CPU market by... checks notes ... Making CPUs that do not explode.This post is sponsored by the latest Intel CPUs, which explode.
(DIR) Post #AlbSR0cSqHl5r8aS0G by cult@pony.social
2024-09-01T20:52:43Z
0 likes, 0 repeats
I wiped one of my older systems for reasons, I do love watching nwipe while it's deleting it's own root FS. See some services begin to fail as they are unable to continue.Root FS was ZFS, it managed 11 minutes before an error was reported after I issued blkdiscard to the entire disk and then started nwipe on it. After that it crashed on a kernel panic within a minute.On the one hand, understandable. But also for a filesystem touting it's safety and stability, I don't think it should kernel panic that easily.BUt that's honestly part of my experience, I've sysadmin'ed ZFS for 5 years, it's only stable for common failure modes. If a controller breaks or disks do fun stuff like "return all zeroes and discard writes" then ZFS will crash your computer just as badly as the other filesystems will.Soapboxing a tiny bit, we should write modern filesystems in a way that we assume that a malicious actor is gonna be messing with our ability to IO with it. That also includes assuming "the device is discarding writes and returning zeroes without error". ZFS is great if you limit yourself to common disk failures (ie, where errors are reported or disconnects). If the controller is faulty or the disk behaves in non-error ways, good chance ZFS will trash the pool.ext4 and btrfs mostly differ in that they take longer to notice things wrong or the corruption is more extensive without notice. ZFS just crashes faster.
(DIR) Post #AlbSR1uE3jYnqVu9KK by cult@pony.social
2024-09-01T20:58:30Z
0 likes, 0 repeats
Also this is the annual reminder that last time anyone did a survey on how good filesystems are at reporting up write errors, ZFS only qualified on reporting some errors and only common ones. Btrfs and ext4 both mostly swallowed write errors.Part of that is infra, in the modern async "issue write and OK it to the process before the device OKs it" world, the FS can't reliable report such things.That's where we got the postgresql "Fsync considered unreliable" from, a bug that persists on linux and can cause data loss on any DB setting other than "Fsync every write or do O_DIRECT"
(DIR) Post #AoEPdGl4TICviN0aTw by cult@pony.social
2024-11-20T10:07:45Z
2 likes, 0 repeats
me, trying to sleep: "surely nothing of interest is happening at this hour so I cna try to sleep"the safe c++ post about to be blasted into my DMs: "allow me to introduce myself"
(DIR) Post #AtlBDPjq0cOHF4ucy0 by cult@pony.social
2025-05-04T18:57:59Z
1 likes, 0 repeats
alright, with that pony.social should finally be back online. I hope nothing is missing.the TL;DR here is that around 4:00 in the morning, the database I ran things on (managed offering from DO) somehow imploded and stopped doing anything meaningful. At 10:0'0 I woke up and started fixing. It's now 20:00, I've had to mess with quite a few parts of the database because of various issues (I hate indices and the backup had a screwed up one that required messing with the restore quite a bit).But everything was put back into the tables it belongs to. The database is now hosted internally, which should probably help stability a bit in comparison to an external hosting that is in a different DC.I apologize for the extensive downtime.