Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.sys.amiga
Subject: Re: More 1.4 whishes
Message-ID: <2064@cps3xx.UUCP>
Date: 3 Mar 89 20:34:13 GMT
References: <5442@abo.fi> <413@antares.UUCP> <5899@abo.fi>
Reply-To: porkka@frith.UUCP (Joseph A Porkka)
Organization: Michigan State University
Lines: 27

In article <5899@abo.fi> vinsci@abo.fi (Leonard Norrgard) writes:
>In article <413@antares.UUCP>, jms@antares.UUCP (Joe Smith) writes:
>> In article <5442@abo.fi> rosenbergr@abo.fi (Robin Rosenberg, Computer Science, ]bo Akademi) writes:
>...
>is obviously performed in the context of a single process. Thus, the startup
>code would have to determine the right order of execution *before* the
>execution begins. This could probably be achieved in many different ways

A better idea. Since everything else on the Amiga
is prioritized, simple apply the same 
to the startup-sequence-directory (please use a shorter name :-] )
Each file would have a priority assigned, from -128 to +127.
Startups for application programs would be zero.
Startups for xtra hardware would have higher numbers.
Commodore could dictate a 'standard' range for each type of thing
so that the priority could be preset without users needing to worry.
example:
	you should use 100-127 for confinguring extra mem if needed.
		       50-99  for filesystems
		       25-49  for networks
		       -20 to 20 for applications
		       -128 to -20 for things you probably don't want
			       anyways


Joe Porkka
porkka@frith.egr.msu.edu