similar to: bug, (or stupid user) report: man page garbled under Sol7

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

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 --------------

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

AIX v4.3 returns the correct error $ /usr/bin/nroff -mdoc a /usr/bin/nroff: 1004-010 Cannot find or open /usr/lib/tmac/tmac.doc $ echo $? 130 $ EdGy

I need some help with .Configure for OpenSSL. I compiled versions for all Solaris (2.5, 2.6, 2.8) platforms, but I am having problems with the SUN sparc Ultra-60 (220-r) running Solaris 7 SUN4U configuration. I am trying to configure OpenSSL 0.9.6.C and have GCC version 2.95.3 for Solaris 7. When executing ./config , I received the following errors: Operating system: sun4u-whatever-solaris2

Something strange happens when I compile the pre27 SSH: ocal/ssh//include -DETCDIR=\"/usr/local/ssh//etc\" \ -DSSH_PROGRAM=\"/usr/local/ssh//bin/ssh\" \ -DSSH_ASKPASS_DEFAULT=\"/usr/local/ssh//libexec/ssh/ssh-askpass\" \ -DHAVE_CONFIG_H -c atomicio.c In file included from includes.h:106, from atomicio.c:26: fake-socket.h:30: parse error before

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 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

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

Dear authors of Vorbis, currently, the manpages that come with vorbistools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on

Jan Stary <hans at stare.cz> wrote: > On Jan 01 00:05:09, jamie at catflap.org wrote: > > Jan Stary via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote: > > > > > On Dec 31 11:43:56, paul at nohats.ca wrote: > > > > Why not go to xml and use xml2man / pandoc ? > > > > > > Because it is a terrible manpage format > > >

On Jan 01 00:05:09, jamie at catflap.org wrote: > Jan Stary via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote: > > > On Dec 31 11:43:56, paul at nohats.ca wrote: > > > Why not go to xml and use xml2man / pandoc ? > > > > Because it is a terrible manpage format > > and the toolchain produces broken crap. > > I have no specific knowledge on

Dear authors of NSD, currently, the manpages that come with NSD are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. See a version of nsd-checkzone.8 below as an example. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters:

ping On Jun 23 09:05:38, hans at stare.cz wrote: > Dear authors of vorbis-tools, > > the manpages are currently writen using the man(7) markup language. > Would there be any interest in having them rewritten to mdoc(7)? > > The mdoc(7) language allows for _semantic_ markup, expressing > things like "this is an optional argument", as opposed to the physical >

Estimados compañeros me tiene loco un problema de codificación que no logro resolver. Importo un fichero cuyo nombre tiene acento. Pongamos por ejemplo "Adrián.doc". Escribo el siguiente comando: mdoc<-list.files(path = dest,pattern = "*.doc", full.names = TRUE) Entonces mdoc, además del path, se me presenta como: "Adria´n.doc" Aunque le quite la tilde con:

Hi, Here's a problem in openssh, some logs, and a very minor patch that cures this: Issue: (open)ssh client WILL NOT talk to F secure SSH-2.0-2.1.0pl2 client S/W version: openssh-2.3.0p1 client O/S version: SunOS 5.7 Generic_106541-11 sun4u sparc server S/W version: SSH-2.0-2.1.0pl2 server O/S version: SunOS 5.7 Generic_106541-11 sun4u sparc Log/Details: : % telnet <mymachine> 22

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

FreeBSD Quarterly Status Report, January-March 2013 Introduction This report covers FreeBSD-related projects between January and March 2013. This is the first of four reports planned for 2013. Highlights from this status report include the busy preparations of 8.4-RELEASE, restoration of binary package building, steady progress of several porting efforts, like work on the FreeBSD

I am using R 1.2.3 on Linux Mandrake 7.2. I have a ton of S Nroff help files that end with source code typified by the following: Last S statement in an example, e.g. X <- y ..KW models ..KW regression ..WR When using R RMD Sd2Rd to create the .Rd file I get X <- y \keyword{models} \keyword{regression} } The } matches a { in \examples{ at the beginning of the example code (started in