From owner-freebsd-stable Tue Jan 26 20:01:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19646 for freebsd-stable-outgoing; Tue, 26 Jan 1999 20:01:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA19638 for ; Tue, 26 Jan 1999 20:01:53 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 24343 invoked by uid 100); 27 Jan 1999 04:01:52 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Jan 1999 04:01:52 -0000 Date: Tue, 26 Jan 1999 20:01:52 -0800 (PST) From: Mike Meyer To: "Mike O'Dell" cc: freebsd-stable@FreeBSD.ORG Subject: Re: rm with no arguments... In-Reply-To: <199901270223.VAA49207@servo.ccr.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3.0R, rm with no arguments complains. rm -f with no arguments doesn't Date: Tue, 26 Jan 1999 21:23:24 -0500 (EST) > From: Mike O'Dell > To: freebsd-stable@FreeBSD.ORG > Subject: rm with no arguments... > > > it seems that "rm" with no arguments now whines about it with a > useage thing and there seems to be no way to get it to stop, so > it now urps into pipes and other things when it didn't before > > great > > export PLEASE_STOP_HELPING_ME=1 > > -mo > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message