From owner-freebsd-arch Mon Jan 29 3:43:47 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 1736437B400 for ; Mon, 29 Jan 2001 03:43:29 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0TBhWK20364; Mon, 29 Jan 2001 12:43:32 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Brian Somers Cc: freebsd-arch@FreeBSD.ORG Subject: Re: Cloned open support In-Reply-To: Your message of "Mon, 29 Jan 2001 10:52:31 GMT." <200101291052.f0TAqVK58112@storm.FreeBSD.org.uk> Date: Mon, 29 Jan 2001 12:43:32 +0100 Message-ID: <20362.980768612@critter> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101291052.f0TAqVK58112@storm.FreeBSD.org.uk>, Brian Somers writes: >Hi, > >I'm considering having a crack at adding support for cloned opens. >Before I start, I guess I've got two questions: > >1. Is anybody else doing this. Not actively. >2. Given that I'll need to change the d_open prototype (and > thus cdevsw) I'm not sure that is really a good idea. If you look at the device name clone stuff I think I have made it possible to handle it there. The idea being that you call it on "/dev/pty" and it will clone "/dev/pty38" for you and return the dev_t for that. You then complete the open on that dev_t. I have not quite thought it through though. Either way, I think cloning open should be kept out of d_open one way or another. -- 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-arch" in the body of the message