Linked by Thom Holwerda on Wed 19th Aug 2009 09:21 UTC
Last week we talked about what Linux (well, okay, X) could learn from Windows Vista and Windows 7, focusing on the graphics stack. A short article over at TechWorld lists seven things Windows 7 should learn from the Linux world. Some of them are spot-on, a few are nonsensical, and of course, and I'm sure you have a few to add too.
Thread beginning with comment 379581
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: a bit of everything
by BluenoseJake on Thu 20th Aug 2009 11:59
in reply to "RE[3]: a bit of everything"
Member since:2005-08-11
it kernel panicked on boot, before loading the filesystem. It was pretty much immediate. As it was my home system, It was faster to reinstall then to start down the long road of fixing that error, then the next one and so forth. I assume it was the new SATA controller that caused the error.
I certainly could have used a live CD, but I wasn't prepared to deal with it because I expected XP to barf, not Etch.
At work, I don't run into those types of problems because only a fool would swap a MB from a production box with a new, totally different MB. I administrate the boxes, which means I want them up and working.
Edited 2009-08-20 12:17 UTC
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-01-10
After login, it continued to grind, then it said it was finished installing new hardware, and wanted me to reboot. When it was done rebooting, XP ran fine. I had to reinstall Etch.
Odd, considering you say this;
That you didn't know you could just boot into a liveCD, chroot into the etch install, and reconfigure everything.
What part of Etch crashed? Just kernel panic, X die, what? I've switched hardware many times, and have never had such a problem. Generally if it crashes on a motherboard setup after a swap, then it just won't run on it at all (due to buggy hardware / driver or whatever) The fact that you were able to re-install on it says otherwise though. Could have just been a module option that was set that messed up on the new motherboard.
XP and pretty much all versions of Windows that have any sort of 'Plug and Play' have had the issue of either being completely unstable after a major hardware swap, or simply don't work.
One thing that could have messed up your Debian install was AHCI vs Legacy. AHCI has been kind of a harsh nail for all operating systems (for example, to get AHCI support in Windows at all you have to reinstall to use it, but for the most part it'll emulate the legacy mode, which Linux doesn't seem to like too much.)