Prev |  | Next

## 4. Download information

This section presents the different methods to download NUT.

### 4.1. Source code

### Note

You should always use PGP/GPG to verify the signatures before using any source code.

You can use the following procedure. to do so.

#### Stable tree: 2.8

- ChangeLog

You can also browse the stable source directory.

#### Development tree:

##### Code repository

The development tree is available through a Git repository hosted at GitHub.

To retrieve the current development tree, use the following command:

    :; git clone git://github.com/networkupstools/nut.git

OPTIONALLY you can then fetch known git tags, so semantic versions look better (based off a recent release):

    :; cd nut
    :; git fetch --tags --all

The `configure` script and its dependencies are not stored in Git. To generate them, ensure that autoconf, automake and libtool are installed, then run the following script in the directory you just checked out:

    :; ./autogen.sh

### Note

it is optionally recommended to have Python 2.x or 3.x, and Perl, to generate some files included into the `configure` script, presence is checked by autotools when it is generated. Neutered files can be just "touched" to pass the `autogen.sh` if these interpreters are not available, and effectively skip those parts of the build later on —`autogen.sh` will then advise which special environment variables to `export` in your situation and re-run it.

Then refer to the NUT user manual for more information.

##### Browse code

You can browse the "vanilla NUT" code at the Main GitHub repository for NUT sources, and some possibly modified copies as part of packaging recipe sources of operating system distributions, as listed below.

##### Snapshots

GitHub has several download links for repository snapshots (for particular tags or branches), but you will need a number of tools such as autoconf, automake and libtool to use these snapshots to generate the `configure` script and some other files.

After you `configure` the source workspace, a `make dist-hash` recipe would create the snapshot tarballs which do not require the auto* tools, and their checksum files, such as those available on the NUT website and attached to GitHub Releases page.

#### Older versions

Browse source directory

### 4.2. Binary packages

### Note

The only official releases from this project are source code.

NUT is already available in the following operating systems (and likely more):

- Repology report on NUT lists 745 entries about NUT, as of this writing

- Linux:

  - 42ITy.org packaging recipes for Debian-based releases
  - Debian Salsa recipes and Debian packages
  - Ubuntu packages
  - Fedora Rawhide recipes and Red Hat / Fedora packages
  - Arch Linux recipe and Arch Linux package info
  - Gentoo Linux recipe and Gentoo Linux package info
  - Novell SUSE / openSUSE official package base recipe and Novell SUSE / openSUSE official package development recipe, and Novell SUSE / openSUSE official package overview
  - Numerous other recipes on Open Build System (not only by SUSE)
  - OpenWRT recipes
  - Slackware package overview
  - Void Linux recipes

- BSD systems:

  - FreeBSD package recipe (devel), FreeBSD package recipe and FreeBSD package overview
  - NetBSD recipe and NetBSD package overview
  - OpenBSD recipe
  - FreeNAS iocage-ports recipe, FreeNAS 9.3 docs on UPS integration and FreeNAS 11.3-U5 docs on UPS integration

- Mac OS X:

  - Fink recipe and Fink package overview
  - MacPorts recipe

- illumos/Solaris:

  - OpenIndiana oi-userland recipe and OpenIndiana latest rolling builds

- Windows (complete port, Beta):

  - Current regular CI builds are available as tarballs with binaries from Appveyor CI— but it may be difficult to locate specifically the master-branch builds. See NUT for Windows wiki article for these details, and more.

    The latest release’s automated build archive is available here: * (OBSOLETE) Windows MSI installer 2.6.5-6

### 4.3. Java packages

- The jNut package has been split into its own GitHub repository.
- NUT Java support (client side, Beta) jNUT 0.2-SNAPSHOT
- NUT Java Web support (client side using REST, Beta) jNutWebAPI 0.2-SNAPSHOT (sources)

### 4.4. Virtualization packages

#### VMware

- NUT client for VMware ESXi (several versions of both; offsite, by René Garcia). Since the hypervisor manager environment lacks access to hardware ports, this package only includes the `upsmon` client integration, and a NUT server must run in a VM with passed-through ports.

  See NUT and VMware (ESXi) page on NUT Wiki for more community-contributed details.

  Note that the VIB package versioning is independent of NUT or VMware versions, they are however mentioned in downloadable file names. As of this writing, there are builds spanning VMware ESXi 5.0-8.0 and NUT 2.7.4-2.8.0.

  ### Warning

  This module is provided "as is" and is not approved by VMware, you may lose VMware support if you install it. Use it at your own risks.

  - GitHub repository with build recipes, including binary releases
  - Original blog entry (French)
  - Historic details of the recipe evolution
  - VIB package (in fact automatically redirects to latest build)

Prev |  | Next
| Home |