bd – Quickly Go Back to a Parent Directory Instead of Typing “cd ../../..” Redundantly

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.95/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Aaron Kili

Aaron Kili is a Linux and F.O.S.S enthusiast, an upcoming Linux SysAdmin, web developer, and currently a content creator for TecMint who loves working with computers and strongly believes in sharing knowledge.

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

16 Responses

  1. Jesse says:

    Why ignore the github.com ssl certificate?

    • Aaron Kili says:

      @Jesse

      That is the command given on the official Github repository for the installation, try to check it.

    • Vigneshwaran says:

      Hi Jesse! I’m the author. Long time back, Github had issues with their certificate so I had to change the instructions to ignore it so wget would be able to download the file.

      You can also just copying the contents file and write to /usr/local/bin/bd using an editor like vim. :)

  2. Jouni "rautamiekka" Järvinen says:

    The backticks are obsoleted by §$(…)§ which supports nesting of commands.

  3. hackel says:

    No Do *not* install user files in /usr/bin! This is terrible advice. Put it in /usr/local/bin (that’s what it’s there for), or add a user dir like ~/.local/bin to your $PATH.

  4. Michael Eager says:

    A simpler version of this, which just steps up one level in the directory tree is:

    alias ..='cd ..;ls'
    

    This creates a command “..” which goes back one directory and does an “ls”. I use it all the time.

  5. Bill says:

    Please don’t suggest using wget –no-check-certificate, that should only be for internal/local use where you can be confident of no MITM attacks.

    Also, when not using your Linux package manager to install a program, you should not be using /usr/bin. For a single user you can install to a folder in your home directory like ~/bin (and add that to your $PATH). Or to make it available to all users of a system you can use /usr/local/bin.

    Never download files as root. Instead of using `sudo wget` you should use wget as a normal user, check the contents of the file and then use sudo to install it to the desired location (here /etc/bash_completion.d/bd).

    Also, there’s no need to use `sudo source` and I’m not sure it would even work. Instead just use `source` as the current user.

    You have responsibilities as a technical writer to give good examples without creating potential security issues for your readers. Please think carefully about commands given in examples.

    • Aaron Kili says:

      @Bill

      Yes, it is always good to share with you guys and receive useful feedback like this. We will consider all you have stressed out here. Many thanks for the heads up.

      • Flurrywinde says:

        Yes, ‘sudo source‘ does not work. Also, you show wget being used to writing the file into /usr/bin/. This needs a sudo (but like Bill says, it shouldn’t be in /usr/bin/ and should be d/led and checked first). Also, looking at the github for bd, it seems it can be installed via a package manager now: https://github.com/vigneshwaranr/bd/issues/32

        Otherwise, thanks for posting this article. `bd` will prove very valuable to me. Thanks!

  6. Raymond Herrera says:

    This command is really cool! I am going to install it right away. This is an excellent opportunity to remind the colleagues out there about a related set of commands: “pushd” and “popd“.

    Thanks and keep up the good work!

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *