Linked by Howard Fosdick on Sat 24th Nov 2012 17:52 UTC
Editorial Do you depend on your computer for your living? If so, I'm sure you've thought long and hard about which hardware and software to use. I'd like to explain why I use generic "white boxes" running open source software. These give me a platform I rely on for 100% availability. They also provide a low-cost solution with excellent security and privacy.
Thread beginning with comment 543306
To view parent comment, click here.
To read all comments associated with this story, please click here.
lucas_maximus
Member since:
2009-08-18

Although the actually usability gap between Windows 7 and the most popular currently Linux distros is virtually nonexistent, stuff happens. When stuff happens in Windows, people shrug and accept it. When stuff happens in Linux, the typical response is a tirade about how crappy Linux is. Even if you're in a position to insist that your consultants are Linux-knowledgeable, I foresee needing the one box running Windows (probably w/a QuickBooks license) for whoever is answering the phone and keeping the books.


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.

Reply Parent Score: 4

Alfman Member since:
2011-01-28

lucas_maximus,

"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)."


I've had long standing issues with Grub on removable media. Infuriatingly they didn't fix this with grub2. The partition map grub used was probably incorrect for your system, and grub stabs around cluelessly loading from arbitrary drives. If you manually fixed the UUID, you should also check that it's loading the right kernel as well. It might still be using a kernel on your hard drive and just using the UUID to boot the distro on your sd-card.

Is this an image you compiled yourself? Most linux live boot disks use syslinux instead because it doesn't get confused about what media it needs to boot off of.


"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..."

There's no excusing the grub problem you had, but I don't think your generalisation is fair. Sometimes the easiest path to fixing a windows problem is to reinstall it.

Reply Parent Score: 2

lucas_maximus Member since:
2009-08-18

There's no excusing the grub problem you had, but I don't think your generalisation is fair. Sometimes the easiest path to fixing a windows problem is to reinstall it.


I actually disagree unless the machine is or was virus infested (there is no way to say there is something the AV didn't catch).

A lot of Windows problems can easily be fix by either looking through the event viewer, testing the memory (I use the Windows Memory tester CD ... seems to work fine and not as verbose as memtest), or using tools such as CCleaner and the task manager.

Windows isn't a magic box that happens to work until it stops working.

Reply Parent Score: 3