Well, now I know why it is bad practice to write code while logged in as root =) I'm learning SDL and after running one of the programs I had written I started getting "Segmentation Error" when trying to use 'ls' and 'tar'. I restarted my computer and got a nasty error saying /dev/hda2 could not be mounted.

Well, at least I've learned enough in the last couple of days to be able to reinstall linux and get my internet connection working (first try this time!).

So, I have now learned my lesson and will not develop code while logged in as root =)

- Stephen

I didnt know that, am fresh to Linux., and have been writing code all day. Thanks for the heads up!

Thanks for posting that -- it's a lesson that every Linux users ought to take to heart (only use the priviliges you need, particularly when trying out new, possibly buggy software, whether it's written by you or somebody else). Let this be a lesson for those people who come in here asking "Why can't I just do everything as root?"

N.B. sometimes it's impossible to avoid running new code as root, for instance when developing system programs (or even kernel programs, which run with kernel priviliges). In these cases, it's a good idea to test the code on a separate machine that you would not mind reinstalling if something goes wrong.

In this context :)


qemu is starting to look quite promising,
specially for linux as both host and guest OS ;)

Create a 3 GB disk-img, install a minimal dev-system,
grab a tgz copy of it and - voila! :)

My qemulated Slack (to a command-line login) boots
in only 15s more than the real thing on the same box.
Quite impressive.



Cheers,
Tink

also have a cd-based distro like knoppix as a back up to check for the harddrive just in case.