Do they know it's 2024?
A strange announcement given that as of last month CentOS 7 and 8 are both end of life and CentOS as an Enterprise OS is now effectively dead, or at the very least pining for the fjords.
47 publicly visible posts • joined 10 Aug 2023
This is good but unfortunately there's a lot of old code written for CentOS 7 which won't work without major changes on later Linux distros. One of the things about CentOS was the backporting of bug fixes for things like PHP. CentOS 7 uses PHP 5.4 which is different enough to later versions to break a lot of things and that's just one component. It's why many people can't just move things to Ubuntu/Debian etc without significant work or in some cases a complete re-write.
Of course this is a much bigger issue of backwards compatibility, not directly related to Linux and the distros themselves, but this backporting was Redhat/CentOS's most significant feature. With new projects that's less of an issue as other distros now have 10+ year support and no sane person would now use anything connected to Redhat. Also while things like the PHP issue still exist, the issues are better understood. However what was a selling point has ended up being a major trap for anyone stuck using Redhat/CentOS.
I was recently given a backup disk from a relative that had been in a draw since 1992. It read perfectly on a new (old stock) £10 USB floppy drive I bought on ebay.
That's 30+ years from a disk that was badly stored and probably well used and a few years old even before that! Yet modern USB flash drives seem to die if you look at them.
When 3G launched in 2003 it didn't even provide internet access, something 2G already had. It took them another year or so to get that working and another 5 years till HSPA etc made it usable. 3G was always over promised and under delivered, so it's ironic that 2G has outlived it.
"If you think Outlook is any good at email, you really don't understand email."
99.9% of the functionality in Outlook has nothing to do with email. It's a very bad email client with an integrated calendar, contacts and task management system that syncs across all devices and staff in an organisation.
It's shocking nobody else has made anything similar (Lotus Notes is the only thing that came close) as Outlook is terrible yet still the only real option for that use case.
Ironically Outlook doesnt even support Microsoft's own Activesync protocol well. All we need is an open source Activesync desktop client with the shared calendar/task/contact/email functionality that already exists in most mobile phones.
Indeed. My copper based landline that worked perfectly for decades is now a copper based "fibre" connection over the same decades old copper wires and now stops working every time it rains or the power goes out, thanks to BT Openreach and Zen Internet.
There's no timeline yet for anyone to provide real fibre here, if they even know the difference, as we're only a small city. :-(
Because it's Meta that asked for the number in the first place. People lose numbers for many reasons outside their control. Moving house, health issues etc. For those same reasons they may also not be able to login for some time, even if they wanted to update their number and knew they should.
Once the number is lost someone else can access your Meta accounts before you get a chance to update them, if you can even login or know you need to. Every part of that is Meta's problem, not the user that only gave a number because they were asked.
That could work, at least in Seattle:
"A helicopter with a pilot and a single passenger was flying around above Seattle when a malfunction disabled all of the aircraft's navigation and communications equipment.
Due to the darkness and haze, the pilot could not determine the helicopter's position and course to get back to the airport.
The pilot saw a tall building with lights on and flew toward it, the pilot had the passenger draw a handwritten sign reading, "WHERE AM I?", and hold it up for the building's occupants to see.
People in the building quickly responded to the aircraft, drew a large sign, and held it in a building window.
Their sign said, "YOU ARE IN A HELICOPTER."
The pilot smiled, waved, looked at his map, determined the course to steer to SEATAC airport, and landed safely.
After they were on the ground, the passenger asked the pilot how the "YOU ARE IN A HELICOPTER" sign helped determine their position.
The pilot responded, "I knew that had to be the Microsoft support building, they gave me a technically correct but entirely useless answer."
Just a warning if using Zen's Fritzbox...
Don't plug in the Fritz if you value your existing POTS landline working. Especially if your landline is needed for emergency calls.
We have VDSL from Zen which came with a Frizbox, which until a year ago was unused as I had a PFsense firewall. I had to use the PFsense elsewhere so plugged in the Fritz as a temp replacement. Roll on a year and the Fritz was still there, so Zen without my permission or even telling us, decided to move the landline to the Fon port on the Fritz since it was connected. I only found out this is what they had done when I reported the landline as faulty teo weeks after they cut of the emergency line. Although unlikely, someone could have died because of this.
I've now switched back to PFsense and Zen appear completely unable to restore our landline to any kind of working fashon and even though I have a Yealink phone with multiple working AAISP VoIP lines on my desk, the Zen VoIP details wont work. Worse than that, our broadband is very flaky VDSL that resyncs several times a day (ongoing Openreach issue) and the landline is (or was) used in case of medical issues as a backup to VoIP and wifi calling. Zen also have no battery backup options to ensure 999 access.
Our only solution now appears to move the number to AAISP and presumably also the broadband.