Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!reed!chaffee
From: chaffee@reed.UUCP (Alex Chaffee)
Newsgroups: comp.sys.mac.programmer
Subject: Re: INIT getting it's file name...
Message-ID: <13474@reed.UUCP>
Date: 29 Oct 89 03:20:25 GMT
References: <56505@tiger.oxy.edu> <4020@helios.ee.lbl.gov> <5511@umd5.umd.edu> <8831@hoptoad.uucp>
Reply-To: chaffee@reed.UUCP (Alex Chaffee)
Distribution: usa
Organization: Reed College, Portland OR
Lines: 12

In article <8831@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>Three:  I have always felt that the ability to rename INITs is
>overrated.  I mean, who cares if you can or not?  However, few people
>agree with me on this.

That's because few people have never had an INIT conflict that could only be
resolved by (guess what) renaming the INIT files.  Renaming INITs is vital.

-- 
Alex Chaffee
chaffee@reed.UUCP
____________________