Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!oliveb!amiga!cbmvax!andy
From: andy@cbmvax.UUCP (Andy Finkel)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Novice questions...
Keywords: S:, process control structure
Message-ID: <7277@cbmvax.UUCP>
Date: 12 Jul 89 15:55:27 GMT
References: <3147@thor.acc.stolaf.edu>
Reply-To: andy@cbmvax.UUCP (Andy Finkel)
Organization: Commodore Technology, West Chester, PA
Lines: 28

In article <3147@thor.acc.stolaf.edu> hopp@agnes.stolaf.edu () writes:
>/* Maybe the line-eater ignores comments? */
>
>Here's a couple of questions from a novice:
>
>First, does anyone know what the real intent behind the S: directory is?  Was
>it intended as a place for shell scripts, or as a place for software
>configuration files?  It has been used for both.  (And the main resident,

It's mainly for script files;  anything that can be safely executed.
If an application desires to place configuration files in the S:
directory, we've suggested creating a subdirectory in the S: directory,
and placing the configuration files there.

>Second,  How does an inquisitive AmigaDOS process look at it's process control
>structure?

FindTask(0L) gives you a pointer to your task structure  (or process
structure ff you are a process).  The dos library include files contain
the needed structure definitions.
-- 
andy finkel		{uunet|rutgers|amiga}!cbmvax!andy
Commodore-Amiga, Inc.

  "It's in there."

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.