You know, it's not really fair use to copy and paste the entire article verbatim. It's not even slashdotted right now. You cannot copy it after it's slashdotted, can you?
Well, their top story is that Netbeans is switching to the GPLv2, whereas Daily Drudge's top story is that HISTORIC HELL STORM SET FOR JAMAICA. What's the "hell storm set"? A historic supercomputer? And what does Jamaica plan to do with it?:-)
Our kernel, which art in vmlinuz, Hallowed be thy inode. Thy booting come, Thy system calls be called, From user space as they are from root. And forgive us our SIGINTs, As we forgive those who SIGINT us. And lead us not into uninterruptible sleep, But deliver us from the kernel panic. For thine is the kernel space, The access control, and the terminal For ever and ever. uptime.
(b) it is illegal to listen to electron emissions -- completely ignoring that it is the intention of many devices like WLAN
Well, fortunately WLAN doesn't emit electrons, but only electromagnetic waves.:-)
Re:Dude, that article sucked.
on
Hardening Linux
·
· Score: 1
What's this with the "Enter kill -9 xxx where xxx is the PID."? How about just/etc/init.d/service_name stop? Just use the package manager to remove it.
Moreover, even if you for whatever reason use kill, you surely won't kill -9, unless things are really fucked up. It is a last-resort matter which doesn't allow an application to do any cleanup, and should only be used if nothing else helps. Never send a SIGKILL without first trying SIGTERM, unless you have very good reasons to do so (I admit I cannot think of such reasons, but then, maybe that's just my limited imagination).
Indeed, for normal processes, if normal SIGTERM doesn't help, it's a good idea to try SIGINT and SIGHUP before resorting to SIGKILL. Most often this way you can avoid to hard-kill it. Of course server processes are not killed by SIGHUP (I'm not sure about SIGINT), so you would not try that one on a server to kill.
Whole paintings would likely look brown to an alien!
I disagree. The pigments surely will also reflect wavelengths they can see. However colors which are similar or even look identical for us could be completely different for them, and vice versa. Probably our paintings would be a meaningless colored mess to them (but then, maybe they'd just consider a Rembrandt a modern arts painting:-)).
Your post has an air of philosophy about it. It can be completely possible for humans to be irrelevant in the grand scheme of things, (ie, you reading this is a pointless, futile waste of time, right?)
To be a futile waste of time implies there's something I could do instead which would matter. But for the universe as a whole it's completely irrelevant if I take the time to read it. That doesn't mean it's irrelevant to me, and I'm quite certain that it's not irrelevant to you either (after all, you wrote the comment, therefore you probably want it to be read). It's already irrelevant for most other people (because neither me reading that posting, nor anything I would have done or not done if I hadn't read it has any noticeable effect on them).
yet interaction between humankind and an alien race would be considered monumental by most (unless, of course, the aliens knew we were here all along;)
It would be monumental for us humans (and probably also for the alien race). It might also matter for other species on earth and/or on the planet of those aliens (e.g. it could lead to more space travel, which might mean more places to start rockets, affecting anything living at those places). It would still be irrelevant for the universe as a whole.
Well, for an (Unix-like) operating systems there are two vital parts: the kernel and the C library (few programs communicate directly to the kernel; even language support libraries for other languages tend to go through the C library on Unix-like systems; also the C library is probably the one userspace component which is the most OS specific). The kernel on Linux systems is Linux. The C library is glibc, i.e. GNU. Thus it makes sense to call the system GNU/Linux.
If it were for all the userland tools commonly used, I guess many current Linux installations would be more properly named KDE/X/Linux (although those running GNOME as desktop would be properly named GNU/X/Linux, since GNOME is GNU).
Ok, maybe make it KDE/X/GNU/Linux... no, that's clearly to long. But then, Linux already has an x, so we can just make that uppercase to properly attribute the X part of it. Also, KDE has the history of simply adding a K to the beginning of everything it touches.
Only problem: Should it now be KNU/LinuX, or GNU/KLinuX?
But you are not the universe. I'm sure that you'll somewhere find an American who favours communism. Does that mean America favours communism? Surely not.
"It's not just a tragedy for us, but also one for nature. Without us, there is no one to witness its infinite beauty; no one to marvel at a sunset, revel in a view, or thrill to the breaking of a wave on a beach." Nature doesn't care the least bit if someone witnesses its infinite beauty (which is a purely human term anyway; not the nature is beauty, but nature, or rather some part of it, fits our perception of beautiness). It doesn't care if we thrill to the breaking of a wave on a beach. Nature has no wishes, no feelings and no desire. It also doesn't exist for a particular purpose (least of all, for the purpose of being considered beautiful). It just is. Not more, not less.
And the LORD SGI commanded the man, "You are free to use any API on your computer; but you must not use the API of DirectX, for when you use it you will surely die."
Don't forget the part about installing malware on Egyptian computers. Some highlights are turning the screen dark, introducing lots of new bugs, and killing all first-forked child processes.
Update: I've now got the great idea to look into the JavaScript console, and I've found an error message which should explain it:
Error: uncaught exception: java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.lang.reflect.InvocationTargetException Since I'm quite sure I didn't open anything else using Java, I'm sure it's from that page. Obviously it didn't work for me because it was explicitly not permitted to work.
Well, maybe you first RTFA before making accusations.
To summarize what can be found there: He did notice SUN, and did not publish until Sun themselves published it. Then, one day after he published it on his page and a lot of people had read/commented on it, Sun reclassified the bug report and asked him to keep confident about it. Since it was too late to avoid it to be known anyway, he decided to leave it on his page. Now that last decision could be argued, but that's quite different from your accusation.
Nor could I (Seamonkey/Linux, Java and JavaScript enabled). The Gecko/JavaScript didn't do anything at all. The pure Java one obviously had something, because Adblock offered me to block it (there was an adblock tag somewhere in the page with no obvious object it belonged to; usually those tags appear above the area occupied by the plugin), but there definitively wasn't any new window opened.
Well, either that, or I'm unknowingly typing on an emulated SeaMonkey...:-)
Slashdot Mirror
No.
The RAM is in the leaves of the tree. The tree itself is the addressing hardware.
No, by the ??AA. Who else would have interest in information that cannot be copied, not even in principle?
What? Blasphemy! :-)
Fall upon you knees and pray:
Our kernel, which art in vmlinuz,
Hallowed be thy inode.
Thy booting come,
Thy system calls be called,
From user space as they are from root.
And forgive us our SIGINTs,
As we forgive those who SIGINT us.
And lead us not into uninterruptible sleep,
But deliver us from the kernel panic.
For thine is the kernel space,
The access control, and the terminal
For ever and ever.
uptime.
Well, fortunately WLAN doesn't emit electrons, but only electromagnetic waves.
Moreover, even if you for whatever reason use kill, you surely won't kill -9, unless things are really fucked up. It is a last-resort matter which doesn't allow an application to do any cleanup, and should only be used if nothing else helps. Never send a SIGKILL without first trying SIGTERM, unless you have very good reasons to do so (I admit I cannot think of such reasons, but then, maybe that's just my limited imagination).
Indeed, for normal processes, if normal SIGTERM doesn't help, it's a good idea to try SIGINT and SIGHUP before resorting to SIGKILL. Most often this way you can avoid to hard-kill it. Of course server processes are not killed by SIGHUP (I'm not sure about SIGINT), so you would not try that one on a server to kill.
Did you know that water vapour increases the greenhouse effect? Hydrogen cars will destroy our climate! :-)
Actually, the more correct name would be hydrogen hydroxide, because it dissociates into a hydrogen ion (H+) and a hydroxide ion (OH-).
I disagree. The pigments surely will also reflect wavelengths they can see. However colors which are similar or even look identical for us could be completely different for them, and vice versa. Probably our paintings would be a meaningless colored mess to them (but then, maybe they'd just consider a Rembrandt a modern arts painting
To be a futile waste of time implies there's something I could do instead which would matter. But for the universe as a whole it's completely irrelevant if I take the time to read it. That doesn't mean it's irrelevant to me, and I'm quite certain that it's not irrelevant to you either (after all, you wrote the comment, therefore you probably want it to be read). It's already irrelevant for most other people (because neither me reading that posting, nor anything I would have done or not done if I hadn't read it has any noticeable effect on them).
It would be monumental for us humans (and probably also for the alien race). It might also matter for other species on earth and/or on the planet of those aliens (e.g. it could lead to more space travel, which might mean more places to start rockets, affecting anything living at those places). It would still be irrelevant for the universe as a whole.
Maybe it's just that no one tried? Quick, take your grammophones and go to Redmont!
Well, for an (Unix-like) operating systems there are two vital parts: the kernel and the C library (few programs communicate directly to the kernel; even language support libraries for other languages tend to go through the C library on Unix-like systems; also the C library is probably the one userspace component which is the most OS specific). The kernel on Linux systems is Linux. The C library is glibc, i.e. GNU. Thus it makes sense to call the system GNU/Linux.
... no, that's clearly to long. But then, Linux already has an x, so we can just make that uppercase to properly attribute the X part of it. Also, KDE has the history of simply adding a K to the beginning of everything it touches.
If it were for all the userland tools commonly used, I guess many current Linux installations would be more properly named KDE/X/Linux (although those running GNOME as desktop would be properly named GNU/X/Linux, since GNOME is GNU).
Ok, maybe make it KDE/X/GNU/Linux
Only problem: Should it now be KNU/LinuX, or GNU/KLinuX?
But you are not the universe.
I'm sure that you'll somewhere find an American who favours communism. Does that mean America favours communism? Surely not.
Neither. Humans are completely irrelevant, as far as the universe as a whole is concerned.
"It's not just a tragedy for us, but also one for nature. Without us, there is no one to witness its infinite beauty; no one to marvel at a sunset, revel in a view, or thrill to the breaking of a wave on a beach."
Nature doesn't care the least bit if someone witnesses its infinite beauty (which is a purely human term anyway; not the nature is beauty, but nature, or rather some part of it, fits our perception of beautiness). It doesn't care if we thrill to the breaking of a wave on a beach. Nature has no wishes, no feelings and no desire. It also doesn't exist for a particular purpose (least of all, for the purpose of being considered beautiful). It just is. Not more, not less.
Machine code also is just a special byte code which happens to be interpreted by the CPU hardware (or even by microcode running inside the CPU).
If someone built a CPU which processes Java bytecode natively, would that suddenly turn Java from an interpreted into a compiled language?
It was cut out and a text version of this program automatically replaced it by a "make people nude" comment.
And the LORD SGI commanded the man, "You are free to use any API on your computer; but you must not use the API of DirectX, for when you use it you will surely die."
Don't forget the part about installing malware on Egyptian computers. Some highlights are turning the screen dark, introducing lots of new bugs, and killing all first-forked child processes.
"You are trying to start Windows. This is possibly dangerous, therefore Windows needs your permission to continue."
:-)
SCNR
Well, maybe you first RTFA before making accusations.
To summarize what can be found there: He did notice SUN, and did not publish until Sun themselves published it. Then, one day after he published it on his page and a lot of people had read/commented on it, Sun reclassified the bug report and asked him to keep confident about it. Since it was too late to avoid it to be known anyway, he decided to leave it on his page. Now that last decision could be argued, but that's quite different from your accusation.
Nor could I (Seamonkey/Linux, Java and JavaScript enabled). The Gecko/JavaScript didn't do anything at all. The pure Java one obviously had something, because Adblock offered me to block it (there was an adblock tag somewhere in the page with no obvious object it belonged to; usually those tags appear above the area occupied by the plugin), but there definitively wasn't any new window opened.
... :-)
Well, either that, or I'm unknowingly typing on an emulated SeaMonkey