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.
I guess we need a stable revamp of the man pages. Man pages are yes full of information, but they are often hard to understand, even intermediate users like me take a bit of time to read everything.
We need stuff like: common problems. More examples, more bolding, more sorting, colour, diagrams!
So I want an ncurses based man, that will read files that code for colour and such and interpret them as so....
Is there something like this already, or is it open for development?
Take man cdrecord for example. They tell you about SCSI, DAO, real write, dummy mode, devices, sectors, but its hard to construct a big picture without re-reading over and over again. And googling. Then after rereading, I find SCSI protocol doesn't really have to be used for cdrecord - it was kernel based. Ide can be used in 2.6.x. Yes, I missed the big picture. Thanks to misleading man pages.
LINKS to other man pages for explanations we need, and a more convenient and compact form than online HOWTOs (ie. what about if you're fixing something and network isn't working properly?). Explain each option and give examples for it. This is good for newbies who don't have time to cross-reference everything.
Distribution: RedHat 9.0 / Slackware 9.0/ FreeBSD 4.8 / Solaris 8 x86 / Mandrake 9.0
Good on you, tell me when your done with this man page project, I mean it's all GPL so go right ahead... On an aside, man pages weren't designed for easy use or diagrams. With konqueor you can get fairly good manpages but I think you will not in the near future get diagrams:
#man #bob's your uncle you have the manpage for man
it also seems that it accesses man pages like this:
man:/man #manpage for man
Man pages are generally less designed to teach you how to use something (though they can, and often have, to work that way) and more designed for 'Was that an upper case or lower case F?'. Reference/reminders for people who already know what they're doing. And it's great to just type 'man command', hit a slash, type in a search, and go. But I do agree that users sometimes need something else to start with. It's not a local help system like you're talking about, but there is an effort to create readable, user-friendly, current documentation: