From owner-freebsd-current Thu Aug 3 10:21:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id KAA06425 for current-outgoing; Thu, 3 Aug 1995 10:21:17 -0700 Received: from eikon.regent.e-technik.tu-muenchen.de (eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id KAA06412 for ; Thu, 3 Aug 1995 10:21:05 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de ([129.187.142.36]) by eikon.regent.e-technik.tu-muenchen.de with SMTP id <55475>; Thu, 3 Aug 1995 19:20:21 +0200 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) id TAA00938 for current@freebsd.org; Thu, 3 Aug 1995 19:05:12 +0200 Date: Thu, 3 Aug 1995 19:05:12 +0200 From: Julian Howard Stacey Message-Id: <199508031705.TAA00938@vector.eikon.e-technik.tu-muenchen.de> To: current@freebsd.org Subject: Backup of 32bit dev entries Sender: current-owner@freebsd.org Precedence: bulk I've forgotten what we've got left that still works to make backups of current /dev entries. I tried these: tar cf /tmp/ttt . tar: rsd2s4h: minor number too large; not dumped pax -w -f /tmp/ttt * pax: Ustar header field is too small for rsd0.ctl find . -print | cpio -o > /tmp/ttt cpio: sd0 not dumped: device number would be truncated dump 0f /tmp/ttt . DUMP: bad sblock magic number The ENTIRE dump is aborted. Allowing 32 bits in before we could easily back them up seems strange, PS let's avoid a format zealot's session here, I guess we have have enough afficionados of each to want all commands to remain usable, if possible :-) Could we put specific examples in the manuals of those commands that are still capable of coping with our FreeBSD specific 32 bit devs, ie let's make it easy for people, no point forcing everyone who has known these commands for years to start poring through manuals, for a clue to defeating the 32bit devs backup problem. Julian S