GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
First, this is meant to be a serious thread. Not complaining or a flame war. I thought it might be useful to tell how I help with answering questions. It may help others better answer questions and hopefully others will post on the methods they employ and we can all learn.
Sometimes, just sometimes, I know the answer off the top of my head and can send off the reply quickly. Most of the time not. There are several things I do and tools I've developed to get answers.
1. Google. For example, if someone has an error message, I either search for the whole error or part of it. I try different phrases. Most of the time you can find something relevant. (I find more and more that google's findings are for LinuxQuestions.org )
2. Use the search feature here on LQ.
3. Read the manuals. Especially the Red Hat ones. They're the best.
Might help you it might not...
I've made a help file that I put all the things that I probably can't remember off the top of my head but I might use in the future. Say I can't remember the syntax for a command I can grep the file for the command. Then I made an alias so I just have to type 411 string_I'm_looking_for and it greps the file for the string.
example:
I used to have a file system fill up all the time so I wanted to find the large files but couldn't remember the option with find that would specify size.
# 411 find
output:
Find large files --> find . -size +1000 -exec ls -l {} \;
Find large files --> find . -size +1000 -exec ls -l {} \; | sort -k 5n
Distribution: Mac OS 10.7 / CentOS 6(servers) / xubuntu 13.04
Posts: 1,186
Rep:
I have to admit that I hate user manuals.. I mean I would rather not look over a user manual when I can ask a quick question on here and get a quick response.. Plus the only manual I own is so damn out of date its usless.. I run RH9 and it is for RH 5.1
Originally posted by Freakygeek55 Maybe I should download one of those and burn it to a CD...
Most of the time during a default install of Redhat, those are installed already on your system.
Also just about every Linux system comes installed with the man pages, built in manual pages for all commands...
Just type man command
So its no excuse for anyone to try that first and read over the man page before asking a question here and waiting for a response, when they could have already had an answer waiting for them in the man page...
Distribution: Mac OS 10.7 / CentOS 6(servers) / xubuntu 13.04
Posts: 1,186
Rep:
Maybe I will try that next before asking a question here.. yet like I said I would rather be told right off hand the answer to a question then trying to interpret what a manual says..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.