similar to: [PATCH] configure.ac: Add mandoc as valid formatter

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

Version info: OpenSSH_7.3p1, OpenSSL 1.0.2i 22 Sep 2016, Arch linux The ssh-agent.1 man page seems to have an indentation oddity, at least, as formatted with recent Arch linux manpage toolset. Here's what appears in the formatted output just after the description of the the "-t" option: ---------- Begin formatted output ------------------------------------- -t life

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

Dear authors of Opus, currently, the manpages that come with opus-tools 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 the

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

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:

Hello, the man pages for openssh-2.3.0p1 look bad on our Tru64 Unix V4.0E systems. (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 communica- tions between two untrusted hosts over an insecure network. X11 connections and arbitrary TCP/IP ports can also be

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

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

The attached patch (relative to the current CVS snapshot) uses a perl script to convert the OpenSSH manpages from the BSD -mdoc format to the -man format used by other systems. This allows the unformatted manpages to be installed normally, rather than defaulting to preformatted pages. I'd like to see this patch integrated into the portable version of OpenSSH. Please let me know what you

http://bugzilla.mindrot.org/show_bug.cgi?id=1202 Summary: Missing instructions for building from CVS Product: Portable OpenSSH Version: 4.3p2 Platform: Other URL: http://openssh.org/portable.html OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Documentation

We use rsync to update an nfs server. After an update, we noticed that a large number of clients didn't see the updated data. It took me a while to be able to reliably reproduce this problem, but it happens on old and new versions of rysnc. It also happens across all the platforms we use here (sun/linux/netapp). This shows the problem: [Note my home directory is NFS mounted]

https://bugzilla.mindrot.org/show_bug.cgi?id=2517 Bug ID: 2517 Summary: GitHub version doesn't include ChangeLog Product: Portable OpenSSH Version: 6.8p1 Hardware: 68k OS: Mac OS X Status: NEW Severity: enhancement Priority: P5 Component: Documentation Assignee:

I have attached two patches to the current source code. The first addresses the pty problems with UnixWare 2.x with connecting with SSH2. It sets the sigaction to SA_RESTART. This fixes UnixWare v2.x, but haven't heard any feedback as to effects on other OS'. The first patch is against misc.c. The second patch adds a section "*-*-sysv4.2uw2*" to configure to set the

I was hoping that someone could try to reproduce an error that I am getting. The R Site Search keeps timing out on me, so apologies of this has already come up. I'm using > R.version _ platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32

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

I'm not sure what LLVM_ENABLE_THREADS impacts - whether it is LLVM executables themselves or LLVM-generated code - but it seems to be on by default on the Windows CMake build (I'm building LLVM+Clang at trunk head using CMake/Visual Studio 2013 Win64). But 3 unit tests in IR, which are compiled only if define LLVM_ENABLE_THREADS is set, fail if LLVM_ENABLE_THEADS=ON:

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: