From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265331AbUHHNjm (ORCPT ); Sun, 8 Aug 2004 09:39:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265348AbUHHNjm (ORCPT ); Sun, 8 Aug 2004 09:39:42 -0400 Received: from cmu-24-35-116-59.mivlmd.cablespeed.com ([24.35.116.59]:7155 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id S265331AbUHHNjl (ORCPT ); Sun, 8 Aug 2004 09:39:41 -0400 Date: Sun, 8 Aug 2004 09:39:26 -0400 (EDT) From: Thomas Molina X-X-Sender: tmolina@localhost.localdomain To: Kernel Mailing List Subject: Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices In-Reply-To: Message-ID: References: <200408071128.i77BSNCd006957@burner.fokus.fraunhofer.de> <20040807114046.GA5249@ucw.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Now that we've had our regularly-scheduled cdrecord imbriglio (my word for today), can we get on to one of our other periodic arguments? > Joerg is wrong. SCSI number simply doesn't work, and the current Linux > setup is absolutely the right thing to do. > > If Joerg keeps breaking cdrecord, the distributions will hopefully just > keep unbreaking it. The way you send SCSI commands to a device under Linux > is to open the device (with O_NDELAY) and then just start sending the > commands. None of the idiotic scanning and SCSI numbering crap. > > Involving Joerg in it just makes you go crazy. Don't bother.