Date: Wed, 07 Jul 1999 09:22:43 -0700 From: Mike Smith <mike@smith.net.au> To: David Wolfskill <dhw@whistle.com> Cc: jwd@unx.sas.com, freebsd-hackers@freebsd.org Subject: Re: Connect and so on.. Message-ID: <199907071622.JAA04081@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 07 Jul 1999 07:15:47 PDT." <199907071415.HAA71896@pau-amma.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Back to -hackers, I've been using and (many times, by necessity) > administering UNIX systems since '86. It seems to me that having points > within "privileged" code where the OS could invoke site-supplied code on > the way in (so the site-supplied code would be able to examine, and > possibly replace, a parameter list), the OS could check some sort of > "return code" from the site-supplied code (absence of the code being > treated as pathologically equivalent to "return code 0"), and either > continue processing with the (possibly replaced) parameter list or > terminate processing early. then, if processing did take place, just > before retunring control to the user-level code, see if there's a > post-processing exit point, and if so, pass control to it (first), to > perform any additional site-specific policy. For system calls at least, you can already do this with KLDs (and you used to be able to do it with LKMs). -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907071622.JAA04081>