bottom

Table of contents

• Features
• Support
• Installation
  • Cargo
  • Arch Linux
  • Debian/Ubuntu
  • Snap
  • Fedora/CentOS
  • Gentoo
  • Nix
  • Solus
  • Homebrew
  • MacPorts
  • Scoop
  • Chocolatey
  • winget
  • Manual installation
  • Binaries
    • Auto-completion
• Usage
• Configuration
• Troubleshooting
• Contribution
  • Contributors
• Thanks

Features

As (yet another) process/system visualization and management application, bottom supports the typical features:

• Graphical visualization widgets for:

  • CPU usage over time, at an average and per-core level
  • RAM and swap usage over time
  • Network I/O usage over time

  with support for zooming in/out the current time interval displayed.

• Widgets for displaying info about:

  • Disk capacity/usage
  • Temperature sensors
  • Battery usage

• A process widget for displaying, sorting, and searching info about processes, as well as support for:

  • Kill signals
  • Tree mode

• Cross-platform support for Linux, macOS, and Windows, with more planned in the future.

• Customizable behaviour that can be controlled with command-line flags or a config file, such as:

  • Custom and pre-built colour themes
  • Changing the default behaviour of some widgets
  • Changing the layout of widgets
  • Filtering out entries in disk and temperature widgets

• Some other nice stuff, like:

  • An htop-inspired basic mode
  • Expansion, which focuses on just one widget

• And more!

You can find more details in the documentation.

Support

bottom officially supports the following operating systems and corresponding architectures:

• macOS (x86_64)
• Linux (x86_64, i686, aarch64)
• Windows (x86_64, i686)

These platforms are tested to work for the most part and issues on these platforms will be fixed if possible.
Furthermore, binaries are expected to be built and tested using the most recent version of stable Rust.

For more details on known problems and unsupported platforms, feel free to check out the documentation page on support.

Installation

Cargo

Installation via cargo is done by installing the bottom crate:

# If required, update Rust on the stable channel
rustup update stable
cargo install bottom --locked
# Alternatively, --locked may be omitted if you wish to not used locked dependencies:
cargo install bottom

Arch Linux

There is an official package that can be installed with pacman:

sudo pacman -Syu bottom

Debian/Ubuntu

A .deb file is provided on each release (currently only for x86-64):

curl -LO https://github.com/ClementTsang/bottom/releases/download/0.6.8/bottom_0.6.8_amd64.deb
sudo dpkg -i bottom_0.6.8_amd64.deb

For ARM (aarch64 and armv7), .deb builds are currently available for the 0.6.8 release and nightly builds.

Snap

bottom is available as a snap:

sudo snap install bottom
# To allow the program to run as intended
sudo snap connect bottom:mount-observe
sudo snap connect bottom:hardware-observe
sudo snap connect bottom:system-observe
sudo snap connect bottom:process-control

Fedora/CentOS

Available in COPR:

sudo dnf copr enable atim/bottom -y
sudo dnf install bottom

Gentoo

Available in GURU and dm9pZCAq overlays:

sudo eselect repository enable guru
sudo emerge --sync guru
echo "sys-process/bottom" | sudo tee /etc/portage/package.accept_keywords/10-guru
sudo emerge sys-process/bottom::guru

or

sudo eselect repository enable dm9pZCAq
sudo emerge --sync dm9pZCAq
sudo emerge sys-process/bottom::dm9pZCAq

Nix

nix-env -i bottom

Solus

sudo eopkg it bottom

Homebrew

brew install bottom

MacPorts

sudo port selfupdate
sudo port install bottom

Scoop

scoop install bottom

Chocolatey

Choco package located here.
Since validation of the package takes time, it may take a while to become available after a release.

choco install bottom
# The version number may be required for newer releases during the approval process:
choco install bottom --version=0.6.8

winget

You can find the packages here:

winget install bottom
# Alternatively
winget install Clement.bottom

You can also manually do the same thing by going to the latest release
and installing via the .msi file.

You can uninstall via Control Panel, Options, or winget --uninstall bottom.

Manual installation

There are a few ways to go about doing this manually. Note that you probably want
to do so using the most recent version of stable Rust, which is how the binaries are built:

# If required, update Rust on the stable channel first
rustup update stable
# Option 1 - Download from releases and install
curl -LO https://github.com/ClementTsang/bottom/archive/0.6.8.tar.gz
tar -xzvf 0.6.8.tar.gz
cargo install --path .
# Option 2 - Clone from master and install manually
git clone https://github.com/ClementTsang/bottom
cd bottom
cargo install --path .
# Option 3 - Clone and install directly from the repo all via Cargo
cargo install --git https://github.com/ClementTsang/bottom

Binaries

You can also try to use the generated release binaries and manually install on your system:

• Latest stable release, generated off of the release branch
• Latest nightly release, generated daily off of the master branch at 00:00 UTC

Auto-completion

The release binaries are packaged with shell auto-completion files for bash, fish, zsh, and Powershell. To install them:

• For bash, move btm.bash to $XDG_CONFIG_HOME/bash_completion or /etc/bash_completion.d/.
• For fish, move btm.fish to $HOME/.config/fish/completions/.
• For zsh, move _btm to one of your $fpath directories.
• For PowerShell, add . _btm.ps1 to your PowerShell
  profile.

Usage

You can run bottom using btm.

• For help on flags, use btm -h for a quick overview or btm --help for more details.
• For info on key and mouse bindings, press ? inside bottom or refer to the documentation.

You can find more information on usage in the documentation.

Configuration

bottom accepts a number of command-line arguments to change the behaviour of the application as desired. Additionally, bottom will automatically
generate a configuration file on the first launch, which one can change as appropriate.

More details on configuration can be found in the documentation.

Troubleshooting

If some things aren't working, give the Troubleshooting page a look. If things still aren't
working, then consider asking a question by opening a question or filing a bug report.

Contribution

Whether it's reporting bugs, suggesting features, maintaining packages, or submitting a PR,
contribution is always welcome! Please read CONTRIBUTING.md for details on how to
contribute to bottom.

Contributors

Thanks to all contributors:

Thanks

• This project is very much inspired by gotop,
  gtop, and htop.

• This application was written with many, many libraries, and built on the
  work of many talented people. This application would be impossible without their
  work. I used to thank them all individually but the list got too large...

• And of course, another round of thanks to all contributors and package maintainers!