Posted on 01/18/2005 11:40:57 AM PST by N3WBI3
Is this more of O'Gara's so-called journalism?
Groklaw's take on it is at:
http://www.groklaw.net/article.php?story=20050115131942494
You'll need to ignore the intertwined death-spiral
debate about Santa Claus :-)
They should just rewrite linux to make it easy and fun to use.
I had a dream last night such a linux existed and I set up an old machine of mine to use it. But I still mostly used windows since there are games and fun stuff to do with windows.
At work, we mostly chase linux and unix (which are the same thing) problems from platform to platform. Every platform claims they're doing it the right way but all they do is break my scripts and piss me off.
Sometimes you can use typeset -Z2 to add leading zeroes and sometimes you have to pull your hair out.
Sometimes you can do:
echo $L|awk -F" " {'print $2,$3,$5 '}|read MONTH DAY SIZE
And other times you're ready to put a sledgehammer through the screen, which, by the way, is the wrong thing to attack since the evil is in the CPU and sometimes on external hard drives.
DEATH TO UNIX! LONG LIVE THE NEW FLESH!
Some folks may find irony in Groklaw's poor choice of using Santa Claus as a myth, to rebuke G2's poor choice in reporting a myth as a story.
Have you suggested they standardize on one version?
Come N3WBI3, I thought you'd (at least) ping GE, since he posted the original. :)
> ... the amount of stolen UNIX code in Windows has recently
> been proven to be much larger than previously thought, ...
Not just Unix. Recall Stac Electronics (among many others)?
Mr. Bill is an equal-opportunity plagiarist, and since his
OS is closed-source, the purloined portions are harder to
find, but find them people do.
Anyway, MS bought a very expensive license from SCO,
ostensibly to protect MS from Unix claims, but it's
also speculated to have been a way for MS to fund the
SCO f.u.d. machine.
I'n not sure of your entire point here.
The mere fact that the word "linux" appears in a patent is meaningless.
Here ya go.
See, I agree with you.
It better happen fast, because one thing about patents is that THEY EXPIRE! Remember the .GIF patent and the patent on RSA encryption? All water under the bridge now.
Of course I *DO* realize that industry will undoubted lobby our corrupt politicos to increase these limits (as they have successfully done with copyrights) - but permit me my fantasies!
Neither of these situations has anything to do with the OS kernel -- these are shell commands, and whichever shell you use can have any number of OS kernels under it. It's not the fault of the kernel that you didn't shebang the proper shell into your program at the outset.
I always shebang ksh. You sound like one of those awkward nerds who embraces this crap because everyone beat up on you in high school, so now you have this overly complicated usless thing that is all your own and you can LORD your false intellectual superiority over other people now.
O/S should be about getting stuff done, not about getting revenge for when you were kicked on the playground when you were ten. The O/S should take care of all of this. That is what "O/S" means. "O/S" means "relax buddy, I'll take care of the stupid crap so you can do what needs to be doing."
It does not mean "Root around the overly long and complectaed man files and if you can't find it 'Ha! Ha!' you probably kicked my master when he was ten." Which, I never did.
I always shebang ksh. You sound like one of those awkward nerds who embraces this crap because everyone beat up on you in high school, so now you have this overly complicated usless thing that is all your own and you can LORD your false intellectual superiority over other people now.
O/S should be about getting stuff done, not about getting revenge for when you were kicked on the playground when you were ten. The O/S should take care of all of this. That is what "O/S" means. "O/S" means "relax buddy, I'll take care of the stupid crap so you can do what needs to be doing."
It does not mean "Root around the overly long and complectaed man files and if you can't find it 'Ha! Ha!' you probably kicked my master when he was ten." Which, I never did.
Btw, just because something is invoked as "ksh" don't mean it came from David Korn. And there are several versions even of that.
Try bash.
Bash is totally unusable. None of my typesets ro awks work at all under that thing and set -o vi doesn't work that well either, if at all. I avoid bash like it was csh, which might be even more useless.
Alternatively, you could use Perl to do that scripting. Forget awk, sed, and never say "typeset" again.
Saying "set -o vi" works quite well on my home systems (using bash) as well as at the office (ksh). Sounds like you got a different problem.
Again, though, none of this has anything to do with the kernel itself.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.