Check These Out
$PRIVATEKEY - Of course the full path to the private key \n
$HOST - The host where to get the backup \n
$SOURCE - The directory you wish to backup \n
$DESTINATION - The destination for the backup on your local machine
Shows the UUID of a filesystem or partition that can be used in kernel root options and in fstab.
Run it without the -u option to generate more information. eg:
~/ sudo vol_id /dev/sda2
ID_FS_USAGE=other
ID_FS_TYPE=swap
ID_FS_VERSION=2
ID_FS_UUID=27fca13d-97b7-4d28-882c-6d03353f0a82
ID_FS_UUID_ENC=27fca13d-97b7-4d28-882c-6d03353f0a82
ID_FS_LABEL=
ID_FS_LABEL_ENC=
When using reverse-i-search you have to type some part of the command that you want to retrieve. However, if the command is very complex it might be difficult to recall the parts that will uniquely identify this command. Using the above trick it's possible to label your commands and access them easily by pressing ^R and typing the label (should be short and descriptive).
UPDATE:
One might suggest using aliases. But in that case it would be difficult to change some parts of the command (such as options, file/directory names, etc).
Same as the other rtfm's, but using the more correct xdg-open instead of $BROWSER.
I can't find a way to open info only if the term exists, so it stays out of my version.
This is a (last resort) way to automate applications that provide no other ways for automation, it would send 'Hello world' to the currently active window. See the manpage (and the -text and -window entries) for how to send special characters and target specific windows.
An example:
Using xwininfo, I get the id of my XPlanet background window:
alanceil@kvirasim:19:51:0:~> xwininfo
xwininfo: Please select the window about which you
would like information by clicking the
mouse in that window.
xwininfo: Window id: 0x3600001 "Xplanet 1.2.0"
Absolute upper-left X: 0
(..etc..)
Now I use xvkbd to tell it to close itself:
xvkbd -xsendevent -window 0x3600001 -text "Q"
Obviously, the best way is to put these commands in a shellscript - just make sure to include a short sleep (sleep .1 should suffice) after each xvkbd call, or some programs will become confused.