Date: Tue, 13 Jun 1995 09:09:15 +0200 (MET DST) From: Michael Ruplitsch <ruplit@fitipc31.tu-graz.ac.at> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: freebsd-bugs@FreeBSD.org Subject: Re: dump having problems with remote tape drive Message-ID: <Pine.BSD.3.91.950613090104.20101A-100000@fitipc31.tu-graz.ac.at> In-Reply-To: <199506091735.TAA04032@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 9 Jun 1995, J Wunsch wrote: > As Michael Ruplitsch wrote: > > > > Hi, > Moin, Servus, > [...] > > Today I wanted to use `dump' to backup my hard drive onto a remote scsi tape > > drive. dump terminated with the message: > > Cannot open output "/dev/rmt/ctapen". > > > I found out that dump tries to open the remote tape for reading and > > writing (by sending "Otape-device\n2\n" to rmt where 2 means O_RDWR) > > instead of opening it for writing only (`1' instead of `2'). Is this a bug > > or is it a feature of dump? > > A feature. Why do you think _this_ might be the problem? > > [dump output deleted] > > Is there any reason why a tape driver should not allow an O_RDWR > access where it does allow O_WRONLY? Hmm, I don't think so. But on the other hand: what does dump need the read permission for? > Anyway, i found another bogon while i've been looking at this: dump > doesn't use an absolute path (/etc/rmt) as it ought to be; instead it > thinks it should rely on "rmt" only. As far as I know rmt does not live in /etc anymore. It's a link to /usr/sbin/rmt which is kept for reasons of backward compatibility. Slan, Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSD.3.91.950613090104.20101A-100000>