See, this is why I need a

Megan — Fri, 29 Feb 2008 14:21:04 +0000

See, this is why I need a good reference.

Quote: I once typed in: rm

pr0gr4mm3r — Thu, 28 Feb 2008 22:42:42 +0000

Quote: I once typed in: rm -rf / by accident once, whilst logged-in as root

I hope there was nothing important on that drive! I ran that command once on a tinker box just to see what happened. I was also amazed at how it didn't crash. I've read stories on how sys admins kept servers up for days with crashed hard drives. Granted, the servers only routed traffic and handed out DHCP leases, but still impressive.

Off the top of my head, I

JeevesBond — Thu, 28 Feb 2008 22:14:19 +0000

Off the top of my head, I would use:

find . -type f -name '*.LCK' -print0 | xargs -0 rm -f

Yeah! Feel t3h p0w4h!

Errrr, and make sure you cd into the right directory first, and do a test run. As pr0gr4mm3r said: rm is dangerous. I once typed in: rm -rf / by accident once, whilst logged-in as root, totally hosed everything! I was impressed at t3h p0w4h of GNU+Linux though, Windows would have stalled and moaned about locks on open system files, but those GNU tools munched the lot down, and the system continued to work, even with nothing on the hard drive! Well it worked until I tried to run a program, then died, I was impressed though (mostly at my own stupidity).

Quote: One thing I was

pr0gr4mm3r — Thu, 28 Feb 2008 20:15:22 +0000

Quote: One thing I was trying to do the other day was remove certain types of files (*.LCK) recursively through directories. Maybe that's not possible.

It's possible with a little scripting. This thread should help. Be careful though because the rm (delete) command is dangerous.

Okay. I have been using this

Megan — Thu, 28 Feb 2008 19:17:47 +0000

Okay. I have been using this tutorial site but it's really broken up across pages.

I have found some wikipedia references to be really helpful so I should look there as well.

One thing I was trying to do the other day was remove certain types of files (*.LCK) recursively through directories. Maybe that's not possible.

man would be fine if I knew what to look up!

Google is what I use as

JeevesBond — Thu, 28 Feb 2008 17:46:30 +0000

Google is what I use as well. It also helps to keep a file of useful commands and some sample arguments.

The advice to use man pages is a good one, they can be a little esoteric, it takes a few tries to get the lingo. Once you understand you'll be able to 'get' most man pages.

Do things in a more task-orientated way, when you want to know how to do something in GNU+Linux, Google it: linux directory list for example. Or you can come on here and ask us.

You're talking Linux/Unix,

pr0gr4mm3r — Wed, 27 Feb 2008 20:39:34 +0000

You're talking Linux/Unix, right? Are you looking for a list of commands or more information on a specific command?

If you are looking for help on a specific command, my favorite references are the manual pages (or 'man' pages). For example, if you need help on the 'cp' command, type 'man cp'. For help with understanding the man pages, type 'man man'.

Here are some basic commands to learn.

Otherwise, I don't have a one specific reference, 'cept Google.

the most resourceful one I

WebsitesNetwork — Wed, 27 Feb 2008 20:22:24 +0000

the most resourceful one I use is TOP