
Why would techies be scratching their heads ?
It was well publicised by Intel that the microcode updates were causing reboot issues, and Red Hat have simply followed all of the other vendors and pulled those updates.
Do keep up... !
30 publicly visible posts • joined 17 May 2013
Reading the comments on the kernel mailing list, it doesn't appear that it was just Linus who wanted to call it Fuckwit, if at all...
https://lkml.org/lkml/2017/12/4/709
2) Namespace
Several people including Linus requested to change the KAISER name.
We came up with a list of technically correct acronyms:
User Address Space Separation, prefix uass_
Forcefully Unmap Complete Kernel With Interrupt Trampolines, prefix fuckwit_
but we are politically correct people so we settled for
Kernel Page Table Isolation, prefix kpti_
Linus, your call :)
https://lkml.org/lkml/2017/12/4/758
On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
>
> Kernel Page Table Isolation, prefix kpti_
>
> Linus, your call :)
I think you probably chose the right name here. The alternatives sound
intriguing, but probably not the right thing to do.
Linus
Now if BT started offering BT Sport to those who weren't either Sky or BT subscribers, and at a sensible price, they *might* get a bit more business in.
Believe it or not BT, there are people who might want to watch say the cricket or rugby, who have don't have broadband through you, don't have a satellite dish, and would rather not spend money on streaming services of dubious legality, that may or not be around next week.
These two recommendations made me cringe a bit:
R19 Update the CAD servers to a modern, supported platform that replaces the existing Itanium servers.
R20 Update the Oracle version to current (or one below as a default).
So probably still on Oracle 10g (10.x) if not earlier, but HP-UX or OpenVMS ?
At a former workplace, we had fun one day, when the card reader controlling access to the computer room decided it wasn't going to work anymore.
Fortunately, whoever installed the door control system mounted the box that controlled everything outside the computer room. Once I'd figured out which of the connector blocks went to off to the door exit button, it took a couple of seconds with a paper clip to get the door open.
I do wonder why the IETF bother coming up with all these standards, when manufacturers just seem to ignore them...
Having spent a reasonable amount of time working at a courier firm, it's quite amazing what you see when spending a few hours watching how parcels are sorted.
Parcels emblazoned with FRAGILE stickers, are always targets. The let's see how high we can throw this one game is, I'm sure, still a favourite.
When this particular company had the contract for delivering Dell kit, I was quite amazed how well a 19" CRT monitor box would roll, corner on corner, down the chutes of the sorting machine, rather than slide !
Parcelfarce, Sh*tty Link, Oops, etc. They get their names for good reason.
In the past I've noted that the firewall on my PC which is sat behind a Home Hub 5, has blocked incoming connections, even though the HH is set to block everything and there's no NAT configured.
Must remember to check what ports were being let through when I get home tonight...
I wonder if this is related to the following announcement made to the BugTraq mailing list last week ?
http://seclists.org/bugtraq/2015/Mar/48
During a source-code audit of the OpenSSL v1.0.2 implementation for Linux; conducted internally by the Advanced Information Security Group, instances of deprecated function use, were observed in relation to the GHOST vulnerability (CVE-2015-0235).
If it is, then there shouldn't be anything to worry about if you've patched glibc...
"setting you back at least $23,000 per Oracle SPARC processor it's installed on, we've heard"
Based on the price list here:
http://www.oracle.com/us/corporate/pricing/technology-price-list-070617.pdf
it's $23,000 per Processor. But most SPARC processors use a factor of 0.5, so it'll only be $11,500...
http://www.oracle.com/us/corporate/contracts/processor-core-factor-table-070634.pdf