funny linux commands
Thread Starter
Moderator


Joined: Feb 2009
Posts: 11,732
Likes: 5
From: Leesville, Louisiana
Vehicle: 2001 Hyundai Tiburon
<div class='codetop'>CODE</div><div class='codemain'>adam@adam-desktop:~$ nice man woman
No manual entry for woman
adam@adam-desktop:~$ [ Where is Obamas birth certificate?
bash: [: missing `]'</div>
Watch star wars
<div class='codetop'>CODE</div><div class='codemain'>telnet towel.blinkenlights.nl</div>
custom banner
<div class='codetop'>CODE</div><div class='codemain'>adam@adam-desktop:~$ banner Hyundai
# #
# # # # # # # # ##### ## #
# # # # # # ## # # # # # #
####### # # # # # # # # # # #
# # # # # # # # # # ###### #
# # # # # # ## # # # # #
# # # #### # # ##### # # #</div>
aptitude -h
the last line states that This aptitude does not have Super Cow Powers.
<div class='codetop'>CODE</div><div class='codemain'>adam@adam-desktop:~$ apt-get moo
(__)
(oo)
/------\/
/ | ||
* /\---/\
~~ ~~
...."Have you mooed today?"...</div>
<div class='codetop'>CODE</div><div class='codemain'>adam@adam-desktop:~$ aptitude moo
There are no Easter Eggs in this program.
adam@adam-desktop:~$ aptitude -v moo
There really are no Easter Eggs in this program.
adam@adam-desktop:~$ aptitude -v -v moo
Didn't I already tell you that there are no Easter Eggs in this program?
adam@adam-desktop:~$ aptitude -v -v -v moo
Stop it!
adam@adam-desktop:~$ aptitude -v -v -v -v moo
Okay, okay, if I give you an Easter Egg, will you go away?
adam@adam-desktop:~$ aptitude -v -v -v -v -v moo
All right, you win.
/----\
-------/ \
/ \
/ |
-----------------/ --------\
----------------------------------------------</div>
If you type apt-get --help the last line says This APT has Super Cow Powers.
You can turn your desktop into a aquarium by pressing alt+F2 and typing "free the fish" in the run box.
You can get some pretty crazy manual pages for use with the man command by typing the following<div class='codetop'>CODE</div><div class='codemain'>sudo apt-get install funny-manpages</div>
<div class='codetop'>CODE</div><div class='codemain'>
adam@adam-desktop:~$ man baby
NAME
baby - create new process from two parents
SYNOPSIS
baby -sex [m|f] [-name name]
DESCRIPTION
baby is initiated when one parent process polls another server process
through a socket connection in the BSD version or through pipes in the
System V implementation. baby runs at low priority for approximately
forty weeks and then terminates with a heavy system load. Most systems
require constant monitoring when baby reaches its final stages of exe_
cution.
Older implementations of baby did not require both initiating processes
to be present at the time of completion. In those versions the initi_
ating process which was not present was awakened and notified of the
results upon completion. It has since been determined that the pres_
ence of both parent processes result in a generally lower system load
at completion, and thus current versions of baby expect both parent
processes to be active during the final stages.
Successful completion of baby results in the creation and naming of a
new process. Parent processes then broadcast messages to all other
processes, local and remote, informing them of their new status.
OPTIONS
-sex define the gender of the created process
-name assign the name name to the new process
EXAMPLES
baby -sex f -name Jacqueline
completed successfully on July 9, 1992 at 9:11pm. Jacqueline's vital
statistics: 8 pounds 3 oz, 20 inches, long dark hair. The parent pro_
cess, Kim Dunbar, is reportedly doing fine.
SEE ALSO
cigar(6), dump(5), cry(3).
BUGS
Despite its complexity, baby only knows one signal, SIGCHLD, (or SIGCLD
in the System V implementation), which it uses to contact the parent
processes. One or both parent processes must then inspect the baby
process to determine the cause of the signal.
The sleep(1) command may not work as expected on either parent process
for some time afterward, as each new instance of baby sends intermit_
tent signals to the parent processes which must be handled by the par_
ents immediately.
A baby process will frequently dump core, requiring either or both par_
ent processes to clean up after it.
Despite the reams of available documentation on invoking and maintain_
ing baby, most parent processes are overwhelmed.
AUTHORS
From a man page by Joe Beck, .</div>
There's a ton of others too..
<div class='codetop'>CODE</div><div class='codemain'>adam@adam-desktop:~$ csh
% "How would you rate Obama's failure
Unmatched ".
% [ Where is RDTiburon.com
[: missing `]
% [ got a light?
[: No match.
% man: Why did you get a divorce?
man:: Too many arguments.
% !:say, did you know I slept with the substitute teacher?
Bad substitute.
% %blow
%blow: No such job.
% \(-
(-: Command not found.</div>
No manual entry for woman
adam@adam-desktop:~$ [ Where is Obamas birth certificate?
bash: [: missing `]'</div>
Watch star wars
<div class='codetop'>CODE</div><div class='codemain'>telnet towel.blinkenlights.nl</div>
custom banner
<div class='codetop'>CODE</div><div class='codemain'>adam@adam-desktop:~$ banner Hyundai
# #
# # # # # # # # ##### ## #
# # # # # # ## # # # # # #
####### # # # # # # # # # # #
# # # # # # # # # # ###### #
# # # # # # ## # # # # #
# # # #### # # ##### # # #</div>
aptitude -h
the last line states that This aptitude does not have Super Cow Powers.
<div class='codetop'>CODE</div><div class='codemain'>adam@adam-desktop:~$ apt-get moo
(__)
(oo)
/------\/
/ | ||
* /\---/\
~~ ~~
...."Have you mooed today?"...</div>
<div class='codetop'>CODE</div><div class='codemain'>adam@adam-desktop:~$ aptitude moo
There are no Easter Eggs in this program.
adam@adam-desktop:~$ aptitude -v moo
There really are no Easter Eggs in this program.
adam@adam-desktop:~$ aptitude -v -v moo
Didn't I already tell you that there are no Easter Eggs in this program?
adam@adam-desktop:~$ aptitude -v -v -v moo
Stop it!
adam@adam-desktop:~$ aptitude -v -v -v -v moo
Okay, okay, if I give you an Easter Egg, will you go away?
adam@adam-desktop:~$ aptitude -v -v -v -v -v moo
All right, you win.
/----\
-------/ \
/ \
/ |
-----------------/ --------\
----------------------------------------------</div>
If you type apt-get --help the last line says This APT has Super Cow Powers.
You can turn your desktop into a aquarium by pressing alt+F2 and typing "free the fish" in the run box.
You can get some pretty crazy manual pages for use with the man command by typing the following<div class='codetop'>CODE</div><div class='codemain'>sudo apt-get install funny-manpages</div>
<div class='codetop'>CODE</div><div class='codemain'>
adam@adam-desktop:~$ man baby
NAME
baby - create new process from two parents
SYNOPSIS
baby -sex [m|f] [-name name]
DESCRIPTION
baby is initiated when one parent process polls another server process
through a socket connection in the BSD version or through pipes in the
System V implementation. baby runs at low priority for approximately
forty weeks and then terminates with a heavy system load. Most systems
require constant monitoring when baby reaches its final stages of exe_
cution.
Older implementations of baby did not require both initiating processes
to be present at the time of completion. In those versions the initi_
ating process which was not present was awakened and notified of the
results upon completion. It has since been determined that the pres_
ence of both parent processes result in a generally lower system load
at completion, and thus current versions of baby expect both parent
processes to be active during the final stages.
Successful completion of baby results in the creation and naming of a
new process. Parent processes then broadcast messages to all other
processes, local and remote, informing them of their new status.
OPTIONS
-sex define the gender of the created process
-name assign the name name to the new process
EXAMPLES
baby -sex f -name Jacqueline
completed successfully on July 9, 1992 at 9:11pm. Jacqueline's vital
statistics: 8 pounds 3 oz, 20 inches, long dark hair. The parent pro_
cess, Kim Dunbar, is reportedly doing fine.
SEE ALSO
cigar(6), dump(5), cry(3).
BUGS
Despite its complexity, baby only knows one signal, SIGCHLD, (or SIGCLD
in the System V implementation), which it uses to contact the parent
processes. One or both parent processes must then inspect the baby
process to determine the cause of the signal.
The sleep(1) command may not work as expected on either parent process
for some time afterward, as each new instance of baby sends intermit_
tent signals to the parent processes which must be handled by the par_
ents immediately.
A baby process will frequently dump core, requiring either or both par_
ent processes to clean up after it.
Despite the reams of available documentation on invoking and maintain_
ing baby, most parent processes are overwhelmed.
AUTHORS
From a man page by Joe Beck, .</div>
There's a ton of others too..
<div class='codetop'>CODE</div><div class='codemain'>adam@adam-desktop:~$ csh
% "How would you rate Obama's failure
Unmatched ".
% [ Where is RDTiburon.com
[: missing `]
% [ got a light?
[: No match.
% man: Why did you get a divorce?
man:: Too many arguments.
% !:say, did you know I slept with the substitute teacher?
Bad substitute.
% %blow
%blow: No such job.
% \(-
(-: Command not found.</div>




