From owner-freebsd-hackers Mon Jan 30 17:36:23 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA18073 for hackers-outgoing; Mon, 30 Jan 1995 17:36:23 -0800 Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.97.216]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id RAA18065 for ; Mon, 30 Jan 1995 17:36:21 -0800 Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.6.9/8.6.9) id RAA00240 for freebsd-hackers@freefall.cdrom.com; Mon, 30 Jan 1995 17:33:09 -0800 From: Steven G Kargl Message-Id: <199501310133.RAA00240@troutmask.apl.washington.edu> Subject: tar dumps core on 950112-SNAP To: freebsd-hackers@freefall.cdrom.com (FreeBSD) Date: Mon, 30 Jan 1995 17:33:07 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1740 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hackers, Simple question: should tar dump core if it tries to access /proc where /proc is, of course, mounted as a procfs? I am going to start to sup the -current tree, so I wanted to backup my entire system. I cd to / and simply issued `tar cvf /dev/rst0 .i >& tar.log &'. The system barfed on /proc. If /proc is unmounted the tar executes as expected. The following error message is printed to the console. Jan 30 16:29:31 troutmask /kernel: pid 115: tar: uid 0: exited on signal 11 Will a similar type of error occur with unionfs and memfs? On other note. I have built several programs from prep.ai.mit.edu (octave-1.1.0, Gnu make-3.71.1), ftp.cs.umb.edu (Karl Berry's distribution of TeX, dvipsk, and xdvik), and ftp.x.org (xfig-3.1.2, transfig-3.0) with very few problems. I quite impressive and thankful for the core team's sweat. One minor problem: Some programs include the following lines: #include int foo() { extern char *sys_errlist[]; .... } FreeBSD-2.[01].x declares extern __const char *__const sys_errlist[]; in stdio.h. gcc complains about the redeclaration, then halts compilation. I modified the sources to read #include #include int foo() { #if BSD < 199303 extern char *sys_errlist[]; #endif .... } Is this the proper way to handle the problem? Finally, I have unsubscribed to -hackers because of my $real$ work load. Please, email any response to me. I will re-subscribe when life calms down. -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Laboratory | Fax: 206-543-6785 | University of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.0-950112 | Seattle, WA 98105 | |