From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S264408AbTIIThC (ORCPT <rfc822;willy@w.ods.org>);
	Tue, 9 Sep 2003 15:37:02 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264428AbTIIThC
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 9 Sep 2003 15:37:02 -0400
Received: from mx2.it.wmich.edu ([141.218.1.94]:17580 "EHLO mx2.it.wmich.edu")
	by vger.kernel.org with ESMTP id S264408AbTIITg7 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 9 Sep 2003 15:36:59 -0400
Message-ID: <3F5E2BA4.60704@wmich.edu>
Date: Tue, 09 Sep 2003 15:36:04 -0400
From: Ed Sweetman <ed.sweetman@wmich.edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030722
X-Accept-Language: en
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: atapi write support? No
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Is anyone able to actually use the atapi write support present in the 
later cdrecord releases?  2.6 can't seem to work with it at all.  Is 
this due to the kernel being broken or cdrecord not being up to date 
with 2.6 semantics?