Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Tuesday 07 December 2004 3:32 pm, David Hummel wrote: > On Tue, Dec 07, 2004 at 03:25:57PM -0500, Jerry Feldman wrote: > > On Tuesday 07 December 2004 3:13 pm, David Hummel wrote: > > > It's generally a bad idea to give a script the same name as a system > > > command (unless it's some kind of wrapper for that command, and even > > > then be careful). Just add .sh, .bash, .pl, whatever. > > > > I actually discuss this in the Linux course I teach. If you noted, > > the name of the script is Kill. Yes, kill.sh would work very nicely > > too, but Kill is more into the Unix paradigm where every command > > should be a few letters to type as possible. (Comes from my ASR33 > > days). > > I think this is pretty much a non-issue with command completion in > modern shells like bash. This is very true. Actually pkill et. al. does essentially the same thing and a bunch more. One issue is just keeping one's environment straight between systems,. -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |