Tag Info

New answers tagged

1

From a practical view, info is the most detailed of three levels of reference documentation: The three levels are increasingly detailed: --help as a common command option - a short usage summary, man - the classic man pages, a "quick reference", and info - a more detailed, GNU-speciffic manual - the full, official documentation. To illustrate the ...


1

First of all, you are mistaken. Package names are decided by the package manager maintainers, not by the specific projects. For example, all Debian/deb packages are lowercase, NetworkManager package even includes a dash, network-manager, in the package name. Arch also use lowercase, but this time, without dash networkmanager. RHEL-based distros packages ...


2

This depends on the distribution. On Ubuntu, the name is not upper case: $ dpkg -l|grep -i network-manager ii network-manager 0.9.8.8-0ubuntu7 The package name is written in upper case in Fedora (and thus Red Hat, CentOS, etc.), though. This is due to the fact that the Fedora Naming Guidelines simply allow upper case package names. There are other ...


0

You could create a single directory for all history files and set HISTFILE in /etc/profile accordingly. For example HISTFILE=/var/somedir/history/${USER}_history Then you have a single location with all history files. A user can however override HISTFILE, for example in her .bashrc.


1

With zsh in emacs mode, Alt+Q or Ctrl+Q (push-line widget), pushes the current command-line on a stack (saves for later) and clears the current input buffer. Then you can enter another command, after which the last pushed command is brought back (popped from that stack).


1

If you specifically want to save the command, I usually do what Emmanuel suggested. But if you just want to enter another command before the current one, you don't need to save it. Go to the beginning of the line, enter the other command and add a semicolon. Ctrl-A cp f.txt /input/file.txt ; Enter This should execute both commands, in the order that you ...


20

Esc-# is like putting a # at the beginning and pressing Enter: Example: $ find /{,usr/}{,s}bin/ -type f -ls | awk '$3~/^...s/' | nl (Esc-#) $ #find /{,usr/}{,s}bin/ -type f -ls | awk '$3~/^...s/' | nl $ _ Works in Bash and the Korn shell.


22

Comment the line then press enter Ctrl-A # Enter so you keep the line in the history


28

Hit CTRL-U (kill line - this saves the line in the shell's kill-ring), do what you need to do, then at the new prompt, hit CTRL-Y (yank from kill-ring) to get back the original command. Alternatively, and this is particularly useful if you are in a nested command, such as a while or for loop, hit CTRL-C, which adds the command to history without executing ...


14

First of all, nobody "gets the kernel from Linus". Yes, Linus is still actively involved in the kernel's development and has final say in any disputes but he most certainly does not write it alone! The wikipedia page on the Linux kernel is quite good on the subject: The kernel changes made in year 2007 have been submitted by no less than 1900 developers ...


17

The distro kernels are all compiled from the official source, with distro specific patches applied. These patches are relatively minor compared to the scope of the kernel itself. As long as you know what you are doing, you can substitute a custom kernel into any of the mainstream distros, although this is discouraged since it may cause a mismatch with ...



Top 50 recent answers are included