Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:3085 comp.os.386bsd.bugs:907 Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!ux1.cso.uiuc.edu!news.cs.indiana.edu!nstn.ns.ca!PHoward.StMarys.CA!PHILIP From: PHILIP@shark.stmarys.ca (Philip Howard (Computer Services)) Subject: Re: rdump problems rmtgets botched protocols Message-ID: <PHILIP.110.740168789@shark.stmarys.ca> Lines: 31 Sender: usenet@nstn.ns.ca (NNTP Entity) Organization: Saint Mary's University References: <1993Jun15.002126.2176@mnemosyne.cs.du.edu> Date: Tue, 15 Jun 1993 18:26:29 GMT In article <1993Jun15.002126.2176@mnemosyne.cs.du.edu> smace@nyx.cs.du.edu (Scott Mace) writes: >From: smace@nyx.cs.du.edu (Scott Mace) >Subject: rdump problems rmtgets botched protocols >Date: Tue, 15 Jun 93 00:21:26 GMT >I am having trouble getting my 386bsd system to dump to a netbsd system >I run rdump 0uf mace1:/dev/nrst0 >It comes back with something about >rmtgets: botched protocol >And terminates. > >386bsd system 00.2.3 netbsd system source dated jun 5 > >Scott Mace Yes, I have the exact same problem (386bsd, patchlevel 0.2.3). I posted it months ago and got no response other than a suggestion that the host system might not be properly configured... it was. We inspected the packets between the 386bsd and the VAX we use for remote tape backups. What we found was a message from the VAX to the 386bsd about command line parameters missing... or some such. Anyway, it looked as if the command line was not getting to the VAX as a single command. We have a Cisco router between the two, but no similar network problems have surfaced. We suspect the problem is with dump/rdump itself. On our net we have Sun and NeXT workstations which rdump just fine! I'd like to hear from anyone else who has heard of this problem. Perhaps we should continue this discussion in .bugs? Philip