Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: What SHOULD go in the kernel
Message-ID: <11346@smoke.BRL.MIL>
Date: 19 Oct 89 11:25:10 GMT
References: <2186@ektools.UUCP> <3596@frame.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 12

In article <3596@frame.UUCP> eeg@frame.UUCP (Eric Griswold) writes:
>  If, after this much thought, there still is no way to implement it as 
>a user process, consider putting it in the kernel.

But first, think carefully about what service it is in GENERAL terms
that the kernel is not providing, and design an elegant implementation
that provides the GENERAL service, rather than just the specific need
that prompted the issue.

Of course, we were talking originally about device drivers.
My advice there is to keep them as simple as possible so long as
all the legitimate uses of the device are supported.