From owner-freebsd-current Mon Nov 12 3:31:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D4E7C37B405 for ; Mon, 12 Nov 2001 03:31:35 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fACBVOB24583; Mon, 12 Nov 2001 06:31:25 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 12 Nov 2001 06:31:24 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Gordon Tetlow Cc: current@freebsd.org Subject: Re: /dev/null problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG So in theory this is fixed, but I actually bumped into an unexpected EPERM again from a linux emulated program yesterday (acroread4) which popped up an error message about /dev/null. I haven't tried to reproduce as yet, since I'm currently rebuilding KDE; /dev/null works properly for me on the FreeBSD ABI again, so maybe it's just a bug in acroread4. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sun, 11 Nov 2001, Gordon Tetlow wrote: > I was trying to build a package the other day, but I was having problems > with /dev/null. My world is from Nov 4th. > > drifter# ls -l /dev/null > crw-rw-rw- 1 root wheel 2, 2 Nov 11 16:56 /dev/null > drifter# echo > /dev/null > drifter# su - gordont > %echo > /dev/null > /dev/null: Operation not permitted. > %ls -l /dev/null > crw-rw-rw- 1 root wheel 2, 2 Nov 11 16:57 /dev/null > > Anyone else seeing this problem? > > -gordon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message