Posts by Scott Marshall 63 publicly visible posts • joined 9 Feb 2011
As a "Superman" fan, I rather like the idea of "General BSOD" (after "General Zod") which also hearkens back to the old "General Protection Fault" messages we used to see.
However, given El Reg's predilection to "zilla" suffixes, I think "BSODzilla" is the way to go.
Another consideration is that given Windows' propensity towards crashes, or "bingles", "Binglezilla" also works!
Unfortunately, due to work getting in the way, I never got around to submitting these options.
Nice to see another graduate of the South Pacific Surfing Champs here.
I fondly recall my metalwork lessons; I definitely preferred them (and John Morrow's woodworking) to Hugo Shaw's art classes. (Hugo was good, it's just that art didn't resonate with me at the same level as that of metalwork and woodwork).
Both Trevor and John were sticklers for workplace safety, especially around the lathes.
It was through them that I gained my love (and respect) for metal, wood and their associated tools.
Has anyone noticed how similar "influencer" is to "influenza"?
IMHO, many of these so-called "influencers" share many of the characteristics of "influenza", excepts that it's easier to get inoculated or vaccinated against 'flu than these other parasites.
ET because I'm not sure that viruses influencers like the Kardashians and their ilk are entirely human.
RHEL/CentOS has for a long-time been my "go to" Linux of choice.
(IMO, Linux Mint is the only half-way decent Debian-based distro for Muggles)
I absolutely loathe GNOME3. Fortunately, apart from CentOS on my notebook, all my Linux servers are non-GUI (ie headless/SSH only).
MATE and Cinnamon are excellent GNOMEish alternatives to GNOME3, however I switched my desktop allegiance to KDE precisely because of the abomination that GNOME3 was when released way-back-when in Fedora.
So, so long as KDE/Qt remains available for CentOS, I couldn't give a rat's arse whether Dead Rat* deprecate KDE in RHEL or not; I absolutely refuse to have the excrement known as GNOME3 shoved down my throat once again.
*Dead Rat because that's what they'll be after they get swallowed by the Sargasso Sea that is Big Blue.
Calling the corporate/banking slime balls "dung beetles" is malicious slander against dung beetles.
Dung beetles provide a very useful service, breaking up and burying all the crap left behind by various creatures and thus helping cut the food supply and nursery for the maggots of various flies.
The added benefit of the dung beetles burying the crap in the ground is that it enriches the soil making it a better bed for plants.
So, don't call corporate slime balls "dung beetles"; call them for what they really are - "maggots".
The call-out rate for Cloud-based services is determined by the "risk" multiplicand I call the "Cloud Fuctor".
The more services that one has "in the Cloud", the higher the "Cloud Fuctor" multiplicand, which will always be ≥ 1.0
The risk can be mitigated by distributing across multiple providers.
Nothing should be in the clouds (except water waiting to precipitate).
Neither aeroplanes nor data should reside in clouds for the same reasons. It's hard to see whom else is sharing your space, and any crashes are catastrophic.
Of course, that doesn't stop the marketing-droids from spruiking about "the advantages of clouds", but then again they can't tell the difference between having one's head up one's arse and having one's head in the clouds.
I like to call that similarity the "Fog Bog™"
<FTFY>
Redmond’s advice comes after over 250 million users installed the OS and gave it a thrashing. Those efforts produced data that Microsoft said shows a twenty per “reduction in system stability issues” and the same reduction “in operating system and driver stability issues.”
</FTFY>
I'd say that the above edit is probably the real story.
... that can operate when offline, a change from the cloud-in-a-box’s usual arrangement, as Thales assumes there may be times during operations when getting online won’t be possible.
One presumes that the part about “getting online won't be possible” is actually a euphemism for the “fog-of-war”.
There you have it folks, in IT circles “military clouds” shall henceforth be known as the “fog-of-war”™.
"Fu**wits" and "Fu**tards"?
Seriously, all this "political correctness" hearkens back to the good-bad-old-days of KGB and the political commissars (or politruk) that ensured (enforced?) ideological "purity" in the organisations in which they were embedded.
I wish the so-called "politically correct" w*nkers would realise that their so-called "inclusiveness" actually creates and promotes more divisiveness than previously existed.
There's only one good thing for the precious little marshmallows; being shoved on the end of a big prong and roasted over an open fire.
RAIN: Redundant Array of Infrastructure Networks.
If you don't use RAIN with CLOUDS, then you've MIST the point.
(MIST: Multiple, Independent Service Technologies)
RAIN helps you avoid DROUGHT when running services on CLOUD.
DROUGHT: Distributed Randomly Over Unreliable Global Hosting Technology
Here in Down-Underland, the Queensland Department of Health had similar problems with, yes, a payroll system developed by IBM.
cf: Learning from the Qld Health payroll fiasco
... and ...
Queensland Health payroll fail: Government ordered to pay IBM costs
Once again, due diligence by the government agency (or agencies) was not adequately performed (if performed at all).
Of course, let's not mention the Australian Census debacle. But then again, let's do:
Tech giant IBM pays about $30m compensation to taxpayers over botched census
The nbn™ was a great idea, but the implementation has left much to be desired.
The ISPs/RSPs need to lift their act too, as from what I can see none of them seem to offer any tools to help their customers choose an appropriate (??!!) nbn™ plan from their offerings.
It should be easy; customer logs in to their account on the ISP and clicks the "help me convert to nbn™" link.
From there, the ISP (who already knows their customer's current plan inclusions) could produce a summary table showing "current plan" and "nbn™ best match".
A web form could also be pre-filled with all the customer's current information and plan details and then the customer could select any additional "nbn™" features they wanted, before hitting "submit", "confirm", "go for it".
Well, one may very well think that; I couldn't possibly comment.®
For the majority of home users, they don't need IPv6 (let alone want).
Consider the raison d'etre for IPv6; every device in the world (and then some) can have a unique, directly accessible public internet address, without the need to traverse NAT between private LANs and the limited pool of accessible IPv4 addresses.
But, does one actually want every one of one's devices directly accessible from the internet?
Methinks not. Security becomes a more complex issue, and the average punter barely understand security as it is.
So, for Jane and Joe Q Public who just want to get out to the internet, and don't give a rat's arse about running up a Web/FTP/whatever server at home, an IPv4 address delivered from their ISP via DHCP to their router, with everything home-side sitting behind NAT in private IPv4 space is all they need (and probably want). The ISPs can provide the infrastructure to bridge between the IPv4 addresses they assign to their clients' routers and the outside IPv6 world.
Those of us who do want to be able to get to our inner-net from the outer-net will want a static IP address. If we want/need to avoid the NAT-trap, then IPv6 is how we will need to go, and of course we'll need to ensure that only the devices we want externally visible will be accessible through whatever firewall and perimeter security devices we interpose between us and them.
For the average Joe (and even many organisations), not everything needs direct access from the internet, so private IPv4 addresses are more than adequate.
Back when I was a wage-slave to Big Blue here Down Under, because I was a "privileged user" the only desktop client I could use was a Linux (RHEL) notebook.
We could only use (and only permitted to connect) Iron Key encrypted USB drives for any data we downloaded.
The problem of course was that the Iron Key drives weren't usable on Solaris and AIX systems, and guess what I spent most of my time managing?
Once again, a policy triggered by issues in the Wintel world bollixes things up for us who use/manage non-Intel platforms.
Now, even though we weren't allowed to connect our mobile (cell) phones to the laptop USB ports, the policy at the time didn't specifically disallow Bluetooth connections!
I've no idea what the policy says about "non-physical connectivity of external devices" now (if anything).
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2023
