Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!quintus!ok
From: ok@quintus.UUCP (Richard A. O'Keefe)
Newsgroups: comp.unix.questions
Subject: Re: Fun with ignoreeof
Message-ID: <592@cresswell.quintus.UUCP>
Date: 28 Jan 88 11:32:20 GMT
References: <2248@tekcrl.TEK.COM> <410@lakesys.UUCP> <584@cresswell.quintus.UUCP> <3854@vdsvax.steinmetz.ge.com>
Organization: Quintus Computer Systems, Mountain View, CA
Lines: 24
Summary: OOPS

In article <3854@vdsvax.steinmetz.ge.com>, barnett@vdsvax.steinmetz.ge.com (Bruce G. Barnett) writes:
> In article <584@cresswell.quintus.UUCP> ok@quintus.UUCP (Richard A. O'Keefe) writes:
> |The command
> |	/bin/kill -HUP $$
> |is immune to aliases, 
> 
> Not really. Try
> 	alias /bin/kill echo
> 
He's absolutely right, folks.  (If I had a Bourne shell with history,
I would change over RIGHT NOW!)  The fine print in the manual says
that the things you alias are "words", and /bin/kill is a "word".
What an amazing feature.  I wish I could make it go away...

Ok, since you can't alias alias 'unalias',
	unalias kill
	kill -HUP $$
or
	''kill -HUP $$
or	\kill -HUP $$
or even
	\/bin/sh -c "/bin/kill -HUP $$"

{sh functions can't look like absolute pathnames}