Delete man command in terminal

Discussion in 'MacBook Pro' started by ericsvizeny, Dec 7, 2010.

  1. ericsvizeny macrumors newbie

    Joined:
    Dec 7, 2010
    #1
    I have download a program, and decided I do not want it.

    this is what the program does:

    "n the spirit of true STW, we have decided to release our automated PACE
    unpacker. Rather than attempt to keep up with minor updates and all requests as
    pertaining to PACE, we're gonna put the power to crack ANY PACE program right
    in your hands. The goal of this is to free up some time for our next big
    release... We've mentioned before that we wish to bring more than iLok to the
    community, and now we're going to. In the future, we will be just updating this
    program as needs require, i.e. PACE implements a new version, etc. Enjoy this
    guys!

    unpace is a command line program that will strip away the PACE protection from
    an executable. Just like any tool, you will need to learn how to use it. A
    complete description and documentation can be found in the man page; i.e. typing
    "man unpace" at the terminal after install.

    We have used unpace for every single one of our releases. It is rock-stable, but
    not without personality. Take the time to get to know it, and you will come to
    love it.

    As part of this package, minihost.app will be installed to your /Applications
    folder. This program is required for cracking some plugins that require external
    frameworks. Again, more details can be found in the man page by typing "man
    unpace" at the terminal prompt.

    Remember that some apps include custom protection in addition to PACE. unpace
    will only strip away the PACE wrapper, which should make any custom prot you
    encounter crackable."

    I want to be able to go into terminal and type in "man unpace" and have nothing come up. I can not figure out how to delete this program.

    Any help would be great!

    Thanks!
    Eric
     
  2. QuarterSwede macrumors G3

    QuarterSwede

    Joined:
    Oct 1, 2005
    Location:
    Colorado Springs, CO
    #2
    I'm guessing you want to delete "unpace" (at least I think that's what it's called) and not "man" as man is the default manual command for *nix. Is that right?
     
  3. ericsvizeny, Dec 7, 2010
    Last edited by a moderator: Dec 7, 2010

    ericsvizeny thread starter macrumors newbie

    Joined:
    Dec 7, 2010
    #3
    Correct, I want to delete "unpace"

    Any help would be great guys!

    Eric
     
  4. LPZ macrumors 65816

    Joined:
    Jul 11, 2006
    #4
    Open Terminal and enter

    Code:
    man unpace
    Post the entire output.
     
  5. ericsvizeny, Dec 7, 2010
    Last edited by a moderator: Dec 7, 2010

    ericsvizeny thread starter macrumors newbie

    Joined:
    Dec 7, 2010
    #5
    This is what comes up when I do that:

    Code:
    Last login: Tue Dec  7 19:22:42 on ttys000
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$ man unpace
    
    unpace(1)                 BSD General Commands Manual                unpace(1)
    
    NAME
         unpace -- an automated PACE unpacker for Intel architecture.
    
    SYNOPSIS
         unpace [-abrsd] [-f /path/to/crypted/bundle]
    
    DESCRIPTION
         unpace decrypts, unpacks, and strips a file of all PACE protection. If a
         file contains multiple architectures, it is thinned to i386 only before
         processing.  unpace requires the latest PACE extensions to be installed.
         They can be found here:
         [url]http://www.paceap.com[/url]
    
         Typically, you would invoke unpace just by specifying the unpace -f
         option followed by the path to the bundle. This will suffice in most
         cases. If plug-ins are crashing, try using the -r or -s options.
    
         A list of arguments and their descriptions:
    
         -f [path]  A path to a PACE-protected plug-in, app, or framework. This
                    must be a bundle, unless the -b option is specified. This is
                    most easily done by typing: unpace -f , followed by a <space>
                    and then dragging and dropping the bundle onto the Terminal
                    window. If -b is specified, then [path] must be the path to a
                    binary file.
    
         -s         Do not strip binary. By default, unpace will strip the binary
                    of symbols, sections, and data that is no longer needed. Pass-
                    ing this flag will tell unpace not to strip the executable.
                    This is useful in some very rare cases that stripping the
                    binary causes runtime issues with the plug-in / app. Also,
                    this flag is required when unpacing a framework bundle.
    
         -r         Do not strip resource file. By default, unpace will strip the
                    bundle's .rsrc file of unused and unneeded PACE resources.
                    This option is recommended to try only if the default causes
                    issues. Once you use the -s option, you can no longer clean
                    the resource file if you haven't already done so.
    
         -u         Do not unpack. This option forgoes decrypting and unpacking
                    the bundle. It is useful if used in combination with the -s or
                    the -r option to just strip the symbols or the resource file.
    
         -b         This tells unpace that [path] is a path to a binary file, not
                    a bundle. Using this option will automatically set the -r
                    option, because a binary has no resource file.
    
         -a         Ask for continued break on dyld_notify. Sometimes an encrypted
                    program will load several frameworks that are encrypted, and
                    unpace does not know which one corresponds to the path you
                    passed to the unpace -f option. In this case, you would spec-
                    ify this flag and follow the on-screen prompts when unpacking
                    to point unpace at the correct bundle. This is only used if
                    you are unpacking a file.
    
         -h [host]  A name of a host, or a path to the binary of a custom host.
                    This option is incredibly useful in a lot of cases if used
                    properly. The accepted values are:
    
                    minihost:  This option requires minihost.app to be in your
                               /Applications folder. minihost is useful if a plug-
                               in requires an external framework to be loaded.
                               You'll know this is the case if you attempt to run
                               unpace on a bundle and it complains about not being
                               able to open a framework at @exe-
                               cutable_path/../Frameworks. In this case, you'll
                               have to locate the framework it's looking for and
                               copy it into the embedded frameworks folder of
                               minihost.app (located in
                               /Applications/minihost.app/Contents/Frameworks) and
                               run unpace with -h minihost option.
    
                    auhost:    This option requires AudioUnitHosting.app to be in
                               your /Applications folder. auhost was a required
                               option when cracking the Waves v7r8 plug-ins. If
                               you use auhost, pass the correct path to the unpace
                               -f option and then choose the plugin in auhost that
                               corresponds to that file to trigger the load.
    
                    reaper:    This option requires REAPER.app to be in your
                               /Applications folder. reaper was useful for trig-
                               gering the PACE protection in VST plug-ins, but is
                               no longer needed now that unpace uses it's own
                               internal loader. However, it's left here in case
                               it's useful again and for nostalgic purposes.
    
                    [path]     This option is here to give an opportunity to pro-
                               vide your own host for use in loading plug-ins. For
                               example, Pro Tools or Digital Performer. When spec-
                               gering the PACE protection in VST plug-ins, but is
                               no longer needed now that unpace uses it's own
                               internal loader. However, it's left here in case
                               it's useful again and for nostalgic purposes.
    
                    [path]     This option is here to give an opportunity to pro-
                               vide your own host for use in loading plug-ins. For
                               example, Pro Tools or Digital Performer. When spec-
                               ifying this option, you must provide the complete
                               path to the actual binary, not just the app bundle.
    
    DISCUSSION
         unpace was used for very single one of our releases. It's incredibly
         reliable and efficient, but is capable of only unwrapping the PACE wrap-
         per.  Some plug-ins / apps use a custom protection scheme in addition to
         the PACE wrapper. Our hope is that by releasing our tool, other crackers
         can step up and defeat these prots as well.
    
    BUGS
         There are currently no known bugs. If you come across any, we'll be happy
         to hear of them.
    
    Mac OSX                        December 7, 2010                        Mac OSX
    (END)
     
  6. LPZ macrumors 65816

    Joined:
    Jul 11, 2006
    #6
    In Terminal, enter

    Code:
    ls /usr/local/bin/un*
    and post output.
     
  7. ericsvizeny thread starter macrumors newbie

    Joined:
    Dec 7, 2010
    #7
    Last login: Tue Dec 7 19:46:45 on ttys000
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$ ls /usr/local/bin/un*
    /usr/local/bin/unpace
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
     
  8. LPZ macrumors 65816

    Joined:
    Jul 11, 2006
    #8
    In Terminal, enter

    Code:
    ls /usr/local/man/man1
    and post output.
     
  9. ericsvizeny thread starter macrumors newbie

    Joined:
    Dec 7, 2010
    #9
    Last login: Tue Dec 7 19:46:45 on ttys000
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$ ls /usr/local/bin/un*
    /usr/local/bin/unpace
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$ ls /usr/local/man/man1
    ls: /usr/local/man/man1: No such file or directory
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
     
  10. LPZ macrumors 65816

    Joined:
    Jul 11, 2006
    #10
    That's a bit odd. Enter

    Code:
    ls /usr/man/man1/un*
    and post.
     
  11. ericsvizeny thread starter macrumors newbie

    Joined:
    Dec 7, 2010
    #11
    Last login: Tue Dec 7 19:50:16 on ttys000
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$ ls /usr/man/man1/un*
    ls: /usr/man/man1/un*: No such file or directory
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$ ls /usr/man/man1/un*
    ls: /usr/man/man1/un*: No such file or directory
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
     
  12. LPZ macrumors 65816

    Joined:
    Jul 11, 2006
    #12
    Weird.

    Enter

    Code:
    ls /usr/local/man
    and post.
     
  13. ericsvizeny thread starter macrumors newbie

    Joined:
    Dec 7, 2010
    #13
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$ ls /usr/local/man
    ls: /usr/local/man: No such file or directory
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
     
  14. LPZ macrumors 65816

    Joined:
    Jul 11, 2006
  15. ericsvizeny thread starter macrumors newbie

    Joined:
    Dec 7, 2010
    #15
    Last login: Tue Dec 7 20:19:40 on ttys001
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$ echo $MANPATH

    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
     
  16. LPZ macrumors 65816

    Joined:
    Jul 11, 2006
  17. ericsvizeny thread starter macrumors newbie

    Joined:
    Dec 7, 2010
    #17
    Last login: Tue Dec 7 20:24:43 on ttys000
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$ man -w unpace
    /usr/share/man/man1/unpace.1
    Eric-Svizenys-MacBook-Pro:~ ericsvizeny$
     
  18. LPZ macrumors 65816

    Joined:
    Jul 11, 2006
    #18
    OK!

    To remove the unpace executable and the unpace man entry, enter

    Code:
    sudo rm /usr/local/bin/unpace /usr/share/man/man1/unpace.1
    You'll need to enter your password when asked.

    Then you should be good.
     
  19. ericsvizeny thread starter macrumors newbie

    Joined:
    Dec 7, 2010
    #19
    That did it!!!!

    Thank you so much!

    Eric
    :apple:
     
  20. LPZ macrumors 65816

    Joined:
    Jul 11, 2006
    #20
    You're welcome. Sorry for the needlessly long solution. Should have used man -w right away.
     
  21. QuarterSwede macrumors G3

    QuarterSwede

    Joined:
    Oct 1, 2005
    Location:
    Colorado Springs, CO
    #21
    Wow LPZ, those are some skills! Kudos on the quick help.
     

Share This Page