dirty UNIX humor

Hey, baby, wanna give me a cronjob?

Mainframers are typically impotent to help when there’s a problem with a Unix server. Essentially, mainframers are all Unix eunuchs.

Ah, you get the point…
O


vidi vici veni!

You know… when you are trying to recall something and hear in your head: “parity error at address…”

:slight_smile:

You know how some users like to set their home directory to /? You know how some deluser utilities like to “clean up” by rm -rf’ing the user’s home directory? I was wondering why it was taking so long.

And then god said “rm r*”, and all was null and void. :slight_smile:

HAHAHAHAHAHA!!! ::mental note to self: harass CS friends with this next time you log on::

Ye gad. :rolleyes:


/devnull

I always twinge when I see a parent fork a child…process that is…
And then I feel remorse when I have to kill all the children. :wink:

DISCLAIMER (to non-Unix users): (All comments above are UNIX terms and are not in anyway referring to what your dirty mind thought they were)

export NAMES=“Audreyk techchick68 eve aenea”

make $NAMES


Who is this General Failure character?
And why is he reading my hard drive?

Why do Unix users always type cryptic, tedious code at the prompt?
They just don’t get the point (and click)!

Yes, but that’s a dirty C story, any sailor would know that.

Let’s not forget these pesky database apps that frequently fork a backend.

And as I am terribly forgetful, I often also find myself running:

man mount

( much to the chagrin of the other people in the computer room :eek: )

#ifdef NON_UNIX_FOLK
#include <disclaimer_from_above>
#endif