Hi, On Tue, Dec 22, 2009 at 2:06 PM, Jason Spiro <jasonspi...@gmail.com> wrote: > jhell <jhell <at> DataIX.net> writes: >> >> This is what shell aliases are for and what a system admins job consist >> of. If it gives you that much of a problem just alias it out for your self >> in your .cshrc .shrc .bashrc .bash_profile etc. If you want to change >> something on a more per user basis figure out how to setup a skeleton >> directory so when a new user is created they get all the files from that >> skel copied into there home. If it is more of a system-wide change then >> the shell files in /etc will probably be of more use. >> >> PS: Applying your changes to a mailing list are not const. > > Using aliases would help me, but wouldn't help people elsewhere in the world > who > don't know what SysV killall does. Renaming FreeBSD killall would help > prevent > them from getting burned, perhaps on a busy production server, even once.
I'm afraid that it's too late to change either parties, i.e. there would be a lot of scripts that rely on the BSD or Linux behavior, etc. Instead of making changes to killall which already diverge between open source implementation and closed source ones, it might be better off to have administrators to learn some more consistent ways to do the same task, i.e. pkill. Cheers, -- Xin LI <delp...@delphij.net> http://www.delphij.net _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
