1. Forum
  2. USENET
  3. comp.sys.mac.system

  • Re: Man command does not behave properly.

    From Sandman@mr@sandman.net to comp.sys.mac.apps,comp.sys.mac.system on Friday, July 04, 2003 14:16:34
    From Newsgroup: comp.sys.mac.system

    In article <BB2AE530.974A%michel_tremblay@hotmail.com>,
    Pierre-Michel Tremblay <michel_tremblay@hotmail.com> wrote:

    Bonjour,

    I'ld like to know how I can reactivate my man pages. I don't know exactly what I did to "loose" them. I know they are still there but the "man" command produces now the following output:


    [modemcable026:/Volumes/FireWire 78100] ptremblay% man chown
    /usr/bin/man: illegal option -- C
    man, version 1.1

    You might have "man" aliased to somehing else. Write "alias man" and see if it prints something including the -C option.

    --
    Sandman[.net]
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Dave Seaman@dseaman@no.such.host to comp.sys.mac.apps,comp.sys.mac.system on Friday, July 04, 2003 13:28:39
    From Newsgroup: comp.sys.mac.system

    On Fri, 04 Jul 2003 08:02:56 -0400, Pierre-Michel Tremblay wrote:
    Bonjour,

    I'ld like to know how I can reactivate my man pages. I don't know exactly what I did to "loose" them. I know they are still there but the "man" command produces now the following output:


    [modemcable026:/Volumes/FireWire 78100] ptremblay% man chown
    /usr/bin/man: illegal option -- C
    man, version 1.1

    Do you have fink installed? If so, try "fink list manconf" to see
    whether that package is the culprit. The current description should
    read:

    manconf-20020121-12: Placeholder package for Jaguar update (do not install)
    This is a placeholder manconf package for the Jaguar update.
    It is used to remove manconf from binary users' systems.
    Once this has been installed, it can be removed.
    .
    Maintainer: Ben Hines <bhines@alumni.ucsd.edu>


    If you have manconf installed from an old version of fink and the
    description doesn't look like this, your manconf is probably the culprit.
    You should visit fink.sf.net and follow the instructions for upgrading to Jaguar.

    The point is, if you simply try a "fink remove manconf", fink may object
    that the package is needed to satisfy some dependency. If you upgrade to
    the latest version of fink and install the new manconf, it gets rid of
    the offending patch but leaves all dependencies satisfied.


    --
    Dave Seaman
    Judge Yohn's mistakes revealed in Mumia Abu-Jamal ruling. <http://www.commoncouragepress.com/index.cfm?action=book&bookid=228>
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Kiran@kiran@no.spam to comp.sys.mac.apps,comp.sys.mac.system on Tuesday, July 08, 2003 16:53:41
    From Newsgroup: comp.sys.mac.system

    Pierre-Michel Tremblay <michel_tremblay@hotmail.com> wrote:

    I'ld like to know how I can reactivate my man pages. I don't know exactly what I did to "loose" them. I know they are still there but the "man" command produces now the following output:

    [modemcable026:/Volumes/FireWire 78100] ptremblay% man chown
    /usr/bin/man: illegal option -- C
    ...

    Well, /usr/bin/man is the "right" man. Looks like either somebody has
    messed with this file, or one of your init files (.login, .cshrc, etc)
    has aliased "man" to mean "man -C". Run the following commands and post
    their outputs and we'll take it from there:

    alias man
    where man
    ls -l /usr/bin/m*

    I suspect your answer lies in the alias; but "where" would tell you if
    you have other man's lying around, and the last one may alert us if
    your /usr/bin/man is more recent than other apps there, and hence
    likely to have been tempered with.

    -
    --- Synchronet 3.18b-Win32 NewsLink 1.113