From owner-freebsd-bugs Sun May 31 04:50:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14482 for freebsd-bugs-outgoing; Sun, 31 May 1998 04:50:18 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14477 for ; Sun, 31 May 1998 04:50:17 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id EAA10214; Sun, 31 May 1998 04:50:00 -0700 (PDT) Date: Sun, 31 May 1998 04:50:00 -0700 (PDT) Message-Id: <199805311150.EAA10214@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Hans Huebner Subject: Re: bin/6799: problem with open(2) in libc_r and opening tape device Reply-To: Hans Huebner Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/6799; it has been noted by GNATS. From: Hans Huebner To: freebsd-gnats-submit@freebsd.org, ian@nmsu.edu Cc: Subject: Re: bin/6799: problem with open(2) in libc_r and opening tape device Date: Sun, 31 May 1998 13:47:20 +0200 Apparently, the observed behaviour is a result of libc_r's attempt to switch the file descriptor to the tape device into asynchronous mode. As of now, neither the old nor the CAM SCSI subsystem support that. This holds true for any SCSI device, not only tapes, which renders FreeBSD's SCSI subsystem inaccessible to multithreaded applications. This requires substantial work to make it properly work, and it is unclear whether this would be warranted for the old SCSI subsystem (iff CAM makes it into 3.0). -Hans -- Hans@Huebner.ORG +49-177-512 1024 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message