IPv6 isn't a mess. It works fine.
What has ALWAYS been a mess is Windows.
741 publicly visible posts • joined 17 Nov 2012
No, Windows 95 was not superior to anything else.
Anything else available from Microsoft maybe... But that doesn't say much for Windows 95.
The same capability had been available for UNIX systems for quite some time. And had mostly left it as the menu system is a rather stilted interface.
And it still is. Good for only what someone else has decided is good for you... but not all that flexible.
Actually they were.
The purpose is to fit the wavelength. You put it elsewhere and your signal strength drops... and you can't connect to other systems on the same cable.
The marks were two meters apart - and the end of the cable had a ballast resistor to kill reflections that would wipe out the signal.
Putting things in the wrong place just isolated the computer.
You mean "hire dozens of Windows professionals over" two or three "Linux AND Windows professionals".
One Linux professional can handle many more systems than one Windows professional. The ratios reported are around 50 linux servers to 1 Windows server... But it does vary. Facebook is reported to use 1 engineer for some 1,000,000 users... or 1 engineer per 130 servers (I believe that was for the same engineer).
But the number varies a lot depending on the environment. For a while I was the Kerberos maintenance (and support) for about 15,000 users scattered across the world using several dozen different computer centers, so I tended to get the admins calling about any problems. If I added up all the servers supported that would be several thousand (between 30 and 100 per center, depending on the center).
Anywhere security was mandatory ... left windows out. You can't secure that.
Depends on your distribution... Ksplice allows for replacing the kernel without a reboot...
There are also other methods of patching a kernel without rebooting...
You also are not required to reboot - just apply the patches. When you next do a PM/other reason to reboot, then the kernel will be the patched one.
It is up to the administrator and management do decide when to do a reboot.
Unless you are on Windows when it is at the will of Microsoft.
There wouldn't be a problem if people were not forced int using NAT.
Nearly all the IoT things already use non-routing IP numbers as specified by their DHCP controlled network.
Unfortunately, those same networks are also bypassing the inherent security by applying NAT to them "for convenience" just because the ISP refuses to migrate to IPv6, and stop using NAT.
The BIG question is:
Since this is a mandatory module, doesn't that imply that the SAME facility is on all the other VMs running on Azure?
IF it does, then that implies the other VMs are ALSO vulnerable to the same/similar attack - each custom to the OS being hosted...
And THAT should scare the pants off Microsoft management.
LISP machines compiled to the machine code.
The problem was that the LISP CPU was not followed up. The CPU itself was a dual CPU, one M680xx just for garbage collection, the other was microcoded to be the LISP interpreter.
It worked - and fairly well, but with no family of CPUs planned the company died before being able to come up with a successor.
Are you sure?
The "honest" politician is one that when bought stays bought.
Trump is known for refusing to pay those that are owed - so now those that "contributed" get stiffed. Guess what, nothing gets through Congress.
And if some suitable dirt gets thrown, impeachment can follow, with possible jail terms afterward. The only reason Nixon avoided that was that Ford granted a pardon.