From owner-freebsd-doc Sun Mar 17 15:50: 6 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 34FDA37B400 for ; Sun, 17 Mar 2002 15:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2HNo2673749; Sun, 17 Mar 2002 15:50:02 -0800 (PST) (envelope-from gnats) Date: Sun, 17 Mar 2002 15:50:02 -0800 (PST) Message-Id: <200203172350.g2HNo2673749@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Giorgos Keramidas Subject: Re: docs/35940: red(1) manual doesn't explain red(1). Reply-To: Giorgos Keramidas Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35940; it has been noted by GNATS. From: Giorgos Keramidas To: "Gary W. Swearingen" Cc: bug-followup@freebsd.org Subject: Re: docs/35940: red(1) manual doesn't explain red(1). Date: Mon, 18 Mar 2002 01:44:47 +0200 On 2002-03-17 12:00, Gary W. Swearingen wrote: > I'd also be more accurate about what the "restrictions" are. For > instance, from my unfinished look at the code, it looked like it would > restrict one from editing "./xxx" which is in the current directory. > Maybe you should commit your change and leave the PR open in case > somebody later cares enough to improve it (or better, the program). Indeed. I'll try to come up with a more verbose description of the restrictions, trying not to duplicate the code "in words". hades:~$ red f ./foo ? h shell access restricted Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message