Tag Info

New answers tagged


Adding to heemayl's answer, it's worth pointing out that fg, bg, and jobs have to be built into the shell, because they manipulate data structures in the shell's memory and/or the kernel state associated with the shell's process. It would not be possible to write an external command that does what fg does. Other commands that have to be built in include ...


You are not getting any files against those commands because they are shell (bash) built-ins, not separate executable files (e.g. binary files, scripts). Actually, shell built-ins are compiled into the shell executable; if you want you can check the source code to be sure of it. As which or whereis only looks for external executable files, you are not ...


This are shell builtin commands. There is no binary for them as they are a part of Bash (or whatever shell you are using). They are documented for example in the Bash manpage (see the section "SHELL BUILTIN COMMANDS")


They are shell built-ins - you can get basic usage information by typing help fg or help jobs at the bash shell prompt, or more detailed information from the bash manpage.


fg, bg and jobs are not separate utilities, but they are part of bash(shell builtin commands). you can find more about them in bash manual using the command man bash


Seems there is a bug in ubuntu 14.04.1 ~$ apt-cache policy docker.io docker.io: Installed: (none) Candidate: 1.0.1~dfsg1-0ubuntu1~ubuntu0.14.04.1 Version table: 1.0.1~dfsg1-0ubuntu1~ubuntu0.14.04.1 0 500 http://cz.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 100 /var/lib/dpkg/status 0.9.1~dfsg1-2 0 ...


If you have installed "Docker" with the following command sudo apt-get install docker.io the man pages can be viewed with man docker Even if you have installed "Docker" with these instructions the man pages can be viewed with man docker With this command, you see the files installed for the man pages: dpkg-query -L <package_name> | grep ...


dman Retrieves Manual Pages In practice, viewing a package's brief description (as mchid suggests) is usually what you'll want to see, to decide if you want the package. However, if you like you can view a manpage provided by a package that has not yet been installed, using the dman utility. dman is provided by the bikeshed package. You can install that ...


In my Opinion you can't read the documentation without installing the package. when you install any specific package you may have noticed some additional files also gets installed one of which is named as 'man-db' or something similar. This 'man-db' actually contains the manual documentation about the package. but you can see some basic details of the ...


not as extensive as manpages but I think this is what you are looking for: apt-cache show <packagename> you can also search for related packages: apt-cache search <searchtag>

Top 50 recent answers are included