From owner-freebsd-bugs Mon Jul 3 13: 1:41 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.102.114]) by hub.freebsd.org (Postfix) with ESMTP id 5CDD137BEFC for ; Mon, 3 Jul 2000 13:01:36 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.3) id NAA83953; Mon, 3 Jul 2000 13:01:28 -0700 (PDT) (envelope-from mph) Date: Mon, 3 Jul 2000 13:01:28 -0700 From: Matthew Hunt To: Sheldon Hearn Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/19611: ee silently overwrites write-protected files Message-ID: <20000703130127.A83401@wopr.caltech.edu> References: <200007030950.CAA47299@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200007030950.CAA47299@freefall.freebsd.org>; from sheldonh@uunet.co.za on Mon, Jul 03, 2000 at 02:50:03AM -0700 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jul 03, 2000 at 02:50:03AM -0700, Sheldon Hearn wrote: > At the moment, the software expects anyone running as root to be clueful > enough to realize that root pays no heed to file permissions. Well, vi(1) doesn't, and I think we generally expect vi(1) users to be at least as clueful as ee(1) users. > It _would_ be possible to pop a dialogue up when root is about to save > to a file which is read-only. If you feel that this is something you That's basically what vi(1) does, if you interpret "dialogue box" sufficiently liberally. What I'd really like is for ":w!" to work for regular users in vi(1) as well, provided I can chmod the file. Usually the only time the issue comes up is when some idiot makes a source tarball with Makefile mode 444. > I think it would be a bad idea for our ee to differ in its interface > from the standard ee, which new users often rely on. There's a standard ee(1)?! Wacky. Matt -- Matthew Hunt * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message