Re: 6.1-RELEASE-i386 man broken?
On Monday 17 July 2006 03:49, J wrote:
> On 2006-07-14 (Fri) 06:55:28 [+], Matthew Seaman wrote:
> > J wrote:
>
> ...
>
> > > FreeBSD, recently, as my transported Linux bash configs contained
> > > MANPATH=$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="${MANPATH:-$(manpath)}:/foo/bar/man:/baz/quux/man"
> > export MANPATH
> >
> > Or to ignore any previous setting of MANPATH in the environment:
> >
> > MANPATH="$( unset MANPATH ; manpath ):/foo/bar/man:/baz/quux/man"
> > export MANPATH
> >
> > csh equivalents are left as an exercise for the student.
>
> Thanks for your time and reply. I'm afraid I'm still failing to see the
> special advantage in the 'MANPATH-produces-warning' method, but I
> suppose it's a 'when in Rome'. :)
> ___
this one has me totally stumped. i have read and re-read this thread so many
times hopeing that i missed some important clue. i have 2 6.1 systems, one
STABLE, and one RELENG (actually, i have i have about 6 RELENG systems, and
just 1 STABLE). the STABLE is exhibiting the:
[EMAIL PROTECTED] ~]$ man man
No manual entry for man
...behavior, but ive been thru checking all the configs, and i cant find whats
different. i have the same .bashrc file on each one (just 3 alias and 1
console colors line, thats it.. no paths or other variables are changed).
all my RELENG boxes will do man pages just fine. here is a brief comparison
of the things suggested in this thread, between my STABLE and one of my
RELENG's:
[EMAIL PROTECTED] ~]$ cat /etc/manpath.config | egrep -v '^#'
MANDATORY_MANPATH /usr/share/man
MANDATORY_MANPATH /usr/share/openssl/man
OPTIONAL_MANPATH/usr/local/man
OPTIONAL_MANPATH/usr/X11R6/man
MANPATH_MAP /bin/usr/share/man
MANPATH_MAP /usr/bin/usr/share/man
MANPATH_MAP /usr/local/bin /usr/local/man
MANPATH_MAP /usr/X11R6/bin /usr/X11R6/man
OPTIONAL_MANPATH/usr/local/lib/perl5/5.8.8/man
OPTIONAL_MANPATH/usr/local/lib/perl5/5.8.8/perl/man
[EMAIL PROTECTED] ~]$ manpath
/usr/share/man:/usr/local/man:/usr/X11R6/man:/usr/share/openssl/man:/usr/local/lib/perl5/5.8.8/man:/usr/local/lib/perl5/5.8.8/perl/man
[EMAIL PROTECTED] ~]$ cat /etc/manpath.config | egrep -v '^#'
MANDATORY_MANPATH /usr/share/man
MANDATORY_MANPATH /usr/share/openssl/man
OPTIONAL_MANPATH/usr/local/man
OPTIONAL_MANPATH/usr/X11R6/man
MANPATH_MAP /bin/usr/share/man
MANPATH_MAP /usr/bin/usr/share/man
MANPATH_MAP /usr/local/bin /usr/local/man
MANPATH_MAP /usr/X11R6/bin /usr/X11R6/man
OPTIONAL_MANPATH/usr/local/lib/perl5/5.8.8/man
OPTIONAL_MANPATH/usr/local/lib/perl5/5.8.8/perl/man
[EMAIL PROTECTED] ~]$ manpath
Warning: couldn't stat file /usr/X11R6/man!
/usr/share/man:/usr/local/man:/usr/share/openssl/man:/usr/local/lib/perl5/5.8.8/man:/usr/local/lib/perl5/5.8.8/perl/man
the RELENG appears to not be happy about the mans for x11, but other than
that, all the manuals work on all my RELENG boxes, and my STABLE is the only
one that does not.
i throw my hands in the air... completely stumped. of course, all my RELENGs
are servers, and my 1 STABLE box is my workstation (with KDE, and i dont
exactly recall at what point i noticed that man pages were no longer
working). if anyone has any advice to offer me, i would greatly appreciate
it.
thanks,
jonathan
___
freebsd-questions@freebsd.org mailing li
Re: 6.1-RELEASE-i386 man broken?
On 2006-07-14 (Fri) 06:55:28 [+], Matthew Seaman wrote:
> J wrote:
...
> > FreeBSD, recently, as my transported Linux bash configs contained
> > MANPATH=$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="${MANPATH:-$(manpath)}:/foo/bar/man:/baz/quux/man"
> export MANPATH
>
> Or to ignore any previous setting of MANPATH in the environment:
>
> MANPATH="$( unset MANPATH ; manpath ):/foo/bar/man:/baz/quux/man"
> export MANPATH
>
> csh equivalents are left as an exercise for the student.
>
Thanks for your time and reply. I'm afraid I'm still failing to see the
special advantage in the 'MANPATH-produces-warning' method, but I
suppose it's a 'when in Rome'. :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-RELEASE-i386 man broken?
J wrote:
> On 2006-07-13 (Thu) 13:25:04 [+], 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.
>
> I ran into and had to solve this problem myself when first coming to
> FreeBSD, recently, as my transported Linux bash configs contained
> MANPATH=$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="${MANPATH:-$(manpath)}:/foo/bar/man:/baz/quux/man"
export MANPATH
Or to ignore any previous setting of MANPATH in the environment:
MANPATH="$( unset MANPATH ; manpath ):/foo/bar/man:/baz/quux/man"
export MANPATH
csh equivalents are left as an exercise for the student.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: 6.1-RELEASE-i386 man broken?
J wrote:
> On 2006-07-13 (Thu) 13:25:04 [+], 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.
>
> I ran into and had to solve this problem myself when first coming to
> FreeBSD, recently, as my transported Linux bash configs contained
> MANPATH=$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="${MANPATH:-$(manpath)}:/foo/bar/man:/baz/quux/man"
export MANPATH
Or to ignore any previous setting of MANPATH in the environment:
MANPATH=$( unset MANPATH ; manpath )
export MANPATH
csh equivalents are left as an exercise for the student.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: 6.1-RELEASE-i386 man broken?
On 2006-07-13 (Thu) 13:25:04 [+], 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. > I ran into and had to solve this problem myself when first coming to FreeBSD, recently, as my transported Linux bash configs contained MANPATH=$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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 6.1-RELEASE-i386 man broken?
freebsd-questions: Nick Withers wrote: > Unfortunately (or at least as I understand it), the contents of > "/etc/manpath.config" don't matter if you have the "MANPATH" > environment variable set. Did you happen to set this yourself > (i.e., explicitly)? Yes: 2006-07-13 13:09:50 [EMAIL PROTECTED] ~ $ grep MANPATH .* .bash_history:echo $MANPATH .bash_profile:MANPATH=$MANPATH:$HOME/cvs/man .bash_profile:MANPATH=$MANPATH:$HOME/man .bash_profile:MANPATH=$MANPATH:$HOME/share/man .bash_profile:export MANPATH=:$HOME/local/man 2006-07-13 13:09:58 [EMAIL PROTECTED] ~ $ echo $MANPATH :/home/dpchrist/local/man I use the same .bash_profile and .bashrc everywhere, with conditionals for various platforms and configurations. Tightening up the conditionals, logging out, and logging in again: 2006-07-13 13:12:55 [EMAIL PROTECTED] ~ $ echo $MANPATH 2006-07-13 13:12:56 [EMAIL PROTECTED] ~ $ manpath /usr/share/man:/usr/local/man:/usr/X11R6/man:/usr/share/openssl/man: /usr/local/lib/perl5/5.8.8/man:/usr/local/lib/perl5/5.8.8/perl/man 2006-07-13 13:12:59 [EMAIL PROTECTED] ~ $ man man Fixed! Micah wrote: > That's where http://www.freebsd.org/cgi/man.cgi comes in handy Yes, that's useful. 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. Thanks everyone for your help. :-) David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-RELEASE-i386 man broken?
David Christensen wrote: > Matthew Seaman wrote: >> What are the contents of /etc/manpath.config ? > > $ cat /etc/manpath.config | egrep -v '^#' > MANDATORY_MANPATH /usr/share/man > MANDATORY_MANPATH /usr/share/openssl/man > OPTIONAL_MANPATH/usr/local/man > OPTIONAL_MANPATH/usr/X11R6/man > MANPATH_MAP /bin/usr/share/man > MANPATH_MAP /usr/bin/usr/share/man > MANPATH_MAP /usr/local/bin /usr/local/man > MANPATH_MAP /usr/X11R6/bin /usr/X11R6/man > OPTIONAL_MANPATH/usr/local/lib/perl5/5.8.8/man > OPTIONAL_MANPATH/usr/local/lib/perl5/5.8.8/perl/man > > >> You can see the ultimate result by running the 'manpath' command. > > 2006-07-13 08:38:20 [EMAIL PROTECTED] ~ > $ manpath > (Warning: MANPATH environment variable set) > :/home/dpchrist/local/man > > >> See the manpath(1) man page for more information. > > 2006-07-13 08:38:58 [EMAIL PROTECTED] ~ > $ man manpath > No manual entry for manpath > > > Any other ideas? Please read what I wrote more carefully. To summarize: don't set $MANPATH in your environment, and the man(1) command will work correctly. Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: 6.1-RELEASE-i386 man broken?
On Jul 13, 2006, at 11:48 AM, Nick Withers wrote: Unfortunately (or at least as I understand it), the contents of "/etc/manpath.config" don't matter if you have the "MANPATH" environment variable set. Is this true if you set it to "$MANPATH:/usr/local/additional/path" ? Come to think of it, this might be the source of David's issue. Jaime ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-RELEASE-i386 man broken?
Nick Withers wrote: On Thu, 13 Jul 2006 08:42:53 -0700 "David Christensen" <[EMAIL PROTECTED]> wrote: Matthew Seaman wrote: See the manpath(1) man page for more information. 2006-07-13 08:38:58 [EMAIL PROTECTED] ~ $ man manpath No manual entry for manpath Hahaha... I absolutely *love* these kinds of problems... You can't find the man page because of a problem locating man pages! :-) That's where http://www.freebsd.org/cgi/man.cgi comes in handy - as long as you also have a working web browser somewhere. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-RELEASE-i386 man broken?
On Thu, 13 Jul 2006 08:42:53 -0700 "David Christensen" <[EMAIL PROTECTED]> wrote: > Matthew Seaman wrote: > > What are the contents of /etc/manpath.config ? > > $ cat /etc/manpath.config | egrep -v '^#' > MANDATORY_MANPATH /usr/share/man > MANDATORY_MANPATH /usr/share/openssl/man > OPTIONAL_MANPATH/usr/local/man > OPTIONAL_MANPATH/usr/X11R6/man > MANPATH_MAP /bin/usr/share/man > MANPATH_MAP /usr/bin/usr/share/man > MANPATH_MAP /usr/local/bin /usr/local/man > MANPATH_MAP /usr/X11R6/bin /usr/X11R6/man > OPTIONAL_MANPATH/usr/local/lib/perl5/5.8.8/man > OPTIONAL_MANPATH/usr/local/lib/perl5/5.8.8/perl/man Unfortunately (or at least as I understand it), the contents of "/etc/manpath.config" don't matter if you have the "MANPATH" environment variable set. Did you happen to set this yourself (i.e., explicitly)? If not, would you be able to post the output of the "pkg_info" command, just so those that have a much better understanding of the environment than me might be able to narrow down which installation (if any) might be harrassed for the dramas you're undergoing? > > You can see the ultimate result by running the 'manpath' command. > > 2006-07-13 08:38:20 [EMAIL PROTECTED] ~ > $ manpath > (Warning: MANPATH environment variable set) Just thought I should draw attention to the warning above... > :/home/dpchrist/local/man > > > > See the manpath(1) man page for more information. > > 2006-07-13 08:38:58 [EMAIL PROTECTED] ~ > $ man manpath > No manual entry for manpath Hahaha... I absolutely *love* these kinds of problems... You can't find the man page because of a problem locating man pages! :-) > Any other ideas? > > David > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Nick Withers email: [EMAIL PROTECTED] Web: http://www.nickwithers.com Mobile: +61 414 397 446 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 6.1-RELEASE-i386 man broken?
Matthew Seaman wrote: > What are the contents of /etc/manpath.config ? $ cat /etc/manpath.config | egrep -v '^#' MANDATORY_MANPATH /usr/share/man MANDATORY_MANPATH /usr/share/openssl/man OPTIONAL_MANPATH/usr/local/man OPTIONAL_MANPATH/usr/X11R6/man MANPATH_MAP /bin/usr/share/man MANPATH_MAP /usr/bin/usr/share/man MANPATH_MAP /usr/local/bin /usr/local/man MANPATH_MAP /usr/X11R6/bin /usr/X11R6/man OPTIONAL_MANPATH/usr/local/lib/perl5/5.8.8/man OPTIONAL_MANPATH/usr/local/lib/perl5/5.8.8/perl/man > You can see the ultimate result by running the 'manpath' command. 2006-07-13 08:38:20 [EMAIL PROTECTED] ~ $ manpath (Warning: MANPATH environment variable set) :/home/dpchrist/local/man > See the manpath(1) man page for more information. 2006-07-13 08:38:58 [EMAIL PROTECTED] ~ $ man manpath No manual entry for manpath Any other ideas? David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-RELEASE-i386 man broken?
David Christensen wrote: > hello, world! > > I'm a FreeBSD newbie who has installed FreeBSD 6.1-RELEASE-i386 using > the "developer with X" option. "man" doesn't seem to work: > > 2006-07-12 21:59:38 [EMAIL PROTECTED] ~ > # man man > No manual entry for man > > 2006-07-12 22:12:42 [EMAIL PROTECTED] ~ > # echo $MANPATH > :/root/local/man > > > The same goes for makewhatis: > > 2006-07-12 22:12:47 [EMAIL PROTECTED] ~ > # makewhatis > makewhatis: : No such file or directory > makewhatis: /root/local/man: No such file or directory > > > Any suggestions? What are the contents of /etc/manpath.config ? The entries in there on a newly installed system will give the man(1) command access to all of the man pages installed in the usual locations (/usr/share/man, /usr/local/man, /usr/X11R6/man) If you've got perl installed there will be a couple of extra 'OPTIONAL_MANPATH' entries specially for that. You can see the ultimate result by running the 'manpath' command. The environment variable MANPATH should in general not be set, as that will override the effects of /etc/manpath.config. See the manpath(1) man page for more information. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK signature.asc Description: OpenPGP digital signature
