commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
Discovering all executables on your system that can be run as another user, especially root, is critical for system security. The above command will find those files with have SUID or SGID bits set and are owned by the root user or group.
There are 7 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
It doesn't run on a Red Hat Linux release 7.3 (Valhalla) with the error:
find: invalid mode `/4000'
RHL 7.3... released May of 2002... 7 years ago. I think it's time to update your system, don't you? However, if you read the man page on find, you'll see that /mode is the preferred way over +mode, but both are identical, even if +mode is deprecated.
Some companies can't or don't want to upgrade the distro that their software is based on.
Of course. That's why the cracker community flourishes as well as it does. They expect people to not keep updated on patching or upgrading their systems. The more systems that sit unpatched, the more reason for your suffering.
I'm not defending the practice ;) I just happen to work for a company whose product is based on a 7-8 old linux distro release. Although, we've updated and repackaged so many of the packages and rewritten many config scripts that, at this point, it is pretty much our own distro.
@atoponce: not every machine is connected to the evil internet, so often there is no need to upgrade the boxens every week...