From owner-freebsd-hackers  Sun Sep  3 16: 7:19 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47])
	by hub.freebsd.org (Postfix) with ESMTP
	id B89BF37B43C; Sun,  3 Sep 2000 16:07:17 -0700 (PDT)
Received: from rumi.usc.edu (rumi.usc.edu [128.125.51.41])
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id QAA36094;
	Sun, 3 Sep 2000 16:07:16 -0700 (PDT)
Received: from rumi (localhost [127.0.0.1])
	by rumi.usc.edu (8.9.3/8.9.3) with ESMTP id QAA34204;
	Sun, 3 Sep 2000 16:07:14 -0700 (PDT)
Message-Id: <200009032307.QAA34204@rumi.usc.edu>
To: Andrzej Bialecki <abial@webgiro.com>
Cc: awr <awr@plan9.hert.org>,
	Pavlin Ivanov Radoslavov <pavlin@catarina.usc.edu>,
	freebsd-hackers@FreeBSD.ORG, sef@FreeBSD.ORG
Subject: Re: Q: System call interception 
In-reply-to: Your message of "Sun, 03 Sep 2000 19:56:42 +0200."
             <Pine.BSF.4.20.0009031954320.93881-100000@mx.webgiro.com> 
Date: Sun, 03 Sep 2000 16:07:14 -0700
From: Pavlin Ivanov Radoslavov <pavlin@catarina.usc.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > 
> > Intercepting syscalls is very easy.  In my mind, what you should do is
> > write a KLD that creates a syscall that mimicks the actions of what

Thanks for the detailed info and the pointers.
However, I forgot to mention that the solution I need should not
require modifications to the system, and should not require root
privilege.

Pavlin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message