From owner-freebsd-bugs Thu Jun 13 01:50:07 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA05920 for bugs-outgoing; Thu, 13 Jun 1996 01:50:07 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA05897; Thu, 13 Jun 1996 01:50:02 -0700 (PDT) Date: Thu, 13 Jun 1996 01:50:02 -0700 (PDT) Message-Id: <199606130850.BAA05897@freefall.freebsd.org> To: freebsd-bugs Cc: From: "Gary Palmer" Subject: Re: bin/1320: dump limits blocksize to 32K Reply-To: "Gary Palmer" Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/1320; it has been noted by GNATS. From: "Gary Palmer" To: gena@netvision.net.il Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/1320: dump limits blocksize to 32K Date: Thu, 13 Jun 1996 09:42:36 +0100 gena@netvision.net.il wrote in message ID <199606130916.LAA16644@Burka.NetVision.net.il>: > All this may be true (?) for local backup , but absolutely not > when using rdump. I back up my system on DLT SCSI tape connected > to Solaris system and tape's manuall says that blocksize = 126 > should be spcified. Your patch is wrong for just that reason ... it is true for local backups, and removing the code which does the check is hence incorrect. It should only ignore the blocksize for non-local backups, not ignore it totally. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info