Date: Mon, 1 May 2000 06:43:02 -0700 (PDT) From: tmessmer@scilearn.com To: freebsd-gnats-submit@FreeBSD.org Subject: ports/18324: pipsecd contains practically no documentation. Message-ID: <200005011343.GAA30359@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 18324 >Category: ports >Synopsis: pipsecd contains practically no documentation. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon May 1 06:50:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Tom Messmer >Release: 4.0 >Organization: Scientific Learning Corp >Environment: n/a >Description: The pipsecd port contains very terse, somewhat incomprehensible documentation. I need to set up an ipsec tunnel and i could use a bit more info here. I have seen some discussion on mailing lists of other people with similar issues with the port. It would be great if something could be put together for this. >How-To-Repeat: more /usr/ports/net/pipsecd/work/pipsec-19991014/README >Fix: Expand the readme, make a man page. I'd be willing to work on this if I ever figure out how to get the damn thing working... >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005011343.GAA30359>