similar to: man pages screwed

I've noticed that the man pages provided in the tarball do not work on Solaris - the output is not formatted as expected. On a linux box it is possible to view the man pages using nroff -mdoc ./sshd.8, where prepended file is /usr/lib/groff/tmac/tmac.doc. There does not appear to be an equivelent macro file on Solaris 2.6. Does anybody know how I can get the man pages to display properly on

Hi The man pages don't format properly on Tru64 unix for portable openssh. They come out as a solid lump of text. I managed to fix the problem by including the line .so /usr/local/share/groff/tmac/tmac.andoc (I have GNU groff installed) In the man pages. It appears the OSF -man option on nroff doesn't format the pages correctly. Thanks Jeremy -- Jeremy Sanders <jss at

On Thu, 3 May 2001, Gus Mancuso wrote: I haven't seen the answer to this question (included way below) yet. I'm installing it on Solaris 8 and have the same problem - I can't read the man pages in any format other than 80 column wrapped text. The Solaris 8 is pretty generic, with all the current patches. OpenSSH version is 2.9p1. The man pages stored in /usr/local/man/manx are

On Thu, 3 May 2001, Gus Mancuso wrote: > Hello OpenSSH developers > > First, many thanks for producing this app! > > I've noticed that the man pages for openssh don't look > at all like man pages. My somewhat limited > troubleshooting skills point towards a problem with > nroff not expanding the macros embedded in the man > files. > When I `man sshd`, I get

Hi, Just tested the latest snapshot on RHL72 via building RPM's of it. Nroff detection was wrong, and if no --with-mantype was specified, the type would always revert to cat. This one-byter fixes it. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert

Hi, On systems that have mandoc installed but are missing an nroff binary, the configure script will fall back to pre-formatted manual pages despite the fact that mandoc could be used. The proposed patch adds mandoc as a valid formatter to configure.ac. As mandoc supports the -mdoc flag, it can simply be added to the list of nroff-like binaries. Wolfgang -------------- next part --------------

Hi Team, I'm looking to "upgrade" my sites ssh installation from the original. I have built openssh-2.3.0p1 and it looks good. I am puzzled as to why there are so many source distributions? However, that is not why am writing - the man pages provided do not format with either Solaris 'nroff -man' or 'groff -man'. What am I missing here? Thanks for your help. Scott

Guus The mdoc warnings (on FreeBSD 8) are getting a little bit annoying at times: anywi at lcrproxy:/usr/ports/security/tinc/work/tinc-1.0.19/doc % man tinc.conf 2>&1 | head -5 mdoc warning: Empty input line #6 mdoc warning: Empty input line #10 mdoc warning: Empty input line #15 mdoc warning: Empty input line #22 mdoc warning: Empty input line #30 There are hundreds. Ctrl-L refreshes

Hi, Is there an easy way to "fix" the man pages to work with Solaris. Solaris uses the "an" ie /usr/share/lib/tmac/an nroff macros and I guess openbsd doesnt!! cheers Jim

Hi, I am sorry about this stupid question but after compilation of openssh-2.3.0p1 the manpages were installed but a man ssh gives only unstructured response without underlined lines etc. A nroff -man sshd.8 gives the same output but the contents of the file shows a nroff-format. Any ideas? My system is a HP-UX 11.000 with the pam-patch. regards Stephan -- LDS Brandenburg Dr. Stephan Hendl

Hi all. I can't read the openssh man pages on Solaris. I tried all the nroff macro packages I could find, with more or less garbled success. Could someone point me to versions suitable for Solaris, or a man2sgml converter? Or to a good online tutorial covering this issue (SysV vs. BSD?) that would allow me to translate the nroff dialects involved? In the latter case, I would of course

HPUX doesn't seem to ship with a set of troff macros that can handle the OpenSSH manpages. Maybe other OSs have this problem? Rather than sodding about with the tmac/ directory, I think we should do one of two things: 1. Ship a set of preformatted manpages, and either auto-install them in $prefix/man/cat{1,1m} or just have instructions in INSTALL to do so 2. Recommend users install groff

Hi all. I just got openssh 2.5.1p1 and when I installed it, it's man pages doesn't seem to be formatted right. I'm on Solaris 8. Here is how it looks: man ssh Reformatting page. Please Wait... done (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine. It is intended to replace rlogin and rsh, and provide secure encrypted

On 2016-09-28 00:10, Ingo Schwarze wrote: > The patch also inserts a few needless .PP before .SH, but that does > no harm. mdoc2man.awk is a terrible hack and not a proper parser > in the first place, so we shouldn't expect beauty in its output. > If the output is correct and portable, that's good enough. At some > point, we should replace mdoc2man.awk with mandoc -Tman

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 xtrans is a library of code that is shared (but is *not* a shared library) among various X packages to handle network protocol transport in a modular fashion, allowing a single place to add new transport types. It is used by the X server, libX11, libICE, the X font server, and related components. This minor release converts the libxtrans API

I have been trying to build the latest 4.8 Stable on a 4.8 Stable system mainly go get the latest fixes, but on "make buildworld" I keep getting the same problem for the past few days. I've even completely removed /usr/src and /usr/obj (ok I backed it up) and re-cvsuped the code and started a-new. I attached the complete "make buildworld" from after that. Anyone have

On a plain vanilla Solaris 8 install, the man page source WILL NOT generate readable manpages. It just ends up as one big paragraph. I've been using the cat pages as a workaround, but it would be nice if the man pages would format with nroff -man --jeh Asst. Systems Administrator Research Computing Systems UW Electrical Engineering

Right out of the box (after I made Damien's LDFLAGS fix in configure) using gcc-2.95.2. The only problem I have now is the man pages. I still can't read them using Solaris nroff, and when I tried to build with --with-catman=cat, I got the following during a make install: /rtr/bin/install -c -m 644 ssh.[01].out /usr/local/man/cat1/ssh.1 Try `/rtr/bin/install --help' for more

Why would this be happening, and how can I fix this - the man subsystem hasn't been working because of this for a while. This is FreeBSD-4.9-Prerelease: # gdb man man GNU gdb 4.18 (FreeBSD) This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... /usr/share/tmac/man: No such file or directory. And when I go to run a manpage, I sometimes get this

Greetings in Christ our Saviour. I am having an enormous amount of difficulties trying to do something that should be quite easy. Obviously, I am missing something. I have read everything I can find on this, and have tried everything I can think of and more... I am trying to mount a Win98 drive on my Redhat 7.0 box. The mounting is no problem. However, when I log into my user account and try