LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > LinuxQuestions.org > LQ Suggestions & Feedback
User Name
Password
LQ Suggestions & Feedback Do you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.

Notices

Reply
 
Search this Thread
Old 05-01-2013, 02:05 AM   #1
trevoratxtal
Member
 
Registered: Dec 2012
Location: South Devon, UK
Distribution: PCLinuxOS, Suse, Mint, Puppy.
Posts: 36

Rep: Reputation: 3
Tips to increase chance of your question being answered.


Do not use abbreviations, use the full word or words in the title and at least once in the main entry.
Search engines do not respond well to abbreviations, try a search for VB so often used for" Virtual Box " the results are no use.
Abbreviations often apply only to one country so are meaningless in others country's.
LQ like many forums is international.
Try a search for DHS, The Security network in the USA, Hospitals in the UK, and even Dead Hackers Society.
If you wish for an answer add the full words and spell correctly.
If English is not your first language or like me dyslexic add a spell checker to your browser or Goggle the word to check.
I hope this helps.
Trev
 
Old 05-01-2013, 09:49 AM   #2
TenTenths
Senior Member
 
Registered: Aug 2011
Location: Dublin
Distribution: Centos 5 / 6
Posts: 1,529

Rep: Reputation: 472Reputation: 472Reputation: 472Reputation: 472Reputation: 472
Include your linux distribution in the question.
If you're following a How-To and get stuck then include a link to the How-To.
Detail what you've already tried.
Give your thread a MEANINGFUL title "HELP!" is NOT a meaningful title. "URGENT" isn't either, it may be urgent for you, but it's not urgent for us!
Don't "hate", be open to the suggestion that sometimes (shockingly!) linux is not necessarily the best O/S for the job.
If you're using RedHat then call RedHat support, that's what you're paying for!
Detail what you've already tried. (Yes, I've said it twice, it's THAT important)
"Help me make proxy give me all instructions." - No, we'll try and help with specific squid problems once you come across them.

Last edited by TenTenths; 05-01-2013 at 09:51 AM.
 
1 members found this post helpful.
Old 05-01-2013, 04:01 PM   #3
John VV
Guru
 
Registered: Aug 2005
Posts: 13,057

Rep: Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741
And if this is a virtual install make 100% sure that is in the FIRST post !

so that by the 8 post we do not just then find out about that VERY important bit of information
 
1 members found this post helpful.
Old 05-01-2013, 09:15 PM   #4
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Mageia, Mint
Posts: 7,932

Rep: Reputation: 1495Reputation: 1495Reputation: 1495Reputation: 1495Reputation: 1495Reputation: 1495Reputation: 1495Reputation: 1495Reputation: 1495Reputation: 1495
If it's hardware-related question, include the make/model of the hardware, whether it's a printer, router, network device, webcam, computer, external HDD, etc.
 
1 members found this post helpful.
Old 05-05-2013, 08:49 AM   #5
David the H.
Bash Guru
 
Registered: Jun 2004
Location: Osaka, Japan
Distribution: Debian sid + kde 3.5 & 4.4
Posts: 6,823

Rep: Reputation: 1949Reputation: 1949Reputation: 1949Reputation: 1949Reputation: 1949Reputation: 1949Reputation: 1949Reputation: 1949Reputation: 1949Reputation: 1949Reputation: 1949
For scripting/coding questions, start by explaining clearly what you want to accomplish, rather than just posting the non-working code. Give some background context for the request as well.

Be sure to include representative examples of both the input and the desired output. This can include examples of the file/directory tree and even the output of common commands, since not everyone will have access to the same commands and set-up you do.

Be sure to explain clearly what parts of that input need to be included in the output and what needs to be excluded, and how to tell the difference between them. Often there are many ways to create the exact output example in the posted request, and only some of them may be applicable the user's actual needs.

