From owner-freebsd-bugs Tue Jul 4 1: 0: 4 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0026537B65B for ; Tue, 4 Jul 2000 01:00:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id BAA44686; Tue, 4 Jul 2000 01:00:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 4 Jul 2000 01:00:01 -0700 (PDT) Message-Id: <200007040800.BAA44686@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/19611: ee silently overwrites write-protected files Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/19611; it has been noted by GNATS. From: Sheldon Hearn To: gerti@BITart.com Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/19611: ee silently overwrites write-protected files Date: Tue, 04 Jul 2000 09:53:49 +0200 On Mon, 03 Jul 2000 17:04:36 EST, Gerd Knops wrote: > Agreed. Actually the current ee behavior seems consistent with other > tools when used as root. I still think a warning would be in order for > any tool writing to a file without write permision, but reality is > different. At least one other person agrees with you that a warning is in order, since vi(1) gives a warning. So if you want to take this further, try to get hold of ee(1)'s author and see if he's happy with the idea. You can post his feedback as a follow-up to your own PR by making sure that you use this subject line and send a message to freebsd-gnats-submit@FreeBSD.org: Subject: Re: bin/19611: ee silently overwrites write-protected files Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message