LQ Suggestions & FeedbackDo 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
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.
I think it would benefit the contributors of LQ,. to have a static LQ pastebin, along with a maintained 'getinfo' script that would automatically grab details that we ask for in NEARLY EVERY SINGLE POST.
Have the user run the script. Paste results to pastebin. Make a thread, and reference the pastebin.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
We've actually discussed some kind of getinfo/machine inventory functionality internally in the past. After the next code update it's likely something we should revisit. I'm interested in what other members think in the mean time. Thanks for the feedback.
While I completely understand trying to circumvent the game of twenty questions that often needs to be played to answer an initial question, I can see pitfalls with trying to develop a single 'getinfo' script.
1. The script would need to be a run on the machine with problems. So what happens in situations like:
My machine cannot/hangs on boot, my internet connection is not working, my display is not working...
2. Exactly what information would be collected? Simple things like 'uname -a', 'cat /etc/os-release', 'lspci' are relatively compact, but if you start to look at things like sound configuration, 'lsmod', Xorg logs then you can run to pages of output. The more information that is collected then the more material that would need to gone through to find a small crucial detail.
Rather than a single script, perhaps have a page that contains instructions on collecting output that should be posted/paste binned when seeking help on a specific topic. When a new question was posted, then the OP could be referred to such a page with a request to follow the suggestions for that topic.
a series of 10 commands can usually lead to the answer. common troubleshooting and such.
Its a tool. Not an end-all solution. It will have applications where it will be helpful,.. as with a philips screwdriver,.. but it will not work in other cases, such as fighting a bear with a philips screwdriver.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.