From owner-freebsd-arch Fri Sep 15 14:25:34 2000 Delivered-To: freebsd-arch@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id E088737B424 for ; Fri, 15 Sep 2000 14:25:32 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id OAA76593; Fri, 15 Sep 2000 14:29:09 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200009152129.OAA76593@troutmask.apl.washington.edu> Subject: Re: Rsh/Rlogin/Rcmd & friends In-Reply-To: <20000915145337.Q40658@radon.gryphonsoft.com> from Will Andrews at "Sep 15, 2000 02:53:37 pm" To: Will Andrews Date: Fri, 15 Sep 2000 14:29:09 -0700 (PDT) Cc: arch@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will Andrews wrote: > On Fri, Sep 15, 2000 at 12:56:10PM -0700, 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? > > 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. > rdump/rrestore (on at least Tru64 Unix) expect to find /etc/rmt on the remote machine. Other non-FreeBSD Unices probably also expect to find /etc/rmt. troutmask:kargl[268] ls -l /etc/rmt l--------- 1 root wheel 13 Nov 17 1998 /etc/rmt@ -> /usr/sbin/rmt Are you advocating that your port will create the proper symlink? /etc/rmt@ -> /usr/local/sbin/rmt Isn't this against the principles of "The Ports Collection". Note rmt(8) states "Rmt is normally started up with an rexec(3) or rcmd(3) call." -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message