Let's document: Parallels

[pixelcmtd]

Finding online info is kinda difficult (manpages might be available somewhere), most of these should be in common, since Parallels is no longer macOS-only. Also, there are probably more binaries, but I've only included those that were on my Mac and seemed easy to understand. (i.e. don't require tracing through IDA or Russian forums for hours to find the information required)

• [ ] pbackup
• [ ] pmigrate
• [ ] pnetstat
• [ ] prlctl
  • [ ] prctl create
  • [ ] prctl list
  • [ ] prctl delete
  • [ ] prctl register
  • [ ] prctl unregister
  • [ ] prctl clone
  • [ ] prctl convert
  • [ ] prctl move
  • [ ] prctl installtools
  • [ ] prctl enter
  • [ ] prctl exec
  • [ ] prctl status
  • [ ] prctl start
  • [ ] prctl change-sid
  • [ ] prctl capture
  • [ ] prctl encrypt
    • [ ] prctl decrypt
  • [ ] prctl archive
  • [ ] prctl unarchive
  • [ ] prctl protection-set
  • [ ] prctl protection-remove
  • [ ] prctl set [1]
  • [ ] prctl snapshot
    • [ ] prctl snapshot-delete
    • [ ] prctl snapshot-list
    • [ ] prctl snapshot-switch
  • [ ] prctl problem-report
  • [ ] prctl guest-debugger
  • [ ] prctl debug-dump
    • prl
• [ ] prl_client_app
• [ ] prl_convert [Old Doc]
• [ ] prl_disk_tool
• [ ] prl_esd2iso
• [ ] prl_ls_users
• [ ] prl_macvm_create
• [ ] prl_mkiso
• [ ] prl_packer_inplace
• [ ] prl_perf_ctl
• [ ] prl_switchspaces
• [ ] prl_updater_ctl
• [ ] prl_vmarchiver
• [ ] prlauth
• [ ] prlcore2dmp
• ~prlexec~ (Broken syslink)
• [ ] prlsrvctl

[asdsyd]

I would like to contribute to this issue but unsure how to do? New to open source contribution.

[navarroaxel]

@asdsyd you should check the contribution-guides first, mainly the style-guide. Then you Google about this command and try to experiment with it locally. Then you can look for a similar command into the existing tldr-pages, maybe you can "clone" examples from them. And then just write your original examples and we can review when you create the PR. Remember that create a PR from your fork's main branch is a bad practice. Create a feature branch in your fork and send the PR from it.

[kbdharun]

@pixelcmtd I added documentation links and added some subcommands. I am not sure if the subcommands with subcommands require separate pages. My friends with mac love parallels and they hate that it has very less documentation.

Finding online info is kinda difficult (manpages might be available somewhere)

Lol, I search it for the past hour I could find none except the parallel's official page. And their command line reference page is the worst. I need to parse through individual pages in order to find these commands. They have a PDF version of the command line reference which can be useful but it can't be referred in pages as they don't have a well defined link.

Parallels is no longer macOS-only. Also, there are probably more binaries, but I've only included those that were on my Mac and seemed easy to understand. (i.e. don't require tracing through IDA or Russian forums for hours to find the information required)

I agree with you some commands work in Linux as well as Windows as per documentation so these commands must definitely be placed in common directory.

I will try to create some PRs soon.

[kbdharun]

I can't find many links to prl, I could only find some pages, the only other page referring to prl is some C API reference page, I guess we can add the currently available pages. And leave the rest for later.