Clearly specify the environment you're working in, if you aren't using a standard GNU/Linux system. We need to know what tools are available to you and what aren't. If the code you post depends on variables or commands that are defined elsewhere, be sure to post what they contain as well.

When you execute a command and it doesn't work, don't just say it failed, post the actual command(s) you used and whatever output/errors you got. Remember, we can't see your screen.

However, don't post 10 pages of nearly-identical error messages either. We don't need walls of text. Just supply a short example of what you have.


In short, don't assume that readers will recognize what your code is doing just from the bit you post. Do whatever you can to ensure that others understand what it's supposed to be doing, and can directly replicate it themselves in testing.

Last edited by David the H.; 05-05-2013 at 08:59 AM.
 
2 members found this post helpful.
Old 05-13-2013, 05:59 AM   #6
goumba
Member
 
Registered: Dec 2009
Location: New Jersey, USA
Distribution: Debian Wheezy (7.0), Jessie (future 8) and Sid (unstable)
Posts: 551
Blog Entries: 3

Rep: Reputation: 66
Quote:
Originally Posted by frankbell View Post
If it's hardware-related question, include the make/model of the hardware, whether it's a printer, router, network device, webcam, computer, external HDD, etc.
If possible, when you're not sure of the specifics, include any relevant output from the lspci command.
 
Old 05-13-2013, 06:18 AM   #7
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,569
Blog Entries: 1

Rep: Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026
Quote:
For scripting/coding questions, start by explaining clearly what you want to accomplish, rather than just posting the non-working code. Give some background context for the request as well.

Be sure to include representative examples of both the input and the desired output. This can include examples of the file/directory tree and even the output of common commands, since not everyone will have access to the same commands and set-up you do.
+100
 
Old 05-13-2013, 07:47 AM   #8
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
One thing I would add is: try to provide relevant information and exclude non-relevant information. I've seen a number of posts that are walls of text, much of which is irrelevant to the problem. If I have limited time and a choice between reading through a wall of text or reading a shorter, more concise, more to the point question ...

Certainly providing more information is good, but it's much more important to provide it in a way that can be easily interpreted. Make sure to use [code tags for sure, because posting a wall of code is even worse than a wall of text.
 
Old 05-13-2013, 08:34 AM   #9
goumba
Member
 
Registered: Dec 2009
Location: New Jersey, USA
Distribution: Debian Wheezy (7.0), Jessie (future 8) and Sid (unstable)
Posts: 551
Blog Entries: 3

Rep: Reputation: 66
Quote:
Originally Posted by H_TeXMeX_H View Post
One thing I would add is: try to provide relevant information and exclude non-relevant information.
I don't know if this is doable or practical, but maybe a sticky with a short synopsis of to get relevant information with a few common cases? New users aren't likely to know where to look at lspci output for certain things, dmesg, etc, and often the first reply is asking for the output of related commands.
 
Old 05-13-2013, 08:58 AM   #10
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Quote:
Originally Posted by goumba View Post
I don't know if this is doable or practical, but maybe a sticky with a short synopsis of to get relevant information with a few common cases? New users aren't likely to know where to look at lspci output for certain things, dmesg, etc, and often the first reply is asking for the output of related commands.
Output of commands is fine, you can put them, but don't tell a long story with unrelated information. I'm not relying on people knowing technical things that are not relevant, but rather practical things that are not relevant. Stay on topic, stay relevant to the question at hand.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Need a simple question answered Trouble31 Linux - Newbie 8 09-12-2011 07:43 PM
[ Answered ] Question about TSIG Dig Linux - Server 4 05-05-2010 02:41 PM
noob question i need answered cooldudejz Ubuntu 4 09-21-2005 07:44 PM
Dare you answer the question, that cannot be answered! Ephemeral Linux - Wireless Networking 8 08-29-2004 06:16 PM
NEWBIE!!! needs question answered microsoft/linux Slackware 15 05-13-2004 08:57 PM


All times are GMT -5. The time now is 08:42 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration