From owner-freebsd-questions@FreeBSD.ORG Fri Jul 14 05:55:29 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1350816A4DF for ; Fri, 14 Jul 2006 05:55:29 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (ns0.infracaninophile.co.uk [81.187.76.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C582143D73 for ; Fri, 14 Jul 2006 05:55:18 +0000 (GMT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from [IPv6:::1] (localhost [IPv6:::1]) by smtp.infracaninophile.co.uk (8.13.6/8.13.6) with ESMTP id k6E5srTI043989 for ; Fri, 14 Jul 2006 06:54:53 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Authentication-Results: smtp.infracaninophile.co.uk from=m.seaman@infracaninophile.co.uk; sender-id=softfail; spf=softfail Message-ID: <44B731A7.70603@infracaninophile.co.uk> Date: Fri, 14 Jul 2006 06:54:47 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Thunderbird 1.5.0.4 (X11/20060610) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20060714014823.c4d0b759.nick@nickwithers.com> <000f01c6a6ba$6d1d4340$0a10a8c0@holgerdanske.local> <20060714003829.GA27743@brokedownpalace> In-Reply-To: <20060714003829.GA27743@brokedownpalace> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig5DD2A3A0591EFFCC152A1BB8" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (smtp.infracaninophile.co.uk [IPv6:::1]); Fri, 14 Jul 2006 06:54:53 +0100 (BST) X-Virus-Scanned: ClamAV 0.88.3/1598/Thu Jul 13 12:38:16 2006 on happy-idiot-talk.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on happy-idiot-talk.infracaninophile.co.uk Subject: Re: 6.1-RELEASE-i386 man broken? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 05:55:29 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5DD2A3A0591EFFCC152A1BB8 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable J wrote: > On 2006-07-13 (Thu) 13:25:04 [+0000], David Christensen wrote: >> Matthew Seaman wrote: >>> Please read what I wrote more carefully. To summarize: don't set >>> $MANPATH in your environment, and the man(1) command will work >>> correctly. >> Now I understand: >> >>> The environment variable MANPATH should in general not be set, as >>> that will override the effects of /etc/manpath.config. >=20 > I ran into and had to solve this problem myself when first coming to > FreeBSD, recently, as my transported Linux bash configs contained > MANPATH=3D$MANPATH:/custom/manpath. What I never figured out was the > rationale for this. Anyone mind me asking what's wrong with MANPATH or > why manpath.config is exclusively favored? For instance, while I have a= > /usr/lib/man.conf on my Linux system and can set the default manpath > there, man happily coexists with any MANPATH. How does one add a custom= > manpath without root privileges? Etc. Just curious; thanks. The manpath(1) program is designed to provide standard system-wide operation of the man(1) command. It covers all of the places the ports system will put manpages and all of the system manpages. That is generally sufficient for most sites. If you have a customised directory layout and start putting man pages in unusual places, then you've got two choices. If these oddly located man pages are for general consumption, then add the appropriate info to /etc/manpath.config -- by editing that one file you will make those manpages visible immediately to all users on the system. Otherwise if you have your own private stache of manpages you should set MANPATH in your shell initialization scripts. However, you should not assume that MANPATH is already set so that you can just append to it. To get the best of both worlds, set your local $MANPATH based on the output of manpath(1). For Bourne-type shells, something like: MANPATH=3D"${MANPATH:-$(manpath)}:/foo/bar/man:/baz/quux/man" export MANPATH Or to ignore any previous setting of MANPATH in the environment: MANPATH=3D$( unset MANPATH ; manpath ) export MANPATH csh equivalents are left as an exercise for the student. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW --------------enig5DD2A3A0591EFFCC152A1BB8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEtzGt8Mjk52CukIwRA6ptAJ4h527A3BCwsbl9xHfPssIYdZtwPQCggdcP GC5yTDtWhT9dXA5MWwyzF+c= =JsC9 -----END PGP SIGNATURE----- --------------enig5DD2A3A0591EFFCC152A1BB8--