How do I print Man pages?
Regards
anindyanuri

Well... I usually just send them to a file first...

man ls > lsmanpage.txt

I guess you could send it to your printer like this:

man ls > /dev/lp0

but that may not work on some printers unless you have an old DM printer.

KC

I used the same option u have given in your first example but got a bad formatting of the .txt file.

I used man fstab > mfstab.txt and the output is as follows :

FSTAB(5) Linux Programmer’s Manual FSTAB(5)



NNAAMMEE
fstab - static information about the filesystems

SSYYNNOOPPSSIISS
##iinncclluuddee <<ffssttaabb..hh>>

DDEESSCCRRIIPPTTIIOONN
The file ffssttaabb contains descriptive information about the various file
systems. ffssttaabb is only read by programs, and not written; it is the
duty of the system administrator to properly create and maintain this
file. Each filesystem is described on a separate line; fields on each
line are separated by tabs or spaces. Lines starting with ’#’ are com-
ments. The order of records in ffssttaabb is important because ffsscckk(8),
mmoouunntt(8), and uummoouunntt(8) sequentially iterate through ffssttaabb doing their
thing.

Now please guide me, how to proceed....

Regards
anindyanuri

hmm, this sounds oddly like a class assignment i had...

Try this in root:

man fstab | col -b > fstab.txt

KC

Yes, the problem has gone but not completely. MAN page includes a lot of single quote marks. In case of single quotes, there is still garbage letters.

Original fstab man page says...
For ordinary mounts it will hold (a link to) a block special device
node (as created by mknod(8)) for the device to be mounted, like
‘/dev/cdrom’ or ‘/dev/sdb7’. For NFS mounts one will have
<host>:<dir>, e.g., ‘knuth.aeb.nl:/’. For procfs, use ‘proc’.

Now the formatted output in the .txt file...
For ordinary mounts it will hold (a link to) a block special device
node (as created by mknod(8)) for the device to be mounted, like
‘/dev/cdrom’ or ‘/dev/sdb7’. For NFS mounts one will have
<host>:<dir>, e.g., ‘knuth.aeb.nl:/’. For procfs, use ‘proc’.


How to get rid off?

Regards
anindyanuri

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.

===============================

To convert output to PDF format

man -t tar | ps2pdf > tar.pdf

===============================

I've tried info2html and didn't like the result.

What I do is use
man -Tdvi <topic> >topic.dvi
or
man -Tps <topic> >topic.ps
and print the .dvi or .ps file from ghostview.

Some distros don't have the -T option for man, but you can use -t instead.
man -t man >man.ps
kghostview man.ps

I just used a similar method with the tex info pages for coreutils and bashref.

I needed to install the source package (rpm based)
Then I CDed to the SPECS directory and ran:
rpmbuild -bp bash.spec # This applies patches which might contain corrections
rpmbuild -bs bash.spec # This builds a new source package

Then in Midnight commander I opened the .src.rpm file created and copied the DOC directory to a working directory. After CDing to the DOC directory, I ran 'tex bashref.texi' to create a print worthy document 'bashref.dvi'.