Posts by phuzz 6734 publicly visible posts • joined 23 Feb 2010
Those with a legitimate (?) need to send out bulk emails will either move away from Exchange, or learn to live within its limits.
Most of the small/medium companies I've worked with have used external services for their spam marketing emails, (such as Mailchimp). Usually after a particularly spammy overenthusiastically broad email campaign got the whole company blacklisted.
Funny thing is, I never saw any repercussions for the marketing team, other than a bigger budget...
I'm not sure if you'd class them as 'adverts', but even a supposedly 'clean' install of Windows has icons for various games and programs (eg Candy Crush, Whatsapp) that aren't installed by default (thank fuck), but the icon links you to their Windows store page. You can delete the icons, but you have to do it manually (although if I had to install Win11 more often I'd think about writing a script to delete them in one go).
It's not a dealbreaker for me, but it is an added annoyance. I'd happily pay for a real 'Pro' version of Windows that didn't install any of this crap in the first place, then Microsoft could reserve ads for the free/'Home' versions if they feel they're hurting for revenue.
They need to design a totally new platform for that
Did Lockheed Martin or Boeing write this? Because I'm sure they're already working on their proposals to print money provide the USAF with aircraft that will definitely come in on budget. /s
These are only test aircraft, so it makes sense to use F16s, because the USAF has over a thousand of them sitting in boneyards.
A better way to phrase it would be that 'programs have a choice of GUI', so you inevitably end up with bits of Gnome and KDE, and whatever else on a machine, because the authors of different bits of software picked whichever GUI framework they felt like. Anyway, dconf is used by both Mate and Cinnamon, but I don't keep track of what they're based on underneath, providing things work.
You can also get tyres which will emit coloured smoke during a burnout, which is pointless but cool.
xz is maintained by one person, whilst being used practically everywhere. A person naming themselves 'Jia Tan' started contributing useful patches, and generally helping out, so the maintainer gradually started trusting them. At some point, whoever was operating the 'Jia Tan' account, slipped this backdoor in as an unrelated change, and it got passed downstream to distros.
So there is definitely a culprit, and it's the person, or persons, behind the Jai Tan account, who deliberately preyed on the overworked maintainer to insert malicious code. Whoever they are, they're clearly skilled at social engineering. There's no way to tell they're a nation-state or just an amateur, but 'Jai Tan' almost certainly isn't their real name.
"If you can't restore from a backup, then your data isn't backed up", so by testing their restore procedures, Larry was actually helping.
(Tongue partially in cheek, because in my last job, if I had to restore from a backup for someone, I'd also tick off my "tested restores" task for the month)
It's the highest frequency (out of the box) CPU ever sold, so by definition everything else must be currently running on 'slower' CPUs.
It's irrelevant though, because AI stuff typically uses GPUs or other dedicated silicon, and cloud servers get their speed from running many (slower) CPUs across many, many, servers. It's like comparing a Bugatti Veyron to a fleet of trucks.
To put it in perspective, a 14900K (6.0GHz) could compress a bunch of files in WinRar in 14.95s, the previous 13900K (5.8GHz) could do it in 15.21 (based on this review). So the 14900KS is probably a similar increase (or decrease I suppose, depending on how you look at it).
I'm not sure I'd could even notice a quarter of a second speed-up. I would probably notice the difference in my electricity bill though.
I had a similar "this should be fine, ohshit" moment, moving power connections on an HP blade enclosure. It could hold up to eight hot-swappable power supplies, this one had six, but IIRC could operate on as few as two with the small number of blades in this particular unit. I'd already moved the power lead of one PSU to a different UPS, so I wasn't expecting anything different when I pulled the kettle lead out of the next one down. Instead there was a click, and the entire blade enclosure powered down, taking with it several important servers. Cue my boss charging into the server room asking what I'd done.
After some testing, it turned out that one of the PSUs seemed ok, right up until it had to draw any significant load, whereupon it would completely fail. If the enclosure had chosen to spread the load onto a different PSU we'd never had noticed, it was just sheer chance it picked the bad one.
Latency and bandwidth are two different things. The simplistic explanation is that bandwidth is how much data you can transmit/receive at once, latency is the time it takes between you sending a packet, and it reaching it's destination.
Latency is mostly noticeable in online games, or VoIP/video calls. eg when you talk, but it takes a noticeable amount of time before the other person hears you.
(Of course, if you don't have enough bandwidth, your latency is going to go way up, so they are somewhat linked)
I've seen someone get a DIMM in the wrong way around, but not deterred by the notch being in the wrong place, they managed to jam it in hard enough to engage the latch on both ends.
Kind of impressive in it's own way. IIRC it worked fine once the DIMM had been re-inserted correctly.
Clarification
When I first read the article, it wasn't clear that it was the crash-inducing key combination that was introduced in Win2k (etc.). I used the corrections form, and got a reply from the author, Richard Speed* promising to make it clearer, and then another email from elReg staff also confirming the clarification. The amended article makes it much clearer, always use the Corrections form folks, the take their jobs seriously :)
Sorry for accusing you of being Ai, elReg :(
*name checks out ;)
Yep that sounds, well, wrong.
PS/2 keyboards were the norm when Windows 1.0 came out, and definitely worked out of the box with Windows 3. They're still supported on Windows 11, if you happen to have a motherboard that has a PS/2 port.
Win95 could just about handle USB keyboards with additional drivers etc. Win98 was the first version with USB support out of the box. (Although you'd still encounter motherboards which required a PS/2 keyboard to access the BIOS).
Oh, and Hyper-V was first added to Server 2008 and Win8.
Have elReg been letting an AI write articles?
Most data centres have multiple network and power connections, specifically picked to run nowhere near each other to reduce the chances of one JCB taking out multiple connections.
Of course, you can run applications internally, but most offices don't have redundant power or networking, so all it takes is one JCB to bring everything scratching to a halt.
According to The Sun, had this been a real mission rather than a test, the launch would have been successful. The MoD is, unsurprisingly, remaining tightlipped about such matters.
So reading between the lines, they're claiming that when they removed the nuke and replaced it with ballast/telemetry, someone broke the rocket?
SpaceX won't be the single point of failure for Artemis, NASA has also contracted Blue Origin to develop a lander.
It's a more conventional design, but it's from a company that so far has only launched sub-orbital rockets (and is also owned by a potentially volatile billionaire).
Still, I'm not a US citizen, so it's not my taxes being wasted :)
The Amiga had my favourite case sensitivity in it's shell, which was, 'some'.
If you wanted to, you could have FILE and file in the same directory (or any combination of cases)*, but assuming that just File existed, then you could use any combination of case to refer to it and the command line would just interpret what you meant.
* I've yet to find a case when I'd want to have both FILE and file as separate files, but apparently it's important to *nix.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
