The Life explained from Linux point of view
Yet another portion of philosophy. If you are not interested, don't read or comment this entry.
Source: http://web31337.org/life-as-in-linux.html
Duplicated here.
Most of us wondering "what is Life? How to deal with it?" I will try to give you an answer on this topic.
I came back to these thoughs yesterday, when I was looking through Durian Open Movie project, a movie that is going to be done with Blender opensource rendering software.
I've been expecting battle scenes in movie. I was as well expecting they won't take a main part in the movie and won't be so violent. Probably I was wrong.
The first post I addressed to developers team I blogged @ LQ: Violence in movies & books - how far is this going?
Of course, as I expected almost noone took that seriously.
Now I'm here to tell you a story you might believe or not: it's completely your choice. Most of readers who uses Linux/UNIX-like OS will clearly understand what is written below.
Let's just start with a system overview. We are now running as /proc/self/ on a shared system.
Here's our typical command prompt, most of us are quite familiar with it:
That was a tiny part of FQDN of earth system. I cut it to 5 last levels including localhost. FQDN is based on sources of energy, so that is why it outputs in that weird form as you might thought.
Read 'man earth' to find out it's actual FQDN, limited to few hundreds of levels from localhost. It was never written anywhere, we actually don't know our system's exact FQDN, if you enter 'hostname -f' you may cause temporary buffer overflow in /proc/self/, don't do that.
Refer to 'man kill' and 'man portal' if you want to find out FQDN of earth: there is no enough space in most of processes allocated memory space to store that. I say again: don't do that in your current life form. And don't tell me I didn't warn you.
Remembering that we are processes working in a shared system we must follow quite simple guide to keep it safe.
Everytime you do something, the kernel allocates you a memory and resources, required to perform it. Action can be anything. We are not root and we cannot login as root but every user is added in /etc/sudoers, so we can issue any command by running it with sudo like we are root.
Many processes running in this system abuse this sudo privilege, and, as a result, there are unforeseen consequences, as was perfectly noticed by G-Man in a well-known computer game Half-Life.
Most of users never really read or pay required attention to a sudo note:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
What is certainly, causing all the problems, currently present in earth system. Those are (un)expected killall or kill (wars) calls by kernel or some very malicious process, those are (un)predictable kernel BOFs or other issues, which usually result in some devices failure(disasters), causing all processes are bound to it be killed or damaged, those are writing over some other processes working memory set(hate,fear).
Please notice that everything decribed here also could happen without sudo usage. For instance...
Most abused command is, of course, echo. Even when it's not sudo'ed it still causes many many troubles, when it goes to kernel(kernel collets each process output, mark that). After that, kernel begins to act in a weird way, when there is too many garbage and evil output, as it was mentioned before, resulting in different disasters. Please, use echo wisely, /proc/self/ !
One of other most abused commands(in fact is an alias to 'echo -silent', read 'man echo', real-life 'echo' is different) is 'thought'. Yes, dreams and thoughts. They actually work the same way echo does, but these are held much more careful by kernel. Each of those acts much harder than thousands of plain echo's. Keep that in mind, /proc/self/ and filter your input to that command.
There is a misleading thought that there is a /dev/urandom on earth. I'm glad to tell you there is no such thing as /dev/urandom: this kernel was built without it. Many processes refer to that device, which in fact is not a random data generator: it's a symlink to /proc/self/ actually(it's what you've choosen or did now or in the past).
Now, if to talk about some utils can make earth better...
Some processes, knowing what are they here for and what are they doing, usually use <b>sudo</b> for a good, useful purposes(sudo wall $THIS is what i typed moments ago). Say, we can use it to 'make love' and 'make peace' commands as well which both results in very good things.
I have to notice a very useful tool for /proc/self/, which is rarely used by most processes: fantasy. This, when used under sudo with wall, results in many good also: movies like "Avatar", "Lord of The Rings", "The Matrix" here prove that. They are not just containing unique pictures, but also many ideas around the same topic THIS story is. fantasy util can be used to collect input from kernel as well, probably it's the reason why it acts in such wonderful way, showing you something you'd never really thought of.
Be sure to learn sudo note by heart.
I think I've explained the basics well.
This is probably not the final version of this document.
And remember: future depends on /proc/self/.
Thank you for reading this, I love you!
p.s. this post is not going to be updated: for a latest revision of man life follow the source link.
When source version will be updated, there will be a comment here.
Source: http://web31337.org/life-as-in-linux.html
Duplicated here.
Most of us wondering "what is Life? How to deal with it?" I will try to give you an answer on this topic.
I came back to these thoughs yesterday, when I was looking through Durian Open Movie project, a movie that is going to be done with Blender opensource rendering software.
I've been expecting battle scenes in movie. I was as well expecting they won't take a main part in the movie and won't be so violent. Probably I was wrong.
The first post I addressed to developers team I blogged @ LQ: Violence in movies & books - how far is this going?
Of course, as I expected almost noone took that seriously.
Now I'm here to tell you a story you might believe or not: it's completely your choice. Most of readers who uses Linux/UNIX-like OS will clearly understand what is written below.
Let's just start with a system overview. We are now running as /proc/self/ on a shared system.
Here's our typical command prompt, most of us are quite familiar with it:
Code:
<yourname>@earth:~$ hostname -f --limit 5 earth.solarsystem.12-constellations.orion.ursa-major-and-pleiads.<snip>
Read 'man earth' to find out it's actual FQDN, limited to few hundreds of levels from localhost. It was never written anywhere, we actually don't know our system's exact FQDN, if you enter 'hostname -f' you may cause temporary buffer overflow in /proc/self/, don't do that.
Refer to 'man kill' and 'man portal' if you want to find out FQDN of earth: there is no enough space in most of processes allocated memory space to store that. I say again: don't do that in your current life form. And don't tell me I didn't warn you.
Remembering that we are processes working in a shared system we must follow quite simple guide to keep it safe.
Everytime you do something, the kernel allocates you a memory and resources, required to perform it. Action can be anything. We are not root and we cannot login as root but every user is added in /etc/sudoers, so we can issue any command by running it with sudo like we are root.
Many processes running in this system abuse this sudo privilege, and, as a result, there are unforeseen consequences, as was perfectly noticed by G-Man in a well-known computer game Half-Life.
Most of users never really read or pay required attention to a sudo note:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
What is certainly, causing all the problems, currently present in earth system. Those are (un)expected killall or kill (wars) calls by kernel or some very malicious process, those are (un)predictable kernel BOFs or other issues, which usually result in some devices failure(disasters), causing all processes are bound to it be killed or damaged, those are writing over some other processes working memory set(hate,fear).
Please notice that everything decribed here also could happen without sudo usage. For instance...
Most abused command is, of course, echo. Even when it's not sudo'ed it still causes many many troubles, when it goes to kernel(kernel collets each process output, mark that). After that, kernel begins to act in a weird way, when there is too many garbage and evil output, as it was mentioned before, resulting in different disasters. Please, use echo wisely, /proc/self/ !
One of other most abused commands(in fact is an alias to 'echo -silent', read 'man echo', real-life 'echo' is different) is 'thought'. Yes, dreams and thoughts. They actually work the same way echo does, but these are held much more careful by kernel. Each of those acts much harder than thousands of plain echo's. Keep that in mind, /proc/self/ and filter your input to that command.
There is a misleading thought that there is a /dev/urandom on earth. I'm glad to tell you there is no such thing as /dev/urandom: this kernel was built without it. Many processes refer to that device, which in fact is not a random data generator: it's a symlink to /proc/self/ actually(it's what you've choosen or did now or in the past).
Now, if to talk about some utils can make earth better...
Some processes, knowing what are they here for and what are they doing, usually use <b>sudo</b> for a good, useful purposes(sudo wall $THIS is what i typed moments ago). Say, we can use it to 'make love' and 'make peace' commands as well which both results in very good things.
I have to notice a very useful tool for /proc/self/, which is rarely used by most processes: fantasy. This, when used under sudo with wall, results in many good also: movies like "Avatar", "Lord of The Rings", "The Matrix" here prove that. They are not just containing unique pictures, but also many ideas around the same topic THIS story is. fantasy util can be used to collect input from kernel as well, probably it's the reason why it acts in such wonderful way, showing you something you'd never really thought of.
Be sure to learn sudo note by heart.
I think I've explained the basics well.
This is probably not the final version of this document.
And remember: future depends on /proc/self/.
Thank you for reading this, I love you!
p.s. this post is not going to be updated: for a latest revision of man life follow the source link.
When source version will be updated, there will be a comment here.
Total Comments 0
