From owner-freebsd-arch Fri Sep 15 14:18:32 2000 Delivered-To: freebsd-arch@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 8823237B422 for ; Fri, 15 Sep 2000 14:18:30 -0700 (PDT) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA03480; Fri, 15 Sep 2000 17:18:12 -0400 (EDT) Date: Fri, 15 Sep 2000 17:18:12 -0400 (EDT) From: Daniel Eischen To: Will Andrews Cc: Will Andrews , Steve Kargl , arch@FreeBSD.ORG Subject: Re: Rsh/Rlogin/Rcmd & friends In-Reply-To: <20000915153602.S40658@radon.gryphonsoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Sep 2000, Will Andrews wrote: > On Fri, Sep 15, 2000 at 04:24:23PM -0400, Daniel Eischen wrote: > > > What consequences? Remember, we'll still have ports for these things. > > > It only matters as far as new installations go. Post-install operations > > > are unimportant. > > > > Wrong. If that were true tcsh wouldn't be in the base system today. > > You misinterpreted me. I meant in this specific case, post-install > operation doesn't matter. People can use ssh to get in the machines to > do things rsh/rlogin/rcmd offer. No, you haven't proven to me that removal of rsh/rlogin/rcmd doesn't break anything like remote backups. As Steve Kargl wrote: > > What are the consequences of your proposal with the use of > > rdump/rrestore from another (non-FreeBSD) machine into a > > tape drive equipped FreeBSD box? To me that means that something that use to work "out of the box" will not work without adding the necessary port(s). Sure, you can argue that you can easily install the port, but the same could be said to folks that wanted tcsh as their default shell. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message