Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
When I want to print out documentation, I usually find myself going to the package's website and hoping there is a nice HTML or PDF file out there I can print, but when worst comes to worse I find myself copying and pasting from the info file into a text editor and printing it out
One option is to install the source package. This will give you access to the topic.tex source.
For example:
rpm -Uhv core-utils-<version>.src.rpm
cd /usr/src/packages/SPECS # The "packages" part may be different on your system.
rpmbuild -bp core-utils.spec # This may apply patches to the document sources
cd ../BUILD
cd core-utils-<version>/
./configure
# There may by targets to produce the documentation such as
make dvi
or
make ps
or make pdf
As a last resort, cd to the "doc" subdirectory, and if a core-utils.tex file exists:
tex core-utils.tex
This will produce a .dvi file which you can print out from kdvi or xdvi, or you could use dvips to convert it to postscript.
This may seem like a lot of work, but will become routine after a few times. The documents produced look very good. Also, many of the documents you will discover this way are lengthy manuals. The bashref, and core-utils manual s are long enough to fill a 3 ring binder. Having them nicely typeset makes using them easier.
Also consider printing out man pages this way:
man -t <topic> | lp -d <printername>
You might want to preview an example this way:
man -t tar | gv -scale 2 -antialias -media letter -
To print man pages:
In this example, using tar man pages.
man -t tar | lpr -Pdraft
Print man pages for tar (will be formatted by troff or groff,
usually for PostScript)
Pipe to lpr
Send to printer <draft> [optional]. The command will
print to the default printer if given as:
man -t tar | lpr
===============================
To print info pages:
In this example, using tar info pages.
cp /usr/share/info/tar.info.gz /home/<user>
Copy the info page to another location to avoid breaking
your on-line documentation.
gunzip /home/<user>/tar.info.gz
After decompressing the file, use a2ps to convert to PostScript.
a2ps tar.info
This produces a PostScript formatted file called tar.info.
Open in your favorite editor and print from there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.