New answers tagged


When in doubt about whether a command is a Bash builtin, an executable file, both, or something else: $ type -a kill kill is aliased to `echo 'You should not use kill - use OUPMclient -K instead.';' kill is a shell builtin kill is /usr/bin/kill kill is /bin/kill This is an peculiar example, since our provider wants us to use some other command rather than ...


ulimit and disown are Bash built in functions and those don't have a manpage of its own but are described in the Bash manpage. If you are running bash you can use the help command, e.g.: $ help disown You may want to pipe the output into less so you can scroll and search, e.g. $ help disown | less


When you type help you see the commands that are built in bash. To see help for these commands type help <command>: help ulimit help disown When you use man (short for manual), you display help for binary programs that are not part of bash. These are separate programs that bash executes them when you type the command. You noticed that you get the ...


disown is a bash built in. So man bash will show ... disown [-ar] [-h] [jobspec ...] Without options, remove each jobspec from the table of active jobs. If jobspec is not present, and neither the -a nor the -r option is supplied, the current job is used. If the -h option is given, each jobspec ...


As already discussed it isn't recommended to do so - the other post explain as well that it is possible nevertheless. I would like to mention some alternatives - software projects offering some kind of user-editable cheat-sheets cheat cheats cheat (bash) tldr cheat (golang) Most of them come with a good preset of cheat-sheets, which you then enhance on ...


Yes, you can, but it isn't recommended. The best approach would probably be something like the tool Rinzwind suggested, but yes, you can also do it manually. I will use the man page for grep as an example. Man pages are compressed files so you either need to use a real editor, like emacs, that can read/write compressed files, or you must first uncompress ...


Install gmanedit. Gtk+ Manpages Editor is an editor for man pages that runs on X with GTK+. Gmanedit is an application which allows you to edit manual pages (man) on Linux/Unix systems. It is like most common HTML editors but more easy. You need to know manpages format.


Square braces [...] mean that their content is optional and can either be added to the command or not. Curly brackets containing pipe-separated items { ... | ... } mean that you must specify one of those items. Example: my_command [--optional-argument] { --either-this | --or-that } Given the syntax above, you have those options to call the command: ...


Taken from this handy guide, Some options will have a limited list of choices. A list of choices will be comma seperated and put between braces. {choice1,choice2} {yes,no} Where you have -P { cpu [,...] | ON | ALL }, it means you must choose one of the following options. The [,...] part means that you can supply a comma separated list.


Command syntax is given in a form that is a bit like Backus-Naur notation, described here. The braces group together two or more options, one of which must be specified. In the case of -I { keyword [,...] | ALL }, that means you either specify keyword [,...] or ALL.


The man pages and man tool simply need be installed, and you need to be running the command within the chroot after doing sudo chroot . inside its root directory. If man pages aren't working, then likely there is some other underlying issue, such as the files have somehow been removed from disk. I just tested here on my Nexus 4, and man ls in the chroot ...

Top 50 recent answers are included