Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1325 ; Tue, 23 Feb 93 14:35:17 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!swrinde!zaphod.mps.ohio-state.edu!menudo.uh.edu!uuneo!sugar!karl From: karl@NeoSoft.com (Karl Lehenbauer) Subject: tar networked client/server works for 386BSD (hints included) Organization: NeoSoft Communications Services -- (713) 684-5900 Date: Sat, 13 Feb 1993 10:08:43 GMT Message-ID: <C2DtIo.Juw@sugar.neosoft.com> Lines: 25 Boy, whenever we dig into 386BSD we are astounded by how much is there and how well it works. Tonight we (Nick Handel <nhandel@neosoft.com> & I) looked into GNU tar's networked client-server ability to use tapedrives on other systems over the network. We were trying to back up a 1 gigabyte 386BSD machine onto a DAT drive on another 386BSD machine. To save you any suspense, it worked great. Well, it didn't work at first because GNU tar expects rmt to be in /etc, and it is in fact in /usr/sbin. The quick fix is: ln -s /usr/sbin/rmt /etc/rmt While it is trivial to patch tar to try to remotely invoke /usr/sbin/rmt, I don't know how many systems out there have it in /etc, anyway. If I don't hear some "leave it in /etc", a patch will be forthcoming for it to try to invoke rmt from /usr/sbin. -- -- Email info@NeoSoft.com for info on getting interactive Internet access. "I didn't have time to write a short letter, so I wrote a long one instead." -- Twain