I'd much rather they open source CMVC but since that would compete with the Rational line I doubt we'll ever see that happen. CMVC was an IBM configuration management and defect tracking system that they marketed for a while. I understand it is still widely used internally at IBM.
I have to go with Cliff and the Zombie on this one. Twenty three years ago when I started working in the *IX world we configured a small NIS domain and counted on a variety of circumstances and basic network security to keep our network relatively secure. Fast forward to today and uhhh... oh crap we're still doing the same thing! I can't believe it.
If you're really interested in shell scripting you'll probably want to read this if you missed it beofore. Interveiw with David Korn. Its great reading for anyone intereted in shells. ksh is my all-time favorite, with bash a close second.
http://slashdot.org/articles/01/02/06/2030205.sh tm l
Well you're right to a point. But it brings about a something about this subject that puzzles me greatly. Why would anyone think shell scripting is hard? The real posix hands write shell scripts every day in a single line at the command pompt. Stuff like
well... its just saving it in a file away from being a shell script. So what's the big deal? Lost Art? Give me a break.
While I'm at it let me walk down memory lane for a couple of shell stories. When I was just starting out in Unix (around 1988) at a big three initial corporation and I first found out about ksh (Command line editing! My life was changed!) I though "korn shell" was a play on words because of the unix "kernel" - Get it? Korn; Kernel? Hey, I was young then.
Later on me and a buddy were working on third level support for NFS. Lots of people were having problems because ksh kept its history file consistent by setting a flock on the history file and if they were keeping it in the home directory over NFS if NFS file locking failed - which was pretty common at that time; the file history would get hosed. I walked into our office one day and heard my buddy Paul talking to somebody on the phone about the problem. When he hung up I asked who he was talking to. He'd decided to just call Bell Labs and asked for David Korn to ask why he used a file lock on the history file. He got through to him and David said it just seemed like a good idea at the time. We changed the three initial corp's flagship posix product's ksh implementation to not use flock and I believe it's the same way today.
Slashdot Mirror
I'd much rather they open source CMVC but since that would compete with the Rational line I doubt we'll ever see that happen. CMVC was an IBM configuration management and defect tracking system that they marketed for a while. I understand it is still widely used internally at IBM.
I'd pay to have IBM opensource CMVC. The best source code control product for small groups ever.
I have to go with Cliff and the Zombie on this one. Twenty three years ago when I started working in the *IX world we configured a small NIS domain and counted on a variety of circumstances and basic network security to keep our network relatively secure. Fast forward to today and uhhh... oh crap we're still doing the same thing! I can't believe it.
If you're really interested in shell scripting you'll probably want to read this if you missed it beofore. Interveiw with David Korn. Its great reading for anyone intereted in shells.
h tm l
ksh is my all-time favorite, with bash a close second.
http://slashdot.org/articles/01/02/06/2030205.s
Well you're right to a point. But it brings about a something about this subject that puzzles me greatly. Why would anyone think shell scripting is hard? The real posix hands write shell scripts every day in a single line at the command pompt. Stuff like
... its just saving it in a file away from being a shell script. So what's the big deal? Lost Art? Give me a break.
ps -elf | grep pine | awk '{print $4}' | \
xargs -i -t kill{}
well
While I'm at it let me walk down memory lane for a
couple of shell stories. When I was just starting out in Unix (around 1988) at a big three initial corporation and I first found out about ksh (Command line editing! My life was changed!) I though "korn shell" was a play on words because of the unix "kernel" - Get it? Korn; Kernel? Hey, I was young then.
Later on me and a buddy were working on third level support for NFS. Lots of people were having problems because ksh kept its history file consistent by setting a flock on the history file and if they were keeping it in the home directory over NFS if NFS file locking failed - which was
pretty common at that time; the file history would get hosed. I walked into our office one day and heard my buddy Paul talking to somebody on the phone about the problem. When he hung up I asked who he was talking to. He'd decided to just call Bell Labs and asked for David Korn to ask why he used a file lock on the history file. He got through to him and David said it just seemed like a good idea at the time. We changed the three initial corp's flagship posix product's ksh implementation to not use flock and I believe it's the same way today.
Shell scripting is your friend on any platform.