🚀 go-pugleaf

In article <5200@batcomputer.tn.cornell.edu> riley@tcgould.tn.cornell.edu (Daniel S. Riley) writes:
>In article <1249@csuna.UUCP> swalton@solar.stanford.edu (Stephen R. Walton) writes:
>>Yes, 1.2 Execute always uses :T for its temporary.  However, there is
>>a real problem with doing this, as I found out: it results in a very
>>slow revalidation of your entire hard disk if your Startup-Sequence

Actually, its the normal speed revalidation :-)

>>does a LoadWB.  I can email the details (or you can read 'em on B$X),
>
>I haven't read the thread on BIX, but this seems a little extreme.  As
>I understand the situation, LoadWB does something equivalent to pulling
>a disk out and sticking it back in (ACTION_something, diskchange or
>inhibit, I guess), so you just need to avoid anything that you wouldn't

The reason Workbench does an ACTION_INHIBIT on all the drives
is to identify the disk devices on the DOS device list.  Only
disk devices are expected to respond to the ACTION_INHIBIT packet.

Under the old file system, this created a window of vunerability.
Inhibit always succeeded...even if there were outstanding locks.
(Fast File System can fail the ACTION_INHIBIT packet, btw).  So, a
WAIT after the LoadWb is probably a pretty good thing to do,
if you plan on creating files in your startup-sequence. 
-- 
andy finkel		{ihnp4|seismo|allegra}!cbmvax!andy 
Commodore-Amiga, Inc.

"Un*x is the answer, but only if you phrase the question very
carefully.
				
Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.