Date: Thu, 16 Jul 1998 11:55:21 -0400 (EDT) From: woods@zeus.leitch.com To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: bin/7300: 'make release' process doesn't copy some device nodes to the 'bin' distribution Message-ID: <199807161555.LAA13294@brain.zeus.leitch.com>
next in thread | raw e-mail | index | archive | help
>Number: 7300 >Category: bin >Synopsis: 'make release' process doesn't copy some device nodes to the 'bin' distribution >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jul 16 09:00:01 PDT 1998 >Last-Modified: >Originator: Greg A. Woods >Organization: Planix, Inc.; Toronto, Ontario; Canada >Release: FreeBSD 2.2.6-STABLE i386 (cvsup'ed 980709) >Environment: FreeBSD brain.zeus.leitch.com 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Tue Jul 14 15:38:10 EDT 1998 woods@brain.zeus.leitch.com:/var/work.d/Leitch-BSD-2.2/sys/compile/BRAIN i386 >Description: During the "make release" process several error messages are printed regarding the inability of 'tar' to copy some device nodes when creating the 'bin' distribution. I don't think this is critical since /dev/MAKEDEV should be run on the target system anyway and that'll replace/repair any of the missing/broken nodes. >How-To-Repeat: Run "make release ..." in /usr/src/release Observe the following output: rolling bin/bin tarball tar: dev/wd0s3: minor number too large; not dumped tar: dev/rwd0s3: minor number too large; not dumped >Fix: Don't use tar to copy filesystems!!!!!!! I don't think tar can even be fixed to copy such devices, not without introducing the possibility of backward incompatability. (dump | restore) should work just fine. Pax may work OK too. >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807161555.LAA13294>