From owner-freebsd-stable Mon Mar 10 22: 7:50 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37D3937B404 for ; Mon, 10 Mar 2003 22:07:48 -0800 (PST) Received: from pikachu.bsp.bc.niigata-u.ac.jp (pikachu.bsp.bc.niigata-u.ac.jp [133.35.85.2]) by mx1.FreeBSD.org (Postfix) with SMTP id DBBFD43F93 for ; Mon, 10 Mar 2003 22:07:44 -0800 (PST) (envelope-from iwaki@bc.niigata-u.ac.jp) Received: (qmail 13182 invoked by alias); 11 Mar 2003 15:07:41 +0900 Message-ID: <20030311060740.13174.qmail@pikachu.bsp.bc.niigata-u.ac.jp> Date: Tue, 11 Mar 2003 15:07:38 +0900 (JST) To: ken@kdm.org Cc: stable@FreeBSD.ORG Subject: Re: cdcontrol via atapicam in 4.8-RC From: Mamoru Iwaki In-Reply-To: <20030310213527.A26660@panzer.kdm.org> References: <20030309073546.A19190@panzer.kdm.org> <20030310044541.10713.qmail@pikachu.bsp.bc.niigata-u.ac.jp> <20030310213527.A26660@panzer.kdm.org> X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: "Kenneth D. Merry" Subject: Re: cdcontrol via atapicam in 4.8-RC Date: Mon, 10 Mar 2003 21:35:27 -0700 > I doubt it'll get fixed in 4.8-RELEASE. 4.8 is in code freeze, about to go > out the door, and I haven't had time to backport things to -stable yet, > much less get it tested for a bit. Oh, of course, yes. I understand that. > I wish I had gotten it in before the freeze, but that didn't happen. :( Right. > My guess is it'll go in after the freeze, and you can pull down a snapshot > or cvsup new sources to get the fixes. Thank you, I'll do so. > As for accessing the devices simultaneously -- yes, you can shoot yourself > in the foot if you're not careful. We've had the same issue with the > normal CAM devices for a while. You can say access the cd(4) device while > you're burning a CD via the pass(4) device and mess up the burning process. Aha, I see. > The simple answer to that problem is "don't do it". :) Sure, I don't like shoot myself. ;) > There's nothing inherently more dangerous about enabling the atapi code and > atapicam at the same time. Just don't use the cd(4) and acd(4) devices > (that share the same underlying physical device) simultaneously and you'll > be fine. As you said in the above example of burning CD process, if simultaneous access possibly causes problems only in the process and no panic in kernel, the situation may be acceptable. Many thanks. --- ----- Mamoru IWAKI (iwaki@bc.niigata-u.ac.jp) Graduate School of Science and Technology, Niigata University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message