*BSD News Article 64219


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!howland.reston.ans.net!Germany.EU.net!Dortmund.Germany.EU.net!interface-business.de!usenet
From: j@ida.interface-business.de (J Wunsch)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: Re: Backup over a network
Date: 25 Mar 1996 10:50:30 GMT
Organization: interface business GmbH, Dresden
Lines: 36
Message-ID: <4j5tpm$le2@innocence.interface-business.de>
References: <31531627.30DA@cdepot.net> <4iv84r$bgl@moon.igcom.net>
Reply-To: joerg_wunsch@interface-business.de (Joerg Wunsch)
NNTP-Posting-Host: ida.interface-business.de
X-Newsreader: knews 0.9.3

david@terra.igcom.net (David B. Bauman) writes:

> : rdump 0ufB sinbad:/dev/nrst0 4000000 /
> 
> : and I get:
> 
> : Permission denied.
> : TCP_MAXSEG setsockopt: Bad file descriptor    

I don't know if BSDi has been fixing this:

This type of service is accomplished via the ``rmt'' protocol (see
rmt(8)).  Traditionally, rmt(8) used to live under /etc, hence this
effectively became the `protocol'.  (There's no written standard
protocol for rmt.)

When 4.4BSD (correctly) decided to remove all the binary cruft out of
/etc, they also did the mistake to drop any reference to rmt there.
However, since /etc/rmt must be known to the *remote* end, it cannot
be up to the decision of the local system where to keep it.  The only
solution is to create a symlink from /usr/sbin/rmt to /etc/rmt.

However, since the fathers of 4.4BSD knew that rmt doesn't reside
anymore under /etc, nor does it reside under /usr/sbin on most
machines, they did yet another mistake: their [r]dump/[r]restore
doesn't call rmt by an explicit path name, instead it relies on being
in the default ${PATH} of the user.  Alas, there's no way for
Bourne-alike shells to run any rc file when invoked via rsh, so you
can't even tweak the PATH.  (csh users can create a ~root/.cshrc.)
The fix is to use /etc/rmt again inside dump and restore.  (Obviously,
you need the sources for this.)

-- 
J"org Wunsch					       Unix support engineer
joerg_wunsch@interface-business.de       http://www.interface-business.de/~j