A How to Question which illustrates the worst impediment to Linux
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This does suggest a problem though... you can read all the way through the man pages for apt-get, and not figure out how to do the type of search that he's asking for, because the it's not in the apt-get man pages, it's in the apt-cache man pages... that's not what I would call discoverable, which is supposed to be one of the benefits of well written command line software.
I really would expect this functionality to be obvious from apt-get --help.
Mon, am I the only one to read tutorials in context or do I just have good short term memory? Just one sentence above the tut talks about
You use the apt-get command to install and remove software packages from your system (one at a time or many at once), as well as update your system's internal listing of what packages are available from your currently selected list or repositories.
It's just a package and if you know or not that debian uses .deb it's just a package.
Let the dogs run wild
(To be honest to gather good tutorials or knowledge on it own is a skill! But thats what schools are for. To believe and not learn )
Now could someone please forgive me for this rant and direct me to a good source that does not leave out important information for newbies and isn't written in incomprehensible jargon that it hasn't defined.
I am willing to pay for it.
I haven't read through this entire thread (so I may be echoing advice), but it sounds like you could benefit from some hands-on professional instruction. That will give you an opportunity to tinker, ask lots of questions, and get quality direction from an expert, in person.
Once you have a basic foundation, you'll likely find your books to be more readable and useful.
Check your local college / community college for offerings. If that doesn't yield results, see if you can get in touch with a nearby LUG (Linux User Group). They may have tips for you, and you might even like to attend their meetings.
This thread prompted me to contact the Linux Documentation Project about writing the document "HOWTO Write Documentation for Linux." There are numerous documents "HOWTO ... Program ... Linux". Also, there are several templates, submission guidelines, and review processes for documents. However, there is little guidance for someone who wants to contribute documentation.
Let me over simplify to present an example. Consider writing a new or improved man-page for some package. A small effort provides you with all of the parts needed to create man-page formatted documents. You sit down to write. Where do you get the facts that you need? Given some details, it is straight forward to put sentences onto [e-]paper, but where do these details come from?
There are thousands of programmer, sysadmin and netadmin folks who move Linux forward every day. This is my plea for technical writers out there to step up to coach and mentor and even contribute to this community.
Three pages of replies, and where is the OP? Does this suggest anything to you?
Well if by OP, you mean original poster, I am still here. I have been reading the various posts, some have echoed my concern, some have addressed possible solutions, but so far there is not a solution to the problem, other than perhaps the notion that there needs to be a "user's guide" But I still have not found such an book. I am still plugging away at trying to assemble a critical mass of user knowledge to be able to read man pages and the like, but I am still early on the learning curve. The suggestion that perhaps I should obtain professional linux instruction had merit but alas I have found no practical source of such instruction.
I have quoted the above post because it is written in jargon. Lets see, the the quoted post consists of, 79 key strokes, to have typed "original poster" instead of "OP" would have required but 16 additional keystrokes, then we could all be sure what the poster intended. It would have been a statement in "plain english" not jargon. So once again I am left with a bit of doubt about what one simple sentence means, Now go to a "man page" and see how every other sentence does the same thing, Pretty soon you have no idea of what it is saying.
Then there is the matter of the second sentence of the quoted post, which asks what the lack of the presence of the OP suggests. The answer is that it suggests NOTHING !
My point is that the linux community condemns itself to obscurity unless and until, it recognizes the crucial need to propagate itself by the nurturing of new users. The near religious zeal of the Linux community has failed to develop an effective scheme for proselytizing. In the realm of religion, there is a translation of the Bible called the BBE, that is theological jargon for the Bible in Basic English. The translation project was developed on the premise that the entire Bible could be translated by using just 1000 different words that constitute basic English language literacy, so that people who don't yet speak the language of theologians could understand what the Bible says. What is needed is for someone to write the LBE, Linux in Basic English (and of course other languages as well). And it should include a thorough index and definition of terms and be limited to establishing basic use of linux and features such as "man" and "info" pages.
My original post was written to address the issue of the propagation of basic linux literacy and not solve the problem of using aptget for a particular installation issue.
My suggestion to the OP [yes, original poster] is it is time you get involved - go log in at The Linux Documentation Project, join a LUG (Linux User Group) or write that book for O'Reilly to publish that finally and purposefully exposes what "NameOfPackage" means. If you want to see Linux not "condemn itself to obscurity" - then you have to get involved and help out. This post started years ago - you have years of experiance to give back so some newbie who wants to know what "NameOfPackage" means.
Thats how Linux gets better. It's all up to us Dgoddard.