Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!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: <13494@reed.UUCP>
Date: 1 Nov 89 19:31:50 GMT
References: <56505@tiger.oxy.edu> <4020@helios.ee.lbl.gov> <5511@umd5.umd.edu> <8831@hoptoad.uucp> <13474@reed.UUCP> <8838@hoptoad.uucp>
Reply-To: chaffee@reed.UUCP (Alex Chaffee)
Organization: Reed College, Portland OR
Lines: 37


>In article <13474@reed.UUCP> chaffee@reed.UUCP (Alex Chaffee) writes:
>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.

In article <8838@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>Any INIT so brain-damaged that this happens, or any combination of
>INITs which interact unpredictably in this way, should be dragged to
>the trash can.  I don't understand how people can be so devil-may-care
>about their system reliability.  I use very few INITs and for that
>reason, when my development software does something strange, I
>generally feel confident that it's my code's fault and I don't waste
>time messing around with possible INIT problems.  INITs are a necessary
>evil and should be treated as such.

When I'm programming, and get a system crash I don't understand, the first
thing I do is turn off all my INITs and reboot.  (I can actually turn them
off while rebooting, thanks to an init manager which, incidentally, I had to
rename to come first in the list.)  However, there are many "brain-damaged"
INITs whose authors were less than compulsive about compatibility, yet whose
functions I find indispensible.  Until I get around to writing replacements
(which I'm actually doing, as a matter of fact, for Pop-Keys), I can live
with keeping "evil" INITs in my system.  And really, if I can't _resolve_ a
conflict by renaming, out it goes.  But if the evil is exorcised by
renaming, I'm happy.  But if the INIT loses functionality if its name
changes... even if it is otherwise a paragon of compatibility... I get mad!

(Well, not _that_ mad...)

                "Nor is it a consequence of my bed's being covered with
                leaves that I am not hallucinating that it is."
                - Barry Stroud
____________________
-- 
Alex Chaffee
chaffee@reed.UUCP
____________________