Slashdot Mirror
Red Hat Nullifies Differences Between Bash, Csh
Andreas(R) writes "Red Hat Software has revealed that future versions of the distribution will hide the differences between command-line user interfaces, creating a 'more unified shell prompt experience'. 'I don't mind if they rebrand and unify the GNOME and KDE interfaces,' said one Linux longhair. 'Frankly, I rarely use GUIs. But when they start messing with my CLI, then it's personal. I'm not going to sit here and let Red Hat infect my beloved tcsh with those annoying quirks from bash." Ah, nothing like satire that only a small group will truly grok. *grin*
If you hadn't noticed it's under the "funny/humour" catogory. Turn this catagory off in your preferences if you dont want it.
They have this in their FAQ, too...
This stuff is fake, right?
Yes, the "news" articles published here at Humorix are, ahem, all made up. Fake, fake, fake. Don't take anything we say seriously (except for this sentence, of course).
A few people have actually written in and asked if an article was true or not. While we are flattered that our fabrications were mistaken for actual news, the fact remains: everything here is fake. A few nuggets of truth might be found, but everything else is a figment of our imaginations. If in doubt, just remember this saying: "Fake news is to Humorix as unconfirmed rumors are to Slashdot."
As p3d0 said, shells behave the opposite. (Although there once was an odd bug in - what was it, Ultrix? - where csh behaved the opposite, i.e. didn't behave the opposite, i.e. was buggy, with regards to the && and || short-circuit operators. But then, csh history is replete with odd bugs.)
But to expand on the point: in Unix, the exit status of a program is an integer (7 unsigned bits, anyway: trying to use more is not portable). Convention dictates that 0 is normal termination, non-zero is abnormal, and anything over 128 means it was killed by a signal rather than the exit() function. (Which signal? Subtract 128 to find out.) Furthermore, many programs document their various abnormal exit status numbers to mean various failure cases.
Note that even MS-DOS (and all of its misshapen get) uses the zero / greater-than-zero convention. In DOS, a process's return value is called the "errorlevel", which indeed more accurately describes its main purpose.
This convention also goes a little deeper in Unix. Most system calls and many C library functions (remember, the standard C library was first defined on Unix) return 0 for success (or similar concepts: "equality" in the string compare function strcmp()) and non-zero for failure ("inequality" in strcmp()). Even system calls which return other meaningful integers (open(), for example) generally use >=0 for success and -1 for failure.
So it may make no sense from a boolean logic point of view but zero==true is surprisingly widespread. Mostly because there is often only one way to succeed at a task but many ways to fail, and it's useful to be able to report specific failure modes.
"How can you claim that you are anti-crack, while still writing a window manager?" — Metacity README
The home page is whatever Malda wants to make it. Slashdot started as Rob Malda's pet project, and that's basically what it will always be. It's an obscenely popular project and makes some money (maybe) now, but it's still his personal project.
Deal with it. No one, especially Rob, cares what you think "should" be on the main page.
Vi is a word in several languages.
Yes, as an example "vi" happens to be the danish word for "we".
Do you care about the security of your wireless mouse?
It won't work. /dev/random isn't usually marked as executable. Even if it were, it wouldn't even get to run anything unless by some miracle the random string was a valid ELF header. Of course, the random string could also be something like "#!/bin/bash", thereby giving them a shell.
/dev/random
What you want to do is make a script like:
#!/bin/sh
cat
Then make that script their shell. When they log in, they'll just get lots of random crap.
My other first post is car post.
Best text editor: BBedit
"It doesn't suck"
if you have ever taken ANY C class you will remember that line at the end of your function 'return 0;' that meant 'everything's fine'
fear is the mind killer
Christ almighty, what the hell do they put in libc to make it 24 megs? On my FreeBSD system, libc.a is 1568K, and there is talk on the mailing list of finding ways to trim it down.
You had me at "dicks fuck assholes".