Path: utzoo!utgpu!watserv1!watmath!att!occrsh!uokmax!apple!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!samsung!xylogics!merk!spdcc!tauxersvilli!alphalpha!nazgul
From: nazgul@alphalpha.com (Kee Hinckley)
Newsgroups: comp.sys.apollo
Subject: Re: How to modify the "kernel'?
Message-ID: <1990Sep6.162814.20549@alphalpha.com>
Date: 6 Sep 90 16:28:14 GMT
References: <6881.26e59640@jetson.uh.edu>
Organization: asi
Lines: 30

In article <6881.26e59640@jetson.uh.edu> cosc4fp@jetson.uh.edu writes:
>This is driving crazy.....  how does one configure the "kernel" on an
>Apollo?  I need to raise the max number of processes on a machine.

First the good news about Apollos.
    You hardly ever need to modify anything that on most systems would
    requiring modifying the kernel.

Now the bad news.
    When you *do* need to, you can't.

The only kernel mod you can get is called a new release of the OS.
SR10.3 supposedly allows around 1024 or so, which ought to do the trick.
You'll run out disk space before you run out of processes.

The process limit on Apollos is so strangely low for a number of
reasons.  It was only meant as a single user machine, Aegis was not
as daemon-crazy as Unix is, Aegis originally used multiple programs
per process, so invoking a new program didn't invoke a new process,
etc..  On the bright side, it used to be 32!

						-kee
-- 
Alphalpha Software, Inc.	|	motif-request@alphalpha.com
nazgul@alphalpha.com		|-----------------------------------
617/646-7703 (voice/fax)	|	Proline BBS: 617/641-3722

I'm not sure which upsets me more; that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.