Overall, while IMO the laptop should be warrantied against such failure, specifically in the Linux case the warranty may indeed be void. The reason is that the power management on Linux by default has no thermal feedback. On Centrino derived laptops under Winhoze it does and it will throttle the CPU frequency if the laptop is overly hot (even if you turn the power savings off).
Any notebook worth having will put thermal management into the ACPI embedded controller firmware. This will normally start the fans when things get hot, and shut the notebook down when things get too hot. However, if the notebook is designed and used properly, the latter should never happen. Linux can do thermal management through ACPI and a lot of distros enable some sort of CPU frequency scaling/throttling by default; scaling is mostly done in response to power supply, but things like cpuspeed can also monitor temperature and scale down accordingly (again, if this is necessary, the notebook is broken). The best situation is to have the software/user decide how fast the CPU should run and the firmware/hardware decide best how to keep it cool, rather than do stuff in the ACPI tables that requires the kernel to switch on fans at given trip-points --- not least because there's a whole truckload of broken BIOSes with bad DSDTs out there. Leaving thermal management up to the operating system is just stupid.
When is the last time you used sed, awk, grep, instead of any of the bloated software mentioned in the original post? (iTunes or any media player)
Any skilled "UBER GEEK Fucker" worth his or her salt would use these tools on a weekly to daily basis, since they allow much more flexibility than the "bloated software mentioned in the original post".
So lemme get this straight: a modern filesystem designed and engineered with a specific purpose, capability- and feature-set outperforms an older, more modestly-specced general-purpose filesystem designed with smaller volumes in mind in tests of such capabilities and feature sets?
A website that cares about duplicate detection! It's as if they understand that readers don't want to read the same story again and again and again! I wish I could think of another website that would benefit from this technology!
Hope it comes with a remote-control kill switch. Hope it doesn't figure out how to circumvent the remote-control kill switch. Hope it doesn't build a bigger version of itself...
Slashdot Mirror
I wouldn't've thought it possible, but here we are.
JUSTIFIED
So... um... where's the interrupt dispatcher at? Come to think of it, what about the IO handler or CPU scheduler?
and almost NSFW!
Funnily enough, I don't have any problems with WiFi, either. I use WPA-Enterprise and Fedora 7. Works great.
Used to work under Windows XP, too. Then it decided to stop working. Damned if I can get it going again.
Fucked if I can be bothered.
metastandardisation.
So lemme get this straight: a modern filesystem designed and engineered with a specific purpose, capability- and feature-set outperforms an older, more modestly-specced general-purpose filesystem designed with smaller volumes in mind in tests of such capabilities and feature sets?
Say it ain't so!
Er, "Kick out the YAMS, motherfucker"?
...given all the recent murmurings of policy shifts, etc.
A website that cares about duplicate detection! It's as if they understand that readers don't want to read the same story again and again and again! I wish I could think of another website that would benefit from this technology!
Nay, overw0rk'd.
Good job GP didn't mention the chocolate eclair, then...
I think you're labouring under the false assumption that the cream bun is for eating.
Fucking tricky one, eh?
Like choosing between an anal probe and a cream bun.
Hope it comes with a remote-control kill switch.
Hope it doesn't figure out how to circumvent the remote-control kill switch.
Hope it doesn't build a bigger version of itself...