Linked by Howard Fosdick on Sat 24th Nov 2012 17:52 UTC
Permalink for comment 543306
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2009-08-18
Not being funny, but the other day I install Fedora 17. Booted from USB stick, I had an error that basically stopped the live distro to boot up, google the problem and there were clues on how to fix the problem. I made a guess that I had to remap the UUID of the USB drive in Grub so I resorted to writing UUIDs of disks down (one was 16 characters long and I think it was my SD card).
The thing is that with a lot of Windows errors there tends to be a work around ... when Linux dumps you at a terminal with a cryptic error message or something just offers no output after erroring out(usually GUI apps that are basically a front end to the CLI) ... it does come somewhat frustrating.
In reality there are very few Windows errors now that aren't friendly.