From owner-freebsd-current@FreeBSD.ORG Fri Apr 2 08:09:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29F8116A4D1; Fri, 2 Apr 2004 08:09:59 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CD1943D46; Fri, 2 Apr 2004 08:09:59 -0800 (PST) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 130435C80A; Fri, 2 Apr 2004 08:09:59 -0800 (PST) Date: Fri, 2 Apr 2004 08:09:59 -0800 From: Alfred Perlstein To: current@freebsd.org Message-ID: <20040402160959.GJ26131@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i cc: alc@freebsd.org Subject: mmap breakage? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Apr 2004 16:09:59 -0000 I noticed that mplayer seems to want to open /dev/zero with RDONLY but then tries to mmap it PROT_READ+PROT_WRITE and gets rejected. This seems to have started failing recently, but also could have been a bug introduced into mplayer as I upgraded both FreeBSD and mplayer at the same time. If it's a FreeBSD bug could someone take a look at fixing it, if it's not, does it hurt us too badly to special case /dev/zero for allowing this instead of EACCESS? -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684