There is also thermochemical cracking which could solve two problems at once - use waste heat from a high-temperature nuclear reactor to make hydrogen as well as conventional baseload generation.
Or, just use concentrating solar - some of these projects reach the temperatures necessary as well.
1. generate a certificate, and add it to the system keychain
2. sign modified kext with new certificate, using the kext signing process outlined 5 months ago at WWDC
3. ???
4. Profit!
In fact if you used this hack in the past, the first time you boot to Yosemite it tells you that the software that performed that hack is not compatible and shitcans it.
At least that's exactly what happened on my Mac Pro.
This is truly a "We're not done until 3rd party stuff doesn't work" situation that everyone always suggested MS had (and MS probably did have to some extent).
Yeah, them turning on a policy that says all kernel-mode drivers need to be signed was clearly a response to one guy writing a binary patch hack to add TRIM support to 3rd party SSDs using Apple's AHCI kext.
That's truly what this is - an unintended consequence of making things more secure and accidentally breaking a completely unsupported modification of the operating system. Would I like to see TRIM enabled on 3rd party drives? Absolutely, as I have two of them in my Mac Pro. But let's not fly off the axle attributing this massively over-scoped change to the incredibly small minority of people that not only put in a 3rd party SSD, but enabled TRIM via this guy's binary patch of Apple's driver.
This is unintended, or at the very worst, a happy coincidence for Apple. Consider the bullet-point version of this scenario:
- Apple's AHCI driver doesn't enable TRIM on non-Apple SSDs. Apple made a decision way back at the beginning of SSD support to not enable TRIM because of buggy firmware on early SSDs. They decided to eat a performance hit rather than have a crap drive eat user data. They likely have never revisited the issue, because those drives are still out there.
- 3rd party SSD manufacturers don't bother supplying OS X drivers that enable TRIM, favoring their customers to use a commonly available hack instead.
- commonly available hack modifies Apple's AHCI driver to do it's thing.
- Apple enabled driver signing in the latest OS to increase kernel-mode security. Something that everyone should be happy about.
- commonly available hack can no longer modify Apple's AHCI driver, because the signing would no longer be valid.
- 3rd party SSD manufacturers still don't bother supplying an OS X driver that enables TRIM.
- Apple gets hammered on Slashdot because they increased the security of ALL kexts, because one out of the over 200 kexts installed with Yosemite was being hacked by a 3rd party software to enable a feature on a 3rd party device. Shame on them!
The funny bit, is that you can turn off the driver signing requirement and hack the AHCI kext anyway, but OMG EVIL APPLE DOES EVIL!!! handwaving will drown that out.
in fact it appears to exist solely to stop third party SSDs performing as well as Apple ones
Really? Requiring all kernel-mode drivers to be signed is specifically to stop 3rd party SSDs from using TRIM? Are you cracked?
This is an unintended side-effect of enacting a higher-security-by-default policy. Otherwise, this is an incredibly inefficient and massively over-scoped way to put a finger in someone's eye for having the gall to buy an aftermarket SSD.
So disable the kext signing and stop crying.
sudo nvram boot-args=kext-dev-mode=1
Do you really think that in a room somewhere, the discussion went like the following?
Engineer: "So we had this idea to require kext signing to increase security. What do you think?"
Manager: "PERFECT. This will totally fuck over all those cheap bastards that buy a 3rd party SSD and then turn on TRIM anyway! I LOVE IT!!"
Engineer: "Uhm... we were talking about a security issue. How did you leap to one minor only-experienced-by-a-small-subset-of-users thing instantly?"
Manager: "Because I'm an EVIL MONEY GRUBBING CORPORATE OVERLORD, and this is a hypothetical conversation on Slashdot!"
Engineer: "..."
Is that more likely than this is merely an undesirable side-effect of Apple making their OS more secure? They don't turn on TRIM because there are older drives out there that totally suck at it and vomit on themselves if it's enabled - which is why Linux has a blacklist in it's AHCI drivers. Apple isn't going to test TRIM functionality on every SSD ever manufactured - they're going to QA against what they ship, like any other company would.
Besides, it's trivial to turn off the kext signing and re-enable TRIM if you're that worked up about it. sudo nvram boot-args=kext-dev-mode=1
Just don't ever clear the nvram and reboot, or you won't be able to load your hacked AHCI kext until you re-introduce that NVRAM flag from recovery mode.
The NT 4 MCSE exams were a joke, because Microsoft was still trying to get people in the door against Novell.
Once word got back to Microsoft that nobody cared about the MCSE battery of certifications because they were viewed as being slightly tougher than CompTIA certs, they revamped the entire thing for Windows 2000, and made it actually something you needed to study for.
But it was too late - even 14 years later everyone views the MCSE as a joke.
The days of the NT 4 paper MCSE are over - Microsoft fixed that by making the infrastructure exam a complete bitch several years back.
MCP is only one of the MCSE tests though, so pick the easiest (workstation cert) and get yourself a certificate in about an hour of brain dump reading.
MCP, however, is a pushover. You can get that by simply passing one of the MCSE tests, usually the one centered around the workstation OS.
If you can install it and do very rudimentary administration, you can get an MCP.
Still impressive at the age of 5 though.
Just like the product.
The company I used to work for implemented Microsoft's Yammer, and it was a vast wasteland devoid of any content whatsoever. Just people wasting time with "shout outs."
This is Facebook being led down a path to nowhere because other companies decided to go there. Unfortunately for all of them, these are solutions to a question that nobody asked.
If you're talking about a MacPro1 that shipped in 2006, then yes, you aren't going to receive support.
I'd challenge you to find ANY hardware company that supports stuff that is 8+ years old without an annual maintenance agreement in place.
WiFi is a nightmare if you buy residential / SoHo gear and expect it to do the job of gear meant for radio-dense environments that you see in education or enterprise.
Get a real WiFi network, and it's not nearly the problem most people make it out to be.
I could see people switching away from Java to
I know of a multi-billion dollar pharmacy business that is running on a Java 6 app, and will take a rewrite to get off of it. Oracle wants to charge over $1M/year for patches they are already writing anyway, because they decided on a whim to kill public support for the platform after creating an incompatible Java 7.
Why rewrite for a new version of Java where you will ultimately end up with the same shithead money-grubbing tactics, when you could rewrite in C# (which has much better functionality than Java now anyway), with the frameworks now open and cross-platform?
Living on Earth may be expensive, but it includes an annual free trip around the Sun.
