Skip site
navigation (1)Skip section navigation (2)
FreeBSD Manual Pages
- beinstall.sh(8)
- install a boot environment using the current FreeBSD source tree
- boot0cfg(8)
- boot manager installation/configuration utility
- bsdinstall(8)
- system installer
- etcupdate(8)
- manage updates to system files not updated by installworld
- freebsd-update(8)
- fetch and install binary updates to FreeBSD
- freebsd-version(1)
- print the version and patch level of the installed system
- install(1)
- install binaries
- lsvfs(1)
- list installed virtual file systems
- rpc_gss_get_mechanisms(3)
- Get installed mechanisms
- rpc_gss_is_installed(3)
- Query for the presence os a security mechanism
- ypinit(8)
- build and install NIS databases
- SSL_CTX_set_msg_callback(3), SSL_CTX_set_msg_callback_arg(3), SSL_set_msg_callback(3), SSL_set_msg_callback_arg(3)
- install callback for observing protocol messages
- SSL_CTX_set_record_padding_callback(3), SSL_set_record_padding_callback(3), SSL_CTX_set_record_padding_callback_arg(3), SSL_set_record_padding_callback_arg(3), SSL_CTX_get_record_padding_callback_arg(3), SSL_get_record_padding_callback_arg(3), SSL_CTX_set_block_padding(3), SSL_set_block_padding(3)
- install callback to specify TLS 1.3 record padding
- CREATE_EXTENSION(7)
- install an extension
- Dpkg::Deps::KnownFacts(3perl)
- list of installed real and virtual packages
- GraphicsMagick++-config(1)
- get information about the installed version of Magick++
- GraphicsMagick-config(1)
- get information about the installed version of GraphicsMagick
- GraphicsMagickWand-config(1)
- get information about the installed version of GraphicsMagick
- MPI_Comm_call_errhandler(3)
- Call the error handler installed on a communicator
- MPI_File_call_errhandler(3)
- Call the error handler installed on a file
- MPI_Win_call_errhandler(3)
- Call the error handler installed on a window object
- Magick++-config(1)
- get information about the installed version of Magick++
- Magick-config(1)
- get information about the installed version of ImageMagick
- MagickCore-config(1)
- get information about the installed version of ImageMagick
- MagickWand-config(1)
- get information about the installed version of the Magick Wand
- Munin::Common::Defaults(3)
- Default values defined by installation scripts
- Munin::Master::HTMLOld(3), munin-html(3)
- A program to draw html-pages on an Munin installation
- Munin::Node::Configure::Plugin(3)
- Class representing a plugin, along with its installed and suggested services
- SSL_CTX_set_msg_callback(3), SSL_CTX_set_msg_callback_arg(3), SSL_set_msg_callback(3), SSL_set_msg_callback_arg(3)
- install callback for observing protocol messages
- SSL_CTX_set_msg_callback(3ossl), SSL_CTX_set_msg_callback_arg(3ossl), SSL_set_msg_callback(3ossl), SSL_set_msg_callback_arg(3ossl)
- install callback for observing protocol messages
- SSL_CTX_set_record_padding_callback(3), SSL_set_record_padding_callback(3), SSL_CTX_set_record_padding_callback_arg(3), SSL_set_record_padding_callback_arg(3), SSL_CTX_get_record_padding_callback_arg(3), SSL_get_record_padding_callback_arg(3), SSL_CTX_set_block_padding(3), SSL_set_block_padding(3)
- install callback to specify TLS 1.3 record padding
- SSL_CTX_set_record_padding_callback(3ossl), SSL_set_record_padding_callback(3ossl), SSL_CTX_set_record_padding_callback_arg(3ossl), SSL_set_record_padding_callback_arg(3ossl), SSL_CTX_get_record_padding_callback_arg(3ossl), SSL_get_record_padding_callback_arg(3ossl), SSL_CTX_set_block_padding(3ossl), SSL_set_block_padding(3ossl)
- install callback to specify TLS 1.3 record padding
- Tk_InitConsoleChannels.tk85(3), Tk_InitConsoleChannels(3)
- Install the console channels as standard channels
- Tk_InitConsoleChannels.tk86(3), Tk_InitConsoleChannels(3)
- Install the console channels as standard channels
- Wand-config(1)
- get information about the installed version of the Magick Wand
- XInstallColormap(3), XUninstallColormap(3), XListInstalledColormaps(3)
- control colormaps
- XmInstallImage(3)
- A pixmap caching function that adds an image to the image cache "XmInstallImage" "pixmaps"
- XmRepTypeAddReverse(3)
- A representation type manager function that installs the reverse converter for a previously registered representation type "XmRepTypeAddReverse" "representation type manager functions" "XmRepTypeAddReverse"
- XmRepTypeInstallTearOffModelConverter(3)
- A representation type manager function that installs the resource converter for XmNtearOffModel. "XmRepTypeInstallTearOff\%ModelConverter" "representation type manager functions" "XmRepTypeInstallTearOff\%ModelConverter"
- XmUninstallImage(3)
- A pixmap caching function that removes an image from the image cache "XmUninstallImage" "pixmaps"
- XmtHelpInstallContextHelp(3), XmtHelpInstallContextHelp()(3), XmtHelpContextHelpCallback()(3)
- keyboard bindings for context help
- XtParseAcceleratorTable(3), XtInstallAccelerators(3), XtInstallAllAccelerators(3)
- managing accelerator tables
- XtParseTranslationTable(3), XtAugmentTranslations(3), XtOverrideTranslations(3), XtUninstallTranslations(3)
- manage translation tables
- afSetErrorHandler(3)
- install a custom error handling routine
- al_install_audio(3)
- Allegro 5 API
- al_install_haptic(3)
- Allegro 5 API
- al_install_joystick(3)
- Allegro 5 API
- al_install_keyboard(3)
- Allegro 5 API
- al_install_mouse(3)
- Allegro 5 API
- al_install_system(3)
- Allegro 5 API
- al_install_touch_input(3)
- Allegro 5 API
- al_is_audio_installed(3)
- Allegro 5 API
- al_is_haptic_installed(3)
- Allegro 5 API
- al_is_joystick_installed(3)
- Allegro 5 API
- al_is_keyboard_installed(3)
- Allegro 5 API
- al_is_mouse_installed(3)
- Allegro 5 API
- al_is_system_installed(3)
- Allegro 5 API
- al_is_touch_input_installed(3)
- Allegro 5 API
- al_uninstall_audio(3)
- Allegro 5 API
- al_uninstall_haptic(3)
- Allegro 5 API
- al_uninstall_joystick(3)
- Allegro 5 API
- al_uninstall_keyboard(3)
- Allegro 5 API
- al_uninstall_mouse(3)
- Allegro 5 API
- al_uninstall_system(3)
- Allegro 5 API
- al_uninstall_touch_input(3)
- Allegro 5 API
- asksetup(1)
- Active Spam Killer user installer
- autoopts-config(1)
- script to get information about installed version of autoopts
- bg-installer(1)
- Standardized installer program
- byobu-launcher-install(1)
- Byobu Launcher installation utility
- byobu-launcher-uninstall(1)
- Byobu Launcher uninstallation utility
- caca-config(1)
- script to get information about the installed version of libcaca
- calamares(8)
- distribution-independent system installer
- chicken-install5(1), chicken-install(1)
- download and install extension libraries for CHICKEN Scheme
- chicken-status5(1), chicken-status(1)
- list information about installed libraries
- chicken-uninstall5(1), chicken-uninstall(1)
- uninstall extension library
- clamav-unofficial-sigs(8)
- Download, test, and install third-party ClamAV signature databases
- coffeebreak(6)
- pretend your machine is busy with a fake FreeBSD installer
- comprex-config(1)
- Get information about a libcomprex installation
- critcl_installer(n), critcl_install_guide(n)
- Critcl - The Installer's Guide
- curl-config(1)
- Get information about a libcurl installation
- cverules(1)
- Generate version matching rules for installed software on a Linux / Unix distribution
- deb-postinst(5)
- package post-installation maintainer script
- deb-preinst(5)
- package pre-installation maintainer script
- desktop-file-install(1), desktop-file-edit(1)
- Installation and edition of desktop files
- dfarc(1)
- An integrated frontend and .dmod installer
-
- dune-build(1), duneN'45'build(1)
- N'45' Build the given targets, or all installable targets if none are givenN'46'
- dune-exec(1), duneN'45'exec(1)
- N'45' Execute a command in a similar environment as if installation was performedN'46'
- dune-install(1), duneN'45'install(1)
- N'45' Install packagesN'46'
- dune-installed-libraries(1), duneN'45'installedN'45'libraries(1)
- N'45' Print out libraries installed on the systemN'46'
- dune-uninstall(1), duneN'45'uninstall(1)
- N'45' Uninstall packagesN'46'
- eboard-addtheme(1)
- a program to easily install new eboard board and sound themes
- eboard-config(1)
- program to get information about the installed eboard
- epminstall(1)
- add a directory, file, or symlink to a list file
- etcupdate(8)
- manage updates to system files not updated by installworld
- expatapi(n), CheckExpatParserObj(n), CHandlerSetInstall(n), CHandlerSetRemove(n), CHandlerSetCreate(n), CHandlerSetGetUserData(n), GetExpatInfo(n)
- Functions to create, install and remove expat parser object extensions
- extipl(8)
- a partition-selectable boot loader/installer for IBM-PC compatible computers
- flickcurl-config(1)
- script to get information about the installed version of flickcurl
- floppyd_installtest(1)
- tests whether floppyd is installed and running '" t TQ \$1 . (is' (if` (pd"
- fltk-config(1)
- script to get information about the installed version of fltk
- foomatic-kitload(8)
- installs a data kit into the foomatic database
- fvwm-config(1)
- query an existing fvwm installation
- g-wrap-config(1)
- script to get information about the installed version of G-Wrap
- gauche-install(1)
- install files and set attributes
- gdome-config(1)
- script to get information about the installed version of gdome2
- gettextize(1)
- install or upgrade gettext infrastructure
- gh-extension-install(1)
- Install a gh extension from a repository
- gh-extension-list(1)
- List installed extension commands
- gh-extension-remove(1)
- Remove an installed extension
- gh-extension-upgrade(1)
- Upgrade installed extensions
- ginstall(1), install(1)
- copy files and set attributes
- git-lfs-install(1)
- Install Git LFS configuration
- git-lfs-uninstall(1)
- Remove Git LFS configuration
- gpgrt-config(1)
- Script to get information about the installed version of libgpg-error
- grub-install(8)
- install GRUB to a device
- gsl-config(1)
- script to get version number and compiler flags of the installed GSL library
- gst-package(1)
- create and install GNU Smalltalk .star package files
- hash_create(3), hash_destroy(3), hash_install(3), hash_lookup(3), hash_uninstall(3), hash_iter(3)
- generic hash tables
- hostsearch(1)
- query several hosts for installed Debian packages
-
- ijs-config(1)
- script to get information about the installed version of ijs
- initialise_joystick(3)
- Deprecated version of install_joystick(). Allegro game programming library
- innoextract(1)
- tool to extract installers created by Inno Setup
- install-info(1)
- update info/dir entries
- install-mh(1)
- initialize the nmh environment
- install-mh(8)
- initialize the MH environment
- install-sid(8)
- update SUBMITTER variable in site or personal config files
- install_allegro(3)
- Initialise the Allegro library
- install_int(3)
- Installs a user timer handler. Allegro game programming library
- install_int_ex(3)
- Adds or modifies a timer. Allegro game programming library
- install_joystick(3)
- Initialises the joystick. Allegro game programming library
- install_keyboard(3)
- Installs the Allegro keyboard interrupt handler
- install_keyboard_hooks(3)
- Installs custom keyboard hooks. Allegro game programming library
- install_mouse(3)
- Installs the Allegro mouse handler
- install_param_int(3)
- Installs a timer routine with a customizable parameter. Allegro game programming library
- install_param_int_ex(3)
- Adds or modifies a timer with a customizable parameter. Allegro game programming library
- install_sound(3)
- Initialises the sound module. Allegro game programming library
- install_sound_input(3)
- Initialises the sound recorder module. Allegro game programming library
- install_timer(3)
- Installs the Allegro timer interrupt handler
- installcheck(1)
- find out which packages cannot be installed
- installer(8)
- Archiveopteryx installer
- installsieve(1)
- Cyrus IMAP documentation rst2man-indent-level 0 1 rstReportMargin \$1
- iodbc-config(1)
- script to get information about the installed version of iODBC
- kf5-config(1)
- Prints Qt(TM) and Frameworks installation paths
- knet_handle_add_datafd(3)
- Install a file descriptor for communication
- knet_handle_enable_filter(3)
- install a filter to route packets
- knet_handle_enable_pmtud_notify(3)
- install a callback to receive PMTUd changes
- knet_host_enable_status_change_notify(3)
- Install a callback to get host status change events
- kpackagetool5(1)
- Install, list, remove Plasma packages
-
- ldap_start_tls(3), ldap_start_tls_s(3), ldap_tls_inplace(3), ldap_install_tls(3)
- LDAP TLS initialization routines
- lib3ds-config(1)
- script to get information about the installed version of lib3ds
- libmikmod-config(1)
- script to get information about the installed version of libmikmod
- llvm-install-name-tool-devel(1), llvm-install-name-tool(1)
- LLVM tool for manipulating install-names and rpaths
- llvm-install-name-tool-morello(1), llvm-install-name-tool(1)
- LLVM tool for manipulating install-names and rpaths
- llvm-install-name-tool12(1), llvm-install-name-tool(1)
- LLVM tool for manipulating install-names and rpaths
- llvm-install-name-tool13(1), llvm-install-name-tool(1)
- LLVM tool for manipulating install-names and rpaths
- llvm-install-name-tool14(1), llvm-install-name-tool(1)
- LLVM tool for manipulating install-names and rpaths
-
- log4c-config(1)
- script to get information about the installed version of log4c
- mate-display-properties-install-systemwide(1)
- customize MATE display behavor
- mate-panel-test-applets(1)
- display and test installed applets
- mkc_install(1), install(1)
- install binaries
- mmencode(1)
- Translate to and from mail-oriented encoding formats (Same program also installed as "mimencode".)
- mrtg-nt-guide(1)
- The MRTG 2.17.4 Windows Installation Guide
- mrtg-unix-guide(1)
- The MRTG 2.17.4 Linux/Unix Installation Guide
- msiexec(1)
- Wine MSI Installer
- munin-html(8)
- A program to generate html-pages in an Munin installation
-
- mysql_install_db(1)
- initialize MySQL data directory
- mysql_secure_installation(1)
- improve MySQL installation security
- neon-config(1)
- script providing information about installed copy of neon library
- net-snmp-config(1)
- returns information about installed net-snmp libraries and binaries
- netatalk-config(1)
- script to get information about the installed version of netatalk
- newalias(1)
- install new elm aliases for user and/or system
-
- nurbs++-config(1)
- script to get information about the installed version of nurbs++
- opam-install(1), opamN'45'install(1)
- N'45' Install a list of packagesN'46'
- opam-installer(1), opamN'45'installer(1)
- N'45' Handles (un)installation of package files following instructions from opam *N'46'install filesN'46'
- opam-reinstall(1), opamN'45'reinstall(1)
- N'45' Reinstall a list of packagesN'46'
- opam-switch(1), opamN'45'switch(1)
- N'45' Manage multiple installation prefixesN'46'
- opam-uninstall(1), opamN'45'uninstall(1)
- N'45' An alias for removeN'46'
- opam-upgrade(1), opamN'45'upgrade(1)
- N'45' Upgrade the installed package to latest versionN'46'
- opendkim-testkey(8)
- DKIM filter installation test
- openssl-fipsinstall(1ossl)
- perform FIPS configuration installation
- opkg-cl(1)
- command line utility to install, upgrade and uninstall opkg software packages
- osinfo-detect(1)
- Detect the operating system on installable media or trees
- osinfo-install-script(1)
- generate a script for automated installation
- oyranos-profile-install(1)
- Oyranos CMS ICC profile installation tool
- packmule(1)
- Creates and packs custom FreeBSD installation images
- paperless(7)
- Index and archive scanned paper documents - installation
- patch-metamail(1)
- Install a patch to the latest metamail release
- perp-setup(8)
- initialize a perp installation
- pg_config(1)
- retrieve information about the installed version of PostgreSQL
- pkcs11-register(1)
- Simple tool to install PKCS#11 modules to known applications
- pkg-add(8), pkg add(8)
- Registers a package and installs it on the system
- pkg-audit(8), pkg audit(8)
- audit installed packages against known vulnerabilities
- pkg-check(8), pkg check(8)
- sanity check installed packages
- pkg-install(8), pkg install(8)
- install packages from remote package repositories or local archives
- pkg-set(8), pkg set(8)
- modify information in the installed database
- pkg-shlib(8), pkg shlib(8)
- display which installed package provides a specfic shared library, and the installed packages which require it library is the filename of the library without any leading path, but including the ABI version number. Only exact matches are handled
- pkg-version(8), pkg version(8)
- summarize installed versions of packages
- pkg-which(8), pkg which(8)
- display which package installed a specific file
- pkg_cleanup(1)
- deinstall 'leaf' packages
- pkg_cutleaves(1)
- deinstall 'leaf' packages
- pkg_deinstall(1)
- a package deinstaller with wildcards and dependency recursion support
- pkg_rmleaves(1)
- deinstall 'leaf' packages
- pkg_validate(1)
- list mismatched and missing files of installed packages
- pkgs_which(1)
- Quickly find packages where trees of files got installed
- plasmapkg2(1)
- Install, list, remove Plasma packages
- ple-config(1)
- Script to get information about the installed version of the PLE library
-
- portsreinstall(8)
- ports upgrading utility for massive forced reinstallation
- portsreinstall-chroot(8)
- Support utility for portsreinstall(8) to build packages in a virtual environment
- portsreinstall-chroot-mount(8)
- Support utility for portsreinstall(8) to mount and unmount a builder environment at the grand host environment
- portsreinstall-upgrade(8)
- Support utility for portsreinstall(8) to update a target environment using packages built in a builder environment
- portupdate-scan(8)
- scan /usr/ports/UPDATING, showing sections for installed ports
- portupgrade(1), portinstall(1)
- tools to upgrade installed packages or install new ones via ports or packages
- portversion(1)
- a tool to compare the versions of installed packages with the ones in the ports tree
- ppl-config(1)
- obtain information about an installation of the Parma Polyhedra Library
- psiconv-config(1)
- script to get information about the installed version of Psiconv
- pspell-config(1)
- prints information about a libpspell installation
- puppet(8)
- Usage: puppet subcommand [options] action [options] Available subcommands: Common: agent The puppet agent daemon apply Apply Puppet manifests locally config Interact with Puppet's settings. help Display Puppet help. lookup Interactive Hiera lookup module Creates, installs and searches for modules on the Puppet Forge. resource The resource abstraction layer shell Specialized: catalog Compile, save, view, and convert catalogs. describe Display help about resource types device Manage remote network devices doc Generate Puppet references epp Interact directly with the EPP template parser/renderer. facts Retrieve and store facts. filebucket Store and retrieve files in a filebucket generate Generates Puppet code from Ruby definitions. node View and manage node definitions. parser Interact directly with the parser. plugin Interact with the Puppet plugin system. script Run a puppet manifests as a script without compiling a catalog ssl Manage SSL keys and certificates for puppet SSL clients See 'puppet help subcommand action' for help on a specific subcommand action. See 'puppet help subcommand' for help on a specific subcommand. Puppet v7.15.0
- puppet-module(8)
- Creates, installs and searches for modules on the Puppet Forge
- pvm_addmhf(3), pvm_delmhf(3)
- Install or remove message-handler functions
- rabbitmq-upgrade(8)
- RabbitMQ installation upgrade tools
- raptor-config(1)
- script to get information about the installed version of Raptor
- rasqal-config(1)
- script to get information about the installed version of the RDF query library
- rcup(1)
- update and install dotfiles managed by rcm
- redland-config(1)
- script to get information about the installed version of Redland
- register_uformat(3)
- Installs handler functions for a new text encoding format. Allegro game programming library
- rinstall(1)
- fetch and install scripts over http
- sane-config(1)
- get information about the installed version of libsane
- set_display_switch_callback(3)
- Installs a switching notification callback. Allegro game programming library
- shtk_cleanup(3), cleanup(3)
- Utilities to install exit handlers for cleanup routines
- shtk_cleanup_register(3)
- Installs cleanup handlers to be called on script termination
- shtool-install(1), shtool install(1)
- GNU shtool install(1) command
-
- smokeping_install(7)
- How to install SmokePing
-
- spot(7)
- Command-line tools installed by Spot
- squeak(1), inisqueak(1)
- Unix Squeak virtual machine and installer
- switch2(1), gtk-theme-switch(1)
- fast and easy tool for switching and installing GTK themes
- sysconftool(1)
- install configuration files
- sysconftool(7)
- format of configuration files installed by sysconftool
- syslinux(1)
- install the SYSLINUX+1 bootloader on a FAT filesystem
- torrus_install_plugin(7), install_plugin(7)
- Installs the Torrus plugin
- ttf2pt1_x2gs(1)
- font installer for Ghostscript
- tvmet-config(1)
- script to get information about the installed version of tvmet
- type1inst(1)
- Type 1 PostScript font installation utility for the X Window System and Ghostscript
- uman(1)
- Uninstalled manual page reader
- unshield(1)
- extract CAB files from an InstallShield installer archive
- update-base(8)
- Easy install of kernel and world
- virt-install(1)
- provision new virtual machines
- wanted-ports(1)
- -- depend on the ports that you want installed
- wzd-config(1)
- retrieve information about the installed version of wzdftpd
- xapian-config(1)
- report information about the installed version of xapian
- xdg-desktop-icon(1)
- command line tool for (un)installing icons to the desktop
- xdg-desktop-menu(1)
- command line tool for (un)installing desktop menu items
- xdg-icon-resource(1)
- command line tool for (un)installing icon resources
- xine-config(1)
- script to get information about the installed version of libxine
- xmedcon-config(1)
- script to get info about the installed version of (X)MedCon
- xmlsec1-config(1)
- detail installed version of xmlsec library
- xosd-config(1)
- script to get information about the installed version of libxosd
- zeekctl(8)
- interactive shell for managing Zeek installations
- Alien::Build::MM(3)
- Alien::Build installer code for ExtUtils::MakeMaker
- Alien::Build::Plugin::Core::CleanInstall(3)
- Implementation for clean_install hook
- Alien::GSL(3)
- Easy installation of the GSL library
- Alien::Gimp(3)
- Encapsulate install info for GIMP
- App::Build(3)
- extends Module::Build to build/install/configure entire applications (i.e. web applications), not just modules and programs
- App::CLI::Extension::Component::InstallCallback(3)
- for App::CLI::Extension install callback module
- App::cpanminus(3)
- get, unpack, build and install modules from CPAN
- App::cpanminus::fatscript(3), cpanm(3)
- get, unpack build and install modules from CPAN
- App::perlbrew(3)
- Manage perl installations in your "$HOME"
- BZ::Client::Bugzilla(3), BZ::Client::Bugzilla(3)
- Provides information about the Bugzilla server. This class provides methods for accessing information about the Bugzilla servers installation
- Bundle::Apache2(3)
- Install Apache mod_perl2 and related modules
- Bundle::Apache::ASP(3)
- Install Apache::ASP and required
- Bundle::Apache::ASP::Extra(3), Bundle::Apache::ASP::Extra(3)
- Install modules that provide additional functionality to Apache::ASP
- Bundle::ApacheTest(3)
- A bundle to install all Apache-Test related modules
- Bundle::CGI::Builder::Complete(3)
- A bundle to install the complete CGI::Builder framework
- Bundle::DBD::CSV(3)
- A bundle to install the DBD::CSV driver
- Bundle::DBD::Pg(3)
- A bundle to install all DBD::Pg related modules
- Bundle::DBI(3)
- A bundle to install DBI and required modules
- Bundle::HTTP::WebTest(3)
- a bundle to install HTTP::WebTest
- Bundle::Perl6(3)
- A bundle to install Perl6-related modules
- Bundle::PerlPoint(3)
- A bundle to install PerlPoint related modules
- Bundle::PlRPC(3)
- A bundle to install PlRPC-Server, Client and prerequisites
- Bundle::SNMP::MIB::Compiler(3)
- A bundle to install all SNMP::MIB::Compiler related modules
- Bundle::Template::Magic(3)
- A bundle to install MagicTemplate distribution plus all related extensions and prerequisites
- Bundle::Text::Query::BuildSQL(3)
- A bundle to install related modules
- CPAN::Testers::Fact::InstalledModules(3)
- Versions of particular modules installed on a system
- CPANPLUS::Dist::Autobundle(3)
- distribution class for installation snapshots
- CPANPLUS::Dist::Build(3)
- CPANPLUS plugin to install packages that use Build.PL
- Carton::Doc::Install(3)
- Install the dependencies
- Class::Accessor::Installer(3)
- Install an accessor subroutine
- Class::MethodMaker::Engine(3)
- The parameter passing, method installation & non-data-structure methods of Class::MethodMaker
- DBD::MariaDB::INSTALL(3)
- How to install and configure DBD::MariaDB
- DBD::mysql::INSTALL(3)
- How to install and configure DBD::mysql
- DBIx::Class::Migration::Script::Help::install(3)
- Install a migration version
- DBIx::Class::Migration::Script::Help::install_if_needed(3)
- Install a migration only if needed
- DBIx::Class::Migration::Script::Help::install_version_storage(3)
- Add missing meta data table
- DBIx::Class::Migration::Script::Help::populate(3)
- Install fixtures to a database
- DBIx::Class::Schema::Loader::Optional::Dependencies(3), $class(3)
- Optional module dependency specifications (for module authors) EOC #@@ #@@ SYNOPSIS HEADING #@@ push @chunks, <<"EOC"; =head1 SYNOPSIS Somewhere in your build-file (e.g. ExtUtils::MakeMaker's Makefile.PL): ... e$EUMM_ARGS{CONFIGURE_REQUIRES} = { e%{ e$EUMM_ARGS{CONFIGURE_REQUIRES} || {} }, DBIx::Class::Schema::Loader => $distver, }; ... my %DBIC_CONFIG_AND_ORACLE_DEPS = %{ eval { require $class; $class->req_list_for([qw( dbicdump_config rdbms_oracle )]); } || {} }; e$EUMM_ARGS{PREREQ_PM} = { e%DBIC_CONFIG_AND_ORACLE_DEPS, e%{ e$EUMM_ARGS{PREREQ_PM} || {} }, }; ... ExtUtils::MakeMaker::WriteMakefile(e%EUMM_ARGS); Note: The eval protection within the example is due to support for requirements during the configure build phase not being available on a sufficient portion of production installations of Perl. Robust support for such dependency requirements is available in the CPAN installer only since version 1.94_56 first made available for production with perl version 5.12. It is the belief of the current maintainer that support for requirements during the configure build phase will not be sufficiently ubiquitous until the year 2020 at the earliest, hence the extra care demonstrated above. It should also be noted that some 3rd party installers (e.g. cpanminus) do the right thing with configure requirements independent from the versions of perl and CPAN available. EOC #@@ #@@ DESCRIPTION HEADING #@@ push @chunks, <<'EOC'; =head1 DESCRIPTION Some of the less-frequently used features of DBIx::Class::Schema::Loader have external module dependencies on their own. In order not to burden the average user with modules they will never use, these optional dependencies are not included in the base Makefile.PL. Instead an exception with a descriptive message is thrown when a specific feature can't find one or several modules required for its operation. This module is the central holding place for the current list of such dependencies, for DBIx::Class::Schema::Loader core authors, and DBIx::Class::Schema::Loader extension authors alike. Dependencies are organized in groups where each group can list one or more required modules, with an optional minimum version (or 0 for any version). In addition groups prefixed with test_ can specify a set of environment variables, some (or all) of which are marked as required for the group to be considered by req_list_for Each group name (or a combination thereof) can be used in the public methods as described below. EOC #@@ #@@ REQUIREMENT GROUPLIST HEADING #@@ push @chunks, '=head1 CURRENT REQUIREMENT GROUPS'; my $standalone_info; for my $group (sort keys %$dbic_reqs) { my $info = $standalone_info->{$group} ||= $class->_groups_to_reqs($group); next unless ( $info->{modreqs_fully_documented} and ( $info->{augments} or $info->{modreqs} ) ); my $p = $dbic_reqs->{$group}{pod}; push @chunks, ( "=head2 $p->{title}", "=head3 $group", $p->{desc}, =over, ); if ( keys %{ $info->{modreqs}||{} } ) { push @chunks, map { "=item * $_" . ($info->{modreqs}{$_} ? " >= $info->{modreqs}{$_}" : ) } ( sort keys %{ $info->{modreqs} } ) ; } else { push @chunks, =item * No standalone requirements, } push @chunks, =back; for my $ag ( sort keys %{ $info->{augments} || {} } ) { my $ag_info = $standalone_info->{$ag} ||= $class->_groups_to_reqs($ag); my $newreqs = $class->modreq_list_for([ $group, $ag ]); for (keys %$newreqs) { delete $newreqs->{$_} if ( ( defined $info->{modreqs}{$_} and $info->{modreqs}{$_} == $newreqs->{$_} ) or ( defined $ag_info->{modreqs}{$_} and $ag_info->{modreqs}{$_} == $newreqs->{$_} ) ); } if (keys %$newreqs) { push @chunks, ( "Combined with L</$ag> additionally requires:", =over, ( map { "=item * $_" . ($newreqs->{$_} ? " >= $newreqs->{$_}" : ) } ( sort keys %$newreqs ) ), =back, ); } } } #@@ #@@ API DOCUMENTATION HEADING #@@ push @chunks, <<'EOC';
- Dist::Joseki::Command::install(3)
- 'install' command for Dist::Joseki::Cmd
- Dist::Zilla(3)
- distribution builder; installer not included!
- Dist::Zilla::App::Command::clean(3)
- clean up after build, test, or install
- Dist::Zilla::App::Command::install(3)
- install your dist
- Dist::Zilla::Dist::Minter(3)
- distribution builder; installer not included!
- Dist::Zilla::Plugin::ExecDir(3)
- install a directory's contents as executables
- Dist::Zilla::Plugin::ModuleShareDirs(3)
- install a directory's contents as module-based "ShareDir" content
- Dist::Zilla::Plugin::ShareDir(3)
- install a directory's contents as "ShareDir" content
- Dist::Zilla::Role::ExecFiles(3)
- something that finds files to install as executables
- Dist::Zilla::Role::InstallTool(3)
- something that creates an install program for a dist
- Dist::Zilla::Role::ShareDir(3)
- something that picks a directory to install as shared files
- DtMsgLogSetHandler(3)
- installs an alternate message logging handler
- DtTermInitialize(3)
- prevent accelerators from being installed on a DtTerm widget
- ExtUtils::AutoInstall(3)
- Automatic install of dependencies via CPAN
- ExtUtils::Install(3)
- install files from here to there
- ExtUtils::InstallPaths(3)
- Build.PL install path logic made easy
- ExtUtils::Installed(3)
- Inventory management of installed modules
- FFI::Build::MM(3)
- FFI::Build installer code for ExtUtils::MakeMaker
- File::ShareDir::Install(3)
- Install shared files
- Gantry::Conf::FAQ(3)
- Frequently Asked Questions regarding Gantry::Conf "Why should I use Gantry::Conf at all?" 4 Item "Why should I use Gantry::Conf at all?" There are many reasons why we feel Gantry::Conf is helpful both during development and after deployment. The next two entries should hopefully answer this question for you as they outline a few common scenarios programmers and system administrators often face. "How is Gantry::Conf helpful during development?" 4 Item "How is Gantry::Conf helpful during development?" "Easy separation of development configs from production configs" 4 Item "Easy separation of development configs from production configs" Often programmers have a separate development environment from their production environment. By using <shared> blocks and dev instances you can avoid spending any serious time setting up your application in the development environment. Take this configuration example: <shared dev> dbuser nobody dbpass secret dbconn "dbi:Pg:dbname=dev" </shared> <shared production> dbuser apache dbpass secret2 dbconn "dbi:Pg:dbname=production" </shared> <instance app1> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use production </instance> <instance app1-dev> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use dev </instance> By separating out our production and dev database information into shared blocks we can essentially switch between our production and dev environments by simply changing the instance we are using. If you were working on a script this would be a simple matter of running: $ script.pl --instance=app1-dev instead of: $ script.pl --instance=app1 "How is Gatnry::Conf helpful in production?" 4 Item "How is Gatnry::Conf helpful in production?" Gantry::Conf has several advantages in a production environment. First, it provides a single place for all config information, if you commit to it. Even if you don't commit to it for all apps, it still provides control to the installing admin over how and where conf information is stored. For instance, the admin could put the config information directly into /etc/gantry.conf, or into a separate file in /etc/gantry.d. She could even set up a secure web server where all boxes would go to get their conf. The short answer is, Gantry::Conf is flexible and production environments benefit from flexibility. "How do I pass my instance information into my application?" 4 Item "How do I pass my instance information into my application?" There are many possible ways to do this a few of which are: "Command line arguments" 4 Item "Command line arguments" If your application accepts arguments on the command line we suggest adding an --instance option to pass in the instance's name. "PerlSetVar" 4 Item "PerlSetVar" In a mod_perl environment you could use a PerlSetVar, possibly named GantryConfInstance, to pull in this value for your application. "ModPerl::ParamBuilder" 4 Item "ModPerl::ParamBuilder" Again in a mod_perl environment, another option would be to use ModPerl::ParamBuilder to pass the instance name. "Hard coded" 4 Item "Hard coded" We include this for the sake of completeness, but advise against it. You could always simply hard code your instance information into your application, but this will greatly reduce the flexibility you have. "How do I add a different provider for an existing ConfigVia method?" 4 Item "How do I add a different provider for an existing ConfigVia method?" Place your provider module in the Gantry::Conf::Provider::Method::* namespace. Make sure your public API matches the existing providers which use the same method. For instance the flat file providers all implement a config method which is called as a class method and receives a file name. "How do I add to the ConfigVia methods?" 4 Item "How do I add to the ConfigVia methods?" If none of the existing provider methods will do, you need to work in Gantry::Conf. In particular, you need to augment the dispatch hash with the name of your provisioning method and a sub name which will handle it. Then you need to implement the method you put in %dispatch
- Gantry::Init(3)
- Gantry install options
- Imager::Graph::Horizontal(3), Imager::Graph::Horizontal(3)
- A super class for line/bar charts n .IP "add_data_series(e@data, $series_name)" 4 .IP "add_data_series(e@data, $series_name)" 4 Item "add_data_series(@data, $series_name)" Add a data series to the graph, of the default type. n .IP "add_bar_data_series(e@data, $series_name)" 4 .IP "add_bar_data_series(e@data, $series_name)" 4 Item "add_bar_data_series(@data, $series_name)" Add a bar data series to the graph. n .IP "add_line_data_series(e@data, $series_name)" 4 .IP "add_line_data_series(e@data, $series_name)" 4 Item "add_line_data_series(@data, $series_name)" Add a line data series to the graph. "set_column_padding($int)" 4 Item "set_column_padding($int)" Sets the number of pixels that should go between columns of data. "set_negative_background($color)" 4 Item "set_negative_background($color)" Sets the background color or fill used below the y axis. "draw()" 4 Item "draw()" Draw the graph "show_vertical_gridlines()" 4 Item "show_vertical_gridlines()" Shows vertical gridlines at the y-tics. Feature: vertical_gridlines "set_vertical_gridline_style(color => ..., style => ...)" 4 Item "set_vertical_gridline_style(color => ..., style => ...)" Set the color and style of the lines drawn for gridlines. Style equivalent: vgrid "show_line_markers()" 4 Item "show_line_markers()" "show_line_markers($value)" 4 Item "show_line_markers($value)" Feature: linemarkers. If $value is missing or true, draw markers on a line data series. Note: line markers are drawn by default. "use_automatic_axis()" 4 Item "use_automatic_axis()" Automatically scale the Y axis, based on Chart::Math::Axis. If Chart::Math::Axis isn't installed, this sets an error and returns undef. Returns 1 if it is installed. "set_x_tics($count)" 4 Item "set_x_tics($count)" Set the number of X tics to use. Their value and position will be determined by the data range
- Imager::Install(3)
- installation notes for Imager
- JMX::Jmx4Perl::Agent::Jolokia::Verifier::GnuPGVerifier(3)
- Verifies PGP signature with a natively installed GnuPG (with gpg found in the path)
- Lingua::Ispell(3), Lingua::Ispell.pm(3)
- a module encapsulating access to the Ispell program. Note: this module was previously known as Text::Ispell; if you have Text::Ispell installed on your system, it is now obsolete and should be replaced by Lingua::Ispell
- Maypole::Manual::Install(3)
- installing Maypole
- Minilla::CLI::Install(3)
- Install the dist to system
- Module::AutoInstall(3)
- Automatic install of dependencies via CPAN
- Module::Build(3)
- Build and install Perl modules
- Module::CPANTS::Kwalitee::BrokenInstaller(3)
- Check for broken Module::Install
- Module::Find(3)
- Find and use installed modules in a (sub)category
- Module::Install(3)
- Standalone, extensible Perl module installer
- Module::Install::API(3)
- Command Reference for Module::Install
- Module::Install::Admin(3)
- Author-side manager for Module::Install
- Module::Install::Admin::Include(3)
- include methods for Module::Install
- Module::Install::Admin::PMC(3)
- Author Support for Perl Compilation (.pmc)
- Module::Install::AuthorRequires(3)
- declare author-only dependencies
- Module::Install::AuthorTests(3)
- designate tests only run by module authors
- Module::Install::Base(3)
- Base class for Module::Install extensions
- Module::Install::Bundle(3)
- Bundle distributions along with your distribution
- Module::Install::Can(3)
- Utility functions for capability detection
- Module::Install::Catalyst(3), Module::Install::Catalyst(3)
- Module::Install extension for Catalyst
- Module::Install::Compiler(3)
- Commands for interacting with the C compiler
- Module::Install::Deprecated(3)
- Warnings and help for deprecated commands
- Module::Install::External(3)
- Specify dependencies on external non-Perl things
- Module::Install::FAQ(3)
- Frequently Asked Questions for Module::Install
- Module::Install::Makefile(3), Module::Install::MakeMaker(3)
- Extension Rules for ExtUtils::MakeMaker
- Module::Install::PAR(3)
- Module::Install Support for PAR::Dist packages
- Module::Install::PMC(3)
- Support for Perl Compilation (.pmc)
- Module::Install::Philosophy(3)
- The concepts behind Module::Install
- Module::Install::ReadmeFromPod(3)
- A Module::Install extension to automatically convert POD to a README
- Module::Install::Repository(3)
- Automatically sets repository URL from svn/svk/Git checkout
- Module::Install::Share(3)
- Install non-code files for use during run-time
- Module::Install::Template(3)
- Treat module source code as a template
- Module::Install::TestBase(3)
- Module::Install Support for Test::Base
- Module::Install::With(3)
- find environnement for Module::Install
- Module::Install::XSUtil(3)
- Utility functions for XS modules
- Module::Installed::Tiny(3)
- Check if a module is installed, with as little code as possible
- Module::Path(3)
- get the full path to a locally installed module
- Module::Plan::Lite(3)
- Lite installation scripts for third-party modules
- MojoMojo::Installation(3)
- Installation instructions for MojoMojo
- PDL::IFiles(3), PDL::Install::Files(3)
- -- Module for use by ExtUtils::Depends and Inline
- Perl::Critic::ThemeListing(3)
- List the themes of the installed Policies
- Perlbal::Manual::Install(3)
- Steps, dependencies and requirements to install Perlbal
- PkgConfig::LibPkgConf::Client(3)
- Query installed libraries for compiling and linking software
- RT::Client::REST::Forms(3)
- This package provides functions from RT::Interface::REST, because we don't want to depend on rt being installed. Derived from rt 3.4.5
- Religion(3)
- Generate tracebacks and create and install die() and warn() handlers
- Rex::Commands::Pkg(3)
- Install/Remove Software packages
- Spoon::Installer(3)
- Spoon Installer Class
- Statistics::Descriptive::Discrete(3)
- Compute descriptive statistics for discrete data sets. To install, use the CPAN module (https://metacpan.org/pod/Statistics::Descriptive::Discrete)
- Sub::Install(3)
- install subroutines into packages easily
- Sub::Installer(3)
- A cleaner way to install (or reinstall) package subroutines
- Sysadm::Install(3)
- Typical installation tasks for system administrators
- Task::Tiny(3)
- install a lightweight development environment
- Template::Declare::Tags(3)
- Build and install XML Tag subroutines for Template::Declare
- Template::Plugin::VMethods(3)
- install vmethods
- Test2::Require::Module(3)
- Skip tests if certain packages are not installed, or insufficient versions
- Test2::Require::Perl(3)
- Skip the test unless the necessary version of Perl is installed
- Test::DBIx::Class::FixtureCommand::Populate(3)
- Install fixtures using Populate
- Test::DBIx::Class::FixtureCommand::PopulateMore(3)
- Install fixtures using PopulateMore
- Tk::Pod::FindPods(3)
- find Pods installed on the current system
- Type::Tiny::Manual::Installation(3)
- how to install Type::Tiny
- VCP::DefaultFilters(3)
- Class for determining default filters to install for a given source and dest
- Vimana::Command::Install(3)
- install a vim plugin package
- WWW::Mechanize::Plugin::phpBB(3)
- Screen scraper for phpBB installations
- arx-install-data(1)
- Install script for Arx Fatalis game data
- bin(1), bk bin(1)
- show binary installation directory
- bk-uninstall(1), bk uninstall(1)
- uninstall BitKeeper
- blib(3)
- Use MakeMaker's uninstalled version of a package
- brlcad-config(1)
- script to get information about the installed version of BRL-CAD
- cargo-install(1)
- Build and install a Rust binary
- cargo-uninstall(1)
- Remove a Rust binary
- certbot(1)
- certbot script documentation 0.0 3.5 C usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. The most common SUBCOMMANDS and flags are: obtain, install, and renew certificates: (default) run Obtain & install a certificate in your current webserver certonly Obtain or renew a certificate, but do not install it renew Renew all previously obtained certificates that are near expiry enhance Add security enhancements to your existing configuration -d DOMAINS Comma-separated list of domains to obtain a certificate for --apache Use the Apache plugin for authentication & installation --standalone Run a standalone webserver for authentication --nginx Use the Nginx plugin for authentication & installation --webroot Place files in a server(aqs webroot folder for authentication --manual Obtain certificates interactively, or using shell script hooks -n Run non-interactively --test-cert Obtain a test certificate from a staging server --dry-run Test "renew" or "certonly" without saving any certificates to disk manage certificates: certificates Display information about certificates you have from Certbot revoke Revoke a certificate (supply --cert-name or --cert-path) delete Delete a certificate (supply --cert-name) manage your account: register Create an ACME account unregister Deactivate an ACME account update_account Update an ACME account --agree-tos Agree to the ACME server(aqs Subscriber Agreement -m EMAIL Email address for important account notifications optional arguments: -h, --help show this help message and exit -c CONFIG_FILE, --config CONFIG_FILE path to config file (default: /etc/letsencrypt/cli.ini and ~/.config/letsencrypt/cli.ini) -v, --verbose This flag can be used multiple times to incrementally increase the verbosity of output, e.g. -vvv. (default: 0) --max-log-backups MAX_LOG_BACKUPS Specifies the maximum number of backup logs that should be kept by Certbot(aqs built in log rotation. Setting this flag to 0 disables log rotation entirely, causing Certbot to always append to the same log file. (default: 1000) -n, --non-interactive, --noninteractive Run without ever asking for user input. This may require additional command line flags; the client will try to explain which ones are required if it finds one missing (default: False) --force-interactive Force Certbot to be interactive even if it detects it(aqs not being run in a terminal. This flag cannot be used with the renew subcommand. (default: False) -d DOMAIN, --domains DOMAIN, --domain DOMAIN Domain names to apply. For multiple domains you can use multiple -d flags or enter a comma separated list of domains as a parameter. The first domain provided will be the subject CN of the certificate, and all domains will be Subject Alternative Names on the certificate. The first domain will also be used in some software user interfaces and as the file paths for the certificate and related material unless otherwise specified or you already have a certificate with the same name. In the case of a name collision it will append a number like 0001 to the file path name. (default: Ask) --eab-kid EAB_KID Key Identifier for External Account Binding (default: None) --eab-hmac-key EAB_HMAC_KEY HMAC key for External Account Binding (default: None) --cert-name CERTNAME Certificate name to apply. This name is used by Certbot for housekeeping and in file paths; it doesn(aqt affect the content of the certificate itself. To see certificate names, run (aqcertbot certificates(aq. When creating a new certificate, specifies the new certificate(aqs name. (default: the first provided domain or the name of an existing certificate on your system for the same domains) --dry-run Perform a test run of the client, obtaining test (invalid) certificates but not saving them to disk. This can currently only be used with the (aqcertonly(aq and (aqrenew(aq subcommands. Note: Although --dry-run tries to avoid making any persistent changes on a system, it is not completely side-effect free: if used with webserver authenticator plugins like apache and nginx, it makes and then reverts temporary config changes in order to obtain test certificates, and reloads webservers to deploy and then roll back those changes. It also calls --pre-hook and --post-hook commands if they are defined because they may be necessary to accurately simulate renewal. --deploy- hook commands are not called. (default: False) --debug-challenges After setting up challenges, wait for user input before submitting to CA (default: False) --preferred-chain PREFERRED_CHAIN Set the preferred certificate chain. If the CA offers multiple certificate chains, prefer the chain whose topmost certificate was issued from this Subject Common Name. If no match, the default offered chain will be used. (default: None) --preferred-challenges PREF_CHALLS A sorted, comma delimited list of the preferred challenge to use during authorization with the most preferred challenge listed first (Eg, "dns" or "http,dns"). Not all plugins support all challenges. See https://certbot.eff.org/docs/using.html#plugins for details. ACME Challenges are versioned, but if you pick "http" rather than "http-01", Certbot will select the latest version automatically. (default: []) --user-agent USER_AGENT Set a custom user agent string for the client. User agent strings allow the CA to collect high level statistics about success rates by OS, plugin and use case, and to know when to deprecate support for past Python versions and flags. If you wish to hide this information from the Let(aqs Encrypt server, set this to "". (default: CertbotACMEClient/1.21.0 (certbot; OS_NAME OS_VERSION) Authenticator/XXX Installer/YYY (SUBCOMMAND; flags: FLAGS) Py/major.minor.patchlevel). The flags encoded in the user agent are: --duplicate, --force-renew, --allow-subset-of-names, -n, and whether any hooks are set. --user-agent-comment USER_AGENT_COMMENT Add a comment to the default user agent string. May be used when repackaging Certbot or calling it from another tool to allow additional statistical data to be collected. Ignored if --user-agent is set. (Example: Foo-Wrapper/1.0) (default: None) automation: Flags for automating execution & other tweaks --keep-until-expiring, --keep, --reinstall If the requested certificate matches an existing certificate, always keep the existing one until it is due for renewal (for the (aqrun(aq subcommand this means reinstall the existing certificate). (default: Ask) --expand If an existing certificate is a strict subset of the requested names, always expand and replace it with the additional names. (default: Ask) --version show program(aqs version number and exit --force-renewal, --renew-by-default If a certificate already exists for the requested domains, renew it now, regardless of whether it is near expiry. (Often --keep-until-expiring is more appropriate). Also implies --expand. (default: False) --renew-with-new-domains If a certificate already exists for the requested certificate name but does not match the requested domains, renew it now, regardless of whether it is near expiry. (default: False) --reuse-key When renewing, use the same private key as the existing certificate. (default: False) --no-reuse-key When renewing, do not use the same private key as the existing certificate. Not reusing private keys is the default behavior of Certbot. This option may be used to unset --reuse-key on an existing certificate. (default: False) --allow-subset-of-names When performing domain validation, do not consider it a failure if authorizations can not be obtained for a strict subset of the requested domains. This may be useful for allowing renewals for multiple domains to succeed even if some domains no longer point at this system. This option cannot be used with --csr. (default: False) --agree-tos Agree to the ACME Subscriber Agreement (default: Ask) --duplicate Allow making a certificate lineage that duplicates an existing one (both can be renewed in parallel) (default: False) -q, --quiet Silence all output except errors. Useful for automation via cron. Implies --non-interactive. (default: False) security: Security parameters & server settings --rsa-key-size N Size of the RSA key. (default: 2048) --key-type {rsa,ecdsa} Type of generated private key. Only *ONE* per invocation can be provided at this time. (default: rsa) --elliptic-curve N The SECG elliptic curve name to use. Please see RFC 8446 for supported values. (default: secp256r1) --must-staple Adds the OCSP Must Staple extension to the certificate. Autoconfigures OCSP Stapling for supported setups (Apache version >= 2.3.3 ). (default: False) --redirect Automatically redirect all HTTP traffic to HTTPS for the newly authenticated vhost. (default: redirect enabled for install and run, disabled for enhance) --no-redirect Do not automatically redirect all HTTP traffic to HTTPS for the newly authenticated vhost. (default: redirect enabled for install and run, disabled for enhance) --hsts Add the Strict-Transport-Security header to every HTTP response. Forcing browser to always use SSL for the domain. Defends against SSL Stripping. (default: None) --uir Add the "Content-Security-Policy: upgrade-insecure- requests" header to every HTTP response. Forcing the browser to use https:// for every http:// resource. (default: None) --staple-ocsp Enables OCSP Stapling. A valid OCSP response is stapled to the certificate that the server offers during TLS. (default: None) --strict-permissions Require that all configuration files are owned by the current user; only needed if your config is somewhere unsafe like /tmp/ (default: False) --auto-hsts Gradually increasing max-age value for HTTP Strict Transport Security security header (default: False) testing: The following flags are meant for testing and integration purposes only. --test-cert, --staging Use the staging server to obtain or revoke test (invalid) certificates; equivalent to --server https://acme-staging-v02.api.letsencrypt.org/directory (default: False) --debug Show tracebacks in case of errors (default: False) --no-verify-ssl Disable verification of the ACME server(aqs certificate. (default: False) --http-01-port HTTP01_PORT Port used in the http-01 challenge. This only affects the port Certbot listens on. A conforming ACME server will still attempt to connect on port 80. (default: 80) --http-01-address HTTP01_ADDRESS The address the server listens to during http-01 challenge. (default: ) --https-port HTTPS_PORT Port used to serve HTTPS. This affects which port Nginx will listen on after a LE certificate is installed. (default: 443) --break-my-certs Be willing to replace or renew valid certificates with invalid (testing/staging) certificates (default: False) paths: Flags for changing execution paths & servers --cert-path CERT_PATH Path to where certificate is saved (with certonly --csr), installed from, or revoked (default: None) --key-path KEY_PATH Path to private key for certificate installation or revocation (if account key is missing) (default: None) --fullchain-path FULLCHAIN_PATH Accompanying path to a full certificate chain (certificate plus chain). (default: None) --chain-path CHAIN_PATH Accompanying path to a certificate chain. (default: None) --config-dir CONFIG_DIR Configuration directory. (default: /etc/letsencrypt) --work-dir WORK_DIR Working directory. (default: /var/lib/letsencrypt) --logs-dir LOGS_DIR Logs directory. (default: /var/log/letsencrypt) --server SERVER ACME Directory Resource URI. (default: https://acme-v02.api.letsencrypt.org/directory) manage: Various subcommands and flags are available for managing your certificates: certificates List certificates managed by Certbot delete Clean up all files related to a certificate renew Renew all certificates (or one specified with --cert- name) revoke Revoke a certificate specified with --cert-path or --cert-name update_symlinks Recreate symlinks in your /etc/letsencrypt/live/ directory run: Options for obtaining & installing certificates certonly: Options for modifying how a certificate is obtained --csr CSR Path to a Certificate Signing Request (CSR) in DER or PEM format. Currently --csr only works with the (aqcertonly(aq subcommand. (default: None) renew: The (aqrenew(aq subcommand will attempt to renew any certificates previously obtained if they are close to expiry, and print a summary of the results. By default, (aqrenew(aq will reuse the plugins and options used to obtain or most recently renew each certificate. You can test whether future renewals will succeed with (ga--dry-run(ga. Individual certificates can be renewed with the (ga--cert-name(ga option. Hooks are available to run commands before and after renewal; see https://certbot.eff.org/docs/using.html#renewal for more information on these. --pre-hook PRE_HOOK Command to be run in a shell before obtaining any certificates. Intended primarily for renewal, where it can be used to temporarily shut down a webserver that might conflict with the standalone plugin. This will only be called if a certificate is actually to be obtained/renewed. When renewing several certificates that have identical pre-hooks, only the first will be executed. (default: None) --post-hook POST_HOOK Command to be run in a shell after attempting to obtain/renew certificates. Can be used to deploy renewed certificates, or to restart any servers that were stopped by --pre-hook. This is only run if an attempt was made to obtain/renew a certificate. If multiple renewed certificates have identical post- hooks, only one will be run. (default: None) --deploy-hook DEPLOY_HOOK Command to be run in a shell once for each successfully issued certificate. For this command, the shell variable $RENEWED_LINEAGE will point to the config live subdirectory (for example, "/etc/letsencrypt/live/example.com") containing the new certificates and keys; the shell variable $RENEWED_DOMAINS will contain a space-delimited list of renewed certificate domains (for example, "example.com www.example.com" (default: None) --disable-hook-validation Ordinarily the commands specified for --pre- hook/--post-hook/--deploy-hook will be checked for validity, to see if the programs being run are in the $PATH, so that mistakes can be caught early, even when the hooks aren(aqt being run just yet. The validation is rather simplistic and fails if you use more advanced shell constructs, so you can use this switch to disable it. (default: False) --no-directory-hooks Disable running executables found in Certbot(aqs hook directories during renewal. (default: False) --disable-renew-updates Disable automatic updates to your server configuration that would otherwise be done by the selected installer plugin, and triggered when the user executes "certbot renew", regardless of if the certificate is renewed. This setting does not apply to important TLS configuration updates. (default: False) --no-autorenew Disable auto renewal of certificates. (default: True) certificates: List certificates managed by Certbot delete: Options for deleting a certificate revoke: Options for revocation of certificates --reason {unspecified,keycompromise,affiliationchanged,superseded,cessationofoperation} Specify reason for revoking certificate. (default: unspecified) --delete-after-revoke Delete certificates after revoking them, along with all previous and later versions of those certificates. (default: None) --no-delete-after-revoke Do not delete certificates after revoking them. This option should be used with caution because the (aqrenew(aq subcommand will attempt to renew undeleted revoked certificates. (default: None) register: Options for account registration --register-unsafely-without-email Specifying this flag enables registering an account with no email address. This is strongly discouraged, because you will be unable to receive notice about impending expiration or revocation of your certificates or problems with your Certbot installation that will lead to failure to renew. (default: False) -m EMAIL, --email EMAIL Email used for registration and recovery contact. Use comma to register multiple emails, ex: u1@example.com,u2@example.com. (default: Ask). --eff-email Share your e-mail address with EFF (default: None) --no-eff-email Don(aqt share your e-mail address with EFF (default: None) update_account: Options for account modification unregister: Options for account deactivation. --account ACCOUNT_ID Account ID to use (default: None) install: Options for modifying how a certificate is deployed rollback: Options for rolling back server configuration changes --checkpoints N Revert configuration N number of checkpoints. (default: 1) plugins: Options for the "plugins" subcommand --init Initialize plugins. (default: False) --prepare Initialize and prepare plugins. (default: False) --authenticators Limit to authenticator plugins only. (default: None) --installers Limit to installer plugins only. (default: None) update_symlinks: Recreates certificate and key symlinks in /etc/letsencrypt/live, if you changed them by hand or edited a renewal configuration file enhance: Helps to harden the TLS configuration by adding security enhancements to already existing configuration. plugins: Plugin Selection: Certbot client supports an extensible plugins architecture. See (aqcertbot plugins(aq for a list of all installed plugins and their names. You can force a particular plugin by setting options provided below. Running --help <plugin_name> will list flags specific to that plugin. --configurator CONFIGURATOR Name of the plugin that is both an authenticator and an installer. Should not be used together with --authenticator or --installer. (default: Ask) -a AUTHENTICATOR, --authenticator AUTHENTICATOR Authenticator plugin name. (default: None) -i INSTALLER, --installer INSTALLER Installer plugin name (also used to find domains). (default: None) --apache Obtain and install certificates using Apache (default: False) --nginx Obtain and install certificates using Nginx (default: False) --standalone Obtain certificates using a "standalone" webserver. (default: False) --manual Provide laborious manual instructions for obtaining a certificate (default: False) --webroot Obtain certificates by placing files in a webroot directory. (default: False) --dns-cloudflare Obtain certificates using a DNS TXT record (if you are using Cloudflare for DNS). (default: False) --dns-cloudxns Obtain certificates using a DNS TXT record (if you are using CloudXNS for DNS). (default: False) --dns-digitalocean Obtain certificates using a DNS TXT record (if you are using DigitalOcean for DNS). (default: False) --dns-dnsimple Obtain certificates using a DNS TXT record (if you are using DNSimple for DNS). (default: False) --dns-dnsmadeeasy Obtain certificates using a DNS TXT record (if you are using DNS Made Easy for DNS). (default: False) --dns-gehirn Obtain certificates using a DNS TXT record (if you are using Gehirn Infrastructure Service for DNS). (default: False) --dns-google Obtain certificates using a DNS TXT record (if you are using Google Cloud DNS). (default: False) --dns-linode Obtain certificates using a DNS TXT record (if you are using Linode for DNS). (default: False) --dns-luadns Obtain certificates using a DNS TXT record (if you are using LuaDNS for DNS). (default: False) --dns-nsone Obtain certificates using a DNS TXT record (if you are using NS1 for DNS). (default: False) --dns-ovh Obtain certificates using a DNS TXT record (if you are using OVH for DNS). (default: False) --dns-rfc2136 Obtain certificates using a DNS TXT record (if you are using BIND for DNS). (default: False) --dns-route53 Obtain certificates using a DNS TXT record (if you are using Route53 for DNS). (default: False) --dns-sakuracloud Obtain certificates using a DNS TXT record (if you are using Sakura Cloud for DNS). (default: False) apache: Apache Web Server plugin (Please note that the default values of the Apache plugin options change depending on the operating system Certbot is run on.) --apache-enmod APACHE_ENMOD Path to the Apache (aqa2enmod(aq binary (default: None) --apache-dismod APACHE_DISMOD Path to the Apache (aqa2dismod(aq binary (default: None) --apache-le-vhost-ext APACHE_LE_VHOST_EXT SSL vhost configuration extension (default: -le- ssl.conf) --apache-server-root APACHE_SERVER_ROOT Apache server root directory (default: /etc/apache2) --apache-vhost-root APACHE_VHOST_ROOT Apache server VirtualHost configuration root (default: None) --apache-logs-root APACHE_LOGS_ROOT Apache server logs directory (default: /var/log/apache2) --apache-challenge-location APACHE_CHALLENGE_LOCATION Directory path for challenge configuration (default: /etc/apache2) --apache-handle-modules APACHE_HANDLE_MODULES Let installer handle enabling required modules for you (Only Ubuntu/Debian currently) (default: False) --apache-handle-sites APACHE_HANDLE_SITES Let installer handle enabling sites for you (Only Ubuntu/Debian currently) (default: False) --apache-ctl APACHE_CTL Full path to Apache control script (default: apache2ctl) --apache-bin APACHE_BIN Full path to apache2/httpd binary (default: None) dns-cloudflare: Obtain certificates using a DNS TXT record (if you are using Cloudflare for DNS). --dns-cloudflare-propagation-seconds DNS_CLOUDFLARE_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 10) --dns-cloudflare-credentials DNS_CLOUDFLARE_CREDENTIALS Cloudflare credentials INI file. (default: None) dns-cloudxns: Obtain certificates using a DNS TXT record (if you are using CloudXNS for DNS). --dns-cloudxns-propagation-seconds DNS_CLOUDXNS_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-cloudxns-credentials DNS_CLOUDXNS_CREDENTIALS CloudXNS credentials INI file. (default: None) dns-digitalocean: Obtain certificates using a DNS TXT record (if you are using DigitalOcean for DNS). --dns-digitalocean-propagation-seconds DNS_DIGITALOCEAN_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 10) --dns-digitalocean-credentials DNS_DIGITALOCEAN_CREDENTIALS DigitalOcean credentials INI file. (default: None) dns-dnsimple: Obtain certificates using a DNS TXT record (if you are using DNSimple for DNS). --dns-dnsimple-propagation-seconds DNS_DNSIMPLE_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-dnsimple-credentials DNS_DNSIMPLE_CREDENTIALS DNSimple credentials INI file. (default: None) dns-dnsmadeeasy: Obtain certificates using a DNS TXT record (if you are using DNS Made Easy for DNS). --dns-dnsmadeeasy-propagation-seconds DNS_DNSMADEEASY_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 60) --dns-dnsmadeeasy-credentials DNS_DNSMADEEASY_CREDENTIALS DNS Made Easy credentials INI file. (default: None) dns-gehirn: Obtain certificates using a DNS TXT record (if you are using Gehirn Infrastructure Service for DNS). --dns-gehirn-propagation-seconds DNS_GEHIRN_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-gehirn-credentials DNS_GEHIRN_CREDENTIALS Gehirn Infrastructure Service credentials file. (default: None) dns-google: Obtain certificates using a DNS TXT record (if you are using Google Cloud DNS for DNS). --dns-google-propagation-seconds DNS_GOOGLE_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 60) --dns-google-credentials DNS_GOOGLE_CREDENTIALS Path to Google Cloud DNS service account JSON file. (See https://developers.google.com/identity/protocols/ OAuth2ServiceAccount#creatinganaccount forinformation about creating a service account and https://cloud.google.com/dns/access- control#permissions_and_roles for information about therequired permissions.) (default: None) dns-linode: Obtain certificates using a DNS TXT record (if you are using Linode for DNS). --dns-linode-propagation-seconds DNS_LINODE_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 120) --dns-linode-credentials DNS_LINODE_CREDENTIALS Linode credentials INI file. (default: None) dns-luadns: Obtain certificates using a DNS TXT record (if you are using LuaDNS for DNS). --dns-luadns-propagation-seconds DNS_LUADNS_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-luadns-credentials DNS_LUADNS_CREDENTIALS LuaDNS credentials INI file. (default: None) dns-nsone: Obtain certificates using a DNS TXT record (if you are using NS1 for DNS). --dns-nsone-propagation-seconds DNS_NSONE_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-nsone-credentials DNS_NSONE_CREDENTIALS NS1 credentials file. (default: None) dns-ovh: Obtain certificates using a DNS TXT record (if you are using OVH for DNS). --dns-ovh-propagation-seconds DNS_OVH_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-ovh-credentials DNS_OVH_CREDENTIALS OVH credentials INI file. (default: None) dns-rfc2136: Obtain certificates using a DNS TXT record (if you are using BIND for DNS). --dns-rfc2136-propagation-seconds DNS_RFC2136_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 60) --dns-rfc2136-credentials DNS_RFC2136_CREDENTIALS RFC 2136 credentials INI file. (default: None) dns-route53: Obtain certificates using a DNS TXT record (if you are using AWS Route53 for DNS). --dns-route53-propagation-seconds DNS_ROUTE53_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 10) dns-sakuracloud: Obtain certificates using a DNS TXT record (if you are using Sakura Cloud for DNS). --dns-sakuracloud-propagation-seconds DNS_SAKURACLOUD_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 90) --dns-sakuracloud-credentials DNS_SAKURACLOUD_CREDENTIALS Sakura Cloud credentials file. (default: None) manual: Authenticate through manual configuration or custom shell scripts. When using shell scripts, an authenticator script must be provided. The environment variables available to this script depend on the type of challenge. $CERTBOT_DOMAIN will always contain the domain being authenticated. For HTTP-01 and DNS-01, $CERTBOT_VALIDATION is the validation string, and $CERTBOT_TOKEN is the filename of the resource requested when performing an HTTP-01 challenge. An additional cleanup script can also be provided and can use the additional variable $CERTBOT_AUTH_OUTPUT which contains the stdout output from the auth script. For both authenticator and cleanup script, on HTTP-01 and DNS-01 challenges, $CERTBOT_REMAINING_CHALLENGES will be equal to the number of challenges that remain after the current one, and $CERTBOT_ALL_DOMAINS contains a comma-separated list of all domains that are challenged for the current certificate. --manual-auth-hook MANUAL_AUTH_HOOK Path or command to execute for the authentication script (default: None) --manual-cleanup-hook MANUAL_CLEANUP_HOOK Path or command to execute for the cleanup script (default: None) nginx: Nginx Web Server plugin --nginx-server-root NGINX_SERVER_ROOT Nginx server root directory. (default: /etc/nginx or /usr/local/etc/nginx) --nginx-ctl NGINX_CTL Path to the (aqnginx(aq binary, used for (aqconfigtest(aq and retrieving nginx version number. (default: nginx) --nginx-sleep-seconds NGINX_SLEEP_SECONDS Number of seconds to wait for nginx configuration changes to apply when reloading. (default: 1) null: Null Installer standalone: Spin up a temporary webserver webroot: Place files in webroot directory --webroot-path WEBROOT_PATH, -w WEBROOT_PATH public_html / webroot path. This can be specified multiple times to handle different domains; each domain will have the webroot path that preceded it. For instance: (ga-w /var/www/example -d example.com -d www.example.com -w /var/www/thing -d thing.net -d m.thing.net(ga (default: Ask) --webroot-map WEBROOT_MAP JSON dictionary mapping domains to webroot paths; this implies -d for each entry. You may need to escape this from your shell. E.g.: --webroot-map (aq{"eg1.is,m.eg1.is":"/www/eg1/", "eg2.is":"/www/eg2"}(aq This option is merged with, but takes precedence over, -w / -d entries. At present, if you put webroot-map in a config file, it needs to be on a single line, like: webroot-map = {"example.com":"/var/www"}. (default: {}) P
- cpaninject(1)
- Inject a distribution for installation via the CPAN shell
- cpanm(1)
- get, unpack build and install modules from CPAN
- createpkg(1), createpkg (1)
- bundles a Ch Package directory for installation
- csa_query_configuration(3)
- Determine information about the installed CSA configuration
- extcheck(1)
- Detects version conflicts between a target Java Archive (JAR) file and currently installed extension JAR files
- fish-completions(1)
- Writing fish completions To specify a completion, use the complete command. complete takes as a parameter the name of the command to specify a completion for. For example, to add a completion for the program myprog, one would start the completion command with complete -c myprog ... To provide a list of possible completions for myprog, use the -a switch. If myprog accepts the arguments start and stop, this can be specified as complete -c myprog -a (aqstart stop(aq. The argument to the -a switch is always a single string. At completion time, it will be tokenized on spaces and tabs, and variable expansion, command substitution and other forms of parameter expansion will take place. fish has a special syntax to support specifying switches accepted by a command. The switches -s, -l and -o are used to specify a short switch (single character, such as -l), a gnu style long switch (such as --color) and an old-style long switch (like -shuffle), respectively. If the command (aqmyprog(aq has an option (aq-o(aq which can also be written as --output, and which can take an additional value of either (aqyes(aq or (aqno(aq, this can be specified by writing: 0.0 3.5 C complete -c myprog -s o -l output -a "yes no" P There are also special switches for specifying that a switch requires an argument, to disable filename completion, to create completions that are only available in some combinations, etc.. For a complete description of the various switches accepted by the complete command, see the documentation for the complete builtin, or write complete --help inside the fish shell. As a more comprehensive example, here(aqs a commented excerpt of the completions for systemd(aqs timedatectl: 0.0 3.5 C # All subcommands that timedatectl knows - this is useful for later. set -l commands status set-time set-timezone list-timezones set-local-rtc set-ntp # Disable file completions for the entire command # because it does not take files anywhere # Note that this can be undone by using "-F". # # File completions also need to be disabled # if you want to have more control over what files are offered # (e.g. just directories, or just files ending in ".mp3"). complete -c timedatectl -f # This line offers the subcommands # -"status", # -"set-timezone", # -"set-time" # -"list-timezones" # if no subcommand has been given so far. # # The (ga-n(ga/(ga--condition(ga option takes script as a string, which it executes. # If it returns true, the completion is offered. # Here the condition is the (ga__fish_seen_subcommands_from(ga helper function. # If returns true if any of the given commands is used on the commandline, # as determined by a simple heuristic. # For more complex uses, you can write your own function. # See e.g. the git completions for an example. # complete -c timedatectl -n "not __fish_seen_subcommand_from $commands" e -a "status set-time set-timezone list-timezones" # If the "set-timezone" subcommand is used, # offer the output of (gatimedatectl list-timezones(ga as completions. # Each line of output is used as a separate candidate, # and anything after a tab is taken as the description. # It(aqs often useful to transform command output with (gastring(ga into that form. complete -c timedatectl -n "__fish_seen_subcommand_from set-timezone" e -a "(timedatectl list-timezones)" # Completion candidates can also be described via (ga-d(ga, # which is useful if the description is constant. # Try to keep these short, because that means the user gets to see more at once. complete -c timedatectl -n "not __fish_seen_subcommand_from $commands" e -a "set-local-rtc" -d "Maintain RTC in local time" # We can also limit options to certain subcommands by using conditions. complete -c timedatectl -n "__fish_seen_subcommand_from set-local-rtc" e -l adjust-system-clock -d (aqSynchronize system clock from the RTC(aq # These are simple options that can be used everywhere. complete -c timedatectl -s h -l help -d (aqPrint a short help text and exit(aq complete -c timedatectl -l version -d (aqPrint a short version string and exit(aq complete -c timedatectl -l no-pager -d (aqDo not pipe output into a pager(aq P For examples of how to write your own complex completions, study the completions in /usr/share/fish/completions. (The exact path depends on your chosen installation prefix and may be slightly different)
- fish-doc(1)
- fish-shell Documentation This is the documentation for fish, the friendly interactive shell. A shell is a program that helps you operate your computer by starting other programs. fish offers a command-line interface focused on usability and interactive use. Unlike other shells, fish does not follow the POSIX standard, but still uses roughly the same model. Some of the special features of fish are: 0.0 (bu 2 Extensive UI: Syntax highlighting, autosuggestions, tab completion and selection lists that can be navigated and filtered. (bu 2 No configuration needed: fish is designed to be ready to use immediately, without requiring extensive configuration. (bu 2 Easy scripting: New functions can be added on the fly. The syntax is easy to learn and use. This page explains how to install and set up fish and where to get more information
- fmtinstall(3), dofmt(3), dorfmt(3), fmtprint(3), fmtvprint(3), fmtrune(3), fmtstrcpy(3), fmtrunestrcpy(3), fmtfdinit(3), fmtfdflush(3), fmtstrinit(3), fmtstrflush(3), runefmtstrinit(3), runefmtstrflush(3), errfmt(3)
- support for user-defined print formats and output routines
- fnt(1)
- download and install fonts
- g.extension(1), g.extension (1)
- Maintains GRASS Addons extensions in local GRASS installation. Downloads and installs extensions from GRASS Addons repository or other source into the local GRASS installation or removes installed extensions
- g.extension.all(1), g.extension.all (1)
- Rebuilds or removes all locally installed GRASS Addons extensions. By default only extensions built against different GIS Library are rebuilt
- gnustep-config(1)
- prints information about the current gnustep installation
- gvm-manage-certs(1)
- manage certificate infrastructure for a GVM installation
- inc::Module::Install(3)
- Module::Install configuration system
- inc::Module::Install::DSL(3)
- Domain Specific Language for Module::Install
- install(1)
- notes about Plan 9 from User Space installation
- install(5)
- Download and install node and npm
- installpkg(1), installpkg (1)
- installs a Ch Package
- instmodsh(1)
- A shell to examine installed modules
- ipsec_verify(8)
- see if the IPsec subsystem has been installed correctly
- kwalitee-metrics(1)
- list details of all kwalitee metrics installed on the system
- kwiki-install(1)
- The CGI::Kwiki installer
- lpod_test(1)
- ODF::lpOD installation test
- lv2info(1)
- print information about an installed LV2 plugin
- lv2ls(1)
- list all installed LV2 plugins
- metaclass(3)
- a pragma for installing and using Class::MOP metaclasses
- mogdelete(1)
- -- Delete keys from a MogileFS installation
- mogfetch(1)
- -- Fetch data from a MogileFS installation
- mogfileinfo(1)
- -- Fetch key metadata from a MogileFS installation
- moglistfids(1)
- -- Iterate fid/key data from a MogileFS installation
- mogtool(1)
- -- Inject/extract data to/from a MogileFS installation WARNING: this utility is deprecated! See MogileFS::Utils
- mogupload(1)
- -- Upload data to a MogileFS installation
- mpath(1)
- display the full path to a perl module (installed locally)
- npm-ci(1)
- Install a project with a clean slate
- npm-edit(1)
- Edit an installed package
- npm-explain(1)
- Explain installed packages
- npm-explore(1)
- Browse an installed package
- npm-install(1)
- Install a package
- npm-install-ci-test(1)
- Install a project with a clean slate and run tests
- npm-install-test(1)
- Install package(s) and run tests
- npm-ls(1)
- List installed packages
- npm-uninstall(1)
- Remove a package
- ompi_info(1)
- Display information about the Open MPI installation
- orte-info(1)
- Display information about the ORTE installation
- orterun(1), mpirun(1), mpiexec(1)
- Execute serial and parallel jobs in Open MPI. oshrun, shmemrun - Execute serial and parallel jobs in Open SHMEM. Note: mpirun, mpiexec, and orterun are all synonyms for each other as well as oshrun, shmemrun in case Open SHMEM is installed. Using any of the names will produce the same behavior
- perlbs2000(1)
- building and installing Perl for BS2000. This document needs to be updated, but we don't know what it should say. Please submit comments to <https://github.com/Perl/perl5/issues>
- perlivp(1)
- Perl Installation Verification Procedure
- perlmodinstall(1)
- Installing CPAN Modules
- perlos390(1)
- building and installing Perl for z/OS (previously called OS/390)
- pip(3)
- The Perl Installation Program, for scripted and third-party distribution installation
- pkg_replace(1)
- a utility for upgrading installed packages
- pkginstall(1), pkginstall (1)
- install a Ch package from the current directory
- pm_which(1)
- find installed modules
- pyi-makespec(1)
- Create a spec file for your PyInstaller project l .SH SYNOPSIS pyi-makespec <options> SCRIPT [SCRIPT ...]
- pyinstaller(1)
- Configure and build a PyInstaller project in one run l .SH SYNOPSIS pyinstaller <options> SCRIPT... pyinstaller <options> SPECFILE
- quote(3), quotestrdup(3), quoterunestrdup(3), unquotestrdup(3), unquoterunestrdup(3), quotestrfmt(3), quoterunestrfmt(3), quotefmtinstall(3), doquote(3), needsrcquote(3)
- quoted character strings
- release_handler(3)
- Unpacking and Installation of Release Packages
- rinse(8)
- RPM Installation Entity
- subfont(3), allocsubfont(3), freesubfont(3), installsubfont(3), lookupsubfont(3), uninstallsubfont(3), subfontname(3), readsubfont(3), readsubfonti(3), writesubfont(3), stringsubfont(3), strsubfontwidth(3), mkfont(3)
- subfont manipulation
- tickit_watch_cancel(3)
- remove a previously-installed callback
- tt_ptype_exists(3)
- indicate whether a ptype is already installed
- tv_find_grabbers(1)
- Find all XMLTV grabbers that are installed on the system
- virt-install(1)
- provision new virtual machines
- visp-config(1)
- get information about installed ViSP library