From owner-freebsd-current Wed Dec 20 14:11: 6 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 20 14:11:04 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id EB48437B400 for ; Wed, 20 Dec 2000 14:11:03 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBKMArf57112; Wed, 20 Dec 2000 23:10:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Tomasz Paszkowski Cc: freebsd-current@FreeBSD.ORG Subject: Re: open in kernelspace In-Reply-To: Your message of "Wed, 20 Dec 2000 23:02:21 +0100." <20001220230221.A66954@genesis.k.pl> Date: Wed, 20 Dec 2000 23:10:53 +0100 Message-ID: <57110.977350253@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001220230221.A66954@genesis.k.pl>, Tomasz Paszkowski writes: >On Wed, Dec 20, 2000 at 10:52:05PM +0100, Poul-Henning Kamp wrote: >> > How to open && read file from kernel space. I have seen VOP_[READ,OPEN] >> > but i think there's something easiest ? >> >> VOP_* is the way to go. > > :(( So I'll have a long night Sorry, yes... ktrace, various accounting and of course open(2) will be the best places to start. In all likely hood you're trying to do something the wrong way though... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message