From owner-freebsd-current Sun Oct 18 00:02:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17914 for freebsd-current-outgoing; Sun, 18 Oct 1998 00:02:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17904 for ; Sun, 18 Oct 1998 00:02:14 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id OAA17728; Sun, 18 Oct 1998 14:55:57 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810180655.OAA17728@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Tom Jackson , Karl Pielorz , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: panic In-reply-to: Your message of "Sat, 17 Oct 1998 22:38:37 MST." <199810180538.WAA09998@dingo.cdrom.com> Date: Sun, 18 Oct 1998 14:55:56 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > *Bingo* no ahh shit! That fixed me here. > > > > I'm began running gpl_math_emulate so that the rc5des client would run on > > the Thinkpad. For your amusement, here's what I get if I change back to the > > straight math_emulate: > > > > -normal probes and swapon- > > /dev/wd0s1a: clean, 10064 [pid 10 (fsck),uid 0: exited on signal 10] > > Bus error > > Actually, that almost looks like no math emulator at all; there's an FP > calculation performed to print those stats, but it's just simple > division and the old emulator used to get that more or less right. Hmm.. I don't have any machines that don't have a FPU.. However, in trap.c, if there was no math emulator loaded, I'd have expected a SIGFPE, not a SIGBUS: if (!pmath_emulate) { i = SIGFPE; ucode = FPE_FPU_NP_TRAP; break; } Just to satisfy my curiosity, I'd like somebody to try this: Index: math_emulate.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/math_emulate.c,v retrieving revision 1.28 diff -c -3 -r1.28 math_emulate.c *** math_emulate.c 1998/10/16 03:54:59 1.28 --- math_emulate.c 1998/10/18 06:45:32 *************** *** 1578,1585 **** case MOD_LOAD: if (pmath_emulate) printf("Another Math emulator already present\n"); ! else pmath_emulate = math_emulate; break; case MOD_UNLOAD: if (pmath_emulate != math_emulate) { --- 1578,1587 ---- case MOD_LOAD: if (pmath_emulate) printf("Another Math emulator already present\n"); ! else { pmath_emulate = math_emulate; + printf("MATH_EMULATE activated\n"); + } break; case MOD_UNLOAD: if (pmath_emulate != math_emulate) { And make sure that it's actually being initialized... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 00:20:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18880 for freebsd-current-outgoing; Sun, 18 Oct 1998 00:20:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18875 for ; Sun, 18 Oct 1998 00:20:30 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id JAA08258; Sun, 18 Oct 1998 09:20:03 +0200 (SAT) From: John Hay Message-Id: <199810180720.JAA08258@zibbi.mikom.csir.co.za> Subject: Re: CVS corruption through cvs-cur.4733.gz In-Reply-To: <199810180638.IAA03066@gratis.grondar.za> from Mark Murray at "Oct 18, 98 08:38:15 am" To: mark@grondar.za (Mark Murray) Date: Sun, 18 Oct 1998 09:20:03 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > And there may be somthing with CTM delta generation - > > there is no new delta after 'cvs-cur.4733.gz'. > > The CTM builder is having a helluva hard time trying to connect to > cvsup.freebsd.org; obviously the world wants 3.0 really badly :-) Can't (shouldn't) the ctm builder machine get direct access to freefall? Surely it is important enough to go directly? (Another ctm user waiting for a cvs-cur with 3.0 tags.) John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 00:50:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20844 for freebsd-current-outgoing; Sun, 18 Oct 1998 00:50:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20771 for ; Sun, 18 Oct 1998 00:49:33 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id PAA19647; Sun, 18 Oct 1998 15:47:13 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810180747.PAA19647@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: modules/atapi change In-reply-to: Your message of "Sun, 18 Oct 1998 01:51:28 -0400." Date: Sun, 18 Oct 1998 15:47:12 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > Seems to be working just fine now :/ I'm insulted you think I wouldn't > have checked I was using the latest bsd.kmod.mk, had cleaned the dir, etc. > I tested it more than once, I'm not just some luser that goes around > saying "this is broken, fix it" without even thinking about what the > problem could be. Anyway, it seems to be Just A Fluke. No need to be insulted, I was just checking to make sure that all the bases were covered. If you read it as insulting, then I'm sorry, it wasn't meant that way. > Cheers, > Brian Feldman Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 01:15:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22519 for freebsd-current-outgoing; Sun, 18 Oct 1998 01:15:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22488 for ; Sun, 18 Oct 1998 01:15:26 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA09674; Sun, 18 Oct 1998 18:09:20 +1000 Date: Sun, 18 Oct 1998 18:09:20 +1000 From: Bruce Evans Message-Id: <199810180809.SAA09674@godzilla.zeta.org.au> To: jhay@mikom.csir.co.za, mark@grondar.za Subject: Re: CVS corruption through cvs-cur.4733.gz Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Can't (shouldn't) the ctm builder machine get direct access to freefall? >Surely it is important enough to go directly? > >(Another ctm user waiting for a cvs-cur with 3.0 tags.) CTM always gets behind when the tree is tagged. I'm waiting for both tags and the final module breakage commit :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 02:18:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26776 for freebsd-current-outgoing; Sun, 18 Oct 1998 02:18:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26748; Sun, 18 Oct 1998 02:18:40 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id LAA12711; Sun, 18 Oct 1998 11:18:04 +0200 (CEST) (envelope-from sos) Message-Id: <199810180918.LAA12711@sos.freebsd.dk> Subject: Re: softupdates/smp In-Reply-To: from Julian Elischer at "Oct 17, 98 07:21:28 pm" To: julian@whistle.com (Julian Elischer) Date: Sun, 18 Oct 1998 11:18:04 +0200 (CEST) Cc: donegan@quick.net, chuckr@mat.net, sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Julian Elischer who wrote: > Well I'm doing it, but I've 'left off' development until the > ELF/CAM/3.0/etc changes all settle down. > > looks to me as if someone has broken it again. > I'll be in europe for a fortnight. When I get back > I hope things will have settled down enough for me to look at it again. Erhm, I've never seen it work reliably under SMP, did you ever get the giant lock prims into the syncer ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 02:56:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28818 for freebsd-current-outgoing; Sun, 18 Oct 1998 02:56:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from teethies.nelefa.org (usr157-edi.cableinet.co.uk [194.117.147.167]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28804 for ; Sun, 18 Oct 1998 02:56:16 -0700 (PDT) (envelope-from jmd@nelefa.org) Received: from localhost (localhost [127.0.0.1]) by teethies.nelefa.org (8.8.8/8.8.8) with SMTP id KAA02651 for ; Sun, 18 Oct 1998 10:55:33 +0100 (BST) (envelope-from jmd@nelefa.org) Date: Sun, 18 Oct 1998 10:55:33 +0100 (BST) From: John Dow X-Sender: jmd@teethies To: freebsd-current@FreeBSD.ORG Subject: subscribe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe John Dow cat man du : where UNIX geeks go when they die To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 05:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12051 for freebsd-current-outgoing; Sun, 18 Oct 1998 05:17:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12044 for ; Sun, 18 Oct 1998 05:17:21 -0700 (PDT) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id OAA05194 for freebsd-current@FreeBSD.ORG; Sun, 18 Oct 1998 14:13:59 +0200 (CEST) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199810181213.OAA05194@ocean.campus.luth.se> Subject: make world breakage To: freebsd-current@FreeBSD.ORG Date: Sun, 18 Oct 1998 14:13:58 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! A friend of mine is having a problem with his make world. He's running on a K6 machine with FreeBSD 3.0-19981012-BETA installed, and he cvsuped and made the world and it failed, and he has cvsuped a few times now but still always gets the same error. It seems a bit weird. BTW, I tried searching the mail archives and ALL messages that came up "could not be accessed". Someone need to check the cgi stuff there I think. Also, there's no tip on how to search for a sequence of words, like "a blue banana" that wouldn't also match "a banana blue". Isn't it possible? Anyway... His make world ends like this: ===> gnu/usr.bin/perl ===> gnu/usr.bin/perl/libperl ===> gnu/usr.bin/perl/miniperl sh config_h.sh Extracting config.h (with variable substitutions) cc -O2 -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlmain.c cc -O2 -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/elf/usr/src/tmp/usr/include -static -o miniperl miniperlmain.o -lperl -lm -lcrypt ===> gnu/usr.bin/perl/perl sh config_h.sh Extracting config.h (with variable substitutions) sh writemain.sh Extracting writemain (with variable substitutions) sh writemain lib/auto/DynaLoader/DynaLoader.a > perlmain.c cc -O2 -pipe -I/usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5 -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl -I/usr/obj/elf/usr/src/tmp/usr/include -c perlmain.c miniperl /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm Config.pm Porting/Glossary myconfig config.sh cd lib ; ln -sf ../Config.pm miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib -e 'use AutoSplit; autosplit_lib_modules(@ARGV)' lib/*.pm lib/*/*.pm AutoSplitting lib/Getopt/Long.pm (lib/auto/Getopt/Long) touch autosplit sh cflags.sh Extracting cflags (with variable substitutions) cd ext/DynaLoader; miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=static INSTALLDIRS=perl PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/elf/usr/src/tmp/usr/share/perl/man3; make -B config PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl Writing Makefile for DynaLoader mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader cd ext/DynaLoader; make -B all PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl /usr/obj/elf/usr/src/tmp/usr/bin/miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib DynaLoader_pm.PL cp DynaLoader.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/DynaLoader.pm AutoSplitting /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/DynaLoader.pm (/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader) cp dl_dlopen.xs DynaLoader.xs /usr/obj/elf/usr/src/tmp/usr/bin/miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp -noprototypes -typemap /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/typemap DynaLoader.xs >xstmp.c && mv xstmp.c DynaLoader.c cc -c -DVERSION=\"1.03\" -DXS_VERSION=\"1.03\" -DPIC -fpic -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl -DPERL_CORE -DLIBC="" DynaLoader.c rm -rf /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader/DynaLoader.a ar cr /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader/DynaLoader.a DynaLoader.o && ranlib /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader/DynaLoader.a chmod 755 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader/DynaLoader.a cc -O2 -pipe -I/usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5 -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl -I/usr/obj/elf/usr/src/tmp/usr/include -o perl perlmain.o lib/auto/DynaLoader/DynaLoader.a -lperl -lm -lcrypt ln -sf /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/pod/pod2man.PL miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib pod2man.PL Extracting pod2man (with variable substitutions) cd ext/B; miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/elf/usr/src/tmp/usr/share/perl/man3 INST_LIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B INST_ARCHLIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B ; make -B config PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl Writing Makefile for B mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/auto mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/auto/B cd ext/B; make -B all PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl cp B/Deparse.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Deparse.pm cp B/CC.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/CC.pm cp B/Debug.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Debug.pm cp B/Showlex.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Showlex.pm cp B/makeliblinks /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/makeliblinks cp B/Bblock.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Bblock.pm cp B/cc_harness /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/cc_harness cp B/Bytecode.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Bytecode.pm cp B.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B.pm cp B/Stackobj.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Stackobj.pm cp B/Xref.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Xref.pm cp B/Lint.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Lint.pm cp B/Asmdata.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Asmdata.pm cp B/Assembler.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Assembler.pm cp O.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/O.pm cp B/Disassembler.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Disassembler.pm cp B/disassemble /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/disassemble cp B/assemble /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/assemble cp B/Terse.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/Terse.pm cp B/C.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/B/C.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/perl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp -typemap /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/typemap -typemap typemap B.xs >B.tc && mv B.tc B.c cc -c -DVERSION=\"a5\" -DXS_VERSION=\"a5\" -DPIC -fpic -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl B.c Running Mkbootstrap for B () chmod 644 B.bs ld -o /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/auto/B/B.so -shared B.o -lperl chmod 755 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/auto/B/B.so cp B.bs /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/auto/B/B.bs chmod 644 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/B/auto/B/B.bs cd ext/DB_File; miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/elf/usr/src/tmp/usr/share/perl/man3 INST_LIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File INST_ARCHLIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File ; make -B config PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl Writing Makefile for DB_File mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File/auto mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File/auto/DB_File cd ext/DB_File; make -B all PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl cp DB_File.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File/DB_File.pm AutoSplitting /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File/DB_File.pm (/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File/auto/DB_File) /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/perl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp -noprototypes -typemap /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/typemap -typemap typemap DB_File.xs >DB_File.tc && mv DB_File.tc DB_File.c cc -c -DVERSION=\"1.60\" -DXS_VERSION=\"1.60\" -DPIC -fpic -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl DB_File.c Running Mkbootstrap for DB_File () chmod 644 DB_File.bs ld -o /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File/auto/DB_File/DB_File.so -shared DB_File.o -lperl chmod 755 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File/auto/DB_File/DB_File.so cp DB_File.bs /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File/auto/DB_File/DB_File.bs chmod 644 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/DB_File/auto/DB_File/DB_File.bs cd ext/Data/Dumper; miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/elf/usr/src/tmp/usr/share/perl/man3 INST_LIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper INST_ARCHLIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper ; make -B config PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl Writing Makefile for Data::Dumper mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper/Data mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper/auto mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper/auto/Data mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper/auto/Data/Dumper cd ext/Data/Dumper; make -B all PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl cp Dumper.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper/Data/Dumper.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/perl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp -typemap /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/typemap Dumper.xs >Dumper.tc && mv Dumper.tc Dumper.c cc -c -DVERSION=\"2.09\" -DXS_VERSION=\"2.09\" -DPIC -fpic -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl Dumper.c Running Mkbootstrap for Data::Dumper () chmod 644 Dumper.bs ld -o /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper/auto/Data/Dumper/Dumper.so -shared Dumper.o -lperl chmod 755 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper/auto/Data/Dumper/Dumper.so cp Dumper.bs /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper/auto/Data/Dumper/Dumper.bs chmod 644 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Data/Dumper/auto/Data/Dumper/Dumper.bs cd ext/Fcntl; miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/elf/usr/src/tmp/usr/share/perl/man3 INST_LIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Fcntl INST_ARCHLIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Fcntl ; make -B config PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl Writing Makefile for Fcntl mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Fcntl mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/auto mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/auto/Fcntl cd ext/Fcntl; make -B all PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl cp Fcntl.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/Fcntl.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/perl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp -noprototypes -typemap /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/typemap Fcntl.xs >Fcntl.tc && mv Fcntl.tc Fcntl.c cc -c -DVERSION=\"1.03\" -DXS_VERSION=\"1.03\" -DPIC -fpic -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl Fcntl.c Running Mkbootstrap for Fcntl () chmod 644 Fcntl.bs ld -o /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/auto/Fcntl/Fcntl.so -shared Fcntl.o -lperl chmod 755 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/auto/Fcntl/Fcntl.so cp Fcntl.bs /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/auto/Fcntl/Fcntl.bs chmod 644 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/auto/Fcntl/Fcntl.bs cd ext/IO; miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/elf/usr/src/tmp/usr/share/perl/man3 INST_LIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO INST_ARCHLIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO ; make -B config PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl Writing Makefile for IO mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/auto mkdir /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/auto/IO cd ext/IO; make -B all PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl cp lib/IO/File.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/IO/File.pm cp lib/IO/Select.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/IO/Select.pm cp lib/IO/Socket.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/IO/Socket.pm cp IO.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/IO.pm cp lib/IO/Handle.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/IO/Handle.pm cp lib/IO/Seekable.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/IO/Seekable.pm cp lib/IO/Pipe.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/IO/Pipe.pm /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/perl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp -noprototypes -typemap /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/typemap IO.xs >IO.tc && mv IO.tc IO.c cc -c -DVERSION=\"1.1505\" -DXS_VERSION=\"1.15\" -DPIC -fpic -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl IO.c Running Mkbootstrap for IO () chmod 644 IO.bs ld -o /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/auto/IO/IO.so -shared IO.o -lperl chmod 755 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/auto/IO/IO.so cp IO.bs /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/auto/IO/IO.bs chmod 644 /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IO/auto/IO/IO.bs cd ext/IPC/SysV; miniperl -I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/elf/usr/src/tmp/usr/share/perl/man3 INST_LIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IPC/SysV INST_ARCHLIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IPC/SysV ; make -B config PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl Checking if your kit is complete... Looks good Writing Makefile for IPC::SysV Makefile out-of-date with respect to Makefile.PL Cleaning current config before rebuilding Makefile... make -f Makefile.old clean > /dev/null 2>&1 || /bin/sh -c true /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/perl "-I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib" "-I/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib" Makefile.PL "LINKTYPE=dynamic" "INSTALLDIRS=perl" "PERL_SRC=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl" "LIBS=-lperl" "INSTALLMAN3DIR=/usr/obj/elf/usr/src/tmp/usr/share/perl/man3" "INST_LIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IPC/SysV" "INST_ARCHLIB=/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/build/IPC/SysV" Checking if your kit is complete... Looks good Writing Makefile for IPC::SysV ==> Your Makefile has been rebuilt. <== ==> Please rerun the make command. <== false *** Error code 1 Stop. Huh? Re-running make world doesn't work, no. Seems it wants us to do a make again somewhere, but shouldn't the make world handle that? Also, WHERE should I run this command, or is where some other problem here? I can't seem to find anythign wrong with his setup... his /etc/objformat contains "OBJFORMAT=elf", if that's of interest. I'm unable to help me... so now I'm asking you guys... And mark (?) especially... What's wrong with perl here? /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 08:19:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23720 for freebsd-current-outgoing; Sun, 18 Oct 1998 08:19:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23715 for ; Sun, 18 Oct 1998 08:19:56 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id RAA27404; Sun, 18 Oct 1998 17:23:39 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 18 Oct 1998 17:23:39 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Karl Pielorz cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Latest kernel In-Reply-To: <36290E93.139108FE@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Oct 1998, Karl Pielorz wrote: > In your kernel config, give this a try: > > config kernel root on XXX dumps on da0s1b > > Where XXX should already be your root filesystem... BE WARNED - in LINT it > doesn't recomend this, I don't know how reliable specifiying the dump device > is here! There's yet another method I don't recommend :-) but I was once desperate enough to use it, and it worked... Be warned though - it's ugly and it can chop your disk in pieces if your finger slips... Step #1: boot machine with known working kernel, drop it to DDB (Ctl-Alt-Esc) and see what is the value of _dumpdev (x/wx _dumpdev), and jot it down. Then exit DDB and shutdown the machine. Step #2: boot machine with the bad kernel. When it panics, and you're in DDB, see the value of _dumpdev, and if it's different, set it to the previous value (w/w _dumpdev 0 1 2 3 ). Step #3: enter "panic". It should dump core to the location pointed by _dumpdev. If it doesn't, not all is lost yet - you can directly call boot(0x104), or if it can't sync disks, boot(0x100). If this fails, the things are really bad, and only remote GDB can help you to debug the problem... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 09:49:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11723 for freebsd-current-outgoing; Sun, 18 Oct 1998 09:49:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11698 for ; Sun, 18 Oct 1998 09:49:12 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id MAA15308 for ; Sun, 18 Oct 1998 12:48:40 -0400 (EDT) Date: Sun, 18 Oct 1998 12:48:39 -0400 (EDT) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: mount flags Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a hard time trying to decide where to post this. It's about a problem that's come up in fixing a broken port (which would mean ports list, usually) but it's a filesystem hacking problem (which would mean hackers), excepting that it hasn't anything at all to do with any system but current. I'm posting to current, and accepting all boos graciously. I have a very recently broke thing that was happily using a call to statfs, to tell if it was an NFS filesystem or not. Last time I had occasion to take a look at this, there were flags of the sort MOUNT_XXX, where the XXX could have been UFS, MFS, NFS, etc. The application is specifically looking for MOUNT_NFS, and it's just not around anymore, that I can find. I would be happy to find it, but I suspect that the method for detecting an NFS mounted FS has changed, so that the app should no longer use statfs. That's kind of odd, because this port works on a lot of other systems which seem to do that fine. Anyhow, anyone got a recommendation on how to change this thing so that it works under current? A real short history on what's changed in regards to this would be a nice thing to stick in the mail archives. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 09:55:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12612 for freebsd-current-outgoing; Sun, 18 Oct 1998 09:55:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silverback.gorilla.net (silverback.gorilla.net [208.128.8.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA12600 for ; Sun, 18 Oct 1998 09:55:07 -0700 (PDT) (envelope-from tom@gorilla.net) Received: from peeper.TOJ.org [208.143.84.62] by silverback.gorilla.net with ESMTP (SMTPD32-4.07) id AC4214F00CE; Sun, 18 Oct 1998 11:50:10 CDT Received: (from tom@localhost) by peeper.TOJ.org (8.9.1/8.8.8) id LAA04691; Sun, 18 Oct 1998 11:54:39 -0500 (CDT) (envelope-from tom) Message-ID: <19981018115408.A4680@TOJ.org> Date: Sun, 18 Oct 1998 11:54:08 -0500 From: Tom Jackson To: Peter Wemm , Mike Smith Cc: Karl Pielorz , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: panic References: <199810180538.WAA09998@dingo.cdrom.com> <199810180655.OAA17728@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810180655.OAA17728@spinner.netplex.com.au>; from Peter Wemm on Sun, Oct 18, 1998 at 02:55:56PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter, With the patch, I get the printf MATH_EMULATE activated. All the faults are the same. I missed one: recording kernel -c changes additional daemons: syslogdOct 18 11:15:20 slim /kernel.math: pid 10 (fsck), uid 0:exited on signal 10 When I am finally running, top faults with signal 10, ps functions okay. I also noticed a lockup of the boot loader at the loader prompt for the first time. Had to use reset to free it. On Sun, Oct 18, 1998 at 02:55:56PM +0800, Peter Wemm wrote: > Mike Smith wrote: > > > *Bingo* no ahh shit! That fixed me here. > > > > > > I'm began running gpl_math_emulate so that the rc5des client would run on > > > the Thinkpad. For your amusement, here's what I get if I change back to the > > > straight math_emulate: > > > > > > -normal probes and swapon- > > > /dev/wd0s1a: clean, 10064 [pid 10 (fsck),uid 0: exited on signal 10] > > > Bus error > > > > Actually, that almost looks like no math emulator at all; there's an FP > > calculation performed to print those stats, but it's just simple > > division and the old emulator used to get that more or less right. > > Hmm.. I don't have any machines that don't have a FPU.. > > However, in trap.c, if there was no math emulator loaded, I'd have > expected a SIGFPE, not a SIGBUS: > if (!pmath_emulate) { > i = SIGFPE; > ucode = FPE_FPU_NP_TRAP; > break; > } > > Just to satisfy my curiosity, I'd like somebody to try this: > Index: math_emulate.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/i386/math_emulate.c,v > retrieving revision 1.28 > diff -c -3 -r1.28 math_emulate.c > *** math_emulate.c 1998/10/16 03:54:59 1.28 > --- math_emulate.c 1998/10/18 06:45:32 > *************** > *** 1578,1585 **** > case MOD_LOAD: > if (pmath_emulate) > printf("Another Math emulator already present\n"); > ! else > pmath_emulate = math_emulate; > break; > case MOD_UNLOAD: > if (pmath_emulate != math_emulate) { > --- 1578,1587 ---- > case MOD_LOAD: > if (pmath_emulate) > printf("Another Math emulator already present\n"); > ! else { > pmath_emulate = math_emulate; > + printf("MATH_EMULATE activated\n"); > + } > break; > case MOD_UNLOAD: > if (pmath_emulate != math_emulate) { > > And make sure that it's actually being initialized... > > Cheers, > -Peter > > > -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 09:58:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13207 for freebsd-current-outgoing; Sun, 18 Oct 1998 09:58:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13197 for ; Sun, 18 Oct 1998 09:58:15 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id AAA01806; Mon, 19 Oct 1998 00:57:06 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810181657.AAA01806@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-reply-to: Your message of "Sun, 18 Oct 1998 12:48:39 -0400." Date: Mon, 19 Oct 1998 00:57:06 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: [..] > I have a very recently broke thing that was happily using a call to > statfs, to tell if it was an NFS filesystem or not. Last time I had > occasion to take a look at this, there were flags of the sort MOUNT_XXX, > where the XXX could have been UFS, MFS, NFS, etc. The application is > specifically looking for MOUNT_NFS, and it's just not around anymore, > that I can find. > > I would be happy to find it, but I suspect that the method for detecting > an NFS mounted FS has changed, so that the app should no longer use > statfs. That's kind of odd, because this port works on a lot of other > systems which seem to do that fine. What's wrong with the f_fstypename[] field in struct statfs? It'll contain a string "nfs" or "ufs" etc.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 10:02:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13723 for freebsd-current-outgoing; Sun, 18 Oct 1998 10:02:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13711 for ; Sun, 18 Oct 1998 10:02:34 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id SAA00864; Sun, 18 Oct 1998 18:02:00 +0100 (BST) Date: Sun, 18 Oct 1998 18:02:00 +0100 (BST) From: Karl Pielorz To: Andrzej Bialecki cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Latest kernel In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Oct 1998, Andrzej Bialecki wrote: > There's yet another method I don't recommend :-) but I was once desperate > enough to use it, and it worked... Be warned though - it's ugly and it can > chop your disk in pieces if your finger slips... > > [ nasty kernel 'magic' removed ;-) ] I had actually thought you might be able to mess around with the dumpdev etc. - but this falls into my current category of "Learn more before opening box" ;-) I'll keep it filed though - just in case Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 10:17:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15006 for freebsd-current-outgoing; Sun, 18 Oct 1998 10:17:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14999 for ; Sun, 18 Oct 1998 10:17:41 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id NAA15408; Sun, 18 Oct 1998 13:16:28 -0400 (EDT) Date: Sun, 18 Oct 1998 13:16:28 -0400 (EDT) From: Chuck Robey To: Peter Wemm cc: freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-Reply-To: <199810181657.AAA01806@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Peter Wemm wrote: > Chuck Robey wrote: > [..] > > I have a very recently broke thing that was happily using a call to > > statfs, to tell if it was an NFS filesystem or not. Last time I had > > occasion to take a look at this, there were flags of the sort MOUNT_XXX, > > where the XXX could have been UFS, MFS, NFS, etc. The application is > > specifically looking for MOUNT_NFS, and it's just not around anymore, > > that I can find. > > > > I would be happy to find it, but I suspect that the method for detecting > > an NFS mounted FS has changed, so that the app should no longer use > > statfs. That's kind of odd, because this port works on a lot of other > > systems which seem to do that fine. > > What's wrong with the f_fstypename[] field in struct statfs? It'll > contain a string "nfs" or "ufs" etc.. I looked in the statfs man page and couldn't see any kind of definition of what went in that field (so as to use it to choose from). I took a quick look at the code, nothing immediately jumps out at me ... for an external system interface, it's certainly obscurely set up, isn't it? Do you know where the derivation of the f_fstypename values comes from? I just can't find it. > > Cheers, > -Peter > > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 10:41:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17378 for freebsd-current-outgoing; Sun, 18 Oct 1998 10:41:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17372 for ; Sun, 18 Oct 1998 10:40:46 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id BAA01986; Mon, 19 Oct 1998 01:39:33 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810181739.BAA01986@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-reply-to: Your message of "Sun, 18 Oct 1998 13:16:28 -0400." Date: Mon, 19 Oct 1998 01:39:32 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > On Mon, 19 Oct 1998, Peter Wemm wrote: > > > Chuck Robey wrote: > > [..] > > > I have a very recently broke thing that was happily using a call to > > > statfs, to tell if it was an NFS filesystem or not. Last time I had > > > occasion to take a look at this, there were flags of the sort MOUNT_XXX, > > > where the XXX could have been UFS, MFS, NFS, etc. The application is > > > specifically looking for MOUNT_NFS, and it's just not around anymore, > > > that I can find. > > > > > > I would be happy to find it, but I suspect that the method for detecting > > > an NFS mounted FS has changed, so that the app should no longer use > > > statfs. That's kind of odd, because this port works on a lot of other > > > systems which seem to do that fine. > > > > What's wrong with the f_fstypename[] field in struct statfs? It'll > > contain a string "nfs" or "ufs" etc.. > > I looked in the statfs man page and couldn't see any kind of definition > of what went in that field (so as to use it to choose from). I took a > quick look at the code, nothing immediately jumps out at me ... for an > external system interface, it's certainly obscurely set up, isn't it? > > Do you know where the derivation of the f_fstypename values comes from? > I just can't find it. Hmm.. Now that you mention it... I don't see where it's being set either. I'm not sure that it is being set at all... :-( Short term hack: look at f_type in the statfs struct, and use the getvfsent() routines to map that back into a type name. According to : /usr/include/sys/mount.h:struct ovfsconf *getvfsbytype __P((int)); This is a bit of a kludge but it should work. struct ovfsconf has a char vfc_name[32] field. In these instances, the strings come from a result of the VFS_SET() macro and the configuration data it creates. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 11:18:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20386 for freebsd-current-outgoing; Sun, 18 Oct 1998 11:18:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20368 for ; Sun, 18 Oct 1998 11:18:42 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from speednet.com.au (zippy.zippynet.iol.net.au [172.22.2.8]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id EAA16852; Mon, 19 Oct 1998 04:16:31 +1000 (EST) Message-ID: <362A307E.8C676700@speednet.com.au> Date: Mon, 19 Oct 1998 04:16:30 +1000 From: Andy Farkas Organization: Speed Internet Services X-Mailer: Mozilla 4.07 [en] (WinNT; I) MIME-Version: 1.0 To: Chuck Robey CC: freebsd-current@FreeBSD.ORG Subject: Re: mount flags References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > I have a very recently broke thing that was happily using a call to > statfs, to tell if it was an NFS filesystem or not. Last time I had > occasion to take a look at this, there were flags of the sort MOUNT_XXX, > where the XXX could have been UFS, MFS, NFS, etc. The application is > specifically looking for MOUNT_NFS, and it's just not around anymore, > that I can find. Yeah, something fishy is going on here with statfs(2). According to the man page on a 2.2.7 system, and in , there are definitions for struct statfs->f_type, but on a 3.0-current, they have strangely disappeared. > Anyhow, anyone got a recommendation on how to change this thing so that > it works under current? You're not trying to compile Midnight Commander are you? If so, add "#define NO_INFOMOUNT 1" to config.h as a workaround .... > A real short history on what's changed in > regards to this would be a nice thing to stick in the mail archives. Me too! -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:01:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08661 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:01:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08655 for ; Sun, 18 Oct 1998 14:01:31 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA16024; Sun, 18 Oct 1998 14:01:08 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma016022; Sun Oct 18 14:00:46 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA09695; Sun, 18 Oct 1998 14:00:45 -0700 (PDT) From: Archie Cobbs Message-Id: <199810182100.OAA09695@bubba.whistle.com> Subject: Re: netscape in -current is broked In-Reply-To: <36276E5F.CAF7B06F@gorean.org> from Studded at "Oct 16, 98 09:03:43 am" To: Studded@gorean.org (Studded) Date: Sun, 18 Oct 1998 14:00:45 -0700 (PDT) Cc: croot@btp1da.phy.uni-bayreuth.de, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Studded writes: > Werner Griessl wrote: > > You need the old aout-Xlibs for netscape: > > Forgive me if this is a silly question, but has anyone tried linking > the old names to the new libraries? That won't work because the old libs are a.out format and the new ones (in the case of this thread) are elf format. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:04:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09061 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:04:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09047 for ; Sun, 18 Oct 1998 14:04:38 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id NAA15869; Sun, 18 Oct 1998 13:56:33 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd015848; Sun Oct 18 13:56:25 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id NAA10501; Sun, 18 Oct 1998 13:56:25 -0700 (MST) From: Terry Lambert Message-Id: <199810182056.NAA10501@usr07.primenet.com> Subject: Re: -current NFS problem To: joelh@gnu.org (Joel Ray Holveck) Date: Sun, 18 Oct 1998 20:56:24 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <86d87soga3.fsf@detlev.UUCP> from "Joel Ray Holveck" at Oct 16, 98 07:14:12 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > David Greenman poseted a vnode locking patch to the -hackers list > > some months ago that I believe would fix this particular problem > > for you. > > Is it being reviewed by anybody for inclusion in -current? I don't know; it may in fact be in -current. You should check the -hackers list for the patch, and then check th -current code and see if it was included. I'd be surprised if he made a patch, got good reports about it, and didn't subsequently check it into -current. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:09:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09508 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:09:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09496; Sun, 18 Oct 1998 14:09:53 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id NAA23038; Sun, 18 Oct 1998 13:55:01 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd023027; Sun Oct 18 13:55:00 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id NAA10435; Sun, 18 Oct 1998 13:54:56 -0700 (MST) From: Terry Lambert Message-Id: <199810182054.NAA10435@usr07.primenet.com> Subject: Re: wine on current: bad system call (semsys) To: mathiasp@virtual-earth.de (Mathias Picker) Date: Sun, 18 Oct 1998 20:54:56 +0000 (GMT) Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG In-Reply-To: <199810161211.OAA02251@mp.virtual-earth.de> from "Mathias Picker" at Oct 16, 98 02:11:57 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After conversion to current/elf and recompiling wine it crashes with > bad system call. A backtrace shows semsys to be the last call, and I > can see semsys in sys/syscall-hide.h. Since the port doesn't do anything > about it and it worked in -stable I guess this is a recent change ?!? > > I don't know if this is a ports or current problem, but has anyone any > idea how to fix it? I really need wine to run QuickBooks. You didn't say how the call was crashing; if it's due to a SIGSYS (this is a FreeBSD'ism; the correct POSIX dictated behaviour is to return an error from the call, and set the errno to ENOSYS), then it failed because the code implementing the system call is not in your kernel. Most likely, you need to rebuild your kernel to include the System V semaphore code (and throw in messaging and shared memory for good measure; if a programmer uses one System V specific wart, there's a good change he or she will use more). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:10:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09649 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:10:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09643; Sun, 18 Oct 1998 14:10:57 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA18830; Sun, 18 Oct 1998 14:10:33 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd018808; Sun Oct 18 14:10:27 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA11047; Sun, 18 Oct 1998 14:10:19 -0700 (MST) From: Terry Lambert Message-Id: <199810182110.OAA11047@usr07.primenet.com> Subject: Re: Never ending 'make clean' in kde port? To: rkw@Dataplex.NET (Richard Wackerbarth) Date: Sun, 18 Oct 1998 21:10:19 +0000 (GMT) Cc: dholland@cs.toronto.edu, asami@FreeBSD.ORG, kpielorz@tdx.co.uk, eivind@yes.no, current@FreeBSD.ORG In-Reply-To: from "Richard Wackerbarth" at Oct 16, 98 10:36:19 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >Why? Probably because some of the operations on the dependency graph > > > >are slower than O(n). > > > > > > I think that his comparison was based, in part, on the idea that you > > > have to do many things repeatedly simply because you do not have the > > > proper dependencies available. > > > >This is sometimes true, but in my experience it really doesn't happen > >very often. > > > >*shrug* > > I disagree. Just look at the convoluted structure of "make world" > or, the "make clean" in ports. Or just try (cd /usr/src; make ; make) > > I see it far too often. :-( Which is throwing out the baby with the bathwater. The correct thing to do is to explicitly specify dependencies. For things like second order effects, it's important to build using the headers in the source tree, and not the installed headers, and to realize that this means that you are building for a system built from the tree, and not for the currently installed system, whatever that may unguessably be. The lack of explicit dependencies in the source tree is the true source of the observed chaos. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:12:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09780 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:12:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09768 for ; Sun, 18 Oct 1998 14:12:40 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id OAA06041; Sun, 18 Oct 1998 14:12:30 -0700 (PDT) Message-Id: <199810182112.OAA06041@implode.root.com> To: Terry Lambert cc: green@zone.syracuse.NET, grog@lemis.com, julian@whistle.com, mike@smith.net.au, bag@sinbin.demos.su, rock@cs.uni-sb.de, current@FreeBSD.ORG Subject: Re: -current NFS problem In-reply-to: Your message of "Sun, 18 Oct 1998 20:48:29 -0000." <199810182048.NAA10205@usr07.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 18 Oct 1998 14:12:30 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Actually that's not true. I can't speak for all of the NFS implementations >> above, but at least in BSD/OS, it works only because they have warts all over >> the place to sidestep the problems with not having FS node locking. > >OK, after having spent several hours trying to see what you mean >here, I'm having a hard time understanding why locking the vnode >that holds the pointer to the nfsnode data is not an implicit lock >on the underlying nfsnode, just as it is for all other data that >the vnode references. Because there is no such thing as a "vnode lock", despite the terminology that we use in describing it. The lock state is stored in the attached fsnode, not in the vnode. For FFS, it is stored in a lock struct that is the first item in the in-core inode. In the special case of NFS, it's not stored at all. This means that VOP_LOCK()/VOP_UNLOCK() do nothing useful for NFS and this exposes all sorts of bugs in code that assumes that they do. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:13:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09857 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:13:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09836 for ; Sun, 18 Oct 1998 14:13:35 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id NAA21971; Sun, 18 Oct 1998 13:48:42 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd021941; Sun Oct 18 13:48:41 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id NAA10205; Sun, 18 Oct 1998 13:48:30 -0700 (MST) From: Terry Lambert Message-Id: <199810182048.NAA10205@usr07.primenet.com> Subject: Re: -current NFS problem To: dg@root.com Date: Sun, 18 Oct 1998 20:48:29 +0000 (GMT) Cc: tlambert@primenet.com, green@zone.syracuse.NET, grog@lemis.com, julian@whistle.com, mike@smith.net.au, bag@sinbin.demos.su, rock@cs.uni-sb.de, current@FreeBSD.ORG In-Reply-To: <199810160139.SAA22337@implode.root.com> from "David Greenman" at Oct 15, 98 06:39:34 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually that's not true. I can't speak for all of the NFS implementations > above, but at least in BSD/OS, it works only because they have warts all over > the place to sidestep the problems with not having FS node locking. OK, after having spent several hours trying to see what you mean here, I'm having a hard time understanding why locking the vnode that holds the pointer to the nfsnode data is not an implicit lock on the underlying nfsnode, just as it is for all other data that the vnode references. I can see a couple of cases where the nfsnode is not treated through the vnode that contains it, but it seems to me that that's where the bug is, and that explicit locks on the nfsnode would be rather a large amount of overhead to work around what is effectively a small set of vnode parameter pre-dereferences that shouldn't be occurring. One case is allocation, where the vnode container should be allocated and locked prior to manipulating the data pointer. Am I missing something? Has anyone asked Rick Macklem about this? > The > argument about FreeBSD vnode stacking/locking is simply meaningless if the > filesystem doesn't implement any node locking, so let's not confuse the > issue by bringing that up. IF the vnode lock implied an nfsnode (or inode) lock in all cases, and IF the nfsnode was never addressed, except through the vnode, and IF the vnode locking was done at a higher layer for all "bottom" FS's (where the vnode is not stacked on a vnode), and IF the requirement that the vnode be locked before a VOP call could be made against it was uniformly enforced, THEN I think there would be no NFS problems, nor a need for nfsnode locking above and beyond the vnode locking. This speaks directly to the call graph inversion (a pervasive problem in many places in the current VFS code, not just NFS), and in particular the inversion in the VOP_LOCK code, and, to a lesser extent, the non-management of vnodes by the FS's in which they represent objects. I also have to say that the *by far* most common problem I encounter in my frequently daily use of NFS (my home directory at work is NFS mounted) is lost UDP packets not getting retried or timed out. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:17:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10316 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:17:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10305 for ; Sun, 18 Oct 1998 14:17:47 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA21069; Sun, 18 Oct 1998 14:17:22 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd021039; Sun Oct 18 14:17:19 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA11370; Sun, 18 Oct 1998 14:17:16 -0700 (MST) From: Terry Lambert Message-Id: <199810182117.OAA11370@usr07.primenet.com> Subject: Re: So, what does ELF give me? To: ckempf@enigami.com (Cory Kempf) Date: Sun, 18 Oct 1998 21:17:15 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Cory Kempf" at Oct 16, 98 11:53:27 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, So I know that ELF is a much newer object file format than a.out, > and that it is supposed to somehow have better support for shared > libraries, the rest of the known universe is using it, and that it is > supposed to be somehow better and we are somehow supposed to be able > to do more things. > > So, what are they? > > What can I, as a developer, do with ELF that I couldn't with a.out? > What does it buy me? How will this difference impact me? > > Is there a discussion of this on line somewhere? Yes, in the -current list archives on www.freebsd.org. Among other things, it allows you to agregate multiple object files into a single object file, while still keeping them logically seperate. Since I'm the one who wrote up the biggest list in favor of ELF (I'm pretty sure no one beat me), I'd really prefer you go look for the list in the archives. As one example, you could build the libkvm into the kernel image itself, which would prevent it from ever getting out of date from now on. A program like ps or w or finger or ... could dlopen the ELF sections implementing the kvm access from the kernel image. This would allow them to access the kmem image of the currently running kernel and/or a crashdump, without fear of using the wrong libkvm. Another example is the ability replace default drivers in a running kernel with ones with more functionality, without having to rebuild the kernel for the change to become permanent for the next boot. Another example is section flagging, which would allow the vast majority of the kernel itself to actually be marked swappable. In user space, you could utilize commerically produced ELF libraries on your FreeBSD system. Etc. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:19:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10468 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:19:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10456 for ; Sun, 18 Oct 1998 14:19:25 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id UAA12938; Sun, 18 Oct 1998 20:09:01 +0100 (BST) (envelope-from nik) Message-ID: <19981018200901.53009@nothing-going-on.org> Date: Sun, 18 Oct 1998 20:09:01 +0100 From: Nik Clayton To: Andy Farkas , Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: mount flags References: <362A307E.8C676700@speednet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <362A307E.8C676700@speednet.com.au>; from Andy Farkas on Mon, Oct 19, 1998 at 04:16:30AM +1000 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 04:16:30AM +1000, Andy Farkas wrote: > Yeah, something fishy is going on here with statfs(2). According to the > man page on a 2.2.7 system, and in , there are definitions > for struct statfs->f_type, but on a 3.0-current, they have strangely > disappeared. >From the logs for src/sys/sys/mount.h; ---------------------------- revision 1.67 date: 1998/09/07 13:17:05; author: bde; state: Exp; lines: +5 -54 Removed statically configured mount type numbers (MOUNT_*) and all references to them. The change a couple of days ago to ignore these numbers in statically configured vfsconf structs was slightly premature because the cd9660, cfs, devfs, ext2fs, nfs vfs's still used MOUNT_* instead of the number in their vfsconf struct. ---------------------------- Bruce can presumably shed some more light. N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11246 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:26:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11233 for ; Sun, 18 Oct 1998 14:26:02 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id RAA16222; Sun, 18 Oct 1998 17:25:14 -0400 (EDT) Date: Sun, 18 Oct 1998 17:25:14 -0400 (EDT) From: Chuck Robey To: Nik Clayton cc: Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-Reply-To: <19981018200901.53009@nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Oct 1998, Nik Clayton wrote: > On Mon, Oct 19, 1998 at 04:16:30AM +1000, Andy Farkas wrote: > > Yeah, something fishy is going on here with statfs(2). According to the > > man page on a 2.2.7 system, and in , there are definitions > > for struct statfs->f_type, but on a 3.0-current, they have strangely > > disappeared. > > >From the logs for src/sys/sys/mount.h; > > ---------------------------- > revision 1.67 > date: 1998/09/07 13:17:05; author: bde; state: Exp; lines: +5 -54 > Removed statically configured mount type numbers (MOUNT_*) and all > references to them. > > The change a couple of days ago to ignore these numbers in statically > configured vfsconf structs was slightly premature because the cd9660, > cfs, devfs, ext2fs, nfs vfs's still used MOUNT_* instead of the number > in their vfsconf struct. > ---------------------------- > > Bruce can presumably shed some more light. I asked him several hours ago. Don't know the clock over there, but he's got to sleep *sometime*, and I've probably hit it. I understand from David O'Brien that this is part and parcel of BSD4.4Lite2 changes ... which seem to make a user's job of identifying what kind of filesystem he's dealing with (as opposed to mounting one from scratch) terribly kludgy. I think it's most likely a missing doc problem, or maybe I just haven't found it yet. Likely... > > N > -- > C.R.F. Consulting -- we're run to make me richer. . . > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:40:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12232 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:40:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles225.castles.com [208.214.165.225]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12173 for ; Sun, 18 Oct 1998 14:39:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA14283; Sun, 18 Oct 1998 14:42:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810182142.OAA14283@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: dg@root.com, green@zone.syracuse.NET, grog@lemis.com, julian@whistle.com, mike@smith.net.au, bag@sinbin.demos.su, rock@cs.uni-sb.de, current@FreeBSD.ORG Subject: Re: -current NFS problem In-reply-to: Your message of "Sun, 18 Oct 1998 20:48:29 -0000." <199810182048.NAA10205@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Oct 1998 14:42:56 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has anyone asked Rick Macklem about this? Rick bowed out of the NFS game a long time ago. Kirk would be a better bet. We do actually have an indirect contact with Rick via Mark Mayo, and he's lukewarm at best about doing anything with his old code, let alone talking about it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:45:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12557 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:45:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12550; Sun, 18 Oct 1998 14:45:44 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA23377; Sun, 18 Oct 1998 14:45:20 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd023364; Sun Oct 18 14:45:13 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA12579; Sun, 18 Oct 1998 14:45:11 -0700 (MST) From: Terry Lambert Message-Id: <199810182145.OAA12579@usr07.primenet.com> Subject: Re: softupdates/smp To: sos@FreeBSD.ORG Date: Sun, 18 Oct 1998 21:45:11 +0000 (GMT) Cc: julian@whistle.com, donegan@quick.net, chuckr@mat.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199810180918.LAA12711@sos.freebsd.dk> from "S?ren" Schmidt" at Oct 18, 98 11:18:04 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Well I'm doing it, but I've 'left off' development until the > > ELF/CAM/3.0/etc changes all settle down. > > > > looks to me as if someone has broken it again. > > I'll be in europe for a fortnight. When I get back > > I hope things will have settled down enough for me to look at it again. > > Erhm, I've never seen it work reliably under SMP, did you ever get the > giant lock prims into the syncer ?? It works reliably on my SMP box at home. Perhaps your SMP motherboard is working around the 8254 not via APIC bug, or you have some other board-specific attribute? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:51:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12828 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:51:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12812 for ; Sun, 18 Oct 1998 14:51:00 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA24329; Sun, 18 Oct 1998 14:50:31 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd024321; Sun Oct 18 14:50:30 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA12751; Sun, 18 Oct 1998 14:50:29 -0700 (MST) From: Terry Lambert Message-Id: <199810182150.OAA12751@usr07.primenet.com> Subject: Re: mount flags To: andyf@speednet.com.au (Andy Farkas) Date: Sun, 18 Oct 1998 21:50:28 +0000 (GMT) Cc: chuckr@mat.net, freebsd-current@FreeBSD.ORG In-Reply-To: <362A307E.8C676700@speednet.com.au> from "Andy Farkas" at Oct 19, 98 04:16:30 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a very recently broke thing that was happily using a call to > > statfs, to tell if it was an NFS filesystem or not. Last time I had > > occasion to take a look at this, there were flags of the sort MOUNT_XXX, > > where the XXX could have been UFS, MFS, NFS, etc. The application is > > specifically looking for MOUNT_NFS, and it's just not around anymore, > > that I can find. > > Yeah, something fishy is going on here with statfs(2). According to the > man page on a 2.2.7 system, and in , there are definitions > for struct statfs->f_type, but on a 3.0-current, they have strangely > disappeared. The use of this field in order to determine FS type presupposes the definition of a manifest value in the mount.h file each time someone adds a new FS type. This is basically an utterly bogus thing to presuppose, since it means that you have to recompile the kernel and modify mount.h to add support for a new FS type. > > Anyhow, anyone got a recommendation on how to change this thing so that > > it works under current? > > You're not trying to compile Midnight Commander are you? If so, add > "#define NO_INFOMOUNT 1" to config.h as a workaround .... > > > A real short history on what's changed in > > regards to this would be a nice thing to stick in the mail archives. > > Me too! I'd like to see a history, as well. IMO, the correct thing to do is to go by string, but this still leaves the mount flags and data in a position where they are rather bogusly externalized for string parsing within the kernel. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:52:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12995 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:52:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12989; Sun, 18 Oct 1998 14:52:55 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id OAA07587; Sun, 18 Oct 1998 14:52:30 -0700 (PDT) Date: Sun, 18 Oct 1998 14:52:30 -0700 (PDT) From: "Steven P. Donegan" To: Terry Lambert cc: sos@FreeBSD.ORG, julian@whistle.com, chuckr@mat.net, freebsd-current@FreeBSD.ORG Subject: Re: softupdates/smp In-Reply-To: <199810182145.OAA12579@usr07.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Oct 1998, Terry Lambert wrote: > > It works reliably on my SMP box at home. > > Perhaps your SMP motherboard is working around the 8254 not via APIC > bug, or you have some other board-specific attribute? > > The motherboards in question are a Tyan Tomcat IIID and IVD - both tombstone in softupdates code right after going SMP. Others on the list had indicated the same kind of tombstone in other areas so I (at the moment) ascribe this to a recent added kernel feature :-) I haven't tried today's world with SMP+softupdates yet... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 14:59:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13435 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:59:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13423 for ; Sun, 18 Oct 1998 14:59:28 -0700 (PDT) (envelope-from rkw@nomad.dataplex.net) Received: (from rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) id QAA09697; Sun, 18 Oct 1998 16:59:03 -0500 (CDT) (envelope-from rkw) Message-Id: <199810182159.QAA09697@nomad.dataplex.net> Date: Sun, 18 Oct 1998 16:59:03 -0500 (CDT) From: User & Subject: Re: Never ending 'make clean' in kde port? To: tlambert@primenet.com cc: current@FreeBSD.ORG In-Reply-To: <199810182110.OAA11047@usr07.primenet.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Oct, Terry Lambert wrote: > Which is throwing out the baby with the bathwater. > > The correct thing to do is to explicitly specify dependencies. I agree. One major problem with the present tree is that they are missing many of the dependencies. (They assume that target ordering will somehow make up for it. Witness the problems with SMP and make -j8) > > For things like second order effects, it's important to build using > the headers in the source tree, and not the installed headers, This is also true for the the target builds. However, we need to recognize that a single source tree may be used for multiple purposes. Although one approach would be to clone selected portions of the tree in order to build the cross-compilation tools, that should not be necessary. We should be able to reference the installed headers/library and the sources in the tree to build the bootstrapping tools. However, this is a degression from the original point.with respect to "recursive makes" > The lack of explicit dependencies in the source tree is the true > source of the observed chaos. With explicit dependencies, we get the observed problem. Only by merging the inter-module dependencies can we avoid the repeated "makes" in the prerequisite modules. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 15:17:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14606 for freebsd-current-outgoing; Sun, 18 Oct 1998 15:17:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14589 for ; Sun, 18 Oct 1998 15:17:50 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA00261; Sun, 18 Oct 1998 15:17:27 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd000246; Sun Oct 18 15:17:26 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id PAA13757; Sun, 18 Oct 1998 15:17:23 -0700 (MST) From: Terry Lambert Message-Id: <199810182217.PAA13757@usr07.primenet.com> Subject: Re: -current NFS problem To: dg@root.com Date: Sun, 18 Oct 1998 22:17:23 +0000 (GMT) Cc: tlambert@primenet.com, green@zone.syracuse.NET, grog@lemis.com, julian@whistle.com, mike@smith.net.au, bag@sinbin.demos.su, rock@cs.uni-sb.de, current@FreeBSD.ORG In-Reply-To: <199810182112.OAA06041@implode.root.com> from "David Greenman" at Oct 18, 98 02:12:30 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >> Actually that's not true. I can't speak for all of the NFS implementations > >> above, but at least in BSD/OS, it works only because they have warts all over > >> the place to sidestep the problems with not having FS node locking. > > > >OK, after having spent several hours trying to see what you mean > >here, I'm having a hard time understanding why locking the vnode > >that holds the pointer to the nfsnode data is not an implicit lock > >on the underlying nfsnode, just as it is for all other data that > >the vnode references. > > Because there is no such thing as a "vnode lock", despite the terminology > that we use in describing it. The lock state is stored in the attached > fsnode, not in the vnode. For FFS, it is stored in a lock struct that is > the first item in the in-core inode. In the special case of NFS, it's not > stored at all. This means that VOP_LOCK()/VOP_UNLOCK() do nothing useful > for NFS and this exposes all sorts of bugs in code that assumes that they > do. Well, this is utterly bogus. What happened to v_interlock? The locking of vnodes should be done against the vnode. Just like the advisory locks should be hung off the vnode instead of off of ip->i_lockf. I have to say the the implementation of vop_nolock(), and the mere existance of vfs_default.c leaves me less than enthused. As things now stand, I can't collapse NULL layers into a single indirection during vfs_init(), nor can I sort the descriptor entries in order to avoid descriptor overhead for cases where the descriptor isn't being externalized (i.e., all VFS stacking layers except Heidemann's VFS network proxy layer). 8-(. I believe that statment in the comments: * This code cannot be used until all the non-locking filesystems * (notably NFS) are converted to properly lock and release nodes. Is correct to this point, if we presume a default implementation instead of a veto-based implementation at the vn_ call layer. * Also, certain vnode operations change the locking state within * the operation (create, mknod, remove, link, rename, mkdir, rmdir, * and symlink). I think this is unavoidable, so long as the operations change the lock state. Ideally these operations should not change the * lock state, but should be changed to let the caller of the * function unlock them. And that this is the correct soloution. Otherwise all intermediate vnode layers * (such as union, umapfs, etc) must catch these functions to do * the necessary locking at their layer. I think this is incorrect. I think that because we might have an FS that externalizes two of the VFS layers in a given stack, that the VFS layer will have to handle this, regardless. The NULL layers, wherein there is not a VFS MUX (e.g., nullfs, umapfs) can ignore the proxy locking (presuming the operations for the NULL layers have been collapes out, and that the exposed layer "does the right thing" interms of requiring the upper layer to proxy the lock down), while the layers with inherent MUX properties (e.g., unionfs, translucentfs) must catch the downpath in all cases to proxy to the N (N > 1) underlying vnodes. If this doesn't happen, then these things will never do cache coherency correctly without requiring access via bmap and synchronization events (which would be a loss). Note that the inactive * and lookup operations also change their lock state, but this * cannot be avoided, so these two operations will always need * to be handled in intermediate layers. Actually, I think this can be avoided by moving some more of the common lookup and inactive code up the function call graph. It's my opinion that the bottom level FS's only interest in locking should be in the local resource pooling, as necessary (ihash is unnecessary, for example) and in changes, as necessary, to increase SMP granularity (and I don't think a lot is necessary in that regard, so long as domain locking that has to occur for local resource pooling, like directory entry management, is sufficiently granular). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 15:53:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16808 for freebsd-current-outgoing; Sun, 18 Oct 1998 15:53:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from orion.tamu.edu (orion.tamu.edu [128.194.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16801 for ; Sun, 18 Oct 1998 15:53:09 -0700 (PDT) (envelope-from daved@orion.tamu.edu) Received: from orion (localhost [127.0.0.1]) by orion.tamu.edu (8.8.8/8.8.8) with ESMTP id RAA12864; Sun, 18 Oct 1998 17:53:23 -0500 (CDT) (envelope-from daved@orion.tamu.edu) Message-Id: <199810182253.RAA12864@orion.tamu.edu> From: "David J. Duchscher" To: Mike Smith cc: ulf@Alameda.net, current@FreeBSD.ORG Subject: Re: newfs problems, more information: In-reply-to: Your message of "Sat, 17 Oct 1998 19:03:04 PDT." <199810180203.TAA08917@dingo.cdrom.com> Date: Sun, 18 Oct 1998 17:53:23 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > newfs: /dev/ccd0c: not a character-special device > > Don't put a filesystem on the 'c' partition. Granted this document references 2.2-RELEASE but it doesn't follow this convention/rule. It should probably be updated. http://www.freebsd.org/tutorials/diskformat/diskformat.html#s1-4-3 DaveD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 16:48:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20754 for freebsd-current-outgoing; Sun, 18 Oct 1998 16:48:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from unix.tfs.net (as1-p34.tfs.net [139.146.210.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20749 for ; Sun, 18 Oct 1998 16:48:48 -0700 (PDT) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id SAA00981; Sun, 18 Oct 1998 18:48:18 -0500 (CDT) From: Jim Bryant Message-Id: <199810182348.SAA00981@unix.tfs.net> Subject: Re: netscape in -current is broked In-Reply-To: <199810182100.OAA09695@bubba.whistle.com> from Archie Cobbs at "Oct 18, 98 02:00:45 pm" To: archie@whistle.com (Archie Cobbs) Date: Sun, 18 Oct 1998 18:48:17 -0500 (CDT) Cc: freebsd-current@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Sat Jun 20 11:57:05 CDT 1998 X-Question: What do you call a Republican on Viagra? X-Answer: A Democrat, of course! X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > Studded writes: > > Werner Griessl wrote: > > > You need the old aout-Xlibs for netscape: > > > > Forgive me if this is a silly question, but has anyone tried linking > > the old names to the new libraries? > > That won't work because the old libs are a.out format and the > new ones (in the case of this thread) are elf format. ACK! I thought this thread was dead... Thank you, you are correct, but the problem has been resolved. I thought i had posted a thank-you to all who helped, but I guess I must not have. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 17:47:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25045 for freebsd-current-outgoing; Sun, 18 Oct 1998 17:47:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25040 for ; Sun, 18 Oct 1998 17:47:31 -0700 (PDT) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id RAA12702; Sun, 18 Oct 1998 17:46:54 -0700 (PDT) Date: Sun, 18 Oct 1998 17:46:54 -0700 (PDT) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199810190046.RAA12702@math.berkeley.edu> To: freebsd-current@FreeBSD.ORG Subject: more 3.0-RELEASE boot.flp problems Cc: dan@math.berkeley.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After installing 3.0-RELEASE, I attempted to boot the new system The booteasy program listed all the dos partition table entries and asked which one to boot, giving the FreeBSD partition as the default. I thought this was a bit odd. In my experience, the first time you boot after a booteasy installation it indicates "F?" is the default. So I hit return and the booteasy program beeped at my. The I hit the specifically desired F-key and the booteasy program beeped at me again. No matter what I typed, the boot program just beeped at me. It did not even retype the boot prompt as I recall it did after an inappropriate input. Then I did a hard reset. No change. I power cycled the machine. No change. I rebooted the bootstrap floppy and it came up running the standard installation script but was very confused about which keyboard key meant what. (For example, the left arrow key selected the "exit" option and the other arrow keys did nothing at all.) I checked all the keyboard "lock" keys and they were ok. So I reset the system and rebooted and this time the boot floppy came up ok. I went into the disk selection/partition menu and reinstalled the booteasy boot block (with the undocumented "w" option). Booteasy continued to misbehave as described above. The I booted a slightly older boot floppy (3.0-19981009-BETA I believe) and reinstalled the booteasy boot block. This fixed the problem. Then I reinstalled booteasy from the 3.0-RELEASE floppy and the problem came back. Then I reinstalled booteasy from the BETA release floppy and this fixed the problem. I decided to leave well enough alone. Then I checksummed my 3.0-RELEASE boot floppy and compared it to the boot.flp image on disk and the boot.flp entry in the 3.0-RELEASE/floppies/CHECKSUM.MD5 file. They all agreed. My floppy was copied correctly. Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 18:47:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00400 for freebsd-current-outgoing; Sun, 18 Oct 1998 18:47:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00395 for ; Sun, 18 Oct 1998 18:47:26 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id SAA24706; Sun, 18 Oct 1998 18:47:05 -0700 (PDT) Message-ID: <19981018184704.A21657@Alameda.net> Date: Sun, 18 Oct 1998 18:47:04 -0700 From: Ulf Zimmermann To: Dan Strick , freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems Reply-To: ulf@Alameda.net References: <199810190046.RAA12702@math.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810190046.RAA12702@math.berkeley.edu>; from Dan Strick on Sun, Oct 18, 1998 at 05:46:54PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed 3.0-R and have exactly the same problems. argl. On Sun, Oct 18, 1998 at 05:46:54PM -0700, Dan Strick wrote: > After installing 3.0-RELEASE, I attempted to boot the new system > The booteasy program listed all the dos partition table entries and > asked which one to boot, giving the FreeBSD partition as the default. > I thought this was a bit odd. In my experience, the first time you > boot after a booteasy installation it indicates "F?" is the default. > So I hit return and the booteasy program beeped at my. The I hit > the specifically desired F-key and the booteasy program beeped at > me again. No matter what I typed, the boot program just beeped > at me. It did not even retype the boot prompt as I recall it > did after an inappropriate input. > > Then I did a hard reset. No change. I power cycled the machine. > No change. I rebooted the bootstrap floppy and it came up running > the standard installation script but was very confused about which > keyboard key meant what. (For example, the left arrow key selected > the "exit" option and the other arrow keys did nothing at all.) > I checked all the keyboard "lock" keys and they were ok. > > So I reset the system and rebooted and this time the boot floppy > came up ok. I went into the disk selection/partition menu > and reinstalled the booteasy boot block (with the undocumented > "w" option). Booteasy continued to misbehave as described > above. The I booted a slightly older boot floppy (3.0-19981009-BETA > I believe) and reinstalled the booteasy boot block. This fixed > the problem. Then I reinstalled booteasy from the 3.0-RELEASE > floppy and the problem came back. Then I reinstalled booteasy > from the BETA release floppy and this fixed the problem. > I decided to leave well enough alone. > > Then I checksummed my 3.0-RELEASE boot floppy and compared it > to the boot.flp image on disk and the boot.flp entry in the > 3.0-RELEASE/floppies/CHECKSUM.MD5 file. They all agreed. > My floppy was copied correctly. > > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. > > Dan Strick > dan@math.berkeley.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 18:55:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01020 for freebsd-current-outgoing; Sun, 18 Oct 1998 18:55:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01002 for ; Sun, 18 Oct 1998 18:55:12 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id JAA03392; Mon, 19 Oct 1998 09:50:35 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810190150.JAA03392@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Nik Clayton cc: Andy Farkas , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-reply-to: Your message of "Sun, 18 Oct 1998 20:09:01 +0100." <19981018200901.53009@nothing-going-on.org> Date: Mon, 19 Oct 1998 09:50:35 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton wrote: > On Mon, Oct 19, 1998 at 04:16:30AM +1000, Andy Farkas wrote: > > Yeah, something fishy is going on here with statfs(2). According to the > > man page on a 2.2.7 system, and in , there are definitions > > for struct statfs->f_type, but on a 3.0-current, they have strangely > > disappeared. > > From the logs for src/sys/sys/mount.h; > > ---------------------------- > revision 1.67 > date: 1998/09/07 13:17:05; author: bde; state: Exp; lines: +5 -54 > Removed statically configured mount type numbers (MOUNT_*) and all > references to them. > > The change a couple of days ago to ignore these numbers in statically > configured vfsconf structs was slightly premature because the cd9660, > cfs, devfs, ext2fs, nfs vfs's still used MOUNT_* instead of the number > in their vfsconf struct. > ---------------------------- > > Bruce can presumably shed some more light. > > N The FS type numbers are essentially random numbers, so it's no good trying to match them to a MOUNT_* constant. NetBSD had them #defined to strings, ie: #define MOUNT_NFS "nfs" so that you had some idea what you could expect from the kernel on a known filesystem. There can be no such thing as a canonical list since of fstypenames because new ones can be loaded on the fly. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 19:06:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02177 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:06:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02172 for ; Sun, 18 Oct 1998 19:06:42 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id TAA25475; Sun, 18 Oct 1998 19:06:21 -0700 (PDT) Message-ID: <19981018190621.B21657@Alameda.net> Date: Sun, 18 Oct 1998 19:06:21 -0700 From: Ulf Zimmermann To: Dan Strick , freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems Reply-To: ulf@Alameda.net References: <199810190046.RAA12702@math.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810190046.RAA12702@math.berkeley.edu>; from Dan Strick on Sun, Oct 18, 1998 at 05:46:54PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As an additional information: Screen comes up looking like this: F1 FreeBSD Default: F2 _ Pressing F1, the floppy starts up. On Sun, Oct 18, 1998 at 05:46:54PM -0700, Dan Strick wrote: > After installing 3.0-RELEASE, I attempted to boot the new system > The booteasy program listed all the dos partition table entries and > asked which one to boot, giving the FreeBSD partition as the default. > I thought this was a bit odd. In my experience, the first time you > boot after a booteasy installation it indicates "F?" is the default. > So I hit return and the booteasy program beeped at my. The I hit > the specifically desired F-key and the booteasy program beeped at > me again. No matter what I typed, the boot program just beeped > at me. It did not even retype the boot prompt as I recall it > did after an inappropriate input. > > Then I did a hard reset. No change. I power cycled the machine. > No change. I rebooted the bootstrap floppy and it came up running > the standard installation script but was very confused about which > keyboard key meant what. (For example, the left arrow key selected > the "exit" option and the other arrow keys did nothing at all.) > I checked all the keyboard "lock" keys and they were ok. > > So I reset the system and rebooted and this time the boot floppy > came up ok. I went into the disk selection/partition menu > and reinstalled the booteasy boot block (with the undocumented > "w" option). Booteasy continued to misbehave as described > above. The I booted a slightly older boot floppy (3.0-19981009-BETA > I believe) and reinstalled the booteasy boot block. This fixed > the problem. Then I reinstalled booteasy from the 3.0-RELEASE > floppy and the problem came back. Then I reinstalled booteasy > from the BETA release floppy and this fixed the problem. > I decided to leave well enough alone. > > Then I checksummed my 3.0-RELEASE boot floppy and compared it > to the boot.flp image on disk and the boot.flp entry in the > 3.0-RELEASE/floppies/CHECKSUM.MD5 file. They all agreed. > My floppy was copied correctly. > > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. > > Dan Strick > dan@math.berkeley.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 19:16:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03393 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:16:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03387 for ; Sun, 18 Oct 1998 19:16:44 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id TAA02013; Sun, 18 Oct 1998 19:15:56 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: dan@math.berkeley.edu (Dan Strick) cc: freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems In-reply-to: Your message of "Sun, 18 Oct 1998 17:46:54 PDT." <199810190046.RAA12702@math.berkeley.edu> Date: Sun, 18 Oct 1998 19:15:56 -0700 Message-ID: <2009.908763356@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. Well, it sounds like the new boot manager (which is not BOOTEASY, even though it looks a bit like it) is in fact broken somehow, even though it works on my test machines (damn!). Could you tell us a bit more about whether this was a dedicated/non-dedicated installation, whether there were other OSes on the disk, etc etc? I really would like to continue using the new boot0 since it's the first time we've had a boot manager for which the sources were compiliable and maintained under the FreeBSD tree, unlike BOOTEASY which was a DOS program getting ever more stale under our umbrella. - Jordan P.S. to Robert: I *told* you we should have made those prompts look more different; people are still confusing it with BOOTEASY! :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 19:19:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03583 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:19:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03571 for ; Sun, 18 Oct 1998 19:19:21 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id WAA03709; Sun, 18 Oct 1998 22:17:31 -0400 (EDT) Date: Sun, 18 Oct 1998 22:17:30 -0400 (EDT) From: Chuck Robey To: Peter Wemm cc: Nik Clayton , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-Reply-To: <199810190150.JAA03392@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Peter Wemm wrote: > > Bruce can presumably shed some more light. > > > > N > > The FS type numbers are essentially random numbers, so it's no good > trying to match them to a MOUNT_* constant. I was hoping you wouldn't say that. Murphy was telling me you would. Mike commented that both the old and new methods should be working ... I agree, at least until the new method doesn't resemble keystone kops so well. Bruce hasn't replied yet, let's be patient. I at least don't know enough about it to undo anything he's done. I *could* do that, but not with safety. > > NetBSD had them #defined to strings, ie: #define MOUNT_NFS "nfs" so that > you had some idea what you could expect from the kernel on a known > filesystem. There can be no such thing as a canonical list since of > fstypenames because new ones can be loaded on the fly. OK. Can the field in struct statfs, f_fsid, be mapped to something, like say the struct vfsconf that comes back from a getvfsbyname(), the vfc_typenum field? Geeze, that nfs code is impenetrable. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 19:49:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05757 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:49:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05752 for ; Sun, 18 Oct 1998 19:49:51 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id TAA02321 for ; Sun, 18 Oct 1998 19:49:04 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: current@FreeBSD.ORG Subject: To everyone who's been having trouble with the new "booteasy" Date: Sun, 18 Oct 1998 19:49:04 -0700 Message-ID: <2317.908765344@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First, an explanation: In 3.0, we're no longer using booteasy, we're using Robert Nordier's boot0 replacement which is hosted entirely under FreeBSD (a major win). However, some people have also reported big problems with this so, for the mean time, I've decided to go back to booteasy with sysinstall until we figure out what's going on. The 3.0 SNAPshots will still continue to use the boot0 code so those wishing to help Robert figure out what's going on can and should continue to install snaps from current.freebsd.org. The 3.0 release bits on ftp.freebsd.org (and the 3.0-RELEASE CDROMs) will continue to use the older booteasy bits for now; I've just re-rolled and copied over boot floppy bits which do so. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 19:50:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05845 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:50:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles338.castles.com [208.214.167.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05840 for ; Sun, 18 Oct 1998 19:50:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA15721; Sun, 18 Oct 1998 19:54:24 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810190254.TAA15721@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: ulf@Alameda.net cc: Dan Strick , freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems In-reply-to: Your message of "Sun, 18 Oct 1998 19:06:21 PDT." <19981018190621.B21657@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Oct 1998 19:54:22 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As an additional information: > > Screen comes up looking like this: > > F1 FreeBSD > > Default: F2 _ This looks like the active flag is set wrongly. > Pressing F1, the floppy starts up. Any error messages at that point? The infamous "read error" message perhaps? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 19:51:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05897 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:51:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles338.castles.com [208.214.167.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05892 for ; Sun, 18 Oct 1998 19:51:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA15738; Sun, 18 Oct 1998 19:55:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810190255.TAA15738@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: dan@math.berkeley.edu (Dan Strick), freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems In-reply-to: Your message of "Sun, 18 Oct 1998 19:15:56 PDT." <2009.908763356@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Oct 1998 19:55:40 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. > > Well, it sounds like the new boot manager (which is not BOOTEASY, > even though it looks a bit like it) is in fact broken somehow, > even though it works on my test machines (damn!). Could you tell > us a bit more about whether this was a dedicated/non-dedicated > installation, whether there were other OSes on the disk, etc etc? > > I really would like to continue using the new boot0 since it's > the first time we've had a boot manager for which the sources were > compiliable and maintained under the FreeBSD tree, unlike BOOTEASY > which was a DOS program getting ever more stale under our umbrella. You should mention that Booteasy is still in the tools directory, and that the bootinst tool should be used to install it if boot0 isn't working out. Another Errata item I guess? > P.S. to Robert: I *told* you we should have made those prompts > look more different; people are still confusing it with BOOTEASY! :-) *laugh* -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 19:53:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06078 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:53:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06073 for ; Sun, 18 Oct 1998 19:53:41 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id VAA08723; Sun, 18 Oct 1998 21:53:11 -0500 (CDT) From: Kevin Day Message-Id: <199810190253.VAA08723@home.dragondata.com> Subject: Re: more 3.0-RELEASE boot.flp problems In-Reply-To: <19981018184704.A21657@Alameda.net> from Ulf Zimmermann at "Oct 18, 98 06:47:04 pm" To: ulf@Alameda.net Date: Sun, 18 Oct 1998 21:53:10 -0500 (CDT) Cc: dan@math.berkeley.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just installed 3.0-R and have exactly the same problems. argl. > > On Sun, Oct 18, 1998 at 05:46:54PM -0700, Dan Strick wrote: > > After installing 3.0-RELEASE, I attempted to boot the new system > > The booteasy program listed all the dos partition table entries and > > asked which one to boot, giving the FreeBSD partition as the default. > > I thought this was a bit odd. In my experience, the first time you > > boot after a booteasy installation it indicates "F?" is the default. > > So I hit return and the booteasy program beeped at my. The I hit > > the specifically desired F-key and the booteasy program beeped at > > me again. No matter what I typed, the boot program just beeped > > at me. It did not even retype the boot prompt as I recall it > > did after an inappropriate input. > > > > Then I did a hard reset. No change. I power cycled the machine. > > No change. I rebooted the bootstrap floppy and it came up running > > the standard installation script but was very confused about which > > keyboard key meant what. (For example, the left arrow key selected > > the "exit" option and the other arrow keys did nothing at all.) > > I checked all the keyboard "lock" keys and they were ok. > > > > So I reset the system and rebooted and this time the boot floppy > > came up ok. I went into the disk selection/partition menu > > and reinstalled the booteasy boot block (with the undocumented > > "w" option). Booteasy continued to misbehave as described > > above. The I booted a slightly older boot floppy (3.0-19981009-BETA > > I believe) and reinstalled the booteasy boot block. This fixed > > the problem. Then I reinstalled booteasy from the 3.0-RELEASE > > floppy and the problem came back. Then I reinstalled booteasy > > from the BETA release floppy and this fixed the problem. > > I decided to leave well enough alone. > > > > Then I checksummed my 3.0-RELEASE boot floppy and compared it > > to the boot.flp image on disk and the boot.flp entry in the > > 3.0-RELEASE/floppies/CHECKSUM.MD5 file. They all agreed. > > My floppy was copied correctly. > > > > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. > > > > Dan Strick > > dan@math.berkeley.edu > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > To add to this, I've got a Tyan Tomcat IV board.... booted it for the first time after doing a clean install of 3.0.... I got the: F1 FreeBSD Default: F2 Thing.. I hit F1, and it beeped 3-4 times, then went ahead and booted anyway. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 19:56:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06344 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:56:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles338.castles.com [208.214.167.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06339 for ; Sun, 18 Oct 1998 19:56:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA15782; Sun, 18 Oct 1998 20:00:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810190300.UAA15782@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dan@math.berkeley.edu (Dan Strick) cc: freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems In-reply-to: Your message of "Sun, 18 Oct 1998 17:46:54 PDT." <199810190046.RAA12702@math.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Oct 1998 20:00:56 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After installing 3.0-RELEASE, I attempted to boot the new system > The booteasy program listed all the dos partition table entries and > asked which one to boot, giving the FreeBSD partition as the default. > I thought this was a bit odd. In my experience, the first time you > boot after a booteasy installation it indicates "F?" is the default. The default bootmanager is actually 'boot0' (pronounced 'BootZero'). You can install Booteasy to (hopefully) fix your problems by fetching it from the directory ftp.cdrom.com/pub/FreeBSD/tools. > So I hit return and the booteasy program beeped at my. The I hit > the specifically desired F-key and the booteasy program beeped at > me again. No matter what I typed, the boot program just beeped > at me. It did not even retype the boot prompt as I recall it > did after an inappropriate input. Boot0 behaves differently. There appears to be a problem with some BIOS translations for disks bigger than the old 504MB limit. > Then I did a hard reset. No change. I power cycled the machine. > No change. I rebooted the bootstrap floppy and it came up running > the standard installation script but was very confused about which > keyboard key meant what. (For example, the left arrow key selected > the "exit" option and the other arrow keys did nothing at all.) We've seen this problem during testing as well, but we haven't been able to characterise it, so we have no idea what's causing it. It doesn't ever seem to happen with the system once installed, only with the installation kernel. > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. Quite erroneous. There are a number of components that aren't working 100%, however on the whole it works pretty well. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 19:56:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06374 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:56:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06366 for ; Sun, 18 Oct 1998 19:56:48 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id TAA02385; Sun, 18 Oct 1998 19:55:57 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Kevin Day cc: ulf@Alameda.net, dan@math.berkeley.edu, freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems In-reply-to: Your message of "Sun, 18 Oct 1998 21:53:10 CDT." <199810190253.VAA08723@home.dragondata.com> Date: Sun, 18 Oct 1998 19:55:57 -0700 Message-ID: <2381.908765757@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can folks please try again with the new boot.flp bits on ftp.cdrom.com? The MD5 checksum to look for is: MD5 (boot.flp) = 1ba1282766ef954df8fa7a5153e5c2e2 This should be the standard old booteasy back again, but I want to also make sure I didn't break something with this 11th hour fix. Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 19:58:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06518 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:58:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06507 for ; Sun, 18 Oct 1998 19:58:14 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA05919; Mon, 19 Oct 1998 12:27:44 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA06104; Mon, 19 Oct 1998 12:27:42 +0930 (CST) Message-ID: <19981019122742.C4015@freebie.lemis.com> Date: Mon, 19 Oct 1998 12:27:42 +0930 From: Greg Lehey To: Mike Smith , Dan Strick Cc: freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems References: <199810190046.RAA12702@math.berkeley.edu> <199810190300.UAA15782@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810190300.UAA15782@dingo.cdrom.com>; from Mike Smith on Sun, Oct 18, 1998 at 08:00:56PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 18 October 1998 at 20:00:56 -0700, Mike Smith wrote: >> Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. > > Quite erroneous. There are a number of components that aren't working > 100%, however on the whole it works pretty well. "Parts of it are excellent" Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 20:00:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06727 for freebsd-current-outgoing; Sun, 18 Oct 1998 20:00:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06716 for ; Sun, 18 Oct 1998 20:00:12 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id KAA03668; Mon, 19 Oct 1998 10:54:40 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810190254.KAA03668@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: Nik Clayton , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-reply-to: Your message of "Sun, 18 Oct 1998 22:17:30 -0400." Date: Mon, 19 Oct 1998 10:54:40 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > On Mon, 19 Oct 1998, Peter Wemm wrote: > > > > Bruce can presumably shed some more light. > > > > > > N > > > > The FS type numbers are essentially random numbers, so it's no good > > trying to match them to a MOUNT_* constant. > > I was hoping you wouldn't say that. Murphy was telling me you would. It's been that way for a while, sorry. > Mike commented that both the old and new methods should be working ... > I agree, at least until the new method doesn't resemble keystone kops so > well. The "old" method is to use getvfsbytype based on the f_type field, that still works across the board, but requires you to know that "nfs" is nfs etc. > > NetBSD had them #defined to strings, ie: #define MOUNT_NFS "nfs" so that > > you had some idea what you could expect from the kernel on a known > > filesystem. There can be no such thing as a canonical list since of > > fstypenames because new ones can be loaded on the fly. > > OK. Can the field in struct statfs, f_fsid, be mapped to something, > like say the struct vfsconf that comes back from a getvfsbyname(), the > vfc_typenum field? f_fsid is used internally by NFS as part of the network protocol, ignore that. vfc_typenum is the same as the statfs.f_type field. That's how you match them. You can, however, do a getvfsbyname("nfs") and get the magic number from the returned vfc_typenum and use that instead of the old MOUNT_NFS constant if that's more convenient. Beware that this isn't guaranteed to remain constant in the face of vfs loads and unloads via the lkm or kld mechanism. > Geeze, that nfs code is impenetrable. You said it. :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 20:17:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08714 for freebsd-current-outgoing; Sun, 18 Oct 1998 20:17:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eterna.binary.net (eterna.binary.net [12.13.120.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08708 for ; Sun, 18 Oct 1998 20:17:28 -0700 (PDT) (envelope-from nathan@matrix.binary.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id WAA23946 for ; Sun, 18 Oct 1998 22:16:29 -0500 (CDT) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id WAA12737; Sun, 18 Oct 1998 22:17:04 -0500 (CDT) Message-ID: <19981018231703.A11707@binary.net> Date: Sun, 18 Oct 1998 23:17:04 -0400 From: Nathan Dorfman To: freebsd-current@FreeBSD.ORG Subject: 3.0-R, CAM, and audio tracks Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At first I thought this was a bug in tosha, or its lack of support for my drive. It will read the TOC from an audio disc just fine, but upon trying to read the audio data itself: error returned from CD-DA read command: (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 20 0 0 a 0 (pass1:ahc0:0:2:0): ILLEGAL REQUEST asc:64,0 (pass1:ahc0:0:2:0): Illegal mode for this track tosha also seems to forget to reset the drive to a sane status because any subsequent CD audio attempts with cdcontrol(1) fail with cdcontrol: /dev/cd0c: Invalid argument. I tried this with both the tosha-0.5 port (most recent ports) and the tosha-0.05-cam.980916.tar.gz on ftp.kdm.org. Both fail the same way. This is a freshly installed 3.0-R system but the same behavior is seen on a 2 week old -current. Anyway, what leads me to think that this is a CAM problem as opposed to a tosha bug is the following little quirk: I popped in the nearest data CD, which happened to be the 2.2.1 live FS, and ran tosha -v -- to my great am{az|us}ement it went right to work writing the pcm file. It was suggested to me that CAM might have a problem with passthrough for audio discs/tracks. Can anyone confirm/deny this? Anyone have any other ideas? -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 20:33:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09609 for freebsd-current-outgoing; Sun, 18 Oct 1998 20:33:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09598 for ; Sun, 18 Oct 1998 20:33:39 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id XAA04027; Sun, 18 Oct 1998 23:30:59 -0400 (EDT) Date: Sun, 18 Oct 1998 23:30:58 -0400 (EDT) From: Chuck Robey To: Peter Wemm cc: Nik Clayton , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-Reply-To: <199810190254.KAA03668@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Peter Wemm wrote: > f_fsid is used internally by NFS as part of the network protocol, ignore > that. OK. I don't like the getvfsbytype method because of the far larger amount of work, it seems truly silly. I'd have to step thru all the available fs types, matching on name until I found one that had "nfs", then match the number found to the one from statfs. My first reaction is that it's a lot of work, wasteful. That's probably ridiculous, but let me ask another question, below. > > vfc_typenum is the same as the statfs.f_type field. That's how you match > them. > > You can, however, do a getvfsbyname("nfs") and get the magic number from > the returned vfc_typenum and use that instead of the old MOUNT_NFS > constant if that's more convenient. Beware that this isn't guaranteed to > remain constant in the face of vfs loads and unloads via the lkm or kld > mechanism. If I do the getvfsbyname method, I do no pattern-matching at all (FreeBSD does that for me). When I do the lookup, the data is good at that point, isn't it, even in the face of the vfs or KLD loads/unloads, right? And, as long as I do no dismounting (the fs is up) that number can't change on me. The *set* of available numbers and their mappings can change, but not the one I'm sitting on, right? If that's true, for my app, that will do. I'd stop doing that, if I trusted that the statfs f_fstypename was reliably being set. It's too new, and I haven't found where it's getting set, no matter how much I search for it. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 20:44:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10213 for freebsd-current-outgoing; Sun, 18 Oct 1998 20:44:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nu.binary.net (nu.binary.net [12.13.120.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10208 for ; Sun, 18 Oct 1998 20:44:55 -0700 (PDT) (envelope-from nathan@matrix.binary.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by nu.binary.net (8.9.1a/8.9.0) with ESMTP id WAA13210 for ; Sun, 18 Oct 1998 22:44:29 -0500 (CDT) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id WAA15812; Sun, 18 Oct 1998 22:44:28 -0500 (CDT) Message-ID: <19981018234428.A15396@binary.net> Date: Sun, 18 Oct 1998 23:44:28 -0400 From: Nathan Dorfman To: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-R, CAM, and audio tracks (more info) References: <19981018231703.A11707@binary.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981018231703.A11707@binary.net>; from Nathan Dorfman on Sun, Oct 18, 1998 at 11:17:04PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 18, 1998 at 11:17:04PM -0400, Nathan Dorfman wrote: > At first I thought this was a bug in tosha, or its lack of support > for my drive. It will read the TOC from an audio disc just fine, > but upon trying to read the audio data itself: > > error returned from CD-DA read command: > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 20 0 0 a 0 > (pass1:ahc0:0:2:0): ILLEGAL REQUEST asc:64,0 > (pass1:ahc0:0:2:0): Illegal mode for this track > > tosha also seems to forget to reset the drive to a sane status > because any subsequent CD audio attempts with cdcontrol(1) fail > with cdcontrol: /dev/cd0c: Invalid argument. I tried this with > both the tosha-0.5 port (most recent ports) and the > tosha-0.05-cam.980916.tar.gz on ftp.kdm.org. Both fail the same > way. This is a freshly installed 3.0-R system but the same > behavior is seen on a 2 week old -current. Anyway, what leads me > to think that this is a CAM problem as opposed to a tosha bug is > the following little quirk: I popped in the nearest data CD, which > happened to be the 2.2.1 live FS, and ran tosha -v -- to my great > am{az|us}ement it went right to work writing the pcm file. > > It was suggested to me that CAM might have a problem with passthrough > for audio discs/tracks. Can anyone confirm/deny this? Anyone have > any other ideas? After compiling the CAMDEBUG options into my kernel and running camcontrol debug -Ic 0:2:0, I got the following: tosha attempting to read audio track and failing: (pass1:ahc0:0:2:0): INQUIRY. CDB: 12 0 0 0 40 0 (pass1:ahc0:0:2:0): MODE SENSE(06). CDB: 1a 0 1 0 c 0 (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 (pass1:ahc0:0:2:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 0 0 0 0 0 1 8 0 0 (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 20 0 0 a 0 tosha attempting to read data track and succeeding: (pass1:ahc0:0:2:0): INQUIRY. CDB: 12 0 0 0 40 0 (pass1:ahc0:0:2:0): MODE SENSE(06). CDB: 1a 0 1 0 c 0 (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 (pass1:ahc0:0:2:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 0 0 0 0 0 1 8 0 0 (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 0 0 0 a 0 (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 a 0 0 a 0 (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 14 0 0 a 0 (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 1e 0 0 a 0 ...etc... Is CAM preventing tosha from reading audio data via passthrough? -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 20:50:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10638 for freebsd-current-outgoing; Sun, 18 Oct 1998 20:50:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10633 for ; Sun, 18 Oct 1998 20:50:46 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id UAA29597; Sun, 18 Oct 1998 20:50:20 -0700 (PDT) Message-ID: <19981018205019.C21657@Alameda.net> Date: Sun, 18 Oct 1998 20:50:19 -0700 From: Ulf Zimmermann To: "Jordan K. Hubbard" , Dan Strick Cc: freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems Reply-To: ulf@Alameda.net References: <199810190046.RAA12702@math.berkeley.edu> <2009.908763356@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <2009.908763356@time.cdrom.com>; from Jordan K. Hubbard on Sun, Oct 18, 1998 at 07:15:56PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 18, 1998 at 07:15:56PM -0700, Jordan K. Hubbard wrote: > > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. > > Well, it sounds like the new boot manager (which is not BOOTEASY, > even though it looks a bit like it) is in fact broken somehow, > even though it works on my test machines (damn!). Could you tell > us a bit more about whether this was a dedicated/non-dedicated > installation, whether there were other OSes on the disk, etc etc? 4GB disk (da0), using Fdisk to make 1 partition with 100%. Not using the "Use Entire Disk" option. Using the standard MBR option, the system comes up. > > I really would like to continue using the new boot0 since it's > the first time we've had a boot manager for which the sources were > compiliable and maintained under the FreeBSD tree, unlike BOOTEASY > which was a DOS program getting ever more stale under our umbrella. > > - Jordan > > P.S. to Robert: I *told* you we should have made those prompts > look more different; people are still confusing it with BOOTEASY! :-) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 21:03:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11495 for freebsd-current-outgoing; Sun, 18 Oct 1998 21:03:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11490 for ; Sun, 18 Oct 1998 21:03:03 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id VAA00157; Sun, 18 Oct 1998 21:02:09 -0700 (PDT) Message-ID: <19981018210209.D21657@Alameda.net> Date: Sun, 18 Oct 1998 21:02:09 -0700 From: Ulf Zimmermann To: Mike Smith Cc: Dan Strick , freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems Reply-To: ulf@Alameda.net References: <19981018190621.B21657@Alameda.net> <199810190254.TAA15721@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810190254.TAA15721@dingo.cdrom.com>; from Mike Smith on Sun, Oct 18, 1998 at 07:54:22PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 18, 1998 at 07:54:22PM -0700, Mike Smith wrote: > > As an additional information: > > > > Screen comes up looking like this: > > > > F1 FreeBSD > > > > Default: F2 _ > > This looks like the active flag is set wrongly. > > > Pressing F1, the floppy starts up. > > Any error messages at that point? The infamous "read error" message > perhaps? No Error messages. Just beeping, even let it sit for a while to see if it boots up, but nothing. I tried to set the Active flag, but after rebooting agian from the boot.flp, it does not show up as active. Here is what I tried: Boot boot.flp, go into Custom, go into Partition, it shows: Disk name: da0 DISK Geometry: 527 cyls/255 heads/63 sectors = 8466255 sectors Offset Size End Name PType Desc Subtype Flags 0 63 62 - 6 unused 0 63 8466192 8466254 da0s1 3 freebsd 165 C 8466255 945 8467199 - 6 unused 0 Using the "S" option I set the FreeBSD parition active. Then used "W" to write the active flag and the bootmgr. "Q" for quit, exit boot.flp and reboot. System comes up with the earlier described screen. Lettting it stand for a while, it beeps, but nothing more happens. Pressing F1, beeps, floppy light goes on for a momement, having a floppy in it or not, doesn't matter. Pressing F2, just beeps, no harddisk drive light as far I can see. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 21:19:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12582 for freebsd-current-outgoing; Sun, 18 Oct 1998 21:19:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12577 for ; Sun, 18 Oct 1998 21:19:11 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA15377; Mon, 19 Oct 1998 14:18:36 +1000 Date: Mon, 19 Oct 1998 14:18:36 +1000 From: Bruce Evans Message-Id: <199810190418.OAA15377@godzilla.zeta.org.au> To: chuckr@mat.net, peter@netplex.com.au Subject: Re: mount flags Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > What's wrong with the f_fstypename[] field in struct statfs? It'll >> > contain a string "nfs" or "ufs" etc.. >> >> I looked in the statfs man page and couldn't see any kind of definition >> of what went in that field (so as to use it to choose from). I took a >> quick look at the code, nothing immediately jumps out at me ... for an >> external system interface, it's certainly obscurely set up, isn't it? >> >> Do you know where the derivation of the f_fstypename values comes from? >> I just can't find it. > >Hmm.. Now that you mention it... I don't see where it's being set >either. I'm not sure that it is being set at all... :-( Er, it's set by a strncpy() in kern/vfs_syscalls.c:mount(). This is as simple as possible. The only complication is that the definitions of type names are distributed, so it is hard to see all the names at once (lsvfs only gives the names of the loadeded ones). >Short term hack: look at f_type in the statfs struct, and use the >getvfsent() routines to map that back into a type name. >According to : >/usr/include/sys/mount.h:struct ovfsconf *getvfsbytype __P((int)); Don't. Interfaces that use ovfsconf are obsolescent. Only lsvfs really needs them. I didn't manage to remove them for 3.0, sigh. The only "correct" use for f_type is to call vfs ioctls by number. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 21:19:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12696 for freebsd-current-outgoing; Sun, 18 Oct 1998 21:19:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12684 for ; Sun, 18 Oct 1998 21:19:48 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA02712 for ; Sun, 18 Oct 1998 21:19:03 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: current@FreeBSD.ORG Subject: countdown to ELF kernel? Date: Sun, 18 Oct 1998 21:19:02 -0700 Message-ID: <2708.908770742@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that we're out of freeze, when are we throwing the switch again? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 21:24:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13033 for freebsd-current-outgoing; Sun, 18 Oct 1998 21:24:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13028 for ; Sun, 18 Oct 1998 21:24:16 -0700 (PDT) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id XAA28404; Sun, 18 Oct 1998 23:23:51 -0500 (EST) Date: Sun, 18 Oct 1998 23:23:50 -0500 (EST) From: John Fieber To: Nathan Dorfman cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-R, CAM, and audio tracks In-Reply-To: <19981018231703.A11707@binary.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Oct 1998, Nathan Dorfman wrote: > It was suggested to me that CAM might have a problem with passthrough > for audio discs/tracks. Can anyone confirm/deny this? Anyone have > any other ideas? I've never been able to get decent audio dumps from my Toshiba 3501 using tosha (or anything else for that matter), but what was unique about my one attempt under 3.0-BETA (Oct 11 kernel) is that my whole SCSI bus ground to a halt. My softupdates enabled filesystems recovered pretty well after a reboot and I promptly delete the tosha port. The controller in an ASUS SC200. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 21:27:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13400 for freebsd-current-outgoing; Sun, 18 Oct 1998 21:27:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nu.binary.net (nu.binary.net [12.13.120.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13395 for ; Sun, 18 Oct 1998 21:27:50 -0700 (PDT) (envelope-from nathan@matrix.binary.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by nu.binary.net (8.9.1a/8.9.0) with ESMTP id XAA13752; Sun, 18 Oct 1998 23:27:26 -0500 (CDT) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id XAA20441; Sun, 18 Oct 1998 23:27:26 -0500 (CDT) Message-ID: <19981019002726.A20104@binary.net> Date: Mon, 19 Oct 1998 00:27:26 -0400 From: Nathan Dorfman To: John Fieber , Nathan Dorfman Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-R, CAM, and audio tracks References: <19981018231703.A11707@binary.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from John Fieber on Sun, Oct 18, 1998 at 11:23:50PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 18, 1998 at 11:23:50PM -0500, John Fieber wrote: > On Sun, 18 Oct 1998, Nathan Dorfman wrote: > > > It was suggested to me that CAM might have a problem with passthrough > > for audio discs/tracks. Can anyone confirm/deny this? Anyone have > > any other ideas? > I've never been able to get decent audio dumps from my Toshiba > 3501 using tosha (or anything else for that matter), but what was > unique about my one attempt under 3.0-BETA (Oct 11 kernel) is > that my whole SCSI bus ground to a halt. My softupdates enabled > filesystems recovered pretty well after a reboot and I promptly > delete the tosha port. I'm on an AHA-2940UW and a Yamaha CDRW-4260. This is fairly decent hardware. Also, it's suspicious that it will read the data tracks but not the audio tracks--I guess either my CD drive or CAM won't let it? Then again, what do I know. It would suck to have to get audio dumps on the loseNt machine in the other room, on a 2x IDE driver, and ftp them over here, that's for sure :/ > The controller in an ASUS SC200. > > -john -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 21:52:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16396 for freebsd-current-outgoing; Sun, 18 Oct 1998 21:52:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf34.cruzers.com [205.215.232.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA16375 for ; Sun, 18 Oct 1998 21:52:28 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 27594 invoked by uid 100); 19 Oct 1998 04:52:21 -0000 Date: Sun, 18 Oct 1998 21:52:21 -0700 To: freebsd-current@FreeBSD.ORG Cc: grog@lemis.com Subject: can't get vinum to work Message-ID: <19981018215221.A27539@top.worldcontrol.com> Mail-Followup-To: freebsd-current@freebsd.org, grog@lemis.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was about to setup ccd running two drives striped, when I found that vinum, while in beta, seems to be the future. However, I get various failures. I'm running -current,elf,CAM. My vinum init file look like: # Drives drive drive1 device /dev/da1h drive drive2 device /dev/da2h # volume volume bigvol plex org striped 64b sd length 2030m drive drive1 sd length 2030m drive drive2 However when I run: bls2# vinum resetconfig bls2# vinum create /etc/rc.vinum ** 2 Can't initialize drive drive1: Invalid argument ** 3 Can't initialize drive drive2: Invalid argument ** 7 Drive drive1 is not accessible: Input/output error ** 8 Unnamed sd is not associated with a plex: Invalid argument Can't save Vinum config: Operation not permitted Configuration summary Drives: 2 (4 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) D drive1 State: down Device /dev/da1h D drive2 State: down Device /dev/da2h V bigvol State: down Plexes: 1 Size: 2030 MB P bigvol.p0 S State: down Subdisks: 1 Size: 2030 MB S bigvol.p0.s0 State: down PO: 0 B Size: 2030 MB with these messages in /var/log/messages: Oct 18 21:15:15 bls2 vinum: configuration obliterated Oct 18 21:15:26 bls2 /kernel: vinum: drive drive1 is down Oct 18 21:15:26 bls2 /kernel: vinum open_drive /dev/da1h: failed with error 22 Oct 18 21:15:26 bls2 /kernel: vinum: drive drive2 is down Oct 18 21:15:26 bls2 /kernel: vinum open_drive /dev/da2h: failed with error 22 Oct 18 21:15:26 bls2 /kernel: vinum: plex bigvol.p0 does not have at least 2 subdisks If I use da1/da2 instead of da1h/da2h, I get this instead: bls2# vinum resetconfig bls2# vinum create /etc/rc.vinum Can't save Vinum config: Operation not permitted Configuration summary Drives: 2 (4 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) D drive1 State: down Device /dev/da1 D drive2 State: down Device /dev/da2 V bigvol State: up Plexes: 1 Size: 4060 MB P bigvol.p0 S State: down Subdisks: 2 Size: 4060 MB S bigvol.p0.s0 State: down PO: 0 B Size: 2030 MB S bigvol.p0.s1 State: down PO: 2030 MB Size: 2030 MB with these messages in /var/log/messages: Oct 18 21:19:55 bls2 vinum: configuration obliterated Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s0 is up Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s1 is up Oct 18 21:19:59 bls2 /kernel: vinum: plex bigvol.p0 is up Oct 18 21:19:59 bls2 /kernel: vinum: volume bigvol is up Oct 18 21:19:59 bls2 /kernel: vinum: Can't write config to /dev/da1, error 19 Oct 18 21:19:59 bls2 /kernel: vinum: drive drive1 is down Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s0 is down Oct 18 21:19:59 bls2 /kernel: vinum: plex bigvol.p0 is degraded Oct 18 21:19:59 bls2 /kernel: vinum: Can't write config to /dev/da2, error 19 Oct 18 21:19:59 bls2 /kernel: vinum: drive drive2 is down Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s1 is down Oct 18 21:20:00 bls2 /kernel: vinum: plex bigvol.p0 is down here is some more support info: bls2# fdisk da1 ******* Working on device /dev/rda1 ******* parameters extracted from in-core disklabel are: cylinders=2063 heads=64 sectors/track=32 (2048 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2063 heads=64 sectors/track=32 (2048 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: bls2# fdisk da2 ******* Working on device /dev/rda2 ******* parameters extracted from in-core disklabel are: cylinders=2063 heads=64 sectors/track=32 (2048 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2063 heads=64 sectors/track=32 (2048 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: >From dmesg: kernel: da2 at ahc0 bus 0 target 5 lun 0 kernel: da2: Fixed Direct Access SCSI2 device kernel: da2: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled kernel: da2: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C) kernel: da1 at ahc0 bus 0 target 4 lun 0 kernel: da1: Fixed Direct Access SCSI2 device kernel: da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled kernel: da1: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C) And in case you are wondering: bls2# modstat Type Id Off Loadaddr Size Info Rev Module Name MISC 0 0 f41fc000 0269 f4206054 1 vinum_mod -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 21:55:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16762 for freebsd-current-outgoing; Sun, 18 Oct 1998 21:55:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16681 for ; Sun, 18 Oct 1998 21:55:24 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id VAA25670 for freebsd-current@freebsd.org; Sun, 18 Oct 1998 21:54:40 -0700 (PDT) Message-ID: <19981018215440.A25652@nuxi.com> Date: Sun, 18 Oct 1998 21:54:40 -0700 From: "David O'Brien" To: freebsd-current@FreeBSD.ORG Subject: GNU Awk replacement Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 2.2.7-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What do people think about replacing GNU awk in the base system with the One True Awk(tm) by bwk? -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 22:07:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17810 for freebsd-current-outgoing; Sun, 18 Oct 1998 22:07:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17804 for ; Sun, 18 Oct 1998 22:07:51 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id BAA04944; Mon, 19 Oct 1998 01:07:10 -0400 (EDT) Date: Mon, 19 Oct 1998 01:07:10 -0400 (EDT) From: Chuck Robey To: "David O'Brien" cc: freebsd-current@FreeBSD.ORG Subject: Re: GNU Awk replacement In-Reply-To: <19981018215440.A25652@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Oct 1998, David O'Brien wrote: > What do people think about replacing GNU awk in the base system with the > One True Awk(tm) by bwk? How far back you harking? Oawk, no. nawk, yes. You loose too much going back too far. I don't care too much, as long as it's not the old original. Wouldn't even mention it, but I think someone's actually unearthed the old one. You don't want to do that. > > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 22:09:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18140 for freebsd-current-outgoing; Sun, 18 Oct 1998 22:09:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18135 for ; Sun, 18 Oct 1998 22:09:06 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA06297 for ; Mon, 19 Oct 1998 14:38:41 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id OAA06463; Mon, 19 Oct 1998 14:38:24 +0930 (CST) Message-ID: <19981019143824.G4015@freebie.lemis.com> Date: Mon, 19 Oct 1998 14:38:24 +0930 From: Greg Lehey To: freebsd-current@FreeBSD.ORG Subject: Re: can't get vinum to work References: <19981018215221.A27539@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981018215221.A27539@top.worldcontrol.com>; from brian@worldcontrol.com on Sun, Oct 18, 1998 at 09:52:21PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 18 October 1998 at 21:52:21 -0700, brian@worldcontrol.com wrote: > I was about to setup ccd running two drives striped, when I found > that vinum, while in beta, seems to be the future. > > However, I get various failures. > > I'm running -current,elf,CAM. > > My vinum init file look like: > # Drives > drive drive1 device /dev/da1h > drive drive2 device /dev/da2h > # volume > volume bigvol > plex org striped 64b > sd length 2030m drive drive1 > sd length 2030m drive drive2 > > However when I run: > > bls2# vinum resetconfig Don't use resetconfig. It's for emergencies only. But it doesn't make any difference here. > bls2# vinum create /etc/rc.vinum > > ** 2 Can't initialize drive drive1: Invalid argument > ** 3 Can't initialize drive drive2: Invalid argument Where did this version of Vinum come from? The message that is now output is Drive %s has invalid partition type > ** 7 Drive drive1 is not accessible: Input/output error > ** 8 Unnamed sd is not associated with a plex: Invalid argument > Can't save Vinum config: Operation not permitted These are all the results of the first problem. > If I use da1/da2 instead of da1h/da2h, I get this instead: I don't have any such device nodes. Do you? What's the minor number? > bls2# vinum resetconfig > bls2# vinum create /etc/rc.vinum > Can't save Vinum config: Operation not permitted > Configuration summary > > Drives: 2 (4 configured) > Volumes: 1 (4 configured) > Plexes: 1 (8 configured) > Subdisks: 2 (16 configured) > > D drive1 State: down Device /dev/da1 > D drive2 State: down Device /dev/da2 > > V bigvol State: up Plexes: 1 Size: 4060 MB > > P bigvol.p0 S State: down Subdisks: 2 Size: 4060 MB > > S bigvol.p0.s0 State: down PO: 0 B Size: 2030 MB > S bigvol.p0.s1 State: down PO: 2030 MB Size: 2030 MB > > with these messages in /var/log/messages: > > Oct 18 21:19:55 bls2 vinum: configuration obliterated > Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s0 is up > Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s1 is up > Oct 18 21:19:59 bls2 /kernel: vinum: plex bigvol.p0 is up > Oct 18 21:19:59 bls2 /kernel: vinum: volume bigvol is up > Oct 18 21:19:59 bls2 /kernel: vinum: Can't write config to /dev/da1, error 19 This is "operation not supported by device". I'm surprised you didn't get error messages from 'vinum create'. > Oct 18 21:19:59 bls2 /kernel: vinum: drive drive1 is down > Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s0 is down > Oct 18 21:19:59 bls2 /kernel: vinum: plex bigvol.p0 is degraded > Oct 18 21:19:59 bls2 /kernel: vinum: Can't write config to /dev/da2, error 19 > Oct 18 21:19:59 bls2 /kernel: vinum: drive drive2 is down > Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s1 is down > Oct 18 21:20:00 bls2 /kernel: vinum: plex bigvol.p0 is down I suspect your real problem is that /dev/da1h and /dev/da2h are set with file system type 4.2BSD. This is appropriate for making UFS file systems, and for some obscure reason ccd requires it, but it's a sure-fire recipe for shooting yourself in the foot. Vinum will ultimately require a file system type 'vinum', but currently it insists on 'unused'. >From vinum(8) DRIVE LAYOUT CONSIDERATIONS vinum drives are currently BSD disk partitions. They must be of type unused in order to avoid overwriting file systems. In later versions of vinum this requirement will change to type vinum. vinum uses the first 265 sectors on each partition for configuration information, so the maxi- mum size of a subdisk is 265 sectors smaller than the drive. You can change it with disklabel -e: from: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 1173930 0 unused 0 0 # (Cyl. 0 - 358) h: 1173930 0 4.2BSD 0 0 # (Cyl. 0 - 358) to: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 1173930 0 unused 0 0 # (Cyl. 0 - 358) h: 1173930 0 unused 0 0 # (Cyl. 0 - 358) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 22:39:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21143 for freebsd-current-outgoing; Sun, 18 Oct 1998 22:39:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21135 for ; Sun, 18 Oct 1998 22:39:38 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id WAA25835 for freebsd-current@FreeBSD.ORG; Sun, 18 Oct 1998 22:39:15 -0700 (PDT) Message-ID: <19981018223914.B25719@nuxi.com> Date: Sun, 18 Oct 1998 22:39:14 -0700 From: "David O'Brien" To: freebsd-current@FreeBSD.ORG Subject: Re: GNU Awk replacement Reply-To: obrien@NUXI.com References: <19981018215440.A25652@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chuck Robey on Mon, Oct 19, 1998 at 01:07:10AM -0400 X-Operating-System: FreeBSD 2.2.7-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What do people think about replacing GNU awk in the base system with the > > One True Awk(tm) by bwk? > > How far back you harking? Oawk, no. nawk, yes. You loose too much Good question. Our kawk port (kawk-98.02.11). from http://cm.bell-labs.com/who/bwk/awk.tar.gz To quote: This is the version of awk described in "The AWK Programming Language", by Al Aho, Brian Kernighan, and Peter Weinberger (Addison-Wesley, 1988, ISBN 0-201-07981-X). It is under a Berkeley/MIT/CMU like copyright. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 22:42:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21459 for freebsd-current-outgoing; Sun, 18 Oct 1998 22:42:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21450 for ; Sun, 18 Oct 1998 22:42:27 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA22459; Mon, 19 Oct 1998 15:41:53 +1000 Date: Mon, 19 Oct 1998 15:41:53 +1000 From: Bruce Evans Message-Id: <199810190541.PAA22459@godzilla.zeta.org.au> To: andyf@speednet.com.au, chuckr@mat.net Subject: Re: mount flags Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> A real short history on what's changed in >> regards to this would be a nice thing to stick in the mail archives. 1. (Integer) type numbers for file systems are broken as designed. 2. Use of them was mostly fixed in 4.4BSD-Lite2 (May 1995). 3. FreeBSD is taking a long time to complete the Lite2 merge. Some mileposts according to sys/mount.h: 1.1.1.2 1996/03/11 Import on vendor branch. 1.36 1997/02/10 Merge (kernel only, 90% only). 1.67 1998/09/07 Merge removal of MOUNT* definitions for type numbers. 1.68 1998/10/15 Tag for first release with Lite2 changes in it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 22:59:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22679 for freebsd-current-outgoing; Sun, 18 Oct 1998 22:59:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles338.castles.com [208.214.167.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22674 for ; Sun, 18 Oct 1998 22:59:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA16555; Sun, 18 Oct 1998 22:58:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810190558.WAA16555@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: Peter Wemm , Nik Clayton , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-reply-to: Your message of "Sun, 18 Oct 1998 23:30:58 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Oct 1998 22:58:13 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If I do the getvfsbyname method, I do no pattern-matching at all > (FreeBSD does that for me). When I do the lookup, the data is good at > that point, isn't it, even in the face of the vfs or KLD loads/unloads, > right? And, as long as I do no dismounting (the fs is up) that number > can't change on me. The *set* of available numbers and their mappings > can change, but not the one I'm sitting on, right? That's correct; a VFS can't be unloaded while it's referenced. > I'd stop doing that, if I trusted that the statfs f_fstypename was > reliably being set. It's too new, and I haven't found where it's > getting set, no matter how much I search for it. You can probably count on it. If you can't, that's *definitely* a bug. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 23:02:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22983 for freebsd-current-outgoing; Sun, 18 Oct 1998 23:02:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles338.castles.com [208.214.167.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA22976 for ; Sun, 18 Oct 1998 23:02:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA16588; Sun, 18 Oct 1998 23:01:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810190601.XAA16588@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: countdown to ELF kernel? In-reply-to: Your message of "Sun, 18 Oct 1998 21:19:02 PDT." <2708.908770742@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Oct 1998 23:01:35 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Now that we're out of freeze, when are we throwing the switch again? MHO, give us a week or so to catch the 3.0-release generated bug traffic before we launch this one. We're getting the usual post-release betatesters showing up just now. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 23:15:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23921 for freebsd-current-outgoing; Sun, 18 Oct 1998 23:15:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flophouse.com (flophouse.com [192.135.198.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23899 for ; Sun, 18 Oct 1998 23:15:47 -0700 (PDT) (envelope-from dpassage@flophouse.com) Received: from flophouse.com (localhost.flophouse.com [127.0.0.1]) by flophouse.com (8.8.8/8.8.8) with ESMTP id XAA16811 for ; Sun, 18 Oct 1998 23:15:23 -0700 (PDT) (envelope-from dpassage@flophouse.com) Message-Id: <199810190615.XAA16811@flophouse.com> To: freebsd-current@FreeBSD.ORG Subject: make buildworld lex library breakage (with fix!) Date: Sun, 18 Oct 1998 23:15:22 -0700 From: "David G. Paschich" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Environment: FreeBSD -stable box as of approx Oct 8, trying to build -current cvsupped around 10pm PDT today. During the "Rebuilding tools necessary to build the include files" stage, the attempt to build compile_et fails because of a missing lex library: [...] cc -O -pipe -I. -I/usr/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/aout/usr/src/tmp/usr/include -static -o compile_et compile_et.o error_table.o -ll ld: -ll: no match *** Error code 1 It appears in Makefile.inc1 (revision 1.36) that the lex library never gets built or installed into the /usr/obj tree. Enabling the build of the lex library in the "make bootstrap" target fixed the problem for me. Diff follows (cut and pasted so the tabs may be wrong): *** Makefile.inc1 1998/10/17 11:56:20 1.36 --- Makefile.inc1 1998/10/19 05:23:24 *************** *** 499,507 **** ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} cd ${.CURDIR}/usr.bin/lex; ${MAKE} bootstrap; \ ${MAKE} ${MK_FLAGS} ${_DEPEND}; \ ! ${MAKE} ${MK_FLAGS} -DNOLIB all; \ ! ${MAKE} ${MK_FLAGS} -DNOLIB -B install ${CLEANDIR} ! cd ${.CURDIR}/usr.bin/lex; ${MAKE} ${OBJDIR} cd ${.CURDIR}/usr.sbin/mtree; ${MAKE} ${MK_FLAGS} ${_DEPEND}; \ ${MAKE} ${MK_FLAGS} all; \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} --- 499,506 ---- ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} cd ${.CURDIR}/usr.bin/lex; ${MAKE} bootstrap; \ ${MAKE} ${MK_FLAGS} ${_DEPEND}; \ ! ${MAKE} ${MK_FLAGS} all; \ ! ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} cd ${.CURDIR}/usr.sbin/mtree; ${MAKE} ${MK_FLAGS} ${_DEPEND}; \ ${MAKE} ${MK_FLAGS} all; \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} -------- David G. Paschich dpassage@flophouse.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 23:18:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24136 for freebsd-current-outgoing; Sun, 18 Oct 1998 23:18:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24127 for ; Sun, 18 Oct 1998 23:18:07 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id AAA21008; Mon, 19 Oct 1998 00:17:41 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810190617.AAA21008@panzer.plutotech.com> Subject: Re: 3.0-R, CAM, and audio tracks (more info) In-Reply-To: <19981018234428.A15396@binary.net> from Nathan Dorfman at "Oct 18, 98 11:44:28 pm" To: nathan@rtfm.net (Nathan Dorfman) Date: Mon, 19 Oct 1998 00:17:41 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nathan Dorfman wrote... > On Sun, Oct 18, 1998 at 11:17:04PM -0400, Nathan Dorfman wrote: > > At first I thought this was a bug in tosha, or its lack of support > > for my drive. It will read the TOC from an audio disc just fine, > > but upon trying to read the audio data itself: > > > > error returned from CD-DA read command: > > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 20 0 0 a 0 > > (pass1:ahc0:0:2:0): ILLEGAL REQUEST asc:64,0 > > (pass1:ahc0:0:2:0): Illegal mode for this track Your CDROM drive didn't like the command that tosha sent. > > tosha also seems to forget to reset the drive to a sane status > > because any subsequent CD audio attempts with cdcontrol(1) fail > > with cdcontrol: /dev/cd0c: Invalid argument. My guess is that the command that tosha did to set the density didn't get undone. It looks like there's a bug in the way error handling is done in the CAM version of tosha -- the density doesn't get set back to its original value before tosha exits if it exits abnormally. > > I tried this with > > both the tosha-0.5 port (most recent ports) and the > > tosha-0.05-cam.980916.tar.gz on ftp.kdm.org. Both fail the same > > way. Not surprising, since it's the same code in both places. > > This is a freshly installed 3.0-R system but the same > > behavior is seen on a 2 week old -current. Ditto. > > Anyway, what leads me > > to think that this is a CAM problem as opposed to a tosha bug is > > the following little quirk: I popped in the nearest data CD, which > > happened to be the 2.2.1 live FS, and ran tosha -v -- to my great > > am{az|us}ement it went right to work writing the pcm file. > > > > It was suggested to me that CAM might have a problem with passthrough > > for audio discs/tracks. Can anyone confirm/deny this? Anyone have > > any other ideas? > > After compiling the CAMDEBUG options into my kernel and running > camcontrol debug -Ic 0:2:0, I got the following: > > tosha attempting to read audio track and failing: > > (pass1:ahc0:0:2:0): INQUIRY. CDB: 12 0 0 0 40 0 > (pass1:ahc0:0:2:0): MODE SENSE(06). CDB: 1a 0 1 0 c 0 > (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > (pass1:ahc0:0:2:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 0 0 0 0 0 1 8 0 0 > > (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 20 0 0 a 0 > > tosha attempting to read data track and succeeding: > > (pass1:ahc0:0:2:0): INQUIRY. CDB: 12 0 0 0 40 0 > (pass1:ahc0:0:2:0): MODE SENSE(06). CDB: 1a 0 1 0 c 0 > (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > (pass1:ahc0:0:2:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 0 0 0 0 0 1 8 0 0 > > (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 0 0 0 a 0 > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 a 0 0 a 0 > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 14 0 0 a 0 > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 1e 0 0 a 0 > ...etc... > > Is CAM preventing tosha from reading audio data via passthrough? Yes. Justin and I were paid by the RIAA to make sure that FreeBSD users can't copy audio CDs. The FBI will contact you shortly to discuss whether or not your use of your CDs constitutes "fair use". It looks like your drive doesn't like it when you try to read audio tracks that way. You may want to talk to Oliver Fromme about it, and see if he's heard any other bug reports about Yamaha drives not working. IIRC, Daniel O'Conner had a similar problem with a Yamaha drive. I think he was able to get it to work with cdda2wav, but he ran into another problem with cdda2wav that looks like a vm problem related to shared memory. I'm not exactly sure what the problem is, but it's most likely related to tosha's interaction with your drive. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 23:24:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24600 for freebsd-current-outgoing; Sun, 18 Oct 1998 23:24:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24590 for ; Sun, 18 Oct 1998 23:24:52 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id AAA21045; Mon, 19 Oct 1998 00:24:23 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810190624.AAA21045@panzer.plutotech.com> Subject: Re: 3.0-R, CAM, and audio tracks In-Reply-To: from John Fieber at "Oct 18, 98 11:23:50 pm" To: jfieber@indiana.edu (John Fieber) Date: Mon, 19 Oct 1998 00:24:23 -0600 (MDT) Cc: nathan@rtfm.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Fieber wrote... > On Sun, 18 Oct 1998, Nathan Dorfman wrote: > > > It was suggested to me that CAM might have a problem with passthrough > > for audio discs/tracks. Can anyone confirm/deny this? Anyone have > > any other ideas? > > I've never been able to get decent audio dumps from my Toshiba > 3501 using tosha (or anything else for that matter), Do you mean "never" as in "not with CAM" or never as in "not with CAM or the old SCSI subsystem"? > but what was > unique about my one attempt under 3.0-BETA (Oct 11 kernel) is > that my whole SCSI bus ground to a halt. My softupdates enabled > filesystems recovered pretty well after a reboot and I promptly > delete the tosha port. > > The controller in an ASUS SC200. That's not good. Were there any interesting error messages? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 18 23:59:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27131 for freebsd-current-outgoing; Sun, 18 Oct 1998 23:59:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27125 for ; Sun, 18 Oct 1998 23:59:51 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA29545; Mon, 19 Oct 1998 16:59:14 +1000 Date: Mon, 19 Oct 1998 16:59:14 +1000 From: Bruce Evans Message-Id: <199810190659.QAA29545@godzilla.zeta.org.au> To: dpassage@flophouse.com, freebsd-current@FreeBSD.ORG Subject: Re: make buildworld lex library breakage (with fix!) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Environment: FreeBSD -stable box as of approx Oct 8, trying to build >-current cvsupped around 10pm PDT today. > >During the "Rebuilding tools necessary to build the include files" >stage, the attempt to build compile_et fails because of a missing lex >library: > >[...] >cc -O -pipe -I. -I/usr/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/aout/usr/src/tmp/usr/include -static -o compile_et compile_et.o error_table.o -ll >ld: -ll: no match >*** Error code 1 > >It appears in Makefile.inc1 (revision 1.36) that the lex library never >gets built or installed into the /usr/obj tree. Enabling the build of Actually, it gets built about 3 times, including in a weird place in lib-tools, but not before building compile_et. >the lex library in the "make bootstrap" target fixed the problem for >me. Diff follows (cut and pasted so the tabs may be wrong): This seems to be correct except it doesn't delete building of the lex library in lib-tools. It used to be wrong because ld used to have to be built before any libraries to get support for the -O and -f flags. Now -O is not used, and -f is only used for `make depend', and `make world' doesn't run `make depend' except in the NOCLEAN case and in buggy parts of the legacy build that misspell ${_DEPEND} as `depend'. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 00:22:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28801 for freebsd-current-outgoing; Mon, 19 Oct 1998 00:22:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28792 for ; Mon, 19 Oct 1998 00:22:50 -0700 (PDT) (envelope-from volf@oasis.IAEhv.nl) Received: from oasis.IAEhv.nl (uucp@localhost) by news.IAEhv.nl (8.8.8/8.8.8) with IAEhv.nl id JAA13566 for freebsd.org!current; Mon, 19 Oct 1998 09:22:26 +0200 (MET DST) (envelope-from volf@oasis.IAEhv.nl) Received: from LOCAL (volf@localhost) by avalon.oasis.IAEhv.nl (8.8.8/1.63); pid 688 on Mon, 19 Oct 1998 07:23:01 GMT; id HAA00688 efrom: volf; eto: current@freebsd.org From: volf@oasis.IAEhv.nl (Frank Volf) Message-Id: <199810190723.HAA00688@avalon.oasis.IAEhv.nl> Subject: Trouble with CVS-CUR? To: current@FreeBSD.ORG Date: Mon, 19 Oct 1998 09:23:01 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is it only me or do other people also have trouble with CTM? In particular I'm still awaiting the CTM delta that contains the 3.0 RELEASE tags. Until now I only received a few deltas that tag part of the ports tree. But the src tree itself has not been touched. Here are the deltas that I received recently: 10 -rw-r--r-- 1 root staff 9597 Oct 15 18:33 cvs-cur.4729.gz 14 -rw-r--r-- 1 root staff 13915 Oct 15 18:42 cvs-cur.4730.gz 120 -rw-r--r-- 1 root staff 113681 Oct 16 22:18 cvs-cur.4731.gz 14 -rw-r--r-- 1 root staff 14030 Oct 16 22:18 cvs-cur.4732.gz 248 -rw-r--r-- 1 root staff 239902 Oct 16 22:18 cvs-cur.4733.gz 61 -rw-r--r-- 1 root staff 61744 Oct 18 11:27 cvs-cur.4734.gz 120 -rw-r--r-- 1 root staff 109291 Oct 18 20:27 cvs-cur.4735.gz 2 -rw-r--r-- 1 root staff 1962 Oct 19 08:59 cvs-cur.4736.gz I check this with the ftp site, but they do not seem to have more deltas than I. Anything wrong? Frank ---------------------------------------------------------------------------- Frank Volf - Internet Access Eindhoven ---------------------------------------------------------------------------- || volf@oasis.IAEhv.nl - use for personal mail || || volf@IAEhv.nl - use for Internet Access Eindhoven related mail || ---------------------------------------------------------------------------- IAE Public Access Unix System - Dial +31.40.2439436 and login as new. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 00:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29130 for freebsd-current-outgoing; Mon, 19 Oct 1998 00:26:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-50-dbn.dial-up.net [196.34.155.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29111 for ; Mon, 19 Oct 1998 00:25:59 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id JAA01380; Mon, 19 Oct 1998 09:24:42 +0200 (SAT) From: Robert Nordier Message-Id: <199810190724.JAA01380@ceia.nordier.com> Subject: Re: To everyone who's been having trouble with the new "booteasy" In-Reply-To: <2317.908765344@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 18, 98 07:49:04 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 19 Oct 1998 09:24:35 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > First, an explanation: In 3.0, we're no longer using booteasy, we're > using Robert Nordier's boot0 replacement which is hosted entirely > under FreeBSD (a major win). However, some people have also reported > big problems with this so, for the mean time, I've decided to go back > to booteasy with sysinstall until we figure out what's going on. The > 3.0 SNAPshots will still continue to use the boot0 code so those > wishing to help Robert figure out what's going on can and should > continue to install snaps from current.freebsd.org. The 3.0 release > bits on ftp.freebsd.org (and the 3.0-RELEASE CDROMs) will continue to > use the older booteasy bits for now; I've just re-rolled and copied > over boot floppy bits which do so. The problem is that boot0 is attempting to make use of an "extended" BIOS read function, if BIOS indicates that this is available. On some machines, this extended function either doesn't work as expected, or is unduly sensitive to the geometry BIOS is using for the drive. It would be trivial to fix boot0 to do only what booteasy does, but that would really just avoid the issue. If anyone who has been having problems would take five minutes to run a small diagnostics program http://www.freebsd.org/~rnordier/bootck-0.02.tar.gz (just dd the enclosed binary onto a floppy and reboot), I'd certainly appreciate it. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 01:43:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06831 for freebsd-current-outgoing; Mon, 19 Oct 1998 01:43:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from minotaur.com (www.minotaur.com [209.70.17.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA06783 for ; Mon, 19 Oct 1998 01:43:23 -0700 (PDT) (envelope-from jon@minotaur.com) Received: (qmail 1235 invoked from network); 19 Oct 1998 08:42:39 -0000 Received: from enterprise.minotaur.com (HELO roaming) (209.70.17.10) by www.minotaur.com with SMTP; 19 Oct 1998 08:42:39 -0000 From: "Jon E. Mitchiner" To: Subject: 3.0 Current to 3.0 Release Woes Date: Mon, 19 Oct 1998 04:50:02 -0400 Message-ID: <000001bdfb3d$76113d20$0400000a@roaming> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I couldnt believe the amount of problems I had recently when upgrading a 3.0 current supped mid-july to 3.0-release yesterday. I didnt realize that the upgrade procedure could be so problematic, so I wanted to warn other people out there that upgrading _can_ cause problems to shed some light on my errors, so others dont repeat it and perhaps someone can help correct my improper installation methods. :) Basically I read instructions and followed the upgrade prodedure. Prior to the upgrade, I followed John Birrell's E-Day message on doing the upgrade, as well as the documentation at http://www.cimlogic.com.au/. I did "make aout-to-elf" and things appeared to work well, then throughout the process, it could not find a directory -- I didn't write it down, but it was something to the effect of freebsd2/aout which I had to create (missing directory for "aout"), then re-ran make aout-to-elf which continued fine. Then at one point the GENERICupgrade kernel had an error, so I had removed the DPT_MEASURE_PERFORMANCE so the kernel would compile correctly. Then after this, the system rebooted. Things seemed to look good. Unfortunately, all the problems occurred here. Upon startup, it could not run /bin/sh or any other shell I had in /bin -- it would do a signal 10. So I was stumped and I was trying to find a way in to correct the problem. Apparently it seems that some libs and the elf programs were not compiled properly and everything was breaking. I couldn't get the system to work correctly. So I gave up, and decided to re-install (and do the upgrade) on top of my 3.0-release system to fix all the bins & libs. Throughout the process when most bins/libs were installed, I had decided to abort the process to try to salvage some things. Another problem came up -- MAKEDEV didnt make the /dev/da0* device files as I had expected make aout-to-elf would have done. No problem, so I had copied it from the /usr/src/etc/etc.i386/MAKEDEV to /dev/MAKEDEV. But apparently I still could not make /dev/da0s2a,b,e,f. It would make all the /dev/da0a-h, da0s1-4, but would not make the characters (a-h). I even tried "sh MAKEDEV /dev/da0s2a" and it would "act" like it made it but no files were generated. After talking to people on irc, they said that using the sd0* characters should still work fine. But I do recall that this was not recommended in the current discussions, but I cant find that particular message. So I wanted to make sure I use da0* for compatibility reasons. (Note: After i did a make world outlined later, I was able to makedev the da0* files correctly so this problem has been fixed.) So after the system has been unstable with continuous problems, I decided to do a full re-install on top of 3.0-RELEASE to try to fix the problem. In the middle of the install (around 25%), FreeBSD just panicked and rebooted. I was watching TV at the time and didnt get the exact error before it rebooted. I found this very odd, so I re-did the installation again and it went through fine and all the files installed (I did a basic install) and rebooted. Once the system rebooted, I could not log in at all. It was complaining about "getty[388]: /usr/bin/login: Exec format error" with /usr/bin/login which was preventing me from being able to successfully log into the system. So I had to go back and boot into single user mode. I went into /usr/bin and did "file login". It said "login: setuid data" which confused me. So I did "file file" and everything else in that directory, everything (the bins) all appeared to be correct as ELF, except "login". Thankfully I have a 3.0-Release in /usr/src so I reinstalled the "login" file from that and allowed me to login. Though the first odd message I saw was: "/usr/games/fortune: Exec format error. Wrong Architecture." so I I did file /usr/games/fortune and saw: "fortune: Infocom game data (Z-machine 8, Release 33514, Serial LN(some ascii chars here))" So apparently there are still some cruft here and there. Ive run make world and apparently it seemed to fix most of my problems. Though now I'm having a problem where one partition is now missing but I'll get to it later as it's getting kinda late. Im just wondering if I missed anything important, or did the missing directory for "aout" screw everything up and cause my system to be unstable and thus forcing me to do a manual upgrade? Thanks! Jon ___________________________________________________________________________ Jon E. Mitchiner - jon@minotaur.com Minotaur Technologies, LLC - http://www.minotaur.com - (703) 560-0683 (FAX) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 02:14:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10054 for freebsd-current-outgoing; Mon, 19 Oct 1998 02:14:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10047 for ; Mon, 19 Oct 1998 02:14:13 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id CAA12945; Mon, 19 Oct 1998 02:13:11 -0700 (PDT) Message-ID: <19981019021311.A12173@Alameda.net> Date: Mon, 19 Oct 1998 02:13:11 -0700 From: Ulf Zimmermann To: Robert Nordier , "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: To everyone who's been having trouble with the new "booteasy" Reply-To: ulf@Alameda.net References: <2317.908765344@time.cdrom.com> <199810190724.JAA01380@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810190724.JAA01380@ceia.nordier.com>; from Robert Nordier on Mon, Oct 19, 1998 at 09:24:35AM +0200 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 09:24:35AM +0200, Robert Nordier wrote: > Jordan K. Hubbard wrote: > > First, an explanation: In 3.0, we're no longer using booteasy, we're > > using Robert Nordier's boot0 replacement which is hosted entirely > > under FreeBSD (a major win). However, some people have also reported > > big problems with this so, for the mean time, I've decided to go back > > to booteasy with sysinstall until we figure out what's going on. The > > 3.0 SNAPshots will still continue to use the boot0 code so those > > wishing to help Robert figure out what's going on can and should > > continue to install snaps from current.freebsd.org. The 3.0 release > > bits on ftp.freebsd.org (and the 3.0-RELEASE CDROMs) will continue to > > use the older booteasy bits for now; I've just re-rolled and copied > > over boot floppy bits which do so. > > The problem is that boot0 is attempting to make use of an "extended" > BIOS read function, if BIOS indicates that this is available. > > On some machines, this extended function either doesn't work as > expected, or is unduly sensitive to the geometry BIOS is using for > the drive. > > It would be trivial to fix boot0 to do only what booteasy does, but > that would really just avoid the issue. > > If anyone who has been having problems would take five minutes to > run a small diagnostics program > > http://www.freebsd.org/~rnordier/bootck-0.02.tar.gz > > (just dd the enclosed binary onto a floppy and reboot), I'd certainly > appreciate it. bootck 0.02 Hit digit for hard drive to check [0-9]: 0 Using BIOS drive 0x80 BIOS geometry (0x13/0x8): 527/255/63 BIOS int 0x13 extensions: version=0x1 support=0x1 BIOS geometry (0x13/0x48): flags=0x1 0/0/0 Reading MBR - 0:* 0/1/1 0xa5 526/254/63 63 8466192 1: 0/0/0 0x0 0/0/0 0 0 2: 0/0/0 0x0 0/0/0 0 0 3: 0/0/0 0x0 0/0/0 0 0 Read test 8466192 Read test OK Hit return to reboot: This is on an Intel DK440LX motherboard with latest BIOS. The system has only the first IDE controller enabled, but the first SCSI disk is set to be the first BIOS drive via the BIOS settings. > > -- > Robert Nordier > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 02:37:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12782 for freebsd-current-outgoing; Mon, 19 Oct 1998 02:37:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12774 for ; Mon, 19 Oct 1998 02:37:52 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA19300; Mon, 19 Oct 1998 19:40:24 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810190940.TAA19300@cimlogic.com.au> Subject: Re: 3.0 Current to 3.0 Release Woes In-Reply-To: <000001bdfb3d$76113d20$0400000a@roaming> from "Jon E. Mitchiner" at "Oct 19, 98 04:50:02 am" To: jon@minotaur.com (Jon E. Mitchiner) Date: Mon, 19 Oct 1998 19:40:24 +1000 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jon E. Mitchiner wrote: > I did "make > aout-to-elf" and things appeared to work well, then throughout the process, > it could not find a directory -- I didn't write it down, but it was > something to the effect of freebsd2/aout which I had to create (missing > directory for "aout"), then re-ran make aout-to-elf which continued fine. Was this during the move of the aout libraries? If so, then the obj trees would have contained complete and up-to-date aout and elf objects, libraries and executables. A library path with "freebsd2" in it sounds like modula-3. I wonder if this is somehow related to a symlink in the library search path. > Then at one point the GENERICupgrade kernel had an error, so I had removed > the DPT_MEASURE_PERFORMANCE so the kernel would compile correctly. Then > after this, the system rebooted. Things seemed to look good. Did you check if GENERICupgrade was _*suitable*_ for your system? > Unfortunately, all the problems occurred here. Upon startup, it could not > run /bin/sh or any other shell I had in /bin -- it would do a signal 10. So > I was stumped and I was trying to find a way in to correct the problem. > Apparently it seems that some libs and the elf programs were not compiled > properly and everything was breaking. I couldn't get the system to work > correctly. Is it possible that you built this with the libc/exec problem that DES warned about on Oct 15: | If you cvsupped -current around 7 or 8 pm GMT, watch out for possible | breakage in src/lib/libc/gen/exec.c. It'll compile but may break some | programs, though it's not very serious (you'll still be able to | recompile a functioning libc even with a broken libc installed) Check | the revision number in RCS Id of that file; it should be 1.9: | | # ident /usr/src/lib/libc/gen/exec.c | /usr/src/lib/libc/gen/exec.c: | $Id: exec.c,v 1.9 1998/10/14 20:23:40 des Exp $ I've deleted the rest of your message because we don't have a hope of working out why things ended up the way they did due to consequential errors. It's unwise to hack a stage of the upgrade to get it to complete. If there is a problem that is preventing the upgrade from completing, that needs to be fixed first. To fix it, we need it reported to -current before you hack and change "evidence". This is the first report I've seen of anyone getting thoroughly hosed by the upgrade process. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 03:06:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15709 for freebsd-current-outgoing; Mon, 19 Oct 1998 03:06:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15704 for ; Mon, 19 Oct 1998 03:06:54 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id MAA04681 for ; Mon, 19 Oct 1998 12:11:32 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id MAA00180 for ; Mon, 19 Oct 1998 12:27:08 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id MAA22724; Mon, 19 Oct 1998 12:06:30 +0200 (CEST) Message-ID: <19981019120630.61686@deepo.prosa.dk> Date: Mon, 19 Oct 1998 12:06:30 +0200 From: Philippe Regnauld To: current@FreeBSD.ORG Subject: truss && init Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1) On 3.0-R (and -current from a week ago), the ktrace(1) man page mentions: -p pid Enable (disable) tracing on the indicated process id (only one -p flag is permitted). For fun, I decided to try: ktrace -p 1 ... and it works: every time I kill some random getty, the getty is respawned and the relevant stuff is logged in ./ktrace.out. However, subsequent invokations of "ktrace -p 1" do NOT turn off the tracing (it only resets the ktrace.out file, and logging continues). Only way out -> reboot or symlink to /dev/null (haven't tried) otherwise you risk filling the disk. 2) Still on 3.0-R, truss(1) mentions: # Follow an already-running process $ truss -p 1 ... and that works, though on a recent -current (~1 week ago), it hung my machine. Will try to reproduce. -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 03:24:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17543 for freebsd-current-outgoing; Mon, 19 Oct 1998 03:24:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from morgan.angis.su.OZ.AU (morgan.angis.su.OZ.AU [129.78.25.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17538 for ; Mon, 19 Oct 1998 03:24:10 -0700 (PDT) (envelope-from tonym@angis.usyd.edu.au) Received: (from tonym@localhost) by morgan.angis.su.OZ.AU (8.8.7/8.6.6) id UAA12119; Mon, 19 Oct 1998 20:23:40 +1000 (EST) Date: Mon, 19 Oct 1998 20:23:40 +1000 (EST) From: Tony Maher Message-Id: <199810191023.UAA12119@morgan.angis.su.OZ.AU> To: jb@cimlogic.com.au Subject: Re: 3.0 Current to 3.0 Release Woes Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jon E. Mitchiner wrote: > > I did "make > > aout-to-elf" and things appeared to work well, then throughout the process, > > it could not find a directory -- I didn't write it down, but it was > > something to the effect of freebsd2/aout which I had to create (missing > > directory for "aout"), then re-ran make aout-to-elf which continued fine. > > Was this during the move of the aout libraries? If so, then the obj > trees would have contained complete and up-to-date aout and elf objects, > libraries and executables. A library path with "freebsd2" in it sounds > like modula-3. I wonder if this is somehow related to a symlink in the > library search path. Similar experience upgrading 2.2.7 Stable to 3.0 Release. It broke at this point during install with: Searching library directory /usr/local/lib/m3/FreeBSD2 for a.out libraries... ldconfig: /usr/local/lib/m3/FreeBSD2/aout: No such file or directory *** Error code 255 Making the directory and rerunning the aout-to-elf-install, it all worked ok and the system booted up fine with the supplied generic kernel. Checking the system and from the install log files I note a number of libraries weren't moved due to schg flag being set. Move libc_r.so.3.0 from /usr/lib to /usr/lib/aout mv: rename /usr/lib/libc_r.so.3.0 to /usr/lib/aout/libc_r.so.3.0: Operation not permitted They are installed anyway by the aout libs created during the build so I deleted them manually afterwards. A number of dangling symlinks to libraries were also left over and removed afterwards. tonym To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 03:30:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18084 for freebsd-current-outgoing; Mon, 19 Oct 1998 03:30:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf41.cruzers.com [205.215.232.41]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA18015 for ; Mon, 19 Oct 1998 03:29:55 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 27986 invoked by uid 100); 19 Oct 1998 10:29:16 -0000 Date: Mon, 19 Oct 1998 03:29:16 -0700 To: Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: can't get vinum to work Message-ID: <19981019032916.A27956@top.worldcontrol.com> Mail-Followup-To: Greg Lehey , freebsd-current@FreeBSD.ORG References: <19981018215221.A27539@top.worldcontrol.com> <19981019143824.G4015@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.6i In-Reply-To: <19981019143824.G4015@freebie.lemis.com>; from Greg Lehey on Mon, Oct 19, 1998 at 02:38:24PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 02:38:24PM +0930, Greg Lehey wrote: > Where did this version of Vinum come from? The message that is now > output is -current as of Mon Oct 18 20:04:21 PDT 1998 > I suspect your real problem is that /dev/da1h and /dev/da2h are set > with file system type 4.2BSD. This is appropriate for making UFS file > systems, and for some obscure reason ccd requires it, but it's a > sure-fire recipe for shooting yourself in the foot. Vinum will > ultimately require a file system type 'vinum', but currently it > insists on 'unused'. My troubles seem to be more basic and probably unrelated to vinum. A simple 'disklabel -e da1' brings up the editor screen with a very reasonable set of numbers. Exiting the editor results in an: label: Operation not supported by device and a pair of messages in /var/log/messages: Oct 19 03:26:40 bls2 /kernel: da1: cannot find label (no disk label) Oct 19 03:26:40 bls2 /kernel: da1s1: cannot find label (no disk label) I resupped and issued a make world just in case there is some out-of-syncness someplace. I may have forgotten the mention the system is SMP. -- brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 03:53:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19896 for freebsd-current-outgoing; Mon, 19 Oct 1998 03:53:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19885 for ; Mon, 19 Oct 1998 03:52:51 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id MAA19830; Mon, 19 Oct 1998 12:51:23 +0200 (CEST) Message-ID: <19981019125122.A19779@foobar.franken.de> Date: Mon, 19 Oct 1998 12:51:22 +0200 From: Harold Gutch To: Philippe Regnauld , current@FreeBSD.ORG Subject: Re: truss && init References: <19981019120630.61686@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981019120630.61686@deepo.prosa.dk>; from Philippe Regnauld on Mon, Oct 19, 1998 at 12:06:30PM +0200 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 12:06:30PM +0200, Philippe Regnauld wrote: > 1) On 3.0-R (and -current from a week ago), the ktrace(1) man page > mentions: > > -p pid Enable (disable) tracing on the indicated process id (only one -p > flag is permitted). It also says: -c Clear the trace points associated with the specified file or pro- cesses. And, in the EXAMPLES-section: # disable all tracing of process 65 $ ktrace -cp 65 > ktrace -p 1 > > However, subsequent invokations of "ktrace -p 1" do NOT turn > off the tracing (it only resets the ktrace.out file, and > logging continues). ktrace -cp 1 -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 04:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23430 for freebsd-current-outgoing; Mon, 19 Oct 1998 04:11:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23425 for ; Mon, 19 Oct 1998 04:11:09 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id NAA26133 for freebsd-current@freebsd.org; Mon, 19 Oct 1998 13:10:42 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m0zVCdd-000X1kC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Mon, 19 Oct 1998 12:34:09 +0200 (CEST) Message-ID: <19981019123408.W21112@mips.rhein-neckar.de> Date: Mon, 19 Oct 1998 12:34:08 +0200 From: Christian Weisgerber To: freebsd-current@FreeBSD.ORG Subject: 3.0-R fixit.flp doesn't work Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I try booting the 3.0-RELEASE fixit floppy from the menu on the install disk I get a prompt to insert a writable fixit disk, another prompt to insert the disk, short activity on the drive, and yet again the first prompt to insert the disk (which of course is in the drive all along, and yes, it's writable). Sysinstall seems to get stuck at this point. MD5 (boot.flp) = b2fd604c0547088d40f12e594efff116 MD5 (fixit.flp) = 9aa1b6ba6724454350c597f047767fbd -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de carpe librum: books 'n' reviews To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 04:16:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23768 for freebsd-current-outgoing; Mon, 19 Oct 1998 04:16:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23759 for ; Mon, 19 Oct 1998 04:16:31 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from bergelmir.ifi.uio.no (2602@bergelmir.ifi.uio.no [129.240.65.172]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id NAA07010 for ; Mon, 19 Oct 1998 13:16:05 +0200 (MET DST) Received: (from dag-erli@localhost) by bergelmir.ifi.uio.no ; Mon, 19 Oct 1998 13:16:03 +0200 (MET DST) Mime-Version: 1.0 To: current@FreeBSD.ORG Subject: sh and ~ expansion Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 19 Oct 1998 13:16:03 +0200 Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA23764 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why doesn't ~ expansion work in the following case: export GLORB=~ as it does in GLORB=~; export GLORB Is it a feature or a bug? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 04:42:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25915 for freebsd-current-outgoing; Mon, 19 Oct 1998 04:42:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25909 for ; Mon, 19 Oct 1998 04:42:04 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id HAA15518; Mon, 19 Oct 1998 07:41:00 -0400 (EDT) Date: Mon, 19 Oct 1998 07:41:00 -0400 (EDT) From: Chuck Robey To: Bruce Evans cc: andyf@speednet.com.au, freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-Reply-To: <199810190541.PAA22459@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Bruce Evans wrote: > >> A real short history on what's changed in > >> regards to this would be a nice thing to stick in the mail archives. > > 1. (Integer) type numbers for file systems are broken as designed. > 2. Use of them was mostly fixed in 4.4BSD-Lite2 (May 1995). > 3. FreeBSD is taking a long time to complete the Lite2 merge. Some > mileposts according to sys/mount.h: > 1.1.1.2 1996/03/11 Import on vendor branch. > 1.36 1997/02/10 Merge (kernel only, 90% only). > 1.67 1998/09/07 Merge removal of MOUNT* definitions for type numbers. > 1.68 1998/10/15 Tag for first release with Lite2 changes in it. In looking around at how other Unixes are doing this, I notice that many have their statfs stuff in a different file than mount.h ... I think in sys/statvfs.h. Is there some URL where I can go hunt around at how 4.4BSDLite2 is doing it, and see if we're going that direction? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 04:58:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA27582 for freebsd-current-outgoing; Mon, 19 Oct 1998 04:58:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA27575 for ; Mon, 19 Oct 1998 04:58:08 -0700 (PDT) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id HAA22582; Mon, 19 Oct 1998 07:57:41 -0400 (EDT) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA02626; Mon, 19 Oct 1998 07:57:20 -0400 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.1/8.9.1) id HAA04554; Mon, 19 Oct 1998 07:56:55 -0400 (EDT) (envelope-from brdean) From: Brian Dean Message-Id: <199810191156.HAA04554@dean.pc.sas.com> Subject: Re: more 3.0-RELEASE boot.flp problems In-Reply-To: <2009.908763356@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 18, 1998 7:15:56 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 19 Oct 1998 07:56:45 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I submitted a problem report on this yesterday. It is PR # 8368. > > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. > > Well, it sounds like the new boot manager (which is not BOOTEASY, > even though it looks a bit like it) is in fact broken somehow, > even though it works on my test machines (damn!). Could you tell > us a bit more about whether this was a dedicated/non-dedicated > installation, whether there were other OSes on the disk, etc etc? > > I really would like to continue using the new boot0 since it's > the first time we've had a boot manager for which the sources were > compiliable and maintained under the FreeBSD tree, unlike BOOTEASY > which was a DOS program getting ever more stale under our umbrella. > > - Jordan > > P.S. to Robert: I *told* you we should have made those prompts > look more different; people are still confusing it with BOOTEASY! :-) -Brian -- Brian Dean Process Engineering brdean@unx.sas.com (x5235) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 05:14:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28845 for freebsd-current-outgoing; Mon, 19 Oct 1998 05:14:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28831 for ; Mon, 19 Oct 1998 05:14:25 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA18383; Mon, 19 Oct 1998 22:13:42 +1000 Date: Mon, 19 Oct 1998 22:13:42 +1000 From: Bruce Evans Message-Id: <199810191213.WAA18383@godzilla.zeta.org.au> To: bde@zeta.org.au, chuckr@mat.net Subject: Re: mount flags Cc: andyf@speednet.com.au, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In looking around at how other Unixes are doing this, I notice that many >have their statfs stuff in a different file than mount.h ... I think in >sys/statvfs.h. Is there some URL where I can go hunt around at how >4.4BSDLite2 is doing it, and see if we're going that direction? Mounting is very unportable. amd seems to have about 200 options, including about 5 options related to statfs. ftp.freebsd.org has most Lite2 sources under cvs :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 05:36:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00263 for freebsd-current-outgoing; Mon, 19 Oct 1998 05:36:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00258 for ; Mon, 19 Oct 1998 05:36:54 -0700 (PDT) (envelope-from tejblum@arc.hq.cti.ru) Received: from arc.hq.cti.ru (localhost [127.0.0.1]) by arc.hq.cti.ru (8.9.0/8.9.0) with ESMTP id QAA13616; Mon, 19 Oct 1998 16:35:48 +0400 (MSD) Message-Id: <199810191235.QAA13616@arc.hq.cti.ru> X-Mailer: exmh version 2.0zeta 7/24/97 To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-reply-to: Your message of "Sun, 18 Oct 1998 12:48:39 EDT." Date: Mon, 19 Oct 1998 16:35:48 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a very recently broke thing that was happily using a call to > statfs, to tell if it was an NFS filesystem or not. Last time I had > occasion to take a look at this, there were flags of the sort MOUNT_XXX, > where the XXX could have been UFS, MFS, NFS, etc. The application is > specifically looking for MOUNT_NFS, and it's just not around anymore, > that I can find. Just a small note: consider check for (f_flags & MNT_LOCAL) instead. I suspect it may be more appropriate in this case. (It is also Lite2-ism, AFAIR). Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 05:42:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00673 for freebsd-current-outgoing; Mon, 19 Oct 1998 05:42:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00668 for ; Mon, 19 Oct 1998 05:42:23 -0700 (PDT) (envelope-from mike@seidata.com) From: mike@seidata.com Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id IAA00861; Mon, 19 Oct 1998 08:41:48 -0400 (EDT) Date: Mon, 19 Oct 1998 08:41:48 -0400 (EDT) To: Robert Nordier cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: To everyone who's been having trouble with the new "booteasy" In-Reply-To: <199810190724.JAA01380@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Robert Nordier wrote: > http://www.freebsd.org/~rnordier/bootck-0.02.tar.gz Curious... what's continuous beeping mean? Other than 'You messed up the floppy...' ;) Later, -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 06:19:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03900 for freebsd-current-outgoing; Mon, 19 Oct 1998 06:19:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03893 for ; Mon, 19 Oct 1998 06:19:09 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id PAA11904 for ; Mon, 19 Oct 1998 15:18:43 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id PAA18058 for ; Mon, 19 Oct 1998 15:18:40 +0200 (MET DST) Received: (qmail 1935 invoked by uid 666); 19 Oct 1998 13:18:59 -0000 Date: Mon, 19 Oct 1998 15:18:59 +0200 From: Jos Backus To: current@FreeBSD.ORG Subject: Re: fetch -p Message-ID: <19981019151859.A1915@hal.mpn.cp.philips.com> References: <19981001215854.A15071@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.10i In-Reply-To: <19981001215854.A15071@hal.mpn.cp.philips.com>; from Jos Backus on Thu, Oct 01, 1998 at 09:58:54PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 02, 1998 at 02:26:11AM +0930, Kris Kennaway wrote: > When using fetch -p to download ports distfiles in passive mode, I > consistently get files with the last few hundred bytes missing, and have to > go and finish the transfer manually. Has anyone else seen this behaviour? Turns out this can be caused by buggy proxy servers. For a fix, try adding -b to the fetch invocation (or stick ``FETCH_BEFORE_ARGS=-b'' in /etc/make.conf). Hth, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 06:32:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05182 for freebsd-current-outgoing; Mon, 19 Oct 1998 06:32:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from minotaur.com (www.minotaur.com [209.70.17.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA05176 for ; Mon, 19 Oct 1998 06:32:33 -0700 (PDT) (envelope-from jon@minotaur.com) Received: (qmail 12534 invoked from network); 19 Oct 1998 13:31:59 -0000 Received: from enterprise.minotaur.com (HELO roaming) (209.70.17.10) by www.minotaur.com with SMTP; 19 Oct 1998 13:31:59 -0000 From: "Jon E. Mitchiner" To: Subject: RE: 3.0-R fixit.flp doesn't work Date: Mon, 19 Oct 1998 09:39:28 -0400 Message-ID: <002e01bdfb65$e542c970$0400000a@roaming> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: <19981019123408.W21112@mips.rhein-neckar.de> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yup, I experienced the same problem yesterday as well, and couldn't use the fixit floppy. It seems to be hosed. Thanks! Jon > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Christian > Weisgerber > Sent: Monday, October 19, 1998 6:34 AM > To: freebsd-current@FreeBSD.ORG > Subject: 3.0-R fixit.flp doesn't work > > > When I try booting the 3.0-RELEASE fixit floppy from the menu on the > install disk I get a prompt to insert a writable fixit disk, another > prompt to insert the disk, short activity on the drive, and yet again > the first prompt to insert the disk (which of course is in > the drive all > along, and yes, it's writable). Sysinstall seems to get stuck at this > point. > > MD5 (boot.flp) = b2fd604c0547088d40f12e594efff116 > MD5 (fixit.flp) = 9aa1b6ba6724454350c597f047767fbd > > -- > Christian "naddy" Weisgerber > naddy@mips.rhein-neckar.de > carpe librum: books 'n' reviews > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 06:56:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07539 for freebsd-current-outgoing; Mon, 19 Oct 1998 06:56:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07528 for ; Mon, 19 Oct 1998 06:56:18 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id PAA04103; Mon, 19 Oct 1998 15:55:37 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810191355.PAA04103@gratis.grondar.za> To: volf@oasis.IAEhv.nl (Frank Volf) cc: current@FreeBSD.ORG Subject: Re: Trouble with CVS-CUR? In-Reply-To: Your message of " Mon, 19 Oct 1998 09:23:01 +0200." <199810190723.HAA00688@avalon.oasis.IAEhv.nl> References: <199810190723.HAA00688@avalon.oasis.IAEhv.nl> Date: Mon, 19 Oct 1998 15:55:35 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG wrote: > > Hi, > > Is it only me or do other people also have trouble with CTM? In particular > I'm still awaiting the CTM delta that contains the 3.0 RELEASE tags. Until > now I only received a few deltas that tag part of the ports tree. But the > src tree itself has not been touched. > > Here are the deltas that I received recently: > > 10 -rw-r--r-- 1 root staff 9597 Oct 15 18:33 cvs-cur.4729.gz > 14 -rw-r--r-- 1 root staff 13915 Oct 15 18:42 cvs-cur.4730.gz > 120 -rw-r--r-- 1 root staff 113681 Oct 16 22:18 cvs-cur.4731.gz > 14 -rw-r--r-- 1 root staff 14030 Oct 16 22:18 cvs-cur.4732.gz > 248 -rw-r--r-- 1 root staff 239902 Oct 16 22:18 cvs-cur.4733.gz > 61 -rw-r--r-- 1 root staff 61744 Oct 18 11:27 cvs-cur.4734.gz > 120 -rw-r--r-- 1 root staff 109291 Oct 18 20:27 cvs-cur.4735.gz > 2 -rw-r--r-- 1 root staff 1962 Oct 19 08:59 cvs-cur.4736.gz > > I check this with the ftp site, but they do not seem to have more deltas > than I. > > Anything wrong? Yes. I am trying to fix it. Please be patient. :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 06:57:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07615 for freebsd-current-outgoing; Mon, 19 Oct 1998 06:57:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07610 for ; Mon, 19 Oct 1998 06:57:19 -0700 (PDT) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id KAA05875; Mon, 19 Oct 1998 10:56:30 -0300 (ADT) Date: Mon, 19 Oct 1998 10:56:29 -0300 (ADT) From: Marc Fournier X-Sender: marc@iceberg To: Edwin Culp cc: freebsd-current@FreeBSD.ORG Subject: Re: paranoid question: aout vs ELF... In-Reply-To: <36279552.F92C02DE@webwizard.org.mx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 16 Oct 1998, Edwin Culp wrote: > "Marc G. Fournier" wrote: > > > I'm going to ask this, which has most likely been asked before,but... > > > > I'm about to take a chance and do a remote upgrade of my system from > > 3.0-AOUT to 3.0-CURRENT.. > > > > My plan (once I can get the cvs problem rectified) is to do a 'make > > buildworld' on the source tree, then build a new kernel, then reboot, and, > > if I make it that far, 'make installworld'... > > IMO > > I would change that to > # make aout-to-elf > shouldn't be a problem Does this build&install, or just build? > # cd /sys/boot > # make depend && make all && make install > Should't be a problem > # cd /usr/src/sys/i386/conf > Compare your config file with the changes to GENERIC and/or LINT > # KERNFORMAT=elf;export KERNFORMAT > # config -r YourKernel > # cd ../../compile/YourKernel > # make depend && make && make install > Now I would reboot with a big smile and update all my rc's and /etc en > general. > > provecho y saludos > > ed > > > > > > > My paranoia...all my aout stuff in /usr/local/bin won't all of a sudden > > break...will it? > > > > Marc G. Fournier scrappy@hub.org > > Systems Administrator @ hub.org > > scrappy@{postgresql|isc}.org ICQ#7615664 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 07:07:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08414 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:07:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08409 for ; Mon, 19 Oct 1998 07:07:46 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id JAA12151; Mon, 19 Oct 1998 09:02:38 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <362B467E.B5D9F088@webwizard.org.mx> Date: Mon, 19 Oct 1998 09:02:38 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Marc Fournier CC: freebsd-current@FreeBSD.ORG Subject: Re: paranoid question: aout vs ELF... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Fournier wrote: > On Fri, 16 Oct 1998, Edwin Culp wrote: > > > "Marc G. Fournier" wrote: > > > > > I'm going to ask this, which has most likely been asked before,but... > > > > > > I'm about to take a chance and do a remote upgrade of my system from > > > 3.0-AOUT to 3.0-CURRENT.. > > > > > > My plan (once I can get the cvs problem rectified) is to do a 'make > > > buildworld' on the source tree, then build a new kernel, then reboot, and, > > > if I make it that far, 'make installworld'... > > > > IMO > > > > I would change that to > > # make aout-to-elf > > shouldn't be a problem > > Does this build&install, or just build? Both > > > > # cd /sys/boot > > # make depend && make all && make install > > Should't be a problem > > # cd /usr/src/sys/i386/conf > > Compare your config file with the changes to GENERIC and/or LINT > > # KERNFORMAT=elf;export KERNFORMAT > > # config -r YourKernel > > # cd ../../compile/YourKernel > > # make depend && make && make install > > Now I would reboot with a big smile and update all my rc's and /etc en > > general. > > > > provecho y saludos > > > > ed > > > > > > > > > > > My paranoia...all my aout stuff in /usr/local/bin won't all of a sudden > > > break...will it? > > > > > > Marc G. Fournier scrappy@hub.org > > > Systems Administrator @ hub.org > > > scrappy@{postgresql|isc}.org ICQ#7615664 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > Marc G. Fournier marc.fournier@acadiau.ca > Systems Administrator, Acadia University > > "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 07:08:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08545 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:08:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08537 for ; Mon, 19 Oct 1998 07:08:06 -0700 (PDT) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id LAA07196; Mon, 19 Oct 1998 11:07:35 -0300 (ADT) Date: Mon, 19 Oct 1998 11:07:34 -0300 (ADT) From: Marc Fournier X-Sender: marc@iceberg To: Edwin Culp cc: freebsd-current@FreeBSD.ORG Subject: Re: paranoid question: aout vs ELF... In-Reply-To: <362B467E.B5D9F088@webwizard.org.mx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Edwin Culp wrote: > Marc Fournier wrote: > > > On Fri, 16 Oct 1998, Edwin Culp wrote: > > > > > "Marc G. Fournier" wrote: > > > > > > > I'm going to ask this, which has most likely been asked before,but... > > > > > > > > I'm about to take a chance and do a remote upgrade of my system from > > > > 3.0-AOUT to 3.0-CURRENT.. > > > > > > > > My plan (once I can get the cvs problem rectified) is to do a 'make > > > > buildworld' on the source tree, then build a new kernel, then reboot, and, > > > > if I make it that far, 'make installworld'... > > > > > > IMO > > > > > > I would change that to > > > # make aout-to-elf > > > shouldn't be a problem > > > > Does this build&install, or just build? > > Both Okay, then that makes me *really* nervous...does the following sound safe? cd /usr/src make aout-to-elf-build cd /usr/src/usr.sbin/config && make install cd /usr/src/sys/i386/conf config -r MyKernel cd ../../compile/MyKernel make depend && make reboot cd /usr/src make aout-to-elf-install I'm still running a 3.0-CURRENT machine as of July 24th or so...its a production machine, and its half a country away, so I'm very nervous... > > > > > > > > # cd /sys/boot > > > # make depend && make all && make install > > > Should't be a problem > > > # cd /usr/src/sys/i386/conf > > > Compare your config file with the changes to GENERIC and/or LINT > > > # KERNFORMAT=elf;export KERNFORMAT > > > # config -r YourKernel > > > # cd ../../compile/YourKernel > > > # make depend && make && make install > > > Now I would reboot with a big smile and update all my rc's and /etc en > > > general. > > > > > > provecho y saludos > > > > > > ed > > > > > > > > > > > > > > > My paranoia...all my aout stuff in /usr/local/bin won't all of a sudden > > > > break...will it? > > > > > > > > Marc G. Fournier scrappy@hub.org > > > > Systems Administrator @ hub.org > > > > scrappy@{postgresql|isc}.org ICQ#7615664 > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > Marc G. Fournier marc.fournier@acadiau.ca > > Systems Administrator, Acadia University > > > > "These are my opinions, which are not necessarily shared by my employer" > > Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 07:12:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08837 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:12:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08823 for ; Mon, 19 Oct 1998 07:12:02 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id KAA21928 for ; Mon, 19 Oct 1998 10:11:36 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA01768; Mon, 19 Oct 1998 10:11:36 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id KAA21204 for freebsd-current@freebsd.org; Mon, 19 Oct 1998 10:11:35 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199810191411.KAA21204@bb01f39.unx.sas.com> Subject: Conflicting ping performance To: freebsd-current@FreeBSD.ORG Date: Mon, 19 Oct 1998 10:11:35 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We're seeing some very interesting ping timings. Wall-clock vs. recorded ping statistics. In the statistics below, the -current system is recording ping statistics 1/2 the values of the march snap. However, the march snap completes in 0.05 seconds, while the -current system requires 10 seconds. A system running the 980825-SNAP gives the same strange results as the -current system. The network controllers should not have any effect since we are testing against localhost. (however, the two machines below are identical hardware configs using fxp0). This problem replicates when testing the actual network devices. Can anyone else replicate this problem? Comments, Critiques, or diffs to fix this are appreciated. Thanks, John ================================================================= From a -current system: (Sunday Oct 18, 20:35:40 EDT) # uname -a FreeBSD FreeBSD.pc.sas.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Sun Oct 18 20:35:40 EDT 1998 root@FreeBSD.pc.sas.com:/usr/src/sys/compile/FreeBSD i386 # time ping -c 500 -f localhost PING localhost.sas.com (127.0.0.1): 56 data bytes . --- localhost.sas.com ping statistics --- 500 packets transmitted, 500 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.033/0.038/0.258/0.015 ms 10.00s real 0.00s user 0.07s system # ================================================================= From a march snap: # uname -a FreeBSD magenta.pc.sas.com 3.0-980325-SNAP FreeBSD 3.0-980325-SNAP #1: Tue May 12 23:29:14 EST 1998 root@magenta.pc.sas.com:/usr/src/sys/compile/MAGENTA i386 # time ping -c 500 -f localhost PING localhost (127.0.0.1): 56 data bytes . --- localhost ping statistics --- 500 packets transmitted, 500 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.080/0.082/0.186/0.005 ms 0.05s real 0.02s user 0.03s system # ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 07:13:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08893 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:13:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08888 for ; Mon, 19 Oct 1998 07:13:01 -0700 (PDT) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA29681; Mon, 19 Oct 1998 09:12:30 -0500 (EST) Date: Mon, 19 Oct 1998 09:12:30 -0500 (EST) From: John Fieber To: "Kenneth D. Merry" cc: nathan@rtfm.net, freebsd-current@FreeBSD.ORG Subject: Re: 3.0-R, CAM, and audio tracks In-Reply-To: <199810190624.AAA21045@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Kenneth D. Merry wrote: > > I've never been able to get decent audio dumps from my Toshiba > > 3501 using tosha (or anything else for that matter), > > Do you mean "never" as in "not with CAM" or never as in "not with CAM or > the old SCSI subsystem"? The latter. With the old SCSI system, the audio would come out with lots of pops, clicks and dropouts and I sometimes had to re-boot to regain use of the CD-ROM drive. I suspect this drive hase some sort of "quirk". > That's not good. Were there any interesting error messages? I neglected to write them down and naturally they didn't make it into /var/log/messages since the whole SCSI subsystem was wedged. I'm sure I could duplicate the experience though.... -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 07:20:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09926 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:20:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09910 for ; Mon, 19 Oct 1998 07:20:11 -0700 (PDT) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id QAA07958 for freebsd-current@FreeBSD.ORG; Mon, 19 Oct 1998 16:16:39 +0200 (CEST) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199810191416.QAA07958@ocean.campus.luth.se> Subject: Re: make world breakage In-Reply-To: <199810181213.OAA05194@ocean.campus.luth.se> from Mikael Karpberg at "Oct 18, 98 02:13:58 pm" To: freebsd-current@FreeBSD.ORG Date: Mon, 19 Oct 1998 16:16:39 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG About my error with make world: According to Mikael Karpberg: > Anyway... His make world ends like this: > > ===> gnu/usr.bin/perl > ===> gnu/usr.bin/perl/libperl > ===> gnu/usr.bin/perl/miniperl [...] > Checking if your kit is complete... > Looks good > Writing Makefile for IPC::SysV > ==> Your Makefile has been rebuilt. <== > ==> Please rerun the make command. <== > false > *** Error code 1 > This problem dissapeared with an "rm -rf /usr/obj/" just FYI. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 07:22:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10082 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:22:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10077 for ; Mon, 19 Oct 1998 07:22:53 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA03011; Mon, 19 Oct 1998 07:23:46 -0700 (PDT) Message-Id: <199810191423.HAA03011@implode.root.com> To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: Conflicting ping performance In-reply-to: Your message of "Mon, 19 Oct 1998 10:11:35 EDT." <199810191411.KAA21204@bb01f39.unx.sas.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 19 Oct 1998 07:23:46 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We're seeing some very interesting ping timings. Wall-clock vs. >recorded ping statistics. > > In the statistics below, the -current system is recording ping >statistics 1/2 the values of the march snap. However, the march >snap completes in 0.05 seconds, while the -current system requires >10 seconds. A system running the 980825-SNAP gives the same strange >results as the -current system. > > The network controllers should not have any effect since we are >testing against localhost. (however, the two machines below are >identical hardware configs using fxp0). > > This problem replicates when testing the actual network devices. > > Can anyone else replicate this problem? > > Comments, Critiques, or diffs to fix this are appreciated. Caused by this: RCS file: /home/ncvs/src/sbin/ping/ping.c,v ... ---------------------------- revision 1.41 date: 1998/08/26 18:51:37; author: des; state: Exp; lines: +1 -13 Remove -c restrictions from previous commit. ---------------------------- revision 1.40 date: 1998/08/26 01:58:39; author: dillon; state: Exp; lines: +38 -11 (well tested at BEST): -i option can now take FP values (e.g. -i 0.1), extremely useful for networking testing. Other options secured from user-level D.O.S. attacks. -f, -s now root-only. -i wait times < 1.0 root-only. -c count limited to 100 and defaults to 16 when ping run by non-root user. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 07:33:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10905 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:33:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10897 for ; Mon, 19 Oct 1998 07:33:15 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id QAA07324 for freebsd-current@freebsd.org; Mon, 19 Oct 1998 16:32:52 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m0zVFqc-000WyOC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Mon, 19 Oct 1998 15:59:46 +0200 (CEST) Message-Id: Date: Mon, 19 Oct 1998 15:59:46 +0200 (CEST) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) To: freebsd-current@FreeBSD.ORG Subject: Re: GNU Awk replacement In-Reply-To: <19981018215440.A25652@nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981018215440.A25652@nuxi.com>, David O'Brien wrote: > What do people think about replacing GNU awk in the base system with the > One True Awk(tm) by bwk? Because it doesn't conform to POSIX, and like other UNIX(TM) code from that era probably has undocumented fixed-size array limitations? What strikes me as a bit bizarre is that FreeBSD uses gawk whereas Debian GNU/Linux(!) uses mawk. mawk is less bloated, faster, and also POSIX compliant. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de See another pointless homepage at . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 07:39:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11413 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:39:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11398 for ; Mon, 19 Oct 1998 07:38:54 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id KAA27305; Mon, 19 Oct 1998 10:38:18 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA08396; Mon, 19 Oct 1998 10:38:18 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id KAA23348; Mon, 19 Oct 1998 10:38:18 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199810191438.KAA23348@bb01f39.unx.sas.com> Subject: Re: Conflicting ping performance In-Reply-To: <199810191423.HAA03011@implode.root.com> from David Greenman at "Oct 19, 98 07:23:46 am" To: dg@root.com Date: Mon, 19 Oct 1998 10:38:18 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Are you telling me it 'should' work this way now? Or that this behaviour is a bug and was introduced in 1.40? It would appear that the -i option is adversely affecting the -f option, and, yes, I am running this test as root so -c should allow infinity. If it's a bug, I'll look into a submitting a diff... Thanks, John > > We're seeing some very interesting ping timings. Wall-clock vs. > >recorded ping statistics. > > > > In the statistics below, the -current system is recording ping > >statistics 1/2 the values of the march snap. However, the march > >snap completes in 0.05 seconds, while the -current system requires > >10 seconds. A system running the 980825-SNAP gives the same strange > >results as the -current system. > > > > The network controllers should not have any effect since we are > >testing against localhost. (however, the two machines below are > >identical hardware configs using fxp0). > > > > This problem replicates when testing the actual network devices. > > > > Can anyone else replicate this problem? > > > > Comments, Critiques, or diffs to fix this are appreciated. > > Caused by this: > > RCS file: /home/ncvs/src/sbin/ping/ping.c,v > ... > ---------------------------- > revision 1.41 > date: 1998/08/26 18:51:37; author: des; state: Exp; lines: +1 -13 > Remove -c restrictions from previous commit. > ---------------------------- > revision 1.40 > date: 1998/08/26 01:58:39; author: dillon; state: Exp; lines: +38 -11 > (well tested at BEST): -i option can now take FP values (e.g. -i 0.1), > extremely useful for networking testing. Other options secured from > user-level D.O.S. attacks. -f, -s now root-only. -i wait times < 1.0 > root-only. -c count limited to 100 and defaults to 16 when ping run > by non-root user. > > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 07:57:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12913 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:57:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12905 for ; Mon, 19 Oct 1998 07:57:15 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA03358; Mon, 19 Oct 1998 07:58:11 -0700 (PDT) Message-Id: <199810191458.HAA03358@implode.root.com> To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: Conflicting ping performance In-reply-to: Your message of "Mon, 19 Oct 1998 10:38:18 EDT." <199810191438.KAA23348@bb01f39.unx.sas.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 19 Oct 1998 07:58:11 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are you telling me it 'should' work this way now? Or that this >behaviour is a bug and was introduced in 1.40? It would appear >that the -i option is adversely affecting the -f option, and, yes, >I am running this test as root so -c should allow infinity. > > If it's a bug, I'll look into a submitting a diff... No, it shouldn't work that way. I've done some more checking and I think now that those changes aren't the cause. It appears that the system is returning ENOBUFS more easily than it used to. Needs more investigation. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 07:57:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12942 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:57:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12935 for ; Mon, 19 Oct 1998 07:57:26 -0700 (PDT) (envelope-from croot@btp1da.phy.uni-bayreuth.de) Received: (from root@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id QAA02282; Mon, 19 Oct 1998 16:56:49 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199810191438.KAA23348@bb01f39.unx.sas.com> Date: Mon, 19 Oct 1998 16:56:49 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: "John W. DeBoskey" Subject: Re: Conflicting ping performance Cc: freebsd-current@FreeBSD.ORG, dg@root.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Oct-98 John W. DeBoskey wrote: > Hi, > > Are you telling me it 'should' work this way now? Or that this > behaviour is a bug and was introduced in 1.40? It would appear > that the -i option is adversely affecting the -f option, and, yes, > I am running this test as root so -c should allow infinity. > > If it's a bug, I'll look into a submitting a diff... > > Thanks, > John > No, I believe it means: use "time ping -c 500 -i 0 localhost > /dev/null" as root instead. Werner > >> > We're seeing some very interesting ping timings. Wall-clock vs. >> >recorded ping statistics. >> > >> > In the statistics below, the -current system is recording ping >> >statistics 1/2 the values of the march snap. However, the march >> >snap completes in 0.05 seconds, while the -current system requires >> >10 seconds. A system running the 980825-SNAP gives the same strange >> >results as the -current system. >> > >> > The network controllers should not have any effect since we are >> >testing against localhost. (however, the two machines below are >> >identical hardware configs using fxp0). >> > >> > This problem replicates when testing the actual network devices. >> > >> > Can anyone else replicate this problem? >> > >> > Comments, Critiques, or diffs to fix this are appreciated. >> >> Caused by this: >> >> RCS file: /home/ncvs/src/sbin/ping/ping.c,v >> ... >> ---------------------------- >> revision 1.41 >> date: 1998/08/26 18:51:37; author: des; state: Exp; lines: +1 -13 >> Remove -c restrictions from previous commit. >> ---------------------------- >> revision 1.40 >> date: 1998/08/26 01:58:39; author: dillon; state: Exp; lines: +38 -11 >> (well tested at BEST): -i option can now take FP values (e.g. -i 0.1), >> extremely useful for networking testing. Other options secured from >> user-level D.O.S. attacks. -f, -s now root-only. -i wait times < 1.0 >> root-only. -c count limited to 100 and defaults to 16 when ping run >> by non-root user. >> >> >> -DG >> >> David Greenman >> Co-founder/Principal Architect, The FreeBSD Project >> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 08:30:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15666 for freebsd-current-outgoing; Mon, 19 Oct 1998 08:30:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15661 for ; Mon, 19 Oct 1998 08:30:34 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id KAA01256; Mon, 19 Oct 1998 10:28:51 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <362B5AB3.CABDA7E5@webwizard.org.mx> Date: Mon, 19 Oct 1998 10:28:51 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Marc Fournier CC: freebsd-current@FreeBSD.ORG Subject: Re: paranoid question: aout vs ELF... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Fournier wrote: > On Mon, 19 Oct 1998, Edwin Culp wrote: > > > Marc Fournier wrote: > > > > > On Fri, 16 Oct 1998, Edwin Culp wrote: > > > > > > > "Marc G. Fournier" wrote: > > > > > > > > > I'm going to ask this, which has most likely been asked before,but... > > > > > > > > > > I'm about to take a chance and do a remote upgrade of my system from > > > > > 3.0-AOUT to 3.0-CURRENT.. > > > > > > > > > > My plan (once I can get the cvs problem rectified) is to do a 'make > > > > > buildworld' on the source tree, then build a new kernel, then reboot, and, > > > > > if I make it that far, 'make installworld'... > > > > > > > > IMO > > > > > > > > I would change that to > > > > # make aout-to-elf > > > > shouldn't be a problem > > > > > > Does this build&install, or just build? > > > > Both > > Okay, then that makes me *really* nervous...does the following sound safe? > > cd /usr/src > make aout-to-elf-build > cd /usr/src/usr.sbin/config && make install > cd /usr/src/sys/i386/conf > config -r MyKernel > cd ../../compile/MyKernel > make depend && make > > reboot > cd /usr/src > make aout-to-elf-install > > I'm still running a 3.0-CURRENT machine as of July 24th or so...its a > production machine, and its half a country away, so I'm very nervous... Me too, I'm doing it right now on one of my customer's machines that is across Mexico. That's what makes life interesting:-) I get a lot more nervous having a new kernel before the world install. I've never been a fan of that system. Hopefully someone will say I'm wrong and I'll feel better. I'm stubbornly using the following because it has worked for me, and if it breaks on the build, no problem, if it installs even less problems:-) : # make aout-to-elf # cd /sys/boot # make depend && make all && make install # cd /usr/src/sys/i386/conf # KERNFORMAT=elf;export KERNFORMAT # config -r MyKernel # cd ../../compile/MyKernel # make depend && make && make install I then do a new X11 - afterstep, apache, squid, and a change of all the daily programs that are in aout and cause nitty problems problems. Maybe I just like doing a file * and everything answers as "ELF 32 bit":-). ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 08:38:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16335 for freebsd-current-outgoing; Mon, 19 Oct 1998 08:38:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16330 for ; Mon, 19 Oct 1998 08:38:04 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA05261; Mon, 19 Oct 1998 11:37:16 -0400 (EDT) (envelope-from wollman) Date: Mon, 19 Oct 1998 11:37:16 -0400 (EDT) From: Garrett Wollman Message-Id: <199810191537.LAA05261@khavrinen.lcs.mit.edu> To: naddy@mips.rhein-neckar.de (Christian Weisgerber) Cc: freebsd-current@FreeBSD.ORG Subject: Re: GNU Awk replacement In-Reply-To: References: <19981018215440.A25652@nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < In article <19981018215440.A25652@nuxi.com>, > David O'Brien wrote: >> What do people think about replacing GNU awk in the base system with the >> One True Awk(tm) by bwk? > Because it doesn't conform to POSIX, and like other UNIX(TM) code from > that era probably has undocumented fixed-size array limitations? How about you actually look at the code before you make such statements? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 08:55:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17927 for freebsd-current-outgoing; Mon, 19 Oct 1998 08:55:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rossel.solplus.de (rossel.solplus.de [195.125.160.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17899 for ; Mon, 19 Oct 1998 08:54:48 -0700 (PDT) (envelope-from doehrm@aubi.de) Received: from igate.aubi.de (root@igate.aubi.de [193.24.63.232]) by rossel.solplus.de (8.8.8/8.8.8) with ESMTP id RAA10227 for ; Mon, 19 Oct 1998 17:55:06 +0200 (MET DST) Received: from exchange.aubi.de ([170.56.121.91]) by igate.aubi.de (8.8.7/8.8.7) with ESMTP id TAA01172 for ; Mon, 19 Oct 1998 19:04:29 +0200 Received: by EXCHANGE.aubi.de with Internet Mail Service (5.5.2232.9) id ; Mon, 19 Oct 1998 17:50:44 +0200 Message-ID: From: =?iso-8859-1?Q?Markus_D=F6hr?= To: freebsd-current@FreeBSD.ORG Subject: make world on i386 Date: Mon, 19 Oct 1998 17:49:33 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA17910 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all! I'm trying to upgrade a 2.2.7 system to 3.0-current. Source is actualised via cvsup. When I try a 'make world' in /usr/src the system starts to build, but stops at libgcc2.c with the error-message tconfig.h:1: mips/x-iris3.h No such file or directory. 'Cause I'm on a i386 plattform, I don't know where to fix this and why the libgcc must include a mips support. I don't wanna build any cross compiler. Any hints? -- Markus Döhr IT Admin AUBI Baubeschläge GmbH Tel.: +49 6503 917 152 Fax : +49 6503 917 119 e-Mail: doehrm@aubi.de ************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 09:45:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22521 for freebsd-current-outgoing; Mon, 19 Oct 1998 09:45:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22515 for ; Mon, 19 Oct 1998 09:45:12 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA25122; Mon, 19 Oct 1998 09:44:32 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 19 Oct 1998 09:44:32 -0700 (PDT) From: Doug White To: "David J. Duchscher" cc: Mike Smith , ulf@Alameda.net, current@FreeBSD.ORG Subject: Re: newfs problems, more information: In-Reply-To: <199810182253.RAA12864@orion.tamu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Oct 1998, David J. Duchscher wrote: > > > newfs: /dev/ccd0c: not a character-special device > > > > Don't put a filesystem on the 'c' partition. Mike likes to preach that (not using partiton c) but I haven't been able to bear it out on -STABLE. 3.0 may have changed the convention; I don't have a disk to test it on. > Granted this document references 2.2-RELEASE but it doesn't follow > this convention/rule. It should probably be updated. > > http://www.freebsd.org/tutorials/diskformat/diskformat.html#s1-4-3 I'll put it in my queue. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 10:20:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25899 for freebsd-current-outgoing; Mon, 19 Oct 1998 10:20:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25887 for ; Mon, 19 Oct 1998 10:20:20 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id KAA19351; Mon, 19 Oct 1998 10:19:51 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <362B74B6.B9B256B4@gorean.org> Date: Mon, 19 Oct 1998 10:19:50 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" CC: current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Dag-Erling C. Smørgrav" wrote: > > Why doesn't ~ expansion work in the following case: > > export GLORB=~ > > as it does in > > GLORB=~; export GLORB I've seen a couple of people complain about 'export foo=bar' causing problems in our implementation of sh. I haven't looked at why it's a problem but if it's any comfort, yes, it seems to be a bug. I've gotten into the habit of using 'foo=bar; export foo' when using sh anyway since it's more portable. Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 10:21:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25980 for freebsd-current-outgoing; Mon, 19 Oct 1998 10:21:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gandalf.relcom.ru (gandalf.relcom.ru [193.125.152.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25964 for ; Mon, 19 Oct 1998 10:21:31 -0700 (PDT) (envelope-from guardian@relis.ru) Received: from lightning (lightning.relcom.ru [193.125.152.92]) by gandalf.relcom.ru (8.8.8/8.8.8) with SMTP id VAA11982 for ; Mon, 19 Oct 1998 21:27:23 +0400 (MSD) Message-ID: <003301bdfb84$5d58d6c0$5c987dc1@lightning.relcom.ru> Reply-To: "Igor Lidin" From: "Igor Lidin" To: Subject: make world breakage :( Date: Mon, 19 Oct 1998 21:17:33 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have this error while make -DNOGAMES buildworld on -current cvsupped today. Can anyone comment this or say what can I do to fix this? My system is -current as of may 1998, with MD5 (if this matters). ===> usr.sbin/config yacc -d /usr1/src/current/src/usr.sbin/config/config.y cp y.tab.c config.c cc -nostdinc -O -pipe -I. -I/usr1/src/current/src/usr.sbin/config -I/usr/o bj/aout/usr1/src/current/src/tmp/usr/include -c config.c cc -nostdinc -O -pipe -I. -I/usr1/src/current/src/usr.sbin/config -I/usr/o bj/aout/usr1/src/current/src/tmp/usr/include -c /usr1/src/current/src/usr.sbin/config/main.c lex -t /usr1/src/current/src/usr.sbin/config/lang.l > lang.c cc -nostdinc -O -pipe -I. -I/usr1/src/current/src/usr.sbin/config -I/usr/o bj/aout/usr1/src/current/src/tmp/usr/include -c lang.c cc -nostdinc -O -pipe -I. -I/usr1/src/current/src/usr.sbin/config -I/usr/o bj/aout/usr1/src/current/src/tmp/usr/include -c /usr1/src/current/src/usr.sbin/config/mkioconf.c /usr1/src/current/src/usr.sbin/config/mkioconf.c:26: lib.h: No such file or directory In file included from /usr/obj/aout/usr1/src/current/src/tmp/usr/include/md5.h:3, from /usr1/src/current/src/usr.sbin/config/mkioconf.c:28: /usr/obj/aout/usr1/src/current/src/tmp/usr/include/sys/md5.h:31: parse error before `u_int32_t' /usr/obj/aout/usr1/src/current/src/tmp/usr/include/sys/md5.h:31: warning: no semicolon at end of struct or union /usr/obj/aout/usr1/src/current/src/tmp/usr/include/sys/md5.h:32: warning: data definition has no type or storage class /usr/obj/aout/usr1/src/current/src/tmp/usr/include/sys/md5.h:34: parse error before `}' /usr/obj/aout/usr1/src/current/src/tmp/usr/include/sys/md5.h:34: warning: data definition has no type or storage class /usr/obj/aout/usr1/src/current/src/tmp/usr/include/sys/md5.h:39: parse error before `*' /usr/obj/aout/usr1/src/current/src/tmp/usr/include/sys/md5.h:40: parse error before `*' /usr/obj/aout/usr1/src/current/src/tmp/usr/include/sys/md5.h:41: parse error before `*' /usr/obj/aout/usr1/src/current/src/tmp/usr/include/sys/md5.h:42: parse error before `MD5_CTX' /usr/obj/aout/usr1/src/current/src/tmp/usr/include/sys/md5.h:43: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c:32: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `add_plist': /usr1/src/current/src/usr.sbin/config/mkioconf.c:34: `PackingList' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:34: (Each undeclared identifier is reported only once /usr1/src/current/src/usr.sbin/config/mkioconf.c:34: for each function it appears in.) /usr1/src/current/src/usr.sbin/config/mkioconf.c:34: parse error before `tmp' /usr1/src/current/src/usr.sbin/config/mkioconf.c:36: `tmp' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:37: `arg' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:38: `type' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:40: `p' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:50: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `add_plist_top': /usr1/src/current/src/usr.sbin/config/mkioconf.c:52: `PackingList' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:52: parse error before `tmp' /usr1/src/current/src/usr.sbin/config/mkioconf.c:54: `tmp' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:55: `arg' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:56: `type' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:58: `p' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:69: parse error before `last_plist' /usr1/src/current/src/usr.sbin/config/mkioconf.c:69: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `last_plist': /usr1/src/current/src/usr.sbin/config/mkioconf.c:71: `p' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:76: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `mark_plist': /usr1/src/current/src/usr.sbin/config/mkioconf.c:78: `PackingList' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:78: parse error before `p' /usr1/src/current/src/usr.sbin/config/mkioconf.c:80: `p' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:81: `TRUE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:88: parse error before `find_plist' /usr1/src/current/src/usr.sbin/config/mkioconf.c:88: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `find_plist': /usr1/src/current/src/usr.sbin/config/mkioconf.c:90: `PackingList' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:90: parse error before `p' /usr1/src/current/src/usr.sbin/config/mkioconf.c:92: `p' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:93: `type' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:97: `NULL' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:102: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `find_plist_option': /usr1/src/current/src/usr.sbin/config/mkioconf.c:104: `PackingList' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:104: parse error before `p' /usr1/src/current/src/usr.sbin/config/mkioconf.c:106: `p' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:107: `PLIST_OPTION' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:107: `name' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:111: `NULL' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:119: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `delete_plist': /usr1/src/current/src/usr.sbin/config/mkioconf.c:121: `PackingList' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:121: parse error before `p' /usr1/src/current/src/usr.sbin/config/mkioconf.c:123: `p' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:124: parse error before `pnext' /usr1/src/current/src/usr.sbin/config/mkioconf.c:126: `type' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:126: `name' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:129: `pnext' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:131: `pkg' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:137: `all' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:148: parse error before `new_plist_entry' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `new_plist_entry': /usr1/src/current/src/usr.sbin/config/mkioconf.c:150: `PackingList' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:150: parse error before `ret' /usr1/src/current/src/usr.sbin/config/mkioconf.c:152: `ret' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:152: parse error before `malloc' /usr1/src/current/src/usr.sbin/config/mkioconf.c:153: sizeof applied to an incomplete type /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:159: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `free_plist': /usr1/src/current/src/usr.sbin/config/mkioconf.c:161: `PackingList' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:161: parse error before `p' /usr1/src/current/src/usr.sbin/config/mkioconf.c:163: `p' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:164: parse error before `p1' /usr1/src/current/src/usr.sbin/config/mkioconf.c:168: `p1' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:170: `pkg' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:170: `NULL' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `plist_cmd': /usr1/src/current/src/usr.sbin/config/mkioconf.c:180: `FILENAME_MAX' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:180: size of array `cmd' has non-integer type /usr1/src/current/src/usr.sbin/config/mkioconf.c:199: `PLIST_CWD' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:201: `PLIST_SRC' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:205: `PLIST_CMD' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:207: `PLIST_UNEXEC' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:209: `PLIST_CHMOD' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:211: `PLIST_CHOWN' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:213: `PLIST_CHGRP' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:215: `PLIST_COMMENT' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:217: `PLIST_IGNORE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:219: `PLIST_IGNORE_INST' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:221: `PLIST_NAME' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:223: `PLIST_DISPLAY' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:225: `PLIST_PKGDEP' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:227: `PLIST_MTREE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:229: `PLIST_DIR_RM' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:231: `PLIST_OPTION' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:233: `FAIL' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:238: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `read_plist': /usr1/src/current/src/usr.sbin/config/mkioconf.c:240: `FILENAME_MAX' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:243: `fp' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:251: `CMD_CHAR' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:253: `FAIL' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:258: `NULL' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:261: `PLIST_FILE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:262: `pkg' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:268: parse error before `*' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `write_plist': /usr1/src/current/src/usr.sbin/config/mkioconf.c:270: `PackingList' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:270: parse error before `plist' /usr1/src/current/src/usr.sbin/config/mkioconf.c:272: `plist' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:274: `PLIST_FILE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:275: `fp' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:278: `PLIST_CWD' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:279: `CMD_CHAR' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:282: `PLIST_SRC' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:286: `PLIST_CMD' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:290: `PLIST_UNEXEC' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:294: `PLIST_CHMOD' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:298: `PLIST_CHOWN' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:302: `PLIST_CHGRP' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:306: `PLIST_COMMENT' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:310: `PLIST_IGNORE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:311: `PLIST_IGNORE_INST' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:315: `PLIST_NAME' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:319: `PLIST_DISPLAY' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:323: `PLIST_PKGDEP' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:327: `PLIST_MTREE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:331: `PLIST_DIR_RM' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:335: `PLIST_OPTION' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:355: parse error before `ign_err' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `delete_package': /usr1/src/current/src/usr.sbin/config/mkioconf.c:357: `PackingList' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:357: parse error before `p' /usr1/src/current/src/usr.sbin/config/mkioconf.c:359: `Boolean' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:359: parse error before `fail' /usr1/src/current/src/usr.sbin/config/mkioconf.c:361: `FILENAME_MAX' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:361: `NULL' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:363: `preserve' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:363: `pkg' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:363: `TRUE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:363: `FALSE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:364: `p' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:366: `PLIST_NAME' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:370: `PLIST_IGNORE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:374: `PLIST_CWD' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:376: `Verbose' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:380: `PLIST_UNEXEC' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:384: `Fake' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:386: `fail' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:386: `FAIL' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:390: `PLIST_FILE' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:398: `PLIST_COMMENT' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:406: `Force' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:417: `ign_err' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:417: `nukedirs' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:434: `PLIST_DIR_RM' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c: At top level: /usr1/src/current/src/usr.sbin/config/mkioconf.c:465: parse error before `Boolean' /usr1/src/current/src/usr.sbin/config/mkioconf.c: In function `delete_hierarchy': /usr1/src/current/src/usr.sbin/config/mkioconf.c:469: `dir' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:471: `ign_err' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:476: `nukedirs' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:477: `REMOVE_CMD' undeclared (first use this function) /usr1/src/current/src/usr.sbin/config/mkioconf.c:492: warning: assignment makes pointer from integer without a cast /usr1/src/current/src/usr.sbin/config/mkioconf.c:492: `NULL' undeclared (first use this function) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. With best regards, Igor Lidin, guardian@relis.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 10:48:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28433 for freebsd-current-outgoing; Mon, 19 Oct 1998 10:48:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28412 for ; Mon, 19 Oct 1998 10:48:10 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id KAA28348; Mon, 19 Oct 1998 10:47:40 -0700 (PDT) Message-ID: <19981019104740.A28337@nuxi.com> Date: Mon, 19 Oct 1998 10:47:40 -0700 From: "David O'Brien" To: Doug White Cc: current@FreeBSD.ORG Subject: Re: newfs problems, more information: Reply-To: obrien@NUXI.com References: <199810182253.RAA12864@orion.tamu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Doug White on Mon, Oct 19, 1998 at 09:44:32AM -0700 X-Operating-System: FreeBSD 2.2.7-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Granted this document references 2.2-RELEASE but it doesn't follow > > this convention/rule. It should probably be updated. > > > > http://www.freebsd.org/tutorials/diskformat/diskformat.html#s1-4-3 > > I'll put it in my queue. Might also be a good idea to sync the "Disks" section of the Handbook with it too. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 11:09:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01697 for freebsd-current-outgoing; Mon, 19 Oct 1998 11:09:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01691 for ; Mon, 19 Oct 1998 11:09:50 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id OAA00680; Mon, 19 Oct 1998 14:08:54 -0400 (EDT) Date: Mon, 19 Oct 1998 14:08:54 -0400 (EDT) From: Chuck Robey To: "David O'Brien" cc: freebsd-current@FreeBSD.ORG Subject: Re: GNU Awk replacement In-Reply-To: <19981018223914.B25719@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Oct 1998, David O'Brien wrote: > > > What do people think about replacing GNU awk in the base system with the > > > One True Awk(tm) by bwk? > > > > How far back you harking? Oawk, no. nawk, yes. You loose too much > > Good question. Our kawk port (kawk-98.02.11). > from http://cm.bell-labs.com/who/bwk/awk.tar.gz > > To quote: > This is the version of awk described in "The AWK Programming Language", > by Al Aho, Brian Kernighan, and Peter Weinberger > (Addison-Wesley, 1988, ISBN 0-201-07981-X). > > It is under a Berkeley/MIT/CMU like copyright. I took a look at this. I _think_ it's what I would have named "nawk", the new awk. I haven't checked it, and I don't immediately remember a short test to prove it .... if I remember right, it was better usage of associational arrays, and also better looping. I remember a while back, learning the hard way that you really don't want to use the old, original awk. Way too primitive for more than 10 liners. I think I'd be happy enough with kawk. Lucent has the copyright, but it's totally open, they give it away. What's more, they've obviously (see the FIXES file) kept putting real fixes into it, right up to this year. > > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 11:14:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02142 for freebsd-current-outgoing; Mon, 19 Oct 1998 11:14:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from terminator.informatik.ba-stuttgart.de (terminator.informatik.ba-stuttgart.de [141.31.111.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02131 for ; Mon, 19 Oct 1998 11:14:43 -0700 (PDT) (envelope-from henry@MX.BA-Stuttgart.De) Received: from marylin.goethestr12-net.marbach-neckar (marylin.informatik.ba-stuttgart.de [141.31.112.1]) by terminator.informatik.ba-stuttgart.de (8.8.8/8.8.8) with ESMTP id UAA23111 for ; Mon, 19 Oct 1998 20:10:27 +0200 (CEST) (envelope-from henry@MX.BA-Stuttgart.De) Received: (from henry@localhost) by marylin.goethestr12-net.marbach-neckar (8.9.1/8.8.8) id UAA00844 for freebsd-current@freebsd.org; Mon, 19 Oct 1998 20:12:55 +0200 (CEST) (envelope-from henry) From: Henry Vogt Message-Id: <199810191812.UAA00844@marylin.goethestr12-net.marbach-neckar> Subject: fxp0 - unsupported PHY=63 ? To: freebsd-current@FreeBSD.ORG Date: Mon, 19 Oct 1998 20:12:55 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Is this a new version of the this card ? It should be an ordianry 'Pro 10/100B'. It is probed as: fxp0: rev 0x05 int a irq 18 on pci0.10.0 fxp0: Ethernet address ff:ff:ff:ff:ff:ff, 10Mbps ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The message is /kernel: fxp0: warning: unsupported PHY, type = 63, addr = 255 The chip on the card is labeled '82558B', and is not mentioned in /sys/pci/if_fxp.c : static const struct fxp_supported_media fxp_media[] = { ... { FXP_PHY_82555B, fxp_media_standard, sizeof(fxp_media_standard) / sizeof(fxp_media_standard[0]), FXP_MEDIA_STANDARD_DEFMEDIA }, ... } Henry -- // // Do you suffer from long term memory loss ? I don't remember:-( // // Henry Vogt (henry@BA-Stuttgart.De) // Goethestr. 12, 71672 Marbach (Neckar), Tel. 07144/841653 // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 11:17:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02478 for freebsd-current-outgoing; Mon, 19 Oct 1998 11:17:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02471 for ; Mon, 19 Oct 1998 11:17:10 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id TAA08196; Mon, 19 Oct 1998 19:15:08 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id TAA01268; Mon, 19 Oct 1998 19:56:40 +0200 (CEST) (envelope-from andreas) Message-ID: <19981019195640.A1022@klemm.gtn.com> Date: Mon, 19 Oct 1998 19:56:40 +0200 From: Andreas Klemm To: =?iso-8859-1?Q?Markus_D=F6hr?= , freebsd-current@FreeBSD.ORG Subject: Re: make world on i386 References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: =?iso-8859-1?Q?=3CAB06BBFD8AFBD111B07600805FCB1192079E85=40EXCHANGE=2Eau?= =?iso-8859-1?Q?bi=2Ede=3E=3B_from_Markus_D=F6hr_on_Mon=2C_Oct_19=2C_1998?= =?iso-8859-1?Q?_at_05:49:33PM_+0200?= X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 2.2.7-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 05:49:33PM +0200, Markus Döhr wrote: > Hi all! > > I'm trying to upgrade a 2.2.7 system to 3.0-current. Source > is actualised via cvsup. > > When I try a 'make world' in /usr/src the system starts to > build, but stops at libgcc2.c with the error-message > > tconfig.h:1: mips/x-iris3.h No such file or directory. > 'Cause I'm on a i386 plattform, I don't know where to > fix this and why the libgcc must include a mips support. > I don't wanna build any cross compiler. > > Any hints? RTFM ;-) Please read the notes in /usr/src/Makefile -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 11:34:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04403 for freebsd-current-outgoing; Mon, 19 Oct 1998 11:34:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04398 for ; Mon, 19 Oct 1998 11:34:33 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA23429; Mon, 19 Oct 1998 11:29:32 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdQ23427; Mon Oct 19 18:29:26 1998 Date: Mon, 19 Oct 1998 11:29:21 -0700 (PDT) From: Julian Elischer To: Henry Vogt cc: freebsd-current@FreeBSD.ORG Subject: Re: fxp0 - unsupported PHY=63 ? In-Reply-To: <199810191812.UAA00844@marylin.goethestr12-net.marbach-neckar> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the eeprom has lost its program (or was never programmed) On Mon, 19 Oct 1998, Henry Vogt wrote: > Hello, > > Is this a new version of the this card ? > It should be an ordianry 'Pro 10/100B'. > It is probed as: > > fxp0: rev 0x05 int a irq 18 on pci0.10.0 > fxp0: Ethernet address ff:ff:ff:ff:ff:ff, 10Mbps > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > The message is > > /kernel: fxp0: warning: unsupported PHY, type = 63, addr = 255 > > The chip on the card is labeled '82558B', and is not mentioned in > /sys/pci/if_fxp.c : > > static const struct fxp_supported_media fxp_media[] = { > ... > { FXP_PHY_82555B, fxp_media_standard, > sizeof(fxp_media_standard) / sizeof(fxp_media_standard[0]), > FXP_MEDIA_STANDARD_DEFMEDIA }, > ... > } > > Henry > > -- > // > // Do you suffer from long term memory loss ? I don't remember:-( > // > // Henry Vogt (henry@BA-Stuttgart.De) > // Goethestr. 12, 71672 Marbach (Neckar), Tel. 07144/841653 > // > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 11:36:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04609 for freebsd-current-outgoing; Mon, 19 Oct 1998 11:36:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04604 for ; Mon, 19 Oct 1998 11:36:24 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id OAA20137; Mon, 19 Oct 1998 14:35:40 -0400 (EDT) Date: Mon, 19 Oct 1998 14:35:40 -0400 (EDT) Message-Id: <199810191835.OAA20137@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We found another libc_r problem which is spinning the CPU at 100%. This makes it impossible for our application to work at all. FreeBSD 3.0 kernel from August. The LATEST libc_r. Tested this on another FreeBSD with a much more recent kernel. Same result. The CPU spins and the threads don't get the condition. Program works fine on other operating systems. After the 3 second start up, it prints nice stream of "Signalling" and "Got Condition!". On FreeBSD 3.0, it prints "Signalling" twice and then spins the CPU. Help is always appreciated. -Rob --- /* Illustration of FreeBSD pthread_cond_wait() bug This program sets up a conditional wait and fires off a dozen threads that simply wait for the condition. Once the threads are started, the main thread loops signalling the condition once a second. Normally, this should result in "Signalling" and "Got Condition" being printed once a second. However, because of some bugs in FreeBSD, the pthread_cond_wait() spins the CPU and no progress is made. g++ -o condWaitBug -D_REENTRANT -D_THREAD_SAFE -g -Wall condWaitBug.C -pthread */ #include #include #include #include #include pthread_mutex_t lock; pthread_cond_t condition; static void *condThread(void *) { // Wait until we are signalled, then print. while (true) { assert(!::pthread_cond_wait(&condition, &lock)); ::printf("Got Condition!\n"); } } int main(int, char **) { // Initialize Lock pthread_mutexattr_t lock_attr; assert(!::pthread_mutexattr_init(&lock_attr)); assert(!::pthread_mutex_init(&lock, &lock_attr)); assert(!::pthread_mutexattr_destroy(&lock_attr)); // Initialize Condition pthread_condattr_t cond_attr; assert(!::pthread_condattr_init(&cond_attr)); assert(!::pthread_cond_init(&condition, &cond_attr)); assert(!::pthread_condattr_destroy(&cond_attr)); // Lock the lock assert(!::pthread_mutex_lock(&lock)); // Spawn off a dozen threads to get signalled for (int j = 0; j < 12; ++j) { pthread_t tid; pthread_attr_t attr; assert(!::pthread_attr_init(&attr)); assert(!::pthread_create(&tid, &attr, condThread, 0)); assert(!::pthread_attr_destroy(&attr)); } // Sleep for 3 seconds to make sure the threads started up. timeval timeout; timeout.tv_sec = 3; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); for (int k = 0; k < 60; ++k) { ::printf("Signalling\n"); ::pthread_cond_signal(&condition); // Sleep for a second timeout.tv_sec = 1; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); } return EXIT_SUCCESS; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 11:39:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04929 for freebsd-current-outgoing; Mon, 19 Oct 1998 11:39:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04923 for ; Mon, 19 Oct 1998 11:39:15 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id LAA22615; Mon, 19 Oct 1998 11:38:49 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd022433; Mon Oct 19 11:38:34 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA00992; Mon, 19 Oct 1998 11:38:23 -0700 (MST) From: Terry Lambert Message-Id: <199810191838.LAA00992@usr02.primenet.com> Subject: Re: mount flags To: chuckr@mat.net (Chuck Robey) Date: Mon, 19 Oct 1998 18:38:23 +0000 (GMT) Cc: peter@netplex.com.au, nik@nothing-going-on.demon.co.uk, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Oct 18, 98 11:30:58 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > vfc_typenum is the same as the statfs.f_type field. That's how you match > > them. > > > > You can, however, do a getvfsbyname("nfs") and get the magic number from > > the returned vfc_typenum and use that instead of the old MOUNT_NFS > > constant if that's more convenient. Beware that this isn't guaranteed to > > remain constant in the face of vfs loads and unloads via the lkm or kld > > mechanism. > > If I do the getvfsbyname method, I do no pattern-matching at all > (FreeBSD does that for me). When I do the lookup, the data is good at > that point, isn't it, even in the face of the vfs or KLD loads/unloads, > right? And, as long as I do no dismounting (the fs is up) that number > can't change on me. The *set* of available numbers and their mappings > can change, but not the one I'm sitting on, right? > > If that's true, for my app, that will do. The number can change if you load and unload modules, however. To be as robust as possible, you should call getvfsbyname() before every comparison. You *could* wrap this the same way errno is currently wrapped, giving you a tiny glue function. > I'd stop doing that, if I trusted that the statfs f_fstypename was > reliably being set. It's too new, and I haven't found where it's > getting set, no matter how much I search for it. It's getting set in the file /usr/src/lib/libc/gen/getvfsent.c from SYSCTL data. Note: the current libc code tries to cache a list; this means that using getvfsbyname is unreliable in the face of list changes as a result of module manipulation. Someone should fix this. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 11:42:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05425 for freebsd-current-outgoing; Mon, 19 Oct 1998 11:42:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05407 for ; Mon, 19 Oct 1998 11:42:39 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id LAA02377; Mon, 19 Oct 1998 11:42:13 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd002316; Mon Oct 19 11:42:03 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA01225; Mon, 19 Oct 1998 11:42:02 -0700 (MST) From: Terry Lambert Message-Id: <199810191842.LAA01225@usr02.primenet.com> Subject: Re: mount flags To: mike@smith.net.au (Mike Smith) Date: Mon, 19 Oct 1998 18:42:02 +0000 (GMT) Cc: chuckr@mat.net, peter@netplex.com.au, nik@nothing-going-on.demon.co.uk, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG In-Reply-To: <199810190558.WAA16555@dingo.cdrom.com> from "Mike Smith" at Oct 18, 98 10:58:13 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If I do the getvfsbyname method, I do no pattern-matching at all > > (FreeBSD does that for me). When I do the lookup, the data is good at > > that point, isn't it, even in the face of the vfs or KLD loads/unloads, > > right? And, as long as I do no dismounting (the fs is up) that number > > can't change on me. The *set* of available numbers and their mappings > > can change, but not the one I'm sitting on, right? > > That's correct; a VFS can't be unloaded while it's referenced. Careful. For one instance of a program, the return from the sysctl's is cached by the library function (getvfsbyname(3)). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 11:47:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05831 for freebsd-current-outgoing; Mon, 19 Oct 1998 11:47:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05826 for ; Mon, 19 Oct 1998 11:47:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00514; Mon, 19 Oct 1998 11:49:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810191849.LAA00514@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug White cc: "David J. Duchscher" , Mike Smith , ulf@Alameda.net, current@FreeBSD.ORG Subject: Re: newfs problems, more information: In-reply-to: Your message of "Mon, 19 Oct 1998 09:44:32 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Oct 1998 11:49:32 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 18 Oct 1998, David J. Duchscher wrote: > > > > > newfs: /dev/ccd0c: not a character-special device > > > > > > Don't put a filesystem on the 'c' partition. > > Mike likes to preach that (not using partiton c) but I haven't been able > to bear it out on -STABLE. 3.0 may have changed the convention; I don't > have a disk to test it on. Actually, I do it all the time. Bruce chastises people for doing it, so I'm just repeating the Best Availalble Practice. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 12:00:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06866 for freebsd-current-outgoing; Mon, 19 Oct 1998 12:00:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06859 for ; Mon, 19 Oct 1998 12:00:40 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id MAA28719 for current@FreeBSD.ORG; Mon, 19 Oct 1998 12:00:16 -0700 (PDT) Message-ID: <19981019120015.A28684@nuxi.com> Date: Mon, 19 Oct 1998 12:00:15 -0700 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: newfs problems, more information: Reply-To: obrien@NUXI.com References: <199810191849.LAA00514@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810191849.LAA00514@dingo.cdrom.com>; from Mike Smith on Mon, Oct 19, 1998 at 11:49:32AM -0700 X-Operating-System: FreeBSD 2.2.7-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Don't put a filesystem on the 'c' partition. > > > > Mike likes to preach that (not using partiton c) but I haven't been able > > Actually, I do it all the time. Bruce chastises people for doing it, > so I'm just repeating the Best Availalble Practice. Julian Elischer also. He's mentioned in the lists that DEVFS will make special use of it. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 12:13:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08416 for freebsd-current-outgoing; Mon, 19 Oct 1998 12:13:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mayn.de (airbus.mayn.de [194.95.209.24]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA08386 for ; Mon, 19 Oct 1998 12:13:21 -0700 (PDT) (envelope-from treif@mayn.de) Received: (qmail 10816 invoked from network); 19 Oct 1998 19:12:59 -0000 Received: from netppp-040.wuerzburg.dialin.mayn.de (HELO mayn.de) (195.37.216.168) by airbus.mayn.de with SMTP; 19 Oct 1998 19:12:59 -0000 Message-ID: <362B705B.E7F8ABBD@mayn.de> Date: Mon, 19 Oct 1998 19:01:15 +0200 From: Tobias Reifenberger Organization: United States of Cosyanna X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: reboot won't work Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi After updating my preCAM -current it shows a strange reboot behavior. The system's locking right after sync - all file systems are clean, but I'm forced to use the reset button. Anybody else seeing the same problem? Oct 19 14:23:56 freebsd /kernel.cam: Copyright (c) 1992-1998 FreeBSD Inc. Oct 19 14:23:56 freebsd /kernel.cam: Copyright (c) 1982, 1986, 1989, 1991, 1993 Oct 19 14:23:56 freebsd /kernel.cam: The Regents of the University of California. All rights reserved. Oct 19 14:23:56 freebsd /kernel.cam: FreeBSD 3.0-CURRENT #12: Sun Oct 18 17:56:34 CEST 1998 Oct 19 14:23:57 freebsd /kernel.cam: root@freebsd.mayn.de:/usr/src/sys/compile/newi Oct 19 14:23:57 freebsd /kernel.cam: Timecounter "i8254" frequency 1193182 Hz cost 2540 ns Oct 19 14:23:57 freebsd /kernel.cam: Timecounter "TSC" frequency 132632234 Hz cost 144 ns Oct 19 14:23:57 freebsd /kernel.cam: CPU: Pentium/P54C (132.63-MHz 586-class CPU) Oct 19 14:23:57 freebsd /kernel.cam: Origin = "GenuineIntel" Id = 0x526 Stepping=6 Oct 19 14:23:57 freebsd /kernel.cam: Features=0x1bf Oct 19 14:23:57 freebsd /kernel.cam: real memory = 41943040 (40960K bytes) Oct 19 14:23:57 freebsd /kernel.cam: avail memory = 38412288 (37512K bytes) Oct 19 14:23:57 freebsd /kernel.cam: Probing for devices on PCI bus 0: Oct 19 14:23:57 freebsd /kernel.cam: chip0: rev 0x02 on pci0.0.0 Oct 19 14:23:57 freebsd /kernel.cam: chip1: rev 0x02 on pci0.7.0 Oct 19 14:23:57 freebsd /kernel.cam: fxp0: rev 0x05 int a irq 14 on pci0.9.0 Oct 19 14:23:57 freebsd /kernel.cam: fxp0: Ethernet address 00:a0:c9:ca:8c:98 Oct 19 14:23:57 freebsd /kernel.cam: ncr0: rev 0x11 int a irq 11 on pci0.10.0 Oct 19 14:23:57 freebsd /kernel.cam: ncr1: rev 0x03 int a irq 10 on pci0.11.0 Oct 19 14:23:57 freebsd /kernel.cam: vga0: rev 0x40 int a irq 0 on pci0.12.0 Oct 19 14:23:57 freebsd /kernel.cam: Probing for devices on the ISA bus: Oct 19 14:23:57 freebsd /kernel.cam: sc0 at 0x60-0x6f irq 1 on motherboard Oct 19 14:23:57 freebsd /kernel.cam: sc0: VGA color <16 virtual consoles, flags=0x0> Oct 19 14:23:57 freebsd /kernel.cam: ed0 at 0x300-0x31f irq 15 on isa Oct 19 14:23:57 freebsd /kernel.cam: ed0: address 00:00:b4:30:af:af, type NE2000 (16 bit) Oct 19 14:23:57 freebsd /kernel.cam: sio0 at 0x3f8-0x3ff irq 4 on isa Oct 19 14:23:57 freebsd /kernel.cam: sio0: type 16550A Oct 19 14:23:57 freebsd /kernel.cam: sio1 at 0x2f8-0x2ff irq 3 on isa Oct 19 14:23:57 freebsd /kernel.cam: sio1: type 16550A Oct 19 14:23:57 freebsd /kernel.cam: lpt0 at 0x378-0x37f irq 7 on isa Oct 19 14:23:57 freebsd /kernel.cam: lpt0: Interrupt-driven port Oct 19 14:23:57 freebsd /kernel.cam: lp0: TCP/IP capable interface Oct 19 14:23:57 freebsd /kernel.cam: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 flags 0x1 on isa Oct 19 14:23:57 freebsd /kernel.cam: fdc0: FIFO enabled, 8 bytes threshold Oct 19 14:23:57 freebsd /kernel.cam: fd0: config-pretended 1.44MB 3.5in Oct 19 14:23:57 freebsd /kernel.cam: npx0 on motherboard Oct 19 14:23:57 freebsd /kernel.cam: npx0: INT 16 interface Oct 19 14:23:57 freebsd /kernel.cam: joy0 at 0x201 on isa Oct 19 14:23:57 freebsd /kernel.cam: joy0: joystick Oct 19 14:23:57 freebsd /kernel.cam: gus0 at 0x220 irq 5 drq 6 flags 0x107 on isa Oct 19 14:23:57 freebsd /kernel.cam: snd0: Oct 19 14:23:57 freebsd /kernel.cam: Intel Pentium F00F detected, installing workaround Oct 19 14:23:57 freebsd /kernel.cam: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled Oct 19 14:23:57 freebsd /kernel.cam: ccd0-3: Concatenated disk drivers Oct 19 14:23:57 freebsd /kernel.cam: Waiting 3 seconds for SCSI devices to settle Oct 19 14:23:57 freebsd /kernel.cam: (probe1:ncr0:0:1:0): phase Oct 19 14:23:57 freebsd /kernel.cam: change 6-7 6@005629b4 resid=4. Oct 19 14:23:57 freebsd /kernel.cam: (probe1:ncr0:0:1:0): MSG_MESSAGE_REJECT received (1:8). Oct 19 14:23:57 freebsd /kernel.cam: changing root device to da0s1a Oct 19 14:23:57 freebsd /kernel.cam: da0 at ncr1 bus 0 target 0 lun 0 Oct 19 14:23:57 freebsd /kernel.cam: da0: Fixed Direct Access SCSI2 device Oct 19 14:23:57 freebsd /kernel.cam: da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled Oct 19 14:23:57 freebsd /kernel.cam: da0: 1002MB (2053880 512 byte sectors: 64H 32S/T 1002C) Oct 19 14:23:57 freebsd /kernel.cam: da1 at ncr1 bus 0 target 1 lun 0 Oct 19 14:23:57 freebsd /kernel.cam: da1: Fixed Direct Access SCSI2 device Oct 19 14:23:57 freebsd /kernel.cam: da1: 20.0MB/s transfers (10.0MHz, offset 15, 16bit), Tagged Queueing Enabled Oct 19 14:23:57 freebsd /kernel.cam: da1: 2050MB (4199760 512 byte sectors: 255H 63S/T 261C) Oct 19 14:23:57 freebsd /kernel.cam: da2 at ncr1 bus 0 target 2 lun 0 Oct 19 14:23:57 freebsd /kernel.cam: da2: Fixed Direct Access SCSI2 device Oct 19 14:23:57 freebsd /kernel.cam: da2: 20.0MB/s transfers (10.0MHz, offset 15, 16bit), Tagged Queueing Enabled Oct 19 14:23:57 freebsd /kernel.cam: da2: 2050MB (4199760 512 byte sectors: 255H 63S/T 261C) Oct 19 14:23:57 freebsd /kernel.cam: cd0 at ncr0 bus 0 target 1 lun 0 Oct 19 14:23:57 freebsd /kernel.cam: cd0: Removable CD-ROM SCSI2 device Oct 19 14:23:58 freebsd /kernel.cam: cd0: 3.300MB/s transfers Oct 19 14:23:58 freebsd /kernel.cam: cd0: cd present [276112 x 2048 byte records] Oct 19 14:23:58 freebsd /kernel.cam: da4 at ncr1 bus 0 target 4 lun 0 Oct 19 14:23:58 freebsd /kernel.cam: da4: Fixed Direct Access SCSI2 device Oct 19 14:23:58 freebsd /kernel.cam: da4: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled Oct 19 14:23:58 freebsd /kernel.cam: da4: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) Oct 19 14:23:58 freebsd /kernel.cam: da3 at ncr1 bus 0 target 3 lun 0 Oct 19 14:23:58 freebsd /kernel.cam: da3: Fixed Direct Access SCSI2 device Oct 19 14:23:58 freebsd /kernel.cam: da3: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled Oct 19 14:23:58 freebsd /kernel.cam: da3: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) Oct 19 14:23:58 freebsd /kernel.cam: ffs_mountfs: superblock updated Oct 19 14:24:00 freebsd /kernel.cam: (da0:ncr1:0:0:0): tagged openings now 17 c ya -- Tobias Reifenberger, DG1NGT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 12:32:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10502 for freebsd-current-outgoing; Mon, 19 Oct 1998 12:32:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10341 for ; Mon, 19 Oct 1998 12:30:40 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id PAA10944; Mon, 19 Oct 1998 15:26:27 -0400 (EDT) Date: Mon, 19 Oct 1998 15:26:27 -0400 (EDT) From: Daniel Eischen Message-Id: <199810191926.PAA10944@pcnet1.pcnet.com> To: current@FreeBSD.ORG, info@highwind.com Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We found another libc_r problem which is spinning the CPU at 100%. > This makes it impossible for our application to work at all. > > FreeBSD 3.0 kernel from August. The LATEST libc_r. Tested this on > another FreeBSD with a much more recent kernel. Same result. The CPU > spins and the threads don't get the condition. I believe your test program is in error. Your threads are not ever going to awake from the pthread_cond_wait() statement because the mutex cannot be acquired. Your main thread locks the mutex and never unlocks it. If this application works on other operating systems, it seems that they are at fault. From the Solaris pthread_cond_wait manpage: A condition variable enables threads to atomically block and test the condition under the protection of a mutual exclu- sion lock (mutex) until the condition is satisfied. If the condition is false, a thread blocks on a condition variable and atomically releases the mutex that is waiting for the condition to change. If another thread changes the condi- tion, it may wake up waiting threads by signaling the asso- ciated condition variable. The waiting threads, upon awak- ening, reacquire the mutex and re-evaluate the condition. Here's a patch to make your test program do what I think it is suppose to: *** condWaitBug.C.orig Mon Oct 19 15:00:28 1998 --- condWaitBug.C Mon Oct 19 15:02:37 1998 *************** *** 26,32 **** --- 26,34 ---- { // Wait until we are signalled, then print. while (true) { + assert(!::pthread_mutex_lock(&lock)); assert(!::pthread_cond_wait(&condition, &lock)); + assert(!::pthread_mutex_unlock(&lock)); ::printf("Got Condition!\n"); } } *************** *** 57,62 **** --- 59,67 ---- assert(!::pthread_attr_destroy(&attr)); } + // Unlock the lock + assert(!::pthread_mutex_unlock(&lock)); + // Sleep for 3 seconds to make sure the threads started up. timeval timeout; timeout.tv_sec = 3; > On FreeBSD 3.0, it prints "Signalling" twice and then spins the CPU. This didn't happen to me on a recent -stable. There were some recent fixes to 3.0 libc_r for incremental priority updates that were not being properly computed. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 12:41:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11475 for freebsd-current-outgoing; Mon, 19 Oct 1998 12:41:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11467 for ; Mon, 19 Oct 1998 12:41:44 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id PAA17849 for ; Mon, 19 Oct 1998 15:43:18 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Mon, 19 Oct 1998 15:43:17 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: current@FreeBSD.ORG Subject: fix for "broken threads" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I lost the original message about broken threads in freebsd but I have a fix. I believe the problem lies in incorrect assumptions about thread locking, a programming error basically, you are double signalling on a conditional variable which I think is the wrong thing to do. However I've just started playing with threads so I'm unsure if this is a "true" fix. You need 2 conditional variables, that way you don't "double signal" on the conditional. I haven't read the spec and perhaps the flip-flop shouldn't be nessesary but it does make sense to implement. take a look at this and tell me if it works for you: /* Fix for the alleged FreeBSD pthread_cond_wait() bug the fix is to simply make sure you don't double signal on the conditional by having a flip flop machanism via conditionals and a single mutex. g++ -o condWaitBug -D_REENTRANT -D_THREAD_SAFE -g -Wall condWaitBug.C -pthread */ #include #include #include #include #include pthread_mutex_t lock=PTHREAD_MUTEX_INITIALIZER; pthread_cond_t condition=PTHREAD_COND_INITIALIZER; pthread_cond_t condition2=PTHREAD_COND_INITIALIZER; static void *condThread(void *) { // Wait until we are signalled, then print. while (true) { assert(!::pthread_cond_wait(&condition, &lock)); assert(!::pthread_cond_signal(&condition2)); ::printf("Got Condition!\n"); } } int main(int, char **) { // Initialize Lock pthread_mutexattr_t lock_attr; assert(!::pthread_mutexattr_init(&lock_attr)); assert(!::pthread_mutex_init(&lock, &lock_attr)); assert(!::pthread_mutexattr_destroy(&lock_attr)); // Initialize Condition pthread_condattr_t cond_attr; assert(!::pthread_condattr_init(&cond_attr)); assert(!::pthread_cond_init(&condition, &cond_attr)); assert(!::pthread_condattr_destroy(&cond_attr)); // Lock the lock assert(!::pthread_mutex_lock(&lock)); // Spawn off a dozen threads to get signalled for (int j = 0; j < 12; ++j) { pthread_t tid; pthread_attr_t attr; assert(!::pthread_attr_init(&attr)); assert(!::pthread_create(&tid, NULL, condThread, 0)); assert(!::pthread_attr_destroy(&attr)); } // Sleep for 3 seconds to make sure the threads started up. timeval timeout; timeout.tv_sec = 3; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); for (int k = 0; k < 60; ++k) { ::printf("Signalling\n"); ::pthread_cond_signal(&condition); assert(!::pthread_cond_wait(&condition2, &lock)); // Sleep for a second timeout.tv_sec = 1; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); ::pthread_yield(); ::pthread_yield(); } return EXIT_SUCCESS; } Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 12:54:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12757 for freebsd-current-outgoing; Mon, 19 Oct 1998 12:54:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12752 for ; Mon, 19 Oct 1998 12:53:59 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA26520 for ; Mon, 19 Oct 1998 12:53:03 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdc26511; Mon Oct 19 19:52:54 1998 Date: Mon, 19 Oct 1998 12:52:49 -0700 (PDT) From: Julian Elischer To: current@FreeBSD.ORG Subject: vote:? reversion of BDE change please? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A while ago bruce changed config(8) to not create the prototypes of the interrupt handlers in the generated file ioconf.h. I don't understand his reasoning but it causes me quite a bit of grief. He now has the rather odd idea that all device drivers should have their interrupt handlers prototyped in isa_device.h. How isa_device.h is supposed to know about al existing 3rd party drivers is apparenlty left as an exercise for the reader.... This is 'odd' in my opinion because that means that if i want to add a device driver I need to edit isa_device.h and add an entry for it. I think this goes in the oposite direction from being able to add drivers easily to the system. Previously I just had to add an approrpriate 'device' entry to my configuration file, and add a new files.MYCONF which held the additional files for my driver(s). I can see no reason that the prototypes for the interrupt handlers cannot be where they were before in ioconf.h. Certainly then a prototype exists for every handler mentionned in ioconf.c! I would like to suggest that despite bruce's objsections (and I'm sure he will object LOUDLY), that unless he can give a GOODB reason, or show how new drivers can be compiled in without editing files we revert that particular change. It's not a particular big reversion in config. Please, if you know why I should not do this (or can lend weight as to why I should) let me know! If I don't get a "DON'T DO THAT" from the core team, or a good reason not to, I will presume that this was another arbitrary BDE "cleanup" and revert it. Particularly I'd like to know if it breaks tha alpha port, or the new device framework? As it is now it certainly breaks several automatic build processes I know of (including the /usr/share/examples/drivers scripts) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:04:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13632 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:04:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13624 for ; Mon, 19 Oct 1998 13:04:01 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA26739; Mon, 19 Oct 1998 12:59:36 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdX26734; Mon Oct 19 19:59:29 1998 Date: Mon, 19 Oct 1998 12:59:24 -0700 (PDT) From: Julian Elischer To: Mike Smith cc: Doug White , "David J. Duchscher" , ulf@Alameda.net, current@FreeBSD.ORG Subject: Re: newfs problems, more information: In-Reply-To: <199810191849.LAA00514@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I also chastise people for it all the time :-) NEVER put a filesystem on 'c' (until 'c' loses all magic) On Mon, 19 Oct 1998, Mike Smith wrote: > > On Sun, 18 Oct 1998, David J. Duchscher wrote: > > > > > > > newfs: /dev/ccd0c: not a character-special device > > > > > > > > Don't put a filesystem on the 'c' partition. > > > > Mike likes to preach that (not using partiton c) but I haven't been able > > to bear it out on -STABLE. 3.0 may have changed the convention; I don't > > have a disk to test it on. > > Actually, I do it all the time. Bruce chastises people for doing it, > so I'm just repeating the Best Availalble Practice. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:05:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13710 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:05:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-26-dbn.dial-up.net [196.34.155.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13702 for ; Mon, 19 Oct 1998 13:05:21 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA00985; Mon, 19 Oct 1998 22:03:48 +0200 (SAT) From: Robert Nordier Message-Id: <199810192003.WAA00985@ceia.nordier.com> Subject: Re: To everyone who's been having trouble with the new "booteasy" In-Reply-To: <19981019021311.A12173@Alameda.net> from Ulf Zimmermann at "Oct 19, 98 02:13:11 am" To: ulf@Alameda.net Date: Mon, 19 Oct 1998 22:03:46 +0200 (SAT) Cc: rnordier@nordier.com, jkh@time.cdrom.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann wrote: > > > > If anyone who has been having problems would take five minutes to > > run a small diagnostics program > > > > http://www.freebsd.org/~rnordier/bootck-0.02.tar.gz > > > > (just dd the enclosed binary onto a floppy and reboot), I'd certainly > > appreciate it. > > bootck 0.02 > > Hit digit for hard drive to check [0-9]: 0 > Using BIOS drive 0x80 > BIOS geometry (0x13/0x8): 527/255/63 > BIOS int 0x13 extensions: version=0x1 support=0x1 > BIOS geometry (0x13/0x48): flags=0x1 0/0/0 > Reading MBR - > 0:* 0/1/1 0xa5 526/254/63 63 8466192 > 1: 0/0/0 0x0 0/0/0 0 0 > 2: 0/0/0 0x0 0/0/0 0 0 > 3: 0/0/0 0x0 0/0/0 0 0 > Read test > 8466192 Read test OK > Hit return to reboot: > > This is on an Intel DK440LX motherboard with latest BIOS. The system has > only the first IDE controller enabled, but the first SCSI disk is set > to be the first BIOS drive via the BIOS settings. Glad to have the feedback, thanks. I've committed some changes to boot0 based on the data received, though there is probably no particular reason to use it rather than booteasy for the moment. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:18:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14784 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:18:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-26-dbn.dial-up.net [196.34.155.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14776 for ; Mon, 19 Oct 1998 13:18:25 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA01014; Mon, 19 Oct 1998 22:17:07 +0200 (SAT) From: Robert Nordier Message-Id: <199810192017.WAA01014@ceia.nordier.com> Subject: Re: To everyone who's been having trouble with the new "booteasy" In-Reply-To: from "mike@seidata.com" at "Oct 19, 98 08:41:48 am" To: mike@seidata.com Date: Mon, 19 Oct 1998 22:17:05 +0200 (SAT) Cc: rnordier@nordier.com, jkh@time.cdrom.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mike@seidata.com wrote: > On Mon, 19 Oct 1998, Robert Nordier wrote: > > > http://www.freebsd.org/~rnordier/bootck-0.02.tar.gz > > Curious... what's continuous beeping mean? Other than 'You messed up > the floppy...' ;) Hope you didn't try to boot the tarball itself. :) Around here it usually means 'The exchange is busy and cannot route your call; please replace the handset and try again later...' Once out of POST (Power-On Self-Test), I don't think there is a standard system of beeps on the PC. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17131 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:44:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17073 for ; Mon, 19 Oct 1998 13:43:58 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01214; Mon, 19 Oct 1998 13:48:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810192048.NAA01214@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: vote:? reversion of BDE change please? In-reply-to: Your message of "Mon, 19 Oct 1998 12:52:49 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Oct 1998 13:48:22 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > A while ago bruce changed config(8) to not create the prototypes of > the interrupt handlers in the generated file ioconf.h. > > I don't understand his reasoning but it causes me quite a bit of grief. > He now has the rather odd idea that all device drivers should have their > interrupt handlers prototyped in isa_device.h. How isa_device.h is > supposed to know about al existing 3rd party drivers is apparenlty left as > an exercise for the reader.... > > This is 'odd' in my opinion because that means that if i want to > add a device driver I need to edit isa_device.h and add an entry for it. > I think this goes in the oposite direction from being able to add drivers > easily to the system. The change is actually in the right direction, as the goal is to remove the prototypes from global scope completely. Instead, ISA device drivers should register their interrupt handlers at attach time. I don't know if there's an example of this at the present time. > Particularly I'd like to know if it breaks tha alpha port, or > the new device framework? > As it is now it certainly breaks several automatic build processes I know > of (including the /usr/share/examples/drivers scripts) IMHO, the followup changes have been too slow coming. The new bus framework should completely obsolete interrupt handler prototypes, which may explain the pedestrian pace of the followups. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:46:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17335 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:46:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17330 for ; Mon, 19 Oct 1998 13:46:25 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id QAA21744; Mon, 19 Oct 1998 16:45:32 -0400 (EDT) Date: Mon, 19 Oct 1998 16:45:32 -0400 (EDT) Message-Id: <199810192045.QAA21744@highwind.com> From: HighWind Software Information To: eischen@vigrid.com CC: current@FreeBSD.ORG, bright@hotjobs.com In-reply-to: <199810191926.PAA10944@pcnet1.pcnet.com> (message from Daniel Eischen on Mon, 19 Oct 1998 15:26:27 -0400 (EDT)) Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe your test program is in error. Your threads are not ever going to awake from the pthread_cond_wait() statement because the mutex cannot be acquired. Your main thread locks the mutex and never unlocks it. I claim that doesn't matter. WHY should the CPU spin if I signal twice on a lock I have? That is PERFECTLY valid. Let's say I want to say that TWO events are ready to be handled. That is perfectly fine. --- Simply to placate your claim, here is another version that locks and unlocks the mutex in proper fashion. I simply had to insert an additional "sleep" to get the bug to appear. In both cases, spinning the CPU at 100% and allowing the program to hang and make no forward progress is a SERIOUS bug. I claim that this new version is 100% valid. Does proper locking, and also works on other O/S's. On FreeBSD it does not work at all. -Rob ------- /* Illustration of FreeBSD pthread_cond_wait() bug This program sets up a conditional wait and fires off a dozen threads that simply wait for the condition. Once the threads are started, the main thread loops signalling the condition once a second. Normally, this should result in "Signalling" and "Got Condition" being printed once a second. However, because of some bugs in FreeBSD, the pthread_cond_wait() spins the CPU and no progress is made. g++ -o condWaitBug -D_REENTRANT -D_THREAD_SAFE -g -Wall condWaitBug.C -pthread */ #include #include #include #include #include pthread_mutex_t lock; pthread_cond_t condition; static void *condThread(void *) { // Wait until we are signalled, then print. while (true) { // Be sure to do proper locking and unlocking assert(!::pthread_mutex_lock(&lock)); assert(!::pthread_cond_wait(&condition, &lock)); ::printf("Got Condition!\n"); assert(!::pthread_mutex_unlock(&lock)); } } int main(int, char **) { // Initialize Lock pthread_mutexattr_t lock_attr; assert(!::pthread_mutexattr_init(&lock_attr)); assert(!::pthread_mutex_init(&lock, &lock_attr)); assert(!::pthread_mutexattr_destroy(&lock_attr)); // Initialize Condition pthread_condattr_t cond_attr; assert(!::pthread_condattr_init(&cond_attr)); assert(!::pthread_cond_init(&condition, &cond_attr)); assert(!::pthread_condattr_destroy(&cond_attr)); // Spawn off a dozen threads to get signalled for (int j = 0; j < 12; ++j) { pthread_t tid; pthread_attr_t attr; assert(!::pthread_attr_init(&attr)); assert(!::pthread_create(&tid, &attr, condThread, 0)); assert(!::pthread_attr_destroy(&attr)); } // Sleep for 3 seconds to make sure the threads started up. timeval timeout; timeout.tv_sec = 3; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); for (int k = 0; k < 60; ++k) { // Signal while locked assert(!::pthread_mutex_lock(&lock)); ::printf("Signalling\n"); assert(!::pthread_cond_signal(&condition)); // Sleep for 1 second timeout.tv_sec = 1; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); ::printf("Signalled again\n"); assert(!::pthread_cond_signal(&condition)); assert(!::pthread_mutex_unlock(&lock)); // Sleep for 1 second timeout.tv_sec = 1; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); } return EXIT_SUCCESS; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:46:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17366 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:46:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17361 for ; Mon, 19 Oct 1998 13:46:47 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id VAA13191; Mon, 19 Oct 1998 21:45:11 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id WAA24037; Mon, 19 Oct 1998 22:33:23 +0200 (CEST) (envelope-from andreas) Message-ID: <19981019223322.B17441@klemm.gtn.com> Date: Mon, 19 Oct 1998 22:33:22 +0200 From: Andreas Klemm To: "Kenneth D. Merry" , Nathan Dorfman Cc: freebsd-current@FreeBSD.ORG Subject: packet writing ( was Re: 3.0-R, CAM, and audio tracks (more info)) References: <19981018234428.A15396@binary.net> <199810190617.AAA21008@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810190617.AAA21008@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Oct 19, 1998 at 12:17:41AM -0600 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 2.2.7-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 12:17:41AM -0600, Kenneth D. Merry wrote: > Nathan Dorfman wrote... BTW, what about "packet writing" ? I really like this feature in Windoof environment. Would there be any possibility to implement this mode and to format/fixate by using a sysctl command or such ? -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:47:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17406 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:47:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17396 for ; Mon, 19 Oct 1998 13:47:19 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id VAA13187; Mon, 19 Oct 1998 21:45:07 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id WAA23184; Mon, 19 Oct 1998 22:30:22 +0200 (CEST) (envelope-from andreas) Message-ID: <19981019223021.A17441@klemm.gtn.com> Date: Mon, 19 Oct 1998 22:30:21 +0200 From: Andreas Klemm To: Mike Smith , ulf@Alameda.net Cc: current@FreeBSD.ORG Subject: Re: newfs problems, more information: References: <19981017184238.A26929@Alameda.net> <199810180203.TAA08917@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810180203.TAA08917@dingo.cdrom.com>; from Mike Smith on Sat, Oct 17, 1998 at 07:03:04PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 2.2.7-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 17, 1998 at 07:03:04PM -0700, Mike Smith wrote: > > > > I have a machine with BETA from 0930 installed: > > Update. > > > Doing a newfs on it: > > > > PacHell root / # newfs /dev/ccd0c > > newfs: /dev/ccd0c: not a character-special device > > Don't put a filesystem on the 'c' partition. Why ? Never had trouble with this ... /dev/ccd0c 198327 92632 89829 51% /obj /dev/ccd1c 198327 25065 157396 14% /news /dev/ccd2c 99055 36883 54248 40% /proxy /dev/ccd3c 3400078 2886831 241241 92% /home -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:47:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17436 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:47:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA17423 for ; Mon, 19 Oct 1998 13:47:27 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zVMCb-0007jg-00; Mon, 19 Oct 1998 14:46:53 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id OAA29076; Mon, 19 Oct 1998 14:46:58 -0600 (MDT) Message-Id: <199810192046.OAA29076@harmony.village.org> To: Julian Elischer Subject: Re: newfs problems, more information: Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Oct 1998 12:59:24 PDT." References: Date: Mon, 19 Oct 1998 14:46:58 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Julian Elischer writes: : I also chastise people for it all the time :-) : NEVER put a filesystem on 'c' : (until 'c' loses all magic) Why? It works and I've been doing it literally for years. What magic does 'c' have that would make this a bad idea? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:50:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17935 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:50:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17927 for ; Mon, 19 Oct 1998 13:50:42 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA23320; Mon, 19 Oct 1998 14:50:17 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA00042; Mon, 19 Oct 1998 14:50:17 -0600 Date: Mon, 19 Oct 1998 14:50:17 -0600 Message-Id: <199810192050.OAA00042@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: vote:? reversion of BDE change please? In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Please, if you know why I should not do this (or can lend weight > as to why I should) let me know! Because the interrupt mechanism need to become less ISA/x86 centric. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:53:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18318 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:53:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18308 for ; Mon, 19 Oct 1998 13:53:02 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id WAA20661; Mon, 19 Oct 1998 22:51:48 +0200 (CEST) To: Mike Smith cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: vote:? reversion of BDE change please? In-reply-to: Your message of "Mon, 19 Oct 1998 13:48:22 PDT." <199810192048.NAA01214@dingo.cdrom.com> Date: Mon, 19 Oct 1998 22:51:48 +0200 Message-ID: <20659.908830308@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The change is actually in the right direction, as the goal is to remove >the prototypes from global scope completely. Instead, ISA device >drivers should register their interrupt handlers at attach time. I >don't know if there's an example of this at the present time. I think some of the pccard stuff does it [*] Poul-Henning [*] probably doing it the bde::wrong_way() -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:54:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18418 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:54:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18412 for ; Mon, 19 Oct 1998 13:54:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01298 for ; Mon, 19 Oct 1998 13:58:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810192058.NAA01298@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Bogus world build results? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Oct 1998 13:58:26 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG azaria:/usr/src>grep ">>>" makelog >>> elf make world started on Mon Oct 19 11:32:01 PDT 1998 >>> Cleaning up the temporary elf build tree >>> Making make >>> Making mtree >>> Making hierarchy >>> Cleaning up the elf obj tree >>> Rebuilding the elf obj tree >>> Rebuilding elf bootstrap tools >>> Rebuilding tools necessary to build the include files >>> Rebuilding /usr/include >>> Rebuilding bootstrap libraries >>> Rebuilding tools needed to build libraries >>> Rebuilding all other tools needed to build the elf world >>> Building elf libraries >>> Building everything.. >>> Making hierarchy >>> Rebuilding the aout obj tree >>> Rebuilding /usr/include >>> Making hierarchy >>> Installing everything.. >>> Re-scanning the shared libraries.. >>> Rebuilding man page indexes >>> aout make world completed on Mon Oct 19 13:43:00 PDT 1998 azaria:/usr/src>file `which ls` /bin/ls: FreeBSD/i386 compact demand paged executable azaria:/usr/src>objformat elf Something appears to have spagged $OBJFORMAT halfway through the build, resulting in an a.out world being built. This is -current as of about 1pm PST today. Any ideas? I'm nuking the entire build tree and starting from scratch just to be sure, but I'm pretty sure I'm clean. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 13:56:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18653 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:56:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nu.binary.net (nu.binary.net [12.13.120.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18642 for ; Mon, 19 Oct 1998 13:56:19 -0700 (PDT) (envelope-from nathan@matrix.binary.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by nu.binary.net (8.9.1a/8.9.0) with ESMTP id PAA26076; Mon, 19 Oct 1998 15:55:54 -0500 (CDT) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id PAA26839; Mon, 19 Oct 1998 15:55:54 -0500 (CDT) Message-ID: <19981019165554.A26588@binary.net> Date: Mon, 19 Oct 1998 16:55:54 -0400 From: Nathan Dorfman To: Andreas Klemm , "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: packet writing ( was Re: 3.0-R, CAM, and audio tracks (more info)) References: <19981018234428.A15396@binary.net> <199810190617.AAA21008@panzer.plutotech.com> <19981019223322.B17441@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981019223322.B17441@klemm.gtn.com>; from Andreas Klemm on Mon, Oct 19, 1998 at 10:33:22PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 10:33:22PM +0200, Andreas Klemm wrote: > On Mon, Oct 19, 1998 at 12:17:41AM -0600, Kenneth D. Merry wrote: > > Nathan Dorfman wrote... > > BTW, what about "packet writing" ? > I really like this feature in Windoof environment. > Would there be any possibility to implement this mode > and to format/fixate by using a sysctl command or such ? There is an 'experimental' packet writing mode in cdrecord. What does it do? And since we're straying really far from my original topic, anyone have an idea what I can do to get an audio grab right? > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > What gives you 90% more speed, for example, in kernel compilation ? > http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html > "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:04:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19374 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:04:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19369 for ; Mon, 19 Oct 1998 14:04:20 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id PAA25261; Mon, 19 Oct 1998 15:03:44 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810192103.PAA25261@panzer.plutotech.com> Subject: Re: packet writing ( was Re: 3.0-R, CAM, and audio tracks (more info)) In-Reply-To: <19981019223322.B17441@klemm.gtn.com> from Andreas Klemm at "Oct 19, 98 10:33:22 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Mon, 19 Oct 1998 15:03:44 -0600 (MDT) Cc: nathan@rtfm.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Klemm wrote... > On Mon, Oct 19, 1998 at 12:17:41AM -0600, Kenneth D. Merry wrote: > > Nathan Dorfman wrote... > > BTW, what about "packet writing" ? > I really like this feature in Windoof environment. > Would there be any possibility to implement this mode > and to format/fixate by using a sysctl command or such ? And this is something that cdrecord won't do? cdrecord is the only supported way of burning CDs under CAM. I may implement a more generic solution through the CD driver at some point, but it probably won't be anytime soon. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:05:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19451 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:05:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19446 for ; Mon, 19 Oct 1998 14:05:31 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id OAA14040; Mon, 19 Oct 1998 14:04:56 -0700 (PDT) Message-ID: <19981019140456.B4089@Alameda.net> Date: Mon, 19 Oct 1998 14:04:56 -0700 From: Ulf Zimmermann To: Robert Nordier Cc: jkh@time.cdrom.com, current@FreeBSD.ORG Subject: Re: To everyone who's been having trouble with the new "booteasy" Reply-To: ulf@Alameda.net References: <19981019021311.A12173@Alameda.net> <199810192003.WAA00985@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810192003.WAA00985@ceia.nordier.com>; from Robert Nordier on Mon, Oct 19, 1998 at 10:03:46PM +0200 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 10:03:46PM +0200, Robert Nordier wrote: > Ulf Zimmermann wrote: > > > > > > If anyone who has been having problems would take five minutes to > > > run a small diagnostics program > > > > > > http://www.freebsd.org/~rnordier/bootck-0.02.tar.gz > > > > > > (just dd the enclosed binary onto a floppy and reboot), I'd certainly > > > appreciate it. > > > > bootck 0.02 > > > > Hit digit for hard drive to check [0-9]: 0 > > Using BIOS drive 0x80 > > BIOS geometry (0x13/0x8): 527/255/63 > > BIOS int 0x13 extensions: version=0x1 support=0x1 > > BIOS geometry (0x13/0x48): flags=0x1 0/0/0 > > Reading MBR - > > 0:* 0/1/1 0xa5 526/254/63 63 8466192 > > 1: 0/0/0 0x0 0/0/0 0 0 > > 2: 0/0/0 0x0 0/0/0 0 0 > > 3: 0/0/0 0x0 0/0/0 0 0 > > Read test > > 8466192 Read test OK > > Hit return to reboot: > > > > This is on an Intel DK440LX motherboard with latest BIOS. The system has > > only the first IDE controller enabled, but the first SCSI disk is set > > to be the first BIOS drive via the BIOS settings. > > Glad to have the feedback, thanks. > > I've committed some changes to boot0 based on the data received, though > there is probably no particular reason to use it rather than booteasy > for the moment. The machine I am testing on is called Playtoy and that name stands for what it is. Gimme something to test and I will test. > > -- > Robert Nordier -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:06:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19549 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:06:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19543 for ; Mon, 19 Oct 1998 14:06:37 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id HAA21106; Tue, 20 Oct 1998 07:08:08 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810192108.HAA21106@cimlogic.com.au> Subject: Re: paranoid question: aout vs ELF... In-Reply-To: from Marc Fournier at "Oct 19, 98 11:07:34 am" To: marc.fournier@acadiau.ca (Marc Fournier) Date: Tue, 20 Oct 1998 07:08:08 +1000 (EST) Cc: eculp@webwizard.org.mx, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Fournier wrote: > Okay, then that makes me *really* nervous...does the following sound safe? [...] > I'm still running a 3.0-CURRENT machine as of July 24th or so...its a > production machine, and its half a country away, so I'm very nervous... Please don't do source-level upgrades of production machines, particularly ones that are "half a country away". This is just asking for trouble. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:09:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19860 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:09:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lepton.nuc.net (lepton.nuc.net [204.49.61.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19852 for ; Mon, 19 Oct 1998 14:09:52 -0700 (PDT) (envelope-from wheelman@nuc.net) Received: from electron.nuc.net (dhcp1.nuc.net [204.49.61.49]) by lepton.nuc.net (8.8.8/8.8.8) with SMTP id QAA27826; Mon, 19 Oct 1998 16:08:21 -0500 (CDT) (envelope-from wheelman@nuc.net) From: "Jaime Bozza" To: "Andreas Klemm" , "Mike Smith" , Cc: Subject: RE: newfs problems, more information: Date: Mon, 19 Oct 1998 16:06:34 -0500 Message-ID: <001101bdfba4$5a663d20$313d31cc@electron.nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-reply-to: <19981019223021.A17441@klemm.gtn.com> Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Don't put a filesystem on the 'c' partition. > > Why ? Never had trouble with this ... > > /dev/ccd0c 198327 92632 89829 51% /obj > /dev/ccd1c 198327 25065 157396 14% /news > /dev/ccd2c 99055 36883 54248 40% /proxy > /dev/ccd3c 3400078 2886831 241241 92% /home Most importantly, how does one specify to *NOT* use 'c' with ccd? /etc/ccd.conf takes the format "ccd0" without [a-g] after it. Once the ccd is configured, you mount /dev/ccd0c. I don't know all the internal workings of ccd, but from the documentation, the 'c' slice is automatically used. And if this is not the preferred way, how would one go about specifying a different slice? Jaime Bozza Nucleus Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:10:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19999 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:10:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf26.cruzers.com [205.215.232.26]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA19993 for ; Mon, 19 Oct 1998 14:10:22 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 28239 invoked by uid 100); 19 Oct 1998 21:09:19 -0000 Date: Mon, 19 Oct 1998 14:09:19 -0700 To: freebsd-current@FreeBSD.ORG Subject: disklabel: ioctl DIOCWLABEL: Operation not supported by device Message-ID: <19981019140919.A28190@top.worldcontrol.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Following the directions at http://www.freebsd.org/tutorials/diskformat/#ch-2 to add a hard drive to my -current,elf,CAM,SMP system I get errors along the lines of label: ioctl DIOCWLABEL: Operation not supported by device The system is -current of around 1:00am 10/19/1998 PDT, including a make world and fresh kernel. I can report that /stand/sysinstall index/partition reports that I have no disks. However, the system is fully functional other than for my attempts to add two hard drives. I've tried the various methods listed in the help page, all fail for various label related reasons. here is a sample: bls2# disklabel -r -w da1 auto disklabel: ioctl DIOCWLABEL: Operation not supported by device dmesg reports: da2 at ahc0 bus 0 target 5 lun 0 da2: Fixed Direct Access SCSI2 device da2: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C) da1 at ahc0 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI2 device da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:14:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20300 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:14:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20295 for ; Mon, 19 Oct 1998 14:14:17 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA00311; Mon, 19 Oct 1998 14:12:19 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdsHR297; Mon Oct 19 21:12:13 1998 Date: Mon, 19 Oct 1998 14:12:05 -0700 (PDT) From: Julian Elischer To: Nate Williams cc: current@FreeBSD.ORG Subject: Re: vote:? reversion of BDE change please? In-Reply-To: <199810192050.OAA00042@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG True, but till that happens automatic mechanisms are broken! he could have just left them in ioconf.h till they were not needed at all and then deleted them from there, rather than break ioconf.c. On Mon, 19 Oct 1998, Nate Williams wrote: > > Please, if you know why I should not do this (or can lend weight > > as to why I should) let me know! > > Because the interrupt mechanism need to become less ISA/x86 centric. > > > Nate > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:14:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20316 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:14:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20311 for ; Mon, 19 Oct 1998 14:14:21 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA29824; Mon, 19 Oct 1998 14:03:36 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdY29818; Mon Oct 19 21:03:30 1998 Date: Mon, 19 Oct 1998 14:03:24 -0700 (PDT) From: Julian Elischer To: Warner Losh cc: current@FreeBSD.ORG Subject: Re: newfs problems, more information: In-Reply-To: <199810192046.OAA29076@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok, for one, there is magic that corrects 'c' partition boundaries under some cases.. if 'c' stops being magic then everything may 'shift' if you are relying on this without knowing it. also, 'c' is special in the case of bad144 error correction though this presently has no real effect. 'c' special and its behaviour may change in the future in unpredictable ways. Until there is no code in the kernel that says if (part == RAW_PART) { some magic occurs; } I personally wouldn't use it. eventually you should be able to use wd0s1 or just wd0 instead of wd0s1c or wd0c why use 'c'? just make an 'a' with the same figures... Oh yeah... 'c' exists even if there is no valid disklabel (it's created by default...) I've seen (not recently) cases where people actually made a filesystem using 'c' and THEN they discoverd that there was not actually a disklabel on the disk :-) (I don't think this can happen any more with bruces code, but it was a problem at one stage before he abstracted all that code from all the drivers) I just get all queezy when I think of it.. :-) It's just relying on too many magic bandaids, which I were removing with my slice code before it was so suddenly deleted. I just don't understand why others don't get this 'uneasy feeling about 'c'' julian On Mon, 19 Oct 1998, Warner Losh wrote: > In message Julian Elischer writes: > : I also chastise people for it all the time :-) > : NEVER put a filesystem on 'c' > : (until 'c' loses all magic) > > Why? It works and I've been doing it literally for years. What magic > does 'c' have that would make this a bad idea? > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:24:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21222 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:24:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21217 for ; Mon, 19 Oct 1998 14:24:29 -0700 (PDT) (envelope-from fcurrent@jraynard.demon.co.uk) Received: from [158.152.42.77] (helo=jraynard.demon.co.uk) by post.mail.demon.net with esmtp (Exim 2.05demon1 #1) id 0zVMmW-00029L-00; Mon, 19 Oct 1998 21:24:01 +0000 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.9.1/8.9.1) id VAA01469; Mon, 19 Oct 1998 21:11:14 +0100 (BST) (envelope-from fcurrent) Message-ID: <19981019211113.21905@jraynard.demon.co.uk> Date: Mon, 19 Oct 1998 21:11:13 +0100 From: James Raynard To: obrien@NUXI.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: GNU Awk replacement References: <19981018215440.A25652@nuxi.com> <19981018223914.B25719@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19981018223914.B25719@nuxi.com>; from David O'Brien on Sun, Oct 18, 1998 at 10:39:14PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 18, 1998 at 10:39:14PM -0700, David O'Brien wrote: > > Good question. Our kawk port (kawk-98.02.11). > from http://cm.bell-labs.com/who/bwk/awk.tar.gz I put a bmake/contribified version of this on my Web page (http://www.freebsd.org/~jraynard), several months before the port went in. It includes ache's I18N patches, amongst other things. I haven't committed it because: 1. I don't know how to test the I18N stuff. 2. I'm not sure how Posix-compliant it is - it fails some of the Posix tests that come with GNU awk, and I'm not convinced they're all GNU-specific. 3. I didn't get any response to my call for testers. 4. I'd just committed a new version of GNU awk and it didn't seem a good time to change things again. 5. I don't actually know very much about awk - I only worked on it because for some reason people kept emailing me about changing the version in the tree :-) James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21349 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:27:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21344 for ; Mon, 19 Oct 1998 14:26:59 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA24567; Mon, 19 Oct 1998 17:26:29 -0400 (EDT) Date: Mon, 19 Oct 1998 17:26:29 -0400 (EDT) From: Daniel Eischen Message-Id: <199810192126.RAA24567@pcnet1.pcnet.com> To: eischen@vigrid.com, info@highwind.com Subject: Re: Another Serious libc_r problem Cc: bright@hotjobs.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I believe your test program is in error. Your threads are > not ever going to awake from the pthread_cond_wait() statement > because the mutex cannot be acquired. Your main thread locks > the mutex and never unlocks it. > > I claim that doesn't matter. WHY should the CPU spin if I signal > twice on a lock I have? That is PERFECTLY valid. > > Let's say I want to say that TWO events are ready to be handled. > That is perfectly fine. > > Simply to placate your claim, here is another version that locks and > unlocks the mutex in proper fashion. I simply had to insert an > additional "sleep" to get the bug to appear. This works peachy on -stable. I don't have access to a -current box until I get home. > > In both cases, spinning the CPU at 100% and allowing the program to > hang and make no forward progress is a SERIOUS bug. Like I said earlier, I believe there was a recent fix for this. If you search the -current mailing list archive, you'll see the original post about this problem and an included patch that purportedly fixes it. Search for "1,000,001 yields and still second thread doesn't execute" Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:36:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22150 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:36:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA22143 for ; Mon, 19 Oct 1998 14:36:41 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 17859 invoked by uid 1001); 19 Oct 1998 21:36:15 +0000 (GMT) To: freebsd-current@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Problems with Digital server with P-166 and Neptune chipset X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 19 Oct 1998 23:36:15 +0200 Message-ID: <17857.908832975@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to get FreeBSD 3.0 to run reliably on a Digital server with Neptune chipset - so far without great success. (2.2.7, btw, wouldn't install at all. 3.0 installed with some effort). The problems I see *may* be the fault of the PCI chipset. On http://www.freebsd.org/handbook/handbook138.html, it says: Neptune: Can not run more than 2 bus master devices. Admitted Intel design flaw. Workarounds include do not run more than 2 bus masters, special hardware design to replace the PCI bus arbiter (appears on Intel Altair board and several other Intel server group MB's). And of course Intel's official answer, move to the Triton chip set, we ``fixed it there''. I don't know any more about the Neptune problem than what I've seen on this Web page. The actual behavior I see is sudden reboots without any apparent cause - and no messages in the system logs. The system *has* more than two bus master devices (21140 Ethernet card, two Buslogic Multimaster SCSI controllers, 7 SCSI disks, SCSI CDROM, SCSI tape). On the other hand, Patrick Duffy's "PCI Chipsets" list says about the Neptune: Rev. 1: (problems mentioned) Rev. 2: This chipset is in boards shipped by Intel to vendors as of about mid August 1994. It has no reported problems (and works well in my system). The system I have may be Rev. 2: chip0: rev 0x11 on pci0.0.0 (/sys/pcisupport.c lists rev 16 and 17 as Neptune - so my guess, without checking the Intel data sheet, is that I have a Neptune rev. 2 chipset.) Any good hints on where I should start looking to find the cause of the sudden reboots? Oh yeah, the two Buslogic SCSI controllers appear in the kernel config file as ISA controllers: controller bt0 at isa? port ? cam irq ? controller bt1 at isa? port ? cam irq ? but they are very definitely PCI controllers: bt0: rev 0x00 int a irq 10 on pci0.6.0 bt0: BT-946C FW Rev. 4.28D Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs bt1: rev 0x00 int a irq 12 on pci0.7.0 bt1: BT-946C FW Rev. 4.28D Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs What's going on here? Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #0: Mon Oct 19 14:24:50 GMT 1998 root@newsfeed50.telia.com:/usr/src/sys/compile/NEWSFEED50 Timecounter "i8254" frequency 1193182 Hz cost 3077 ns Timecounter "TSC" frequency 166666786 Hz cost 140 ns CPU: Pentium/P54C (166.67-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 269221888 (262912K bytes) avail memory = 258985984 (252916K bytes) eisa0: Probing for devices on the EISA bus Probing for devices on PCI bus 0: chip0: rev 0x11 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x03 on pci0.2.0 bt0: rev 0x00 int a irq 10 on pci0.6.0 bt0: BT-946C FW Rev. 4.28D Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs bt1: rev 0x00 int a irq 12 on pci0.7.0 bt1: BT-946C FW Rev. 4.28D Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs de0: rev 0x12 int a irq 11 on pci0.8.0 de0: DEC DE500-XA 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:f8:03:25:26 Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 bt: unit number (2) too high bt2 not found at 0x230 bt: unit number (2) too high bt2 not found at 0x230 npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround Waiting 3 seconds for SCSI devices to settle de0: enabling 10baseT port sa0 at bt1 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 5.0MB/s transfers (5.0MHz, offset 8) da0 at bt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 2007MB (4110480 512 byte sectors: 128H 32S/T 1003C) da3 at bt1 bus 0 target 0 lun 0 da3: Fixed Direct Access SCSI2 device da3: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da3: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) da4 at bt1 bus 0 target 1 lun 0 da4: Fixed Direct Access SCSI2 device da4: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da4: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) da2 at bt0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da2: 2007MB (4110480 512 byte sectors: 128H 32S/T 1003C) da1 at bt0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2007MB (4110480 512 byte sectors: 128H 32S/T 1003C) da6 at bt1 bus 0 target 3 lun 0 da6: Fixed Direct Access SCSI2 device da6: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da6: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) da5 at bt1 bus 0 target 2 lun 0 da5: Fixed Direct Access SCSI2 device da5: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da5: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) changing root device to da0s1a de0: enabling 100baseTX port de0: enabling Full Duplex 100baseTX port cd0 at bt1 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 4.32MB/s transfers (4.32MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:43:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23062 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:43:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA23053 for ; Mon, 19 Oct 1998 14:43:50 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 17904 invoked by uid 1001); 19 Oct 1998 21:41:40 +0000 (GMT) To: julian@whistle.com Cc: current@FreeBSD.ORG Subject: Re: newfs problems, more information: In-Reply-To: Your message of "Mon, 19 Oct 1998 14:03:24 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 19 Oct 1998 23:41:40 +0200 Message-ID: <17902.908833300@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just don't understand why others don't get this 'uneasy feeling about > 'c'' - Because it works in other operating systems. - Because it *appears* to work in FreeBSD. - Because it seems completely unnecessary to create an extra partition when you want to use exactly what the c partition covers. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:49:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23503 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:49:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23498 for ; Mon, 19 Oct 1998 14:49:04 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id PAA22655; Mon, 19 Oct 1998 15:41:37 -0600 (MDT) Date: Mon, 19 Oct 1998 15:41:37 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199810192141.PAA22655@narnia.plutotech.com> To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: vote:? reversion of BDE change please? Newsgroups: pluto.freebsd.current In-Reply-To: <199810192048.NAA01214@dingo.cdrom.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The change is actually in the right direction, as the goal is to remove > the prototypes from global scope completely. Instead, ISA device > drivers should register their interrupt handlers at attach time. I > don't know if there's an example of this at the present time. The CAM ISA SCSI drivers set their own vectors and thus do not need entries in isa_devices.h. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:52:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23893 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:52:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23858 for ; Mon, 19 Oct 1998 14:52:03 -0700 (PDT) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id SAA08408; Mon, 19 Oct 1998 18:51:12 -0300 (ADT) Date: Mon, 19 Oct 1998 18:51:10 -0300 (ADT) From: Marc Fournier X-Sender: marc@iceberg To: John Birrell cc: eculp@webwizard.org.mx, freebsd-current@FreeBSD.ORG Subject: Re: paranoid question: aout vs ELF... In-Reply-To: <199810192108.HAA21106@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, John Birrell wrote: > Marc Fournier wrote: > > Okay, then that makes me *really* nervous...does the following sound safe? > [...] > > I'm still running a 3.0-CURRENT machine as of July 24th or so...its a > > production machine, and its half a country away, so I'm very nervous... > > Please don't do source-level upgrades of production machines, particularly > ones that are "half a country away". This is just asking for trouble. Unless you can suggestion something else, I don't have much choice in this matter :( My history file for news is at ~700Meg, and expire won't work because it can't allocate memory due to a hard limit in my kernel.. :( Trust me, this isn't something that I really want to be doing :( Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 14:59:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24375 for freebsd-current-outgoing; Mon, 19 Oct 1998 14:59:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24365 for ; Mon, 19 Oct 1998 14:59:00 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA21511; Tue, 20 Oct 1998 08:00:36 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810192200.IAA21511@cimlogic.com.au> Subject: Re: paranoid question: aout vs ELF... In-Reply-To: from Marc Fournier at "Oct 19, 98 06:51:10 pm" To: marc.fournier@acadiau.ca (Marc Fournier) Date: Tue, 20 Oct 1998 08:00:36 +1000 (EST) Cc: jb@cimlogic.com.au, eculp@webwizard.org.mx, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Fournier wrote: > Unless you can suggestion something else, I don't have much choice in this > matter :( My history file for news is at ~700Meg, and expire won't work > because it can't allocate memory due to a hard limit in my kernel.. :( Is it possible for you to just build a new kernel to get around the hard limit problem? Introducing a significant emotional event like upgrading to elf at the same time seems unnecessary. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:03:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24736 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:03:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24695 for ; Mon, 19 Oct 1998 15:03:01 -0700 (PDT) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id TAA09608; Mon, 19 Oct 1998 19:02:17 -0300 (ADT) Date: Mon, 19 Oct 1998 19:02:16 -0300 (ADT) From: Marc Fournier X-Sender: marc@iceberg To: John Birrell cc: eculp@webwizard.org.mx, freebsd-current@FreeBSD.ORG Subject: Re: paranoid question: aout vs ELF... In-Reply-To: <199810192200.IAA21511@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, John Birrell wrote: > Marc Fournier wrote: > > Unless you can suggestion something else, I don't have much choice in this > > matter :( My history file for news is at ~700Meg, and expire won't work > > because it can't allocate memory due to a hard limit in my kernel.. :( > > Is it possible for you to just build a new kernel to get around the > hard limit problem? Introducing a significant emotional event like upgrading > to elf at the same time seems unnecessary. The problem is that my last upgrade was around mid-July...prior to CAM being integrated, so it was all 'hand-patched'...if I upgrade just the 'current kernel', I *have* to upgrade the rest, no? I don't want to go back to the mid-Jully source tree, since there has been alot of stuff done with CAM since then :( Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:05:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24929 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:05:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24924 for ; Mon, 19 Oct 1998 15:05:39 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id SAA27896; Mon, 19 Oct 1998 18:05:08 -0400 (EDT) Message-ID: <19981019180508.A26343@netmonger.net> Date: Mon, 19 Oct 1998 18:05:08 -0400 From: Christopher Masto To: freebsd-current@FreeBSD.ORG Subject: Re: cvsup and file permissions Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <19981015194840.A16439@netmonger.net> <199810160028.RAA02305@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810160028.RAA02305@dingo.cdrom.com>; from Mike Smith on Thu, Oct 15, 1998 at 05:28:51PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 15, 1998 at 05:28:51PM -0700, Mike Smith wrote: > > This is something I've kind of been ignoring for a while, but now that > > I'm tracking current/BETA on a couple more machines, I'd like to solve > > it. I don't see anything obvious in the manpage. > > > > Basically, I maintain one copy of the CVS tree on our big server with > > cvsup, and use remote CVS+ssh to check stuff out onto other machines. > > Because CVS needs write access, I have set up a group for the users > > that have permission to do this sort of thing. The problem is that cvsup > > keeps taking the group permissions away when it updates the repository. > > Use the -R option to cvs when checking out. I've gotten around to trying this and it doesn't actually work.. chris@lion-around:/tmp/cvstest$ export CVS_RSH=ssh chris@lion-around:/tmp/cvstest$ cvs -R -d :ext:chris@cheddar:/usr/cvs/freebsd checkout src/tools cvs server: Updating src/tools cvs server: failed to create lock directory in repository `/usr/cvs/freebsd/src/tools': Permission denied cvs server: failed to obtain dir lock in repository `/usr/cvs/freebsd/src/tools' cvs [server aborted]: read lock failed - giving up It does work if I log on to the repository machine and don't use remote CVS. Regardless, it would be nice to have a way to tell cvsup not to sync permissions. -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ Appeasement, said Winston Churchill, consists of being nice to a crocodile in the hope that he will eat you last. At the moment, the biggest crocodile in the world is Microsoft, and everybody is busy sucking up to it. - JOHN NAUGHTON, the London Observer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:07:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25044 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:07:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25037 for ; Mon, 19 Oct 1998 15:07:15 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA21546; Tue, 20 Oct 1998 08:08:46 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810192208.IAA21546@cimlogic.com.au> Subject: Re: paranoid question: aout vs ELF... In-Reply-To: from Marc Fournier at "Oct 19, 98 07:02:16 pm" To: marc.fournier@acadiau.ca (Marc Fournier) Date: Tue, 20 Oct 1998 08:08:46 +1000 (EST) Cc: jb@cimlogic.com.au, eculp@webwizard.org.mx, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Fournier wrote: > The problem is that my last upgrade was around mid-July...prior to > CAM being integrated, so it was all 'hand-patched'...if I upgrade just the > 'current kernel', I *have* to upgrade the rest, no? I don't want to go > back to the mid-Jully source tree, since there has been alot of stuff done > with CAM since then :( OK, then stay aout for the initial `make world'. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:16:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25745 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:16:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25740 for ; Mon, 19 Oct 1998 15:16:07 -0700 (PDT) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id TAA10827; Mon, 19 Oct 1998 19:15:26 -0300 (ADT) Date: Mon, 19 Oct 1998 19:15:25 -0300 (ADT) From: Marc Fournier X-Sender: marc@iceberg To: John Birrell cc: eculp@webwizard.org.mx, freebsd-current@FreeBSD.ORG Subject: Re: paranoid question: aout vs ELF... In-Reply-To: <199810192208.IAA21546@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, John Birrell wrote: > Marc Fournier wrote: > > The problem is that my last upgrade was around mid-July...prior to > > CAM being integrated, so it was all 'hand-patched'...if I upgrade just the > > 'current kernel', I *have* to upgrade the rest, no? I don't want to go > > back to the mid-Jully source tree, since there has been alot of stuff done > > with CAM since then :( > > OK, then stay aout for the initial `make world'. Huh? I didn't think that was a choice? Just do my "usual", consisting of: make buildworld install new config build new kernel install new kernel make installworld and that's it? Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:19:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25998 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:19:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25993 for ; Mon, 19 Oct 1998 15:19:55 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA21603; Tue, 20 Oct 1998 08:21:34 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810192221.IAA21603@cimlogic.com.au> Subject: Re: paranoid question: aout vs ELF... In-Reply-To: from Marc Fournier at "Oct 19, 98 07:15:25 pm" To: marc.fournier@acadiau.ca (Marc Fournier) Date: Tue, 20 Oct 1998 08:21:34 +1000 (EST) Cc: jb@cimlogic.com.au, eculp@webwizard.org.mx, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Fournier wrote: > Huh? I didn't think that was a choice? Just do my "usual", > consisting of: > > make buildworld > install new config > build new kernel > install new kernel > make installworld > > and that's it? Yes, that should still work. If it doesn't, let's fix that problem before you go on. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:21:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26158 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:21:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26134; Mon, 19 Oct 1998 15:21:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01755; Mon, 19 Oct 1998 15:25:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810192225.PAA01755@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sthaug@nethelp.no cc: freebsd-current@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Problems with Digital server with P-166 and Neptune chipset In-reply-to: Your message of "Mon, 19 Oct 1998 23:36:15 +0200." <17857.908832975@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Oct 1998 15:25:00 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problems I see *may* be the fault of the PCI chipset. On > http://www.freebsd.org/handbook/handbook138.html, it says: > > Neptune: > > Can not run more than 2 bus master devices. Admitted Intel design > flaw. Workarounds include do not run more than 2 bus masters, special > hardware design to replace the PCI bus arbiter (appears on Intel > Altair board and several other Intel server group MB's). And of course > Intel's official answer, move to the Triton chip set, we ``fixed it > there''. > > I don't know any more about the Neptune problem than what I've seen on > this Web page. The actual behavior I see is sudden reboots without any > apparent cause - and no messages in the system logs. The system *has* > more than two bus master devices (21140 Ethernet card, two Buslogic > Multimaster SCSI controllers, 7 SCSI disks, SCSI CDROM, SCSI tape). > > On the other hand, Patrick Duffy's "PCI Chipsets" list says about the > Neptune: > > Rev. 1: (problems mentioned) > > Rev. 2: This chipset is in boards shipped by Intel to vendors as of > about mid August 1994. It has no reported problems (and works > well in my system). > > The system I have may be Rev. 2: > > chip0: rev 0x11 on pci0.0.0 > > (/sys/pcisupport.c lists rev 16 and 17 as Neptune - so my guess, without > checking the Intel data sheet, is that I have a Neptune rev. 2 chipset.) > > Any good hints on where I should start looking to find the cause of the > sudden reboots? Well, I'd start by going back to just 2 bus masters for starters. > Oh yeah, the two Buslogic SCSI controllers appear in the kernel config > file as ISA controllers: > > controller bt0 at isa? port ? cam irq ? > controller bt1 at isa? port ? cam irq ? > > but they are very definitely PCI controllers: This may be a leftover from the way the old bt driver used to handle PCI instances. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:22:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26309 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:22:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26304 for ; Mon, 19 Oct 1998 15:22:51 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01775; Mon, 19 Oct 1998 15:26:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810192226.PAA01775@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Masto cc: freebsd-current@FreeBSD.ORG Subject: Re: cvsup and file permissions In-reply-to: Your message of "Mon, 19 Oct 1998 18:05:08 EDT." <19981019180508.A26343@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Oct 1998 15:26:44 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Oct 15, 1998 at 05:28:51PM -0700, Mike Smith wrote: > > > This is something I've kind of been ignoring for a while, but now that > > > I'm tracking current/BETA on a couple more machines, I'd like to solve > > > it. I don't see anything obvious in the manpage. > > > > > > Basically, I maintain one copy of the CVS tree on our big server with > > > cvsup, and use remote CVS+ssh to check stuff out onto other machines. > > > Because CVS needs write access, I have set up a group for the users > > > that have permission to do this sort of thing. The problem is that cvsup > > > keeps taking the group permissions away when it updates the repository. > > > > Use the -R option to cvs when checking out. > > I've gotten around to trying this and it doesn't actually work.. > > chris@lion-around:/tmp/cvstest$ export CVS_RSH=ssh > chris@lion-around:/tmp/cvstest$ cvs -R -d :ext:chris@cheddar:/usr/cvs/freebsd checkout src/tools > cvs server: Updating src/tools > cvs server: failed to create lock directory in repository `/usr/cvs/freebsd/src/tools': Permission denied > cvs server: failed to obtain dir lock in repository `/usr/cvs/freebsd/src/tools' > cvs [server aborted]: read lock failed - giving up > > It does work if I log on to the repository machine and don't use > remote CVS. You need to tell the server side to use readonly mode; you can probably do this if you can set the CVS options on the server side eg. by forwarding your environment across and using the CVS options variable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:24:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26606 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:24:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26601 for ; Mon, 19 Oct 1998 15:24:24 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id SAA00469; Mon, 19 Oct 1998 18:25:49 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Mon, 19 Oct 1998 18:25:49 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: HighWind Software Information cc: John Birrell , current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem In-Reply-To: <199810192045.QAA21744@highwind.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hrm, you are right, i'm looking at the source and seeing if i can grasp what to do. In fact running gdb/ddd on both programs you sent seem to cause deadlock in different parts of the scheduler. Do you have time at all to compile your libc_r with -g? i've eadited my makefile in /usr/src/lib/libc_r to have a line with: # Uncomment this if you want libc_r to contain debug information for # thread locking. CFLAGS+=-D_LOCK_DEBUG -g I'm also interested in the effect of a pthread_cond_signal after a pthread_cond_broadcast, but i have to take care of some important things, i'll look more later tonight. I'll have to take a look at this, I'm also forwarding to John Birrell about this, as it seems to be mostly his code. I think something about scheduling a thread to run causes it to be ran with the SPINLOCK still in place creating deadlock later on. I think queing/scheduling might need a arg list of internal values to lock/unlock on entry/exit. I apologize for discounting your argument earlier, i am new at threads though. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Mon, 19 Oct 1998, HighWind Software Information wrote: > > I believe your test program is in error. Your threads are > not ever going to awake from the pthread_cond_wait() statement > because the mutex cannot be acquired. Your main thread locks > the mutex and never unlocks it. > > I claim that doesn't matter. WHY should the CPU spin if I signal > twice on a lock I have? That is PERFECTLY valid. > > Let's say I want to say that TWO events are ready to be handled. > That is perfectly fine. > > --- > > Simply to placate your claim, here is another version that locks and > unlocks the mutex in proper fashion. I simply had to insert an > additional "sleep" to get the bug to appear. > > In both cases, spinning the CPU at 100% and allowing the program to > hang and make no forward progress is a SERIOUS bug. > > I claim that this new version is 100% valid. Does proper locking, and > also works on other O/S's. On FreeBSD it does not work at all. > > -Rob > > /* This program sets up a conditional wait and fires off a dozen threads that simply wait for the condition. Once the threads are started, the main thread loops signalling the condition once a second. Normally, this should result in "Signalling" and "Got Condition" being printed once a second. However, because of some bugs in FreeBSD, the pthread_cond_wait() spins the CPU and no progress is made. g++ -o condWaitBug -D_REENTRANT -D_THREAD_SAFE -g -Wall condWaitBug.C -pthread */ #include #include #include #include #include pthread_mutex_t lock; pthread_cond_t condition; static void *condThread(void *) { // Wait until we are signalled, then print. while (true) { // Be sure to do proper locking and unlocking assert(!::pthread_mutex_lock(&lock)); assert(!::pthread_cond_wait(&condition, &lock)); ::printf("Got Condition!\n"); assert(!::pthread_mutex_unlock(&lock)); } } int main(int, char **) { // Initialize Lock pthread_mutexattr_t lock_attr; assert(!::pthread_mutexattr_init(&lock_attr)); assert(!::pthread_mutex_init(&lock, &lock_attr)); assert(!::pthread_mutexattr_destroy(&lock_attr)); // Initialize Condition pthread_condattr_t cond_attr; assert(!::pthread_condattr_init(&cond_attr)); assert(!::pthread_cond_init(&condition, &cond_attr)); assert(!::pthread_condattr_destroy(&cond_attr)); // Spawn off a dozen threads to get signalled for (int j = 0; j < 12; ++j) { pthread_t tid; pthread_attr_t attr; assert(!::pthread_attr_init(&attr)); assert(!::pthread_create(&tid, &attr, condThread, 0)); assert(!::pthread_attr_destroy(&attr)); } // Sleep for 3 seconds to make sure the threads started up. timeval timeout; timeout.tv_sec = 3; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); for (int k = 0; k < 60; ++k) { // Signal while locked assert(!::pthread_mutex_lock(&lock)); ::printf("Signalling\n"); assert(!::pthread_cond_signal(&condition)); // Sleep for 1 second timeout.tv_sec = 1; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); ::printf("Signalled again\n"); assert(!::pthread_cond_signal(&condition)); assert(!::pthread_mutex_unlock(&lock)); // Sleep for 1 second timeout.tv_sec = 1; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); } return EXIT_SUCCESS; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:35:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27705 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:35:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA27697 for ; Mon, 19 Oct 1998 15:35:09 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zVNss-0007ng-00; Mon, 19 Oct 1998 16:34:38 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id QAA00210; Mon, 19 Oct 1998 16:34:44 -0600 (MDT) Message-Id: <199810192234.QAA00210@harmony.village.org> To: Julian Elischer Subject: Re: newfs problems, more information: Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Oct 1998 14:03:24 PDT." References: Date: Mon, 19 Oct 1998 16:34:44 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Julian Elischer writes: : Until there is no code in the kernel that says : if (part == RAW_PART) { : some magic occurs; : } : I personally wouldn't use it. A grep of the kernel shows boatloads of cases where 'c' is special... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:37:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27903 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:37:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA27897 for ; Mon, 19 Oct 1998 15:37:34 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zVNut-00001d-00; Mon, 19 Oct 1998 16:36:43 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id QAA00299; Mon, 19 Oct 1998 16:36:50 -0600 (MDT) Message-Id: <199810192236.QAA00299@harmony.village.org> To: Poul-Henning Kamp Subject: Re: vote:? reversion of BDE change please? Cc: current@FreeBSD.ORG reply-to: chat@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Oct 1998 22:51:48 +0200." <20659.908830308@critter.freebsd.dk> References: <20659.908830308@critter.freebsd.dk> Date: Mon, 19 Oct 1998 16:36:49 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20659.908830308@critter.freebsd.dk> Poul-Henning Kamp writes: : [*] probably doing it the bde::wrong_way() Can somebody send me bde.h and bde.cc? :-) Or at the very least bde::filter? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 15:52:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29380 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:52:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nu.binary.net (nu.binary.net [12.13.120.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29375 for ; Mon, 19 Oct 1998 15:52:42 -0700 (PDT) (envelope-from nathan@matrix.binary.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by nu.binary.net (8.9.1a/8.9.0) with ESMTP id RAA28153; Mon, 19 Oct 1998 17:52:17 -0500 (CDT) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id RAA11263; Mon, 19 Oct 1998 17:52:17 -0500 (CDT) Message-ID: <19981019185216.B10530@rtfm.net> Date: Mon, 19 Oct 1998 18:52:17 -0400 From: Nathan Dorfman To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-R, CAM, and audio tracks (more info) References: <19981018234428.A15396@binary.net> <199810190617.AAA21008@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810190617.AAA21008@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Oct 19, 1998 at 12:17:41AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 12:17:41AM -0600, Kenneth D. Merry wrote: > Nathan Dorfman wrote... > > Your CDROM drive didn't like the command that tosha sent. Sounds fishy to me, because it likes the same commands just fine when the track isn't an audio track (significantly reducing tosha's usefulness, however). However, you're Mr. CAM, so if you say it's my drive and not CAM, I guess I'll have to believe you :-) > > After compiling the CAMDEBUG options into my kernel and running > > camcontrol debug -Ic 0:2:0, I got the following: > > > > tosha attempting to read audio track and failing: > > > > (pass1:ahc0:0:2:0): INQUIRY. CDB: 12 0 0 0 40 0 > > (pass1:ahc0:0:2:0): MODE SENSE(06). CDB: 1a 0 1 0 c 0 > > (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > > (pass1:ahc0:0:2:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 0 0 0 0 0 1 8 0 0 > > > > (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 20 0 0 a 0 > > > > tosha attempting to read data track and succeeding: > > > > (pass1:ahc0:0:2:0): INQUIRY. CDB: 12 0 0 0 40 0 > > (pass1:ahc0:0:2:0): MODE SENSE(06). CDB: 1a 0 1 0 c 0 > > (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > > (pass1:ahc0:0:2:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 0 0 0 0 0 1 8 0 0 > > > > (pass1:ahc0:0:2:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 0 0 0 a 0 > > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 a 0 0 a 0 > > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 14 0 0 a 0 > > (pass1:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 0 1e 0 0 a 0 > > ...etc... > > > > Is CAM preventing tosha from reading audio data via passthrough? > > Yes. Justin and I were paid by the RIAA to make sure that FreeBSD users > can't copy audio CDs. The FBI will contact you shortly to discuss whether > or not your use of your CDs constitutes "fair use". Haha :) that's *not* what I meant. Actually, I want to create a CD, for my personal use, that contains my favorite tracks from other discs that I own. Is this "fair use"? No one seemed to mind when everyone did it with tapes. > It looks like your drive doesn't like it when you try to read audio tracks > that way. You may want to talk to Oliver Fromme about it, and see if he's > heard any other bug reports about Yamaha drives not working. IIRC, Daniel > O'Conner had a similar problem with a Yamaha drive. I think he was able to > get it to work with cdda2wav, but he ran into another problem with cdda2wav > that looks like a vm problem related to shared memory. > > I'm not exactly sure what the problem is, but it's most likely related to > tosha's interaction with your drive. I e-mailed Oliver and am still waiting for a response. Meanwhile, is there any way to force the drive to reset to a sane state without rebooting so I can at least use it? I'll KIT if I find any solution/workaround :-/ thanks for your time. > Ken > -- > Kenneth Merry > ken@plutotech.com -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 16:08:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00882 for freebsd-current-outgoing; Mon, 19 Oct 1998 16:08:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nu.binary.net (nu.binary.net [12.13.120.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00868 for ; Mon, 19 Oct 1998 16:08:38 -0700 (PDT) (envelope-from nathan@matrix.binary.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by nu.binary.net (8.9.1a/8.9.0) with ESMTP id SAA28477; Mon, 19 Oct 1998 18:08:14 -0500 (CDT) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id SAA12921; Mon, 19 Oct 1998 18:08:13 -0500 (CDT) Message-ID: <19981019190813.C10530@rtfm.net> Date: Mon, 19 Oct 1998 19:08:13 -0400 From: Nathan Dorfman To: "Kenneth D. Merry" , Andreas Klemm Cc: freebsd-current@FreeBSD.ORG Subject: Re: packet writing ( was Re: 3.0-R, CAM, and audio tracks (more info)) References: <19981019223322.B17441@klemm.gtn.com> <199810192103.PAA25261@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810192103.PAA25261@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Oct 19, 1998 at 03:03:44PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 03:03:44PM -0600, Kenneth D. Merry wrote: > Andreas Klemm wrote... > > > > BTW, what about "packet writing" ? > > I really like this feature in Windoof environment. > > Would there be any possibility to implement this mode > > and to format/fixate by using a sysctl command or such ? > > And this is something that cdrecord won't do? cdrecord is the only > supported way of burning CDs under CAM. > > I may implement a more generic solution through the CD driver at some > point, but it probably won't be anytime soon. cdrecord-1.6 documents an "experimental" packet writing interface. Can someone clue me in as to what this is and the advantages/drawbacks of it? All I've heard about it is my cousin's rant about dragging and dropping to the CD in lose9x I fail to see a good reason for an OS-specific in-kernel CD-R driver, when the cdrecord package works on plenty of systems that have SCSI generic devices (passthrough). Unless I am missing some advantage of having CD burning code in the kernel, this strikes me as a horrible duplication of effort. So, what am I missing and why is this a good idea? :) > Ken > -- > Kenneth Merry > ken@plutotech.com -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 16:19:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01943 for freebsd-current-outgoing; Mon, 19 Oct 1998 16:19:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01914 for ; Mon, 19 Oct 1998 16:19:50 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id RAA26289; Mon, 19 Oct 1998 17:19:20 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810192319.RAA26289@panzer.plutotech.com> Subject: Re: 3.0-R, CAM, and audio tracks (more info) In-Reply-To: <19981019185216.B10530@rtfm.net> from Nathan Dorfman at "Oct 19, 98 06:52:17 pm" To: nathan@rtfm.net (Nathan Dorfman) Date: Mon, 19 Oct 1998 17:19:20 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM908839160-26263-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM908839160-26263-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Nathan Dorfman wrote... > On Mon, Oct 19, 1998 at 12:17:41AM -0600, Kenneth D. Merry wrote: > > Nathan Dorfman wrote... > > > > Your CDROM drive didn't like the command that tosha sent. > > Sounds fishy to me, because it likes the same commands just fine > when the track isn't an audio track (significantly reducing tosha's > usefulness, however). However, you're Mr. CAM, so if you say it's > my drive and not CAM, I guess I'll have to believe you :-) It's actually tosha's interaction with your drive. I'm sure that given the correct commands, it would probably work. The difference between audio and data tracks is probably the density code and sector size you have to set before issuing the read command. > > > Is CAM preventing tosha from reading audio data via passthrough? > > > > Yes. Justin and I were paid by the RIAA to make sure that FreeBSD users > > can't copy audio CDs. The FBI will contact you shortly to discuss whether > > or not your use of your CDs constitutes "fair use". > > Haha :) that's *not* what I meant. Actually, I want to create a CD, > for my personal use, that contains my favorite tracks from other > discs that I own. Is this "fair use"? No one seemed to mind when > everyone did it with tapes. Yes, that's fair use. If you own the CDs in question, I think you can copy them for your own personal use. > > It looks like your drive doesn't like it when you try to read audio tracks > > that way. You may want to talk to Oliver Fromme about it, and see if he's > > heard any other bug reports about Yamaha drives not working. IIRC, Daniel > > O'Conner had a similar problem with a Yamaha drive. I think he was able to > > get it to work with cdda2wav, but he ran into another problem with cdda2wav > > that looks like a vm problem related to shared memory. > > > > I'm not exactly sure what the problem is, but it's most likely related to > > tosha's interaction with your drive. > > I e-mailed Oliver and am still waiting for a response. Meanwhile, is there > any way to force the drive to reset to a sane state without rebooting so I > can at least use it? Try replacing tosha/patches/patch-ab with the attached patch. It should theoretically re-set the density code and sector size to their original values before it exits. I say "theoretically", since tosha works just fine with my Plextor drives, and therefore doesn't exit abnormally. Ken -- Kenneth Merry ken@plutotech.com --ELM908839160-26263-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=tosha-0.05.cam_diffs.981019 Content-Description: tosha-0.05.cam_diffs.981019 Content-Transfer-Encoding: 7bit diff -c ../tosha-0.05/Makefile ./Makefile *** ../tosha-0.05/Makefile Tue May 20 17:57:17 1997 --- ./Makefile Mon Jul 6 16:26:50 1998 *************** *** 19,24 **** --- 19,31 ---- CFLAGS=-O2 -Wall -ansi # CFLAGS=-g -Wall -ansi -pedantic + .if (exists(/usr/include/camlib.h)) + CFLAGS+=-DCAM + LDFLAGS=-lcam + .else + LDFLAGS=-lscsi + .endif + all: tosha pcmplay pcmfade utils.o: utils.c utils.h *************** *** 28,34 **** pcmfade.o: pcmfade.c utils.h tosha: tosha.o utils.o getlopt.o ! $(CC) $(CFLAGS) -o tosha -lscsi tosha.o utils.o getlopt.o pcmplay: pcmplay.o utils.o getlopt.o $(CC) $(CFLAGS) -o pcmplay pcmplay.o utils.o getlopt.o --- 35,41 ---- pcmfade.o: pcmfade.c utils.h tosha: tosha.o utils.o getlopt.o ! $(CC) $(CFLAGS) -o tosha $(LDFLAGS) tosha.o utils.o getlopt.o pcmplay: pcmplay.o utils.o getlopt.o $(CC) $(CFLAGS) -o pcmplay pcmplay.o utils.o getlopt.o diff -c ../tosha-0.05/tosha.c ./tosha.c *** ../tosha-0.05/tosha.c Tue May 20 18:11:49 1997 --- ./tosha.c Mon Oct 19 17:10:41 1998 *************** *** 47,55 **** #include #include #include - #include #include #include extern int errno; /* --- 47,65 ---- #include #include #include #include + #ifdef CAM + #include + #include + #include + #include + #include + #include + #include + #else /* !CAM */ + #include #include + #endif /* !CAM */ extern int errno; /* *************** *** 74,79 **** --- 84,90 ---- * wasn't able to find a better solution. */ + #ifndef CAM #undef SCSIREQ_ERROR #define SCSIREQ_ERROR(SR) (\ 0 \ *************** *** 81,86 **** --- 92,98 ---- || SR->retsts /* SCSI transfer status */ \ || SR->error /* copy of errno */ \ ) + #endif /* * Uncommenting this define will cause a LOT of output. *************** *** 95,102 **** --- 107,119 ---- typedef unsigned char byte; typedef unsigned long ulong; + #ifdef CAM + union ccb *ccb; + struct cam_device *cam_dev; + #else /* !CAM */ struct scsireq *sreq; /* SCSI device request structure */ int scsifd; /* SCSI device file descriptor */ + #endif /* !CAM */ int readcmd = 0x28; /* read command to use for DA reading */ int byteswap = FALSE; /* do we have to swap byte order? */ *************** *** 126,131 **** --- 143,176 ---- { int result; + #ifdef CAM + bzero(&(&ccb->ccb_h)[1], sizeof(struct ccb_scsiio)); + csio_build(&ccb->csio, + /* data_ptr */ (u_int8_t *)buf, + /* dxfer_len */ size, + /* flags */ flags, + /* retry_count */ 1, + /* timeout */ 10000, + /* cmd_spec */ cmd); + + if ((result = cam_send_ccb(cam_dev, ccb)) < 0) { + perror("error sending SCSI command"); + cam_freeccb(ccb); + cam_close_device(cam_dev); + exit(1); + } + if ((ccb->ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_CMP) { + fprintf(stderr, "error returned from SCSI command:\n"); + if ((ccb->ccb_h.status & CAM_STATUS_MASK) == + CAM_SCSI_STATUS_ERROR) + scsi_sense_print(cam_dev, &ccb->csio, stderr); + else + fprintf(stderr, "ccb->ccb_h.status == %d\n", + ccb->ccb_h.status); + + exit(1); + } + #else /* !CAM */ scsireq_reset (sreq); sreq->timeout = 10000; scsireq_build (sreq, size, (char *) buf, flags, cmd); *************** *** 134,139 **** --- 179,185 ---- if (SCSIREQ_ERROR (sreq)) #endif scsi_debug (stderr, result, sreq); + #endif /* !CAM */ return (result); } *************** *** 144,150 **** --- 190,202 ---- void get_density (int *density, int *secsize) { + #ifdef CAM + simple_request (12, CAM_DIR_IN | + CAM_DEV_QFRZDIS | + CAM_PASS_ERR_RECOVER, "1A 0 1 0 C 0"); + #else /* !CAM */ simple_request (12, SCCMD_READ, "1A 0 1 0 C 0"); + #endif /* !CAM */ *density = buf[4]; *secsize = buf[10] << 8 | buf[11]; } *************** *** 161,167 **** --- 213,225 ---- buf[4] = density; buf[10] = secsize >> 8; buf[11] = secsize & 0xff; + #ifdef CAM + simple_request (12, CAM_DIR_OUT | + CAM_DEV_QFRZDIS | + CAM_PASS_ERR_RECOVER, "15 10 0 0 C 0"); + #else /* !CAM */ simple_request (12, SCCMD_WRITE, "15 10 0 0 C 0"); + #endif /* !CAM */ } /* *************** *** 386,391 **** --- 444,489 ---- for (sec = start; sec < endpp; sec += secread) { if ((secread = framesperbuf) > endpp - sec) secread = endpp - sec; + + #ifdef CAM + if (readcmd == 0xd8) + csio_build(&ccb->csio, + /* data_ptr */ (u_int8_t *)buf, + /* dxfer_len */ FRAMESIZE * secread, + /* flags */ CAM_DIR_IN, + /* retries */ 1, + /* timeout */ 10000, + /* cmd_spec */ "v 0 0 v:i3 0 0 0 v 0 0", + readcmd, sec, secread); + else + csio_build(&ccb->csio, + /* data_ptr */ (u_int8_t *)buf, + /* dxfer_len */ FRAMESIZE * secread, + /* flags */ CAM_DIR_IN, + /* retries */ 1, + /* timeout */ 10000, + /* cmd_spec */ "v 0 0 v:i3 0 0 v 0", + readcmd, sec, secread ); + + if ((result = cam_send_ccb(cam_dev, ccb)) < 0) { + perror("error sending CD-DA read command"); + return(FALSE); + } + + if ((ccb->ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_CMP) { + fprintf(stderr, "error returned from CD-DA" + " read command:\n"); + if ((ccb->ccb_h.status & CAM_STATUS_MASK) == + CAM_SCSI_STATUS_ERROR) + scsi_sense_print(cam_dev, &ccb->csio, stderr); + else + fprintf(stderr, "ccb->ccb_h.status == %d\n", + ccb->ccb_h.status); + + return(FALSE); + } + #else /* !CAM */ + scsireq_reset (sreq); sreq->timeout = 10000; if (readcmd == 0xd8) *************** *** 403,408 **** --- 501,507 ---- if (SCSIREQ_ERROR (sreq)) #endif scsi_debug (stderr, result, sreq); + #endif /* !CAM */ if (byteswap) { int j, num = FRAMESIZE * secread; byte t; *************** *** 460,465 **** --- 559,565 ---- char *vendor, *product, *versid; char *ofname; /* output file name */ int density, sectorsize; + int exit_val = 0; int index; int singlefile = FALSE; int modechange = TRUE, denschange = 0; *************** *** 497,514 **** * Open SCSI device and initialize SCSI request structure. */ if ((scsifd = scsi_open(device, O_RDWR)) == -1) die (device); if (!(sreq = scsireq_new())) { fprintf (stderr, "%s: scsireq_new(): Out of memory.\n", me); exit (1); } ! /* * Get vendor & product IDs. */ simple_request (64, SCCMD_READ, "12 0 0 0 40 0"); vendor = justify(strndup((char *) buf+8, 8)); product = justify(strndup((char *) buf+16, 16)); versid = justify(strndup((char *) buf+32, 4)); --- 597,630 ---- * Open SCSI device and initialize SCSI request structure. */ + #ifdef CAM + if ((cam_dev = cam_open_device(device, O_RDWR)) == NULL) { + fprintf(stderr, "%s: %s\n", me, cam_errbuf); + exit(1); + } + if ((ccb = cam_getccb(cam_dev)) == NULL) { + fprintf(stderr, "%s: couldn't allocate CCB\n", me); + exit(1); + } + #else /* !CAM */ if ((scsifd = scsi_open(device, O_RDWR)) == -1) die (device); if (!(sreq = scsireq_new())) { fprintf (stderr, "%s: scsireq_new(): Out of memory.\n", me); exit (1); } ! #endif /* !CAM */ /* * Get vendor & product IDs. */ + #ifdef CAM + simple_request(64, CAM_DIR_IN | + CAM_DEV_QFRZDIS | + CAM_PASS_ERR_RECOVER, "12 0 0 0 40 0"); + #else /* !CAM */ simple_request (64, SCCMD_READ, "12 0 0 0 40 0"); + #endif /* !CAM */ vendor = justify(strndup((char *) buf+8, 8)); product = justify(strndup((char *) buf+16, 16)); versid = justify(strndup((char *) buf+32, 4)); *************** *** 571,577 **** --- 687,700 ---- * Get table of contents. */ + #ifdef CAM + if (simple_request (2048, CAM_DIR_IN | + CAM_DEV_QFRZDIS | + CAM_PASS_ERR_RECOVER, + "43 0 0 0 0 0 1 8 0 0")) { + #else /* !CAM */ if (simple_request (2048, SCCMD_READ, "43 0 0 0 0 0 1 8 0 0")) { + #endif /* !CAM */ fprintf (stderr, "%s: Can't read table of contents.\n", me); exit (1); } *************** *** 631,638 **** print_trackinfo (-1, 1, startsec, endsec); fprintf (stderr, " Reading ...\r"); } ! if (!indexonly) ! readsectors (startsec, endsec, pcmfd); } else { for (index = 0; index < tracklistsize; index++) { --- 754,765 ---- print_trackinfo (-1, 1, startsec, endsec); fprintf (stderr, " Reading ...\r"); } ! if (!indexonly) { ! if (readsectors(startsec, endsec, pcmfd) == FALSE) { ! exit_val = 1; ! goto error_exit; ! } ! } } else { for (index = 0; index < tracklistsize; index++) { *************** *** 657,663 **** O_TRUNC, 0644)) < 0) die ("open(output file)"); } ! readsectors (trackstart[i], trackstart[i + 1], pcmfd); if (!singlefile) close (pcmfd); } --- 784,794 ---- O_TRUNC, 0644)) < 0) die ("open(output file)"); } ! if (readsectors(trackstart[i], ! trackstart[i + 1], pcmfd) == FALSE) { ! exit_val = FALSE; ! goto error_exit; ! } if (!singlefile) close (pcmfd); } *************** *** 687,697 **** /* * Set original density code and sector size. */ set_density (density, sectorsize); close (scsifd); ! exit (0); } /* EOF */ --- 818,835 ---- /* * Set original density code and sector size. */ + error_exit: set_density (density, sectorsize); + #ifdef CAM + cam_freeccb(ccb); + + cam_close_device(cam_dev); + #else /* !CAM */ close (scsifd); ! #endif /* !CAM */ ! exit (exit_val); } /* EOF */ --ELM908839160-26263-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 16:24:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02967 for freebsd-current-outgoing; Mon, 19 Oct 1998 16:24:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02957 for ; Mon, 19 Oct 1998 16:24:05 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA05729; Mon, 19 Oct 1998 16:19:19 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdcP5727; Mon Oct 19 23:19:18 1998 Date: Mon, 19 Oct 1998 16:19:13 -0700 (PDT) From: Julian Elischer To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: vote:? reversion of BDE change please? In-Reply-To: <199810192048.NAA01214@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess I'll change the drivers in quiestion to simply register their own intrrupt handlers.. as Justin says he has examples I'll go look there.. On Mon, 19 Oct 1998, Mike Smith wrote: > > > > A while ago bruce changed config(8) to not create the prototypes of > > the interrupt handlers in the generated file ioconf.h. > > > > I don't understand his reasoning but it causes me quite a bit of grief. > > He now has the rather odd idea that all device drivers should have their > > interrupt handlers prototyped in isa_device.h. How isa_device.h is > > supposed to know about al existing 3rd party drivers is apparenlty left as > > an exercise for the reader.... > > > > This is 'odd' in my opinion because that means that if i want to > > add a device driver I need to edit isa_device.h and add an entry for it. > > I think this goes in the oposite direction from being able to add drivers > > easily to the system. > > The change is actually in the right direction, as the goal is to remove > the prototypes from global scope completely. Instead, ISA device > drivers should register their interrupt handlers at attach time. I > don't know if there's an example of this at the present time. > > > Particularly I'd like to know if it breaks tha alpha port, or > > the new device framework? > > As it is now it certainly breaks several automatic build processes I know > > of (including the /usr/share/examples/drivers scripts) > > IMHO, the followup changes have been too slow coming. The new bus > framework should completely obsolete interrupt handler prototypes, > which may explain the pedestrian pace of the followups. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 16:27:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03167 for freebsd-current-outgoing; Mon, 19 Oct 1998 16:27:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03159; Mon, 19 Oct 1998 16:27:19 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by ns1.aha.ru (8.9.1/8.9.1/aha-r/0.04B) with ESMTP id DAA19358; Tue, 20 Oct 1998 03:26:54 +0400 (MSD) Received: by sunny.aha.ru id DAA06603; (8.8.8/vak/1.9) Tue, 20 Oct 1998 03:26:27 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma006566; Tue Oct 20 03:26:00 1998 Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by serv.etrust.ru (8.9.1/8.9.1) with ESMTP id DAA17817; Tue, 20 Oct 1998 03:25:30 +0400 (MSD) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id DAA00564; Tue, 20 Oct 1998 03:26:04 +0400 (MSD) (envelope-from osa@etrust.ru) Date: Tue, 20 Oct 1998 03:26:03 +0400 (MSD) From: oZZ!!! To: freebsd-current@FreeBSD.ORG cc: freebsd-ports@FreeBSD.ORG Subject: netscape-4.07 is dead ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I want to report about problem with netscape4-communicator from ports. Today i reinstall XFree86-3.3.2.3-ELF with aout-Xlibs for my FreeBSD-3.0-ELF. After successfully install NN-4.07 (from ports) : $ netscape Bus error What does it mean & what can i do? Rgdz, ïÓÏËÉÎ óÅÒÇÅÊ aka oZZ, osa@etrust.ru FreeBSD - äÁ ÐÒÅÂÕÄÅÔ Ó ÎÁÍÉ ÓÉÌÁ! áÓÓÏÃÉÁÃÉÑ ÒÕÓÓËÏÑÚÙÞÎÙÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ FreeBSD http://www.freebsd.org.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 16:31:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03555 for freebsd-current-outgoing; Mon, 19 Oct 1998 16:31:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03549 for ; Mon, 19 Oct 1998 16:31:23 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id RAA26343; Mon, 19 Oct 1998 17:30:46 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810192330.RAA26343@panzer.plutotech.com> Subject: Re: packet writing ( was Re: 3.0-R, CAM, and audio tracks (more info)) In-Reply-To: <19981019190813.C10530@rtfm.net> from Nathan Dorfman at "Oct 19, 98 07:08:13 pm" To: nathan@rtfm.net (Nathan Dorfman) Date: Mon, 19 Oct 1998 17:30:46 -0600 (MDT) Cc: andreas@klemm.gtn.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nathan Dorfman wrote... > On Mon, Oct 19, 1998 at 03:03:44PM -0600, Kenneth D. Merry wrote: > > Andreas Klemm wrote... > > > > > > BTW, what about "packet writing" ? > > > I really like this feature in Windoof environment. > > > Would there be any possibility to implement this mode > > > and to format/fixate by using a sysctl command or such ? > > > > And this is something that cdrecord won't do? cdrecord is the only > > supported way of burning CDs under CAM. > > > > I may implement a more generic solution through the CD driver at some > > point, but it probably won't be anytime soon. > > cdrecord-1.6 documents an "experimental" packet writing interface. Can > someone clue me in as to what this is and the advantages/drawbacks of it? > All I've heard about it is my cousin's rant about dragging and dropping > to the CD in lose9x I dunno anything about it. > I fail to see a good reason for an OS-specific in-kernel CD-R driver, > when the cdrecord package works on plenty of systems that have SCSI > generic devices (passthrough). Unless I am missing some advantage of > having CD burning code in the kernel, this strikes me as a horrible > duplication of effort. So, what am I missing and why is this a good > idea? :) Well, in many ways it is a duplication of effort. It would be nice to have the capability to write CD-RW and DVD disks incrementally through a filesystem-type interface. To do that, you'd need filesystem support (probably), but also driver-level support for writing to CDs or DVDs. My guess is that "packet writing" lets you write incrementally to CDs, and that your cousin's Win95 box is doing it through a filesystem type interface. In fact, in the cdrecord README, Joerg Schilling seems to indicate that there's a filesystem available for Solaris that does something like that. For now, though, cdrecord seems to do a good job of burning CDs. If I do get around to writing driver-level support for writeable CD-type devices, I doubt I'll support all of the devices cdrecord supports. So there will probably be a need for it even then. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 16:36:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03947 for freebsd-current-outgoing; Mon, 19 Oct 1998 16:36:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03941 for ; Mon, 19 Oct 1998 16:36:46 -0700 (PDT) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id TAA28117; Mon, 19 Oct 1998 19:34:16 -0400 (EDT) (envelope-from mark) Message-ID: <19981019193416.A28045@vmunix.com> Date: Mon, 19 Oct 1998 19:34:16 -0400 From: Mark Mayo To: Mike Smith , Terry Lambert Cc: dg@root.com, green@zone.syracuse.NET, grog@lemis.com, julian@whistle.com, bag@sinbin.demos.su, rock@cs.uni-sb.de, current@FreeBSD.ORG Subject: Re: -current NFS problem References: <199810182048.NAA10205@usr07.primenet.com> <199810182142.OAA14283@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199810182142.OAA14283@dingo.cdrom.com>; from Mike Smith on Sun, Oct 18, 1998 at 02:42:56PM -0700 X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 18, 1998 at 02:42:56PM -0700, Mike Smith wrote: > > Has anyone asked Rick Macklem about this? > > Rick bowed out of the NFS game a long time ago. Kirk would be a better > bet. > > We do actually have an indirect contact with Rick via Mark Mayo, and > he's lukewarm at best about doing anything with his old code, let alone > talking about it. I do see Rick from time to time at the bar, so if anybody has *specific* questions about things in the NFS code I can always group them up and go over things with Rick in person. He's pretty much "inaccessable" via email, but in person he occasionally gets interested and reveals some nuggets of information. :-) In general, he's not interested in helping FreeBSD in any way, since he thinks the code has become too "polluted" and "complicated" now. (which I would disagree with.. initial inspection by myself a while ago suggested that not much at all has really changed..) At any rate, if you find problems with *Rick's* code, I'd bet he'll fix it, if he still remembers any of it.. :-) As for any other help, as I said, give me a list of specific questions and I'll do my best to get answers. -Mark > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark ------------------------------------------------------------------------ "The Church says the earth is flat. But I know it's round, for I have seen the shadow on the moon. And I have more faith in a shadow than in the Church." - Ferdinand Magellan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 16:37:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04006 for freebsd-current-outgoing; Mon, 19 Oct 1998 16:37:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04001 for ; Mon, 19 Oct 1998 16:37:51 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id RAA26400; Mon, 19 Oct 1998 17:37:22 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810192337.RAA26400@panzer.plutotech.com> Subject: Re: 3.0-R, CAM, and audio tracks In-Reply-To: from John Fieber at "Oct 19, 98 09:12:30 am" To: jfieber@indiana.edu (John Fieber) Date: Mon, 19 Oct 1998 17:37:22 -0600 (MDT) Cc: nathan@rtfm.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Fieber wrote... > On Mon, 19 Oct 1998, Kenneth D. Merry wrote: > > > > I've never been able to get decent audio dumps from my Toshiba > > > 3501 using tosha (or anything else for that matter), > > > > Do you mean "never" as in "not with CAM" or never as in "not with CAM or > > the old SCSI subsystem"? > > The latter. With the old SCSI system, the audio would come out > with lots of pops, clicks and dropouts and I sometimes had to > re-boot to regain use of the CD-ROM drive. I suspect this drive > hase some sort of "quirk". Probably so. Perhaps cdd or cdda2wav would work better with it. (there isn't an 'official' CAM port of either at the moment, though) You may want to try the patch I sent to Nathan Dorfman for tosha. It sets the drive parameters back to their previous settings when it exits abnormally. So, at least your drive settings wouldn't get hosed, if that's happening now. > > That's not good. Were there any interesting error messages? > > I neglected to write them down and naturally they didn't make it > into /var/log/messages since the whole SCSI subsystem was wedged. > > I'm sure I could duplicate the experience though.... Well, if you'd like to do it, go for it. It might help if you setup a serial console. You wouldn't have to write things down. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 17:00:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06122 for freebsd-current-outgoing; Mon, 19 Oct 1998 17:00:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06116 for ; Mon, 19 Oct 1998 17:00:57 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA03335; Mon, 19 Oct 1998 17:00:32 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd003265; Mon Oct 19 17:00:23 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id RAA19037; Mon, 19 Oct 1998 17:00:13 -0700 (MST) From: Terry Lambert Message-Id: <199810200000.RAA19037@usr02.primenet.com> Subject: Re: -current NFS problem To: mark@vmunix.com (Mark Mayo) Date: Tue, 20 Oct 1998 00:00:12 +0000 (GMT) Cc: mike@smith.net.au, tlambert@primenet.com, dg@root.com, green@zone.syracuse.NET, grog@lemis.com, julian@whistle.com, bag@sinbin.demos.su, rock@cs.uni-sb.de, current@FreeBSD.ORG In-Reply-To: <19981019193416.A28045@vmunix.com> from "Mark Mayo" at Oct 19, 98 07:34:16 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Has anyone asked Rick Macklem about this? > > > > Rick bowed out of the NFS game a long time ago. Kirk would be a better > > bet. [ ... ] > In general, he's not interested in helping FreeBSD in any way, since > he thinks the code has become too "polluted" and "complicated" now. > (which I would disagree with.. initial inspection by myself a while > ago suggested that not much at all has really changed..) I'd agree with him, starting with the "cookie" for VOP_READDIR. > As for any other help, as I said, give me a list of specific questions > and I'll do my best to get answers. I think if we get one shot at this, the list of questions should be agreed upon. My main question would be: o Do you see any reason why nfsnode locking should be necessary? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 17:16:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09910 for freebsd-current-outgoing; Mon, 19 Oct 1998 17:16:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09875 for ; Mon, 19 Oct 1998 17:16:48 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id BAA24945; Tue, 20 Oct 1998 01:15:17 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id AAA01757; Tue, 20 Oct 1998 00:27:44 +0200 (CEST) (envelope-from andreas) Message-ID: <19981020002744.B1458@klemm.gtn.com> Date: Tue, 20 Oct 1998 00:27:44 +0200 From: Andreas Klemm To: "Kenneth D. Merry" Cc: nathan@rtfm.net, freebsd-current@FreeBSD.ORG Subject: Re: packet writing ( was Re: 3.0-R, CAM, and audio tracks (more info)) References: <19981019223322.B17441@klemm.gtn.com> <199810192103.PAA25261@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810192103.PAA25261@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Oct 19, 1998 at 03:03:44PM -0600 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 2.2.7-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 03:03:44PM -0600, Kenneth D. Merry wrote: > Andreas Klemm wrote... > > On Mon, Oct 19, 1998 at 12:17:41AM -0600, Kenneth D. Merry wrote: > > > Nathan Dorfman wrote... > > > > BTW, what about "packet writing" ? > > I really like this feature in Windoof environment. > > Would there be any possibility to implement this mode > > and to format/fixate by using a sysctl command or such ? > > And this is something that cdrecord won't do? cdrecord is the only > supported way of burning CDs under CAM. > > I may implement a more generic solution through the CD driver at some > point, but it probably won't be anytime soon. Ok. thanks. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 17:30:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11241 for freebsd-current-outgoing; Mon, 19 Oct 1998 17:30:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11170 for ; Mon, 19 Oct 1998 17:30:00 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id RAA00367; Mon, 19 Oct 1998 17:28:06 -0700 (PDT) Message-ID: <19981019172806.A353@nuxi.com> Date: Mon, 19 Oct 1998 17:28:06 -0700 From: "David O'Brien" To: Marc Fournier Cc: freebsd-current@FreeBSD.ORG Subject: Re: paranoid question: aout vs ELF... Reply-To: obrien@NUXI.com References: <199810192208.IAA21546@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Marc Fournier on Mon, Oct 19, 1998 at 07:15:25PM -0300 X-Operating-System: FreeBSD 2.2.7-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > OK, then stay aout for the initial `make world'. > > Huh? I didn't think that was a choice? Very. All three of my 3.0-CURRENT boxes are still a.out. I won't do E-day until the ports are in better E shape. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 17:32:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11521 for freebsd-current-outgoing; Mon, 19 Oct 1998 17:32:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11516 for ; Mon, 19 Oct 1998 17:32:46 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id RAA00394; Mon, 19 Oct 1998 17:32:16 -0700 (PDT) Message-ID: <19981019173216.B353@nuxi.com> Date: Mon, 19 Oct 1998 17:32:16 -0700 From: "David O'Brien" To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: packet writing ( was Re: 3.0-R, CAM, and audio tracks (more info)) Reply-To: obrien@NUXI.com References: <19981019190813.C10530@rtfm.net> <199810192330.RAA26343@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810192330.RAA26343@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Oct 19, 1998 at 05:30:46PM -0600 X-Operating-System: FreeBSD 2.2.7-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In fact, in the cdrecord README, Joerg Schilling seems to indicate that > there's a filesystem available for Solaris that does something like that. AFAIK (I've used cdrecord on Solaris) that only has the functionality of our `vn' driver. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 18:03:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14497 for freebsd-current-outgoing; Mon, 19 Oct 1998 18:03:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from orkan.canonware.com (canonware.com [206.184.206.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14486 for ; Mon, 19 Oct 1998 18:03:05 -0700 (PDT) (envelope-from jasone@canonware.com) Received: from localhost (jasone@localhost) by orkan.canonware.com (8.8.7/8.8.7) with SMTP id SAA08966; Mon, 19 Oct 1998 18:03:23 -0700 Date: Mon, 19 Oct 1998 18:03:22 -0700 (PDT) From: Jason Evans To: HighWind Software Information cc: current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem In-Reply-To: <199810191835.OAA20137@highwind.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, your test case is very similar to some code that was causing deadlock for me. However, I boiled it down to the following code as being the actual bug. We may be seeing the same thing (but maybe not; I haven't had time to dig into this all the way). Jason Jason Evans Email: [jasone@canonware.com] Web: [http://www.canonware.com/~jasone] Home phone: [(650) 856-8204] Work phone: [(415) 808-8742] Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] ======================== /* -*-mode:c-*- */ #ifndef _REENTRANT # define _REENTRANT #endif #include #include #include #include #include int main() { pthread_mutex_t mutex; int error; error = pthread_mutex_init(&mutex, NULL); if (error) { fprintf(stderr, "Error in pthread_mutex_init(): %s\n", strerror(error)); exit(1); } fprintf(stderr, "About to lock mutex first time.\n"); error = pthread_mutex_lock(&mutex); if (error) { fprintf(stderr, "Error in pthread_mutex_lock(): %s\n", strerror(error)); exit(1); } fprintf(stderr, "About to lock mutex second time; expect deadlock.\n"); error = pthread_mutex_lock(&mutex); if (error) { fprintf(stderr, "Error in pthread_mutex_lock(): %s\n", strerror(error)); exit(1); } fprintf(stderr, "Wow, no deadlock.\n"); error = pthread_mutex_destroy(&mutex); if (error) { fprintf(stderr, "Error in pthread_mutex_destroy(): %s\n", strerror(error)); exit(1); } return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 18:10:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15506 for freebsd-current-outgoing; Mon, 19 Oct 1998 18:10:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15499 for ; Mon, 19 Oct 1998 18:10:39 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id TAA25658; Mon, 19 Oct 1998 19:10:00 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id TAA08488; Mon, 19 Oct 1998 19:09:59 -0600 Date: Mon, 19 Oct 1998 19:09:59 -0600 Message-Id: <199810200109.TAA08488@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: vote:? reversion of BDE change please? In-Reply-To: <20659.908830308@critter.freebsd.dk> References: <199810192048.NAA01214@dingo.cdrom.com> <20659.908830308@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >The change is actually in the right direction, as the goal is to remove > >the prototypes from global scope completely. Instead, ISA device > >drivers should register their interrupt handlers at attach time. I > >don't know if there's an example of this at the present time. > > I think some of the pccard stuff does it [*] Nope, they do it 'wrong', but it happens to work. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 18:25:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17067 for freebsd-current-outgoing; Mon, 19 Oct 1998 18:25:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silverback.gorilla.net (silverback.gorilla.net [208.128.8.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA17053 for ; Mon, 19 Oct 1998 18:25:32 -0700 (PDT) (envelope-from tom@gorilla.net) Received: from peeper.TOJ.org [208.143.84.60] by silverback.gorilla.net with ESMTP (SMTPD32-4.07) id A56A1BA0088; Mon, 19 Oct 1998 20:20:42 CDT Received: (from tom@localhost) by peeper.TOJ.org (8.9.1/8.8.8) id UAA03538 for freebsd-current@freebsd.org; Mon, 19 Oct 1998 20:25:30 -0500 (CDT) (envelope-from tom) Message-ID: <19981019202448.A3534@TOJ.org> Date: Mon, 19 Oct 1998 20:24:48 -0500 From: Tom Jackson To: FreeBSD Current Subject: Howto boot0 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How do you manually install boot0 to test it? May be somewhere, sorry if I missed it. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 18:36:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18751 for freebsd-current-outgoing; Mon, 19 Oct 1998 18:36:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18743 for ; Mon, 19 Oct 1998 18:36:06 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA10499 for ; Tue, 20 Oct 1998 11:05:39 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA00729; Tue, 20 Oct 1998 11:05:21 +0930 (CST) Message-ID: <19981020110520.E433@freebie.lemis.com> Date: Tue, 20 Oct 1998 11:05:20 +0930 From: Greg Lehey To: freebsd-current@FreeBSD.ORG Subject: Re: can't get vinum to work References: <19981018215221.A27539@top.worldcontrol.com> <19981019143824.G4015@freebie.lemis.com> <19981019032916.A27956@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981019032916.A27956@top.worldcontrol.com>; from brian@worldcontrol.com on Mon, Oct 19, 1998 at 03:29:16AM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 19 October 1998 at 3:29:16 -0700, brian@worldcontrol.com wrote: > On Mon, Oct 19, 1998 at 02:38:24PM +0930, Greg Lehey wrote: >> I suspect your real problem is that /dev/da1h and /dev/da2h are set >> with file system type 4.2BSD. This is appropriate for making UFS file >> systems, and for some obscure reason ccd requires it, but it's a >> sure-fire recipe for shooting yourself in the foot. Vinum will >> ultimately require a file system type 'vinum', but currently it >> insists on 'unused'. > > My troubles seem to be more basic and probably unrelated to vinum. > > A simple 'disklabel -e da1' brings up the editor screen with > a very reasonable set of numbers. Exiting the editor results in an: > > label: Operation not supported by device > > and a pair of messages in /var/log/messages: > > Oct 19 03:26:40 bls2 /kernel: da1: cannot find label (no disk label) > Oct 19 03:26:40 bls2 /kernel: da1s1: cannot find label (no disk label) > > I resupped and issued a make world just in case there is some > out-of-syncness someplace. No, this looks like a brand new disk. The easiest way to write the original disk label is probably with /stand/sysinstall. Choose the partition editor and write the partition information with the 'w' command. > I may have forgotten the mention the system is SMP. That doesn't make any difference yet. We have seen some problems with SMP, but we're not sure where they're coming from and whether it's relevant that it's an SMP system. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 19:19:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23624 for freebsd-current-outgoing; Mon, 19 Oct 1998 19:19:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23617 for ; Mon, 19 Oct 1998 19:19:12 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id TAA18294; Mon, 19 Oct 1998 19:18:39 -0700 (PDT) (envelope-from jdp) Message-Id: <199810200218.TAA18294@austin.polstra.com> To: mike@smith.net.au Subject: Re: Bogus world build results? In-Reply-To: <199810192058.NAA01298@dingo.cdrom.com> References: <199810192058.NAA01298@dingo.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Mon, 19 Oct 1998 19:18:39 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199810192058.NAA01298@dingo.cdrom.com>, Mike Smith wrote: > >>> aout make world completed on Mon Oct 19 13:43:00 PDT 1998 > azaria:/usr/src>file `which ls` > /bin/ls: FreeBSD/i386 compact demand paged executable > azaria:/usr/src>objformat > elf > > Something appears to have spagged $OBJFORMAT halfway through the build, > resulting in an a.out world being built. This is -current as of about > 1pm PST today. Just as a point of reference, I built world (ELF) from almost exactly the same sources today, without seeing any problems. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 19:29:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24348 for freebsd-current-outgoing; Mon, 19 Oct 1998 19:29:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eterna.binary.net (eterna.binary.net [12.13.120.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24342 for ; Mon, 19 Oct 1998 19:29:42 -0700 (PDT) (envelope-from nathan@matrix.binary.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id VAA17905; Mon, 19 Oct 1998 21:28:27 -0500 (CDT) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id VAA04093; Mon, 19 Oct 1998 21:29:02 -0500 (CDT) Message-ID: <19981019222902.A2666@rtfm.net> Date: Mon, 19 Oct 1998 22:29:02 -0400 From: Nathan Dorfman To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-R, CAM, and audio tracks (more info) References: <19981019185216.B10530@rtfm.net> <199810192319.RAA26289@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810192319.RAA26289@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Oct 19, 1998 at 05:19:20PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The author of tosha has just gotten back to me, and apparently support for the 4260RW has been added in the latest revision. I checked out the current tosha from the author's anonymous cvs repository and it seems to work fine. It also integrates KDM's CAM patches. Ken, thanks for your time and help. I've also forwarded your patch to reset the CD device to the author. -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 19:35:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24781 for freebsd-current-outgoing; Mon, 19 Oct 1998 19:35:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24774 for ; Mon, 19 Oct 1998 19:35:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA03287; Mon, 19 Oct 1998 19:37:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810200237.TAA03287@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Bogus world build results? In-reply-to: Your message of "Mon, 19 Oct 1998 19:18:39 PDT." <199810200218.TAA18294@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Oct 1998 19:37:15 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <199810192058.NAA01298@dingo.cdrom.com>, > Mike Smith wrote: > > > >>> aout make world completed on Mon Oct 19 13:43:00 PDT 1998 > > azaria:/usr/src>file `which ls` > > /bin/ls: FreeBSD/i386 compact demand paged executable > > azaria:/usr/src>objformat > > elf > > > > Something appears to have spagged $OBJFORMAT halfway through the build, > > resulting in an a.out world being built. This is -current as of about > > 1pm PST today. > > Just as a point of reference, I built world (ELF) from almost > exactly the same sources today, without seeing any problems. A complete extermination of the entire source and object tree fixed it; sounds like unexpected pollution or cosmic rays. Still, it was pretty weird. 8/ -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 19:59:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26930 for freebsd-current-outgoing; Mon, 19 Oct 1998 19:59:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26901 for ; Mon, 19 Oct 1998 19:59:28 -0700 (PDT) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id MAA14472; Tue, 20 Oct 1998 12:59:01 +1000 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma014468; Tue, 20 Oct 98 12:58:37 +1000 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id MAA05563 for ; Tue, 20 Oct 1998 12:58:37 +1000 From: "John Saunders" To: Subject: RE: packet writing Date: Tue, 20 Oct 1998 12:58:36 +1000 Message-ID: <003001bdfbd5$88164a90$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <199810192330.RAA26343@panzer.plutotech.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > cdrecord-1.6 documents an "experimental" packet writing interface. Can > > someone clue me in as to what this is and the advantages/drawbacks of it? > > All I've heard about it is my cousin's rant about dragging and dropping > > to the CD in lose9x > > I dunno anything about it. Basically packet writing allows you to stop, then re-start, the burn mid track. However when you do this you end up with a few sectors of junk while the laser is stopping and starting. You can then use this feature however you like. Most Windows software are split into fixed packet length and variable packet length methods. The variable packet length writes data continuously until there is no more to write. The fixed packet method breaks all writes up into packets equal to the size of the CDR drives buffer. With fixed size packets you can never underrun, with variable sized packets you can. With fixed sized packets you end of with "junk" sectors mid file, with variable length packets the "junk" sectors are between the files. However to make use of this you need a filesystem able to deal with WORM like media. Each time a file is written or modified a new copy of the file is written to the end of the media. Then a new copy of the directory structure is written to the end of the disk that links to the new file. If a file is deleted then only the directory structure is re-written. The "standard" filesystem for packet writing is called UDF. The spec for it is available from the usual standards bodies. However it's likely that a filesystem supporting a WORM drive will work just as well. > > I fail to see a good reason for an OS-specific in-kernel CD-R driver, > > when the cdrecord package works on plenty of systems that have SCSI > > generic devices (passthrough). Unless I am missing some advantage of > > having CD burning code in the kernel, this strikes me as a horrible > > duplication of effort. So, what am I missing and why is this a good > > idea? :) > > Well, in many ways it is a duplication of effort. It would be > nice to have > the capability to write CD-RW and DVD disks incrementally through a > filesystem-type interface. To do that, you'd need filesystem support > (probably), but also driver-level support for writing to CDs or DVDs. My > guess is that "packet writing" lets you write incrementally to CDs, and > that your cousin's Win95 box is doing it through a filesystem type > interface. For packet writing you could probably get away with just supporting SCSI3/mmc compatible drives. But unless there is some ability to have a user space filesystems (like GNU Hurd) then it will have to be in the kernel. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 20:59:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01847 for freebsd-current-outgoing; Mon, 19 Oct 1998 20:59:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01834 for ; Mon, 19 Oct 1998 20:59:29 -0700 (PDT) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id NAA18254; Tue, 20 Oct 1998 13:59:03 +1000 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma018232; Tue, 20 Oct 98 13:58:50 +1000 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id NAA05981 for ; Tue, 20 Oct 1998 13:58:41 +1000 From: "John Saunders" To: Subject: RE: packet writing Date: Tue, 20 Oct 1998 13:58:39 +1000 Message-ID: <003101bdfbdd$ebed17d0$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <199810192330.RAA26343@panzer.plutotech.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > cdrecord-1.6 documents an "experimental" packet writing interface. Can > > someone clue me in as to what this is and the advantages/drawbacks of it? > > All I've heard about it is my cousin's rant about dragging and dropping > > to the CD in lose9x > > I dunno anything about it. Basically packet writing allows you to stop, then re-start, the burn mid track. However when you do this you end up with a few sectors of junk while the laser is stopping and starting. You can then use this feature however you like. Most Windows software are split into fixed packet length and variable packet length methods. The variable packet length writes data continuously until there is no more to write. The fixed packet method breaks all writes up into packets equal to the size of the CDR drives buffer. With fixed size packets you can never underrun, with variable sized packets you can. With fixed sized packets you end of with "junk" sectors mid file, with variable length packets the "junk" sectors are between the files. However to make use of this you need a filesystem able to deal with WORM like media. Each time a file is written or modified a new copy of the file is written to the end of the media. Then a new copy of the directory structure is written to the end of the disk that links to the new file. If a file is deleted then only the directory structure is re-written. The "standard" filesystem for packet writing is called UDF. The spec for it is available from the usual standards bodies. However it's likely that a filesystem supporting a WORM drive will work just as well. > > I fail to see a good reason for an OS-specific in-kernel CD-R driver, > > when the cdrecord package works on plenty of systems that have SCSI > > generic devices (passthrough). Unless I am missing some advantage of > > having CD burning code in the kernel, this strikes me as a horrible > > duplication of effort. So, what am I missing and why is this a good > > idea? :) > > Well, in many ways it is a duplication of effort. It would be > nice to have > the capability to write CD-RW and DVD disks incrementally through a > filesystem-type interface. To do that, you'd need filesystem support > (probably), but also driver-level support for writing to CDs or DVDs. My > guess is that "packet writing" lets you write incrementally to CDs, and > that your cousin's Win95 box is doing it through a filesystem type > interface. For packet writing you could probably get away with just supporting SCSI3/mmc compatible drives. But unless there is some ability to have a user space filesystems (like GNU Hurd) then it will have to be in the kernel. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 21:05:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02424 for freebsd-current-outgoing; Mon, 19 Oct 1998 21:05:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (209-239-204-33.oak.jps.net [209.239.204.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA02418 for ; Mon, 19 Oct 1998 21:05:53 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 28981 invoked by uid 100); 20 Oct 1998 03:39:02 -0000 Date: Mon, 19 Oct 1998 20:39:02 -0700 To: freebsd-current@FreeBSD.ORG Subject: disklabel vs. DIOCWLABEL Message-ID: <19981019203902.A28965@top.worldcontrol.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my -current,elf,CAM,SMP system disklabel and DIOCWLABEL do not get along. I have an adaptec 2940UW SCSI controller with 3 hard drives on it. I was trying to label 2 of the drives for use with vinum, when I kept getting: disklabel: ioctl DIOCWLABEL: Operation not supported by device errors. Nothing helped, not even the tutorial pages related to bringing up additional drives. After a day of failures I edited /usr/src/sbin/disklabel/disklabel.c and commented out the 4 calls to ioctl with DIOCWLABEL. After that disklabel worked exactly as expected and I am happily using vinum: bls2# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s2a 39647 35784 692 98% / /dev/da0s2e 396895 253521 111623 69% /usr /dev/da0s2f 3365518 2097507 998770 68% /uss /dev/vinum/bigvol 4029406 154362 3552692 4% /ust My 'make world' and kernel are from 10/19/1998 around 1:00am. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 21:10:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02815 for freebsd-current-outgoing; Mon, 19 Oct 1998 21:10:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eesn17.ews.uiuc.edu (eesn17.ews.uiuc.edu [130.126.161.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02808 for ; Mon, 19 Oct 1998 21:10:54 -0700 (PDT) (envelope-from ramasubr@ews.uiuc.edu) Received: from localhost (ramasubr@localhost) by eesn17.ews.uiuc.edu (8.8.8/8.7.3) with SMTP id XAA26348 for ; Mon, 19 Oct 1998 23:10:29 -0500 (CDT) X-Authentication-Warning: eesn17.ews.uiuc.edu: ramasubr owned process doing -bs Date: Mon, 19 Oct 1998 23:10:29 -0500 (CDT) From: Vijay Ramasubramanian Reply-To: Vijay Ramasubramanian To: freebsd-current@FreeBSD.ORG Subject: Installation probs w/3.0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello again. I wrote to the list on 13 October detailing my problems installing the 3.0-19981009-BETA release. The full text of my post can be accessed with the URL below (please put the two lines together to get the correct URL): http://www.freebsd.org/cgi/getmsg.cgi?fetch=355371+359877+ /usr/local/www/db/text/1998/freebsd-current/19981011.freebsd-current Briefly stated, I was always getting installation crashes around the 40th chunk with messages that indicated FS corruption (stuff such as ufs_dirbad, ffs_alloccg: bad map, and so on). My hardware config is as below: AMD K6-233 (one of the latest revisions) Intel TX chipset motherboard w/512KB cache 64 MB SDRAM in 1 DIMM AdvanSys ABP-940 SCSI host adapter, SCSI ID 7 IBM DCAS 2.2 GB Ultra SCSI drive, SCSI ID 0 IBM DCAS 2.2 GB Ultra SCSI drive, SCSI ID 1 Fujitsu 405 MB Fast SCSI-2 drive, SCSI ID 2 NEC 3X SCSI CD-ROM, SCSI ID 3 S3 Virge-based PCI video card SMC EtherPower II (9432TX) PCI Ethernet card PS/2 Logitech mouse Well, in response to this post, I got replies from Mr. Justin Gibbs and Mr. Mike Smith, both with the suggestions that it might be bad RAM or bad cache. It's neither. I had a lifetime warranty on the DIMM, so I called Kingston and they sent me a new module. I swapped it in today, and tried to install 3.0-RELEASE. It died with the ufs_dirbad message around the same spot as before. I then went into the BIOS and disabled the external cache, and set memory timings to the slowest possible. Same thing. I've tested and retested my HDDs for bad sectors. Haven't seen one. So I ask you guys, is it possible that I've hit a bug in the AdvanSys driver, or that my host adapter is not configured properly for this driver (queue depth, etc.)? What do I do? How can I track this down? What's more frustrating than not being able to install FreeBSD (which is *very* frustrating) is that I don't even know where the problem lies. Please help... PLEASE CC replies to me personally. Thank you. .______ | Vijay N. Ramasubramanian mailto:ramasubr@ews.uiuc.edu http://www.ews.uiuc.edu/~ramasubr/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 21:47:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05331 for freebsd-current-outgoing; Mon, 19 Oct 1998 21:47:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05322 for ; Mon, 19 Oct 1998 21:46:57 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id XAA04189; Mon, 19 Oct 1998 23:15:31 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id XAA01782; Mon, 19 Oct 1998 23:06:06 -0500 (CDT) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13868.3117.390224.376379@zuhause.zuhause.mn.org> Date: Mon, 19 Oct 1998 23:06:05 -0500 (CDT) To: "Jaime Bozza" Cc: Subject: RE: newfs problems, more information: In-Reply-To: <001101bdfba4$5a663d20$313d31cc@electron.nuc.net> References: <19981019223021.A17441@klemm.gtn.com> <001101bdfba4$5a663d20$313d31cc@electron.nuc.net> X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaime Bozza writes: > > > Don't put a filesystem on the 'c' partition. > > > > Why ? Never had trouble with this ... > > > > /dev/ccd0c 198327 92632 89829 51% /obj > > /dev/ccd1c 198327 25065 157396 14% /news > > /dev/ccd2c 99055 36883 54248 40% /proxy > > /dev/ccd3c 3400078 2886831 241241 92% /home > > Most importantly, how does one specify to *NOT* use 'c' with ccd? > /etc/ccd.conf takes the format "ccd0" without [a-g] after it. Once the ccd > is configured, you mount /dev/ccd0c. I don't know all the internal > workings of ccd, but from the documentation, the 'c' slice is automatically > used. > > And if this is not the preferred way, how would one go about specifying a > different slice? You do it the same way you do it for any other disk. You create the partition information, and do a disklabel for ccd0 to write the label, and then you newfs each partition, ccd0d, ccd0e, ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 22:17:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07066 for freebsd-current-outgoing; Mon, 19 Oct 1998 22:17:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07056; Mon, 19 Oct 1998 22:17:25 -0700 (PDT) (envelope-from dmm125@bellatlantic.net) Received: from dmm125 (client201-122-45.bellatlantic.net [151.201.122.45]) by iconmail.bellatlantic.net (IConNet Sendmail) with SMTP id BAA28521; Tue, 20 Oct 1998 01:13:26 -0400 (EDT) Message-ID: <000d01bdfbe8$593b87e0$02000003@dmm125> From: "Donn Miller" To: , Subject: FAT32 support for 3.0 installation Date: Tue, 20 Oct 1998 01:13:15 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01BDFBC6.D0A7DBC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000A_01BDFBC6.D0A7DBC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I've seen all the postings about how FAT32 support was removed from the = 3.0-RELEASE installation floppy. I tried moving the distribution files = to my FAT16 partition and I couldn't install from there either. Was = msdos filesystem support removed altogether from the boot floppy = (boot.flp) of the 3.0-RELEASE and 3.0-current branch? Thanks Donn ------=_NextPart_000_000A_01BDFBC6.D0A7DBC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I've seen all the postings about how FAT32 support = was removed=20 from the 3.0-RELEASE installation floppy.  I tried moving the = distribution=20 files to my FAT16 partition and I couldn't install from there = either.  Was=20 msdos filesystem support removed altogether from the boot floppy = (boot.flp) of=20 the 3.0-RELEASE and 3.0-current branch?
 
Thanks
 
Donn
------=_NextPart_000_000A_01BDFBC6.D0A7DBC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 22:58:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10623 for freebsd-current-outgoing; Mon, 19 Oct 1998 22:58:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles150.castles.com [208.214.165.150]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10616; Mon, 19 Oct 1998 22:58:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA00408; Mon, 19 Oct 1998 22:27:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810200527.WAA00408@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Donn Miller" cc: questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: FAT32 support for 3.0 installation In-reply-to: Your message of "Tue, 20 Oct 1998 01:13:15 EDT." <000d01bdfbe8$593b87e0$02000003@dmm125> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Oct 1998 22:27:37 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've seen all the postings about how FAT32 support was removed from the = > 3.0-RELEASE installation floppy. I tried moving the distribution files = > to my FAT16 partition and I couldn't install from there either. Was = > msdos filesystem support removed altogether from the boot floppy = > (boot.flp) of the 3.0-RELEASE and 3.0-current branch? FAT32 wasn't removed from the floppy. The FAT code was removed and replaced several times, but I believe it's in there. You need to be just a little more specific about your problems... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 19 23:18:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12415 for freebsd-current-outgoing; Mon, 19 Oct 1998 23:18:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12405 for ; Mon, 19 Oct 1998 23:18:09 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA00889; Tue, 20 Oct 1998 16:17:42 +1000 Date: Tue, 20 Oct 1998 16:17:42 +1000 From: Bruce Evans Message-Id: <199810200617.QAA00889@godzilla.zeta.org.au> To: gibbs@narnia.plutotech.com, mike@smith.net.au Subject: Re: vote:? reversion of BDE change please? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The change is actually in the right direction, as the goal is to remove >> the prototypes from global scope completely. Instead, ISA device >> drivers should register their interrupt handlers at attach time. I >> don't know if there's an example of this at the present time. > >The CAM ISA SCSI drivers set their own vectors and thus do not need >entries in isa_devices.h. Examples for doing it not-quite-right are trivial. For old drivers, it it essentially takes a 1 line assignment: diff -c2 syscons.c~ syscons.c *** syscons.c~ Fri Oct 2 14:44:31 1998 --- syscons.c Tue Oct 20 15:53:49 1998 *************** *** 240,243 **** --- 240,244 ---- /* prototypes */ static int scattach(struct isa_device *dev); + static ointhand2_t scintr; static int scparam(struct tty *tp, struct termios *t); static int scprobe(struct isa_device *dev); *************** *** 646,649 **** --- 647,651 ---- #endif + dev->id_intr = (inthand2_t *)scintr; scinit(); sc_flags = dev->id_flags; *************** *** 852,856 **** } ! void scintr(int unit) { --- 854,858 ---- } ! static void scintr(int unit) { Also, the declaration of scintr() must be changed to `#define scintr NULL' in isa_device.h so that old config files don't break. For new drivers, just don't put interrupt vectors in config files or declarations for interrupt handlers in isa_device.h. I have converted about 50 drivers as above. New drivers should also use `inthand2_t' interrupt handlers and not cast to (inthand2_t *). There is not enough infrastructure for doing this cleanly - it currently takes larger, uglier code than assigning to id_intr. I have converted about 5 drivers to use a NetBSDish interrupt attach function. The larger, uglier code goes away, something like this: diff -c2 bt_isa.c~ bt_isa.c *** bt_isa.c~ Tue Oct 13 19:42:04 1998 --- bt_isa.c Tue Oct 13 19:42:20 1998 *************** *** 43,47 **** static int bt_isa_probe __P((struct isa_device *dev)); static int bt_isa_attach __P((struct isa_device *dev)); - static void bt_isa_intr __P((void *unit)); static bus_dma_filter_t btvlbouncefilter; --- 43,46 ---- *************** *** 196,199 **** --- 208,212 ---- void *filter_arg; bus_addr_t lowaddr; + int result; bt = bt_softcs[dev->id_unit]; *************** *** 282,298 **** } ! return (bt_attach(bt)); ! } ! ! /* ! * Handle an ISA interrupt. ! * XXX should go away as soon as ISA interrupt handlers ! * take a (void *) arg. ! */ ! static void ! bt_isa_intr(void *unit) ! { ! struct bt_softc* arg = bt_softcs[(int)unit]; ! bt_intr((void *)arg); } --- 295,301 ---- } ! result = bt_attach(bt); ! isa_intr_establish(dev, &bio_imask, bt_intr, bt); ! return (result); } However, I think this doesn't actually work for drivers that that hack on dev->id_intr (pnp and maybe pccard drivers). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 00:36:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18027 for freebsd-current-outgoing; Tue, 20 Oct 1998 00:36:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18015 for ; Tue, 20 Oct 1998 00:36:23 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id UAA25508; Tue, 20 Oct 1998 20:35:54 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id UAA29893; Tue, 20 Oct 1998 20:35:53 +1300 (NZDT) Message-ID: <19981020203553.C29849@clear.co.nz> Date: Tue, 20 Oct 1998 20:35:53 +1300 From: Joe Abley To: Jason Evans , HighWind Software Information Cc: current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem References: <199810191835.OAA20137@highwind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jason Evans on Mon, Oct 19, 1998 at 06:03:22PM -0700 X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 06:03:22PM -0700, Jason Evans wrote: > > #ifndef _REENTRANT > # define _REENTRANT > #endif > Shouldn't that be _THREAD_SAFE on FreeBSD? I thought _REENTRANT was a Sunism? -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Net http://www.clear.net.nz/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 01:03:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19998 for freebsd-current-outgoing; Tue, 20 Oct 1998 01:03:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19993 for ; Tue, 20 Oct 1998 01:03:18 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA18145; Tue, 20 Oct 1998 09:01:26 +0100 (BST) Date: Tue, 20 Oct 1998 09:01:26 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: Mark Mayo , mike@smith.net.au, dg@root.com, green@zone.syracuse.NET, grog@lemis.com, julian@whistle.com, bag@sinbin.demos.su, rock@cs.uni-sb.de, current@FreeBSD.ORG Subject: Re: -current NFS problem In-Reply-To: <199810200000.RAA19037@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, Terry Lambert wrote: > > > > Has anyone asked Rick Macklem about this? > > > > > > Rick bowed out of the NFS game a long time ago. Kirk would be a better > > > bet. > > [ ... ] > > > In general, he's not interested in helping FreeBSD in any way, since > > he thinks the code has become too "polluted" and "complicated" now. > > (which I would disagree with.. initial inspection by myself a while > > ago suggested that not much at all has really changed..) > > I'd agree with him, starting with the "cookie" for VOP_READDIR. Which was also in Lite2. > > > > As for any other help, as I said, give me a list of specific questions > > and I'll do my best to get answers. > > I think if we get one shot at this, the list of questions should be > agreed upon. > > My main question would be: > > o Do you see any reason why nfsnode locking should be necessary? The last time I spoke to Rick about this, he said that the reason NFS can't use a vnode lock is to prevent a server hang from causing a lock cascade ending up with the root vnode being locked and the whole machine wedged. I experimented for a while with a gross hack which only locked regular files but it was too complicated and I ditched it. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 01:20:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21223 for freebsd-current-outgoing; Tue, 20 Oct 1998 01:20:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21161 for ; Tue, 20 Oct 1998 01:19:59 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA18187; Tue, 20 Oct 1998 09:19:43 +0100 (BST) Date: Tue, 20 Oct 1998 09:19:43 +0100 (BST) From: Doug Rabson To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: vote:? reversion of BDE change please? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Julian Elischer wrote: > Particularly I'd like to know if it breaks tha alpha port, or > the new device framework? > As it is now it certainly breaks several automatic build processes I know > of (including the /usr/share/examples/drivers scripts) The alpha doesn't do its ISA configuration like this at all. The interrupt handlers are static functions inside the driver and are registered explicitly when the device is attached. The i386 code should go in this direction IMHO. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 01:27:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21806 for freebsd-current-outgoing; Tue, 20 Oct 1998 01:27:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21791; Tue, 20 Oct 1998 01:27:15 -0700 (PDT) (envelope-from dmm125@bellatlantic.net) Received: from dmm125 (client201-122-45.bellatlantic.net [151.201.122.45]) by iconmail.bellatlantic.net (IConNet Sendmail) with SMTP id EAA04253; Tue, 20 Oct 1998 04:25:06 -0400 (EDT) Message-ID: <000401bdfc03$1f396b00$02000003@dmm125> From: "Donn Miller" To: "Mike Smith" Cc: , Subject: Re: FAT32 support for 3.0 installation Date: Tue, 20 Oct 1998 04:24:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Mike Smith To: Donn Miller Cc: questions@FreeBSD.ORG ; freebsd-current@FreeBSD.ORG Date: Tuesday, October 20, 1998 1:58 AM Subject: Re: FAT32 support for 3.0 installation >> >> I've seen all the postings about how FAT32 support was removed from the = >> 3.0-RELEASE installation floppy. I tried moving the distribution files = >> to my FAT16 partition and I couldn't install from there either. Was = >> msdos filesystem support removed altogether from the boot floppy = >> (boot.flp) of the 3.0-RELEASE and 3.0-current branch? > >FAT32 wasn't removed from the floppy. The FAT code was removed and >replaced several times, but I believe it's in there. You need to be >just a little more specific about your problems... The problems I'm having are that I boot up on the boot floppy (boot.flp). Then when it gets to the point of the installation where it tries to extract the distributions off my FAT32 partition, I get an error to the effect that the following distributions weren't found: bin manpages proflibs des compat. Basically, all of them. I thought that maybe sysinstall expected a certain combination of uppercase/lowercase letter combinations. Like: C:\FreeBSD\bin C:\FREEBSD\bin C:\freebsd\BIN C:\Freebsd\bin etc. since now we are working with case-sensitive filenames with msdos. I remember with 2.2.7 I had problems because I used a scheme like C:\FreeBSD\bin for my FAT32 partition. It said the same thing that it couldn't find the dists. Then I changed the filenames to e.g. C:\FREEBSD\bin and then it installed OK. But this time I tried various combinations of uppercase/lowercase to no avail. I even tried copying C:\FreeBSD (FAT32) to D:\FreeBSD (FAT16) since D: is FAT16. The thinking there was that if it couldn't install from FAT32, FAT16 should work. As a check I tried booting off the boot.flp from the latest 3.0-SNAP release, with the same result. I also tried booting off the boot.flp from 2.2.7-RELEASE as a check with just a minimal install and it went OK (but it caught SIG 11). The main thing was it could at least mount and read the msdos-fs. Someone suggested that all msdos-fs code was removed from 3.0's boot floppy. Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 02:09:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24852 for freebsd-current-outgoing; Tue, 20 Oct 1998 02:09:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from amadeus.informatik.ba-stuttgart.de (amadeus.informatik.ba-stuttgart.de [141.31.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24837 for ; Tue, 20 Oct 1998 02:09:42 -0700 (PDT) (envelope-from henry@BA-Stuttgart.De) Received: from gilels.informatik.ba-stuttgart.de (gilels.informatik.ba-stuttgart.de [141.31.111.69]) by amadeus.informatik.ba-stuttgart.de with ESMTP (8.7.1/8.7.1) id LAA02173; Tue, 20 Oct 1998 11:09:02 +0200 (METDST) From: Henry Vogt Received: (from henry@localhost) by gilels.informatik.ba-stuttgart.de (8.9.1/8.8.8) id LAA05198; Tue, 20 Oct 1998 11:08:01 +0200 (CEST) (envelope-from henry) Message-Id: <199810200908.LAA05198@gilels.informatik.ba-stuttgart.de> Subject: Re: fxp0 - unsupported PHY=63 ? To: dg@root.com Date: Tue, 20 Oct 1998 11:08:01 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello David, >>The chip on the card is labeled '82558B', and is not mentioned in > Can you look on the board and see what serial EEPROM it uses? > -DG It's a 93C14 EEPROM, the exact label is -------------- 85AF93C14 M8 -------------- The intel Prozessor is a SB82558, the exact label is -------------- SB82558B L829ID71 SL2P4 -------------- Regards Henry -- // // Do you suffer from long term memory loss ? // - I don't remember:-( // // Henry Vogt, FR Informationstechnik an der Berufsakademie Stuttgart. // e-mail: hv@BA-Stuttgart.De Tel. (dienstl.): 0711/6673-6967 // http://www.informatik.ba-stuttgart.de/~hv // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 03:55:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00412 for freebsd-current-outgoing; Tue, 20 Oct 1998 03:55:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-15-dbn.dial-up.net [196.34.155.79]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00395 for ; Tue, 20 Oct 1998 03:55:07 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id MAA05541; Tue, 20 Oct 1998 12:53:27 +0200 (SAT) From: Robert Nordier Message-Id: <199810201053.MAA05541@ceia.nordier.com> Subject: Re: Howto boot0 In-Reply-To: <19981019202448.A3534@TOJ.org> from Tom Jackson at "Oct 19, 98 08:24:48 pm" To: toj@gorilla.net (Tom Jackson) Date: Tue, 20 Oct 1998 12:53:20 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom Jackson wrote: > How do you manually install boot0 to test it? May be somewhere, > sorry if I missed it. You can use sysinstall, but there's a simple installation program, together with the current boot0 binary, at http://www.freebsd.org/~rnordier/boot0inst-1.0.tar.gz -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 03:57:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00680 for freebsd-current-outgoing; Tue, 20 Oct 1998 03:57:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-15-dbn.dial-up.net [196.34.155.79]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00671 for ; Tue, 20 Oct 1998 03:57:20 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id MAA05554; Tue, 20 Oct 1998 12:55:52 +0200 (SAT) From: Robert Nordier Message-Id: <199810201055.MAA05554@ceia.nordier.com> Subject: Re: To everyone who's been having trouble with the new "booteasy" In-Reply-To: <19981019140456.B4089@Alameda.net> from Ulf Zimmermann at "Oct 19, 98 02:04:56 pm" To: ulf@Alameda.net Date: Tue, 20 Oct 1998 12:55:44 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann wrote: > > Glad to have the feedback, thanks. > > > > I've committed some changes to boot0 based on the data received, though > > there is probably no particular reason to use it rather than booteasy > > for the moment. > > The machine I am testing on is called Playtoy and that name stands for > what it is. Gimme something to test and I will test. That's a useful offer, thanks. The latest boot0 binary, together with a simple installation program, is at wget http://www.freebsd.org/~rnordier/boot0inst-1.0.tar.gz -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 04:09:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03797 for freebsd-current-outgoing; Tue, 20 Oct 1998 04:09:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03788 for ; Tue, 20 Oct 1998 04:09:35 -0700 (PDT) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id IAA16905; Tue, 20 Oct 1998 08:08:55 -0300 (ADT) Date: Tue, 20 Oct 1998 08:08:55 -0300 (ADT) From: Marc Fournier X-Sender: marc@iceberg To: John Birrell cc: eculp@webwizard.org.mx, freebsd-current@FreeBSD.ORG Subject: Re: paranoid question: aout vs ELF... In-Reply-To: <199810192221.IAA21603@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, John Birrell wrote: > Marc Fournier wrote: > > Huh? I didn't think that was a choice? Just do my "usual", > > consisting of: > > > > make buildworld > > install new config > > build new kernel > > install new kernel > > make installworld > > > > and that's it? > > Yes, that should still work. If it doesn't, let's fix that problem before > you go on. make buildworld appears to work okay, building new kernel doesn't: hub# make depend cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../i386/i386/genassym.c cc1: Invalid option `-fformat-extensions' *** Error code 1 Stop. hub# hub# which cc /usr/bin/cc hub# cc -v gcc version 2.7.2.1 Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 06:01:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12991 for freebsd-current-outgoing; Tue, 20 Oct 1998 06:01:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12985 for ; Tue, 20 Oct 1998 06:01:43 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id IAA09236; Tue, 20 Oct 1998 08:01:12 -0500 (CDT) Message-Id: <199810201301.IAA09236@ns.tar.com> From: "Richard Seaman, Jr." To: "HighWind Software Information" Cc: "current@freebsd.org" Date: Tue, 20 Oct 98 08:01:12 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998 16:45:32 -0400 (EDT), HighWind Software Information wrote: >Simply to placate your claim, here is another version that locks and >unlocks the mutex in proper fashion. I simply had to insert an >additional "sleep" to get the bug to appear. > >In both cases, spinning the CPU at 100% and allowing the program to >hang and make no forward progress is a SERIOUS bug. > >I claim that this new version is 100% valid. Does proper locking, and >also works on other O/S's. On FreeBSD it does not work at all. > >-Rob I can confirm that your test program behaves as you describe on my machine also. I haven't had a lot of time to look at it, but I'd *guess* that what happens is this: 1) The main thread starts its loop by locking the mutex 2) It calls pthread_cond_signal, which in turn wakes up one of your sleeping condThreads. 3) Upon waking up inside pthread_cond_wait, the condThread locks the spinlock for the cond variable condition (this is the error which leads to the deadlock) 4) the condThread tries to lock the mutex, finds it locked already, so it waits (still inside pthreat_cond_wait) 5) meanwhile, the main thread enters pthread_cond_signal a second time, and tries to lock the spinlock for condition. Its already locked by a condThread, so it waits. 6) result: deadlock The fix is to clean up the spinlock code in the pthread_cond_* code. As far as I can tell, the spinlock on the condition variable should only be set when the condition variable structures are being messed with. If this is do, and the code fixed appropriately, my guess is that the deadlock would be eliminated. I will try to look at this later, if I have time. However, there are others who know a lot more about this than I do who could probably do a better fix. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 06:09:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13785 for freebsd-current-outgoing; Tue, 20 Oct 1998 06:09:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rossel.solplus.de (rossel.solplus.de [195.125.160.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13774 for ; Tue, 20 Oct 1998 06:09:10 -0700 (PDT) (envelope-from doehrm@aubi.de) Received: from igate.aubi.de (root@igate.aubi.de [193.24.63.232]) by rossel.solplus.de (8.8.8/8.8.8) with ESMTP id PAA00566 for ; Tue, 20 Oct 1998 15:09:23 +0200 (MET DST) Received: from exchange.aubi.de ([170.56.121.91]) by igate.aubi.de (8.8.7/8.8.7) with ESMTP id QAA05556 for ; Tue, 20 Oct 1998 16:18:44 +0200 Received: by EXCHANGE.aubi.de with Internet Mail Service (5.5.2232.9) id ; Tue, 20 Oct 1998 15:04:56 +0200 Message-ID: From: =?iso-8859-1?Q?Markus_D=F6hr?= To: freebsd-current@FreeBSD.ORG Subject: upgrading 2.2.7 - 3.0 Date: Tue, 20 Oct 1998 15:03:49 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA13777 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all! I'm tryin' to upgrade a system from 2.2.7 from the sources to 3.0 I did a 'make aout-to-elf' in the /usr/src directory and the machine compiled the whole night long. Now I get a prompt to confirm the movement of the aout-libs. When I press enter it says the following Searching library directory /usr/lib for a.out libraries Searching library directory /usr/lib/compat for a.out libraries Searching library directory /usr/local/lib for a.out libraries Searching library directory /usr/X11R6/lib for a.out libraries ldconfig: /usr/local/lib/aout: No such file or directory ***Error code 255 Stop. What am I doin' wrong? -- Markus Döhr IT Admin AUBI Baubeschläge GmbH Tel.: +49 6503 917 152 Fax : +49 6503 917 119 e-Mail: doehrm@aubi.de ************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 06:31:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17077 for freebsd-current-outgoing; Tue, 20 Oct 1998 06:31:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17072 for ; Tue, 20 Oct 1998 06:31:02 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id IAA09508; Tue, 20 Oct 1998 08:30:30 -0500 (CDT) Message-Id: <199810201330.IAA09508@ns.tar.com> From: "Richard Seaman, Jr." To: "HighWind Software Information" Cc: "current@freebsd.org" Date: Tue, 20 Oct 98 08:30:30 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 98 08:01:12 -0500, Richard Seaman, Jr. wrote: >I will try to look at this later, if I have time. However, there are >others who know a lot more about this than I do who could probably >do a better fix. You could try the following patch. However, someone else should look at it too before its committed. *** uthread_cond.c.orig Tue Oct 20 08:13:58 1998 --- uthread_cond.c Tue Oct 20 08:21:31 1998 *************** *** 137,144 **** */ else if (*cond != NULL || (rval = pthread_cond_init(cond,NULL)) == 0) { - /* Lock the condition variable structure: */ - _SPINLOCK(&(*cond)->lock); /* Process according to condition variable type: */ switch ((*cond)->c_type) { --- 137,142 ---- *************** *** 148,154 **** --- 146,156 ---- * Queue the running thread for the condition * variable: */ + + /* Lock the condition variable structure: */ + _SPINLOCK(&(*cond)->lock); _thread_queue_enq(&(*cond)->c_queue, _thread_run); + _SPINUNLOCK(&(*cond)->lock); /* Unlock the mutex: */ pthread_mutex_unlock(mutex); *************** *** 156,171 **** /* Wait forever: */ _thread_run->wakeup_time.tv_sec = -1; - /* Unlock the condition variable structure: */ - _SPINUNLOCK(&(*cond)->lock); /* Schedule the next thread: */ _thread_kern_sched_state(PS_COND_WAIT, __FILE__, __LINE__); - /* Lock the condition variable structure: */ - _SPINLOCK(&(*cond)->lock); - /* Lock the mutex: */ rval = pthread_mutex_lock(mutex); break; --- 158,168 ---- *************** *** 177,184 **** break; } - /* Unlock the condition variable structure: */ - _SPINUNLOCK(&(*cond)->lock); } /* Return the completion status: */ --- 174,179 ---- *************** *** 201,208 **** */ else if (*cond != NULL || (rval = pthread_cond_init(cond,NULL)) == 0) { - /* Lock the condition variable structure: */ - _SPINLOCK(&(*cond)->lock); /* Process according to condition variable type: */ switch ((*cond)->c_type) { --- 196,201 ---- *************** *** 219,225 **** --- 212,221 ---- * Queue the running thread for the condition * variable: */ + /* Lock the condition variable structure: */ + _SPINLOCK(&(*cond)->lock); _thread_queue_enq(&(*cond)->c_queue, _thread_run); + _SPINUNLOCK(&(*cond)->lock); /* Unlock the mutex: */ if ((rval = pthread_mutex_unlock(mutex)) != 0) { *************** *** 228,245 **** * running thread from the condition * variable queue: */ _thread_queue_deq(&(*cond)->c_queue); } else { - /* Unlock the condition variable structure: */ - _SPINUNLOCK(&(*cond)->lock); /* Schedule the next thread: */ _thread_kern_sched_state(PS_COND_WAIT, __FILE__, __LINE__); - /* Lock the condition variable structure: */ - _SPINLOCK(&(*cond)->lock); - /* Lock the mutex: */ if ((rval = pthread_mutex_lock(mutex)) != 0) { } --- 224,238 ---- * running thread from the condition * variable queue: */ + _SPINLOCK(&(*cond)->lock); _thread_queue_deq(&(*cond)->c_queue); + _SPINUNLOCK(&(*cond)->lock); } else { /* Schedule the next thread: */ _thread_kern_sched_state(PS_COND_WAIT, __FILE__, __LINE__); /* Lock the mutex: */ if ((rval = pthread_mutex_lock(mutex)) != 0) { } *************** *** 258,265 **** break; } - /* Unlock the condition variable structure: */ - _SPINUNLOCK(&(*cond)->lock); } /* Return the completion status: */ --- 251,256 ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 07:26:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20516 for freebsd-current-outgoing; Tue, 20 Oct 1998 07:26:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20478 for ; Tue, 20 Oct 1998 07:25:52 -0700 (PDT) (envelope-from tejblum@arc.hq.cti.ru) Received: from arc.hq.cti.ru (localhost [127.0.0.1]) by arc.hq.cti.ru (8.9.0/8.9.0) with ESMTP id SAA29616; Tue, 20 Oct 1998 18:24:42 +0400 (MSD) Message-Id: <199810201424.SAA29616@arc.hq.cti.ru> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Richard Seaman, Jr." cc: "HighWind Software Information" , "current@freebsd.org" Subject: Re: Another Serious libc_r problem In-reply-to: Your message of "Tue, 20 Oct 1998 08:30:30 CDT." <199810201330.IAA09508@ns.tar.com> Date: Tue, 20 Oct 1998 18:24:42 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 20 Oct 98 08:01:12 -0500, Richard Seaman, Jr. wrote: > > >I will try to look at this later, if I have time. However, there are > >others who know a lot more about this than I do who could probably > >do a better fix. > > You could try the following patch. However, someone else should look at > it too before its committed. Heh. I was just about post a very similar patch when received your posting. I think, howewer, that your patch is slightly wrong, so I will post mine anyway. As far as I understand, it is better to do pthread_mutex_unlock and _thread_queue_enc under same _SPINLOCK. (I'm afraid, there is still some races in this code). Here is my patch: *** uthread_cond.c Tue Oct 20 13:55:49 1998 --- uthread_cond.c Tue Oct 20 14:14:55 1998 *************** *** 137,149 **** */ else if (*cond != NULL || (rval = pthread_cond_init(cond,NULL)) == 0) { - /* Lock the condition variable structure: */ - _SPINLOCK(&(*cond)->lock); - /* Process according to condition variable type: */ switch ((*cond)->c_type) { /* Fast condition variable: */ case COND_TYPE_FAST: /* * Queue the running thread for the condition * variable: --- 137,152 ---- */ else if (*cond != NULL || (rval = pthread_cond_init(cond,NULL)) == 0) { /* Process according to condition variable type: */ switch ((*cond)->c_type) { /* Fast condition variable: */ case COND_TYPE_FAST: + /* Wait forever: */ + _thread_run->wakeup_time.tv_sec = -1; + + /* Lock the condition variable structure: */ + _SPINLOCK(&(*cond)->lock); + /* * Queue the running thread for the condition * variable: *************** *** 151,173 **** _thread_queue_enq(&(*cond)->c_queue, _thread_run); /* Unlock the mutex: */ ! pthread_mutex_unlock(mutex); ! ! /* Wait forever: */ ! _thread_run->wakeup_time.tv_sec = -1; ! ! /* Unlock the condition variable structure: */ ! _SPINUNLOCK(&(*cond)->lock); ! /* Schedule the next thread: */ ! _thread_kern_sched_state(PS_COND_WAIT, ! __FILE__, __LINE__); ! /* Lock the condition variable structure: */ ! _SPINLOCK(&(*cond)->lock); ! /* Lock the mutex: */ ! rval = pthread_mutex_lock(mutex); break; /* Trap invalid condition variable types: */ --- 154,180 ---- _thread_queue_enq(&(*cond)->c_queue, _thread_run); /* Unlock the mutex: */ ! if ((rval = pthread_mutex_unlock(mutex)) != 0) { ! /* ! * Cannot unlock the mutex, so remove the ! * running thread from the condition ! * variable queue: ! */ ! _thread_queue_deq(&(*cond)->c_queue); ! /* Unlock the condition variable structure: */ ! _SPINUNLOCK(&(*cond)->lock); ! } else { ! /* Unlock the condition variable structure: */ ! _SPINUNLOCK(&(*cond)->lock); ! /* Schedule the next thread: */ ! _thread_kern_sched_state(PS_COND_WAIT, ! __FILE__, __LINE__); ! /* Lock the mutex: */ ! rval = pthread_mutex_lock(mutex); ! } break; /* Trap invalid condition variable types: */ *************** *** 177,184 **** break; } - /* Unlock the condition variable structure: */ - _SPINUNLOCK(&(*cond)->lock); } /* Return the completion status: */ --- 184,189 ---- *************** *** 201,209 **** */ else if (*cond != NULL || (rval = pthread_cond_init(cond,NULL)) == 0) { - /* Lock the condition variable structure: */ - _SPINLOCK(&(*cond)->lock); - /* Process according to condition variable type: */ switch ((*cond)->c_type) { /* Fast condition variable: */ --- 206,211 ---- *************** *** 215,220 **** --- 217,225 ---- /* Reset the timeout flag: */ _thread_run->timeout = 0; + /* Lock the condition variable structure: */ + _SPINLOCK(&(*cond)->lock); + /* * Queue the running thread for the condition * variable: *************** *** 229,234 **** --- 234,242 ---- * variable queue: */ _thread_queue_deq(&(*cond)->c_queue); + + /* Unlock the condition variable structure: */ + _SPINUNLOCK(&(*cond)->lock); } else { /* Unlock the condition variable structure: */ _SPINUNLOCK(&(*cond)->lock); *************** *** 237,245 **** _thread_kern_sched_state(PS_COND_WAIT, __FILE__, __LINE__); - /* Lock the condition variable structure: */ - _SPINLOCK(&(*cond)->lock); - /* Lock the mutex: */ if ((rval = pthread_mutex_lock(mutex)) != 0) { } --- 245,250 ---- *************** *** 258,265 **** break; } - /* Unlock the condition variable structure: */ - _SPINUNLOCK(&(*cond)->lock); } /* Return the completion status: */ --- 263,268 ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 07:53:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22463 for freebsd-current-outgoing; Tue, 20 Oct 1998 07:53:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22458 for ; Tue, 20 Oct 1998 07:52:59 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id HAA04158; Tue, 20 Oct 1998 07:52:28 -0700 (PDT) (envelope-from jdp) Message-Id: <199810201452.HAA04158@austin.polstra.com> To: chris@netmonger.net Subject: Re: cvsup and file permissions In-Reply-To: <19981019180508.A26343@netmonger.net> References: <19981015194840.A16439@netmonger.net> <199810160028.RAA02305@dingo.cdrom.com> <19981019180508.A26343@netmonger.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 20 Oct 1998 07:52:28 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981019180508.A26343@netmonger.net>, Christopher Masto wrote: > Regardless, it would be nice to have a way to tell cvsup not to sync > permissions. That feature's on my to-do list. I think I might actually get some time to work on CVSup again in the not-to-distant future. Meanwhile, try changing the umask as I suggested in my other mail. I'm pretty sure that will work. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 08:09:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23999 for freebsd-current-outgoing; Tue, 20 Oct 1998 08:09:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23994 for ; Tue, 20 Oct 1998 08:09:30 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA09518; Tue, 20 Oct 1998 11:09:01 -0400 (EDT) (envelope-from wollman) Date: Tue, 20 Oct 1998 11:09:01 -0400 (EDT) From: Garrett Wollman Message-Id: <199810201509.LAA09518@khavrinen.lcs.mit.edu> To: Doug Rabson Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: vote:? reversion of BDE change please? In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > The alpha doesn't do its ISA configuration like this at all. The > interrupt handlers are static functions inside the driver and are > registered explicitly when the device is attached. The i386 code should > go in this direction IMHO. Working on it.... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 08:31:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26257 for freebsd-current-outgoing; Tue, 20 Oct 1998 08:31:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26252 for ; Tue, 20 Oct 1998 08:31:54 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id LAA28817; Tue, 20 Oct 1998 11:33:19 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Tue, 20 Oct 1998 11:33:19 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: "Richard Seaman, Jr." cc: HighWind Software Information , "current@freebsd.org" Subject: Re: Another Serious libc_r problem In-Reply-To: <199810201330.IAA09508@ns.tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this patch may be over corecting the problem by not locking around the mutex lock after being woken up. Take a look at what i tried, it "batches" wakeups on a cond_broadcast as to avoid a tight loop on spinlock aquiring/release and also seems to fix the problem. It would be great to have an extensive test suite that stressed pthread functionality though. The patch is at the end of the message. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 20 Oct 1998, Richard Seaman, Jr. wrote: > On Tue, 20 Oct 98 08:01:12 -0500, Richard Seaman, Jr. wrote: > > >I will try to look at this later, if I have time. However, there are > >others who know a lot more about this than I do who could probably > >do a better fix. > > You could try the following patch. However, someone else should look at > it too before its committed. > this looks wrong, although mutex aquiring is atomic we really should lock on the conditional, no? > *** 148,154 **** > --- 146,156 ---- > * Queue the running thread for the condition > * variable: > */ > + > + /* Lock the condition variable structure: */ > + _SPINLOCK(&(*cond)->lock); > _thread_queue_enq(&(*cond)->c_queue, _thread_run); > + _SPINUNLOCK(&(*cond)->lock); > > /* Unlock the mutex: */ > pthread_mutex_unlock(mutex); > *************** > *** 156,171 **** > /* Wait forever: */ > _thread_run->wakeup_time.tv_sec = -1; > > - /* Unlock the condition variable structure: */ > - _SPINUNLOCK(&(*cond)->lock); > > /* Schedule the next thread: */ > _thread_kern_sched_state(PS_COND_WAIT, > __FILE__, __LINE__); > > - /* Lock the condition variable structure: */ > - _SPINLOCK(&(*cond)->lock); > - > /* Lock the mutex: */ > rval = pthread_mutex_lock(mutex); > break; --- uthread_cond.c Tue Oct 20 11:31:31 1998 +++ /root/uthread_fix.c Tue Oct 20 11:31:12 1998 @@ -37,6 +37,11 @@ #include #include "pthread_private.h" +/* number of signals to batch for pthread_cond_broadcast() to avoid + * expensive looping on a spinlock + */ +#define _PTHREAD_MBROADCAST 10 + int pthread_cond_init(pthread_cond_t * cond, const pthread_condattr_t * cond_attr) { @@ -164,7 +169,6 @@ __FILE__, __LINE__); /* Lock the condition variable structure: */ - _SPINLOCK(&(*cond)->lock); /* Lock the mutex: */ rval = pthread_mutex_lock(mutex); @@ -174,11 +178,11 @@ default: /* Return an invalid argument error: */ rval = EINVAL; + _SPINUNLOCK(&(*cond)->lock); break; } /* Unlock the condition variable structure: */ - _SPINUNLOCK(&(*cond)->lock); } /* Return the completion status: */ @@ -284,21 +288,19 @@ /* Fast condition variable: */ case COND_TYPE_FAST: /* Bring the next thread off the condition queue: */ - if ((pthread = _thread_queue_deq(&(*cond)->c_queue)) != NULL) { + pthread = _thread_queue_deq(&(*cond)->c_queue); + _SPINUNLOCK(&(*cond)->lock); /* Allow the thread to run: */ - PTHREAD_NEW_STATE(pthread,PS_RUNNING); - } + if(pthread) PTHREAD_NEW_STATE(pthread,PS_RUNNING); break; /* Trap invalid condition variable types: */ default: /* Return an invalid argument error: */ rval = EINVAL; + _SPINUNLOCK(&(*cond)->lock); break; } - - /* Unlock the condition variable structure: */ - _SPINUNLOCK(&(*cond)->lock); } /* Return the completion status: */ @@ -312,12 +314,12 @@ int status; pthread_t pthread; + pthread_t nospin[_PTHREAD_MBROADCAST]; + int i,j; + if (cond == NULL || *cond == NULL) rval = EINVAL; else { - /* Lock the condition variable structure: */ - _SPINLOCK(&(*cond)->lock); - /* Process according to condition variable type: */ switch ((*cond)->c_type) { /* Fast condition variable: */ @@ -325,12 +327,23 @@ /* * Enter a loop to bring all threads off the * condition queue: + * to avoid heavy spinlocking we "batch" unblocking */ - while ((pthread = - _thread_queue_deq(&(*cond)->c_queue)) != NULL) { - /* Allow the thread to run: */ - PTHREAD_NEW_STATE(pthread,PS_RUNNING); - } + do{ + /* lock for queue access */ + _SPINLOCK(&(*cond)->lock); + for( i = 0; i < _PTHREAD_MBROADCAST ; i++){ + /* fill array, early out on NULL */ + if( (nospin[i] = _thread_queue_deq(&(*cond)->c_queue) ) == NULL){ + break; + } + } + _SPINUNLOCK(&(*cond)->lock); + /* unlock to prevent deadlock */ + for( j = 0; j < i ; j++){ + PTHREAD_NEW_STATE(nospin[j],PS_RUNNING); + } + }while(nospin[j]); break; /* Trap invalid condition variable types: */ @@ -340,8 +353,6 @@ break; } - /* Unlock the condition variable structure: */ - _SPINUNLOCK(&(*cond)->lock); } /* Return the completion status: */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 08:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27620 for freebsd-current-outgoing; Tue, 20 Oct 1998 08:44:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27614 for ; Tue, 20 Oct 1998 08:44:04 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id IAA14327; Tue, 20 Oct 1998 08:43:06 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 20 Oct 1998 08:43:06 -0700 (PDT) From: Doug White To: "David O'Brien" cc: current@FreeBSD.ORG Subject: Re: newfs problems, more information: In-Reply-To: <19981019104740.A28337@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, David O'Brien wrote: > > > Granted this document references 2.2-RELEASE but it doesn't follow > > > this convention/rule. It should probably be updated. > > > > > > http://www.freebsd.org/tutorials/diskformat/diskformat.html#s1-4-3 > > > > I'll put it in my queue. > > Might also be a good idea to sync the "Disks" section of the Handbook > with it too. I've mulled over that recently and decided that if I touched that section I'd end up fully merging the tutorial into the handbook. The existing Handbook section doesn't have enough detail for my taste. Unless that's okay with you... Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 08:46:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28001 for freebsd-current-outgoing; Tue, 20 Oct 1998 08:46:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27990 for ; Tue, 20 Oct 1998 08:46:18 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA21709; Tue, 20 Oct 1998 11:45:50 -0400 (EDT) Date: Tue, 20 Oct 1998 11:45:50 -0400 (EDT) From: Daniel Eischen Message-Id: <199810201545.LAA21709@pcnet1.pcnet.com> To: lists@tar.com, tejblum@arc.hq.cti.ru Subject: Re: Another Serious libc_r problem Cc: current@FreeBSD.ORG, info@highwind.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitrij Tejblum wrote: > > On Tue, 20 Oct 98 08:01:12 -0500, Richard Seaman, Jr. wrote: > > > > >I will try to look at this later, if I have time. However, there are > > >others who know a lot more about this than I do who could probably > > >do a better fix. > > > > You could try the following patch. However, someone else should look at > > it too before its committed. > > Heh. I was just about post a very similar patch when received your posting. > I think, howewer, that your patch is slightly wrong, so I will post mine > anyway. As far as I understand, it is better to do pthread_mutex_unlock and > _thread_queue_enc under same _SPINLOCK. (I'm afraid, there is still some > races in this code). I don't think you want to wrap anything other than the condtion queue and dequeue with the condition spin locks; they should be used just to protect changing the condition variable. As long as you enqueue the condition variable before you unlock the mutex, there should be no race conditions. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 08:48:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28367 for freebsd-current-outgoing; Tue, 20 Oct 1998 08:48:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28362 for ; Tue, 20 Oct 1998 08:48:12 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id IAA15336; Tue, 20 Oct 1998 08:47:19 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 20 Oct 1998 08:47:18 -0700 (PDT) From: Doug White To: Jaime Bozza cc: Andreas Klemm , Mike Smith , ulf@Alameda.net, current@FreeBSD.ORG Subject: RE: newfs problems, more information: In-Reply-To: <001101bdfba4$5a663d20$313d31cc@electron.nuc.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Jaime Bozza wrote: > > > Don't put a filesystem on the 'c' partition. > > > > Why ? Never had trouble with this ... > > > > /dev/ccd0c 198327 92632 89829 51% /obj > > /dev/ccd1c 198327 25065 157396 14% /news > > /dev/ccd2c 99055 36883 54248 40% /proxy > > /dev/ccd3c 3400078 2886831 241241 92% /home > > Most importantly, how does one specify to *NOT* use 'c' with ccd? > /etc/ccd.conf takes the format "ccd0" without [a-g] after it. Once the ccd > is configured, you mount /dev/ccd0c. I don't know all the internal > workings of ccd, but from the documentation, the 'c' slice is automatically > used. I think ccd is a special case. if you want to specify a different partition, you have to offset it by 240 blocks or so otherwise it stomps the ccd disklabel. newfsing the c partition seems to account for that in some funny way. We ran into this building a ccd on an OpenBSD box. > And if this is not the preferred way, how would one go about specifying a > different slice? In disklabel -e, just copy the 'c' line and change the c to h. Then newfs h. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 09:16:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02266 for freebsd-current-outgoing; Tue, 20 Oct 1998 09:16:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from amsoft.ru (amsoft.ru [194.87.86.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02124 for ; Tue, 20 Oct 1998 09:15:49 -0700 (PDT) (envelope-from am@amsoft.ru) Received: (from am@localhost) by amsoft.ru (8.8.8/amsoft/1.0) id UAA10603 for freebsd-current@freebsd.org; Tue, 20 Oct 1998 20:08:21 +0400 (MSD) From: Andrew Maltsev Message-Id: <199810201608.UAA10603@amsoft.ru> Subject: minor problem with 3.0 build To: freebsd-current@FreeBSD.ORG Date: Tue, 20 Oct 1998 20:08:20 +0400 (MSD) Organization: AM'soft X-Location: Oryol (http://www.oryol.ru/), Russia X-Phone: +7 086 229 9988 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG src/gnu/usr.bin/binutils/strip/Makefile has the following lines: maybe_stripped: strip cp strip maybe_stripped .if defined(STRIP) .if ${STRIP:M-s} != "" strip maybe_stripped .endif .endif When the PATH defined as something like `PATH=.:/bin:/usr/bin:...' (yes, I know it's a Bad Thing) and strip was built in a.out format but without a.out support it tries to strip itself and fails. As a solution I used full path to a.out strip instead of calling it by PATH. Worked ok for me. Andrew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 09:19:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02613 for freebsd-current-outgoing; Tue, 20 Oct 1998 09:19:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02608 for ; Tue, 20 Oct 1998 09:19:37 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id MAA26576; Tue, 20 Oct 1998 12:18:43 -0400 (EDT) Date: Tue, 20 Oct 1998 12:18:43 -0400 (EDT) Message-Id: <199810201618.MAA26576@highwind.com> From: HighWind Software Information To: bright@hotjobs.com CC: lists@tar.com, current@FreeBSD.ORG In-reply-to: (message from Alfred Perlstein on Tue, 20 Oct 1998 11:33:19 -0400 (EDT)) Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm. Now we got 3 patches. I am a little wary about Alfred's "broadcast" patch. Seems premature optimization. I'd rather have something that is conservative first. Can someone with commit priviledges take a peek at this and add one of these to the source? -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 09:33:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04706 for freebsd-current-outgoing; Tue, 20 Oct 1998 09:33:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04697 for ; Tue, 20 Oct 1998 09:33:35 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id MAA28941; Tue, 20 Oct 1998 12:35:14 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Tue, 20 Oct 1998 12:35:14 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: HighWind Software Information cc: current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem In-Reply-To: <199810201618.MAA26576@highwind.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hmmm, a better idea would be for queues to remeber how many elements are on them, that way a malloc could have been done, either that or the scheduler should be able to accept a queue of threads to schedule, but that would require a lot of work. btw, the patch I do isn't anything spectacular it just avoids looping and spinlocking, if you apply the patch and time a much longer loop in the main thread, 6,000,000 iterations vs 12 and removed the select calls you should see some improvement in the execution time. The problem with all these patches is that the even the ones that address broadcasts (which don't work to begin with) do not make it an atomic operation. (where it was in theory before, but didn't work) As a side note, has anyone thought of hybrid kernel+userland threads? Basically a userland scheduler with kernel hooks for mutexes and distributing signals. At startup or on the first pthread_create() the pthreads library would sysctl out the number of processors in the system and prefork kernel threads for each. The kernel threads would only be active on SMP machines, otherwise there really is no point. Does anyone have any papers/webpages about an algorithm like that? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 20 Oct 1998, HighWind Software Information wrote: > > Hmmm. Now we got 3 patches. > > I am a little wary about Alfred's "broadcast" patch. Seems premature > optimization. I'd rather have something that is conservative first. > > Can someone with commit priviledges take a peek at this and add one > of these to the source? > > -Rob > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 09:34:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04915 for freebsd-current-outgoing; Tue, 20 Oct 1998 09:34:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mnw.eas.slu.edu (mnw.eas.slu.edu [165.134.8.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04875 for ; Tue, 20 Oct 1998 09:34:08 -0700 (PDT) (envelope-from ejh@mnw.eas.slu.edu) Received: (from ejh@localhost) by mnw.eas.slu.edu (8.8.8/8.8.8) id LAA06373 for current@freebsd.org; Tue, 20 Oct 1998 11:33:40 -0500 (CDT) Date: Tue, 20 Oct 1998 11:33:40 -0500 (CDT) From: Eric Haug Message-Id: <199810201633.LAA06373@mnw.eas.slu.edu> To: current@FreeBSD.ORG Subject: nfs panic in free() Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I am having a repeatable panic in the nfs server code. I have a -g compile kernel and a vmcore file. dmesg output included Should this be sent via send-pr? Anyone else seeing this sort of nfs bug? Another problem that this system has: The Promise card has the prom removed, cause the system will not recognize the disks connected to it when the prom is in there. I believe that this results in the disk access timing being off so that transfers are about half of what they could be. The MBoard is a Matsonic MS6260S running at system clock of 100MHz. The CPU is rated for more than 300 MHz. i.e. the system is not overclocked. The gdb-aout's where command produces: #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 #1 0xf01389db in panic (fmt=0xf01354a4 "free: multiple frees") at ../../kern/kern_shutdown.c:430 #2 0xf0135593 in free (addr=0x0, type=0xf022a380) at ../../kern/kern_malloc.c:334 #3 0xf01a0845 in nfsrv_dorec (slp=0xf0a34300, nfsd=0xf087f600, ndp=0xf4184e38) at ../../nfs/nfs_socket.c:2235 #4 0xf01a47d0 in nfssvc_nfsd (nsd=0xf4184e94, argp=0x8071afc "", p=0xf414afc0) at ../../nfs/nfs_syscalls.c:537 #5 0xf01a43ed in nfssvc (p=0xf414afc0, uap=0xf4184f94) at ../../nfs/nfs_syscalls.c:342 #6 0xf01f8d5f in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 6, tf_esi = 1, tf_ebp = -272638524, tf_isp = -199733276, tf_ebx = 0, tf_edx = -272638920, tf_ecx = 0, tf_eax = 155, tf_trapno = 12, tf_err = 2, tf_eip = 134519048, tf_cs = 31, tf_eflags = 646, tf_esp = -272638916, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #7 0xf01ef02c in Xint0x80_syscall () (kgdb) frame 2 #2 0xf0135593 in free (addr=0x0, type=0xf022a380) at ../../kern/kern_malloc.c:334 334 panic("free: multiple frees"); (kgdb) frame 3 #3 0xf01a0845 in nfsrv_dorec (slp=0xf0a34300, nfsd=0xf087f600, ndp=0xf4184e38) at ../../nfs/nfs_socket.c:2235 2235 FREE(nam, M_SONAME); (kgdb) frame 4 #4 0xf01a47d0 in nfssvc_nfsd (nsd=0xf4184e94, argp=0x8071afc "", p=0xf414afc0) at ../../nfs/nfs_syscalls.c:537 537 error = nfsrv_dorec(slp, nfsd, &nd); (kgdb) frame 5 #5 0xf01a43ed in nfssvc (p=0xf414afc0, uap=0xf4184f94) at ../../nfs/nfs_syscalls.c:342 342 error = nfssvc_nfsd(nsd, uap->argp, p); dmesg produces: ejh@tds.eas.slu.edu:/usr/src/sys/compile/GG Timecounter "i8254" frequency 1193182 Hz cost 1443 ns Timecounter "TSC" frequency 300682610 Hz cost 78 ns CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 62853120 (61380K bytes) Bad DMI table checksum! Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x04 on pci0.1.0 chip2: rev 0x00 on pci0.3.0 chip3: rev 0xb4 on pci0.7.0 ide_pci0: rev 0x20 int a irq 0 on pci0.15.0 ide_pci: controller is simplex, no DMA on secondary channel ide_pci1: rev 0x01 int a irq 10 on pci0.16.0 ide_pci1: adding drives to controller 4: 4 5 6 7 tx0: rev 0x06 int a irq 11 on pci0.18.0 tx0: address 00:e0:29:24:4f:18, type SMC9432TX, Auto-Neg 10Mbps vga0: rev 0x06 int a irq 0 on pci0.20.0 Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 11349MB (23243472 sectors), 23059 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 wdc2 at 0xdfa0-0xdfa7 flags 0xa0ffa0ff on isa ide_pci: generic_dmainit dfa0:1: warning, IDE controller timing not set wdc2: unit 0 (wd4): , DMA, 32-bit, multi-block-16 wd4: 11349MB (23243472 sectors), 23059 cyls, 16 heads, 63 S/T, 512 B/S ide_pci: generic_dmainit dfa0:1: warning, IDE controller timing not set wdc2: unit 1 (wd5): , DMA, 32-bit, multi-block-16 wd5: 11349MB (23243472 sectors), 23059 cyls, 16 heads, 63 S/T, 512 B/S wdc3 at 0xdf90-0xdf97 flags 0xa0ffa0ff on isa ide_pci: generic_dmainit df90:1: warning, IDE controller timing not set wdc3: unit 0 (wd6): , DMA, 32-bit, multi-block-16 wd6: 11349MB (23243472 sectors), 23059 cyls, 16 heads, 63 S/T, 512 B/S ide_pci: generic_dmainit df90:1: warning, IDE controller timing not set wdc3: unit 1 (wd7): , DMA, 32-bit, multi-block-16 wd7: 11349MB (23243472 sectors), 23059 cyls, 16 heads, 63 S/T, 512 B/S adv0 not found at 0x330 npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers changing root device to wd0s1a WARNING: / was not properly dismounted ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated --- eric haug Saint Louis Univ. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 10:16:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09575 for freebsd-current-outgoing; Tue, 20 Oct 1998 10:16:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09562 for ; Tue, 20 Oct 1998 10:16:04 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.05 #3) id 0zVfLA-00006Q-00; Tue, 20 Oct 1998 18:13:00 +0100 Date: Tue, 20 Oct 1998 18:13:00 +0100 From: Ben Smithurst To: Peter Wemm Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic Message-ID: <19981020181300.A293@scientia.demon.co.uk> References: <199810180305.LAA23805@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199810180305.LAA23805@spinner.netplex.com.au> User-Agent: Mutt/0.94.12i (FreeBSD 3.0-BETA i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > Hmm, you don't have MATH_EMULATE or GPL_MATH_EMULATE options turned on by > any chance, do you? Take them out if so. I had the same problem, and removing GPL_MATH_EMULATE fixed it, thanks. But, is removing that likely to affect anything else? -- Ben Smithurst ben@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 10:50:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12465 for freebsd-current-outgoing; Tue, 20 Oct 1998 10:50:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12460 for ; Tue, 20 Oct 1998 10:50:42 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id NAA29023; Tue, 20 Oct 1998 13:52:22 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Tue, 20 Oct 1998 13:52:22 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: HighWind Software Information cc: current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem In-Reply-To: <199810201618.MAA26576@highwind.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG urk, problem: pthread_cond_broadcast() locks, unqueues, unlocks, schedules then loops. this can cause incorrect behavior when: a thread initiates a broadcast and is prempted after unlocking but before emptying the queue, then during the loop to unqueue and schedule another thread waits on the conditional the thread that joins after the broadcast will be signaled, the broadcast should be atomic. a solution is to store the number of items in a queue. then the broadcast function can malloc that number of pthread_t objects and dequeue them into an array then release the lock and loop while scheduling. but this also causes problems if the sheduling is pre-empted and a thread is scheduled twice. i'll see what i can do about this, i think the real real solution is for the scheduler to be able to atomically dequeue a number of threads in a critical section of code. i apologize for my zealousness that lead to the not correct patch, i also apologize for thinking aloud on this list, but i'm hoping to bring up some valid points for those with more experiance to make sure all the bases are covered. sorry, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 20 Oct 1998, HighWind Software Information wrote: > > Hmmm. Now we got 3 patches. > > I am a little wary about Alfred's "broadcast" patch. Seems premature > optimization. I'd rather have something that is conservative first. > > Can someone with commit priviledges take a peek at this and add one > of these to the source? > > -Rob > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 11:05:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14390 for freebsd-current-outgoing; Tue, 20 Oct 1998 11:05:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14384 for ; Tue, 20 Oct 1998 11:05:52 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id NAA11025; Tue, 20 Oct 1998 13:05:04 -0500 (CDT) Message-Id: <199810201805.NAA11025@ns.tar.com> From: "Richard Seaman, Jr." To: "Jason Evans" Cc: "current@freebsd.org" Date: Tue, 20 Oct 98 13:05:03 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998 18:03:22 -0700 (PDT), Jason Evans wrote: >Hmm, your test case is very similar to some code that was causing deadlock >for me. However, I boiled it down to the following code as being the >actual bug. We may be seeing the same thing (but maybe not; I haven't had >time to dig into this all the way). > >Jason I think the problem in your code is that you expect to be able to recursively lock a mutex in the same thread, using the default mutex type. I don't think this is a bug, since the "default" mutex type is implementation defined, if I'm not mistaken. Try the following adjustments to your code: /* -*-mode:c-*- */ #ifndef _REENTRANT # define _REENTRANT #endif #include #include #include #include #include int pthread_mutexattr_setkind_np(pthread_mutexattr_t *attr, int kind); int main() { pthread_mutex_t mutex; pthread_mutexattr_t attr; int error; pthread_mutexattr_init (&attr); pthread_mutexattr_setkind_np (&attr, MUTEX_TYPE_COUNTING_FAST); error = pthread_mutex_init(&mutex, &attr); pthread_mutexattr_destroy (&attr); if (error) { fprintf(stderr, "Error in pthread_mutex_init(): %s\n", strerror(error)); exit(1); } fprintf(stderr, "About to lock mutex first time.\n"); error = pthread_mutex_lock(&mutex); if (error) { fprintf(stderr, "Error in pthread_mutex_lock(): %s\n", strerror(error)); exit(1); } fprintf(stderr, "About to lock mutex second time; expect deadlock.\n"); error = pthread_mutex_lock(&mutex); if (error) { fprintf(stderr, "Error in pthread_mutex_lock(): %s\n", strerror(error)); exit(1); } fprintf(stderr, "Wow, no deadlock.\n"); error = pthread_mutex_destroy(&mutex); if (error) { fprintf(stderr, "Error in pthread_mutex_destroy(): %s\n", strerror(error)); exit(1); } return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 11:39:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17598 for freebsd-current-outgoing; Tue, 20 Oct 1998 11:39:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17591 for ; Tue, 20 Oct 1998 11:39:33 -0700 (PDT) (envelope-from mishania@skraldespand.demos.su) Received: by skraldespand.demos.su id WAA01373; (8.8.8/D) Tue, 20 Oct 1998 22:39:04 +0400 (MSD) Message-ID: <19981020223904.26635@demos.su> Date: Tue, 20 Oct 1998 22:39:04 +0400 From: "Mikhail A. Sokolov" To: current@FreeBSD.ORG Subject: ufd_dirbad and mp_lock() and happy reboots etc. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. X-Useless-Header: Look ma! It's a # sign! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, lately I was stuck to ufs_baddir on /, right as it in ufs_lookup.c ("mangled entry"). It took me some 2 days of constant hitting reset button to realize it since the machine would either not reboot and just "freeze" or reboot without giving a dump or something. Once I was lucky to see that the inode is mangled, since it finally got frozen when it was trying to sync disks, reboot and failed with mp_lock() on CPU0. I wonder why would it be so shy when it a) has broken FS, b) can't reboot properly, c) can't reboot when has SMP in use? The machine is ELF 3.0R, kernel aout, but it doesn't make any difference since it was the same during those days it was 3.0-current as of 24.04/21.05-1998 during last week or two. I also broke the reset button on the machine since the attitude to it got a bit less gentle as it was, but that's another issue. Thanks in advance, -- -mishania, who's gonna make a slogan 'a localized culprit of reboot is 99.999% of fix' his fetish. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 12:39:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24050 for freebsd-current-outgoing; Tue, 20 Oct 1998 12:39:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24044 for ; Tue, 20 Oct 1998 12:39:47 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id NAA29092; Tue, 20 Oct 1998 13:32:28 -0600 (MDT) Date: Tue, 20 Oct 1998 13:32:28 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199810201932.NAA29092@narnia.plutotech.com> To: Vijay Ramasubramanian cc: current@FreeBSD.ORG Subject: Re: Installation probs w/3.0 In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > Briefly stated, I was always getting installation crashes around the 40th > chunk with messages that indicated FS corruption (stuff such as > ufs_dirbad, ffs_alloccg: bad map, and so on). > > My hardware config is as below: > > AMD K6-233 (one of the latest revisions) > Intel TX chipset motherboard w/512KB cache > 64 MB SDRAM in 1 DIMM > AdvanSys ABP-940 SCSI host adapter, SCSI ID 7 Is this an ABP-940, an ABP-940U, an ABP-940UA, or an ABP-940UW? I have all three here, and I want to ensure that I use the same board you have to reproduce the bug. > IBM DCAS 2.2 GB Ultra SCSI drive, SCSI ID 0 > IBM DCAS 2.2 GB Ultra SCSI drive, SCSI ID 1 > Fujitsu 405 MB Fast SCSI-2 drive, SCSI ID 2 Which of these drives is being accessed at the time of the failure? Does the Fujitsu claim to support tagged queuing? Are there any SCSI error messages printed on the console? You can get this information by hitting and once you hit the install screen to see the kernel messages for the drives. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 13:16:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27823 for freebsd-current-outgoing; Tue, 20 Oct 1998 13:16:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from orkan.canonware.com (canonware.com [206.184.206.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27791 for ; Tue, 20 Oct 1998 13:16:14 -0700 (PDT) (envelope-from jasone@canonware.com) Received: from localhost (jasone@localhost) by orkan.canonware.com (8.8.7/8.8.7) with SMTP id NAA11586; Tue, 20 Oct 1998 13:16:08 -0700 Date: Tue, 20 Oct 1998 13:16:07 -0700 (PDT) From: Jason Evans To: "Richard Seaman, Jr." cc: "current@freebsd.org" Subject: Re: Another Serious libc_r problem In-Reply-To: <199810201805.NAA11025@ns.tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, Richard Seaman, Jr. wrote: > On Mon, 19 Oct 1998 18:03:22 -0700 (PDT), Jason Evans wrote: > > >Hmm, your test case is very similar to some code that was causing deadlock > >for me. However, I boiled it down to the following code as being the > >actual bug. We may be seeing the same thing (but maybe not; I haven't had > >time to dig into this all the way). > > > >Jason > > I think the problem in your code is that you expect to be able to recursively > lock a mutex in the same thread, using the default mutex type. I don't > think this is a bug, since the "default" mutex type is implementation > defined, if I'm not mistaken. Did you actually run the code? The point I was trying to make is that the code does _not_ deadlock for the default (fast mutex). I'm not sure that this is a bug, but it is different than the behavior I've seen on other systems. Can someone say whether this is allowed by the POSIX spec? Jason Jason Evans Email: [jasone@canonware.com] Web: [http://www.canonware.com/~jasone] Home phone: [(650) 856-8204] Work phone: [(415) 808-8742] Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 13:26:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28952 for freebsd-current-outgoing; Tue, 20 Oct 1998 13:26:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28945 for ; Tue, 20 Oct 1998 13:26:36 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.8.8) with ESMTP id QAA21145 for ; Tue, 20 Oct 1998 16:26:05 -0400 (EDT) (envelope-from scrappy@hub.org) Date: Tue, 20 Oct 1998 16:25:55 -0400 (EDT) From: "Marc G. Fournier" To: freebsd-current@FreeBSD.ORG Subject: Invalid option for compiler...? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trying to build a new kernel, and I get the following error: hub# make depend cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../i386/i386/genassym.c cc1: Invalid option `-fformat-extensions' *** Error code 1 This is with GCC 2.7.2.1 of about July 15th or so... Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@{postgresql|isc}.org ICQ#7615664 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 15:01:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08832 for freebsd-current-outgoing; Tue, 20 Oct 1998 15:01:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lepton.nuc.net (lepton.nuc.net [204.49.61.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08825 for ; Tue, 20 Oct 1998 15:01:35 -0700 (PDT) (envelope-from wheelman@nuc.net) Received: from electron.nuc.net (dhcp1.nuc.net [204.49.61.49]) by lepton.nuc.net (8.8.8/8.8.8) with SMTP id RAA13280; Tue, 20 Oct 1998 17:00:51 -0500 (CDT) (envelope-from wheelman@nuc.net) From: "Jaime Bozza" To: "Bruce Albrecht" Cc: Subject: RE: newfs problems, more information: Date: Tue, 20 Oct 1998 16:59:04 -0500 Message-ID: <003801bdfc74$da58cae0$313d31cc@electron.nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-reply-to: <13868.3117.390224.376379@zuhause.zuhause.mn.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You do it the same way you do it for any other disk. You create the > partition information, and do a disklabel for ccd0 to write the label, > and then you newfs each partition, ccd0d, ccd0e, ... Are you saying you can have subpartitions within a ccd? (Which in itself is formed by partitions on the original drives) That could be pretty interesting. I've fiddled with disklabel and was finally able to create a disklabel for a ccd. But I haven't been able to create a partition 'e' ... disklabel returns "Bad partition name". I was able to create an 'a' partition though. Jaime Bozza Nucleus Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 15:05:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09194 for freebsd-current-outgoing; Tue, 20 Oct 1998 15:05:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lepton.nuc.net (lepton.nuc.net [204.49.61.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09181 for ; Tue, 20 Oct 1998 15:05:24 -0700 (PDT) (envelope-from wheelman@nuc.net) Received: from electron.nuc.net (dhcp1.nuc.net [204.49.61.49]) by lepton.nuc.net (8.8.8/8.8.8) with SMTP id RAA13368; Tue, 20 Oct 1998 17:04:40 -0500 (CDT) (envelope-from wheelman@nuc.net) From: "Jaime Bozza" To: "Doug White" Cc: Subject: RE: newfs problems, more information: Date: Tue, 20 Oct 1998 17:02:53 -0500 Message-ID: <003901bdfc75$62bbf420$313d31cc@electron.nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-reply-to: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In disklabel -e, just copy the 'c' line and change the c to h. > Then newfs h. Doing that causes disklabel to return "bad partition name". Jaime Bozza Nucleus Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 15:06:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09305 for freebsd-current-outgoing; Tue, 20 Oct 1998 15:06:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lepton.nuc.net (lepton.nuc.net [204.49.61.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09299 for ; Tue, 20 Oct 1998 15:06:05 -0700 (PDT) (envelope-from wheelman@nuc.net) Received: from electron.nuc.net (dhcp1.nuc.net [204.49.61.49]) by lepton.nuc.net (8.8.8/8.8.8) with SMTP id RAA13392; Tue, 20 Oct 1998 17:05:25 -0500 (CDT) (envelope-from wheelman@nuc.net) From: "Jaime Bozza" To: "Doug White" Cc: Subject: RE: newfs problems, more information: Date: Tue, 20 Oct 1998 17:03:38 -0500 Message-ID: <003a01bdfc75$7d8ce200$313d31cc@electron.nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-reply-to: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In disklabel -e, just copy the 'c' line and change the c to h. > Then newfs h. Nevermind. I had to increase the number of partitions and then it worked. Thanks. Jaime Bozza Nucleus Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 15:06:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09357 for freebsd-current-outgoing; Tue, 20 Oct 1998 15:06:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09351 for ; Tue, 20 Oct 1998 15:06:55 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id RAA15321; Tue, 20 Oct 1998 17:06:19 -0500 (CDT) Message-Id: <199810202206.RAA15321@ns.tar.com> From: "Richard Seaman, Jr." To: "Jason Evans" Cc: "current@freebsd.org" Date: Tue, 20 Oct 98 17:06:19 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998 13:16:07 -0700 (PDT), Jason Evans wrote: >Did you actually run the code? No. >The point I was trying to make is that the >code does _not_ deadlock for the default (fast mutex). Yes, I missed your point. >I'm not sure that >this is a bug, but it is different than the behavior I've seen on other >systems. Can someone say whether this is allowed by the POSIX spec? It is my impression that the X/Open XSH5 standard allows the default mutex type to be implementation dependent. The "NORMAL" type, equivalent to "fast", should not do error checking and not report deadlocks from recursion, and should hang if a thread tries to lock a mutex it owns. However, DEFAULT does not have to be NORMAL. As to the POSIX spec, I'm not positive. Butenhof's book "Programming with POSIX Threads" states (page 52): "You cannot lock a mutex when the calling thread already has that mutex locked. The result ... may be an error return (EDEAKLK), or it may be a self-deadlock." I believe that Butenhof intended his book to describe the POSIX 1003.1c-1995 standard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 15:21:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10651 for freebsd-current-outgoing; Tue, 20 Oct 1998 15:21:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10641 for ; Tue, 20 Oct 1998 15:21:22 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id AAA19490; Wed, 21 Oct 1998 00:20:54 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA17270; Wed, 21 Oct 1998 00:20:54 +0200 (MET DST) Message-ID: <19981021002053.38506@follo.net> Date: Wed, 21 Oct 1998 00:20:53 +0200 From: Eivind Eklund To: Jason Evans , "Richard Seaman, Jr." Cc: "current@freebsd.org" Subject: Re: Another Serious libc_r problem References: <199810201805.NAA11025@ns.tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Jason Evans on Tue, Oct 20, 1998 at 01:16:07PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 20, 1998 at 01:16:07PM -0700, Jason Evans wrote: > On Tue, 20 Oct 1998, Richard Seaman, Jr. wrote: > > > On Mon, 19 Oct 1998 18:03:22 -0700 (PDT), Jason Evans wrote: > > > > >Hmm, your test case is very similar to some code that was causing deadlock > > >for me. However, I boiled it down to the following code as being the > > >actual bug. We may be seeing the same thing (but maybe not; I haven't had > > >time to dig into this all the way). > > > > > >Jason > > > > I think the problem in your code is that you expect to be able to recursively > > lock a mutex in the same thread, using the default mutex type. I don't > > think this is a bug, since the "default" mutex type is implementation > > defined, if I'm not mistaken. > > Did you actually run the code? The point I was trying to make is that the > code does _not_ deadlock for the default (fast mutex). I'm not sure that > this is a bug, but it is different than the behavior I've seen on other > systems. Can someone say whether this is allowed by the POSIX spec? It is allowed by SS2, at least. SS2 creates a PTHREAD_MUTEX_DEFAULT by default, which hardly has any restrictions. A PTHREAD_MUTEX_NORMAL has to deadlock (said so one place in the text - it is slightly inconsistent with the text other places in SS2, which say it 'may' deadlock). There is also a something I believe to be a bug in the handling of MUTEX_TYPE_COUNTING_FAST - it needs to be mutex_unlock()'ed one more time than it is mutex_lock()'ed. The following patch will make it work correctly (I hope to have this in the tree sometime tomorrow): --- uthread_mutex.c.EE Tue Oct 20 22:01:46 1998 +++ uthread_mutex.c Tue Oct 20 22:34:20 1998 @@ -383,17 +383,19 @@ ret = EINVAL; } /* Check if there are still counts: */ - else if ((*mutex)->m_data.m_count) { + else if ((*mutex)->m_data.m_count > 1) { /* Decrement the count: */ (*mutex)->m_data.m_count--; - } - /* - * Get the next thread from the queue of threads waiting on - * the mutex: - */ - else if (((*mutex)->m_owner = _thread_queue_deq(&(*mutex)->m_queue)) != NULL) { - /* Allow the new owner of the mutex to run: */ - PTHREAD_NEW_STATE((*mutex)->m_owner,PS_RUNNING); + } else { + (*mutex)->m_data.m_count = 0; + /* + * Get the next thread from the queue of threads waiting on + * the mutex: + */ + if (((*mutex)->m_owner = _thread_queue_deq(&(*mutex)->m_queue)) != NULL) { + /* Allow the new owner of the mutex to run: */ + PTHREAD_NEW_STATE((*mutex)->m_owner,PS_RUNNING); + } } break; There will be a slight fuzz when you apply this; don't worry, this is due to it being between two working versions of my source (I've also got patches to add support for the SS2 pthread_mutextattr_settype() call, but these are tested much yet). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 16:19:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15547 for freebsd-current-outgoing; Tue, 20 Oct 1998 16:19:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15542 for ; Tue, 20 Oct 1998 16:19:21 -0700 (PDT) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id DAA32277; Wed, 21 Oct 1998 03:11:34 +0400 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.1/8.9.1) with ESMTP id DAA02588; Wed, 21 Oct 1998 03:12:40 +0400 (MSD) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199810202312.DAA02588@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Daniel Eischen cc: lists@tar.com, tejblum@arc.hq.cti.ru, current@FreeBSD.ORG, info@highwind.com Subject: Re: Another Serious libc_r problem In-reply-to: Your message of "Tue, 20 Oct 1998 11:45:50 EDT." <199810201545.LAA21709@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Oct 1998 03:12:40 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > > I don't think you want to wrap anything other than the condtion > queue and dequeue with the condition spin locks; they should be > used just to protect changing the condition variable. > > As long as you enqueue the condition variable before you unlock the > mutex, there should be no race conditions. > Well, specs says that mutex unlocking and enqueuing are atomic, so we may put it in the code ;-|. (Note also that mutex_unlock may fail.) Anyway, what if a rescheduling happens just after thread was enqueued for condition variable, and some other thread signaled the condition? Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 16:31:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16709 for freebsd-current-outgoing; Tue, 20 Oct 1998 16:31:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16703 for ; Tue, 20 Oct 1998 16:31:07 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id BAA18625 for freebsd-current@FreeBSD.ORG; Wed, 21 Oct 1998 01:30:40 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 179321548; Wed, 21 Oct 1998 00:50:45 +0200 (CEST) Date: Wed, 21 Oct 1998 00:50:44 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Fonts for syscons Message-ID: <19981021005044.A6295@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4731 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A long time ago I committed the ISO-8859-1 thin font usable for syscons. This font (iso-thin-8x16) is only partially ISO-8859-1 as it lacks some semi-graphic characters and some other are misplaced. I have updated this font and also made a Latin9 (aka ISO-8859-15) version of this font. The "problem" I have is the one about naming. We're not really consistent here: -r--r--r-- 1 root wheel 5680 Dec 21 1996 iso-8859-2-8x16.fnt -r--r--r-- 1 root wheel 5673 Dec 21 1996 iso-8x16.fnt -r--r--r-- 1 root wheel 5678 Aug 26 1997 iso-thin-8x16.fnt -r--r--r-- 1 root wheel 5675 Oct 5 1997 iso02-8x16.fnt iso-8859-1-thin-8x16.fnt seems a bit long. What about iso01-thin-8x16.fnt ? (the new one would be named iso15-thin-8x16.fnt of course) Any bright idea here ? I used a small script to turn the BDF version from the X server into a raw font file for syscons. If anyone's interested, just ask. -rwxr-xr-x 1 roberto staff 2112 21 oct 00:34 bdftoscn.pl* -rwxr-xr-x 1 roberto staff 598 21 oct 00:20 displayfn.pl* -rwxr-xr-x 1 roberto staff 1609 21 oct 00:30 scntobdf.pl* bdftoscn.pl is a very old script of mine (circa 93) I made to convert X fonts into ones suitable for the 386BSD co(4) console driver... The latin9 font is rather important for us Western Europe users as it has some missing characters (Euro, 'o' and 'e' together and some others) that were forgotten in latin1. PS: xmbdfed rulez. That's a great program. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 17:30:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22453 for freebsd-current-outgoing; Tue, 20 Oct 1998 17:30:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-25.ppp.wenet.net [206.15.85.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22448 for ; Tue, 20 Oct 1998 17:30:22 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id OAA01173; Tue, 20 Oct 1998 14:53:48 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 20 Oct 1998 14:53:43 -0700 (PDT) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: "Marc G. Fournier" cc: freebsd-current@FreeBSD.ORG Subject: Re: Invalid option for compiler...? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, Marc G. Fournier wrote: > > Trying to build a new kernel, and I get the following error: > > hub# make depend > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -g -nostdinc > -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h > ../../i386/i386/genassym.c > cc1: Invalid option `-fformat-extensions' > *** Error code 1 -fformat-extensions is used to quash some warnings that might be generated by the odd format identifiers in the kernel. As long as you're not using -Werror, it's safe to remove this (and is the only way to go with a non stock cc). The "correct" solution would be to rebuild cc1 (a make world will do this as well as rebuild other parts required for use of a post 3.0-R kernel). - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 17:43:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23656 for freebsd-current-outgoing; Tue, 20 Oct 1998 17:43:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA23616 for ; Tue, 20 Oct 1998 17:42:59 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 6826 invoked by uid 1001); 21 Oct 1998 00:42:24 +0000 (GMT) To: freebsd-current@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Problems with Digital server with P-166 and Neptune chipset In-Reply-To: Your message of "Mon, 19 Oct 1998 23:36:15 +0200" References: <17857.908832975@verdi.nethelp.no> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 21 Oct 1998 02:42:24 +0200 Message-ID: <6824.908930544@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > I'm trying to get FreeBSD 3.0 to run reliably on a Digital server with > Neptune chipset - so far without great success. (2.2.7, btw, wouldn't > install at all. 3.0 installed with some effort). I now have some more info. Built a kernel with debug info, built an aout gdb. I have two identical machines running 3.0-RELEASE now, and both of them are crashing the same way (page fault in kernel mode) and in the same place (the zalloc inline routine in vm/vm_zone.h). Here are two backtraces, one from each machine. These both happened at the same time, namely when running /etc/daily at 02.00. In both cases, the kernel is trying to follow a null pointer (z) at vm/vm_zone.h line 87: item = z->zitems; However, the zalloc inline routine is called from vmspace_alloc: vm = zalloc(vmspace_zone); and here the vmspace_zone seems to have a sensible value, 0xf0dd9980. I'm going to try to recompile the kernel with DIAGNOSTIC enabled to see if I can get some more info. Meanwhile, can anybody suggest why z is null in zalloc when vmspace_zone isn't? Missing spl protection? Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- Machine 1: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x7200720 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01cc637 stack pointer = 0x10:0xf882c970 frame pointer = 0x10:0xf882c978 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 286 (cron) interrupt mask = trap number = 12 panic: page fault syncing disks... 4 4 done ... #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 268 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 #1 0xf012e62b in panic (fmt=0xf01e651f "page fault") at ../../kern/kern_shutdown.c:430 #2 0xf01e716d in trap_fatal (frame=0xf882c934) at ../../i386/i386/trap.c:879 #3 0xf01e6c00 in trap_pfault (frame=0xf882c934, usermode=0) at ../../i386/i386/trap.c:772 #4 0xf01e685f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -126140544, tf_esi = -125645156, tf_ebp = -125646472, tf_isp = -125646500, tf_ebx = -126123776, tf_edx = 119539488, tf_ecx = -253912704, tf_eax = 42, tf_trapno = 12, tf_err = 0, tf_eip = -266549705, tf_cs = 8, tf_eflags = 66199, tf_esp = -126123776, tf_ss = -125645156}) at ../../i386/i386/trap.c:396 #5 0xf01cc637 in vmspace_alloc (min=0, max=4022329344) at ../../vm/vm_zone.h:87 #6 0xf01cebdf in vmspace_exec (p=0xf87b3f80) at ../../vm/vm_map.c:2220 #7 0xf0127227 in exec_new_vmspace (imgp=0xf882ce9c) at ../../kern/kern_exec.c:443 #8 0xf011d598 in exec_elf_imgact (imgp=0xf882ce9c) at ../../kern/imgact_elf.c:468 #9 0xf0126c97 in execve (p=0xf87b3f80, uap=0xf882cf94) at ../../kern/kern_exec.c:176 #10 0xf01e73ff in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 134689062, tf_esi = -272640068, tf_ebp = -272640040, tf_isp = -125644828, tf_ebx = 671929380, tf_edx = -272640012, tf_ecx = 3, tf_eax = 59, tf_trapno = 0, tf_err = 2, tf_eip = 671680280, tf_cs = 31, tf_eflags = 582, tf_esp = -272640084, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #11 0xf01da86c in Xint0x80_syscall () #12 0x804a5bf in ?? () #13 0x804a20a in ?? () #14 0x804abef in ?? () Machine 2: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x7200720 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01cc637 stack pointer = 0x10:0xf8814ec4 frame pointer = 0x10:0xf8814ecc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 479 (sh) interrupt mask = trap number = 12 panic: page fault syncing disks... 23 17 4 done ... #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 #1 0xf012e62b in panic (fmt=0xf01e651f "page fault") at ../../kern/kern_shutdown.c:430 #2 0xf01e716d in trap_fatal (frame=0xf8814e88) at ../../i386/i386/trap.c:879 #3 0xf01e6c00 in trap_pfault (frame=0xf8814e88, usermode=0) at ../../i386/i386/trap.c:772 #4 0xf01e685f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -126139584, tf_esi = -126139584, tf_ebp = -125743412, tf_isp = -125743440, tf_ebx = 20, tf_edx = 119539488, tf_ecx = -253912704, tf_eax = 42, tf_trapno = 12, tf_err = 0, tf_eip = -266549705, tf_cs = 8, tf_eflags = 66199, tf_esp = 20, tf_ss = -126139584}) at ../../i386/i386/trap.c:396 #5 0xf01cc637 in vmspace_alloc (min=0, max=4022329344) at ../../vm/vm_zone.h:87 #6 0xf01ce9d0 in vmspace_fork (vm1=0xf87b8100) at ../../vm/vm_map.c:2122 #7 0xf01cb98f in vm_fork (p1=0xf87b4340, p2=0xf87b3f80, flags=20) at ../../vm/vm_glue.c:222 #8 0xf01285dc in fork1 (p1=0xf87b4340, flags=20) at ../../kern/kern_fork.c:403 #9 0xf0128091 in fork (p=0xf87b4340, uap=0xf8814f94) at ../../kern/kern_fork.c:96 #10 0xf01e73ff in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 134877312, tf_esi = 134857940, tf_ebp = -272639248, tf_isp = -125743132, tf_ebx = 134857880, tf_edx = -272639248, tf_ecx = 134857688, tf_eax = 2, tf_trapno = 12, tf_err = 2, tf_eip = 134621760, tf_cs = 31, tf_eflags = 514, tf_esp = -272639272, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #11 0xf01da86c in Xint0x80_syscall () #12 0x804acdd in ?? () #13 0x804a852 in ?? () #14 0x804aef6 in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 17:46:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24149 for freebsd-current-outgoing; Tue, 20 Oct 1998 17:46:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24140 for ; Tue, 20 Oct 1998 17:46:50 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id UAA17914; Tue, 20 Oct 1998 20:46:19 -0400 (EDT) Message-ID: <19981020204619.F16673@netmonger.net> Date: Tue, 20 Oct 1998 20:46:19 -0400 From: Christopher Masto To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: cvsup and file permissions References: <19981015194840.A16439@netmonger.net> <199810160028.RAA02305@dingo.cdrom.com> <19981019180508.A26343@netmonger.net> <199810201452.HAA04158@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810201452.HAA04158@austin.polstra.com>; from John Polstra on Tue, Oct 20, 1998 at 07:52:28AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 20, 1998 at 07:52:28AM -0700, John Polstra wrote: > In article <19981019180508.A26343@netmonger.net>, > Christopher Masto wrote: > > > Regardless, it would be nice to have a way to tell cvsup not to sync > > permissions. > > That feature's on my to-do list. I think I might actually get some > time to work on CVSup again in the not-to-distant future. > > Meanwhile, try changing the umask as I suggested in my other mail. > I'm pretty sure that will work. The umask already _is_ 002. Perhaps I'm misunderstanding something, but doesn't the umask simply mask the bits that are assigned when a file is created? It seems pretty clear that CVSup is actually syncing with the master repository by calling chmod(). This is what I see every time I change permissions here and then re-cvsup: SetAttrs src/etc/sendmail/freebsd.mc,v SetAttrs src/etc/sendmail/freefall.mc,v SetAttrs src/gnu/games/chess/Xchess/scrollText/scrollText.c,v -> Attic Maybe I'll install the M3 compiler tonight and see what I can do. -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ You're either a friend or a foe, and you're an enemy now. - STEVE BALLMER, Executive Vice President, Sales & Support, Microsoft, to Pacific Bell CEO David Dorman after Pacific Bell chose Netscape's Web software over Microsoft's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 18:09:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26182 for freebsd-current-outgoing; Tue, 20 Oct 1998 18:09:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26173 for ; Tue, 20 Oct 1998 18:09:50 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id UAA04880; Tue, 20 Oct 1998 20:09:22 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id TAA02369; Tue, 20 Oct 1998 19:56:35 -0500 (CDT) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13869.12610.899877.506387@zuhause.zuhause.mn.org> Date: Tue, 20 Oct 1998 19:56:34 -0500 (CDT) To: "Jaime Bozza" Cc: Subject: RE: newfs problems, more information: In-Reply-To: <003801bdfc74$da58cae0$313d31cc@electron.nuc.net> References: <13868.3117.390224.376379@zuhause.zuhause.mn.org> <003801bdfc74$da58cae0$313d31cc@electron.nuc.net> X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaime Bozza writes: > > You do it the same way you do it for any other disk. You create the > > partition information, and do a disklabel for ccd0 to write the label, > > and then you newfs each partition, ccd0d, ccd0e, ... > > Are you saying you can have subpartitions within a ccd? (Which in itself > is formed by partitions on the original drives) > > That could be pretty interesting. I've fiddled with disklabel and was > finally able to create a disklabel for a ccd. But I haven't been able to > create a partition 'e' ... disklabel returns "Bad partition name". I was > able to create an 'a' partition though. I never had any problem doing so. Here's my ccd's disklabel entry: ccdx32:\ :ty=winchester:dt=SCSI:rm#5411:\ :se#512:nc#2416:nt#125:ns#48:\ :oc#0:pc#14496000:\ :ob#2:pb#287486:tb=swap:\ :od#287488:pd#503808:td=4.2BSD:\ :oe#791296:pe#2801664:te=4.2BSD:\ :of#3592960:pf#5402624:tf=4.2BSD:\ :og#8995584:pg#5496832:tg=4.2BSD: I've been told that you're better off not using a ccd partition for swap, but I haven't gotten around to dumping everything, repartitioning the raw drives, etc., to do swap partitions on each drive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 18:25:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28082 for freebsd-current-outgoing; Tue, 20 Oct 1998 18:25:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28075 for ; Tue, 20 Oct 1998 18:25:48 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id SAA07770; Tue, 20 Oct 1998 18:25:18 -0700 (PDT) (envelope-from jdp) Message-Id: <199810210125.SAA07770@austin.polstra.com> To: Christopher Masto cc: current@FreeBSD.ORG Subject: Re: cvsup and file permissions In-reply-to: Your message of "Tue, 20 Oct 1998 20:46:19 EDT." <19981020204619.F16673@netmonger.net> Date: Tue, 20 Oct 1998 18:25:18 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Meanwhile, try changing the umask as I suggested in my other mail. > > I'm pretty sure that will work. > > The umask already _is_ 002. Perhaps I'm misunderstanding something, We are miscommunicating somehow, because it _does_ work. > but doesn't the umask simply mask the bits that are assigned when a > file is created? No. It also affects which bits CVSup pays attention to when it is determining whether the two files are the "same". I.e., CVSup looks at the umask and does something with it. Again, it _does_ work. Watch this. First I will get some files under a umask of 22: vashon$ umask 22 vashon$ cvsup -1gL2 -P m -i src/bin/cat supfile Parsing supfile "supfile" Looking up address of cvsup.freebsd.org Connecting to cvsup.freebsd.org Connected to cvsup.freebsd.org Server software version: REL_15_4_2 Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection src-bin/cvs Mkdir src Mkdir src/bin Mkdir src/bin/cat Create src/bin/cat/Makefile,v Create src/bin/cat/cat.1,v Create src/bin/cat/cat.c,v SetAttrs src/bin/cat SetAttrs src/bin SetAttrs src Shutting down connection to server Finished successfully And they come out with modes like you're getting: vashon$ ls -lRF src total 1 drwxr-xr-x 3 jdp jdp 512 Oct 20 18:14 bin/ src/bin: total 1 drwxr-xr-x 2 jdp jdp 512 Oct 20 18:14 cat/ src/bin/cat: total 24 -r--r--r-- 1 jdp jdp 1651 Oct 15 23:06 Makefile,v -r--r--r-- 1 jdp jdp 9380 Oct 15 23:06 cat.1,v -r--r--r-- 1 jdp jdp 12201 Oct 15 23:06 cat.c,v Now I change my umask to 2 and do another update: vashon$ umask 2 vashon$ cvsup -1gL2 -P m -i src/bin/cat supfile Parsing supfile "supfile" Looking up address of cvsup.freebsd.org Connecting to cvsup.freebsd.org Connected to cvsup.freebsd.org Server software version: REL_15_4_2 Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection src-bin/cvs SetAttrs src/bin/cat SetAttrs src/bin SetAttrs src Shutting down connection to server Finished successfully And now the files have the modes that you desire: vashon$ ls -lRF src total 1 drwxrwxr-x 3 jdp jdp 512 Oct 20 18:14 bin/ src/bin: total 1 drwxrwxr-x 2 jdp jdp 512 Oct 20 18:14 cat/ src/bin/cat: total 24 -r--r--r-- 1 jdp jdp 1651 Oct 15 23:06 Makefile,v -r--r--r-- 1 jdp jdp 9380 Oct 15 23:06 cat.1,v -r--r--r-- 1 jdp jdp 12201 Oct 15 23:06 cat.c,v Just for good measure, I do yet another update, still with a umask of 2: vashon$ cvsup -1gL2 -P m -i src/bin/cat supfile Parsing supfile "supfile" Looking up address of cvsup.freebsd.org Connecting to cvsup.freebsd.org Connected to cvsup.freebsd.org Server software version: REL_15_4_2 Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection src-bin/cvs Shutting down connection to server Finished successfully Surprise surprise, no "SetAttrs". Please try it like that, and see if it works. If it doesn't, then send me your cvsupfile as well as the output from "cvsup -v". Don't worry, we'll get to the bottom of this. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 18:56:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01481 for freebsd-current-outgoing; Tue, 20 Oct 1998 18:56:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01476 for ; Tue, 20 Oct 1998 18:56:41 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id VAA21424; Tue, 20 Oct 1998 21:56:09 -0400 (EDT) Message-ID: <19981020215609.A20479@netmonger.net> Date: Tue, 20 Oct 1998 21:56:09 -0400 From: Christopher Masto To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: cvsup and file permissions References: <19981020204619.F16673@netmonger.net> <199810210125.SAA07770@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810210125.SAA07770@austin.polstra.com>; from John Polstra on Tue, Oct 20, 1998 at 06:25:18PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 20, 1998 at 06:25:18PM -0700, John Polstra wrote: > No. It also affects which bits CVSup pays attention to when it is > determining whether the two files are the "same". I.e., CVSup looks > at the umask and does something with it. [...] > Please try it like that, and see if it works. If it doesn't, then > send me your cvsupfile as well as the output from "cvsup -v". Don't > worry, we'll get to the bottom of this. How right you are. Ouch. The problem is that I've been using sudo to run it, and while I've been setting _my_ umask to 2 for years, I see that it is not being inherited when I sudo. I feel like an idiot and I apologize for wasting your time. This particular machine has been around since before login.conf, so we never bothered to tweak it. -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ You're either a friend or a foe, and you're an enemy now. - STEVE BALLMER, Executive Vice President, Sales & Support, Microsoft, to Pacific Bell CEO David Dorman after Pacific Bell chose Netscape's Web software over Microsoft's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 19:01:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02018 for freebsd-current-outgoing; Tue, 20 Oct 1998 19:01:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02007 for ; Tue, 20 Oct 1998 19:01:03 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id WAA04708; Tue, 20 Oct 1998 22:00:30 -0400 (EDT) Date: Tue, 20 Oct 1998 22:00:30 -0400 (EDT) From: Daniel Eischen Message-Id: <199810210200.WAA04708@pcnet1.pcnet.com> To: dima@tejblum.dnttm.rssi.ru, eischen@vigrid.com Subject: Re: Another Serious libc_r problem Cc: current@FreeBSD.ORG, info@highwind.com, lists@tar.com, tejblum@arc.hq.cti.ru Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dima wrote: > Daniel Eischen wrote: > > > I don't think you want to wrap anything other than the condtion > > queue and dequeue with the condition spin locks; they should be > > used just to protect changing the condition variable. > > > > As long as you enqueue the condition variable before you unlock the > > mutex, there should be no race conditions. > > Well, specs says that mutex unlocking and enqueuing are atomic, so we may > put it in the code ;-|. (Note also that mutex_unlock may fail.) > > Anyway, what if a rescheduling happens just after thread was enqueued for > condition variable, and some other thread signaled the condition? Yes, it seems that we need a method of disabling task scheduing while we enqueue the condition variable and call the thread kern scheduler. You should be able to do this by setting _thread_kern_in_sched = 1. Something like this (from pthread_cond_timedwait): /* Lock the condition variable structure: */ _SPINLOCK(&(*cond)->lock); /* Process according to condition variable type: */ switch ((*cond)->c_type) { /* Fast condition variable: */ case COND_TYPE_FAST: /* * Disable thread scheduling. */ _thread_kern_in_sched = 1; /* Set the wakeup time: */ _thread_run->wakeup_time.tv_sec = abstime->tv_sec; _thread_run->wakeup_time.tv_nsec = abstime->tv_nsec; /* Reset the timeout flag: */ _thread_run->timeout = 0; /* * Queue the running thread for the condition * variable: */ _thread_queue_enq(&(*cond)->c_queue, _thread_run); /* Unlock the condition variable structure: */ _SPINUNLOCK(&(*cond)->lock); /* Unlock the mutex: */ if ((rval = pthread_mutex_unlock(mutex)) != 0) { /* Lock the condition variable structure: */ _SPINLOCK(&(*cond)->lock); /* * Cannot unlock the mutex, so remove the * running thread from the condition * variable queue: */ _thread_queue_deq(&(*cond)->c_queue); /* Unlock the condition variable structure: */ _SPINUNLOCK(&(*cond)->lock); /* * There could have had a SIGVTALRM between * here and where we disabled thread * scheduling; force a reschedule. */ pthread_yield(); } else { /* Schedule the next thread: */ _thread_kern_sched_state(PS_COND_WAIT, __FILE__, __LINE__); /* Lock the mutex: */ if ((rval = pthread_mutex_lock(mutex)) != 0) { } /* Check if the wait timed out: */ else if (_thread_run->timeout) { /* Return a timeout error: */ rval = ETIMEDOUT; } } break; /* Trap invalid condition variable types: */ default: /* Unlock the condition variable structure: */ _SPINUNLOCK(&(*cond)->lock); /* Return an invalid argument error: */ rval = EINVAL; break; } Calling _thread_kern_sched_state will end up clearing _thread_kern_in_sched, (and so will pthread_yield). The signal handler will not cause a reschedule when _thread_kern_sched_state is non-zero. You could always block signals to disable thread scheduling, but that seems too costly for something that can be done simply by using what's already in place. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 19:03:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02344 for freebsd-current-outgoing; Tue, 20 Oct 1998 19:03:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02324 for ; Tue, 20 Oct 1998 19:03:35 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id TAA07982; Tue, 20 Oct 1998 19:03:04 -0700 (PDT) (envelope-from jdp) Message-Id: <199810210203.TAA07982@austin.polstra.com> To: Christopher Masto cc: current@FreeBSD.ORG Subject: Re: cvsup and file permissions In-reply-to: Your message of "Tue, 20 Oct 1998 21:56:09 EDT." <19981020215609.A20479@netmonger.net> Date: Tue, 20 Oct 1998 19:03:04 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How right you are. Ouch. The problem is that I've been using sudo > to run it, and while I've been setting _my_ umask to 2 for years, > I see that it is not being inherited when I sudo. I feel like an > idiot and I apologize for wasting your time. No need. I'm just glad the problem is solved. You're not the first person to run into something like this. It reinforces the need for CVSup to support a "umask" specification in the cvsupfile itself. The only problem is, it's not as simple as it sounds. The user might reasonably want to specify different umask values for different collections. But CVSup can't simply use those values to call umask() directly, because at any given time it may well be working on up to 3 collections simultaneously. (That's because of its pipelined architecture.) So the effects of the umask system call will probably have to be faked manually, and that's why I haven't implemented it yet. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 19:20:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03996 for freebsd-current-outgoing; Tue, 20 Oct 1998 19:20:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03991 for ; Tue, 20 Oct 1998 19:20:41 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id WAA06394; Tue, 20 Oct 1998 22:20:12 -0400 (EDT) Date: Tue, 20 Oct 1998 22:20:12 -0400 (EDT) From: Daniel Eischen Message-Id: <199810210220.WAA06394@pcnet1.pcnet.com> To: jasone@canonware.com, lists@tar.com Subject: Re: Another Serious libc_r problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >The point I was trying to make is that the > >code does _not_ deadlock for the default (fast mutex). > > Yes, I missed your point. > > >I'm not sure that > >this is a bug, but it is different than the behavior I've seen on other > >systems. Can someone say whether this is allowed by the POSIX spec? POSIX says that "an attempt by the current owner of a mutex to relock the mutex results in undefined behaviour". It also says that if the current thread already owns the mutex, then EDEADLK should be returned. I don't see any kind of counting mutex in the POSIX spec. It seems our pthread_mutex_lock() is wrong, and should return EDEADLK in this case. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 19:42:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05754 for freebsd-current-outgoing; Tue, 20 Oct 1998 19:42:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05749 for ; Tue, 20 Oct 1998 19:42:48 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id WAA00469; Tue, 20 Oct 1998 22:41:12 -0400 (EDT) Date: Tue, 20 Oct 1998 22:41:12 -0400 (EDT) Message-Id: <199810210241.WAA00469@highwind.com> From: HighWind Software Information To: eischen@vigrid.com CC: dima@tejblum.dnttm.rssi.ru, eischen@vigrid.com, current@FreeBSD.ORG, lists@tar.com, tejblum@arc.hq.cti.ru In-reply-to: <199810210200.WAA04708@pcnet1.pcnet.com> (message from Daniel Eischen on Tue, 20 Oct 1998 22:00:30 -0400 (EDT)) Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, it seems that we need a method of disabling task scheduing while we enqueue the condition variable and call the thread kern scheduler. You should be able to do this by setting _thread_kern_in_sched = 1. Something like this (from pthread_cond_timedwait): Hmmm. If this is necessary here, wouldn't it be needed in other places in libc_r. Like uthread_mutex.c, uthread_join.c, uthread_fd.c Perhaps I'm confused. -- In the meantime, the earlier patch to uthread_cond.c seems to have worked. However, I'd really like to see libc_r become even more robust. I think it is time someone with commit-priv's gets involved to integrate this good work. We are happy to keep beating up the library and providing test programs that make it unhappy. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 19:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06293 for freebsd-current-outgoing; Tue, 20 Oct 1998 19:48:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eesn17.ews.uiuc.edu (eesn17.ews.uiuc.edu [130.126.161.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06287 for ; Tue, 20 Oct 1998 19:48:42 -0700 (PDT) (envelope-from ramasubr@ews.uiuc.edu) Received: from localhost (ramasubr@localhost) by eesn17.ews.uiuc.edu (8.8.8/8.7.3) with SMTP id VAA06752; Tue, 20 Oct 1998 21:48:11 -0500 (CDT) X-Authentication-Warning: eesn17.ews.uiuc.edu: ramasubr owned process doing -bs Date: Tue, 20 Oct 1998 21:48:11 -0500 (CDT) From: Vijay Ramasubramanian Reply-To: Vijay Ramasubramanian To: "Justin T. Gibbs" cc: current@FreeBSD.ORG Subject: Re: Installation probs w/3.0 In-Reply-To: <199810201932.NAA29092@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, Justin T. Gibbs wrote: > Is this an ABP-940, an ABP-940U, an ABP-940UA, or an ABP-940UW? > I have all three here, and I want to ensure that I use the same > board you have to reproduce the bug. This is an ABP-940UA. BTW, what is the difference between U and UA? BIOS version 2.8M. AdvanSys BIOS settings: Adapter config: SCSI ID 7 Spin Up Delay 1 Termination Enabled (last device on SCSI chain, so this is correct) PCI Burst Mode Enabled Multiple Drive Support Enabled Removable Media Support Disabled (no removable disks are/will be attached) Bootable CD Support Disabled SCSI Parity Enabled (all devices on this bus support parity and have it turned on) Ultra SCSI Enabled Host Queue Size 240 (this was the default value - can I/should I set this any higher or lower?) Device Queue Size 32 Device Config: All SCSI IDs are set identically with the following settings: Start Unit Command - Yes SCSI Disconnection - Yes Command Queuing - Yes Synchronous Transfer - Yes BIOS Target Control - Yes > Which of these drives is being accessed at the time of the failure? The failure occurs while data is being written to the / filesystem, which means that it is the 1st disk, the IBM drive at ID 0, being accessed. > Does the Fujitsu claim to support tagged queuing? Are there any > SCSI error messages printed on the console? You can get this > information by hitting and once you hit > the install screen to see the kernel messages for the drives. SCSI info from the device probe at boot is as follows: adv0: rev 0x03 int a irq 15 on pci0.12.0 adv0: AdvanSys Ultra SCSI Host Adapter, SCSI ID 7, queue depth 240 da2 at adv0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0 MHz, offset 15), Tagged Queuing Enabled da2: 405MB (830430 512 byte sectors: 64H 32S/T 405C) da0 at adv0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 20.0 MB/s transfers (20.0 MHz, offset 15), Tagged Queing Enabled da0: 2063 MB (4226725 512 byte sectors: 255H 63S/T 263C) da1's output is exactly the same as da0's, except that it is target 1 When the failures occur, I do not see any messages indicating SCSI errors with the exception of the Fujitsu error messages which Mr. Smith indicated might be due to the Synchronize Cache command not being supported but the error being harmless. Even if I take the Fujitsu off the SCSI bus (and designate a partition on the 2nd IBM drive as Swap) these installation failures occur. I installed RedHat Linux 5.1 on the machine yesterday (also via FTP) to try to test the hardware and make sure that it was not a problem with my hardware. The install of approximately 125 MB succeeded. It did seem to pause in places, but it continued fine all the way through. (I've never installed RedHat before so I don't know if there's anything unusual about the pausing - I suspect not since the whole installation went through without a hitch) The Linux install used the same partitioning scheme as I was trying to use with FreeBSD. It did not detect any bad blocks during the formatting of the partitions (and I had the check for bad blocks option enabled and monitored the debug consoles). I will attempt a kernel build and let you know the results of that. I can also install NT 4.0 onto the machine if you think that might serve as a reasonable test of the hardware. What are your suspicions? Thanks. .______ | Vijay N. Ramasubramanian mailto:ramasubr@ews.uiuc.edu http://www.ews.uiuc.edu/~ramasubr/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 20:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08395 for freebsd-current-outgoing; Tue, 20 Oct 1998 20:12:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08389; Tue, 20 Oct 1998 20:12:45 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA27299; Tue, 20 Oct 1998 20:02:46 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdB27297; Wed Oct 21 03:02:39 1998 Message-ID: <362D4EC7.167EB0E7@whistle.com> Date: Tue, 20 Oct 1998 20:02:31 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: sos@FreeBSD.ORG CC: current@FreeBSD.ORG Subject: Re: softupdates/smp References: <199810180918.LAA12711@sos.freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S?ren Schmidt wrote: > > In reply to Julian Elischer who wrote: > > Well I'm doing it, but I've 'left off' development until the > > ELF/CAM/3.0/etc changes all settle down. > > > > looks to me as if someone has broken it again. > > I'll be in europe for a fortnight. When I get back > > I hope things will have settled down enough for me to look at it again. > > Erhm, I've never seen it work reliably under SMP, did you ever get the > giant lock prims into the syncer ?? > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. As the syncer is a kernel thread and always in the kernel, it can only be scheduled if it already has the lock. At least that is my understanding. I have no proof of this however. as I haven't looked at the 'giant lock' code.. If this is not true we have other problems. Who knows about the "GL" code? julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 20:22:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09066 for freebsd-current-outgoing; Tue, 20 Oct 1998 20:22:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09056 for ; Tue, 20 Oct 1998 20:22:52 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA27651 for ; Tue, 20 Oct 1998 20:22:19 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdM27640; Wed Oct 21 03:22:14 1998 Message-ID: <362D5359.446B9B3D@whistle.com> Date: Tue, 20 Oct 1998 20:22:01 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Soft-Updates aware fsck available. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk has supplied a 'soft-updates aware' fsck. It requires a small tweek to compile under FreeBSD but that's all. I've made the shar file available at: http://www.freebsd.org/~julian/ (at the bottom of the page). It probably needs to be merged into out present one (or maybe just replace it.. He suggests it's much improved. I will be away for a while so can't merge it, but if anyone feels like it'd be worth looking at, be my guest. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 20:45:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11106 for freebsd-current-outgoing; Tue, 20 Oct 1998 20:45:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11095 for ; Tue, 20 Oct 1998 20:45:45 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id XAA00424; Tue, 20 Oct 1998 23:45:03 -0400 (EDT) Date: Tue, 20 Oct 1998 23:45:03 -0400 (EDT) From: Chuck Robey To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: Soft-Updates aware fsck available. In-Reply-To: <362D5359.446B9B3D@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, Julian Elischer wrote: > Kirk has supplied a 'soft-updates aware' fsck. > It requires a small tweek to compile under FreeBSD > but that's all. > > I've made the shar file available at: > http://www.freebsd.org/~julian/ > (at the bottom of the page). > > It probably needs to be merged into out present one (or maybe just > replace it.. He suggests it's much improved. > > I will be away for a while so can't merge it, but if anyone feels like > it'd be worth looking at, be my guest. Have you tried it, do you have any expectation it's really safe to experiment with? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 21:05:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12677 for freebsd-current-outgoing; Tue, 20 Oct 1998 21:05:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12660; Tue, 20 Oct 1998 21:05:36 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.1/8.9.1) with ESMTP id GAA07127; Wed, 21 Oct 1998 06:05:06 +0200 (CEST) Message-Id: <199810210405.GAA07127@midten.fast.no> To: sthaug@nethelp.no Cc: freebsd-current@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Problems with Digital server with P-166 and Neptune chipset From: Tor.Egge@fast.no In-Reply-To: Your message of "Wed, 21 Oct 1998 02:42:24 +0200" References: <6824.908930544@verdi.nethelp.no> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 21 Oct 1998 06:05:06 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I wrote: > > > I'm trying to get FreeBSD 3.0 to run reliably on a Digital server with > > Neptune chipset - so far without great success. (2.2.7, btw, wouldn't > > install at all. 3.0 installed with some effort). > > I now have some more info. Built a kernel with debug info, built an aout > gdb. I have two identical machines running 3.0-RELEASE now, and both of > them are crashing the same way (page fault in kernel mode) and in the > same place (the zalloc inline routine in vm/vm_zone.h). 0xe01d4194 : pushl %ebp 0xe01d4195 : movl %esp,%ebp 0xe01d4197 : pushl %esi 0xe01d4198 : pushl %ebx 0xe01d4199 : movl 0xe02561d0,%ecx 0xe01d419f : movl 0x8(%ecx),%eax 0xe01d41a2 : cmpl %eax,0xc(%ecx) 0xe01d41a5 : jl 0xe01d41b4 0xe01d41a7 : pushl %ecx 0xe01d41a8 : call 0xe01dfd44 <_zget> 0xe01d41ad : movl %eax,%esi 0xe01d41af : addl $0x4,%esp 0xe01d41b2 : jmp 0xe01d41c4 item = z->zitems; 0xe01d41b4 : movl 0x4(%ecx),%edx z->zitems = ((void **) item)[0]; 0xe01d41b7 : movl (%edx),%eax Here it crashed z (ecx) is 0xf0dd9980, cf. tf_ecx = -253912704 items (edx) is 0x7200720, cf. tf_edx = 119539488 0xe01d41b9 : movl %eax,0x4(%ecx) .... > > Here are two backtraces, one from each machine. These both happened at > the same time, namely when running /etc/daily at 02.00. In both cases, > the kernel is trying to follow a null pointer (z) at vm/vm_zone.h line 87: > > item = z->zitems; The fault virtual address was 0x07200720 according to the panic messages. > > However, the zalloc inline routine is called from vmspace_alloc: > > vm = zalloc(vmspace_zone); > > and here the vmspace_zone seems to have a sensible value, 0xf0dd9980. > > I'm going to try to recompile the kernel with DIAGNOSTIC enabled to see > if I can get some more info. Meanwhile, can anybody suggest why z is > null in zalloc when vmspace_zone isn't? Missing spl protection? Looking at you dmesg output (from an earlier message), I find real memory = 269221888 (262912K bytes) instead of the expected real memory = 268435456 (262144K bytes) which indicates that the speculative memory probe stopped at 0x0100C0000, i.e. at the end of aliased VGA memory. I suggest adding options "MAXMEM=(256*1024)" to your kernel config file. Two space characters with black background and grey foreground --> 0x07200720 in screen memory. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 21:37:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15093 for freebsd-current-outgoing; Tue, 20 Oct 1998 21:37:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15088 for ; Tue, 20 Oct 1998 21:37:11 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id GAA22810; Wed, 21 Oct 1998 06:36:43 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id GAA18955; Wed, 21 Oct 1998 06:36:36 +0200 (MET DST) Message-ID: <19981021063635.42023@follo.net> Date: Wed, 21 Oct 1998 06:36:35 +0200 From: Eivind Eklund To: Daniel Eischen , jasone@canonware.com, lists@tar.com Cc: current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem References: <199810210220.WAA06394@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199810210220.WAA06394@pcnet1.pcnet.com>; from Daniel Eischen on Tue, Oct 20, 1998 at 10:20:12PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 20, 1998 at 10:20:12PM -0400, Daniel Eischen wrote: > > >The point I was trying to make is that the > > >code does _not_ deadlock for the default (fast mutex). > > > > Yes, I missed your point. > > > > >I'm not sure that > > >this is a bug, but it is different than the behavior I've seen on other > > >systems. Can someone say whether this is allowed by the POSIX spec? > > POSIX says that "an attempt by the current owner of a mutex to relock > the mutex results in undefined behaviour". It also says that if > the current thread already owns the mutex, then EDEADLK should > be returned. I don't see any kind of counting mutex in the POSIX > spec. It can't say both (not without being ambiguous, anyway). Which one is it? I'm modifying that code and will have to run full tests on it anyway, so fixing this at the same time wouldn't hurt (actually, it would be a one-line change to sources I presently have - they already support both PTHREAD_MUTEX_DEFAULT (which is equal to the present implementation of MUTEX_TYPE_FAST), PTHREAD_MUTEX_NORMAL (which deadlock on locking against itself), and PTHREAD_MUTEX_ERRORCHECK (which return EDEADLK)). As soon as somebody can describe the wanted semantics (preferably with the appropriate quotes from the standard, I'll fix it. I don't have the relevant POSIX standard itself, so I can't just look it up :-/ > It seems our pthread_mutex_lock() is wrong, and should return > EDEADLK in this case. Sounds somewhat reasonable. However, if this is a requirement of POSIX, then SS2 has specified more relaxed restrictions than POSIX... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 21:44:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15656 for freebsd-current-outgoing; Tue, 20 Oct 1998 21:44:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15627; Tue, 20 Oct 1998 21:43:56 -0700 (PDT) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id VAA15732; Tue, 20 Oct 1998 21:41:59 -0700 (PDT) Date: Tue, 20 Oct 1998 21:41:59 -0700 (PDT) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199810210441.VAA15732@math.berkeley.edu> To: dmm125@bellatlantic.net, mike@smith.net.au Subject: Re: FAT32 support for 3.0 installation Cc: dan@math.berkeley.edu, freebsd-current@FreeBSD.ORG, questions@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problems I'm having are that I boot up on the boot floppy (boot.flp). > Then when it gets to the point of the installation where it tries to extract > the distributions off my FAT32 partition, I get an error to the effect that > the following distributions weren't found: bin manpages proflibs des compat. > Basically, all of them. I thought that maybe sysinstall expected a certain > combination of uppercase/lowercase letter combinations. Like: > > C:\FreeBSD\bin > C:\FREEBSD\bin > C:\freebsd\BIN > C:\Freebsd\bin etc. since now we are working with case-sensitive filenames > with msdos. There is another possibility. I don't know if this is the case with installing recent releases from a local dos or other file system, but when installing via ftp, the installation program is looking for a subdirectory of the specified directory whose name is the release name. For example, when installing 3.0-19981009-BETA, I gave the installation program this URL: "ftp://xxx.berkeley.edu/FreeBSD" and it looked for the directory "FreeBSD/3.0-19981009-BETA/bin" within my home directory on the machine "xxx.berkeley.edu". The subdirectory/release name is wired into the installation floppy but changeable in the options installation menu. I am not at all certain that this is your problem, but I think it is worth looking into. The installation manual used to be a little vague about making copies of the release files for installation from local disk or tape. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 22:12:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17182 for freebsd-current-outgoing; Tue, 20 Oct 1998 22:12:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17176 for ; Tue, 20 Oct 1998 22:12:38 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id BAA19668; Wed, 21 Oct 1998 01:12:09 -0400 (EDT) Date: Wed, 21 Oct 1998 01:12:09 -0400 (EDT) From: Daniel Eischen Message-Id: <199810210512.BAA19668@pcnet1.pcnet.com> To: eischen@vigrid.com, eivind@yes.no, jasone@canonware.com, lists@tar.com Subject: Re: Another Serious libc_r problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > On Tue, Oct 20, 1998 at 10:20:12PM -0400, Daniel Eischen wrote: > > > >The point I was trying to make is that the > > > >code does _not_ deadlock for the default (fast mutex). > > > > > > Yes, I missed your point. > > > > > > >I'm not sure that > > > >this is a bug, but it is different than the behavior I've seen on other > > > >systems. Can someone say whether this is allowed by the POSIX spec? > > > > POSIX says that "an attempt by the current owner of a mutex to relock > > the mutex results in undefined behaviour". It also says that if > > the current thread already owns the mutex, then EDEADLK should > > be returned. I don't see any kind of counting mutex in the POSIX > > spec. > > It can't say both (not without being ambiguous, anyway). Which one is > it? It does say both, but regarding the EDEADLK return value, it says "if the condition [thread already owns the mutex] is detected". So if the implementation were not to detect the condition, then I think "undefined behaviour" would occur. Since we can and do detect the condition, we should return EDEADLK in this case. > I'm modifying that code and will have to run full tests on it > anyway, so fixing this at the same time wouldn't hurt (actually, it > would be a one-line change to sources I presently have - they already > support both PTHREAD_MUTEX_DEFAULT (which is equal to the present > implementation of MUTEX_TYPE_FAST), PTHREAD_MUTEX_NORMAL (which > deadlock on locking against itself), and PTHREAD_MUTEX_ERRORCHECK > (which return EDEADLK)). I don't see any of these in the POSIX spec, although I just got the spec and may have overlooked them. Are you also working on priority ceilings and inheritence? > As soon as somebody can describe the wanted semantics (preferably with > the appropriate quotes from the standard, I'll fix it. I don't have > the relevant POSIX standard itself, so I can't just look it up :-/ If you have questions ask me and I can look them up for you. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 20 22:33:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18430 for freebsd-current-outgoing; Tue, 20 Oct 1998 22:33:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18425 for ; Tue, 20 Oct 1998 22:33:43 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id BAA20955; Wed, 21 Oct 1998 01:33:14 -0400 (EDT) Date: Wed, 21 Oct 1998 01:33:14 -0400 (EDT) From: Daniel Eischen Message-Id: <199810210533.BAA20955@pcnet1.pcnet.com> To: eischen@vigrid.com, info@highwind.com Subject: Re: Another Serious libc_r problem Cc: current@FreeBSD.ORG, dima@tejblum.dnttm.rssi.ru, lists@tar.com, tejblum@arc.hq.cti.ru Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, it seems that we need a method of disabling task scheduing > while we enqueue the condition variable and call the thread > kern scheduler. You should be able to do this by setting > _thread_kern_in_sched = 1. Something like this (from > pthread_cond_timedwait): > > Hmmm. If this is necessary here, wouldn't it be needed in other > places in libc_r. Like uthread_mutex.c, uthread_join.c, uthread_fd.c Yeah, probably. It is a very, very small window where the timer can go off and schedule a new thread, but it could still happen. > Perhaps I'm confused. Nope :-) > In the meantime, the earlier patch to uthread_cond.c seems to have > worked. However, I'd really like to see libc_r become even more > robust. > > I think it is time someone with commit-priv's gets involved to > integrate this good work. We are happy to keep beating up the library > and providing test programs that make it unhappy. Eivind Eklund said in previous mail that he was working on mutexes. Maybe if you send him a T-shirt, he'll do it for you :-) Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 00:15:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24279 for freebsd-current-outgoing; Wed, 21 Oct 1998 00:15:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24271 for ; Wed, 21 Oct 1998 00:15:00 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.9.1/8.7.3) id JAA02191 for freebsd-current@freebsd.org; Wed, 21 Oct 1998 09:14:32 +0200 (CEST) From: Holm Tiffe Message-Id: <199810210714.JAA02191@magnet.geophysik.tu-freiberg.de> Subject: Unable to install 3.0-RELEASE with an AHA1542 ! To: freebsd-current@FreeBSD.ORG Date: Wed, 21 Oct 1998 09:14:32 +0200 (CEST) Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Today I've tried to install a 3.0 RELEASE on a PII/350 system (Gigabyte GA-6BA w. 128MB SDRAM) and an old 1542. This configuration was only chosen to test the usability from old LANCE based Network cards, dont say me that I shouldn't use such a configuration :-) In the Storage menu from sysinstall I've choosen the "Adaptec 154x SCSI Controller" (that has in this menu no configurable port adresses and no IRQ's) When I boot up the system (Install Menu) and scroll backwards the system says ahc0: not found at 0x134! I know that is one of 6 possible adresses for the aha1542, but the default is 0x330.... In 2.2.7-Release that's all fine. Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 01:22:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29532 for freebsd-current-outgoing; Wed, 21 Oct 1998 01:22:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA29522 for ; Wed, 21 Oct 1998 01:22:05 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 11703 invoked by uid 1001); 21 Oct 1998 08:20:01 +0000 (GMT) To: Tor.Egge@fast.no Cc: freebsd-current@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Problems with Digital server with P-166 and Neptune chipset In-Reply-To: Your message of "Wed, 21 Oct 1998 06:05:06 +0200" References: <199810210405.GAA07127@midten.fast.no> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 21 Oct 1998 10:20:01 +0200 Message-ID: <11701.908958001@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I now have some more info. Built a kernel with debug info, built an aout > > gdb. I have two identical machines running 3.0-RELEASE now, and both of > > them are crashing the same way (page fault in kernel mode) and in the > > same place (the zalloc inline routine in vm/vm_zone.h). ... > Looking at you dmesg output (from an earlier message), I find > > real memory = 269221888 (262912K bytes) > > instead of the expected > > real memory = 268435456 (262144K bytes) > > which indicates that the speculative memory probe stopped at 0x0100C0000, > i.e. at the end of aliased VGA memory. Yes, that was indeed the problem. Adding a suitable MAXMEM, as suggested, cured it. And I learned something about kernel debugging. Thanks a lot! Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 01:29:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00201 for freebsd-current-outgoing; Wed, 21 Oct 1998 01:29:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00190 for ; Wed, 21 Oct 1998 01:29:05 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA16152; Wed, 21 Oct 1998 17:58:05 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id RAA02068; Wed, 21 Oct 1998 17:57:54 +0930 (CST) Message-ID: <19981021175753.W21008@freebie.lemis.com> Date: Wed, 21 Oct 1998 17:57:53 +0930 From: Greg Lehey To: Jaime Bozza , Bruce Albrecht Cc: current@FreeBSD.ORG Subject: Re: newfs problems, more information: References: <13868.3117.390224.376379@zuhause.zuhause.mn.org> <003801bdfc74$da58cae0$313d31cc@electron.nuc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <003801bdfc74$da58cae0$313d31cc@electron.nuc.net>; from Jaime Bozza on Tue, Oct 20, 1998 at 04:59:04PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 20 October 1998 at 16:59:04 -0500, Jaime Bozza wrote: >> You do it the same way you do it for any other disk. You create the >> partition information, and do a disklabel for ccd0 to write the label, >> and then you newfs each partition, ccd0d, ccd0e, ... > > Are you saying you can have subpartitions within a ccd? (Which in itself > is formed by partitions on the original drives) Yes. I can't see much reason to do so, though. There's certainly none whatsoever with vinum. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 01:31:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00514 for freebsd-current-outgoing; Wed, 21 Oct 1998 01:31:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00485 for ; Wed, 21 Oct 1998 01:31:11 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA16171; Wed, 21 Oct 1998 18:00:33 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA03231; Wed, 21 Oct 1998 18:00:32 +0930 (CST) Message-ID: <19981021180032.X21008@freebie.lemis.com> Date: Wed, 21 Oct 1998 18:00:32 +0930 From: Greg Lehey To: Bruce Albrecht , Jaime Bozza Cc: current@FreeBSD.ORG Subject: Subdividing synthetic disks (was: newfs problems, more information:) References: <13868.3117.390224.376379@zuhause.zuhause.mn.org> <003801bdfc74$da58cae0$313d31cc@electron.nuc.net> <13869.12610.899877.506387@zuhause.zuhause.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <13869.12610.899877.506387@zuhause.zuhause.mn.org>; from Bruce Albrecht on Tue, Oct 20, 1998 at 07:56:34PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 20 October 1998 at 19:56:34 -0500, Bruce Albrecht wrote: > Jaime Bozza writes: >>> You do it the same way you do it for any other disk. You create the >>> partition information, and do a disklabel for ccd0 to write the label, >>> and then you newfs each partition, ccd0d, ccd0e, ... >> >> Are you saying you can have subpartitions within a ccd? (Which in itself >> is formed by partitions on the original drives) >> >> That could be pretty interesting. I've fiddled with disklabel and was >> finally able to create a disklabel for a ccd. But I haven't been able to >> create a partition 'e' ... disklabel returns "Bad partition name". I was >> able to create an 'a' partition though. > > I never had any problem doing so. Here's my ccd's disklabel entry: > > (snip) Why do you want to do this? Would you still find a reason to do it with vinum? > I've been told that you're better off not using a ccd partition for > swap, Right. The ccd driver malloc()s, and there's the danger of a deadlock if malloc tries to swap. I'm working on a solution for vinum, which currently carries the same danger. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 01:57:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02384 for freebsd-current-outgoing; Wed, 21 Oct 1998 01:57:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02379 for ; Wed, 21 Oct 1998 01:57:19 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA21762; Wed, 21 Oct 1998 09:56:04 +0100 (BST) Date: Wed, 21 Oct 1998 09:56:04 +0100 (BST) From: Doug Rabson To: Eric Haug cc: current@FreeBSD.ORG Subject: Re: nfs panic in free() In-Reply-To: <199810201633.LAA06373@mnw.eas.slu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, Eric Haug wrote: > Hi all, > I am having a repeatable panic in the nfs server code. > I have a -g compile kernel and a vmcore file. > dmesg output included > Should this be sent via send-pr? > Anyone else seeing this sort of nfs bug? > > Another problem that this system has: > The Promise card has the prom removed, cause the system will not > recognize the disks connected to it when the prom is in there. > I believe that this results in the disk access timing being off > so that transfers are about half of what they could be. > > The MBoard is a Matsonic MS6260S running at system clock of 100MHz. > The CPU is rated for more than 300 MHz. i.e. the system > is not overclocked. Could you test this fix (thanks for the stacktrace it made it pretty easy to see what was going on): Index: nfs_socket.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_socket.c,v retrieving revision 1.46 diff -u -r1.46 nfs_socket.c --- nfs_socket.c 1998/09/29 22:33:05 1.46 +++ nfs_socket.c 1998/10/21 08:55:41 @@ -2232,7 +2232,9 @@ nd->nd_dpos = mtod(m, caddr_t); error = nfs_getreq(nd, nfsd, TRUE); if (error) { - FREE(nam, M_SONAME); + if (nam) { + FREE(nam, M_SONAME); + } free((caddr_t)nd, M_NFSRVDESC); return (error); } -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 02:21:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03901 for freebsd-current-outgoing; Wed, 21 Oct 1998 02:21:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Guard.PolyNet.Lviv.UA (Guard.PolyNet.Lviv.UA [194.44.138.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA03895 for ; Wed, 21 Oct 1998 02:21:40 -0700 (PDT) (envelope-from pam@polynet.lviv.ua) From: pam@polynet.lviv.ua Received: (qmail 9410 invoked by alias); 21 Oct 1998 09:21:03 -0000 Received: (qmail 9403 invoked from network); 21 Oct 1998 09:21:03 -0000 Received: from postoffice.polynet.lviv.ua (194.44.138.1) by guard.polynet.lviv.ua with SMTP; 21 Oct 1998 09:21:03 -0000 Received: (qmail 14187 invoked by uid 1001); 21 Oct 1998 09:21:02 -0000 Date: 21 Oct 1998 12:21:02 +0300 Date: Wed, 21 Oct 1998 12:21:02 +0300 (EEST) X-Sender: pam@NetSurfer.lp.lviv.ua To: current@FreeBSD.ORG Subject: [Q]: Buildworld without secure libs (to use MD5 passwords) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everybody! I want to generate FreeBSD-current system with MD5 crypted (hashed) passwords, by default. it generates DES libcrypt libraries. Which build flag changes that behaviour? Maybe someone can post a list of useful build switches for system customization like NOAOUT, NOSENDMAIL, NOGAMES ... etc Thanks in advance. Adrian Pavlykevych email: System Administrator phone/fax: +380 (322) 742041 State University "Lvivska Polytechnica" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 03:43:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07009 for freebsd-current-outgoing; Wed, 21 Oct 1998 03:43:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA07004 for ; Wed, 21 Oct 1998 03:43:42 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id MAA27734; Wed, 21 Oct 1998 12:20:20 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA19668; Wed, 21 Oct 1998 12:20:19 +0200 (MET DST) Message-ID: <19981021122019.33548@follo.net> Date: Wed, 21 Oct 1998 12:20:19 +0200 From: Eivind Eklund To: Daniel Eischen , jasone@canonware.com, lists@tar.com Cc: current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem References: <199810210512.BAA19668@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199810210512.BAA19668@pcnet1.pcnet.com>; from Daniel Eischen on Wed, Oct 21, 1998 at 01:12:09AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 21, 1998 at 01:12:09AM -0400, Daniel Eischen wrote: > Eivind Eklund wrote: > > On Tue, Oct 20, 1998 at 10:20:12PM -0400, Daniel Eischen wrote: > > > POSIX says that "an attempt by the current owner of a mutex to relock > > > the mutex results in undefined behaviour". It also says that if > > > the current thread already owns the mutex, then EDEADLK should > > > be returned. I don't see any kind of counting mutex in the POSIX > > > spec. > > > > It can't say both (not without being ambiguous, anyway). Which one is > > it? > > It does say both, but regarding the EDEADLK return value, it says > "if the condition [thread already owns the mutex] is detected". So > if the implementation were not to detect the condition, then I > think "undefined behaviour" would occur. Since we can and do detect > the condition, we should return EDEADLK in this case. Yeah, I think I agree. However, it may shock FreeBSD-specific threaded programs. Well, "gratious implementation knowledge" and all that. > > I'm modifying that code and will have to run full tests on it > > anyway, so fixing this at the same time wouldn't hurt (actually, it > > would be a one-line change to sources I presently have - they already > > support both PTHREAD_MUTEX_DEFAULT (which is equal to the present > > implementation of MUTEX_TYPE_FAST), PTHREAD_MUTEX_NORMAL (which > > deadlock on locking against itself), and PTHREAD_MUTEX_ERRORCHECK > > (which return EDEADLK)). > > I don't see any of these in the POSIX spec, although I just got > the spec and may have overlooked them. They would be described in the section for pthread_mutexattr_settype() if they are there at all. These are different types of locks - you can see the descriptions of them at http://www.opengroup.org/onlinepubs/7908799/xsh/pthread_mutexattr_settype.html > Are you also working on priority ceilings and inheritence? No. I started doing the changes because one of my co-workers' programs needed recursive locks, and we try to write to the SS2 API. > > As soon as somebody can describe the wanted semantics (preferably with > > the appropriate quotes from the standard, I'll fix it. I don't have > > the relevant POSIX standard itself, so I can't just look it up :-/ > > If you have questions ask me and I can look them up for you. Exact definition of how the locks are supposed to work (the relevant quotes, not just from memory) would be very nice. If you have time, just cross-referencing with SS2 and telling about the differences would probably be what makes things easiest. (I can't promise to spend much time on this - what I was doing was just random maintenance due to it being required locally - my present 'pet project' for FreeBSD is something else). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 06:19:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14884 for freebsd-current-outgoing; Wed, 21 Oct 1998 06:19:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14846 for ; Wed, 21 Oct 1998 06:18:52 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id JAA23767; Wed, 21 Oct 1998 09:18:22 -0400 (EDT) Date: Wed, 21 Oct 1998 09:18:22 -0400 (EDT) From: Daniel Eischen Message-Id: <199810211318.JAA23767@pcnet1.pcnet.com> To: eischen@vigrid.com, lists@tar.com Subject: Re: Another Serious libc_r problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Yes, it seems that we need a method of disabling task scheduing > >while we enqueue the condition variable and call the thread > >kern scheduler. You should be able to do this by setting > >_thread_kern_in_sched = 1. Something like this (from > >pthread_cond_timedwait): > > [snip] > > >Calling _thread_kern_sched_state will end up clearing _thread_kern_in_sched, > >(and so will pthread_yield). The signal handler will not cause a > >reschedule when _thread_kern_sched_state is non-zero. > > Bear with me while I try to understand this. Between the time you > set _thread_kern_in_sched = 1 and the call to _thread_kern_sched_state > (or pthread_yield) you call pthread_mutex_unlock, which does a spinlock. > Also, before calling pthread_yield you also do a spinlock. Isn't a > spinlock a potential yield call to the kernel scheduler, which in > turn could set _thread_kern_in_sched = 0, and thus still leave you > vulnerable to the scheduling window you are concerned about? Yeah, good point. Although one could argue that the SPINLOCK in pthread_mutex_unlock shouldn't yield because other threads shouldn't be able to run at this point (_thread_kern_in_sched is non-zero) What we need are _thread_kern_sched_[un]lock() routines that wrap whatevers necessary to disable a signal from causing a thread switch. > If I understand, and I may not, what you are concerned about is that > after you unlock the condition spinlock, and before you yield to > the scheduler, you could be pre-empted, and that the condition could > be signaled (thus causing you to wait on a condition that has already > been signaled, a mistake?). Right, as someone else pointed out also. > The condition can only be signaled when > the condition spinlock is not held. So... why wouldn't you hold the > condition spinlock as long as possible (ie. after the mutex unlock) > and *then* set _thread_kern_in_sched = 1 after all the spinlocks have > been done? If the thread doesn't own the mutex, then you've got the condition variable locked while you're waiting for the pthread_mutex_unlock(). Since this falls into the category of "undefined behavior" it probably doesn't matter though. > Or, using your code snippet, why not this? > Yes this is OK and the way I had it originally before I felt a wave of AR'ness come over me. I think the part where the pthread_mutex_lock fails wrong (you don't need to lock the condition variable - it's already locked, and you don't need to disable thread scheduling and call pthread_yield). But I understand what you're saying. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 06:23:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15669 for freebsd-current-outgoing; Wed, 21 Oct 1998 06:23:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15664 for ; Wed, 21 Oct 1998 06:23:17 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id JAA24201; Wed, 21 Oct 1998 09:22:47 -0400 (EDT) Date: Wed, 21 Oct 1998 09:22:47 -0400 (EDT) From: Daniel Eischen Message-Id: <199810211322.JAA24201@pcnet1.pcnet.com> To: eischen@vigrid.com, eivind@yes.no, jasone@canonware.com, lists@tar.com Subject: Re: Another Serious libc_r problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > They would be described in the section for pthread_mutexattr_settype() > if they are there at all. These are different types of locks - you > can see the descriptions of them at > http://www.opengroup.org/onlinepubs/7908799/xsh/pthread_mutexattr_settype.html Thanks for the URL. pthread_mutexattr_settype is not in the POSIX spec. The PTHREAD_MUTEX_DEFAULT type seems to be consistent with the POSIX spec > Exact definition of how the locks are supposed to work (the relevant > quotes, not just from memory) would be very nice. If you have time, > just cross-referencing with SS2 and telling about the differences > would probably be what makes things easiest. (I can't promise to > spend much time on this - what I was doing was just random maintenance > due to it being required locally - my present 'pet project' for > FreeBSD is something else). pthread_mutex_lock pthread_mutex_trylock pthread_mutex_unlock Excerpts from 11.3.3.2 Descriptions: "The mutex object referenced by mutex shall be locked by calling pthread_mutex_lock(). ... An attempt by the current owner of a mutex to relock the mutex results in undefined behavior. The function pthread_mutex_trylock() is identical to pthread_mutex_lock() except that if the mutex object referenced by mutex is currently locked (by any thread, including the current thread), the call returns immediately. The function pthread_mutex_unlock() is called by the owner of the mutex object referenced by mutex to release it. A pthread_mutex_unlock() call by a thread that is not the owner of the mutex results in undefined behavior. Calling pthread_mutex_unlock() when the mutex object is unlocked also results in undefined behavior. ..." Excerpts from 11.3.3.4 Errors: "... the pthread_mutex_lock() and pthread_mutex_trylock() functions shall return the following corresponding error number: [EINVAL] The mutex was created with the protocol attribute having the value PTHREAD_PRIO_PROTECT and the priority of the calling thread is higher than the current priority ceiling of the mutex. ... the pthread_mutex_trylock() function shall return the corresponding error number: [EBUSY] The mutex could not be acquired because it was already locked. ... if the condition is detected, the pthread_mutex_lock(), pthread_mutex_trylock(), and the pthread_mutex_unlock() functions shall return the following error number: [EINVAL] The value specified by the mutex does not refer to an initialized mutex object. ... if the condition is detected, the pthread_mutex_lock() function shall return the corresponding error number: [EDEADLK] The current thread already owns the mutex. ... if the condition is detected, the pthread_mutex_unlock() function shall return the corresponding error number: [EPERM] The current thread does not own the mutex." Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 06:24:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15765 for freebsd-current-outgoing; Wed, 21 Oct 1998 06:24:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15757 for ; Wed, 21 Oct 1998 06:24:03 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id FAA19064; Wed, 21 Oct 1998 05:52:48 -0500 (CDT) Message-Id: <199810211052.FAA19064@ns.tar.com> From: "Richard Seaman, Jr." To: "Daniel Eischen" Cc: "current@freebsd.org" Date: Wed, 21 Oct 98 05:52:47 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998 22:00:30 -0400 (EDT), Daniel Eischen wrote: >Yes, it seems that we need a method of disabling task scheduing >while we enqueue the condition variable and call the thread >kern scheduler. You should be able to do this by setting >_thread_kern_in_sched = 1. Something like this (from >pthread_cond_timedwait): [snip] >Calling _thread_kern_sched_state will end up clearing _thread_kern_in_sched, >(and so will pthread_yield). The signal handler will not cause a >reschedule when _thread_kern_sched_state is non-zero. Bear with me while I try to understand this. Between the time you set _thread_kern_in_sched = 1 and the call to _thread_kern_sched_state (or pthread_yield) you call pthread_mutex_unlock, which does a spinlock. Also, before calling pthread_yield you also do a spinlock. Isn't a spinlock a potential yield call to the kernel scheduler, which in turn could set _thread_kern_in_sched = 0, and thus still leave you vulnerable to the scheduling window you are concerned about? If I understand, and I may not, what you are concerned about is that after you unlock the condition spinlock, and before you yield to the scheduler, you could be pre-empted, and that the condition could be signaled (thus causing you to wait on a condition that has already been signaled, a mistake?). The condition can only be signaled when the condition spinlock is not held. So... why wouldn't you hold the condition spinlock as long as possible (ie. after the mutex unlock) and *then* set _thread_kern_in_sched = 1 after all the spinlocks have been done? Or, using your code snippet, why not this? /* Lock the condition variable structure: */ _SPINLOCK(&(*cond)->lock); /* Process according to condition variable type: */ switch ((*cond)->c_type) { /* Fast condition variable: */ case COND_TYPE_FAST: /* Set the wakeup time: */ _thread_run->wakeup_time.tv_sec = abstime->tv_sec; _thread_run->wakeup_time.tv_nsec = abstime->tv_nsec; /* Reset the timeout flag: */ _thread_run->timeout = 0; /* * Queue the running thread for the condition * variable: */ _thread_queue_enq(&(*cond)->c_queue, _thread_run); /* Unlock the mutex: */ if ((rval = pthread_mutex_unlock(mutex)) != 0) { /* Lock the condition variable structure: */ _SPINLOCK(&(*cond)->lock); /* * Cannot unlock the mutex, so remove the * running thread from the condition * variable queue: */ _thread_queue_deq(&(*cond)->c_queue); /* * Disable thread scheduling. */ _thread_kern_in_sched = 1; /* Unlock the condition variable structure: */ _SPINUNLOCK(&(*cond)->lock); /* * There could have had a SIGVTALRM between * here and where we disabled thread * scheduling; force a reschedule. */ pthread_yield(); } else { /* * Disable thread scheduling. */ _thread_kern_in_sched = 1; /* Unlock the condition variable structure: */ _SPINUNLOCK(&(*cond)->lock); /* Schedule the next thread: */ _thread_kern_sched_state(PS_COND_WAIT, __FILE__, __LINE__); /* Lock the mutex: */ if ((rval = pthread_mutex_lock(mutex)) != 0) { } /* Check if the wait timed out: */ else if (_thread_run->timeout) { /* Return a timeout error: */ rval = ETIMEDOUT; } } break; /* Trap invalid condition variable types: */ default: /* Unlock the condition variable structure: */ _SPINUNLOCK(&(*cond)->lock); /* Return an invalid argument error: */ rval = EINVAL; break; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 06:34:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17365 for freebsd-current-outgoing; Wed, 21 Oct 1998 06:34:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opi.flirtbox.ch ([62.48.0.50]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA17347 for ; Wed, 21 Oct 1998 06:34:07 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 6125 invoked from network); 21 Oct 1998 13:05:49 -0000 Received: from unknown (HELO pipeline.ch) (195.134.140.4) by opi.flirtbox.ch with SMTP; 21 Oct 1998 13:05:49 -0000 Message-ID: <362DDC74.B04C3057@pipeline.ch> Date: Wed, 21 Oct 1998 15:07:00 +0200 From: Andre Oppermann Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: Alfred Perlstein CC: HighWind Software Information , current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: -snip- > As a side note, has anyone thought of hybrid kernel+userland threads? > Basically a userland scheduler with kernel hooks for mutexes and > distributing signals. At startup or on the first pthread_create() the > pthreads library would sysctl out the number of processors in the > system and prefork kernel threads for each. The kernel threads would only > be active on SMP machines, otherwise there really is no point. Does > anyone have any papers/webpages about an algorithm like that? http://www.freebsd.org/~terry (I think so...) -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 06:44:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19056 for freebsd-current-outgoing; Wed, 21 Oct 1998 06:44:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19045 for ; Wed, 21 Oct 1998 06:44:24 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.8.8) with ESMTP id JAA21518; Wed, 21 Oct 1998 09:07:46 -0400 (EDT) (envelope-from scrappy@hub.org) Date: Wed, 21 Oct 1998 09:07:46 -0400 (EDT) From: "Marc G. Fournier" To: Alex Zepeda cc: freebsd-current@FreeBSD.ORG Subject: Re: Invalid option for compiler...? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, Alex Zepeda wrote: > On Tue, 20 Oct 1998, Marc G. Fournier wrote: > > > > > Trying to build a new kernel, and I get the following error: > > > > hub# make depend > > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > > -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -g -nostdinc > > -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h > > ../../i386/i386/genassym.c > > cc1: Invalid option `-fformat-extensions' > > *** Error code 1 > > -fformat-extensions is used to quash some warnings that might be generated > by the odd format identifiers in the kernel. As long as you're not using > -Werror, it's safe to remove this (and is the only way to go with a non > stock cc). The "correct" solution would be to rebuild cc1 (a make world > will do this as well as rebuild other parts required for use of a post > 3.0-R kernel). I generally do the 'make world' after I know the kernel is going to run on my platform...I've already done the 'make buildworld', but need to get a kernel built and reboot'd into first. How do I get rid of the -fformat-extensions -Werror flags? I've checked /usr/share/mk/*, /etc/make.conf, /usr/src/sys/i386/conf/Makefile.i386, and can't find it defined in any of those places...which place am I missing? Thanks.. Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@{postgresql|isc}.org ICQ#7615664 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 06:46:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19282 for freebsd-current-outgoing; Wed, 21 Oct 1998 06:46:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19277 for ; Wed, 21 Oct 1998 06:46:11 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id IAA08810; Wed, 21 Oct 1998 08:45:33 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id IAA02006; Wed, 21 Oct 1998 08:40:29 -0500 (CDT) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13869.58445.435772.587309@zuhause.zuhause.mn.org> Date: Wed, 21 Oct 1998 08:40:29 -0500 (CDT) To: Greg Lehey Cc: Jaime Bozza , current@FreeBSD.ORG Subject: Re: Subdividing synthetic disks (was: newfs problems, more information:) In-Reply-To: <19981021180032.X21008@freebie.lemis.com> References: <13868.3117.390224.376379@zuhause.zuhause.mn.org> <003801bdfc74$da58cae0$313d31cc@electron.nuc.net> <13869.12610.899877.506387@zuhause.zuhause.mn.org> <19981021180032.X21008@freebie.lemis.com> X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > > I never had any problem doing so. Here's my ccd's disklabel entry: > > > > (snip) > > Why do you want to do this? Would you still find a reason to do it > with vinum? I have a 3 disk CCD with multiple partitions set up because it appears to improve transfer rates by about 50% (IIRC) over having each partition on a separate drive. I know you advocate using one very large partition, but I prefer to keep my partitions small enough so that I can dump any of them to a 90 meter DAT tape (roughly 2 GB) without having to deal with tape swap. I have a DAT autoloader, so if there's an automated way of dealing with EOT with dump, I would reconsider this decision, but this is the easiest way for me to deal with backup at this time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 06:59:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20816 for freebsd-current-outgoing; Wed, 21 Oct 1998 06:59:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20795 for ; Wed, 21 Oct 1998 06:59:33 -0700 (PDT) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id PAA29091; Wed, 21 Oct 1998 15:58:56 +0200 (CEST) Received: from cs.uni-sb.de (acc1-209.telip.uni-sb.de [134.96.113.209]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id PAA15383; Wed, 21 Oct 1998 15:58:56 +0200 (CEST) Message-ID: <362DE8E7.6D31C492@cs.uni-sb.de> Date: Wed, 21 Oct 1998 16:00:07 +0200 From: Daniel Rock X-Mailer: Mozilla 4.07 [de] (Win98; U) MIME-Version: 1.0 To: "Marc G. Fournier" CC: Alex Zepeda , freebsd-current@FreeBSD.ORG Subject: Re: Invalid option for compiler...? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc G. Fournier schrieb: > I generally do the 'make world' after I know the kernel is going > to run on my platform...I've already done the 'make buildworld', but need > to get a kernel built and reboot'd into first. > > How do I get rid of the -fformat-extensions -Werror flags? I've > checked /usr/share/mk/*, /etc/make.conf, > /usr/src/sys/i386/conf/Makefile.i386, and can't find it defined in any of > those places...which place am I missing? The kernel Makefile first tries to include /share/mk/bsd.kern.mk. It only includes /usr/src/share/mk/bsd.kern.mk, if /share/mk doesn't exist: .if exists($S/../share/mk) .include "$S/../share/mk/bsd.kern.mk" .else .include .endif Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 07:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26005 for freebsd-current-outgoing; Wed, 21 Oct 1998 07:40:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-37.ppp.wenet.net [206.15.85.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25999 for ; Wed, 21 Oct 1998 07:40:23 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id HAA00649; Wed, 21 Oct 1998 07:41:59 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 21 Oct 1998 07:41:59 -0700 (PDT) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: "Marc G. Fournier" cc: freebsd-current@FreeBSD.ORG Subject: Re: Invalid option for compiler...? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998, Marc G. Fournier wrote: > How do I get rid of the -fformat-extensions -Werror flags? I've > checked /usr/share/mk/*, /etc/make.conf, > /usr/src/sys/i386/conf/Makefile.i386, and can't find it defined in any of > those places...which place am I missing? /usr/src/share/mk/bsd.kern.mk IIRC. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 07:42:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26171 for freebsd-current-outgoing; Wed, 21 Oct 1998 07:42:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26164 for ; Wed, 21 Oct 1998 07:42:32 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id JAA20186; Wed, 21 Oct 1998 09:42:02 -0500 (CDT) Message-Id: <199810211442.JAA20186@ns.tar.com> From: "Richard Seaman, Jr." To: "Daniel Eischen" Cc: "current@freebsd.org" Date: Wed, 21 Oct 98 09:42:02 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998 09:18:22 -0400 (EDT), Daniel Eischen wrote: >> The condition can only be signaled when >> the condition spinlock is not held. So... why wouldn't you hold the >> condition spinlock as long as possible (ie. after the mutex unlock) >> and *then* set _thread_kern_in_sched = 1 after all the spinlocks have >> been done? > >If the thread doesn't own the mutex, then you've got the >condition variable locked while you're waiting for the >pthread_mutex_unlock(). Since this falls into the category >of "undefined behavior" it probably doesn't matter though. However, the thread should own the mutex shouldn't it? I thought the spec for pthread_cond_wait says it should return EINVAL if the thread doesn't own the mutex? However, its not clear to me that our pthread_cond_wait code makes this check (I think it doesn't). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 07:48:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26976 for freebsd-current-outgoing; Wed, 21 Oct 1998 07:48:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26969 for ; Wed, 21 Oct 1998 07:48:21 -0700 (PDT) (envelope-from jeff@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id JAA21246 for ; Wed, 21 Oct 1998 09:47:58 -0500 (CDT) Received: from harkol-51.isdn.mke.execpc.com(169.207.64.179) by peak.mountin.net via smap (V1.3) id sma021242; Wed Oct 21 09:47:34 1998 Message-Id: <3.0.3.32.19981021094325.00f6a88c@207.227.119.2> X-Sender: jeffm@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 09:43:25 -0500 To: freebsd-current@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: 3.0 missing some docs? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm.... This may be minor, but I noticed some empty directories in /usr/share/doc tutorials/ddwg: tutorials/devel: tutorials/diskformat: tutorials/disklessx: tutorials/fonts: tutorials/mh: tutorials/multios: tutorials/newuser: tutorials/ppp: tutorials/upgrade: There were other additons (ie es and ja), but there were empty. These are new since 2.2.7R. Oversight or on TDD list? FWIW, trying to find more info on CAM, for example what is the pass0 for, LINT doesn't say much, makes me wonder if it it's need or not in the kernel. PS - My workstation has a little green hat (with tassle) and is happily running an ELF kernel. So far all the ports I use are too. Little green hat off to the ports team. 8-) Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 08:02:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28474 for freebsd-current-outgoing; Wed, 21 Oct 1998 08:02:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28467 for ; Wed, 21 Oct 1998 08:02:54 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.9.1/8.8.8) with ESMTP id LAA07558; Wed, 21 Oct 1998 11:02:25 -0400 (EDT) (envelope-from scrappy@hub.org) Date: Wed, 21 Oct 1998 11:02:25 -0400 (EDT) From: "Marc G. Fournier" To: Alex Zepeda cc: freebsd-current@FreeBSD.ORG Subject: Re: Invalid option for compiler...? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998, Alex Zepeda wrote: > On Wed, 21 Oct 1998, Marc G. Fournier wrote: > > How do I get rid of the -fformat-extensions -Werror flags? I've > > checked /usr/share/mk/*, /etc/make.conf, > > /usr/src/sys/i386/conf/Makefile.i386, and can't find it defined in any of > > those places...which place am I missing? > > /usr/src/share/mk/bsd.kern.mk IIRC. Finally figured that one out :( kernel compiled, rebooted and all is well...make world done too :) I have a 431Meg expire process running right now, its soooo cool :) Thanks for all the help to everyone... Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@{postgresql|isc}.org ICQ#7615664 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 08:19:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29895 for freebsd-current-outgoing; Wed, 21 Oct 1998 08:19:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29886 for ; Wed, 21 Oct 1998 08:19:31 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA07958; Wed, 21 Oct 1998 11:19:01 -0400 (EDT) Date: Wed, 21 Oct 1998 11:19:01 -0400 (EDT) From: Daniel Eischen Message-Id: <199810211519.LAA07958@pcnet1.pcnet.com> To: eischen@vigrid.com, lists@tar.com Subject: Re: Another Serious libc_r problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >If the thread doesn't own the mutex, then you've got the > >condition variable locked while you're waiting for the > >pthread_mutex_unlock(). Since this falls into the category > >of "undefined behavior" it probably doesn't matter though. > > However, the thread should own the mutex shouldn't it? I thought > the spec for pthread_cond_wait says it should return EINVAL if > the thread doesn't own the mutex? However, its not clear to > me that our pthread_cond_wait code makes this check (I think > it doesn't). Yeah, we're saying the same thing. The thread *should* own the mutex, and then your solution works. If it doesn't own the mutex, then you've got a potential deadlock condition, but this could be deemed acceptable because POSIX says that "undefined behavior" will occur in this case. I don't have the POSIX spec handy, but I think you're right in that pthread_cond_wait should return EINVAL if the thread doesn't own the mutex. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 08:37:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01780 for freebsd-current-outgoing; Wed, 21 Oct 1998 08:37:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01775 for ; Wed, 21 Oct 1998 08:37:45 -0700 (PDT) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.1/8.9.1) with ESMTP id LAA18225 for ; Wed, 21 Oct 1998 11:37:13 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 21 Oct 1998 11:37:13 -0400 (EDT) From: "Alok K. Dhir" To: current@FreeBSD.ORG Subject: Vinum vs CCD? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi - I recently stumbled accross the existence of vinum in 3.0, and have a couple of simple questions: 1. How does vinum compare to CCD, specifically with regards to performance and stability? 2. Is anyone using Vinum on an SMP -current box with any horror/success stories? Thanks! Al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 08:42:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02138 for freebsd-current-outgoing; Wed, 21 Oct 1998 08:42:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from webc02.globecomm.net (www2.iname.net [165.251.12.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02131 for ; Wed, 21 Oct 1998 08:42:16 -0700 (PDT) (envelope-from slpalmer@email.com) From: slpalmer@email.com Received: by webc02.globecomm.net (8.9.1/8.8.0) id LAA22832 MIME-Version: 1.0 Message-Id: <9810211141364G.14328@webc02.globecomm.net> Date: Wed, 21 Oct 1998 11:41:36 -0400 (EDT) Content-Type: Text/Plain Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: Newbie (to development) would like to help Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings! I would like to join in on the FreeBSD project in whatever way I could. I don't know what the best route to go about this is, so I'll just give a quick list of what (I think) I'm capable of, and solicit suggestions. BACKGROUND: I first tried to run BSD/386 in '92 or so but had only a MicroChannel machine, and proting to a new arch was beyond me. I've run various GNU/Linux systems since .9x kernels, and used FreeBSD since version 2.1. I work for Sprint Paranet as a UN*X Technical Analyst doing everything from System Administration to Perl Development, and general UN*X Support. I am proficiant (not a wizard ;) at Perl5. I can read and understand most C code, although I'm not good at developing in C from scratch. HARDWARE: My home system is an AMD K6-233 w/ 64 meg of RAM and a Western Digital 6.4 gig Hard Disk (IDE/UDMA). I have a Zoom parallel-port full-motion-color camera (Like a Connectix color QuickCam) that I've not yet tried under FreeBSD, a small 10baseT network, HP JetDirect External, RIVA TNT based video card (I'm running the VGA16 server until it's supported). My system stays connected to the net (56k) from 8:00 AM CST to 5:00 PM CST. I CVSup FreeBSD-CURRENT and make world daily. (Since 3.0-RELEASE) During business hours my system can be reached at http://midearth.dyn.ml.org Any suggestions on how I can be more helpful? Stephen L. Palmer slpalmer@email.com ----------------------------------------------- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 09:32:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07050 for freebsd-current-outgoing; Wed, 21 Oct 1998 09:32:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07045 for ; Wed, 21 Oct 1998 09:32:04 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA23454; Wed, 21 Oct 1998 09:31:00 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 21 Oct 1998 09:30:59 -0700 (PDT) From: Doug White To: pam@polynet.lviv.ua cc: current@FreeBSD.ORG Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21 Oct 1998 pam@polynet.lviv.ua wrote: > Hi everybody! > > I want to generate FreeBSD-current system with MD5 crypted (hashed) > passwords, by default. it generates DES libcrypt libraries. Which build > flag changes that behaviour? Don't grab the src-secure dist, or (I think) it's the NOSECURE flag. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 09:35:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07333 for freebsd-current-outgoing; Wed, 21 Oct 1998 09:35:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07322 for ; Wed, 21 Oct 1998 09:35:35 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA24455; Wed, 21 Oct 1998 09:35:00 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 21 Oct 1998 09:34:58 -0700 (PDT) From: Doug White To: "Jeffrey J. Mountin" cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 missing some docs? In-Reply-To: <3.0.3.32.19981021094325.00f6a88c@207.227.119.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998, Jeffrey J. Mountin wrote: > Hmmm.... > > This may be minor, but I noticed some empty directories in /usr/share/doc > > tutorials/upgrade: Hm, looks like they were supposed to be there but didn't make it. Jordan? > FWIW, trying to find more info on CAM, for example what is the pass0 for, > LINT doesn't say much, makes me wonder if it it's need or not in the kernel. pass0 is required, it's the passhrough device for scsi devices. I think post-RELEASE -current has #warn stupid-checks. > PS - My workstation has a little green hat (with tassle) and is happily > running an ELF kernel. So far all the ports I use are too. > > Little green hat off to the ports team. 8-) 3.0 has been working beautifully on my prototype box. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 09:38:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07551 for freebsd-current-outgoing; Wed, 21 Oct 1998 09:38:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07544 for ; Wed, 21 Oct 1998 09:38:40 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA25031; Wed, 21 Oct 1998 09:38:09 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 21 Oct 1998 09:38:08 -0700 (PDT) From: Doug White To: slpalmer@email.com cc: FreeBSD Current Subject: Re: Newbie (to development) would like to help In-Reply-To: <9810211141364G.14328@webc02.globecomm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please wrap your lines at about 70 chracters. Thanks. On Wed, 21 Oct 1998 slpalmer@email.com wrote: > Greetings! > I would like to join in on the FreeBSD project in whatever way I > could. I don't know what the best route to go about this is, so I'll > just give a quick list of what (I think) I'm capable of, and solicit > suggestions. Welcome aboard! If you're looking for somewhere to plug yourself in, keep an eye on this list and/or hackers@freebsd.org. Also check the projects page at http://www.freebsd.org/projects/. We can alway use people for the doc project too. :) Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 09:46:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08886 for freebsd-current-outgoing; Wed, 21 Oct 1998 09:46:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08880 for ; Wed, 21 Oct 1998 09:46:41 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA10038; Wed, 21 Oct 1998 10:46:02 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810211646.KAA10038@panzer.plutotech.com> Subject: Re: 3.0 missing some docs? In-Reply-To: from Doug White at "Oct 21, 98 09:34:58 am" To: dwhite@resnet.uoregon.edu (Doug White) Date: Wed, 21 Oct 1998 10:46:02 -0600 (MDT) Cc: jeff@mountin.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote... > On Wed, 21 Oct 1998, Jeffrey J. Mountin wrote: > > > Hmmm.... > > > > This may be minor, but I noticed some empty directories in /usr/share/doc > > > > tutorials/upgrade: > > Hm, looks like they were supposed to be there but didn't make it. Jordan? > > > FWIW, trying to find more info on CAM, for example what is the pass0 for, > > LINT doesn't say much, makes me wonder if it it's need or not in the kernel. > > pass0 is required, it's the passhrough device for scsi devices. I think > post-RELEASE -current has #warn stupid-checks. Actually, it isn't required. It's highly recommended, but optional. Some folks might want to disable it for security reasons. I put warning messages in the transport layer so that when people go looking for a passthrough device, but don't have it in their kernel, they get hit on the head. I got tired of people asking me why camcontrol, cdrecord, or whatever didn't work. (don't worry, if you've asked me about that, you're in very good company...) If you're looking for documentation on the passthrough driver, RTFM. ("man pass") Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 10:03:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10662 for freebsd-current-outgoing; Wed, 21 Oct 1998 10:03:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA10657 for ; Wed, 21 Oct 1998 10:03:31 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 13811 invoked from network); 21 Oct 1998 17:03:03 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 21 Oct 1998 17:03:03 -0000 Date: Wed, 21 Oct 1998 12:03:02 -0500 (CDT) From: John Sconiers To: slpalmer@email.com cc: FreeBSD Current Subject: Re: Newbie (to development) would like to help In-Reply-To: <9810211141364G.14328@webc02.globecomm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998 slpalmer@email.com wrote: > > Greetings! > I would like to join in on the FreeBSD project in whatever way I could. I don't know what the best route to go about this is, so I'll just give a quick list of what (I think) I'm capable of, and solicit suggestions. > > BACKGROUND: > I first tried to run BSD/386 in '92 or so but had only a MicroChannel machine, and proting to a new arch was beyond me. I've run various GNU/Linux systems since .9x kernels, and used FreeBSD since version 2.1. > I work for Sprint Paranet as a UN*X Technical Analyst doing everything from System Administration to Perl Development, and general UN*X Support. > I am proficiant (not a wizard ;) at Perl5. I can read and understand most C code, although I'm not good at developing in C from scratch. > > HARDWARE: > My home system is an AMD K6-233 w/ 64 meg of RAM and a Western Digital 6.4 gig Hard Disk (IDE/UDMA). I have a Zoom parallel-port full-motion-color camera (Like a Connectix color QuickCam) that I've not yet tried under FreeBSD, a small 10baseT network, HP JetDirect External, RIVA TNT based video card (I'm running the VGA16 server until it's supported). Thus shoulf help you fix the support of XFREE86 http://www.nvidia.com/Marketing/Developer/OpenDrvDwn.nsf > > My system stays connected to the net (56k) from 8:00 AM CST to 5:00 PM CST. I CVSup FreeBSD-CURRENT and make world daily. (Since 3.0-RELEASE) During business hours my system can be reached at http://midearth.dyn.ml.org > > Any suggestions on how I can be more helpful? > > Stephen L. Palmer > slpalmer@email.com > > > ----------------------------------------------- > FREE! The World's Best Email Address @email.com > Reserve your name now at http://www.email.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 11:12:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18555 for freebsd-current-outgoing; Wed, 21 Oct 1998 11:12:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18529 for ; Wed, 21 Oct 1998 11:12:07 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@woof.lan.awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA03634; Wed, 21 Oct 1998 19:11:37 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id LAA01095; Wed, 21 Oct 1998 11:31:58 +0100 (BST) (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199810211031.LAA01095@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Kris Kennaway cc: Brian Somers , current@FreeBSD.ORG Subject: Re: Improper sharing of modem bandwidth In-reply-to: Your message of "Wed, 07 Oct 1998 14:36:02 BST." <199810071336.OAA01091@woof.lan.awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Oct 1998 11:31:58 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > If you're interested, you could try doing a ``s/20/100/'' in bundle.c > in src/usr.sbin/ppp and rebuilding & installing ppp. Perhaps the > ``20'' is a bit light. Did you try this ? > Opinions ? > > [.....] > > Kris > > -- > Brian , , > > Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 11:29:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20585 for freebsd-current-outgoing; Wed, 21 Oct 1998 11:29:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20580 for ; Wed, 21 Oct 1998 11:29:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA01141; Wed, 21 Oct 1998 11:32:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810211832.LAA01141@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd@magnet.geophysik.tu-freiberg.de cc: freebsd-current@FreeBSD.ORG Subject: Re: Unable to install 3.0-RELEASE with an AHA1542 ! In-reply-to: Your message of "Wed, 21 Oct 1998 09:14:32 +0200." <199810210714.JAA02191@magnet.geophysik.tu-freiberg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Oct 1998 11:32:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > Today I've tried to install a 3.0 RELEASE on a PII/350 > system (Gigabyte GA-6BA w. 128MB SDRAM) and an old 1542. > This configuration was only chosen to test the usability > from old LANCE based Network cards, dont say me that I > shouldn't use such a configuration :-) > > In the Storage menu from sysinstall I've choosen the > "Adaptec 154x SCSI Controller" (that has in this menu > no configurable port adresses and no IRQ's) > > When I boot up the system (Install Menu) and scroll backwards > the system says ahc0: not found at 0x134! > I know that is one of 6 possible adresses for the aha1542, > but the default is 0x330.... The 1542 is supported by the 'aha' driver, and this driver will search all of the supported locations for the 1542. There isn't a "Storage" menu in sysinstall. You should try booting without making any configuration changes first, and let the system try to sort itself out. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 11:46:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22850 for freebsd-current-outgoing; Wed, 21 Oct 1998 11:46:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22845 for ; Wed, 21 Oct 1998 11:46:25 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA18784; Wed, 21 Oct 1998 11:37:51 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdd18777; Wed Oct 21 18:37:43 1998 Message-ID: <362E29EC.41C67EA6@whistle.com> Date: Wed, 21 Oct 1998 11:37:32 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Chuck Robey CC: current@FreeBSD.ORG Subject: Re: Soft-Updates aware fsck available. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > On Tue, 20 Oct 1998, Julian Elischer wrote: > > > Kirk has supplied a 'soft-updates aware' fsck. > > It requires a small tweek to compile under FreeBSD > > but that's all. > > > > I've made the shar file available at: > > http://www.freebsd.org/~julian/ > > (at the bottom of the page). > > > > It probably needs to be merged into out present one (or maybe just > > replace it.. He suggests it's much improved. > > > > I will be away for a while so can't merge it, but if anyone feels like > > it'd be worth looking at, be my guest. > > Have you tried it, do you have any expectation it's really safe to > experiment with? > I have tried it which is how I know it requires a small tweek to compile :-) > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (NetBSD). > ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 12:08:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26003 for freebsd-current-outgoing; Wed, 21 Oct 1998 12:08:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25988 for ; Wed, 21 Oct 1998 12:08:04 -0700 (PDT) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.9.1) id OAA01527 for freebsd-current@freebsd.org; Wed, 21 Oct 1998 14:04:30 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 21 Oct 1998 14:04:30 -0500 (CDT) Reply-To: conrads@neosoft.com Organization: NeoSoft, Inc. From: Conrad Sabatier To: freebsd-current@FreeBSD.ORG Subject: This seems a little odd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG conrads@dolphin:/$ file kernel kernel: unknown pure executable 3.0-CURRENT, aout-to-elf upgrade from -stable on 10/19, custom aout kernel built on 10/21 -- Conrad Sabatier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 12:20:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27670 for freebsd-current-outgoing; Wed, 21 Oct 1998 12:20:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27664 for ; Wed, 21 Oct 1998 12:20:37 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id OAA22303; Wed, 21 Oct 1998 14:20:03 -0500 (CDT) Received: from klinzhai-1.isdn.mke.execpc.com(169.207.65.129) by peak.mountin.net via smap (V1.3) id sma022290; Wed Oct 21 14:19:35 1998 Message-Id: <3.0.3.32.19981021141506.00f0b3e4@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 14:15:06 -0500 To: Doug White From: "Jeffrey J. Mountin" Subject: Re: 3.0 missing some docs? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.19981021094325.00f6a88c@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:34 AM 10/21/98 -0700, Doug White wrote: >> tutorials/upgrade: > >Hm, looks like they were supposed to be there but didn't make it. Jordan? Worth pointing out. >pass0 is required, it's the passhrough device for scsi devices. I think >post-RELEASE -current has #warn stupid-checks. Even without Kenneth's response I would have to say "no" since I tested it. >3.0 has been working beautifully on my prototype box. I'm pleased and plan to move my upgrades schedules up. Interestingly before going to an ELF kernel my system had: Oct 18 07:58:26 local /kernel: stray irq 7 Oct 18 07:59:20 local last message repeated 3 times Oct 18 07:59:20 local /kernel: too many stray irq 7's; not logging any more Forget the why and how of this ugly problem, which it doesn't seem to be (this time at least). Strangly it would happen after a reboot, but nothing was going on. Only running the basic daemons, no sendmail, no crons, no network activity, and I never logged in (have to sleep now and again). Immediately after changing the kernel to ELF, poof! Gone. Only 3.0 release did this, never ever have I seen this on this box and it's been around since 2.1.5 with same hardware, barring a CPU fan and a change from a P133 -> P166 laying around. Odd thing since there is nothing using it and lpt0 is not compiled in the kernel, nor does the BIOS have the parallel port enabled. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 12:31:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28675 for freebsd-current-outgoing; Wed, 21 Oct 1998 12:31:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28669 for ; Wed, 21 Oct 1998 12:30:58 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id OAA22342; Wed, 21 Oct 1998 14:30:33 -0500 (CDT) Received: from klinzhai-1.isdn.mke.execpc.com(169.207.65.129) by peak.mountin.net via smap (V1.3) id sma022338; Wed Oct 21 14:30:06 1998 Message-Id: <3.0.3.32.19981021142537.00fe1ff4@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 14:25:37 -0500 To: "Kenneth D. Merry" From: "Jeffrey J. Mountin" Subject: Re: 3.0 missing some docs? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199810211646.KAA10038@panzer.plutotech.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:46 AM 10/21/98 -0600, Kenneth D. Merry wrote: >Actually, it isn't required. It's highly recommended, but optional. Some >folks might want to disable it for security reasons. There or not everything works. Don't understand the security part. However the man page does make reference, but: ls /dev/pa* crw------- 1 root operator 31, 0 Oct 17 22:58 /dev/pass0 crw------- 1 root operator 31, 1 Oct 17 22:58 /dev/pass1 crw------- 1 root operator 31, 2 Oct 17 22:58 /dev/pass2 crw------- 1 root operator 31, 3 Oct 17 22:58 /dev/pass3 How can userland? >I put warning messages in the transport layer so that when people go >looking for a passthrough device, but don't have it in their kernel, they >get hit on the head. I got tired of people asking me why camcontrol, >cdrecord, or whatever didn't work. (don't worry, if you've asked me about >that, you're in very good company...) Have yet to try a CDR on FBSD, but plan to (Philips 2600). FBSD doesn't seem to read Joilet from a M$ burn. A legend works for now, but I'd like to burn "base" systems to CD for checking against. >If you're looking for documentation on the passthrough driver, RTFM. ("man >pass") Don't believe I have a need to tinker with CAM, being transparent for the most part, AFAIC. Was thinking more along the lines of whitepaper. RTFM'ing man pages isn't fun, since references scatter one to the 4 winds. Guess I don't know the practical benefits or if/should there be any additional tweaks (mind you I only glaced through the pages and followed a few references). There is plenty of options if you need to debug. 8-) Somewhat related to what I started here is DPT card support. I've seen plenty of references to the 3334 cards, but from the "CD" HARDWARE.TXT:dpt n/a n/a n/a n/a DPT RAID SCSI controllers. RELNOTES.TXT:DPT SCSI/RAID controllers (most variants). Wondering about 2044/2144 support? Plan to use the 3334 for a few servers in the near future, but for home use a 2044 ($200) is sufficient. "Most variants" means "no test drive method for me, thank you." Rather know before buying or else it would be good for NT (bleh!). This should be more clear, after all there are not that many models. Checked in the sources and there is no reference for any model number, not suprising. cheers! Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 12:51:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01364 for freebsd-current-outgoing; Wed, 21 Oct 1998 12:51:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01357 for ; Wed, 21 Oct 1998 12:51:57 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA11348; Wed, 21 Oct 1998 13:51:26 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810211951.NAA11348@panzer.plutotech.com> Subject: Re: 3.0 missing some docs? In-Reply-To: <3.0.3.32.19981021142537.00fe1ff4@207.227.119.2> from "Jeffrey J. Mountin" at "Oct 21, 98 02:25:37 pm" To: jeff-ml@mountin.net (Jeffrey J. Mountin) Date: Wed, 21 Oct 1998 13:51:26 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeffrey J. Mountin wrote... > At 10:46 AM 10/21/98 -0600, Kenneth D. Merry wrote: > >Actually, it isn't required. It's highly recommended, but optional. Some > >folks might want to disable it for security reasons. > > There or not everything works. Don't understand the security part. > However the man page does make reference, but: > > ls /dev/pa* > crw------- 1 root operator 31, 0 Oct 17 22:58 /dev/pass0 > crw------- 1 root operator 31, 1 Oct 17 22:58 /dev/pass1 > crw------- 1 root operator 31, 2 Oct 17 22:58 /dev/pass2 > crw------- 1 root operator 31, 3 Oct 17 22:58 /dev/pass3 > > How can userland? How can userland ....what? If someone cracks root, they can wreak havoc with the passthrough driver. The disks have the same problem. e.g.: dd if=/dev/zero of=/dev/rda0s1a count=50 bs=1024k The stuff about permissions in the pass(4) man page is basically to warn system administrators that granting regular users access to the pass driver can be potentially dangerous. (just like granting access to disk device nodes can be dangerous) [ ... ] > >If you're looking for documentation on the passthrough driver, RTFM. ("man > >pass") > > Don't believe I have a need to tinker with CAM, being transparent for the > most part, AFAIC. Was thinking more along the lines of whitepaper. http://www.freebsd.org/~gibbs/ > RTFM'ing man pages isn't fun, since references scatter one to the 4 winds. That's the way it goes. [ ... ] > Somewhat related to what I started here is DPT card support. I've seen > plenty of references to the 3334 cards, but from the "CD" > > HARDWARE.TXT:dpt n/a n/a n/a n/a DPT RAID SCSI > controllers. > RELNOTES.TXT:DPT SCSI/RAID controllers (most variants). > > Wondering about 2044/2144 support? Plan to use the 3334 for a few servers > in the near future, but for home use a 2044 ($200) is sufficient. "Most > variants" means "no test drive method for me, thank you." Rather know > before buying or else it would be good for NT (bleh!). This should be more > clear, after all there are not that many models. Checked in the sources > and there is no reference for any model number, not suprising. RTFM ("man dpt"). Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:06:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03439 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:06:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from webc02.globecomm.net (www2.iname.net [165.251.12.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03434 for ; Wed, 21 Oct 1998 13:06:28 -0700 (PDT) (envelope-from slpalmer@email.com) From: slpalmer@email.com Received: by webc02.globecomm.net (8.9.1/8.8.0) id QAA12632 MIME-Version: 1.0 Message-Id: <9810211605510W.28561@webc02.globecomm.net> Date: Wed, 21 Oct 1998 16:05:51 -0400 (EDT) Content-Type: Text/Plain Content-Transfer-Encoding: 7bit To: John Sconiers Cc: freebsd-current@FreeBSD.ORG Subject: Re: Riva TNT Patch (Re: Newbie (to development) would like to help Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actualy, I was just reading the question about mounting a NT (SMB) Share like a NFS Mount. Linux has a utility (smbmount) to do exactly this. I looked in the -current ports and could not find an existing port. I have not yet looked at the source to smbmount, so I don't know how involved it would be to port it. If I feel it's doable though, I'm prepared to start on it. I'll get the source to smbmount tonight and look at it. Stephen L. Palmer slpalmer@email.com ---- On Oct 21 John Sconiers wrote: > > Sounds like a plan! > > > > > Did you have anything in mind? > > > > slpalmer > > > JOHN > ----------------------------------------------- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:08:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03626 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:08:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03618 for ; Wed, 21 Oct 1998 13:08:31 -0700 (PDT) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:37640 "HELO deskfix" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with SMTP id <7999-26621>; Wed, 21 Oct 1998 22:07:51 +0200 Message-ID: <00b701bdfd2e$7b29c5a0$1400000a@deskfix.local> From: "Jeroen C. van Gelderen" To: Subject: echo behaviour Date: Wed, 21 Oct 1998 22:07:50 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hallo, Today I stumbled on the problem of building a 'cross-platform' shell script for the sh shell. I noticed that the /bin/echo behaves differently then the sh built-in echo in reacting to the "\c" escape. FreeBSD sh accepts "\c" only when the -e flag is specified. FreeBSD /bin/echo accepts "\c" always and does not accept the -e flag Solaris sh accepts "\c" always and does not accept the -e flag Linux' built-in echo accepts "\c" only when the -e flag is specified. Why the inconsistency between the sh built-in and /bin/echo? Is it on purpose? If so, shouldn't the man-page be updated to reflect the inconsistency? If it's not on purpose: is conforming to the opengroup 'Single UNIX' considered a good idea? I'll patch if neccessary, please tell me what -if any- I should patch... Last but not least: is this the correct list? Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04120 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:11:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04111 for ; Wed, 21 Oct 1998 13:11:11 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id QAA14792; Wed, 21 Oct 1998 16:10:43 -0400 (EDT) Message-ID: <19981021161042.A14475@netmonger.net> Date: Wed, 21 Oct 1998 16:10:42 -0400 From: Christopher Masto To: freebsd-current@FreeBSD.ORG Subject: Panic starting X with current kernel? Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just cvsupped a couple of hours ago and ran a make world and built a new kernel. Now I get a panic when starting X: panic: vm_page_insert: already inserted Debugger("panic") Stopped at _Debugger+0x35: movb $0,_in_Debugger.98 db> trace _Debugger(f011b57f) at _Debugger+0x35 _panic(f01c0c25,80000000,f0aaf000,f5393d8c,f01b6581) at _panic+0x6f _vm_page_insert(f0aaf000,f53904c8,f4000,f056d9f8,400000) at _vm_page_insert+0x1e _dev_pager_getpages(f53904c8,f5393dd4,1,0,f5393dd8) at _dev_pager_getpages+0xc5 _vm_pager_get_pages(f53904c8,f5393dd4,1,0) at _vm_pager_get_pages+0x1f _pmap_object_init_pt(f5327160,28400000,f53904c8,f4000,400000,1) at _pmap_object_ init_pt+0xb9 _vm_mmap(f5327100,f5393ee8,400000,3,7) at _vm_mmap+0x298 _mmap(f5323340,f5393f94,2834343c,400000,f4000000) at _mmap+0x352 _syscall(27,27,f4000000,400000,efbfdb38) at _syscall+0x187 _Xint0x80_syscall() at _Xint0x80_syscall+0x2c I can boot my previous kernel (Oct 13) and this panic doesn't occur. I'm currently waiting for that machine to fsck so I can poke around. -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ Netscape pollution must be eradicated. - JEFF RAIKES, Group Vice President, Sales & Marketing, Microsoft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:16:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04950 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:16:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04945 for ; Wed, 21 Oct 1998 13:16:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01707; Wed, 21 Oct 1998 13:16:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810212016.NAA01707@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: slpalmer@email.com cc: John Sconiers , freebsd-current@FreeBSD.ORG Subject: Re: Riva TNT Patch (Re: Newbie (to development) would like to help In-reply-to: Your message of "Wed, 21 Oct 1998 16:05:51 EDT." <9810211605510W.28561@webc02.globecomm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Oct 1998 13:16:16 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actualy, > I was just reading the question about > mounting a NT (SMB) Share like a NFS Mount. > Linux has a utility (smbmount) to do exactly > this. I looked in the -current ports and > could not find an existing port. I have not > yet looked at the source to smbmount, so I > don't know how involved it would be to port > it. If I feel it's doable though, I'm > prepared to start on it. > > I'll get the source to smbmount tonight > and look at it. See the 'sharity' port. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:17:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05091 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:17:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA05081 for ; Wed, 21 Oct 1998 13:17:55 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 8689 invoked from network); 21 Oct 1998 20:17:27 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 21 Oct 1998 20:17:27 -0000 Date: Wed, 21 Oct 1998 15:17:27 -0500 (CDT) From: John Sconiers To: slpalmer@email.com cc: freebsd-current@FreeBSD.ORG Subject: Re: Riva TNT Patch (Re: Newbie (to development) would like to help In-Reply-To: <9810211605510W.28561@webc02.globecomm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actualy, > I was just reading the question about > mounting a NT (SMB) Share like a NFS Mount. > Linux has a utility (smbmount) to do exactly > this. I looked in the -current ports and > could not find an existing port. I have not > yet looked at the source to smbmount, so I > don't know how involved it would be to port > it. If I feel it's doable though, I'm > prepared to start on it. OK let me know....I have an idea about a port that I know exists in Linux and NetBSD. I forgot the name however it only allows a UFS to be be resized the way you want sort of like patrition magic. If I Find the name i would be willing to port that as well. JOHN > > I'll get the source to smbmount tonight > and look at it. > > Stephen L. Palmer > slpalmer@email.com > > > ---- On Oct 21 John Sconiers wrote: > > > Sounds like a plan! > > > > > > > > > > Did you have anything in mind? > > > > > > > slpalmer > > > > > JOHN > > > > > ----------------------------------------------- > FREE! The World's Best Email Address @email.com > Reserve your name now at http://www.email.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:19:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05389 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:19:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.linkdesign.com (relay.linkdesign.com [194.42.128.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05379 for ; Wed, 21 Oct 1998 13:19:34 -0700 (PDT) (envelope-from Claudia.Fahrner@Linkdesign.com) Received: from aen (office-access.linkdesign.com [194.42.131.135]) by relay.linkdesign.com (8.8.8/8.8.6) with SMTP id XAA18502; Wed, 21 Oct 1998 23:17:14 +0300 (EEST) Message-ID: <001c01bdfd30$01c09de0$87832ac2@aen> Reply-To: "Claudia Fahrner" From: "Claudia Fahrner" To: , "John Sconiers" Cc: Subject: Re: Riva TNT Patch (Re: Newbie (to development) would like to help Date: Wed, 21 Oct 1998 23:18:42 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG take a look at rumba in the ports directory ... -----Original Message----- From: slpalmer@email.com To: John Sconiers Cc: freebsd-current@FreeBSD.ORG Date: 21 October 1998 23:05 Subject: Re: Riva TNT Patch (Re: Newbie (to development) would like to help >Actualy, > I was just reading the question about >mounting a NT (SMB) Share like a NFS Mount. >Linux has a utility (smbmount) to do exactly >this. I looked in the -current ports and >could not find an existing port. I have not >yet looked at the source to smbmount, so I >don't know how involved it would be to port >it. If I feel it's doable though, I'm >prepared to start on it. > > I'll get the source to smbmount tonight >and look at it. > >Stephen L. Palmer >slpalmer@email.com > > > ---- On Oct 21 John Sconiers wrote: >> > Sounds like a plan! >> >> >> >> >> Did you have anything in mind? >> >> >> > slpalmer >> > >> JOHN >> > > >----------------------------------------------- >FREE! The World's Best Email Address @email.com >Reserve your name now at http://www.email.com > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:35:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07383 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:35:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07376 for ; Wed, 21 Oct 1998 13:35:39 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id QAA16254; Wed, 21 Oct 1998 16:35:12 -0400 (EDT) Message-ID: <19981021163511.A16058@netmonger.net> Date: Wed, 21 Oct 1998 16:35:11 -0400 From: Christopher Masto To: freebsd-current@FreeBSD.ORG Subject: Re: Panic starting X with current kernel? Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <19981021161042.A14475@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981021161042.A14475@netmonger.net>; from Christopher Masto on Wed, Oct 21, 1998 at 04:10:42PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 21, 1998 at 04:10:42PM -0400, Christopher Masto wrote: > I just cvsupped a couple of hours ago and ran a make world and built > a new kernel. Now I get a panic when starting X: > > panic: vm_page_insert: already inserted > Debugger("panic") > Stopped at _Debugger+0x35: movb $0,_in_Debugger.98 > db> trace > _Debugger(f011b57f) at _Debugger+0x35 > _panic(f01c0c25,80000000,f0aaf000,f5393d8c,f01b6581) at _panic+0x6f > _vm_page_insert(f0aaf000,f53904c8,f4000,f056d9f8,400000) at _vm_page_insert+0x1e > > _dev_pager_getpages(f53904c8,f5393dd4,1,0,f5393dd8) at _dev_pager_getpages+0xc5 > _vm_pager_get_pages(f53904c8,f5393dd4,1,0) at _vm_pager_get_pages+0x1f > _pmap_object_init_pt(f5327160,28400000,f53904c8,f4000,400000,1) at _pmap_object_ > init_pt+0xb9 > _vm_mmap(f5327100,f5393ee8,400000,3,7) at _vm_mmap+0x298 > _mmap(f5323340,f5393f94,2834343c,400000,f4000000) at _mmap+0x352 > _syscall(27,27,f4000000,400000,efbfdb38) at _syscall+0x187 > _Xint0x80_syscall() at _Xint0x80_syscall+0x2c > > I can boot my previous kernel (Oct 13) and this panic doesn't occur. > > I'm currently waiting for that machine to fsck so I can poke around. I backed out dg's PG_TABLED removal and I'm no longer getting a panic. I guess this means I'm only ignoring the real source of the problem, but I don't think I have enough time today to learn the VM system and figure out what's really going on. If anyone is working on this, I will be glad to test anything. -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ My view of Microsoft is that they had two goals in the last 10 years: to copy the Macintosh and to copy Lotus' success in the applications business. And they accomplished those goals. Now, they're kind of lost. I've told Bill that I think it's in Microsoft's best interest if NeXT becomes successful because we'll give him something to copy for the rest of this decade. - STEVE JOBS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:35:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07434 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:35:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07422 for ; Wed, 21 Oct 1998 13:35:51 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id QAA28826; Wed, 21 Oct 1998 16:34:57 -0400 (EDT) Date: Wed, 21 Oct 1998 16:34:55 -0400 (EDT) From: Chuck Robey To: "Jeroen C. van Gelderen" cc: freebsd-current@FreeBSD.ORG Subject: Re: echo behaviour In-Reply-To: <00b701bdfd2e$7b29c5a0$1400000a@deskfix.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998, Jeroen C. van Gelderen wrote: > Hallo, > > Today I stumbled on the problem of building a 'cross-platform' shell script > for the sh shell. I noticed that the /bin/echo behaves differently then the > sh built-in echo in reacting to the "\c" escape. > > FreeBSD sh accepts "\c" only when the -e flag is specified. > FreeBSD /bin/echo accepts "\c" always and does not accept the -e flag > Solaris sh accepts "\c" always and does not accept the -e flag > Linux' built-in echo accepts "\c" only when the -e flag is specified. > > Why the inconsistency between the sh built-in and /bin/echo? Is it on > purpose? If so, shouldn't the man-page be updated to reflect the > inconsistency? If it's not on purpose: is conforming to the opengroup > 'Single UNIX' considered a good idea? I'll patch if neccessary, please tell > me what -if any- I should patch... You really ought to search the mailing list archives, this has been beaten to death quite often ... ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:37:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07651 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:37:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA07644 for ; Wed, 21 Oct 1998 13:37:22 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zW4zy-000030-00; Wed, 21 Oct 1998 13:36:50 -0700 Date: Wed, 21 Oct 1998 13:36:47 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: slpalmer@email.com cc: John Sconiers , freebsd-current@FreeBSD.ORG Subject: Re: Riva TNT Patch (Re: Newbie (to development) would like to help In-Reply-To: <9810211605510W.28561@webc02.globecomm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998 slpalmer@email.com wrote: > Actualy, > I was just reading the question about > mounting a NT (SMB) Share like a NFS Mount. > Linux has a utility (smbmount) to do exactly > this. I looked in the -current ports and > could not find an existing port. I have not > yet looked at the source to smbmount, so I > don't know how involved it would be to port > it. If I feel it's doable though, I'm > prepared to start on it. > > I'll get the source to smbmount tonight > and look at it. > > Stephen L. Palmer > slpalmer@email.com smbmount and smbfs code is probably one of the most difficult projects you can attempt. You would have to understand filesystem operation in FreeBSD very well, and understand CIFS (SMB) very well too. The client side of CIFS is the most difficult because it requires kernel support. The server side (samba) is easy in comparison. FreeBSD users typically use Rhumba, which translates SMB to NFS, so it SMB shares can be mounted as if they were NFS. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:50:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09308 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:50:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09302 for ; Wed, 21 Oct 1998 13:50:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01892; Wed, 21 Oct 1998 13:50:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810212050.NAA01892@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Sconiers cc: slpalmer@email.com, freebsd-current@FreeBSD.ORG Subject: Re: Riva TNT Patch (Re: Newbie (to development) would like to help In-reply-to: Your message of "Wed, 21 Oct 1998 15:17:27 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Oct 1998 13:50:03 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Actualy, > > I was just reading the question about > > mounting a NT (SMB) Share like a NFS Mount. > > Linux has a utility (smbmount) to do exactly > > this. I looked in the -current ports and > > could not find an existing port. I have not > > yet looked at the source to smbmount, so I > > don't know how involved it would be to port > > it. If I feel it's doable though, I'm > > prepared to start on it. > > > OK let me know....I have an idea about a port that I know exists in Linux > and NetBSD. I forgot the name however it only allows a UFS to be be > resized the way you want sort of like patrition magic. If I Find the name > i would be willing to port that as well. ufsresize. Source in the archives, or ask Der Mouse for it. It'd definitely be worth having. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:53:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09777 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:53:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09760 for ; Wed, 21 Oct 1998 13:53:40 -0700 (PDT) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:53512 "HELO deskfix" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with SMTP id <7997-26619>; Wed, 21 Oct 1998 22:52:56 +0200 Message-ID: <00c001bdfd34$c7843920$1400000a@deskfix.local> From: "Jeroen C. van Gelderen" To: Subject: Re: echo behaviour Date: Wed, 21 Oct 1998 22:52:56 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Chuck Robey >You really ought to search the mailing list archives, this has been >beaten to death quite often ... Whoops, sorry! Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 13:59:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10409 for freebsd-current-outgoing; Wed, 21 Oct 1998 13:59:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10402 for ; Wed, 21 Oct 1998 13:59:40 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id PAA22891; Wed, 21 Oct 1998 15:59:05 -0500 (CDT) Received: from klinzhai-1.isdn.mke.execpc.com(169.207.65.129) by peak.mountin.net via smap (V1.3) id sma022889; Wed Oct 21 15:58:37 1998 Message-Id: <3.0.3.32.19981021155403.010d90d0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 15:54:03 -0500 To: conrads@neosoft.com, freebsd-current@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: This seems a little odd In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:04 PM 10/21/98 -0500, Conrad Sabatier wrote: > >conrads@dolphin:/$ file kernel >kernel: unknown pure executable > >3.0-CURRENT, aout-to-elf upgrade from -stable on 10/19, custom aout kernel built >on 10/21 The kernel is aout that's why: kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped kernel.GENERIC: unknown pure executable kernel.old: unknown pure executable not stripped The first is my elf kernel, 2nd is obvious, and kernel.old is my last tweaked aout kernel. I'm sure there is a more technical explanation, but nothing is wrong with what you see. The "not stripped" makes me wonder what happens if it is stripped, as apparently the GENERIC is. No programmer here, but do recall the need to strip certain things after compilation on BSDi. If it works.... Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:03:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10708 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:03:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10701 for ; Wed, 21 Oct 1998 14:03:21 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA25137; Wed, 21 Oct 1998 14:02:45 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma025135; Wed Oct 21 14:02:20 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA28227; Wed, 21 Oct 1998 14:02:19 -0700 (PDT) From: Archie Cobbs Message-Id: <199810212102.OAA28227@bubba.whistle.com> Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) In-Reply-To: from Doug White at "Oct 21, 98 09:30:59 am" To: dwhite@resnet.uoregon.edu (Doug White) Date: Wed, 21 Oct 1998 14:02:19 -0700 (PDT) Cc: pam@polynet.lviv.ua, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White writes: > > I want to generate FreeBSD-current system with MD5 crypted (hashed) > > passwords, by default. it generates DES libcrypt libraries. Which build > > flag changes that behaviour? > > Don't grab the src-secure dist, or (I think) it's the NOSECURE flag. Or, just change the /usr/lib/libcrypt* symlinks to point to libscrypt instead of libdescrypt. It seems like "I want libdes available" and "I want passwords encrypted with DES instead of MD5" are completely independent variables... Can't these two not be forcibly linked together in the install process? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:08:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11272 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:08:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11264 for ; Wed, 21 Oct 1998 14:08:47 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA25212; Wed, 21 Oct 1998 14:08:16 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma025208; Wed Oct 21 14:07:56 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA28265; Wed, 21 Oct 1998 14:07:56 -0700 (PDT) From: Archie Cobbs Message-Id: <199810212107.OAA28265@bubba.whistle.com> Subject: Re: Another Serious libc_r problem In-Reply-To: <199810211519.LAA07958@pcnet1.pcnet.com> from Daniel Eischen at "Oct 21, 98 11:19:01 am" To: eischen@vigrid.com (Daniel Eischen) Date: Wed, 21 Oct 1998 14:07:56 -0700 (PDT) Cc: eischen@vigrid.com, lists@tar.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen writes: > the mutex, and then your solution works. If it doesn't own > the mutex, then you've got a potential deadlock condition, > but this could be deemed acceptable because POSIX says that > "undefined behavior" will occur in this case. Random interjected comment.. I would argue that for any case that POSIX says results in "undefined behavior", and the pthread code can easily detect this case, FreeBSD should immediately abort(3). Threads programmers will thank you when their bugs are revealed for them. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:10:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11487 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:10:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11468 for ; Wed, 21 Oct 1998 14:10:09 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id VAA14054; Wed, 21 Oct 1998 21:46:15 +0100 (BST) (envelope-from nik) Message-ID: <19981021214615.41943@nothing-going-on.org> Date: Wed, 21 Oct 1998 21:46:15 +0100 From: Nik Clayton To: "Jeffrey J. Mountin" , freebsd-current@FreeBSD.ORG Subject: Re: 3.0 missing some docs? References: <3.0.3.32.19981021094325.00f6a88c@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <3.0.3.32.19981021094325.00f6a88c@207.227.119.2>; from Jeffrey J. Mountin on Wed, Oct 21, 1998 at 09:43:25AM -0500 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 21, 1998 at 09:43:25AM -0500, Jeffrey J. Mountin wrote: > This may be minor, but I noticed some empty directories in /usr/share/doc > > tutorials/ddwg: [...] Is there a /usr/share/doc/en? If so, they're in there. N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:11:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11646 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:11:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11637 for ; Wed, 21 Oct 1998 14:11:29 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id RAA07616; Wed, 21 Oct 1998 17:10:45 -0400 (EDT) Date: Wed, 21 Oct 1998 17:10:45 -0400 (EDT) From: Chuck Robey To: "Jeroen C. van Gelderen" cc: freebsd-current@FreeBSD.ORG Subject: Re: echo behaviour In-Reply-To: <00c001bdfd34$c7843920$1400000a@deskfix.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998, Jeroen C. van Gelderen wrote: > From: Chuck Robey > >You really ought to search the mailing list archives, this has been > >beaten to death quite often ... > > Whoops, sorry! I like my own personal mistakes bigger and showier. You're just an amateur! You should (please, should NOT) look up some of my classics. I'm not saying you're right or wrong, either. BTW, there's a short shell script somewhere in the archives, shows how to portably test and set your shell scripts to just DTRT in respect to echo. Let me know if you can't find it. That's the way to handle your problem. I just wanted to avoid a lot of discussion in current on that. Too much noise on current lately, because of all the upheaval. You understand. > > Cheers, > Jeroen > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:12:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11695 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:12:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11688 for ; Wed, 21 Oct 1998 14:12:00 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id QAA22995; Wed, 21 Oct 1998 16:11:36 -0500 (CDT) Received: from klinzhai-1.isdn.mke.execpc.com(169.207.65.129) by peak.mountin.net via smap (V1.3) id sma022990; Wed Oct 21 16:11:18 1998 Message-Id: <3.0.3.32.19981021160643.010d94a4@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 16:06:43 -0500 To: "Kenneth D. Merry" From: "Jeffrey J. Mountin" Subject: Re: 3.0 missing some docs? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199810211951.NAA11348@panzer.plutotech.com> References: <3.0.3.32.19981021142537.00fe1ff4@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:51 PM 10/21/98 -0600, Kenneth D. Merry wrote: >How can userland ....what? You answer it below. >If someone cracks root, they can wreak havoc with the passthrough driver. >The disks have the same problem. e.g.: > >dd if=/dev/zero of=/dev/rda0s1a count=50 bs=1024k > >The stuff about permissions in the pass(4) man page is basically to warn >system administrators that granting regular users access to the pass driver >can be potentially dangerous. (just like granting access to disk device >nodes can be dangerous) If they get root, there are plenty of things they *can* do. This is then notable, but trivial. >http://www.freebsd.org/~gibbs/ > >> RTFM'ing man pages isn't fun, since references scatter one to the 4 winds. > >That's the way it goes. You page does help me follow them better. Thanks. 8-) >RTFM ("man dpt"). No manual entry for dpt No manual entry for dpt0 Ahhh, yeah (BTDT). FWIW, a find comes with with nada too. Another oversight? Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:17:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12454 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:17:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12443 for ; Wed, 21 Oct 1998 14:17:45 -0700 (PDT) (envelope-from karl@tdx.com) Received: from tdx.com (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id WAA11376; Wed, 21 Oct 1998 22:16:50 +0100 (BST) Message-ID: <362E4EF8.49B8315E@tdx.com> Date: Wed, 21 Oct 1998 22:15:36 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: conrads@neosoft.com CC: current@FreeBSD.ORG Subject: Re: This seems a little odd References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I get this: caladan> file /kernel /kernel: unknown pure executable not stripped My system is CAM, ELF, current as of the 19th of October... The Kernel is an a.out debug kernel, stripped with 'strip -d -aout' before being installed... Odd - yes... Worrying? - Hmmm, system seems to work OK... :-) Regards, Karl Conrad Sabatier wrote: > > conrads@dolphin:/$ file kernel > kernel: unknown pure executable > > 3.0-CURRENT, aout-to-elf upgrade from -stable on 10/19, custom aout kernel built > on 10/21 > > -- > Conrad Sabatier > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:22:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13071 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:22:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13049 for ; Wed, 21 Oct 1998 14:22:35 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA16655; Wed, 21 Oct 1998 17:21:59 -0400 (EDT) Date: Wed, 21 Oct 1998 17:21:59 -0400 (EDT) From: Daniel Eischen Message-Id: <199810212121.RAA16655@pcnet1.pcnet.com> To: archie@whistle.com, eischen@vigrid.com Subject: Re: Another Serious libc_r problem Cc: current@FreeBSD.ORG, lists@tar.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Random interjected comment.. > > I would argue that for any case that POSIX says results in "undefined > behavior", and the pthread code can easily detect this case, FreeBSD > should immediately abort(3). Threads programmers will thank you > when their bugs are revealed for them. If it's like pthread_mutex_lock(), POSIX will say that pthread_cond_wait should return EINVAL if it doesn't own the mutex *and* this condition is detected by the implementation. Much as we'd like to say "Bad programmer, Bad!" I don't think POSIX will allow us to with anything other than an EINVAL return value. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:27:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13592 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:27:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13585 for ; Wed, 21 Oct 1998 14:27:56 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id PAA11988; Wed, 21 Oct 1998 15:27:26 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810212127.PAA11988@panzer.plutotech.com> Subject: Re: 3.0 missing some docs? In-Reply-To: <3.0.3.32.19981021160643.010d94a4@207.227.119.2> from "Jeffrey J. Mountin" at "Oct 21, 98 04:06:43 pm" To: jeff-ml@mountin.net (Jeffrey J. Mountin) Date: Wed, 21 Oct 1998 15:27:26 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeffrey J. Mountin wrote... > At 01:51 PM 10/21/98 -0600, Kenneth D. Merry wrote: > >http://www.freebsd.org/~gibbs/ > > > >> RTFM'ing man pages isn't fun, since references scatter one to the 4 winds. > > > >That's the way it goes. > > You page does help me follow them better. Thanks. 8-) > > >RTFM ("man dpt"). > > No manual entry for dpt > No manual entry for dpt0 > > Ahhh, yeah (BTDT). FWIW, a find comes with with nada too. > > Another oversight? Yes. You're out of date. {roadwarrior:/usr/src/share/man/man4/man4.i386:7:0} cvs log dpt.4 RCS file: /usr/local/cvs/src/share/man/man4/man4.i386/dpt.4,v Working file: dpt.4 head: 1.1 branch: locks: strict access list: symbolic names: keyword substitution: kv total revisions: 1; selected revisions: 1 description: ---------------------------- revision 1.1 date: 1998/10/16 22:00:55; author: ken; state: Exp; Add the dpt(4) man page. Reviewed by: ken Submitted by: gibbs ============================================================================= Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:32:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14347 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:32:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14323 for ; Wed, 21 Oct 1998 14:32:03 -0700 (PDT) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.9.1) id QAA09077; Wed, 21 Oct 1998 16:28:18 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <362E4EF8.49B8315E@tdx.com> Date: Wed, 21 Oct 1998 16:28:18 -0500 (CDT) Reply-To: conrads@neosoft.com Organization: NeoSoft, Inc. From: Conrad Sabatier To: Karl Pielorz Subject: Re: This seems a little odd Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Oct-98 Karl Pielorz wrote: > Hi, > > I get this: > > caladan> file /kernel > /kernel: unknown pure executable not stripped > > My system is CAM, ELF, current as of the 19th of October... The Kernel is an > a.out debug kernel, stripped with 'strip -d -aout' before being installed... > > Odd - yes... Worrying? - Hmmm, system seems to work OK... :-) I agree. :-) Not a worrisome thing, just not what I expected. The system *is* working great. I'm very, very pleased with this upgrade. -- Conrad Sabatier Mollison's Bureaucracy Hypothesis: If an idea can survive a bureaucratic review and be implemented it wasn't worth doing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:33:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14502 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:33:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14489 for ; Wed, 21 Oct 1998 14:33:22 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id RAA01626; Wed, 21 Oct 1998 17:35:07 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Wed, 21 Oct 1998 17:35:07 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Daniel Eischen cc: current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem In-Reply-To: <199810212121.RAA16655@pcnet1.pcnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG while we're on the subject, does anyone know the defined behavior when a threaded process fork()s? i can't seem to find anything in the small library of stevens books i've been collecting over the past couple of years. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Wed, 21 Oct 1998, Daniel Eischen wrote: > > Random interjected comment.. > > > > I would argue that for any case that POSIX says results in "undefined > > behavior", and the pthread code can easily detect this case, FreeBSD > > should immediately abort(3). Threads programmers will thank you > > when their bugs are revealed for them. > > If it's like pthread_mutex_lock(), POSIX will say that pthread_cond_wait > should return EINVAL if it doesn't own the mutex *and* this condition > is detected by the implementation. Much as we'd like to say "Bad > programmer, Bad!" I don't think POSIX will allow us to with anything > other than an EINVAL return value. > > Dan Eischen > eischen@vigrid.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:38:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15453 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:38:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15439 for ; Wed, 21 Oct 1998 14:38:21 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA25475; Wed, 21 Oct 1998 14:37:16 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma025471; Wed Oct 21 14:36:47 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA28470; Wed, 21 Oct 1998 14:36:47 -0700 (PDT) From: Archie Cobbs Message-Id: <199810212136.OAA28470@bubba.whistle.com> Subject: Re: Another Serious libc_r problem In-Reply-To: <199810212121.RAA16655@pcnet1.pcnet.com> from Daniel Eischen at "Oct 21, 98 05:21:59 pm" To: eischen@vigrid.com (Daniel Eischen) Date: Wed, 21 Oct 1998 14:36:47 -0700 (PDT) Cc: current@FreeBSD.ORG, lists@tar.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen writes: > > Random interjected comment.. > > > > I would argue that for any case that POSIX says results in "undefined > > behavior", and the pthread code can easily detect this case, FreeBSD > > should immediately abort(3). Threads programmers will thank you > > when their bugs are revealed for them. > > If it's like pthread_mutex_lock(), POSIX will say that pthread_cond_wait > should return EINVAL if it doesn't own the mutex *and* this condition > is detected by the implementation. Much as we'd like to say "Bad > programmer, Bad!" I don't think POSIX will allow us to with anything > other than an EINVAL return value. What you've described looks like *defined* behavior to me... -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 14:57:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17368 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:57:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eesn17.ews.uiuc.edu (eesn17.ews.uiuc.edu [130.126.161.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17361 for ; Wed, 21 Oct 1998 14:57:47 -0700 (PDT) (envelope-from ramasubr@ews.uiuc.edu) Received: from localhost (ramasubr@localhost) by eesn17.ews.uiuc.edu (8.8.8/8.7.3) with SMTP id QAA14986; Wed, 21 Oct 1998 16:57:16 -0500 (CDT) X-Authentication-Warning: eesn17.ews.uiuc.edu: ramasubr owned process doing -bs Date: Wed, 21 Oct 1998 16:57:16 -0500 (CDT) From: Vijay Ramasubramanian To: "Justin T. Gibbs" cc: current@FreeBSD.ORG Subject: Re: Installation probs w/3.0 In-Reply-To: <199810201932.NAA29092@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wanted to let you know that I successfully built the Linux 2.0.34 kernel on the RedHat installation I told you about. The build process seemed to fly, and of course, no signal 11s or anything. This leads me to believe that nothing's wrong with the hardware itself... .______ | Vijay N. Ramasubramanian mailto:ramasubr@ews.uiuc.edu http://www.ews.uiuc.edu/~ramasubr/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 15:21:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19829 for freebsd-current-outgoing; Wed, 21 Oct 1998 15:21:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19820 for ; Wed, 21 Oct 1998 15:21:48 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id RAA23363; Wed, 21 Oct 1998 17:21:07 -0500 (CDT) Received: from klinzhai-1.isdn.mke.execpc.com(169.207.65.129) by peak.mountin.net via smap (V1.3) id sma023361; Wed Oct 21 17:20:42 1998 Message-Id: <3.0.3.32.19981021171559.010e0654@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 17:15:59 -0500 To: Nik Clayton , freebsd-current@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: 3.0 missing some docs? In-Reply-To: <19981021214615.41943@nothing-going-on.org> References: <3.0.3.32.19981021094325.00f6a88c@207.227.119.2> <3.0.3.32.19981021094325.00f6a88c@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:46 PM 10/21/98 +0100, Nik Clayton wrote: >On Wed, Oct 21, 1998 at 09:43:25AM -0500, Jeffrey J. Mountin wrote: >> This may be minor, but I noticed some empty directories in /usr/share/doc >> >> tutorials/ddwg: >[...] > >Is there a /usr/share/doc/en? If so, they're in there. No checked /usr/src/share as well. The may have appeared, but at the moment I'm holding at 3.0R with daily sups for the ports. Suppose Jordan has already submitted 3.0 for pressing. No matter, just a point of notice for possible fixing or errata. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 15:46:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22201 for freebsd-current-outgoing; Wed, 21 Oct 1998 15:46:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dewdrop2.mindspring.com (dewdrop2.mindspring.com [207.69.200.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22154 for ; Wed, 21 Oct 1998 15:45:59 -0700 (PDT) (envelope-from stevensl@mindspring.net) Received: from freelove.mindspring.net (freelove.mindspring.net [207.69.192.92]) by dewdrop2.mindspring.com (8.8.5/8.8.5) with SMTP id SAA28736 for ; Wed, 21 Oct 1998 18:45:22 -0400 (EDT) Date: Wed, 21 Oct 1998 18:51:25 -0400 (EDT) From: steven To: current@FreeBSD.ORG Subject: 3.0-Current/3Com 509B ether problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi gang. first off.. 3.0 is great! but i have a problem that no posts seems to clearly identify or fix. i've got a 3com 509b ISA ethernet card. It worked fine with 2.2.6 2.2.7 and an early Sept 3.0 install. I went to the last BETA and the bootup stopped seeing the card. I went 3.0-current and same thing. dmesg shows.. fd0: 1.44MB 3.5in ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 npx0 on motherboard before 3.0 it never detected anything on ie0 and ep0 was always what i used for the card. I swapped the card into my Windows box and the card does appear to work. Ideas? Steven S. >>> 403forbidden.net "You don't blame the camera for pornography. Why do you blame the gun for murder?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 15:56:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23263 for freebsd-current-outgoing; Wed, 21 Oct 1998 15:56:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23242 for ; Wed, 21 Oct 1998 15:56:02 -0700 (PDT) (envelope-from ugc!ugc.ab.ca!geoff@scanner.worldgate.com) Received: from ugc.UUCP (uucp@localhost) by scanner.worldgate.com (8.9.1a/8.9.1) with UUCP id QAA22736; Wed, 21 Oct 1998 16:55:23 -0600 (MDT) Received: from pcugc(really [192.139.124.2]) by ugc.ugc.ab.ca via sendmail with smtp id for ; Wed, 21 Oct 1998 16:39:34 -0600 (MDT) (Smail-3.2.0.92 1997-Feb-9 #1 built 1997-Apr-3) Message-Id: Comments: Authenticated sender is From: "Geoff Coleman" Organization: UGC Consulting Ltd To: Mike Smith Date: Wed, 21 Oct 1998 16:50:51 -700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Unable to install 3.0-RELEASE with an AHA1542 ! Reply-to: geoff@ugc.ab.ca CC: freebsd-current@FreeBSD.ORG In-reply-to: <199810211832.LAA01141@dingo.cdrom.com> References: Your message of "Wed, 21 Oct 1998 09:14:32 +0200." <199810210714.JAA02191@magnet.geophysik.tu-freiberg.de> X-mailer: Pegasus Mail for Win32 (v2.54) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've encountered the same problem with a 1540B. it would appear to be a timing issue. If I put lots of debug messages in and boot verbose then it will some times see the card. This is a machine that has been ruuning Freebsd CURRENT for some time. About a week ago I picked up the latest patches and now new kernel's will not see the controller. This is filed as PR/8340 Geoff Coleman > > Hi, > > > > Today I've tried to install a 3.0 RELEASE on a PII/350 > > system (Gigabyte GA-6BA w. 128MB SDRAM) and an old 1542. > > This configuration was only chosen to test the usability > > from old LANCE based Network cards, dont say me that I > > shouldn't use such a configuration :-) > > > > In the Storage menu from sysinstall I've choosen the > > "Adaptec 154x SCSI Controller" (that has in this menu > > no configurable port adresses and no IRQ's) > > > > When I boot up the system (Install Menu) and scroll backwards > > the system says ahc0: not found at 0x134! > > I know that is one of 6 possible adresses for the aha1542, > > but the default is 0x330.... > > The 1542 is supported by the 'aha' driver, and this driver will search > all of the supported locations for the 1542. > > There isn't a "Storage" menu in sysinstall. You should try booting > without making any configuration changes first, and let the system try > to sort itself out. > > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 15:56:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23313 for freebsd-current-outgoing; Wed, 21 Oct 1998 15:56:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23257 for ; Wed, 21 Oct 1998 15:56:04 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id RAA23447; Wed, 21 Oct 1998 17:55:08 -0500 (CDT) Received: from klinzhai-1.isdn.mke.execpc.com(169.207.65.129) by peak.mountin.net via smap (V1.3) id sma023442; Wed Oct 21 17:54:51 1998 Message-Id: <3.0.3.32.19981021175006.010e16fc@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 17:50:06 -0500 To: "Kenneth D. Merry" From: "Jeffrey J. Mountin" Subject: Re: 3.0 missing some docs? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199810212127.PAA11988@panzer.plutotech.com> References: <3.0.3.32.19981021160643.010d94a4@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:27 PM 10/21/98 -0600, Kenneth D. Merry wrote: >> Another oversight? > >Yes. You're out of date. Er, I'm not supping right now (duck). My 3.0 system drive is going to be swapped out shortly to a production system. >{roadwarrior:/usr/src/share/man/man4/man4.i386:7:0} cvs log dpt.4 > >RCS file: /usr/local/cvs/src/share/man/man4/man4.i386/dpt.4,v >Working file: dpt.4 >head: 1.1 >branch: >locks: strict >access list: >symbolic names: >keyword substitution: kv >total revisions: 1; selected revisions: 1 >description: >---------------------------- >revision 1.1 >date: 1998/10/16 22:00:55; author: ken; state: Exp; >Add the dpt(4) man page. > >Reviewed by: ken >Submitted by: gibbs >============================================================================= Many other commits for man pages about this time. Will they be lacking on the 3.0 CD as well? Even 2.2.7R had dpt support, but no man pages (Merged to -stable I hope). Maybe worth mention in errata? Begging Jordan's pardon. Guess I could do a selective sup without perterbing 3.0R too much. Plan to be -current within 2 weeks (also should have dual-PPro by then as well). Very happy with 3.0 and will be upgrading my server much sooner than expected. Just don't care to introduce any new bugs. ;) Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 16:08:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24914 for freebsd-current-outgoing; Wed, 21 Oct 1998 16:08:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24906 for ; Wed, 21 Oct 1998 16:08:19 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA06855; Wed, 21 Oct 1998 16:09:00 -0700 (PDT) Message-Id: <199810212309.QAA06855@implode.root.com> To: Christopher Masto cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic starting X with current kernel? In-reply-to: Your message of "Wed, 21 Oct 1998 16:10:42 EDT." <19981021161042.A14475@netmonger.net> From: David Greenman Reply-To: dg@root.com Date: Wed, 21 Oct 1998 16:09:00 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I just cvsupped a couple of hours ago and ran a make world and built >a new kernel. Now I get a panic when starting X: > >panic: vm_page_insert: already inserted Fixed in rev 1.33 of sys/vm/device_pager.c. Thanks for the bug report (especially the traceback!). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 16:50:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29985 for freebsd-current-outgoing; Wed, 21 Oct 1998 16:50:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29979 for ; Wed, 21 Oct 1998 16:50:36 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA21178; Thu, 22 Oct 1998 09:19:32 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id JAA01225; Thu, 22 Oct 1998 09:19:23 +0930 (CST) Message-ID: <19981022091922.A1219@freebie.lemis.com> Date: Thu, 22 Oct 1998 09:19:22 +0930 From: Greg Lehey To: Bruce Albrecht Cc: Jaime Bozza , current@FreeBSD.ORG Subject: Re: Subdividing synthetic disks (was: newfs problems, more information:) References: <13868.3117.390224.376379@zuhause.zuhause.mn.org> <003801bdfc74$da58cae0$313d31cc@electron.nuc.net> <13869.12610.899877.506387@zuhause.zuhause.mn.org> <19981021180032.X21008@freebie.lemis.com> <13869.58445.435772.587309@zuhause.zuhause.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <13869.58445.435772.587309@zuhause.zuhause.mn.org>; from Bruce Albrecht on Wed, Oct 21, 1998 at 08:40:29AM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 21 October 1998 at 8:40:29 -0500, Bruce Albrecht wrote: > Greg Lehey writes: >>> I never had any problem doing so. Here's my ccd's disklabel entry: >>> >>> (snip) >> >> Why do you want to do this? Would you still find a reason to do it >> with vinum? > > I have a 3 disk CCD with multiple partitions set up because it appears > to improve transfer rates by about 50% (IIRC) over having each > partition on a separate drive. I know you advocate using one very > large partition, but I prefer to keep my partitions small enough so > that I can dump any of them to a 90 meter DAT tape (roughly 2 GB) > without having to deal with tape swap. I have a DAT autoloader, so if > there's an automated way of dealing with EOT with dump, I would > reconsider this decision, but this is the easiest way for me to deal > with backup at this time. Hmm. Yes, that's a valid reason. It wouldn't be with vinum, because you could then just create individual volumes. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 17:38:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04119 for freebsd-current-outgoing; Wed, 21 Oct 1998 17:38:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04095 for ; Wed, 21 Oct 1998 17:37:59 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA21346; Thu, 22 Oct 1998 10:07:28 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA01449; Thu, 22 Oct 1998 10:07:27 +0930 (CST) Message-ID: <19981022100727.C1219@freebie.lemis.com> Date: Thu, 22 Oct 1998 10:07:27 +0930 From: Greg Lehey To: dg@root.com Cc: FreeBSD current users Subject: inetd still dying (was: cvs commit: src/sys/cam/scsi scsi_da.c src/sys/i386/i386 busdma_machdep.c vm_machdep.c src/sys/i386/ibcs2 imgact_coff.c src/sys/i386/include param.h src/sys/i386/isa isa.c wd.c src/sys/kern imgact_elf.c sys_pipe.c sysv_shm.c vfs_b References: <199810131154.EAA12696@implode.root.com> <19981014071356.S21983@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981014071356.S21983@freebie.lemis.com>; from Greg Lehey on Wed, Oct 14, 1998 at 07:13:56AM +0930 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 14 October 1998 at 7:13:56 +0930, Greg Lehey wrote: > On Tuesday, 13 October 1998 at 4:54:04 -0700, David Greenman wrote: >>> On Tue, 13 Oct 1998, David Greenman wrote: >>> >>>> dg 1998/10/13 01:24:45 PDT >>>> Log: >>>> Fixed two potentially serious classes of bugs: >>> >>> David, I'm having the inetd type problem on a system I can't bring to >>> current, it's using a kernel from back in August, but I was wondering if >>> it might be worth my while to see if these changes might possibly >>> backport that far, without breaking other things. Could I get your >>> non-binding guess on that, would it be worth my time to see if I could >>> do that? >>> >>> It's the problem that seems to be caused by starvation. >> >> It shouldn't be too difficult to port the changes to an August kernel. It >> is possible that this commit might fix the problem, but I'm fairly skeptical. >> It would probably be wise to wait and see if someone who is running up-to-date >> -current and was having the inetd problem can do some testing >> first. > > I've been having the problem, but only every couple of days. It still > existed yesterday. I'll report if it happens again. It happened again. I put inetd into gdb, but I couldn't find a way to resolve library addresses. It works if I start a program, but apparently not if I attach to it. Can anybody give me some pointers (like how to find the load address of a library)? This is a real -current but still using a.out binaries. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 17:48:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05353 for freebsd-current-outgoing; Wed, 21 Oct 1998 17:48:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05342 for ; Wed, 21 Oct 1998 17:48:52 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA21393; Thu, 22 Oct 1998 10:18:17 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA01575; Thu, 22 Oct 1998 10:18:15 +0930 (CST) Message-ID: <19981022101814.D1219@freebie.lemis.com> Date: Thu, 22 Oct 1998 10:18:14 +0930 From: Greg Lehey To: "Alok K. Dhir" , current@FreeBSD.ORG Subject: Re: Vinum vs CCD? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Alok K. Dhir on Wed, Oct 21, 1998 at 11:37:13AM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 21 October 1998 at 11:37:13 -0400, Alok K. Dhir wrote: > > Hi - I recently stumbled accross the existence of vinum in 3.0, and have a > couple of simple questions: > > 1. How does vinum compare to CCD, specifically with regards to > performance and stability? We haven't done much performance testing. My indications, using dd from a raw volume, are that even with the current debug code in Vinum, it will drop performance by about 2% compared to a standard partition. The throughput of both raw partition and raw volume was in the order of 10 MB/s (this is a new IBM IDE drive). I haven't tried it with ccd, but I don't expect much difference. Usingn striping, you can improve overall performance with multiple access only, so it wouldn't show up with a simple dd. When I have time, I'll start doing some serious performance comparisons. > 2. Is anyone using Vinum on an SMP -current box with any horror/success > stories? Yes, with both :-) It seems to work fine with IDE drives, but a couple of people have reported problems in conjunction with CAM and the RAID-5 version. We haven't quite identified the causes, but it seems that under some situations CAM will return an I/O error, and Vinum doesn't always handle it correctly. I'm working on the Vinum side of this problem; the CAM side may be due to incorrect termination which only shows up in typical highly concurrent access patterns which Vinum RAID-5 causes, or in one case it's been suggested that the power supply can't handle the demands of several drives being accessed concurrently. We don't have any specific evidence of a CAM problem. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 17:57:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06021 for freebsd-current-outgoing; Wed, 21 Oct 1998 17:57:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06016 for ; Wed, 21 Oct 1998 17:57:03 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA21432; Thu, 22 Oct 1998 10:26:33 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA01620; Thu, 22 Oct 1998 10:26:32 +0930 (CST) Message-ID: <19981022102631.F1219@freebie.lemis.com> Date: Thu, 22 Oct 1998 10:26:31 +0930 From: Greg Lehey To: Karl Pielorz , conrads@neosoft.com Cc: current@FreeBSD.ORG Subject: Re: This seems a little odd References: <362E4EF8.49B8315E@tdx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <362E4EF8.49B8315E@tdx.com>; from Karl Pielorz on Wed, Oct 21, 1998 at 10:15:36PM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 21 October 1998 at 22:15:36 +0100, Karl Pielorz wrote: > Conrad Sabatier wrote: >> >> conrads@dolphin:/$ file kernel >> kernel: unknown pure executable >> >> 3.0-CURRENT, aout-to-elf upgrade from -stable on 10/19, custom aout kernel built >> on 10/21 > > I get this: > > caladan> file /kernel > /kernel: unknown pure executable not stripped > > My system is CAM, ELF, current as of the 19th of October... The Kernel is an > a.out debug kernel, stripped with 'strip -d -aout' before being installed... This has nothing to do with the ELF transition. Kernels are not quite your standard a.out file. From a 2.2.7 machine: $ file /kernel /kernel: unknown pure executable Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 18:08:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07074 for freebsd-current-outgoing; Wed, 21 Oct 1998 18:08:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07067 for ; Wed, 21 Oct 1998 18:08:01 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id VAA07017; Wed, 21 Oct 1998 21:06:18 -0400 (EDT) Date: Wed, 21 Oct 1998 21:06:18 -0400 (EDT) From: Daniel Eischen Message-Id: <199810220106.VAA07017@pcnet1.pcnet.com> To: archie@whistle.com, eischen@vigrid.com Subject: Re: Another Serious libc_r problem Cc: current@FreeBSD.ORG, lists@tar.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Daniel Eischen writes: > > > Random interjected comment.. > > > > > > I would argue that for any case that POSIX says results in "undefined > > > behavior", and the pthread code can easily detect this case, FreeBSD > > > should immediately abort(3). Threads programmers will thank you > > > when their bugs are revealed for them. > > > > If it's like pthread_mutex_lock(), POSIX will say that pthread_cond_wait > > should return EINVAL if it doesn't own the mutex *and* this condition > > is detected by the implementation. Much as we'd like to say "Bad > > programmer, Bad!" I don't think POSIX will allow us to with anything > > other than an EINVAL return value. > > What you've described looks like *defined* behavior to me... Well, that's what the POSIX spec says. If you are going to detect the condition, then you must return EINVAL. If you are not going to detect the condition, then "undefined behavior" occurs. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 19:35:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15930 for freebsd-current-outgoing; Wed, 21 Oct 1998 19:35:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15925 for ; Wed, 21 Oct 1998 19:35:46 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA13922; Wed, 21 Oct 1998 19:35:16 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd013908; Wed Oct 21 19:35:15 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA14623; Wed, 21 Oct 1998 19:35:14 -0700 (MST) From: Terry Lambert Message-Id: <199810220235.TAA14623@usr01.primenet.com> Subject: Re: Riva TNT Patch (Re: Newbie (to development) would like to help To: tom@uniserve.com (Tom) Date: Thu, 22 Oct 1998 02:35:14 +0000 (GMT) Cc: slpalmer@email.com, jrs@enteract.com, freebsd-current@FreeBSD.ORG In-Reply-To: from "Tom" at Oct 21, 98 01:36:47 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > smbmount and smbfs code is probably one of the most difficult projects > you can attempt. You would have to understand filesystem operation in > FreeBSD very well, and understand CIFS (SMB) very well too. The client > side of CIFS is the most difficult because it requires kernel support. Actually, it's not the hard. The bugger is that you need to proxy credentials to the remote server on a per user basis. Newer versions of SMB allow this, but you can't make it work uniformly without creating an active session manager program to act as a credential holder for the older servers. > The server side (samba) is easy in comparison. I'll let Jeremey Allison comment on that, if he's listening. 8-). > FreeBSD users typically use Rhumba, which translates SMB to NFS, so it > SMB shares can be mounted as if they were NFS. Right. Note that they get mounted as a single credential, which basically destroys the ability to centrally manage access to resources on a per account basis on your NT server (i.e., it is intentional damage to the security model). This is what makes it so painful to implement: to implement it right requires that you avoid damaging the NT security model, and it's very different (unless you allow the FreeBSD box to be a domain controller client, in which case, you damage the UNIX security model, since it has a requirement that you not use easily crackable passwords or cleartext keys 8-)). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 19:37:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16113 for freebsd-current-outgoing; Wed, 21 Oct 1998 19:37:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16104 for ; Wed, 21 Oct 1998 19:37:23 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA09950; Wed, 21 Oct 1998 19:36:51 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd009929; Wed Oct 21 19:36:46 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA14737; Wed, 21 Oct 1998 19:36:44 -0700 (MST) From: Terry Lambert Message-Id: <199810220236.TAA14737@usr01.primenet.com> Subject: Re: inetd still dying (was: cvs commit: src/sys/cam/scsi scsi_da.c src/sys/i386/i386 busdma_machdep.c vm_machdep.c src/sys/i386/ibcs To: grog@lemis.com (Greg Lehey) Date: Thu, 22 Oct 1998 02:36:44 +0000 (GMT) Cc: dg@root.com, FreeBSD-current@FreeBSD.ORG In-Reply-To: <19981022100727.C1219@freebie.lemis.com> from "Greg Lehey" at Oct 22, 98 10:07:27 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Inre: the subject. I am reminded of the Paul Reubens character in the original "Buffy the Vampire Slayer" movie... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 19:47:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17126 for freebsd-current-outgoing; Wed, 21 Oct 1998 19:47:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17099; Wed, 21 Oct 1998 19:47:23 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA17694; Wed, 21 Oct 1998 19:46:51 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd017678; Wed Oct 21 19:46:45 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA15164; Wed, 21 Oct 1998 19:46:44 -0700 (MST) From: Terry Lambert Message-Id: <199810220246.TAA15164@usr01.primenet.com> Subject: Re: FAT32 support for 3.0 installation To: dmm125@bellatlantic.net (Donn Miller) Date: Thu, 22 Oct 1998 02:46:44 +0000 (GMT) Cc: mike@smith.net.au, questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <000401bdfc03$1f396b00$02000003@dmm125> from "Donn Miller" at Oct 20, 98 04:24:55 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problems I'm having are that I boot up on the boot floppy (boot.flp). > Then when it gets to the point of the installation where it tries to extract > the distributions off my FAT32 partition, I get an error to the effect that > the following distributions weren't found: bin manpages proflibs des compat. > Basically, all of them. I thought that maybe sysinstall expected a certain > combination of uppercase/lowercase letter combinations. Like: > > C:\FreeBSD\bin > C:\FREEBSD\bin > C:\freebsd\BIN > C:\Freebsd\bin etc. since now we are working with case-sensitive filenames > with msdos. This requires kernel globbing to implement. Specifically, FAT32 and HPFS are case-sensitive on storage, case insensitive on lookup". The only way you can implement a case insensitive lookup for an interative traversal function is to perform globbing in the kernel such that the first iterated value that matches with the implied strncasecmp in place of the strncmp can be returned. Basically, in order to support FAT32 semantics fully, you have to *become* FAT32 (an unpleasent prospect). I would suggest that if FAT instead of FAT32 were used, that you use the mount option to force returned values into lowercase. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 19:50:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17528 for freebsd-current-outgoing; Wed, 21 Oct 1998 19:50:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17523 for ; Wed, 21 Oct 1998 19:50:45 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA14444; Wed, 21 Oct 1998 19:50:16 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd014421; Wed Oct 21 19:50:13 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA15310; Wed, 21 Oct 1998 19:50:12 -0700 (MST) From: Terry Lambert Message-Id: <199810220250.TAA15310@usr01.primenet.com> Subject: Re: cvsup and file permissions To: jdp@polstra.com (John Polstra) Date: Thu, 22 Oct 1998 02:50:12 +0000 (GMT) Cc: chris@netmonger.net, current@FreeBSD.ORG In-Reply-To: <199810201452.HAA04158@austin.polstra.com> from "John Polstra" at Oct 20, 98 07:52:28 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Regardless, it would be nice to have a way to tell cvsup not to sync > > permissions. > > That feature's on my to-do list. I think I might actually get some > time to work on CVSup again in the not-to-distant future. > > Meanwhile, try changing the umask as I suggested in my other mail. > I'm pretty sure that will work. Oh, oh, let me vote for "implied vendor branch" again, then, so that you can do local branches and checkouts and merges relative to a steadily advancing "vendor branch" CVSup'ed from "the vendor". It would be *too cool* if someone were to cause sendmail, ISC BIND, and other CVS maintained projects from other vendors to show up in FreeBSD as a constantly updated vendor branch. I'm pretty sure the Ports people would like this, too. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 20:35:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21044 for freebsd-current-outgoing; Wed, 21 Oct 1998 20:35:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat0997.mpoweredpc.net [142.177.191.235]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21018 for ; Wed, 21 Oct 1998 20:34:59 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id AAA04950 for ; Thu, 22 Oct 1998 00:34:17 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 22 Oct 1998 00:34:16 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: How to strip a kernel in 3.0-RELEASE... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morning... Just had the pleasure of installing 3.0-RELEASE on a new drive, and just hit something unexpected...'strip -d kernel' just doesn't seem to work anymore :) What is the current method of doign this? Looking at the man pages between the old and new strip, I suspect just: strip --strip-debug kernel But is there another that I want to do too? According to the old, -d did both debugging and 'empty' symbols... Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 20:45:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22132 for freebsd-current-outgoing; Wed, 21 Oct 1998 20:45:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup11.gaffaneys.com [208.155.161.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22084 for ; Wed, 21 Oct 1998 20:45:09 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id DAA23406 for FreeBSD-current@FreeBSD.ORG; Thu, 22 Oct 1998 03:45:39 GMT (envelope-from zach) Message-ID: <19981021224539.A10190@znh.org> Date: Wed, 21 Oct 1998 22:45:39 -0500 From: Zach Heilig To: FreeBSD-current@FreeBSD.ORG Subject: cdda2wav == panic (/sys/vm/vm_page.c:516) Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is an ELF kernel compiled from sources cvsup-ed ~01:50 GMT (Oct 22) Relevent hardware: ncr0: rev 0x04 int a irq 11 on pci0.13.0 cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: cd present [176612 x 2048 byte records] The ncr0 is a diamond fireport 40, and the cdr is the only device on that bus (it is in an external case, with a terminator plugged into the passthrough connector). It works very well burning audio/data tracks and reading data tracks. I noticed this earlier today with a kernel from Oct 10. The panic with an up to date kernel is different from the Oct 10 kernel. That kernel would usually wait until cdda2wav exited before panic'ing (complaining about dirty pages -- the last 5-10 megs or so of the track would be zero's after reboot), today's kernel panics 8-10 Mbytes into the track (at least the 3 times I tried to read an audio track). stack trace: GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 2895872 initial pcb at 25efcc panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffd6 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01e44e0 stack pointer = 0x10:0xf48dacac frame pointer = 0x10:0xf48dacb4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 332 (cdda2wav) interrupt mask = bio panic: from debugger syncing disks... 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 giving up 1: dev:00020400, flags:21020034, blkno:131376, lblkno:131376 2: dev:00020400, flags:21020034, blkno:131264, lblkno:131264 3: dev:00020407, flags:20000010, blkno:3880032, lblkno:3880032 4: dev:00020407, flags:20000010, blkno:3880016, lblkno:3880016 5: dev:00020407, flags:21000034, blkno:3866672, lblkno:3866672 6: dev:00020407, flags:21020034, blkno:3801184, lblkno:3801184 7: dev:00020404, flags:21020034, blkno:65648, lblkno:65648 8: dev:00020404, flags:21020034, blkno:66128, lblkno:66128 9: dev:00020404, flags:21020034, blkno:65664, lblkno:65664 10: dev:00020404, flags:21020034, blkno:66096, lblkno:66096 11: dev:00020407, flags:21000034, blkno:2032, lblkno:2032 12: dev:ffffffff, flags:20020014, blkno:3936800, lblkno:4267 13: dev:ffffffff, flags:20020014, blkno:3936784, lblkno:4266 14: dev:ffffffff, flags:20020014, blkno:3936768, lblkno:4265 15: dev:ffffffff, flags:20020014, blkno:3936752, lblkno:4264 16: dev:ffffffff, flags:20020014, blkno:3936704, lblkno:4261 17: dev:ffffffff, flags:20020014, blkno:3936720, lblkno:4262 18: dev:ffffffff, flags:20020034, blkno:3936736, lblkno:4263 19: dev:ffffffff, flags:20020014, blkno:3936688, lblkno:4260 20: dev:00020407, flags:21020034, blkno:2883648, lblkno:2883648 21: dev:00020407, flags:21000034, blkno:16, lblkno:16 22: dev:ffffffff, flags:20000030, blkno:4275, lblkno:4275 23: dev:00020407, flags:21020034, blkno:1048736, lblkno:1048736 24: dev:00020400, flags:21020034, blkno:131280, lblkno:131280 25: dev:00020407, flags:20000010, blkno:3934192, lblkno:3934192 26: dev:ffffffff, flags:220202b0, blkno:3934192, lblkno:-4108 27: dev:00020407, flags:21000034, blkno:3932208, lblkno:3932208 28: dev:00020400, flags:21020034, blkno:65600, lblkno:65600 29: dev:00020400, flags:21020034, blkno:196672, lblkno:196672 dumping to dev 20401, offset 262144 dump 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 268 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 #1 0xf01478bc in at_shutdown (function=0xf022901e , arg=0xf48daba8, queue=-267228095) at ../../kern/kern_shutdown.c:430 #2 0xf0126ca1 in db_panic (addr=-266451744, have_addr=0, count=-1, modif=0xf48dab30 "") at ../../ddb/db_command.c:432 #3 0xf0126c41 in db_command (last_cmdp=0xf0246804, cmd_table=0xf0246664, aux_cmd_tablep=0xf025c4e4) at ../../ddb/db_command.c:332 #4 0xf0126d06 in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf0129067 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #6 0xf01ec719 in kdb_trap (type=12, code=0, regs=0xf48dac70) at ../../i386/i386/db_interface.c:157 #7 0xf01f6d93 in trap_fatal (frame=0xf48dac70) at ../../i386/i386/trap.c:874 #8 0xf01f6a84 in trap_pfault (frame=0xf48dac70, usermode=0) at ../../i386/i386/trap.c:772 #9 0xf01f66d7 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -236365800, tf_esi = 8550, tf_ebp = -192041804, tf_isp = -192041832, tf_ebx = 51390, tf_edx = 65470, tf_ecx = -192026224, tf_eax = -264085512, tf_trapno = 12, tf_err = 0, tf_eip = -266451744, tf_cs = 8, tf_eflags = 66054, tf_esp = 0, tf_ss = 0}) at ../../i386/i386/trap.c:396 #10 0xf01e44e0 in vm_page_lookup (object=0xf48de990, pindex=8550) at ../../vm/vm_page.c:516 #11 0xf01630c7 in allocbuf (bp=0xf1e95818, size=8192) at ../../kern/vfs_bio.c:1782 #12 0xf0162cb2 in getblk (vp=0xf48a82c0, blkno=4275, size=8192, slpflag=0, slptimeo=0) at ../../kern/vfs_bio.c:1557 #13 0xf01cb09f in ffs_balloc (ap=0xf48dae98) at ../../ufs/ffs/ffs_balloc.c:297 #14 0xf01d38a4 in ffs_write (ap=0xf48daeec) at vnode_if.h:1015 #15 0xf016dc17 in vn_write (fp=0xf0b28640, uio=0xf48daf30, cred=0xf0a59b00) at vnode_if.h:331 #16 0xf014f9a2 in write (p=0xf4834e00, uap=0xf48daf84) at ../../kern/sys_generic.c:270 #17 0xf01f7017 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 805601292, tf_esi = 805601292, tf_ebp = 805730652, tf_isp = -192041004, tf_ebx = 129360, tf_edx = 805601292, tf_ecx = 0, tf_eax = 4, tf_trapno = 7, tf_err = 2, tf_eip = 671874136, tf_cs = 31, tf_eflags = 582, tf_esp = -272640664, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #18 0xf01ed06c in Xint0x80_syscall () (kgdb) -- Zach Heilig If it looks like a duck, and quacks like a duck, we have to at least consider the possibility that we have a small aquatic bird of the family Anatidæ on our hands (Douglas Adams -- Dirk Gently's Holistic Detective Agency) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 20:49:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22513 for freebsd-current-outgoing; Wed, 21 Oct 1998 20:49:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22482 for ; Wed, 21 Oct 1998 20:49:04 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id XAA08404; Wed, 21 Oct 1998 23:48:04 -0400 (EDT) Date: Wed, 21 Oct 1998 23:48:03 -0400 (EDT) From: Chuck Robey To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: How to strip a kernel in 3.0-RELEASE... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998, The Hermit Hacker wrote: > > Morning... > > Just had the pleasure of installing 3.0-RELEASE on a new drive, > and just hit something unexpected...'strip -d kernel' just doesn't seem to > work anymore :) > > What is the current method of doign this? Looking at the man > pages between the old and new strip, I suspect just: > > strip --strip-debug kernel > > But is there another that I want to do too? According to the old, > -d did both debugging and 'empty' symbols... Kernel's still aout ... try this: env OBJFORMAT=aout strip -d kernel That'll work. Have you checked out how the system deals with dual sets of build tools? This is probably boring to most, but I think it's the keenest thing, the way that stuff that needs to be aout or elf depending on the setting of OBJFORMAT exists in /usr/libexec/elf or /usr/libexec/aout, and the guys that get called in /usr/bin, like /usr/bin/ld, really just use /usr/bin/objformat to pick what kind of format you want, then kick off the real tool for you. You set /etc/objformat to have a single line, OBJFORMAT=, or you use a environmental variable. The make aout to elf does the /etc/objformat setting for you, so you can just adjust things temporarily with the environmental vars very nicely. Works for ports just as nicely. Sorry for the lecture, but maybe some don't know this (and I _am_ impressed by it all!) ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 21:11:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24301 for freebsd-current-outgoing; Wed, 21 Oct 1998 21:11:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup21.gaffaneys.com [208.155.161.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24296 for ; Wed, 21 Oct 1998 21:11:30 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id EAA00448; Thu, 22 Oct 1998 04:11:42 GMT (envelope-from zach) Message-ID: <19981021231142.A434@znh.org> Date: Wed, 21 Oct 1998 23:11:42 -0500 From: Zach Heilig To: Chuck Robey , The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: How to strip a kernel in 3.0-RELEASE... References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chuck Robey on Wed, Oct 21, 1998 at 11:48:03PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 21, 1998 at 11:48:03PM -0400, Chuck Robey wrote: > Kernel's still aout ... try this: > > env OBJFORMAT=aout strip -d kernel > > That'll work. Or, check /usr/src/etc/make.conf, and note there is a new variable: KERNFORMAT= elf as for which command to use to strip it... I tried the --strip-debug option, and it seems to work... -- Zach Heilig If it looks like a duck, and quacks like a duck, we have to at least consider the possibility that we have a small aquatic bird of the family Anatidæ on our hands (Douglas Adams -- Dirk Gently's Holistic Detective Agency) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 21:16:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24618 for freebsd-current-outgoing; Wed, 21 Oct 1998 21:16:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24550 for ; Wed, 21 Oct 1998 21:16:00 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id XAA14666; Wed, 21 Oct 1998 23:15:19 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id XAA05302; Wed, 21 Oct 1998 23:14:22 -0500 (CDT) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13870.45342.532896.964071@zuhause.zuhause.mn.org> Date: Wed, 21 Oct 1998 23:14:22 -0500 (CDT) To: Greg Lehey Cc: Jaime Bozza , current@FreeBSD.ORG Subject: Re: Subdividing synthetic disks (was: newfs problems, more information:) In-Reply-To: <19981022091922.A1219@freebie.lemis.com> References: <13868.3117.390224.376379@zuhause.zuhause.mn.org> <003801bdfc74$da58cae0$313d31cc@electron.nuc.net> <13869.12610.899877.506387@zuhause.zuhause.mn.org> <19981021180032.X21008@freebie.lemis.com> <13869.58445.435772.587309@zuhause.zuhause.mn.org> <19981022091922.A1219@freebie.lemis.com> X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > On Wednesday, 21 October 1998 at 8:40:29 -0500, Bruce Albrecht wrote: > > Greg Lehey writes: > >>> I never had any problem doing so. Here's my ccd's disklabel entry: > >>> > >>> (snip) > >> > >> Why do you want to do this? Would you still find a reason to do it > >> with vinum? > > > > I have a 3 disk CCD with multiple partitions set up because it appears > > to improve transfer rates by about 50% (IIRC) over having each > > partition on a separate drive. I know you advocate using one very > > large partition, but I prefer to keep my partitions small enough so > > that I can dump any of them to a 90 meter DAT tape (roughly 2 GB) > > without having to deal with tape swap. > > Hmm. Yes, that's a valid reason. It wouldn't be with vinum, because > you could then just create individual volumes. So each vinum volume is a logical disk, and you still get the performance boost from striping, but you get the other vinum features as well, such as raid-5 and the ability to add additional space to a volume on the fly? In my case, I'd just create volumes that are 2 GB or less. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 21:18:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24782 for freebsd-current-outgoing; Wed, 21 Oct 1998 21:18:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24775 for ; Wed, 21 Oct 1998 21:18:09 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA22054; Thu, 22 Oct 1998 13:47:32 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA29155; Thu, 22 Oct 1998 13:47:31 +0930 (CST) Message-ID: <19981022134731.R1219@freebie.lemis.com> Date: Thu, 22 Oct 1998 13:47:31 +0930 From: Greg Lehey To: Bruce Albrecht Cc: Jaime Bozza , current@FreeBSD.ORG Subject: Re: Subdividing synthetic disks (was: newfs problems, more information:) References: <13868.3117.390224.376379@zuhause.zuhause.mn.org> <003801bdfc74$da58cae0$313d31cc@electron.nuc.net> <13869.12610.899877.506387@zuhause.zuhause.mn.org> <19981021180032.X21008@freebie.lemis.com> <13869.58445.435772.587309@zuhause.zuhause.mn.org> <19981022091922.A1219@freebie.lemis.com> <13870.45342.532896.964071@zuhause.zuhause.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <13870.45342.532896.964071@zuhause.zuhause.mn.org>; from Bruce Albrecht on Wed, Oct 21, 1998 at 11:14:22PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 21 October 1998 at 23:14:22 -0500, Bruce Albrecht wrote: > Greg Lehey writes: >> On Wednesday, 21 October 1998 at 8:40:29 -0500, Bruce Albrecht wrote: >>> Greg Lehey writes: >>>>> I never had any problem doing so. Here's my ccd's disklabel entry: >>>>> >>>>> (snip) >>>> >>>> Why do you want to do this? Would you still find a reason to do it >>>> with vinum? >>> >>> I have a 3 disk CCD with multiple partitions set up because it appears >>> to improve transfer rates by about 50% (IIRC) over having each >>> partition on a separate drive. I know you advocate using one very >>> large partition, but I prefer to keep my partitions small enough so >>> that I can dump any of them to a 90 meter DAT tape (roughly 2 GB) >>> without having to deal with tape swap. >> >> Hmm. Yes, that's a valid reason. It wouldn't be with vinum, because >> you could then just create individual volumes. > > So each vinum volume is a logical disk, and you still get the performance > boost from striping, but you get the other vinum features as well, such as > raid-5 and the ability to add additional space to a volume on the > fly? Correct. Note that ufs currently won't let you do much with the additional space, but it could be useful for swap. > In my case, I'd just create volumes that are 2 GB or less. Precisely. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 21:18:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24801 for freebsd-current-outgoing; Wed, 21 Oct 1998 21:18:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup21.gaffaneys.com [208.155.161.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24794 for ; Wed, 21 Oct 1998 21:18:18 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id EAA00473 for FreeBSD-current@FreeBSD.ORG; Thu, 22 Oct 1998 04:18:50 GMT (envelope-from zach) Message-ID: <19981021231850.B434@znh.org> Date: Wed, 21 Oct 1998 23:18:50 -0500 From: Zach Heilig To: FreeBSD-current@FreeBSD.ORG Subject: Re: cdda2wav == panic (/sys/vm/vm_page.c:516) References: <19981021224539.A10190@znh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: <19981021224539.A10190@znh.org>; from Zach Heilig on Wed, Oct 21, 1998 at 10:45:39PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I should also note that this form of the 'cdda2wav' command doesn't panic: cdda2wav -N ... -N keeps it from writing the disk file (not very useful). -- Zach Heilig If it looks like a duck, and quacks like a duck, we have to at least consider the possibility that we have a small aquatic bird of the family Anatidæ on our hands (Douglas Adams -- Dirk Gently's Holistic Detective Agency) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 21:24:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25169 for freebsd-current-outgoing; Wed, 21 Oct 1998 21:24:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-35.ppp.wenet.net [206.15.85.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25161 for ; Wed, 21 Oct 1998 21:24:35 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id VAA24973; Wed, 21 Oct 1998 21:25:58 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 21 Oct 1998 21:25:57 -0700 (PDT) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Chuck Robey cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: How to strip a kernel in 3.0-RELEASE... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998, Chuck Robey wrote: [...] > Kernel's still aout ... try this: > > env OBJFORMAT=aout strip -d kernel > > That'll work. Why not just use strip -aout -d kernel? And if you've got an elf kernel, strip -g (or --strip-debug) is the correct thing to do. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 21:57:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27117 for freebsd-current-outgoing; Wed, 21 Oct 1998 21:57:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA27110 for ; Wed, 21 Oct 1998 21:57:28 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zWCng-0001av-00; Wed, 21 Oct 1998 22:56:40 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id WAA09077 for ; Wed, 21 Oct 1998 22:57:14 -0600 (MDT) Message-Id: <199810220457.WAA09077@harmony.village.org> To: current@FreeBSD.ORG Subject: file 3.26 from christos Date: Wed, 21 Oct 1998 22:57:14 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to update our file from its current rev to file 3.26 that christos appears to be maintaining for NetBSD. I'd like to do this in the /usr/src/contrib area. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 22:01:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27471 for freebsd-current-outgoing; Wed, 21 Oct 1998 22:01:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27466 for ; Wed, 21 Oct 1998 22:01:13 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.58.227]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1C41 for ; Thu, 22 Oct 1998 07:00:43 +0200 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 22 Oct 1998 07:03:43 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Make World stop Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, whilst trying to make world last night I discovered that make failed on me with a ld -ll not known error. I am doing a make clean and make world now and will let ye all know how it went. Anyone else have experienced it? And while I am on subject, how can I do something like: time make world 2>&1 > make-world.211098.txt and add an extra command to still show the output on screen as well as port it to a file? Thanks, --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 22:09:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27830 for freebsd-current-outgoing; Wed, 21 Oct 1998 22:09:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27824 for ; Wed, 21 Oct 1998 22:09:14 -0700 (PDT) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id PAA20894; Thu, 22 Oct 1998 15:08:44 +1000 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma020873; Thu, 22 Oct 98 15:08:30 +1000 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id PAA27492 for ; Thu, 22 Oct 1998 15:08:30 +1000 From: "John Saunders" To: "FreeBSD current" Subject: Package upgrade check program Date: Thu, 22 Oct 1998 15:08:29 +1000 Message-ID: <001b01bdfd7a$021fd540$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With everybody hot into upgrading to 3.0, I thought I would throw this script in that I have been working on the last couple of days (bit at a time). This script suggests upgrades to installed packages. I'm continuing to work on a version that will do the upgrade for you (after prompting of course). Enjoy... #!/bin/sh # pkg_check: # # Scan the installed packages and suggest upgrades or alternative # packages to install. # # Change directory to the package database directory. if cd /var/db/pkg 2>/dev/null; then else echo "Cannot find package database directory /var/db/pkg" exit 1 fi # Scan through all the installed packages. for pkg in *; do # Try to determine the name of the package without the version # number postfix. Commented out line uses lazy checking. base=`echo $pkg | sed -e '1,$ s/\([a-zA-Z_]-\)[0-9].*$/\1/'` #base=`echo $pkg | sed -e '1,$ s/\([a-zA-Z_]\)-[0-9].*$/\1/'` # Get a list of ports matching the package base name. new=`grep "^$base" /usr/ports/INDEX | sed -e '1,$ s/|.*$//'` # Upgrade is yes when installed package doesn't match any in ports. upgrade="yes" # Alternatives is yes when one of the ports matches the installed # package, but multiple ports are available. alternatives="no" # Simple case no upgrade needed. if [ "$pkg" = "$new" ]; then upgrade="no" else # Scan the multiple available ports. for i in $new; do if [ "$pkg" = "$i" ]; then upgrade="no" else alternatives="yes" fi done fi # Dump the information. if [ "$upgrade" = "yes" ]; then echo "Upgrade package $pkg to one of..." for i in $new; do echo " $i" done elif [ "$alternatives" = "yes" ]; then echo "Alternatives for $pkg exist..." for i in $new; do if [ "$pkg" = "$i" ]; then echo " $i (installed)" else echo " $i" fi done fi done exit 0 -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 22:28:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29015 for freebsd-current-outgoing; Wed, 21 Oct 1998 22:28:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29010 for ; Wed, 21 Oct 1998 22:28:51 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id WAA25823; Wed, 21 Oct 1998 22:28:10 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <362EC26A.F5B171C8@gorean.org> Date: Wed, 21 Oct 1998 22:28:10 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert CC: John Polstra , current@FreeBSD.ORG Subject: Towards a more contrib'ified system (Was: cvsup and file permissions) References: <199810220250.TAA15310@usr01.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > > Regardless, it would be nice to have a way to tell cvsup not to sync > > > permissions. > > > > That feature's on my to-do list. I think I might actually get some > > time to work on CVSup again in the not-to-distant future. > > > > Meanwhile, try changing the umask as I suggested in my other mail. > > I'm pretty sure that will work. > > Oh, oh, let me vote for "implied vendor branch" again, then, > so that you can do local branches and checkouts and merges > relative to a steadily advancing "vendor branch" CVSup'ed from > "the vendor". > > It would be *too cool* if someone were to cause sendmail, ISC BIND, > and other CVS maintained projects from other vendors to show up in > FreeBSD as a constantly updated vendor branch. Actually the mini-hornet's nest that I stirred up today by suggesting that we upgrade cvs to take care of bugs reminded me that this is something that's been on my list for a long time. On one hand the fact that freebsd is a tightly integrated system is one of its strengths. On the other hand that integration limits flexibility and reduces the ease of upgrading non-project components. I think that elf-ifying is a major step forward on this line. The next two steps are things that can happen in tandem. Namely rooting as much gcc dependence out of the system as humanly possible, then calling in an exorcist for the rest. :) It would be nice to be able to build the system with whatever compiler the user wants to. Along with that, there should be an ongoing process of contrib'ifying all of the 3rd party sources with an eye towards carefully documenting the freebsd'isms that we've built into them. Following that process, it would be nice if we could look seriously into providing desirable freebsd-specific behaviour via some sort of wrapper process, and/or a mechanism like the ports system could be developed to archive the needed patches and combine them with the contribified sources. In this way the technically demanding user can more easily see and decide on said changes, and dependencies can be viewed more easily. This would greatly increase the flexibility of the system, and ease the introduction of new versions of third party sources because people who are interested in that particular item could more easily test the new versions. We should also keep in mind that some people might want to use different components for things like mail, etc. Making the make system more frobbable should be part of the goal. Both along the lines of making things more easily replacable (or easier to substitute entirely) and making things that the user doesn't need easier to not build. Please note that I DO NOT want to move to a linux-like system where the "latest and greatest" bits are thrown together with no thought towards integration. I envision -Current as close to or on the bleeding edge as people want to keep it and -Stable a step or two back, with tried and true bits filtering down as they do now. Our integration is a major part of our strength. Finally a major strength of this kind of system is that it more easily takes advantage of the cross-platform solutions (and other expertise) alreadly in place on the development teams of the third party apps we already use. I don't think I need to elaborate on this point. I hope that this suggestion is taken for what it is, and moreover I hope that the topics I'm proposing are seriously considered. And before anyone asks, yes, I am willing to help with the process. It would be nice if someone could come up with a document like the "How to make a port" part of the handbook for contrib'ifying as a place to start. Also, a pointer to references for the bmake system would be very helpful. Over time it's becoming more clear to me, but I'd rather not repeat mistakes of the past or waste people's time with foolish mistakes of my own. With an eye toward the future, Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 21 22:49:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29973 for freebsd-current-outgoing; Wed, 21 Oct 1998 22:49:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29963 for ; Wed, 21 Oct 1998 22:49:43 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id PAA04980; Thu, 22 Oct 1998 15:19:13 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA13026; Thu, 22 Oct 1998 15:19:12 +0930 Date: Thu, 22 Oct 1998 15:19:12 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: John Saunders Cc: FreeBSD current Subject: Re: Package upgrade check program In-Reply-To: <001b01bdfd7a$021fd540$6cb611cb@saruman.scitec.com.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998, John Saunders wrote: > With everybody hot into upgrading to 3.0, I thought I would > throw this script in that I have been working on the last > couple of days (bit at a time). This script suggests upgrades > to installed packages. I'm continuing to work on a version > that will do the upgrade for you (after prompting of course). Bruce Mah posted a similar script to one of the mailing lists a few months ago- search the mailing list archives for pkg_version. IMO it would be good to get something like this into the base system, or perhaps as a port (a la mergemaster). Perhaps you could get together and combine your good ideas and submit something to the ports team. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 00:57:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07838 for freebsd-current-outgoing; Thu, 22 Oct 1998 00:57:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Guard.PolyNet.Lviv.UA (Guard.PolyNet.Lviv.UA [194.44.138.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA07799 for ; Thu, 22 Oct 1998 00:57:35 -0700 (PDT) (envelope-from pam@polynet.lviv.ua) From: pam@polynet.lviv.ua Received: (qmail 22376 invoked by alias); 22 Oct 1998 07:56:52 -0000 Message-ID: <19981022075652.22375.qmail@Guard.PolyNet.Lviv.UA> Received: (qmail 22361 invoked from network); 22 Oct 1998 07:56:52 -0000 Received: from postoffice.polynet.lviv.ua (HELO NETADMIN.LP.LVIV.UA) (194.44.138.1) by guard.polynet.lviv.ua with SMTP; 22 Oct 1998 07:56:52 -0000 Received: from NETADMIN/SpoolDir by NETADMIN.LP.LVIV.UA (Mercury 1.43); 22 Oct 98 10:56:52 +0200 Received: from SpoolDir by NETADMIN (Mercury 1.43); 22 Oct 98 10:56:38 +0200 Organization: St. Univ. "Lvivska Polytechnica" To: Archie Cobbs Date: Thu, 22 Oct 1998 10:56:33 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) Reply-to: pam@polynet.lviv.ua CC: dwhite@resnet.uoregon.edu (Doug White), current@FreeBSD.ORG In-reply-to: <199810212102.OAA28227@bubba.whistle.com> References: from Doug White at "Oct 21, 98 09:30:59 am" X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21 Oct 98, at 14:02, Archie Cobbs wrote: > Doug White writes: > > > I want to generate FreeBSD-current system with MD5 crypted (hashed) > > > passwords, by default. it generates DES libcrypt libraries. Which > > > build flag changes that behaviour? > > > > Don't grab the src-secure dist, I want to have option to build libdescrypt (one my system is DES- enabled, and as far as I know no DES->MD5 migration is possible) I know that libdescrypt can verify MD5 passwords but stores new one in DES. Why libscrypt can't do the opposite?! >or (I think) it's the NOSECURE flag. I've put NOSECURE into /etc/make.conf without result. > Or, just change the /usr/lib/libcrypt* symlinks to point to > libscrypt instead of libdescrypt. But, first I need to have libscrypt.* build during world process, do I? ;-> > It seems like "I want libdes available" and "I want passwords > encrypted with DES instead of MD5" are completely independent > variables... Can't these two not be forcibly linked together in > the install process? Totaly agree! Please add my wote > -Archie > > __________________________________________________________________________ > _ Archie Cobbs * Whistle Communications, Inc. * > http://www.whistle.com > Adrian Pavlykevych System Administrator | State University "Lvivska Polytechnica" Campus Computer Network | 12, St. Bandery str, | Lviv, 290646 tel/fax:+380 (322) 742041 | Ukraine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 01:16:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09186 for freebsd-current-outgoing; Thu, 22 Oct 1998 01:16:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09174 for ; Thu, 22 Oct 1998 01:16:07 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA22543 for ; Thu, 22 Oct 1998 17:45:34 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id RAA28130; Thu, 22 Oct 1998 17:45:21 +0930 (CST) Message-ID: <19981022174520.V1219@freebie.lemis.com> Date: Thu, 22 Oct 1998 17:45:20 +0930 From: Greg Lehey To: FreeBSD current users Subject: sendmail dying with SIGSEGV? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since today, I've had repeated cases of the sendmail daemon dying with a SIGSEGV. In each case, it's a child process: the parent daemon continues to run. This is a 3.0-RELEASE kernel compiled 5 days ago. I tried recompiling sendmail with debug symbols, but I can't find any core dumps. Does it not leave one under these circumstances? Can I change its mind? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 01:33:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10371 for freebsd-current-outgoing; Thu, 22 Oct 1998 01:33:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.training.iafrica.com (axl.training.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10361 for ; Thu, 22 Oct 1998 01:32:59 -0700 (PDT) (envelope-from sheldonh@axl.training.iafrica.com) Received: from sheldonh (helo=iafrica.com) by axl.training.iafrica.com with local-esmtp (Exim 2.05 #1) id 0zWG9r-00058L-00; Thu, 22 Oct 1998 10:31:47 +0200 From: Sheldon Hearn To: "John Saunders" cc: "FreeBSD current" Subject: Re: Package upgrade check program In-reply-to: Your message of "Thu, 22 Oct 1998 15:08:29 +1000." <001b01bdfd7a$021fd540$6cb611cb@saruman.scitec.com.au> Date: Thu, 22 Oct 1998 10:31:46 +0200 Message-ID: <19736.909045106@iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998 15:08:29 +1000, "John Saunders" wrote: > # Get a list of ports matching the package base name. > new=`grep "^$base" /usr/ports/INDEX | sed -e '1,$ s/|.*$//'` I did something like this myself and hit the same problem you have -- the INDEX file isn't regenerated too frequently. If you want your script to work "in the heat of the moment", you should look at ports/Makefile, particularly the ``index'' target. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 01:34:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10558 for freebsd-current-outgoing; Thu, 22 Oct 1998 01:34:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10550 for ; Thu, 22 Oct 1998 01:34:06 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id BAA13428; Thu, 22 Oct 1998 01:33:09 -0700 (PDT) (envelope-from obrien) Message-ID: <19981022013309.A12667@nuxi.com> Date: Thu, 22 Oct 1998 01:33:09 -0700 From: "David O'Brien" To: Warner Losh , current@FreeBSD.ORG Subject: Re: file 3.26 from christos Reply-To: obrien@NUXI.com References: <199810220457.WAA09077@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810220457.WAA09077@harmony.village.org>; from Warner Losh on Wed, Oct 21, 1998 at 10:57:14PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'd like to update our file from its current rev to file 3.26 that Since it is a small program, why not just leave it where it is and bring in diffs (attribued to christos/NetBSD). -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 02:16:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13320 for freebsd-current-outgoing; Thu, 22 Oct 1998 02:16:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13315 for ; Thu, 22 Oct 1998 02:16:03 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id CAA13917; Thu, 22 Oct 1998 02:14:48 -0700 (PDT) (envelope-from obrien) Message-ID: <19981022021448.A13887@nuxi.com> Date: Thu, 22 Oct 1998 02:14:48 -0700 From: "David O'Brien" To: slpalmer@email.com Cc: current@FreeBSD.ORG Subject: Re: Newbie (to development) would like to help Reply-To: obrien@NUXI.com References: <9810211141364G.14328@webc02.globecomm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <9810211141364G.14328@webc02.globecomm.net>; from slpalmer@email.com on Wed, Oct 21, 1998 at 11:41:36AM -0400 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > RIVA TNT based video card (I'm running the VGA16 server until it's > supported). I had a friend that had one of these. I emailed David Schmenk to see if they had a server for us. He has a Linux server and offered me the patches/src so I could make a FreeBSD one. My friend returned the card, so I didn't go thru with getting the src and making a FreeBSD server. But you should contact him if you are interested. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 03:22:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17670 for freebsd-current-outgoing; Thu, 22 Oct 1998 03:22:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA17664 for ; Thu, 22 Oct 1998 03:21:58 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 21752 invoked by uid 1001); 22 Oct 1998 10:21:28 -0000 To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem References: From: Ville-Pertti Keinonen Date: 22 Oct 1998 13:19:51 +0300 In-Reply-To: Alfred Perlstein's message of "20 Oct 1998 23:10:32 +0300" Message-ID: <863e8guce0.fsf@not.oeno.com> Lines: 71 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > As a side note, has anyone thought of hybrid kernel+userland threads? > Basically a userland scheduler with kernel hooks for mutexes and > distributing signals. At startup or on the first pthread_create() the > pthreads library would sysctl out the number of processors in the > system and prefork kernel threads for each. The kernel threads would only > be active on SMP machines, otherwise there really is no point. Does > anyone have any papers/webpages about an algorithm like that? I'm not sure what you mean by kernel hooks for mutexes and signals, in most cases mutexes are the last thing you want the kernel to know about...but what you're suggesting mostly sounds like simply adding a kernel threads capability and primarily using user threads with code similar to the current system except that multiple kernel threads would be allocated for the user threads if it would allow for actual concurrency (SMP). This wouldn't really require a lot of changes in the thread code, but is, in my opinion, a bad idea. (A sort of similar approach is used by Mach cthreads, but it works better for various reasons that don't apply to FreeBSD) The problem I see with this picture (as well as the current one) is that a supposed advantage of userland threads, performance, often is not applicable. How can performance be measured? It isn't trivial. One quite significant factor is switching between threads. Not just running the scheduling algorithm but the changes in context. In terms of switching performance, well-implemented kernel threads can match or outperform any userland threads that need to perform any system calls while performing the switch. On the other hand, a userland thread implementation that doesn't perform system calls can be faster by several orders of magnitude, but either is broken or requires movement of some of the "system" behavior to a user-level. FreeBSD currently has the slowest alternative, userland threads that perform system calls while doing just about anything... I think it's at *least* four for a thread switch. In the absence of the ability to tell the thread system "I-don't-give-a-damn-about-signals", "gimme-crude-scheduling" etc., user-level threads are actually killing performance and adding complexity. Even if signals could be ignored, the overhead of polling the kernel for I/O is still difficult to avoid if there are threads waiting for something other than other threads and cpu cycles. There are, of course, other reasons for considering kernel threads undesirable, such as the fact that the kernel might need to keep much of the thread info in wired-down memory, as well as the fact that there is a restricted set of scheduling semantics available. For reasonable user-level thread performance, some kind of addition to the kernel API would be needed that could perform all of the kernel actions required for a thread switch (and, if possible, other thread ops) in one system call (any more and performance-wise, you'd very likely be better off using kernel threads). This is still not the same thing as kernel threads, since the controlling semantics and thread context structures could still be at a user level. In a hybrid system where the kernel "knows" about user threads (not actively, but with the ability to "react" to them), something like this would be a rather natural part of the hybrid API. But it could be done without kernel threads, as well. The belief that the current thread system is fine as long as you don't want to take advantage of SMP requires a rather unconservative definition of "fine". In many respects, plain kernel threads would be better than the current system (simpler, faster), unless the primary concern is saving kernel memory. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 03:41:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18674 for freebsd-current-outgoing; Thu, 22 Oct 1998 03:41:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18669 for ; Thu, 22 Oct 1998 03:41:22 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA14937 for current@freebsd.org; Thu, 22 Oct 1998 20:40:51 +1000 Date: Thu, 22 Oct 1998 20:40:51 +1000 From: Bruce Evans Message-Id: <199810221040.UAA14937@godzilla.zeta.org.au> To: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/isa aic6360.c alog.c asc.c cy.c fd.c if_ar.c if_cs.c if_cx.c if_ed.c if_eg.c if_el.c if_ep.c if_ex.c if_fe.c if_ie.c if_le.c if_lnc.c if_sr.c if_wl.c if_ze.c if_zp.c isa.c isa_device.h labpc.c loran.c lpt.c mcd.c mse.c ncr5380.c ... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This change is a bit dangerous because it affects so many drivers (all isa ones). It breaks the sound drivers at compile time. This may be fixed in the next version of soundcard.c. Runtime problems might be reported in boot messages like "foo0: irq with no handler". Bruce >bde 1998/10/21 22:58:46 PDT > > Modified files: > sys/i386/isa aic6360.c alog.c asc.c cy.c fd.c if_ar.c > if_cs.c if_cx.c if_ed.c if_eg.c if_el.c > if_ep.c if_ex.c if_fe.c if_ie.c if_le.c > if_lnc.c if_sr.c if_wl.c if_ze.c if_zp.c > isa.c isa_device.h labpc.c loran.c lpt.c > mcd.c mse.c ncr5380.c npx.c pcf.c pnp.c > ppc.c psm.c rc.c seagate.c sio.c spigot.c > stallion.c syscons.c tw.c ultra14f.c wd.c > wd7000.c wdreg.h wt.c > sys/i386/isa/bs bsif.c > sys/i386/isa/pcvt pcvt_drv.c pcvt_hdr.h > sys/i386/isa/snd sound.c sound.h > sys/i386/isa/sound sound_calls.h soundcard.c > sys/pc98/pc98 fd.c if_ed.c if_fe.c lpt.c mse.c npx.c > pc98.c sio.c syscons.c wd.c > Log: > Initialize isa_devtab entries for interrupt handlers in individual > device drivers, not in ioconf.c. Use a different hack in isa_device.h > so that a new config(8) is not required yet. > > pc98 parts approved by: kato > > Revision Changes Path > 1.42 +4 -2 src/sys/i386/isa/aic6360.c > 1.7 +3 -1 src/sys/i386/isa/alog.c > 1.32 +5 -2 src/sys/i386/isa/asc.c > 1.72 +3 -1 src/sys/i386/isa/cy.c > 1.124 +4 -2 src/sys/i386/isa/fd.c > 1.23 +4 -2 src/sys/i386/isa/if_ar.c > 1.6 +4 -2 src/sys/i386/isa/if_cs.c > 1.25 +4 -1 src/sys/i386/isa/if_cx.c > 1.146 +4 -2 src/sys/i386/isa/if_ed.c > 1.29 +4 -2 src/sys/i386/isa/if_eg.c > 1.38 +4 -2 src/sys/i386/isa/if_el.c > 1.77 +4 -2 src/sys/i386/isa/if_ep.c > 1.13 +5 -2 src/sys/i386/isa/if_ex.c > 1.43 +5 -2 src/sys/i386/isa/if_fe.c > 1.57 +5 -2 src/sys/i386/isa/if_ie.c > 1.48 +4 -2 src/sys/i386/isa/if_le.c > 1.47 +6 -3 src/sys/i386/isa/if_lnc.c > 1.16 +3 -2 src/sys/i386/isa/if_sr.c > 1.16 +5 -3 src/sys/i386/isa/if_wl.c > 1.55 +5 -2 src/sys/i386/isa/if_ze.c > 1.49 +5 -2 src/sys/i386/isa/if_zp.c > 1.116 +6 -3 src/sys/i386/isa/isa.c > 1.56 +65 -69 src/sys/i386/isa/isa_device.h > 1.28 +3 -1 src/sys/i386/isa/labpc.c > 1.9 +5 -2 src/sys/i386/isa/loran.c > 1.71 +4 -2 src/sys/i386/isa/lpt.c > 1.101 +4 -2 src/sys/i386/isa/mcd.c > 1.39 +4 -2 src/sys/i386/isa/mse.c > 1.21 +4 -1 src/sys/i386/isa/ncr5380.c > 1.62 +4 -1 src/sys/i386/isa/npx.c > 1.2 +4 -2 src/sys/i386/isa/pcf.c > 1.7 +2 -2 src/sys/i386/isa/pnp.c > 1.10 +5 -2 src/sys/i386/isa/ppc.c > 1.56 +5 -2 src/sys/i386/isa/psm.c > 1.40 +5 -1 src/sys/i386/isa/rc.c > 1.32 +5 -2 src/sys/i386/isa/seagate.c > 1.216 +4 -2 src/sys/i386/isa/sio.c > 1.35 +4 -1 src/sys/i386/isa/spigot.c > 1.23 +5 -2 src/sys/i386/isa/stallion.c > 1.285 +4 -2 src/sys/i386/isa/syscons.c > 1.28 +3 -1 src/sys/i386/isa/tw.c > 1.62 +6 -2 src/sys/i386/isa/ultra14f.c > 1.178 +3 -1 src/sys/i386/isa/wd.c > 1.21 +3 -1 src/sys/i386/isa/wd7000.c > 1.23 +3 -1 src/sys/i386/isa/wdreg.h > 1.46 +4 -2 src/sys/i386/isa/wt.c > 1.7 +3 -1 src/sys/i386/isa/bs/bsif.c > 1.42 +2 -0 src/sys/i386/isa/pcvt/pcvt_drv.c > 1.28 +1 -0 src/sys/i386/isa/pcvt/pcvt_hdr.h > 1.19 +2 -0 src/sys/i386/isa/snd/sound.c > 1.9 +2 -0 src/sys/i386/isa/snd/sound.h > 1.24 +6 -1 src/sys/i386/isa/sound/sound_calls.h > 1.71 +23 -2 src/sys/i386/isa/sound/soundcard.c > 1.42 +4 -2 src/sys/pc98/pc98/fd.c > 1.55 +4 -2 src/sys/pc98/pc98/if_ed.c > 1.35 +5 -2 src/sys/pc98/pc98/if_fe.c > 1.23 +4 -2 src/sys/pc98/pc98/lpt.c > 1.18 +4 -2 src/sys/pc98/pc98/mse.c > 1.39 +4 -1 src/sys/pc98/pc98/npx.c > 1.54 +6 -3 src/sys/pc98/pc98/pc98.c > 1.68 +9 -7 src/sys/pc98/pc98/sio.c > 1.102 +4 -2 src/sys/pc98/pc98/syscons.c > 1.65 +3 -1 src/sys/pc98/pc98/wd.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 04:18:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22102 for freebsd-current-outgoing; Thu, 22 Oct 1998 04:18:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22079 for ; Thu, 22 Oct 1998 04:17:59 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem13.masternet.it [194.184.65.23]) by www.giovannelli.it (8.8.8/8.8.5) with SMTP id NAA00509 for ; Thu, 22 Oct 1998 13:12:10 +0200 (MET DST) Message-Id: <199810221112.NAA00509@www.giovannelli.it> From: "Gianmarco Giovannelli" To: current@FreeBSD.ORG Date: Thu, 22 Oct 1998 13:20:26 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: make installworld fails... Reply-to: gmarco@giovannelli.it X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Installing legacy libraries -------------------------------------------------------------- cd /usr/src/lib; /usr/obj/elf/usr/src/tmp/usr/bin/make -B -DNOMAN -DNOINFO install ===> csu/i386 install -C -c -o root -g wheel -m 444 crt0.o c++rt0.o gcrt0.o scrt0.o sgcrt0.o /usr/lib/aout install: crt0.o: No such file or directory *** Error code 71 Stop. *** Error code 1 the thing is not good if you have to make some make "reinstall" from the "clients" even if the server succeded in making world ... But it is not able to finish a "make installworld" itself... Dunno... Thanks again for attention... Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 04:52:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24204 for freebsd-current-outgoing; Thu, 22 Oct 1998 04:52:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup6.gaffaneys.com [208.155.161.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24186 for ; Thu, 22 Oct 1998 04:52:23 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id LAA01296; Thu, 22 Oct 1998 11:52:49 GMT (envelope-from zach) Message-ID: <19981022065249.A1166@znh.org> Date: Thu, 22 Oct 1998 06:52:49 -0500 From: Zach Heilig To: Jeroen Ruigrok/Asmodai , FreeBSD Current Subject: Re: Make World stop References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Thu, Oct 22, 1998 at 07:03:43AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 22, 1998 at 07:03:43AM +0200, Jeroen Ruigrok/Asmodai wrote: > whilst trying to make world last night I discovered that make failed on me with > a ld -ll not known error. ... > Anyone else have experienced it? No, sorry. > And while I am on subject, how can I do something like: > time make world 2>&1 > make-world.211098.txt > and add an extra command to still show the output on screen as well as port it > to a file? I simply do something similar to this: # nohup time make world > foo.log 2>&1 & # exit $ tail -f foo.log you could also do this: # (time make world 2>&1) | tee foo.log -- Zach Heilig If it looks like a duck, and quacks like a duck, we have to at least consider the possibility that we have a small aquatic bird of the family Anatidæ on our hands (Douglas Adams -- Dirk Gently's Holistic Detective Agency) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 05:41:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26971 for freebsd-current-outgoing; Thu, 22 Oct 1998 05:41:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup9.gaffaneys.com [208.155.161.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26964 for ; Thu, 22 Oct 1998 05:41:54 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id MAA01853; Thu, 22 Oct 1998 12:42:23 GMT (envelope-from zach) Message-ID: <19981022074223.A1730@znh.org> Date: Thu, 22 Oct 1998 07:42:23 -0500 From: Zach Heilig To: Zach Heilig , FreeBSD-current@FreeBSD.ORG Subject: Re: cdda2wav == panic ... (cases where it does NOT panic) References: <19981021224539.A10190@znh.org> <19981021231850.B434@znh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: <19981021231850.B434@znh.org>; from Zach Heilig on Wed, Oct 21, 1998 at 11:18:50PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cdda2wav does not panic this system under these conditions: 1) with the -N option (does not write data to disk) 2) with the -n 1 option (reads/writes a single sector at a time, default is 55) 3) when 'audio.wav' is a fifo, but it fails in a different (non-panic'y) way: ... No overlap sampling active samplefiles size total will be 415316600 bytes. 10 tracks recording seconds stereo with 16 bits @ Hz ->'audio'... cannot set realtime scheduling policy: Function not implemented cannot set realtime scheduling policy: Function not implemented write(audio, 0x3004800C, 129360) = 8192 Probably disk space exhausted: Undefined error: 0 (with a 'cat audio.wav > foo.wav' also running) This is a kernel from ~01:50 GMT Thursday Oct 22. -- Zach Heilig If it looks like a duck, and quacks like a duck, we have to at least consider the possibility that we have a small aquatic bird of the family Anatidæ on our hands (Douglas Adams -- Dirk Gently's Holistic Detective Agency) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 06:07:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28787 for freebsd-current-outgoing; Thu, 22 Oct 1998 06:07:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28782 for ; Thu, 22 Oct 1998 06:07:32 -0700 (PDT) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id JAA00198; Thu, 22 Oct 1998 09:07:02 -0400 (EDT) To: freebsd-current@FreeBSD.ORG Subject: Netscape 4.5 & ld-linux.so.2? X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 22 Oct 1998 09:07:02 -0400 Message-ID: Lines: 21 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I make netscape 4.5 from the ports collection (or just downloading the it from netscape's web site), I get the following when I try to run: % netscape ELF interpreter /compat/linux/lib/ld-linux.so.2 not found zsh: abort netscape /compat/linux/lib contains a ld-linux.so.1, and a ld-linux.so.1.7.14, but no .2 version. Where does the missing version come from? This is on a -current from a few days ago. +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 06:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29489 for freebsd-current-outgoing; Thu, 22 Oct 1998 06:17:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29478 for ; Thu, 22 Oct 1998 06:17:23 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id IAA00553; Thu, 22 Oct 1998 08:14:23 -0500 (CDT) Message-Id: <199810221314.IAA00553@ns.tar.com> From: "Richard Seaman, Jr." To: "Ville-Pertti Keinonen" Cc: "current@freebsd.org" Date: Thu, 22 Oct 98 08:14:23 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Another Serious libc_r problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22 Oct 1998 13:19:51 +0300, Ville-Pertti Keinonen wrote: >How can performance be measured? It isn't trivial. One quite >significant factor is switching between threads. Not just running the >scheduling algorithm but the changes in context. > >In terms of switching performance, well-implemented kernel threads can >match or outperform any userland threads that need to perform any >system calls while performing the switch. On the other hand, a >userland thread implementation that doesn't perform system calls can >be faster by several orders of magnitude, but either is broken or >requires movement of some of the "system" behavior to a user-level. > >FreeBSD currently has the slowest alternative, userland threads that >perform system calls while doing just about anything... I think it's >at *least* four for a thread switch. In the absence of the ability to >tell the thread system "I-don't-give-a-damn-about-signals", >"gimme-crude-scheduling" etc., user-level threads are actually killing >performance and adding complexity. > >Even if signals could be ignored, the overhead of polling the kernel >for I/O is still difficult to avoid if there are threads waiting for >something other than other threads and cpu cycles. FWIW, John Dyson posted a "kernel threads" implementation a couple of months ago. It wasn't anything close to a full pthreads implementation though. For the heck of it, I wrote a small program that spawned several threads, which just yielded back and forth among them, and compiled it under both the kernel threads and FreeBSD user threads. The kernel threads were about 2.2 times faster (could do 2.2 times more yields per seconds) than the FreeBSD user threads. I never tried to profile the reason, but the system calls are it, I'm sure. And, I didn't have any open file descriptors, so my code bypassed the extra system call to select that the user thread scheduler would do in that case. As to complexity, I've compared the Linux kernel threads implementation to the FreeBSD user threads. The FreeBSD implementation is much more massive, much more complex, and implements far fewer features. Most of the extra complexity is in the code dealing with handling blocking i/o, and would disappear with kernel threads. >For reasonable user-level thread performance, some kind of addition to >the kernel API would be needed that could perform all of the kernel >actions required for a thread switch (and, if possible, other thread >ops) in one system call (any more and performance-wise, you'd very >likely be better off using kernel threads). Most likely, yes. >The belief that the current thread system is fine as long as you don't >want to take advantage of SMP requires a rather unconservative >definition of "fine". In many respects, plain kernel threads would be >better than the current system (simpler, faster), unless the primary >concern is saving kernel memory. I agree completely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 06:26:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00476 for freebsd-current-outgoing; Thu, 22 Oct 1998 06:26:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megadeth.rtci.com (megadeth.noc.rtci.com [216.27.37.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00466 for ; Thu, 22 Oct 1998 06:26:14 -0700 (PDT) (envelope-from dhopkins@rtci.com) Received: from rtci.com (oxygen.schizo.com [216.27.37.251]) by megadeth.rtci.com (8.8.8/8.8.8) with ESMTP id JAA26037; Thu, 22 Oct 1998 09:28:51 -0400 (EDT) (envelope-from dhopkins@rtci.com) Message-ID: <362F345E.90820D5C@rtci.com> Date: Thu, 22 Oct 1998 09:34:22 -0400 From: Damon Hopkins Organization: Research Triangle Consultants, Inc. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: current-digest V4 #298 References: <199810221152.EAA24211@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey I just use tee. puts it in the file and displays it. make world | tee /var/log/makeworld-10221998.log Damon Hopkins Research Triangle Consultants >Date: Thu, 22 Oct 1998 07:03:43 +0200 (CEST) >From: Jeroen Ruigrok/Asmodai >Subject: Make World stop > >Hi, > >whilst trying to make world last night I discovered that make failed on >me with >a ld -ll not known error. > >I am doing a make clean and make world now and will let ye all know how >it went. > >Anyone else have experienced it? > >And while I am on subject, how can I do something like: > >time make world 2>&1 > make-world.211098.txt > >and add an extra command to still show the output on screen as well as >port it >to a file? > >Thanks, > >- --- >Jeroen Ruigrok van der Werven/Asmodai >asmodai(at)wxs.nl >Junior Network/Security Specialist >FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 06:28:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00632 for freebsd-current-outgoing; Thu, 22 Oct 1998 06:28:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from misio.office.linkdesign.com (office-access.linkdesign.com [194.42.131.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00624 for ; Thu, 22 Oct 1998 06:28:37 -0700 (PDT) (envelope-from root@linkdesign.com) Received: from linkdesign.com (root@localhost [127.0.0.1]) by misio.office.linkdesign.com (8.8.8/8.8.8) with ESMTP id QAA07792; Thu, 22 Oct 1998 16:27:45 +0300 Message-Id: <199810221327.QAA07792@misio.office.linkdesign.com> Date: Thu, 22 Oct 1998 16:27:42 +0300 (EEST) From: Michael.Bielicki@linkdesign.com Reply-To: Michael.Bielicki@linkdesign.com Subject: Re: Netscape 4.5 & ld-linux.so.2? To: ckempf@enigami.com cc: freebsd-current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22 Oct, Cory Kempf shaped the electrons to say: Looks like you got a glibc-2 version of netscape. ld-linux.so.2 is the ldloader for glibc-2 cheers Michael > When I make netscape 4.5 from the ports collection (or just > downloading the it from netscape's web site), I get the following when > I try to run: > > % netscape > ELF interpreter /compat/linux/lib/ld-linux.so.2 not found > zsh: abort netscape > > /compat/linux/lib contains a ld-linux.so.1, and a ld-linux.so.1.7.14, > but no .2 version. Where does the missing version come from? > > This is on a -current from a few days ago. > > +C > > -- > Thinking of purchasing RAM from the Chip Merchant? > Please read this first: > > Cory Kempf Macintosh / Unix Consulting & Software Development > ckempf@enigami.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ---------------------------------------------------- Reach me by ICQ. My ICQ# is 15359693 or, Work: +357 2 817 134 Fax: +357 2 817 135 Home: +357 2 347 202 Michael Bielicki Buisnetco Telecommunications Ltd. ---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 07:27:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06724 for freebsd-current-outgoing; Thu, 22 Oct 1998 07:27:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06712 for ; Thu, 22 Oct 1998 07:27:35 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id QAA13867; Thu, 22 Oct 1998 16:26:49 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810221426.QAA13867@gratis.grondar.za> To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: Netscape 4.5 & ld-linux.so.2? In-Reply-To: Your message of " 22 Oct 1998 09:07:02 -0400." References: Date: Thu, 22 Oct 1998 16:26:48 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cory Kempf wrote: > When I make netscape 4.5 from the ports collection (or just > downloading the it from netscape's web site), I get the following when > I try to run: > > % netscape > ELF interpreter /compat/linux/lib/ld-linux.so.2 not found > zsh: abort netscape > > /compat/linux/lib contains a ld-linux.so.1, and a ld-linux.so.1.7.14, > but no .2 version. Where does the missing version come from? I have another Linux program (Physica from triumf.ca) that also wants ld-linux.so.2, and this one also wants libc.so.6 and libm.so.6. The author reckons he did the compile on a Redhat box, but all the Redhat mirrors I can find had ld-linux.so.1 and lib[cm].so.5.N.M. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 07:58:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09226 for freebsd-current-outgoing; Thu, 22 Oct 1998 07:58:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09221 for ; Thu, 22 Oct 1998 07:58:47 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id RAA22562; Thu, 22 Oct 1998 17:02:27 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 22 Oct 1998 17:02:27 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mark Murray cc: Cory Kempf , freebsd-current@FreeBSD.ORG Subject: Re: Netscape 4.5 & ld-linux.so.2? In-Reply-To: <199810221426.QAA13867@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998, Mark Murray wrote: > Cory Kempf wrote: > > When I make netscape 4.5 from the ports collection (or just > > downloading the it from netscape's web site), I get the following when > > I try to run: > > > > % netscape > > ELF interpreter /compat/linux/lib/ld-linux.so.2 not found > > zsh: abort netscape > > > > /compat/linux/lib contains a ld-linux.so.1, and a ld-linux.so.1.7.14, > > but no .2 version. Where does the missing version come from? > > I have another Linux program (Physica from triumf.ca) that also > wants ld-linux.so.2, and this one also wants libc.so.6 and libm.so.6. > The author reckons he did the compile on a Redhat box, but all the > Redhat mirrors I can find had ld-linux.so.1 and lib[cm].so.5.N.M. These are also the requirements for Oracle8 for Linux... It would definitely help to freshen up our linux_lib package... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 08:05:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09697 for freebsd-current-outgoing; Thu, 22 Oct 1998 08:05:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09683 for ; Thu, 22 Oct 1998 08:05:50 -0700 (PDT) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id LAA17429; Thu, 22 Oct 1998 11:05:20 -0400 (EDT) To: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: Netscape 4.5 & ld-linux.so.2? References: X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 22 Oct 1998 11:05:20 -0400 In-Reply-To: Andrzej Bialecki's message of "Thu, 22 Oct 1998 17:02:27 +0200 (CEST)" Message-ID: Lines: 29 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki writes: >On Thu, 22 Oct 1998, Mark Murray wrote: >> Cory Kempf wrote: >> > % netscape >> > ELF interpreter /compat/linux/lib/ld-linux.so.2 not found >> > zsh: abort netscape >> > >> I have another Linux program (Physica from triumf.ca) that also >> wants ld-linux.so.2, and this one also wants libc.so.6 and libm.so.6. >> The author reckons he did the compile on a Redhat box, but all the >> Redhat mirrors I can find had ld-linux.so.1 and lib[cm].so.5.N.M. > >These are also the requirements for Oracle8 for Linux... It would >definitely help to freshen up our linux_lib package... So, what needs to happen? Simply locate and install the libraries from a linux system? Once the correct libraries are located, how can they be put into the distribution? I gather I am not the only person with the problem... +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 08:09:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09987 for freebsd-current-outgoing; Thu, 22 Oct 1998 08:09:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www4.iname.net (www4.iname.net [165.251.12.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09978 for ; Thu, 22 Oct 1998 08:09:51 -0700 (PDT) (envelope-from slpalmer@email.com) From: slpalmer@email.com Received: by www4.iname.net (8.9.1/8.8.0) id KAA10044 MIME-Version: 1.0 Message-Id: <9810221059415K.14741@www4.iname.net> Date: Thu, 22 Oct 1998 10:59:41 -0400 (EDT) Content-Type: Text/Plain Content-Transfer-Encoding: 7bit To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Riva TNT / XF86 / FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've gotten Dave Schmenk's patches, and though they applied cleanly, they did not build on my FreeBSD-current box... I've sent Dave Schmenk e-mail, hoping to fix this. I will make the binary available once I've got one ;-) slpalmer ---- On Oct 22 "David O'Brien" wrote: > > RIVA TNT based video card (I'm running the VGA16 server until it's > > supported). > > I had a friend that had one of these. > > I emailed David Schmenk to see if they had a server > for us. He has a Linux server and offered me the patches/src so I could > make a FreeBSD one. > > My friend returned the card, so I didn't go thru with getting the src and > making a FreeBSD server. But you should contact him if you are > interested. > > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) > ----------------------------------------------- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 08:51:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13141 for freebsd-current-outgoing; Thu, 22 Oct 1998 08:51:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13133 for ; Thu, 22 Oct 1998 08:51:04 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id IAA18935; Thu, 22 Oct 1998 08:50:17 -0700 (PDT) (envelope-from jdp) Message-Id: <199810221550.IAA18935@austin.polstra.com> To: grog@lemis.com Subject: Re: inetd still dying (was: cvs commit: src/sys/cam/scsi scsi_da.c src/sys/i386/i386 busdma_machdep.c vm_machdep.c src/sys/i386/ibcs2 imgact_coff.c src/sys/i386/include param.h src/sys/i386/isa isa.c wd.c src/sys/kern imgact_elf.c sys_pipe.c sysv_shm.c vfs_b In-Reply-To: <19981022100727.C1219@freebie.lemis.com> References: <199810131154.EAA12696@implode.root.com> <19981014071356.S21983@freebie.lemis.com> <19981022100727.C1219@freebie.lemis.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 22 Oct 1998 08:50:17 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981022100727.C1219@freebie.lemis.com>, Greg Lehey wrote: > It happened again. I put inetd into gdb, but I couldn't find a way to > resolve library addresses. It works if I start a program, but > apparently not if I attach to it. Can anybody give me some pointers > (like how to find the load address of a library)? This is a real > -current but still using a.out binaries. Hmm, you're right -- it works great for ELF but not for a.out. So you'll have to fake it. You can find out where the shared libraries are loaded by using ldd: vashon# ldd /usr/sbin/inetd /usr/sbin/inetd: -lutil.2 => /usr/lib/aout/libutil.so.2.2 (0x2001c000) -lc.3 => /usr/lib/aout/libc.so.3.1 (0x20022000) Then use add-symbol-file specifying the address in the ldd output + 0x20 (the size of the a.out header, *gag*). I don't think the +0x20 should be necessary, but it is. For serious debugging, ELF is way better. For one thing, the core dumps contain all of the writable regions of memory. That means you get the data segments of all the shared libraries, so you can look at the variables in them. If you want to debug this on an a.out system, your best bet might be to install a static version of inetd. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 08:55:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13824 for freebsd-current-outgoing; Thu, 22 Oct 1998 08:55:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13819 for ; Thu, 22 Oct 1998 08:55:38 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id IAA15880; Thu, 22 Oct 1998 08:55:06 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 22 Oct 1998 08:55:05 -0700 (PDT) From: Doug White To: "Jeffrey J. Mountin" cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 missing some docs? In-Reply-To: <3.0.3.32.19981021141506.00f0b3e4@207.227.119.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998, Jeffrey J. Mountin wrote: > >3.0 has been working beautifully on my prototype box. > > I'm pleased and plan to move my upgrades schedules up. > > Interestingly before going to an ELF kernel my system had: > > Oct 18 07:58:26 local /kernel: stray irq 7 > Oct 18 07:59:20 local last message repeated 3 times > Oct 18 07:59:20 local /kernel: too many stray irq 7's; not > logging any more > > Forget the why and how of this ugly problem, which it doesn't seem to be > (this time at least). Strangly it would happen after a reboot, but nothing > was going on. Only running the basic daemons, no sendmail, no crons, no > network activity, and I never logged in (have to sleep now and again). > Immediately after changing the kernel to ELF, poof! Gone. Only 3.0 > release did this, never ever have I seen this on this box and it's been > around since 2.1.5 with same hardware, barring a CPU fan and a change from > a P133 -> P166 laying around. I'd have to install 3.0 on my -STABLE workstation to test this. It may be that the message was hidden behind bootverbose since it doesn't mean anything and there's nothing you can do about it. My workstation spits out an IRQ 7 each time the serial port is closed. Wacky, eh? I have a ASUS T2P4 board. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 08:58:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14276 for freebsd-current-outgoing; Thu, 22 Oct 1998 08:58:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14256 for ; Thu, 22 Oct 1998 08:58:21 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id IAA19015; Thu, 22 Oct 1998 08:55:51 -0700 (PDT) (envelope-from jdp) Message-Id: <199810221555.IAA19015@austin.polstra.com> To: obrien@NUXI.com Subject: Re: file 3.26 from christos In-Reply-To: <19981022013309.A12667@nuxi.com> References: <199810220457.WAA09077@harmony.village.org> <19981022013309.A12667@nuxi.com> Organization: Polstra & Co., Seattle, WA Cc: Warner Losh , current@FreeBSD.ORG Date: Thu, 22 Oct 1998 08:55:50 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981022013309.A12667@nuxi.com>, David O'Brien wrote: > > I'd like to update our file from its current rev to file 3.26 that > > Since it is a small program, why not just leave it where it is and bring > in diffs (attribued to christos/NetBSD). The program is medium-small, but it has about 110 files in Magdir that go toward building the "magic" file. Using contrib might make a lot of sense. One thing, though -- we have a few local changes. Whoever brings in the new version should be careful not to lose them. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 09:00:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14506 for freebsd-current-outgoing; Thu, 22 Oct 1998 09:00:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14488 for ; Thu, 22 Oct 1998 09:00:14 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id IAA19074; Thu, 22 Oct 1998 08:59:07 -0700 (PDT) (envelope-from jdp) Message-Id: <199810221559.IAA19074@austin.polstra.com> To: grog@lemis.com Subject: Re: sendmail dying with SIGSEGV? In-Reply-To: <19981022174520.V1219@freebie.lemis.com> References: <19981022174520.V1219@freebie.lemis.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 22 Oct 1998 08:59:07 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981022174520.V1219@freebie.lemis.com>, Greg Lehey wrote: > Since today, I've had repeated cases of the sendmail daemon dying with > a SIGSEGV. In each case, it's a child process: the parent daemon > continues to run. This is a 3.0-RELEASE kernel compiled 5 days ago. > I tried recompiling sendmail with debug symbols, but I can't find any > core dumps. Does it not leave one under these circumstances? Can I > change its mind? You can set the sysctl variable "kern.sugid_coredump" to 1. That's kind of a blunt instrument, though, since its effect is systemwide. You can also change "kern.corefile" to make it put the core dumps into a fixed directory, no matter where the process was executing when it died. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 09:04:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14758 for freebsd-current-outgoing; Thu, 22 Oct 1998 09:04:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14753 for ; Thu, 22 Oct 1998 09:04:43 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA17225; Thu, 22 Oct 1998 09:03:56 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 22 Oct 1998 09:03:55 -0700 (PDT) From: Doug White To: pam@polynet.lviv.ua cc: Archie Cobbs , current@FreeBSD.ORG Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) In-Reply-To: <19981022075652.22374.qmail@Guard.PolyNet.Lviv.UA> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998 pam@polynet.lviv.ua wrote: > I want to have option to build libdescrypt (one my system is DES- > enabled, and as far as I know no DES->MD5 migration is possible) > I know that libdescrypt can verify MD5 passwords but stores new one > in DES. Why libscrypt can't do the opposite?! Because libscrypt is DES-free for international distribution. Unfortunately FreeBSD is made in the US and we have perverse crypto export laws. Having a separate DES library lows us to split it out into it's own module/distribution that can be export-controlled. If you want new passwords stored in MD5 and still decrypt DES, you have to hack passwd to pass the MD5 magic '$1$' to the crypt() routine so it returns an MD5 key. It's a one line change; I'm highly tempted to make it a compile-time #define in the base code. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 09:09:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15032 for freebsd-current-outgoing; Thu, 22 Oct 1998 09:09:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15024 for ; Thu, 22 Oct 1998 09:09:11 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA18487; Thu, 22 Oct 1998 09:08:40 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 22 Oct 1998 09:08:39 -0700 (PDT) From: Doug White To: steven cc: current@FreeBSD.ORG Subject: Re: 3.0-Current/3Com 509B ether problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998, steven wrote: > but i have a problem that no posts seems to clearly identify or > fix. > > i've got a 3com 509b ISA ethernet card. > It worked fine with 2.2.6 2.2.7 and an early Sept 3.0 install. > I went to the last BETA and the bootup stopped seeing the card. > I went 3.0-current and same thing. > > dmesg shows.. > > fd0: 1.44MB 3.5in > ie0: unknown board_id: f000 > ie0 not found at 0x300 > ep0 not found at 0x300 > npx0 on motherboard > > before 3.0 it never detected anything on ie0 and ep0 was always what > i used for the card. > > I swapped the card into my Windows box and the card does appear to > work. Ideas? Um, disable the ethernet card drivers you're not using? Some ether card probes are destructive. Ican't say I've noticed the same thing on my systems with ie and ep both turned on, it sees no ie0 but the ep0 at IRQ 10 port 0x300 is detected properly. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 09:21:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16375 for freebsd-current-outgoing; Thu, 22 Oct 1998 09:21:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16370 for ; Thu, 22 Oct 1998 09:21:48 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id JAA04277; Thu, 22 Oct 1998 09:20:38 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma004275; Thu Oct 22 09:20:14 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id JAA01628; Thu, 22 Oct 1998 09:20:14 -0700 (PDT) From: Archie Cobbs Message-Id: <199810221620.JAA01628@bubba.whistle.com> Subject: Re: Another Serious libc_r problem In-Reply-To: <199810220106.VAA07017@pcnet1.pcnet.com> from Daniel Eischen at "Oct 21, 98 09:06:18 pm" To: eischen@vigrid.com (Daniel Eischen) Date: Thu, 22 Oct 1998 09:20:14 -0700 (PDT) Cc: current@FreeBSD.ORG, lists@tar.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen writes: > > > > I would argue that for any case that POSIX says results in "undefined > > > > behavior", and the pthread code can easily detect this case, FreeBSD > > > > should immediately abort(3). Threads programmers will thank you > > > > when their bugs are revealed for them. > > > > > > If it's like pthread_mutex_lock(), POSIX will say that pthread_cond_wait > > > should return EINVAL if it doesn't own the mutex *and* this condition > > > is detected by the implementation. Much as we'd like to say "Bad > > > programmer, Bad!" I don't think POSIX will allow us to with anything > > > other than an EINVAL return value. > > > > What you've described looks like *defined* behavior to me... > > Well, that's what the POSIX spec says. If you are going to > detect the condition, then you must return EINVAL. If you > are not going to detect the condition, then "undefined > behavior" occurs. So, then it's kindof like an honor system :-) who's to know when you've "detected" it? Anyway, I conceed. Modify the original idea with the phrase "when not in conflict with the spec"... -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 09:31:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17583 for freebsd-current-outgoing; Thu, 22 Oct 1998 09:31:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17564 for ; Thu, 22 Oct 1998 09:31:23 -0700 (PDT) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.9.1) id LAA22103; Thu, 22 Oct 1998 11:27:36 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 22 Oct 1998 11:27:36 -0500 (CDT) Reply-To: conrads@neosoft.com Organization: NeoSoft, Inc. From: Conrad Sabatier To: Cory Kempf Subject: RE: Netscape 4.5 & ld-linux.so.2? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Oct-98 Cory Kempf wrote: > When I make netscape 4.5 from the ports collection (or just > downloading the it from netscape's web site), I get the following when > I try to run: > > % netscape > ELF interpreter /compat/linux/lib/ld-linux.so.2 not found > zsh: abort netscape > > /compat/linux/lib contains a ld-linux.so.1, and a ld-linux.so.1.7.14, > but no .2 version. Where does the missing version come from? > > This is on a -current from a few days ago. How strange. I was reading this thread as I was in the process of downloading the Linux version of Communicator 4.5, and thought, "Oh no! Trouble ahead!". Installed a few minutes ago and it ran fine the first time (and I have no /compat/linux/lib/ld-linux.so.2, nor even a symlink to it). Don't ask me, I'm just glad it's working! :-) -- Conrad Sabatier Hanlon's Razor: Never attribute to malice that which is adequately explained by stupidity. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 09:36:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18471 for freebsd-current-outgoing; Thu, 22 Oct 1998 09:36:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA18464 for ; Thu, 22 Oct 1998 09:36:56 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 17471 invoked from network); 22 Oct 1998 16:36:25 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 22 Oct 1998 16:36:25 -0000 Date: Thu, 22 Oct 1998 11:36:25 -0500 (CDT) From: John Sconiers To: slpalmer@email.com cc: "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: Riva TNT / XF86 / FreeBSD In-Reply-To: <9810221059415K.14741@www4.iname.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998 slpalmer@email.com wrote: > I've gotten Dave Schmenk's patches, and > though they applied cleanly, they did not > build on my FreeBSD-current box... I've sent > Dave Schmenk e-mail, hoping to fix this. I > will make the binary available once I've got > one ;-) I'm not implying that anyone here is not installing the patches correctly but on a 2.2.7 box the pathc worked. Since then he has went up to a -current snapshot and it still works. i will attempt to contact him to make sure he's not having a problem. > slpalmer JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 09:53:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20541 for freebsd-current-outgoing; Thu, 22 Oct 1998 09:53:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20528 for ; Thu, 22 Oct 1998 09:53:50 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA16575; Thu, 22 Oct 1998 10:53:15 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810221653.KAA16575@panzer.plutotech.com> Subject: Re: cdda2wav == panic (/sys/vm/vm_page.c:516) In-Reply-To: <19981021224539.A10190@znh.org> from Zach Heilig at "Oct 21, 98 10:45:39 pm" To: zach@gaffaneys.com (Zach Heilig) Date: Thu, 22 Oct 1998 10:53:15 -0600 (MDT) Cc: FreeBSD-current@FreeBSD.ORG, dg@root.com X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zach Heilig wrote... > This is an ELF kernel compiled from sources cvsup-ed ~01:50 GMT (Oct 22) > > Relevent hardware: > ncr0: rev 0x04 int a irq 11 on pci0.13.0 > cd0 at ncr0 bus 0 target 5 lun 0 > cd0: Removable CD-ROM SCSI2 device > cd0: 10.0MB/s transfers (10.0MHz, offset 8) > cd0: cd present [176612 x 2048 byte records] > > The ncr0 is a diamond fireport 40, and the cdr is the only device on that bus > (it is in an external case, with a terminator plugged into the passthrough > connector). It works very well burning audio/data tracks and reading data > tracks. > > I noticed this earlier today with a kernel from Oct 10. The panic with an up > to date kernel is different from the Oct 10 kernel. That kernel would usually > wait until cdda2wav exited before panic'ing (complaining about dirty pages -- > the last 5-10 megs or so of the track would be zero's after reboot), today's > kernel panics 8-10 Mbytes into the track (at least the 3 times I tried to > read an audio track). > > stack trace: [ ... ] > #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 > 268 dumppcb.pcb_cr3 = rcr3(); > (kgdb) where > #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 > #1 0xf01478bc in at_shutdown (function=0xf022901e , > arg=0xf48daba8, queue=-267228095) at ../../kern/kern_shutdown.c:430 > #2 0xf0126ca1 in db_panic (addr=-266451744, have_addr=0, count=-1, > modif=0xf48dab30 "") at ../../ddb/db_command.c:432 > #3 0xf0126c41 in db_command (last_cmdp=0xf0246804, cmd_table=0xf0246664, > aux_cmd_tablep=0xf025c4e4) at ../../ddb/db_command.c:332 > #4 0xf0126d06 in db_command_loop () at ../../ddb/db_command.c:454 > #5 0xf0129067 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 > #6 0xf01ec719 in kdb_trap (type=12, code=0, regs=0xf48dac70) > at ../../i386/i386/db_interface.c:157 > #7 0xf01f6d93 in trap_fatal (frame=0xf48dac70) at ../../i386/i386/trap.c:874 > #8 0xf01f6a84 in trap_pfault (frame=0xf48dac70, usermode=0) > at ../../i386/i386/trap.c:772 > #9 0xf01f66d7 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -236365800, > tf_esi = 8550, tf_ebp = -192041804, tf_isp = -192041832, tf_ebx = 51390, > tf_edx = 65470, tf_ecx = -192026224, tf_eax = -264085512, > tf_trapno = 12, tf_err = 0, tf_eip = -266451744, tf_cs = 8, > tf_eflags = 66054, tf_esp = 0, tf_ss = 0}) at ../../i386/i386/trap.c:396 > #10 0xf01e44e0 in vm_page_lookup (object=0xf48de990, pindex=8550) > at ../../vm/vm_page.c:516 > #11 0xf01630c7 in allocbuf (bp=0xf1e95818, size=8192) > at ../../kern/vfs_bio.c:1782 > #12 0xf0162cb2 in getblk (vp=0xf48a82c0, blkno=4275, size=8192, slpflag=0, > slptimeo=0) at ../../kern/vfs_bio.c:1557 > #13 0xf01cb09f in ffs_balloc (ap=0xf48dae98) at ../../ufs/ffs/ffs_balloc.c:297 > #14 0xf01d38a4 in ffs_write (ap=0xf48daeec) at vnode_if.h:1015 > #15 0xf016dc17 in vn_write (fp=0xf0b28640, uio=0xf48daf30, cred=0xf0a59b00) > at vnode_if.h:331 > #16 0xf014f9a2 in write (p=0xf4834e00, uap=0xf48daf84) > at ../../kern/sys_generic.c:270 > #17 0xf01f7017 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 805601292, > tf_esi = 805601292, tf_ebp = 805730652, tf_isp = -192041004, > tf_ebx = 129360, tf_edx = 805601292, tf_ecx = 0, tf_eax = 4, > tf_trapno = 7, tf_err = 2, tf_eip = 671874136, tf_cs = 31, > tf_eflags = 582, tf_esp = -272640664, tf_ss = 39}) > at ../../i386/i386/trap.c:1031 > #18 0xf01ed06c in Xint0x80_syscall () > (kgdb) This is a known problem. Daniel O'Conner first reported it with 2.2.7 and CAM. See PR kern/8112. I was also able to reproduce the problem under -current/CAM last month. I haven't messed with it since. Here's the stack trace from my panic last month (Sept. 8th): ================================================================== login: vm_page_free: pindex(63), busy(0), PG_BUSY(1), hold(9) panic: vm_page_free: freeing busy page mp_lock = 01000001; cpuid = 1; lapic.id = 00000000 Debugger("panic") Stopped at _Debugger+0x35: movb $0,_in_Debugger.98 db> trace _Debugger(f0134343) at _Debugger+0x35 _panic(f01f17ff,f054241c,80000000,f83f3ea8,f01f19b0) at _panic+0x8d _vm_page_freechk_and_unqueue(f054241c) at _vm_page_freechk_and_unqueue+0x6e _vm_page_free(f054241c,f8976220,0,f83f3ed4,f01eeffd) at _vm_page_free+0x1c _vm_object_terminate(f8976220,f4dd85f0,f091e220,f189e440,f83f3ee8) at _vm_object_terminate+0xb7 _vm_object_deallocate(f8976220,f4dd85f0,0,f83f3f00,f01423fe) at _vm_object_deallocate+0x1c9 _shm_deallocate_segment(f4dd85f0,f189e440,0,f8344cc0,f83f3f1c) at _shm_deallocate_segment+0x12 _shm_delete_mapping(f8344cc0,f189e440) at _shm_delete_mapping+0x6e _shmexit(f8344cc0) at _shmexit+0x29 _exit1(f8344cc0,0,f83f3fb4,f020dbdf,f8344cc0) at _exit1+0x1bc _exit(f8344cc0,f83f3f94,200c2060,ffffffff,0) at _exit+0x14 _syscall(27,27,0,ffffffff,efbfd2f4) at _syscall+0x187 _Xsyscall() at _Xsyscall+0x55 --- syscall 0x1, eip = 0x200b1c4d, esp = 0xefbfd2e0, ebp = 0xefbfd2f4 --- db> panic panic: from debugger mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 ================================================================== It looks like your panic is somewhat different from the one I saw. Daniel O'Conner was able to work around this by hacking cdda2wav so it didn't remove shared memory segments. However, he got the same panic later when he tried to remove the shared memory segments by hand. From your later mail, it looks like you've found other ways to work around it. If I knew what the problem was, I would have probably fixed it by now. :) I think it will take someone knowledgeable about the VM system to fix this, so I'm CCing this to David. :) The CAM passthrough driver uses vmapbuf() and vunmapbuf() (via cam_periph_mapmem()) to map data segments into and out of kernel virtual memory. My guess is that this, in combination with cdda2wav's shared memory usage, exposes some VM bug. Anyway, hopefully someone can shed some light on this. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 10:38:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27559 for freebsd-current-outgoing; Thu, 22 Oct 1998 10:38:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup10.gaffaneys.com [208.155.161.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27551 for ; Thu, 22 Oct 1998 10:38:28 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id RAA05423; Thu, 22 Oct 1998 17:38:38 GMT (envelope-from zach) Message-ID: <19981022123838.A5174@znh.org> Date: Thu, 22 Oct 1998 12:38:38 -0500 From: Zach Heilig To: "Kenneth D. Merry" , Zach Heil{g Cc: FreeBSD-current@FreeBSD.ORG, dg@root.com Subject: Re: cdda2wav == panic (/sys/vm/vm_page.c:516) References: <19981021224539.A10190@znh.org> <199810221653.KAA16575@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: <199810221653.KAA16575@panzer.plutotech.com>; from Kenneth D. Merry on Thu, Oct 22, 1998 at 10:53:15AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 22, 1998 at 10:53:15AM -0600, Kenneth D. Merry wrote: > It looks like your panic is somewhat different from the one I saw. > > Daniel O'Conner was able to work around this by hacking cdda2wav so it > didn't remove shared memory segments. However, he got the same panic later > when he tried to remove the shared memory segments by hand. From your > later mail, it looks like you've found other ways to work around it. I tried to get rid of shared memory all together to see if that was the problem (it has #if's to use pipes instead), but that just dumps core. > If I knew what the problem was, I would have probably fixed it by now. :) > I think it will take someone knowledgeable about the VM system to fix this, > so I'm CCing this to David. :) > > The CAM passthrough driver uses vmapbuf() and vunmapbuf() (via > cam_periph_mapmem()) to map data segments into and out of kernel virtual > memory. My guess is that this, in combination with cdda2wav's shared > memory usage, exposes some VM bug. > > Anyway, hopefully someone can shed some light on this. I hope so... After making it use only 1 sector, I did notice that the 55 2352 byte sectors it writes (with a single call to a file opened with O_NONBLOCK) happens to be the most sectors that fit in under 128K (coincidence?). If I set the number of sectors it writes (-n option) to 22, it does not crash, even after trying it several times (this is just over 50K.. I should have tried 27 and 28 sectors, the sector counts on each side 64K.. will be trying that later). My guess is the shared memory segment is getting ripped out from under the write() syscall. I did get a 'vm_page_cache: caching a dirty page, pindex:' panic first few times I tried it (before updating to Oct 22... I don't recall the exact message, that one is from /sys/vm/vm_page.c -- it's the only message that mostly resembles those first few panic's). -- Zach Heilig If it looks like a duck, and quacks like a duck, we have to at least consider the possibility that we have a small aquatic bird of the family Anatidæ on our hands (Douglas Adams -- Dirk Gently's Holistic Detective Agency) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 10:40:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27896 for freebsd-current-outgoing; Thu, 22 Oct 1998 10:40:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from locnar.eng.mindspring.net (locnar.eng.mindspring.net [207.69.192.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27890 for ; Thu, 22 Oct 1998 10:40:34 -0700 (PDT) (envelope-from sevn@mindspring.net) Received: from localhost (localhost [127.0.0.1]) by locnar.eng.mindspring.net (8.9.1/8.9.1) with SMTP id NAA07297 for ; Thu, 22 Oct 1998 13:37:15 -0400 (EDT) (envelope-from sevn@mindspring.net) Date: Thu, 22 Oct 1998 13:37:15 -0400 (EDT) From: Scott Wilson X-Sender: sevn@locnar.eng.mindspring.net To: current@FreeBSD.ORG Subject: Re: 3.0-Current/3Com 509B ether problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the same problem with a 3c509TPO a while back. Going into the mother bios and saying specifically that IRC 10 was used by ISA fixed it for me. It's also possible that the card is now convinced that it's supposed to be somewhere else. I think we had to reset a card at work once with the DOS utility on a win95 box, then put it back into the FreeBSD machine. I've also had problems before if the motherboard bios is set to "plug and play OS installed". Hope this helps. Scott On Thu, 22 Oct 1998, Doug White wrote: > On Wed, 21 Oct 1998, steven wrote: > > > but i have a problem that no posts seems to clearly identify or > > fix. > > > > i've got a 3com 509b ISA ethernet card. > > It worked fine with 2.2.6 2.2.7 and an early Sept 3.0 install. > > I went to the last BETA and the bootup stopped seeing the card. > > I went 3.0-current and same thing. > > > > dmesg shows.. > > > > fd0: 1.44MB 3.5in > > ie0: unknown board_id: f000 > > ie0 not found at 0x300 > > ep0 not found at 0x300 > > npx0 on motherboard > > > > before 3.0 it never detected anything on ie0 and ep0 was always what > > i used for the card. > > > > I swapped the card into my Windows box and the card does appear to > > work. Ideas? > > Um, disable the ethernet card drivers you're not using? Some ether card > probes are destructive. Ican't say I've noticed the same thing on my > systems with ie and ep both turned on, it sees no ie0 but the ep0 at IRQ > 10 port 0x300 is detected properly. > > Doug White > Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 10:48:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29447 for freebsd-current-outgoing; Thu, 22 Oct 1998 10:48:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup6.gaffaneys.com [208.155.161.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29438 for ; Thu, 22 Oct 1998 10:48:53 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id RAA05423; Thu, 22 Oct 1998 17:38:38 GMT (envelope-from zach) Message-ID: <19981022123838.A5174@znh.org> Date: Thu, 22 Oct 1998 12:38:38 -0500 From: Zach Heilig To: "Kenneth D. Merry" , Zach Heil{g Cc: FreeBSD-current@FreeBSD.ORG, dg@root.com Subject: Re: cdda2wav == panic (/sys/vm/vm_page.c:516) References: <19981021224539.A10190@znh.org> <199810221653.KAA16575@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: <199810221653.KAA16575@panzer.plutotech.com>; from Kenneth D. Merry on Thu, Oct 22, 1998 at 10:53:15AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 22, 1998 at 10:53:15AM -0600, Kenneth D. Merry wrote: > It looks like your panic is somewhat different from the one I saw. > > Daniel O'Conner was able to work around this by hacking cdda2wav so it > didn't remove shared memory segments. However, he got the same panic later > when he tried to remove the shared memory segments by hand. From your > later mail, it looks like you've found other ways to work around it. I tried to get rid of shared memory all together to see if that was the problem (it has #if's to use pipes instead), but that just dumps core. > If I knew what the problem was, I would have probably fixed it by now. :) > I think it will take someone knowledgeable about the VM system to fix this, > so I'm CCing this to David. :) > > The CAM passthrough driver uses vmapbuf() and vunmapbuf() (via > cam_periph_mapmem()) to map data segments into and out of kernel virtual > memory. My guess is that this, in combination with cdda2wav's shared > memory usage, exposes some VM bug. > > Anyway, hopefully someone can shed some light on this. I hope so... After making it use only 1 sector, I did notice that the 55 2352 byte sectors it writes (with a single call to a file opened with O_NONBLOCK) happens to be the most sectors that fit in under 128K (coincidence?). If I set the number of sectors it writes (-n option) to 22, it does not crash, even after trying it several times (this is just over 50K.. I should have tried 27 and 28 sectors, the sector counts on each side 64K.. will be trying that later). My guess is the shared memory segment is getting ripped out from under the write() syscall. I did get a 'vm_page_cache: caching a dirty page, pindex:' panic first few times I tried it (before updating to Oct 22... I don't recall the exact message, that one is from /sys/vm/vm_page.c -- it's the only message that mostly resembles those first few panic's). -- Zach Heilig If it looks like a duck, and quacks like a duck, we have to at least consider the possibility that we have a small aquatic bird of the family Anatidæ on our hands (Douglas Adams -- Dirk Gently's Holistic Detective Agency) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 11:20:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03392 for freebsd-current-outgoing; Thu, 22 Oct 1998 11:20:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opi.flirtbox.ch ([62.48.0.50]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA03387 for ; Thu, 22 Oct 1998 11:20:12 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 7749 invoked from network); 22 Oct 1998 18:18:20 -0000 Received: from unknown (HELO pipeline.ch) (195.134.140.1) by opi.flirtbox.ch with SMTP; 22 Oct 1998 18:18:20 -0000 Message-ID: <362F773B.62E19504@pipeline.ch> Date: Thu, 22 Oct 1998 20:19:39 +0200 From: Andre Oppermann Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: ALTQ in -current? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi How far is the integration of ALTQ into -current (Post-3.0) away? I'd like to volunteer if help is needed. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 11:24:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04115 for freebsd-current-outgoing; Thu, 22 Oct 1998 11:24:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from stennis.ca.sandia.gov (stennis.ca.sandia.gov [146.246.243.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04108 for ; Thu, 22 Oct 1998 11:24:09 -0700 (PDT) (envelope-from bmah@stennis.ca.sandia.gov) Received: (from bmah@localhost) by stennis.ca.sandia.gov (8.9.1/8.9.1) id LAA10521; Thu, 22 Oct 1998 11:23:32 -0700 (PDT) Message-Id: <199810221823.LAA10521@stennis.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: Kris Kennaway Cc: John Saunders , FreeBSD current Subject: Re: Package upgrade check program In-Reply-To: Your message of "Thu, 22 Oct 1998 15:19:12 +0930." From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_132680773P"; micalg=pgp-md5; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 22 Oct 1998 11:23:31 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_132680773P Content-Type: text/plain; charset=us-ascii If memory serves me right, Kris Kennaway wrote: > On Thu, 22 Oct 1998, John Saunders wrote: > > > With everybody hot into upgrading to 3.0, I thought I would > > throw this script in that I have been working on the last > > couple of days (bit at a time). This script suggests upgrades > > to installed packages. I'm continuing to work on a version > > that will do the upgrade for you (after prompting of course). > > Bruce Mah posted a similar script to one of the mailing lists a few months > ago- search the mailing list archives for pkg_version. IMO it would be good t > o > get something like this into the base system, or perhaps as a port (a la > mergemaster). Perhaps you could get together and combine your good ideas and > submit something to the ports team. I did submit pkg_version as a new port (ports/7777), but it probably wasn't high up enough on anyone's priority list to commit, with all of the 3.0-RELEASE stuff happening about the same time. Since then, it needs a little tweak to make it find perl correctly (i.e. use ${PERL}). I haven't done a follow-up yet, because I just now got a 3.0-RELEASE machine up to test things on. I'm a little leery of the "automatic upgrades" part, and I never had any plans to put it into pkg_version. In my experience it's too easy to get really confused by having multiple versions of a port installed (e.g. ssh-1.2.2[256]), and you sometimes can't predict all these due to port dependencies. Moreover, different packages have various degrees of co-existence tolerance, and the INDEX file can't really express this information well. This paragraph isn't criticism of the ports system; it's a hard problem. I'm not sure what the right solution is. So I just took the easy way out...pkg_version just generates a report (as John's pkg_check does), and it's up to the user to figure out what to do. Right now it does pretty much everything that I personally need it to do. John, what else (in addition to automatic upgrades) do you have in mind for pkg_check? Bruce. --==_Exmh_132680773P Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.2 iQCVAwUBNi94I6jOOi0j7CY9AQE5VgP/fdu9hBbDysGOaOeF6YTQiUlzsmuxmfKN Oe5TD2HvnEPFGZY0BBByKNEloGcyFOyYteQyxCZMl3s5wzSalRDNO89mSH4nyihS ZlgDXorpX6Fd+idhYWNcxybfHUQViWjWX9JPWvKv22pKZzbErCOcGEPV3nzn0dUB YOTP90ZYDLo= =xnEd -----END PGP MESSAGE----- --==_Exmh_132680773P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 12:02:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09889 for freebsd-current-outgoing; Thu, 22 Oct 1998 12:02:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fani.fidata.fi (fani.fidata.fi [193.64.102.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09884 for ; Thu, 22 Oct 1998 12:02:30 -0700 (PDT) (envelope-from tomppa@fidata.fi) Received: from zeta.fidata.fi (zeta.fidata.fi [193.64.103.213]) by fani.fidata.fi (8.8.8/8.8.8) with ESMTP id WAA00795 for ; Thu, 22 Oct 1998 22:01:58 +0300 (EET DST) Received: (from tomppa@localhost) by zeta.fidata.fi (8.9.1/8.9.1) id WAA22337; Thu, 22 Oct 1998 22:01:58 +0300 (EET DST) From: Tomi Vainio MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13871.33062.481564.696745@zeta.fidata.fi> Date: Thu, 22 Oct 1998 22:01:58 +0300 (EET DST) To: freebsd-current@FreeBSD.ORG Subject: 3.0 current mkdir/umask problem X-Mailer: VM 6.47 under 20.4 "Emerald" XEmacs Lucid Reply-To: tomppa@fidata.fi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I feel little stupid asking this. I just installed 3.0R and compiled latest current over it. If I make new directory with mkdir command it will always get 777 permissions so it won't respect umask setting. I also tried mkdir binary from 2.2-stable and it works correctly. Is this some new nosecure option? Tomppa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 12:49:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17681 for freebsd-current-outgoing; Thu, 22 Oct 1998 12:49:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sunny.bog.msu.su (sunny.bog.msu.su [158.250.20.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17641 for ; Thu, 22 Oct 1998 12:49:04 -0700 (PDT) (envelope-from dima@bog.msu.su) Received: from localhost (dima@localhost) by sunny.bog.msu.su (8.9.1a/8.9.1) with ESMTP id WAA10347 for ; Thu, 22 Oct 1998 22:48:25 +0300 (MSK) (envelope-from dima@bog.msu.su) Date: Thu, 22 Oct 1998 22:48:24 +0300 (MSK) From: Dmitry Khrustalev To: freebsd-current@FreeBSD.ORG Subject: perl5 modules version breakage in current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some perl modules in the tree generate their version number like this: $VERSION = (qw$Revision$)[1]; or $VERSION = substr q$Revision$, 10; or $VERSION = sprintf("%d.%02d", q$Revision$ =~ /(\d+)\.(\d+)/); since cvs changes $Revision$ this breaks CPAN, use Module VERSION, etc. -Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 12:55:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19139 for freebsd-current-outgoing; Thu, 22 Oct 1998 12:55:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19115 for ; Thu, 22 Oct 1998 12:55:16 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by ns1.aha.ru (8.9.1/8.9.1/aha-r/0.04B) with ESMTP id XAA24961 for ; Thu, 22 Oct 1998 23:54:45 +0400 (MSD) Received: by sunny.aha.ru id XAA19913; (8.8.8/vak/1.9) Thu, 22 Oct 1998 23:54:12 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma019884; Thu Oct 22 23:54:04 1998 Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by serv.etrust.ru (8.9.1/8.9.1) with ESMTP id XAA00190 for ; Thu, 22 Oct 1998 23:46:06 +0400 (MSD) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id XAA08784 for ; Thu, 22 Oct 1998 23:39:50 +0400 (MSD) (envelope-from osa@etrust.ru) Date: Thu, 22 Oct 1998 23:39:49 +0400 (MSD) From: oZZ!!! To: current@FreeBSD.ORG Subject: netscape-4.07 from ports can't work on 3.0-RELEASE ??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! My system is FreeBSD-3.0-ELF with ELF-kernel. I install Netscape Communicator-4.07 from ports... When i type: $ netscape Bus error (core dumped) $ ls -l *.core -rw------- 1 ... ...... 3497984 22 ÏËÔ 23:28 communicator-4.0.core $ gdb ..... (gdb) core communicator-4.0.core "/usr/home/.../communicator-4.0.core" is not a core dump: File format not recognized Any idea ? Rgdz, oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 13:04:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21124 for freebsd-current-outgoing; Thu, 22 Oct 1998 13:04:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20937 for ; Thu, 22 Oct 1998 13:03:59 -0700 (PDT) (envelope-from gozer@ludd.luth.se) Received: from father.ludd.luth.se (gozer@father.ludd.luth.se [130.240.16.18]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id VAA16799; Thu, 22 Oct 1998 21:03:20 +0100 Date: Thu, 22 Oct 1998 22:03:19 +0200 (MET DST) From: Johan Larsson To: Tomi Vainio cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 current mkdir/umask problem In-Reply-To: <13871.33062.481564.696745@zeta.fidata.fi> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998, Tomi Vainio wrote: > I feel little stupid asking this. I just installed 3.0R and compiled > latest current over it. If I make new directory with mkdir command it > will always get 777 permissions so it won't respect umask setting. I > also tried mkdir binary from 2.2-stable and it works correctly. Is > this some new nosecure option? I can confirm this, make world this night, and hey: johan@ball; mkdir test johan@ball; touch test2 johan@ball; ls -ald test test2 -rw-rw-r-- 1 johan johan 0 Oct 22 22:02 test2 drwxrwxrwx 2 johan johan 512 Oct 22 22:02 test/ johan@ball; umask 2 Yikes.... :) (Doesn't matter if it's on nfs or local). Johan -- * mailto:gozer@ludd.luth.se * http://www.ludd.luth.se/users/gozer/ * * Powered by FreeBSD. http://www.se.freebsd.org/ +-+-+-+-+-+-+-+-+ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 13:20:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23645 for freebsd-current-outgoing; Thu, 22 Oct 1998 13:20:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.84.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23486; Thu, 22 Oct 1998 13:19:09 -0700 (PDT) (envelope-from root@danberlin.resnet.rochester.edu) Received: from danberlin.resnet.rochester.edu (root@danberlin.resnet.rochester.edu [128.151.84.217]) by danberlin.resnet.rochester.edu (8.9.1a+3.1W/8.9.1/Debian/GNU) with ESMTP id OAA15170; Thu, 22 Oct 1998 14:59:31 -0400 Date: Thu, 22 Oct 1998 14:59:31 -0400 (EDT) From: Daniel Berlin To: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Our CardBus support Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the status of cardbus support in -current. I notice pcic_p.c in the pci dir, and it appears to have defines for TI CardBus controllers, and one other type. Do the TI's actually work? I have a TI1250 in my laptop, and from looking at the linux PCMCIA CS stuff, they just treat it like an 113x, except for one small thing to determine what mode it is in. I tried a quick hack, and added the device ID into pcic_p.h, and the approriate stuff in pcic_p.c, and it no work (right now i've got it complaining about intr_connect failing for a few IRQ's). I'll try it with two other CardBus cards, and i just tried it with a 3C589, and it noticed none of them. So is this my stupidity, or is our cardbus support not up to snuff yet, and if this is the case, is anyone working on it? If not, i guess i'll give it a whirl. Any clue how much work it would take? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 13:53:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28461 for freebsd-current-outgoing; Thu, 22 Oct 1998 13:53:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28456 for ; Thu, 22 Oct 1998 13:53:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00823; Thu, 22 Oct 1998 13:57:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222057.NAA00823@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Zach Heilig cc: FreeBSD-current@FreeBSD.ORG Subject: Re: cdda2wav == panic ... (cases where it does NOT panic) In-reply-to: Your message of "Thu, 22 Oct 1998 07:42:23 CDT." <19981022074223.A1730@znh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 22 Oct 1998 13:57:53 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA28457 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > cdda2wav does not panic this system under these conditions: This issue has been discussed to death several times; it relates to a bad interaction between the I/O system and SYSV shared memory, where pages out of the shared region are still busy when cdda2wav exits. This appeared with the CAM integration, and *may* be related to the way the two interact. > 1) with the -N option (does not write data to disk) > 2) with the -n 1 option (reads/writes a single sector at a time, default is 55) > 3) when 'audio.wav' is a fifo, but it fails in a different (non-panic'y) way: > ... > No overlap sampling active > samplefiles size total will be 415316600 bytes. 10 tracks > recording seconds stereo with 16 bits @ Hz ->'audio'... > cannot set realtime scheduling policy: Function not implemented > cannot set realtime scheduling policy: Function not implemented > write(audio, 0x3004800C, 129360) = 8192 > Probably disk space exhausted: Undefined error: 0 This is a bug in cdda2wav it would appear; a short write is not an error. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 13:54:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28668 for freebsd-current-outgoing; Thu, 22 Oct 1998 13:54:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28661 for ; Thu, 22 Oct 1998 13:54:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00837; Thu, 22 Oct 1998 13:58:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222058.NAA00837@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: Netscape 4.5 & ld-linux.so.2? In-reply-to: Your message of "22 Oct 1998 09:07:02 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 13:58:31 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When I make netscape 4.5 from the ports collection (or just > downloading the it from netscape's web site), I get the following when > I try to run: > > % netscape > ELF interpreter /compat/linux/lib/ld-linux.so.2 not found > zsh: abort netscape > > /compat/linux/lib contains a ld-linux.so.1, and a ld-linux.so.1.7.14, > but no .2 version. Where does the missing version come from? > > This is on a -current from a few days ago. The linux_lib port hasn't been upgraded for glibc binaries yet. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 14:02:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00296 for freebsd-current-outgoing; Thu, 22 Oct 1998 14:02:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00287 for ; Thu, 22 Oct 1998 14:02:56 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id RAA03567; Thu, 22 Oct 1998 17:01:41 -0400 (EDT) (envelope-from wollman) Date: Thu, 22 Oct 1998 17:01:41 -0400 (EDT) From: Garrett Wollman Message-Id: <199810222101.RAA03567@khavrinen.lcs.mit.edu> To: Daniel Berlin Cc: current@FreeBSD.ORG Subject: Our CardBus support In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: Please post to one mailing-list only. > What is the status of cardbus support in -current. There isn't any. Several of us are working on it, at various priorities. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 14:24:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03368 for freebsd-current-outgoing; Thu, 22 Oct 1998 14:24:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03361 for ; Thu, 22 Oct 1998 14:24:27 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01027; Thu, 22 Oct 1998 14:28:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222128.OAA01027@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: tomppa@fidata.fi cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 current mkdir/umask problem In-reply-to: Your message of "Thu, 22 Oct 1998 22:01:58 +0300." <13871.33062.481564.696745@zeta.fidata.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 14:28:00 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I feel little stupid asking this. I just installed 3.0R and compiled > latest current over it. If I make new directory with mkdir command it > will always get 777 permissions so it won't respect umask setting. I > also tried mkdir binary from 2.2-stable and it works correctly. Is > this some new nosecure option? No, it's a bug in the "fixes" I committed from Apple via NetBSD. I'm working on doing it "right" (preserving the ability to set the mode properly, but also respecting the umask if you're not). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 14:36:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04686 for freebsd-current-outgoing; Thu, 22 Oct 1998 14:36:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.interlinks.net (ns2.interlinks.net [207.107.160.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04647; Thu, 22 Oct 1998 14:35:59 -0700 (PDT) (envelope-from bill@interlinks.net) Received: from localhost (bill@localhost) by ns2.interlinks.net (8.9.1/8.8.8) with ESMTP id RAA05042; Thu, 22 Oct 1998 17:28:33 -0400 (EDT) Date: Thu, 22 Oct 1998 17:28:33 -0400 (EDT) From: Bill Sandiford To: freebsd-current@FreeBSD.ORG cc: freebsd-stable@FreeBSD.ORG Subject: FreeBSD 3.0 Release and pw command - Potential Bug? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We are having a problem with FreeBSD 3.0 Release and it's associated pw command. We have scripts that used to work perfectly in the 2.2.x line. The script still works perfectly when we run it manually as root (logged in at the terminal) however when cron executes the script, the pw commands in the script don't work. We are executing the script using the crontab for root. We know that the script is executing because some of the other commands in the script are happening and working. The script is designed to add a new user to our system and the line with pw looks something like this : echo password | pw useradd username -h 0 -c "Full Name" -g group -u uid -m -d homedir obviously we substitute a correct numeric id for uid and proper groupname for group, etc. We are not sure if this is a problem with our system or a bug with the pw command that is in the 3.0 release...we have also tried invoking the script from and inetd process as well.....we have tried this script on 3 different systems and it doesn't work on any of them except when invoked manually. Any help please!!! ------------------------------------------ Bill Sandiford Jr. - Systems Administrator Interlinks - http://www.interlinks.net sysop@interlinks.net - bill@interlinks.net (905)404-0810 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 14:51:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06955 for freebsd-current-outgoing; Thu, 22 Oct 1998 14:51:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06935; Thu, 22 Oct 1998 14:51:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01173; Thu, 22 Oct 1998 14:52:24 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222152.OAA01173@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Sandiford cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? In-reply-to: Your message of "Thu, 22 Oct 1998 17:28:33 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 14:52:24 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is almost *never* correct to post to both -current and -stable. Please pick the one list that suits only. > We are having a problem with FreeBSD 3.0 Release and it's associated pw > command. We have scripts that used to work perfectly in the 2.2.x line. > The script still works perfectly when we run it manually as root (logged > in at the terminal) however when cron executes the script, the pw commands > in the script don't work. "Help, my car doesn't work. Help me!". You might want to start by offering some more details. Any error messages and the return code would be a good start. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 15:08:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09847 for freebsd-current-outgoing; Thu, 22 Oct 1998 15:08:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09836 for ; Thu, 22 Oct 1998 15:08:19 -0700 (PDT) (envelope-from w@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id AAA06664; Fri, 23 Oct 1998 00:07:35 +0200 (CEST) (envelope-from w@panke.de.freebsd.org) Received: (from w@localhost) by campa.panke.de.freebsd.org (8.8.8/8.8.8) id GAA06595; Thu, 22 Oct 1998 06:09:18 +0200 (MET DST) (envelope-from w) Message-ID: <19981022060917.A6585@panke.de.freebsd.org> Date: Thu, 22 Oct 1998 06:09:17 +0200 From: Wolfram Schneider To: Chuck Robey , "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: GNU Awk replacement References: <19981018223914.B25719@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Chuck Robey on Mon, Oct 19, 1998 at 02:08:54PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From my memory, kawk is 2 x slower than gawk. Wolfram On 1998-10-19 14:08:54 -0400, Chuck Robey wrote: > > Good question. Our kawk port (kawk-98.02.11). > > from http://cm.bell-labs.com/who/bwk/awk.tar.gz > > > > To quote: > > This is the version of awk described in "The AWK Programming Language", > > by Al Aho, Brian Kernighan, and Peter Weinberger > > (Addison-Wesley, 1988, ISBN 0-201-07981-X). > > > > It is under a Berkeley/MIT/CMU like copyright. > > I took a look at this. I _think_ it's what I would have named "nawk", > the new awk. I haven't checked it, and I don't immediately remember a > short test to prove it .... if I remember right, it was better usage of > associational arrays, and also better looping. I remember a while back, > learning the hard way that you really don't want to use the old, > original awk. Way too primitive for more than 10 liners. > > I think I'd be happy enough with kawk. Lucent has the copyright, but > it's totally open, they give it away. What's more, they've obviously > (see the FIXES file) kept putting real fixes into it, right up to this > year. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 15:08:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09872 for freebsd-current-outgoing; Thu, 22 Oct 1998 15:08:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09863 for ; Thu, 22 Oct 1998 15:08:31 -0700 (PDT) (envelope-from w@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id AAA06669; Fri, 23 Oct 1998 00:07:55 +0200 (CEST) (envelope-from w@panke.de.freebsd.org) Received: (from w@localhost) by campa.panke.de.freebsd.org (8.8.8/8.8.8) id GAA06605; Thu, 22 Oct 1998 06:14:39 +0200 (MET DST) (envelope-from w) Message-ID: <19981022061437.B6585@panke.de.freebsd.org> Date: Thu, 22 Oct 1998 06:14:37 +0200 From: Wolfram Schneider To: "Jeffrey J. Mountin" , freebsd-current@FreeBSD.ORG Subject: Re: 3.0 missing some docs? References: <3.0.3.32.19981021094325.00f6a88c@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <3.0.3.32.19981021094325.00f6a88c@207.227.119.2>; from Jeffrey J. Mountin on Wed, Oct 21, 1998 at 09:43:25AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-10-21 09:43:25 -0500, Jeffrey J. Mountin wrote: > This may be minor, but I noticed some empty directories in /usr/share/doc > > tutorials/ddwg: > tutorials/devel: > tutorials/diskformat: > tutorials/disklessx: > tutorials/fonts: > tutorials/mh: > tutorials/multios: > tutorials/newuser: > tutorials/ppp: > tutorials/upgrade: > > There were other additons (ie es and ja), but there were empty. These are > new since 2.2.7R. > > Oversight or on TDD list? The Makefiles to install the tutorials in /usr/share/doc/tuturials are not ready for 3.0. I will fix it in the next weeks. Wolfram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 15:43:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14665 for freebsd-current-outgoing; Thu, 22 Oct 1998 15:43:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.interlinks.net (ns2.interlinks.net [207.107.160.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14569; Thu, 22 Oct 1998 15:42:25 -0700 (PDT) (envelope-from sysop@interlinks.net) Received: from ns1 (ns3.interlinks.net [207.107.160.3]) by ns2.interlinks.net (8.9.1/8.8.8) with SMTP id SAA07374; Thu, 22 Oct 1998 18:34:02 -0400 (EDT) Message-ID: <000e01bdfe0d$09042b20$03a06bcf@ns1.interlinks.net> From: "Bill Sandiford" To: "Bill Sandiford" , "Mike Smith" Cc: , Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? Date: Thu, 22 Oct 1998 18:40:52 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3115.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike thanks for your kind words. If there was an error message or a return code I would of posted it...however since there was none I didn't...Nothing comes up on the screen...syslog doesn't print anything...I have even tried redirecting the output to /dev/console so that I wouldn't miss something that happened while cron was running the script...All produce nothing except for the text that the script is supposed to print out. > >It is almost *never* correct to post to both -current and -stable. >Please pick the one list that suits only. > >> We are having a problem with FreeBSD 3.0 Release and it's associated pw >> command. We have scripts that used to work perfectly in the 2.2.x line. >> The script still works perfectly when we run it manually as root (logged >> in at the terminal) however when cron executes the script, the pw commands >> in the script don't work. > >"Help, my car doesn't work. Help me!". > >You might want to start by offering some more details. Any error >messages and the return code would be a good start. > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 16:07:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18250 for freebsd-current-outgoing; Thu, 22 Oct 1998 16:07:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18225 for ; Thu, 22 Oct 1998 16:07:06 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id TAA13669 for ; Thu, 22 Oct 1998 19:06:14 -0400 (EDT) Date: Thu, 22 Oct 1998 19:06:14 -0400 (EDT) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: new boot tools Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are the new boot tools documented anywhere? Things like how to install them, and what kind of things to have on hand to deinstall them if an emergency should occur? Can't do too much experimentation without that. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 16:13:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19605 for freebsd-current-outgoing; Thu, 22 Oct 1998 16:13:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19586; Thu, 22 Oct 1998 16:13:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01710; Thu, 22 Oct 1998 16:16:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222316.QAA01710@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Bill Sandiford" cc: "Bill Sandiford" , "Mike Smith" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? In-reply-to: Your message of "Thu, 22 Oct 1998 18:40:52 EDT." <000e01bdfe0d$09042b20$03a06bcf@ns1.interlinks.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 16:16:55 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If there was an error message or a return code I would of posted > it...however since there was none I didn't...Nothing comes up on the > screen...syslog doesn't print anything...I have even tried redirecting the > output to /dev/console so that I wouldn't miss something that happened while > cron was running the script...All produce nothing except for the text that > the script is supposed to print out. Ok, but that was only half the question; pw also returns status codes according to . Something like: echo password | pw args... echo "pw returned $?" Can you send a sample, minimal example that fails? I tried: azaria# crontab -l # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.nextN12946 installed on Thu Oct 22 16:15:52 1998) # (Cron version -- $Id: crontab.c,v 1.11 1997/09/15 06:39:15 charnier Exp $) 16 * * * * /tmp/pwtest azaria# cat /tmp/pwtest #!/bin/sh echo password | /usr/sbin/pw useradd foo -h 0 azaria# finger foo Login: foo Name: User Foo Directory: /home/foo Shell: /bin/sh Never logged in. No Mail. No Plan. on a 3.0-RELEASE vintage system, so it doesn't seem to be fundamental breakage. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 16:30:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22195 for freebsd-current-outgoing; Thu, 22 Oct 1998 16:30:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22083 for ; Thu, 22 Oct 1998 16:29:59 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id QAA16447; Thu, 22 Oct 1998 16:29:05 -0700 (PDT) (envelope-from obrien) Message-ID: <19981022162904.D16225@nuxi.com> Date: Thu, 22 Oct 1998 16:29:04 -0700 From: "David O'Brien" To: John Sconiers , slpalmer@email.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Riva TNT / XF86 / FreeBSD Reply-To: obrien@NUXI.com References: <9810221059415K.14741@www4.iname.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from John Sconiers on Thu, Oct 22, 1998 at 11:36:25AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not implying that anyone here is not installing the patches correctly > but on a 2.2.7 box the pathc worked. Since then he has went up to a > -current snapshot and it still works. Would it be possible to put the Xserver you built up for download then? -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 16:35:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22717 for freebsd-current-outgoing; Thu, 22 Oct 1998 16:35:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lodgenet.com (cline.lodgenet.com [204.124.122.251]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22705 for ; Thu, 22 Oct 1998 16:35:03 -0700 (PDT) (envelope-from johnp@lodgenet.com) Received: from milo.lodgenet.com (milo.lodgenet.com [10.0.122.42]) by lodgenet.com (8.7.5/8.7.3) with ESMTP id SAA04610; Thu, 22 Oct 1998 18:34:31 -0500 Received: from milo.lodgenet.com (localhost [127.0.0.1]) by milo.lodgenet.com (8.9.1/8.9.1) with ESMTP id SAA12494; Thu, 22 Oct 1998 18:34:14 -0500 (CDT) (envelope-from johnp@milo.lodgenet.com) Message-Id: <199810222334.SAA12494@milo.lodgenet.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Bill Sandiford" cc: "Bill Sandiford" , "Mike Smith" , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? In-reply-to: Your message of "Thu, 22 Oct 1998 18:40:52 EDT." <000e01bdfe0d$09042b20$03a06bcf@ns1.interlinks.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 18:34:13 -0500 From: John Prince Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bill, Take a look at /var/cron/log .. See if there is something there that may shed some light.. --john "Bill Sandiford" writes: > Mike thanks for your kind words. > > > If there was an error message or a return code I would of posted > it...however since there was none I didn't...Nothing comes up on the > screen...syslog doesn't print anything...I have even tried redirecting the > output to /dev/console so that I wouldn't miss something that happened while > cron was running the script...All produce nothing except for the text that > the script is supposed to print out. > ....... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 17:20:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27484 for freebsd-current-outgoing; Thu, 22 Oct 1998 17:20:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27470 for ; Thu, 22 Oct 1998 17:20:33 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id KAA20357; Fri, 23 Oct 1998 10:19:36 +1000 (EST) Message-ID: <19981023101936.A20302@rf900.physics.usyd.edu.au> Date: Fri, 23 Oct 1998 10:19:36 +1000 From: David Dawes To: obrien@NUXI.com, slpalmer@email.com Cc: current@FreeBSD.ORG Subject: Re: Newbie (to development) would like to help References: <9810211141364G.14328@webc02.globecomm.net> <19981022021448.A13887@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981022021448.A13887@nuxi.com>; from David O'Brien on Thu, Oct 22, 1998 at 02:14:48AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 22, 1998 at 02:14:48AM -0700, David O'Brien wrote: >> RIVA TNT based video card (I'm running the VGA16 server until it's >> supported). > >I had a friend that had one of these. > >I emailed David Schmenk to see if they had a server >for us. He has a Linux server and offered me the patches/src so I could >make a FreeBSD one. > >My friend returned the card, so I didn't go thru with getting the src and >making a FreeBSD server. But you should contact him if you are >interested. Just to let you know, this code will also be included in XFree86 3.3.3, which should be released in the next month or so. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 17:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27929 for freebsd-current-outgoing; Thu, 22 Oct 1998 17:25:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caliban.dihelix.com (TCR1-Dialup42.PacificGlobal.NET [209.84.182.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27922 for ; Thu, 22 Oct 1998 17:25:04 -0700 (PDT) (envelope-from langfod@caliban.dihelix.com) Received: (from langfod@localhost) by caliban.dihelix.com (8.9.1/8.8.3) id PAA03182 for freebsd-current@freebsd.org; Thu, 22 Oct 1998 15:24:33 -1000 (HST) Date: Thu, 22 Oct 1998 15:24:33 -1000 (HST) From: David Langford Message-Id: <199810230124.PAA03182@caliban.dihelix.com> To: freebsd-current@FreeBSD.ORG Subject: 3.0-CURRENT and broken groff? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have a machine that I have been trying to get current compiled on. Strated from 3.0-RELEASE and cvsup'ed from there. Groff seems to be having problems though: ===> doc/smm/12.timed touch _stamp.extraobjs (cd /usr/src/share/doc/smm/12.timed/../../../../usr.sbin/timed/SMM.doc/timed; groff -mtty-char -Tascii -t -s -ms -o1- /usr/src/share/doc/smm/12.timed/../../../../usr.sbin/timed/SMM.doc/timed/timed.ms) | gzip -cn > paper.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' A trace shows: ... syscall open("devascii/DESC",0,0666) errno 2 'No such file or directory' groff: can't find `DESC' file I have tried every permution of rebuild world (-DNOSHARE, -k etc..) and I cant get past this. Obiously this breaks man pages et el. The libgroff that it builds seems to have: /usr/share/groff_font GROFF_FONT_PATH I cannot figure this out. Thank you, -David Langford langfod@dihelix.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 18:30:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04521 for freebsd-current-outgoing; Thu, 22 Oct 1998 18:30:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04516 for ; Thu, 22 Oct 1998 18:30:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02477; Thu, 22 Oct 1998 18:34:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810230134.SAA02477@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: new boot tools In-reply-to: Your message of "Thu, 22 Oct 1998 19:06:14 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 18:34:08 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are the new boot tools documented anywhere? Things like how to install > them, and what kind of things to have on hand to deinstall them if an > emergency should occur? The parts that require manual installation are installed just like the old ones. The remainder are installed by 'make world'. You deinstall the manually-installed parts by installing the old parts. For experimentation, just put "/boot/loader" in /boot.config. If it's not working for you, override it at the boot: prompt and then remove it when you're booted. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 18:40:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05465 for freebsd-current-outgoing; Thu, 22 Oct 1998 18:40:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05460 for ; Thu, 22 Oct 1998 18:40:55 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA00537; Fri, 23 Oct 1998 11:09:57 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19981022123838.A5174@znh.org> Date: Fri, 23 Oct 1998 11:09:57 +0930 (CST) From: "Daniel O'Connor" To: Zach Heilig Subject: Re: cdda2wav == panic (/sys/vm/vm_page.c:516) Cc: dg@root.com, FreeBSD-current@FreeBSD.ORG, "Kenneth D. Merry" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Oct-98 Zach Heilig wrote: > > Daniel O'Conner was able to work around this by hacking cdda2wav so it O'Connor =) > > when he tried to remove the shared memory segments by hand. From your > > later mail, it looks like you've found other ways to work around it. > I tried to get rid of shared memory all together to see if that was the > problem (it has #if's to use pipes instead), but that just dumps core. I 'fixed' (haha) it by altering it not to remove its shared memory on exit.. Of course you run out of share mem after a while, and then you have to delete some of it.. (Which works some of the time but if you pick the wrong segment and *booom*) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 19:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08419 for freebsd-current-outgoing; Thu, 22 Oct 1998 19:12:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08414 for ; Thu, 22 Oct 1998 19:12:44 -0700 (PDT) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id MAA23510; Fri, 23 Oct 1998 12:12:14 +1000 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma023508; Fri, 23 Oct 98 12:12:11 +1000 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id MAA06082 for ; Fri, 23 Oct 1998 12:12:09 +1000 From: "John Saunders" To: "FreeBSD current" Subject: RE: [Q]: Buildworld without secure libs (to use MD5 passwords) Date: Fri, 23 Oct 1998 12:12:09 +1000 Message-ID: <002a01bdfe2a$89f55480$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you want new passwords stored in MD5 and still decrypt DES, you have to > hack passwd to pass the MD5 magic '$1$' to the crypt() routine so it > returns an MD5 key. It's a one line change; I'm highly tempted to make > it a compile-time #define in the base code. How about changing passwd check for the existance of a magic file such as /etc/create_md5_passwords. Just like adjkerntz checks for the /etc/wall_cmos_clock file. This should do it... --- /usr/src/usr.bin/passwd/local_passwd.c.orig Fri Oct 23 12:04:27 1998 +++ /usr/src/usr.bin/passwd/local_passwd.c Fri Oct 23 12:09:25 1998 @@ -162,7 +162,8 @@ #else /* Make a good size salt for algoritms that can use it. */ gettimeofday(&tv,0); - if (strncmp(pw->pw_passwd, "$1$", 3)) { + if (strncmp(pw->pw_passwd, "$1$", 3) && + access("/etc/create_md5_passwords", F_OK)) { /* DES Salt */ to64(&salt[0], random(), 3); to64(&salt[3], tv.tv_usec, 3); Also I think that if you have DES installed, a make world should build and install _both_ the libdescrypt and libscrypt libraries. My system has libscrypt libraries from 2.2.5 because it doesn't get updated with make world. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 19:52:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11297 for freebsd-current-outgoing; Thu, 22 Oct 1998 19:52:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11286 for ; Thu, 22 Oct 1998 19:52:13 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (o2.cs.rpi.edu [128.213.8.201]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id WAA03972 for ; Thu, 22 Oct 1998 22:51:29 -0400 (EDT) Received: from o2.cs.rpi.edu (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id WAA19680 for ; Thu, 22 Oct 1998 22:51:29 -0400 (EDT) Message-Id: <199810230251.WAA19680@o2.cs.rpi.edu> X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Begging to be asked (ELF Kernel) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 22:51:28 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today I went to an ELF kernel, flawless, 3rd stage boot is wonderfull, many thanks to all involved, great job! I do have one[two] question[s]: *phoenix / $ file /kernel /kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped _dynamically linked_?? Curiosity got to me so I tried: *phoenix / $ ldd /kernel /kernel: /kernel: signal 6 signal 6 is 'sigabrt'. So my 2 questions are: 1)Why is the kernel dynamically linked, and 2) why can I not ldd the kernel (I coppied the file to another place and attempted to ldd that un-live kernel as well, no dice) -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 19:57:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11607 for freebsd-current-outgoing; Thu, 22 Oct 1998 19:57:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11599 for ; Thu, 22 Oct 1998 19:57:07 -0700 (PDT) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id TAA11585; Thu, 22 Oct 1998 19:57:48 -0700 (PDT) Message-Id: <199810230257.TAA11585@implode.root.com> To: "Kenneth D. Merry" cc: zach@gaffaneys.com (Zach Heilig), FreeBSD-current@FreeBSD.ORG Subject: Re: cdda2wav == panic (/sys/vm/vm_page.c:516) In-reply-to: Your message of "Thu, 22 Oct 1998 10:53:15 MDT." <199810221653.KAA16575@panzer.plutotech.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 22 Oct 1998 19:57:48 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> #7 0xf01f6d93 in trap_fatal (frame=0xf48dac70) at ../../i386/i386/trap.c:874 >> #8 0xf01f6a84 in trap_pfault (frame=0xf48dac70, usermode=0) >> at ../../i386/i386/trap.c:772 >> #9 0xf01f66d7 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -236365800, >> tf_esi = 8550, tf_ebp = -192041804, tf_isp = -192041832, tf_ebx = 51390, >> tf_edx = 65470, tf_ecx = -192026224, tf_eax = -264085512, >> tf_trapno = 12, tf_err = 0, tf_eip = -266451744, tf_cs = 8, >> tf_eflags = 66054, tf_esp = 0, tf_ss = 0}) at ../../i386/i386/trap.c:396 >> #10 0xf01e44e0 in vm_page_lookup (object=0xf48de990, pindex=8550) >> at ../../vm/vm_page.c:516 >> #11 0xf01630c7 in allocbuf (bp=0xf1e95818, size=8192) >> at ../../kern/vfs_bio.c:1782 The above indicates that the VM object hash list has been messed up for some reason. A VM object might have gotten trashed or perhaps the list pointers were messed up due to missing splvm protection somewhere. >Here's the stack trace from my panic last month (Sept. 8th): > >================================================================== >login: vm_page_free: pindex(63), busy(0), PG_BUSY(1), hold(9) >panic: vm_page_free: freeing busy page >mp_lock = 01000001; cpuid = 1; lapic.id = 00000000 >Debugger("panic") >Stopped at _Debugger+0x35: movb $0,_in_Debugger.98 >db> trace >_Debugger(f0134343) at _Debugger+0x35 >_panic(f01f17ff,f054241c,80000000,f83f3ea8,f01f19b0) at _panic+0x8d >_vm_page_freechk_and_unqueue(f054241c) at _vm_page_freechk_and_unqueue+0x6e >_vm_page_free(f054241c,f8976220,0,f83f3ed4,f01eeffd) at _vm_page_free+0x1c >_vm_object_terminate(f8976220,f4dd85f0,f091e220,f189e440,f83f3ee8) at _vm_object_terminate+0xb7 >_vm_object_deallocate(f8976220,f4dd85f0,0,f83f3f00,f01423fe) at _vm_object_deallocate+0x1c9 >_shm_deallocate_segment(f4dd85f0,f189e440,0,f8344cc0,f83f3f1c) at _shm_deallocate_segment+0x12 >_shm_delete_mapping(f8344cc0,f189e440) at _shm_delete_mapping+0x6e >_shmexit(f8344cc0) at _shmexit+0x29 >_exit1(f8344cc0,0,f83f3fb4,f020dbdf,f8344cc0) at _exit1+0x1bc This is a different, apparantly unrelated panic that seems to be caused by a bug with the original page allocation - it isn't properly clearing the PG_BUSY flag (via vm_page_wakeup()). This might be a bug in vm_fault(). >If I knew what the problem was, I would have probably fixed it by now. :) >I think it will take someone knowledgeable about the VM system to fix this, >so I'm CCing this to David. :) ... >The CAM passthrough driver uses vmapbuf() and vunmapbuf() (via >cam_periph_mapmem()) to map data segments into and out of kernel virtual >memory. My guess is that this, in combination with cdda2wav's shared >memory usage, exposes some VM bug. Hmmm. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 20:04:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12422 for freebsd-current-outgoing; Thu, 22 Oct 1998 20:04:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12413 for ; Thu, 22 Oct 1998 20:04:41 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id LAA24981; Fri, 23 Oct 1998 11:02:11 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810230302.LAA24981@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" cc: freebsd-current@FreeBSD.ORG Subject: Re: Begging to be asked (ELF Kernel) In-reply-to: Your message of "Thu, 22 Oct 1998 22:51:28 -0400." <199810230251.WAA19680@o2.cs.rpi.edu> Date: Fri, 23 Oct 1998 11:02:11 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: > Today I went to an ELF kernel, flawless, 3rd stage boot is wonderfull, many > thanks to all involved, great job! > > I do have one[two] question[s]: > > *phoenix / $ file /kernel > /kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), > dynamically linked, not stripped > > _dynamically linked_?? Heh. :-) Don't panic, it just means that it's got the data tables present that are mainly intended for ld.so. The in-kernel equivalent of ld.so uses these when loading kernel modules. > Curiosity got to me so I tried: > *phoenix / $ ldd /kernel > /kernel: > /kernel: signal 6 > > signal 6 is 'sigabrt'. > > So my 2 questions are: 1)Why is the kernel dynamically linked, and 2) why ca n > I not ldd the kernel (I coppied the file to another place and attempted to ld d > that un-live kernel as well, no dice) ldd is an a.out tool. What you want is: 122> objdump --all-headers /kernel | more /kernel: file format elf32-i386 /kernel architecture: i386, flags 0x00000112: EXEC_P, HAS_SYMS, D_PAGED start address 0xf011a460 Program Header: PHDR off 0x00000034 vaddr 0xf0100034 paddr 0xf0100034 align 2**2 filesz 0x000000a0 memsz 0x000000a0 flags r-x INTERP off 0x000000d4 vaddr 0xf01000d4 paddr 0xf01000d4 align 2**0 filesz 0x0000000d memsz 0x0000000d flags r-- LOAD off 0x00000000 vaddr 0xf0100000 paddr 0xf0100000 align 2**12 filesz 0x0013d790 memsz 0x0013d790 flags r-x LOAD off 0x0013d790 vaddr 0xf023e790 paddr 0xf023e790 align 2**12 filesz 0x0001519c memsz 0x00041d84 flags rw- DYNAMIC off 0x001528ec vaddr 0xf02538ec paddr 0xf02538ec align 2**2 filesz 0x00000040 memsz 0x00000040 flags rw- Dynamic Section: NEEDED hack.so HASH 0xf01000e4 STRTAB 0xf0110f5c SYMTAB 0xf01050ac STRSZ 0x94fd SYMENT 0x10 DEBUG 0x0 [..] "hack.so" is a red herring used to trick binutils ld into producing a dynamic object even though it's not actually used at link time. Note that the kernel is **not** PIC like shared libraries, so don't panic about the slowdown that PIC causes due to the loss of %ebx and the jump table indirection. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 22:03:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20878 for freebsd-current-outgoing; Thu, 22 Oct 1998 22:03:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from miris.lcs.mit.edu (miris.lcs.mit.edu [18.111.0.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20872 for ; Thu, 22 Oct 1998 22:03:10 -0700 (PDT) (envelope-from beng@miris.lcs.mit.edu) Received: from miris.lcs.mit.edu (beng@localhost [127.0.0.1]) by miris.lcs.mit.edu (8.8.7/8.8.7) with ESMTP id BAA01214 for ; Fri, 23 Oct 1998 01:02:12 -0400 (EDT) Message-Id: <199810230502.BAA01214@miris.lcs.mit.edu> To: freebsd-current@FreeBSD.ORG Subject: VM bug triggered by X server death From: Benjamin Greenwald X-Sender: beng@lcs.mit.edu Date: Fri, 23 Oct 1998 01:02:11 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings all, With the most recent kernel, every time my X server dies (reboot, explicit kill, whatever) the kernel panics. Looks like some sort of VM bug. A backtrace follows. This problem is easily and completely reproducible (translate it happens every time) and it occurs with both my Xi Graphics X server as well as the XSuSE XFCom_3DLabs server (I have a Fire GL 1000 Pro). -Ben bellatrix:/usr/src/sys/compile/BELLATRIX# gdb -k GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc. (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.1 (kgdb) core-file /var/crash/vmcore.1 IdlePTD 2760704 initial pcb at 23b038 panicstr: vm_page_remove: page not busy panic messages: --- panic: vm_page_remove: page not busy syncing disks... done dumping to dev 20409, offset 262272 dump 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 268 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 #1 0xf013f6dc in at_shutdown ( function=0xf021a0f1 , arg=0xf41bdfc0, queue=-199571212) at ../../kern/kern_shutdown.c:430 #2 0xf01d2505 in vm_page_remove (m=0xf41bdfc0) at ../../vm/vm_page.c:442 #3 0xf01d0a51 in vm_object_terminate (object=0xf41b7000) at ../../vm/vm_object.c:464 #4 0xf01d095d in vm_object_deallocate (object=0xf41b7000) at ../../vm/vm_object.c:391 #5 0xf01ce08f in vm_map_entry_delete (map=0xf414a100, entry=0xf41b884c) at ../../vm/vm_map.c:1742 #6 0xf01ce293 in vm_map_delete (map=0xf414a100, start=0, end=4022329344) at ../../vm/vm_map.c:1858 #7 0xf01ce319 in vm_map_remove (map=0xf414a100, start=0, end=4022329344) at ../../vm/vm_map.c:1883 #8 0xf0138c25 in exec_new_vmspace (imgp=0xf41ace9c) at ../../kern/kern_exec.c:441 #9 0xf012fae8 in exec_elf_imgact (imgp=0xf41ace9c) at ../../kern/imgact_elf.c:437 #10 0xf01386a3 in execve (p=0xf4146340, uap=0xf41acf94) at ../../kern/kern_exec.c:176 #11 0xf01e41eb in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 1286048, tf_esi = 8, tf_ebp = -272641892, tf_isp = -199569436, tf_ebx = 538153056, tf_edx = -272641812, tf_ecx = -272642001, tf_eax = 59, tf_trapno = 7, tf_err = 7, tf_eip = 537856945, tf_cs = 31, tf_eflags = 12946, tf_esp = -272643064, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #12 0x200f0bb1 in ?? () Cannot access memory at address 0xefbfd09c. (kgdb) up 2 #2 0xf01d2505 in vm_page_remove (m=0xf41bdfc0) at ../../vm/vm_page.c:442 442 panic("vm_page_remove: page not busy"); (kgdb) list 437 if (m->object == NULL) 438 return; 439 440 #if !defined(MAX_PERF) 441 if ((m->flags & PG_BUSY) == 0) { 442 panic("vm_page_remove: page not busy"); 443 } 444 #endif 445 446 vm_page_flag_clear(m, PG_BUSY); (kgdb) up #3 0xf01d0a51 in vm_object_terminate (object=0xf41b7000) at ../../vm/vm_object.c:464 464 vm_page_remove(p); (kgdb) list 459 vm_page_busy(p); 460 vm_page_free(p); 461 cnt.v_pfree++; 462 } else { 463 printf("vm_object_terminate: not freeing wired page; wire_count=%d\n", p->wire_count); 464 vm_page_remove(p); 465 } 466 } 467 /* 468 * Let the pager know object is dead. (kgdb) p *p $3 = {pageq = {tqe_next = 0xf41bdf80, tqe_prev = 0xf41b7078}, hashq = { tqe_next = 0xf41bdf80, tqe_prev = 0xf0413e80}, listq = { tqe_next = 0xf41bdf80, tqe_prev = 0xf41b7018}, object = 0xf41b7000, pindex = 160, phys_addr = 655360, queue = 0, flags = 184, pc = 0, wire_count = 1, hold_count = 0, act_count = 0 '\000', busy = 0 '\000', valid = 255 'ÿ', dirty = 0 '\000'} (kgdb) up #4 0xf01d095d in vm_object_deallocate (object=0xf41b7000) at ../../vm/vm_object.c:391 391 vm_object_terminate(object); (kgdb) list 386 if (temp->ref_count == 0) 387 vm_object_clear_flag(temp, OBJ_OPT); 388 temp->generation++; 389 object->backing_object = NULL; 390 } 391 vm_object_terminate(object); 392 /* unlocks and deallocates object */ 393 object = temp; 394 } 395 } (kgdb) p *object $5 = {object_list = {tqe_next = 0xf41c0f68, tqe_prev = 0xf41b7440}, shadow_head = {tqh_first = 0x0, tqh_last = 0xf41b7008}, shadow_list = { tqe_next = 0x0, tqe_prev = 0x0}, memq = {tqh_first = 0xf41bdfc0, tqh_last = 0xf41befd0}, generation = 388, type = OBJT_DEVICE, size = 929824, ref_count = 0, shadow_count = 0, pg_color = 17, id = 4029, flags = 8584, paging_in_progress = 0, behavior = 0, resident_page_count = 129, cache_count = 0, wire_count = 129, paging_offset = 0x0000000000000000, backing_object = 0x0, backing_object_offset = 0x0000000000000000, last_read = 0, page_hint = 0xf41befc0, pager_object_list = {tqe_next = 0x0, tqe_prev = 0xf023f9b4}, handle = 0x200, un_pager = {vnp = { vnp_size = 0xf41befc0f41bdfc0}, devp = {devp_pglist = { tqh_first = 0xf41bdfc0, tqh_last = 0xf41befc0}}, swp = { swp_nblocks = -199499840, swp_allocsize = -199495744, swp_blocks = 0x0, swp_poip = 0}}} (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 22:12:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21759 for freebsd-current-outgoing; Thu, 22 Oct 1998 22:12:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21748 for ; Thu, 22 Oct 1998 22:12:15 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from photon (photon [129.127.36.4]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id OAA14062; Fri, 23 Oct 1998 14:41:42 +0930 (CST) Received: from localhost by photon; (5.65/1.1.8.2/04Aug95-0645PM) id AA03316; Fri, 23 Oct 1998 14:41:42 +0930 Date: Fri, 23 Oct 1998 14:41:41 +0930 (CST) From: Kris Kennaway To: Benjamin Greenwald Cc: freebsd-current@FreeBSD.ORG Subject: Re: VM bug triggered by X server death In-Reply-To: <199810230502.BAA01214@miris.lcs.mit.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Oct 1998, Benjamin Greenwald wrote: > With the most recent kernel, every time my X server dies (reboot, explicit > kill, whatever) the kernel panics. Looks like some sort of VM bug. A > backtrace follows. This problem is easily and completely reproducible > (translate it happens every time) and it occurs with both my Xi Graphics X > server as well as the XSuSE XFCom_3DLabs server (I have a Fire GL 1000 Pro). I also get a panic in this case running a current kernel (ELF, and since dg's recent changes in this area). Mine however dies with (from memory): vm_object_terminate: not freeing wired page; wire_count=1 which is something dg changed the other day. I havent yet been able to get a core dump - something odd is going on where it says it's dumping an image, but doesnt seem to. I was planning on looking at this further since I've probably done something wrong (can you in fact dump to a vn which is configured as a swap device? I don't have big enough "real" swap partitions to take a kernel dump), but since it's come up.. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 22:16:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22104 for freebsd-current-outgoing; Thu, 22 Oct 1998 22:16:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22094 for ; Thu, 22 Oct 1998 22:16:54 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id WAA23336; Thu, 22 Oct 1998 22:16:15 -0700 (PDT) (envelope-from jdp) Message-Id: <199810230516.WAA23336@austin.polstra.com> To: peter@netplex.com.au Subject: Re: Begging to be asked (ELF Kernel) In-Reply-To: <199810230302.LAA24981@spinner.netplex.com.au> References: <199810230302.LAA24981@spinner.netplex.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 22 Oct 1998 22:16:15 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199810230302.LAA24981@spinner.netplex.com.au>, Peter Wemm wrote: > > So my 2 questions are: 1)Why is the kernel dynamically linked, > > and 2) why can I not ldd the kernel (I coppied the file to another > > place and attempted to ldd that un-live kernel as well, no dice) > > ldd is an a.out tool. It's an ELF tool too. Doug Rabson added the necessary stuff to the ELF dynamic linker last May. The way I would put it is that ldd is a tool for application programs, not for kernels. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 22:19:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22503 for freebsd-current-outgoing; Thu, 22 Oct 1998 22:19:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pozo.pozo.com (pozo.pozo.com [207.201.8.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22497 for ; Thu, 22 Oct 1998 22:19:08 -0700 (PDT) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.168.0.2]) by pozo.pozo.com (8.9.1/8.9.1) with SMTP id WAA00430; Thu, 22 Oct 1998 22:18:14 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <4.1.19981022221656.00a1bd00@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 22 Oct 1998 22:18:13 -0700 To: Benjamin Greenwald , freebsd-current@FreeBSD.ORG From: Manfred Antar Subject: Re: VM bug triggered by X server death In-Reply-To: <199810230502.BAA01214@miris.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:02 AM 10/23/98 -0400, Benjamin Greenwald wrote: >Greetings all, > >With the most recent kernel, every time my X server dies (reboot, explicit >kill, whatever) the kernel panics. Looks like some sort of VM bug. A >backtrace follows. This problem is easily and completely reproducible >(translate it happens every time) and it occurs with both my Xi Graphics X >server as well as the XSuSE XFCom_3DLabs server (I have a Fire GL 1000 Pro). > Same thing happens to me every time I do a shutdown -r now. A kernel from yesterday is fine. Manfred ============================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 22:26:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23158 for freebsd-current-outgoing; Thu, 22 Oct 1998 22:26:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23150 for ; Thu, 22 Oct 1998 22:26:38 -0700 (PDT) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA12629; Thu, 22 Oct 1998 22:27:10 -0700 (PDT) Message-Id: <199810230527.WAA12629@implode.root.com> To: Kris Kennaway cc: Benjamin Greenwald , freebsd-current@FreeBSD.ORG Subject: Re: VM bug triggered by X server death In-reply-to: Your message of "Fri, 23 Oct 1998 14:41:41 +0930." From: David Greenman Reply-To: dg@root.com Date: Thu, 22 Oct 1998 22:27:10 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Fri, 23 Oct 1998, Benjamin Greenwald wrote: > >> With the most recent kernel, every time my X server dies (reboot, explicit >> kill, whatever) the kernel panics. Looks like some sort of VM bug. A >> backtrace follows. This problem is easily and completely reproducible >> (translate it happens every time) and it occurs with both my Xi Graphics X >> server as well as the XSuSE XFCom_3DLabs server (I have a Fire GL 1000 Pro). > >I also get a panic in this case running a current kernel (ELF, and since >dg's recent changes in this area). Mine however dies with (from memory): > >vm_object_terminate: not freeing wired page; wire_count=1 That will be coming out in Ben's case as well, just before the panic. The problem was caused by two bugs, actually. Fixed in rev 1.131 of vm_object.c. Thanks for the bug reports. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 22:35:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23990 for freebsd-current-outgoing; Thu, 22 Oct 1998 22:35:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23985 for ; Thu, 22 Oct 1998 22:35:41 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.59.118]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA6249 for ; Fri, 23 Oct 1998 07:35:10 +0200 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 23 Oct 1998 07:38:19 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: make world stops Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, after doing a make clean and make world yesterday eve I got these errors again: -------------------------------------------------------------- >>> Rebuilding tools necessary to build the include files -------------------------------------------------------------- cc -O -pipe -I. -I/src/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/aout/src/src/tmp/usr/include -c error_table.c cc -O -pipe -I. -I/src/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/aout/src/src/tmp/usr/include -static -o compile_et compile_et.o error_table.o -ll ld: -ll: no match *** Error code 1 Stop. *** Error code 1 and then some more stops Hope somebody can provide a slight insight. make world worked sunday or monday, no changes were made in the set-up from that time. Regards, --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 22:50:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25541 for freebsd-current-outgoing; Thu, 22 Oct 1998 22:50:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25535 for ; Thu, 22 Oct 1998 22:50:49 -0700 (PDT) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA12963; Thu, 22 Oct 1998 22:51:31 -0700 (PDT) Message-Id: <199810230551.WAA12963@implode.root.com> To: Kris Kennaway cc: Benjamin Greenwald , freebsd-current@FreeBSD.ORG Subject: Re: VM bug triggered by X server death In-reply-to: Your message of "Thu, 22 Oct 1998 22:27:10 PDT." <199810230527.WAA12629@implode.root.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 22 Oct 1998 22:51:30 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >problem was caused by two bugs, actually. Fixed in rev 1.131 of vm_object.c. Oops, make that rev 1.132 of vm_object.c. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 22:59:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26066 for freebsd-current-outgoing; Thu, 22 Oct 1998 22:59:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26061 for ; Thu, 22 Oct 1998 22:59:21 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem01.masternet.it [194.184.65.11]) by www.giovannelli.it (8.8.8/8.8.5) with SMTP id HAA00255 for ; Fri, 23 Oct 1998 07:53:35 +0200 (MET DST) Message-Id: <199810230553.HAA00255@www.giovannelli.it> From: "Gianmarco Giovannelli" To: current@FreeBSD.ORG Date: Fri, 23 Oct 1998 08:01:48 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: make installworld fails... Reply-to: gmarco@giovannelli.it In-reply-to: <199810221112.NAA00509@www.giovannelli.it> X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >>> Installing legacy libraries > -------------------------------------------------------------- > cd /usr/src/lib; /usr/obj/elf/usr/src/tmp/usr/bin/make -B -DNOMAN -DNOINFO install > ===> csu/i386 > install -C -c -o root -g wheel -m 444 crt0.o c++rt0.o gcrt0.o scrt0.o sgcrt0.o /usr/lib/aout > install: crt0.o: No such file or directory > *** Error code 71 > > Stop. > *** Error code 1 > Ops... I didn't build aout world first .... sorry for the silly posting ... Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 23:04:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26415 for freebsd-current-outgoing; Thu, 22 Oct 1998 23:04:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26375 for ; Thu, 22 Oct 1998 23:03:47 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA16901; Fri, 23 Oct 1998 08:02:55 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810230602.IAA16901@gratis.grondar.za> To: "John Saunders" cc: "FreeBSD current" Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) In-Reply-To: Your message of " Fri, 23 Oct 1998 12:12:09 +1000." <002a01bdfe2a$89f55480$6cb611cb@saruman.scitec.com.au> References: <002a01bdfe2a$89f55480$6cb611cb@saruman.scitec.com.au> Date: Fri, 23 Oct 1998 08:02:54 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John Saunders" wrote: > How about changing passwd check for the existance of a magic > file such as /etc/create_md5_passwords. Just like adjkerntz > checks for the /etc/wall_cmos_clock file. This should do it... [snip] This will probably work, but I'd rather make a knob in the brand-new /etc/auth.conf. I'll do it this weekend. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 23:08:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26659 for freebsd-current-outgoing; Thu, 22 Oct 1998 23:08:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26649 for ; Thu, 22 Oct 1998 23:08:12 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA16924; Fri, 23 Oct 1998 08:06:45 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810230606.IAA16924@gratis.grondar.za> To: Peter Wemm cc: freebsd-current@FreeBSD.ORG Subject: Re: Begging to be asked (ELF Kernel) In-Reply-To: Your message of " Fri, 23 Oct 1998 11:02:11 +0800." <199810230302.LAA24981@spinner.netplex.com.au> References: <199810230302.LAA24981@spinner.netplex.com.au> Date: Fri, 23 Oct 1998 08:06:44 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > ldd is an a.out tool. Huh? [greenpeace] /usr/ports/emulators/linux_lib # file /usr/bin/perl /usr/bin/perl: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked, stripped [greenpeace] /usr/ports/emulators/linux_lib # ldd /usr/bin/perl /usr/bin/perl: libperl.so.3 => /usr/lib/libperl.so.3 (0x28052000) libm.so.2 => /usr/lib/libm.so.2 (0x280e2000) libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x280fc000) libc.so.3 => /usr/lib/libc.so.3 (0x28111000) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 23:12:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27178 for freebsd-current-outgoing; Thu, 22 Oct 1998 23:12:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27172 for ; Thu, 22 Oct 1998 23:12:19 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA16995; Fri, 23 Oct 1998 08:10:52 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810230610.IAA16995@gratis.grondar.za> To: Dmitry Khrustalev cc: freebsd-current@FreeBSD.ORG Subject: Re: perl5 modules version breakage in current In-Reply-To: Your message of " Thu, 22 Oct 1998 22:48:24 +0300." References: Date: Fri, 23 Oct 1998 08:10:51 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Khrustalev wrote: > > Some perl modules in the tree generate their version number like this: > > $VERSION = (qw$Revision$)[1]; > or > $VERSION = substr q$Revision$, 10; > or > $VERSION = sprintf("%d.%02d", q$Revision$ =~ /(\d+)\.(\d+)/); > > since cvs changes $Revision$ this breaks CPAN, use Module VERSION, etc. Drat. Ok - I'll look at it. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 23:17:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27818 for freebsd-current-outgoing; Thu, 22 Oct 1998 23:17:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27802 for ; Thu, 22 Oct 1998 23:17:22 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id XAA10310; Thu, 22 Oct 1998 23:16:51 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id XAA18616; Thu, 22 Oct 1998 23:16:50 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id XAA19968; Thu, 22 Oct 1998 23:16:49 -0700 (PDT) From: Don Lewis Message-Id: <199810230616.XAA19968@salsa.gv.tsc.tdk.com> Date: Thu, 22 Oct 1998 23:16:49 -0700 In-Reply-To: Julian Elischer "Soft-Updates aware fsck available." (Oct 20, 8:22pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Julian Elischer , current@FreeBSD.ORG, mckusick@McKusick.COM Subject: Re: Soft-Updates aware fsck available. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 20, 8:22pm, Julian Elischer wrote: } Subject: Soft-Updates aware fsck available. } Kirk has supplied a 'soft-updates aware' fsck. } It requires a small tweek to compile under FreeBSD } but that's all. } } I've made the shar file available at: } http://www.freebsd.org/~julian/ } (at the bottom of the page). I now think that inoinfo(orphan)->ino_state = DFOUND; propagate(); needs to happen in pass3() even if linkup() fails (because lost+found filled or whatever), otherwise we risk tossing away files because their parent directory could not be reconnected. This gives the administrator the option of cleaning out lost+found and rerunning fsck to reconnect more stuff, and comes closer to the behavior of the current version of fsck in the tree. I also worry that /* * If we are running with soft updates and we come * across unreferenced directories, we just leave * them in DSTATE which will cause them to be pitched * in pass 4. */ if (preen && resolved && usedsoftdep && state == DSTATE) { if (inp->i_dotdot >= ROOTINO) inoinfo(inp->i_dotdot)->ino_linkcnt++; continue; } might be too agressive. What happens if we lose a directory close to the root due to an bad block? I'd only toss the directory if it is empty, which appears to be the usual cruft left behind by a crash when softupdates is in use. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 22 23:33:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29121 for freebsd-current-outgoing; Thu, 22 Oct 1998 23:33:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from knecht.Sendmail.ORG (knecht.sendmail.org [209.31.233.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29116 for ; Thu, 22 Oct 1998 23:32:58 -0700 (PDT) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [209.31.233.178]) by knecht.Sendmail.ORG (8.9.1/8.9.1) with ESMTP id XAA02924; Thu, 22 Oct 1998 23:32:29 -0700 (PDT) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id WAA19582; Thu, 22 Oct 1998 22:40:40 -0700 (PDT) Message-Id: <199810230540.WAA19582@flamingo.McKusick.COM> To: Don Lewis Subject: Re: Soft-Updates aware fsck available. cc: Julian Elischer , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 22 Oct 1998 23:16:49 PDT." <199810230616.XAA19968@salsa.gv.tsc.tdk.com> Date: Thu, 22 Oct 1998 22:40:39 -0700 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Don Lewis Date: Thu, 22 Oct 1998 23:16:49 -0700 In-Reply-To: Julian Elischer "Soft-Updates aware fsck available." (Oct 20, 8:22pm) To: Julian Elischer , current@FreeBSD.ORG, mckusick@McKusick.COM Subject: Re: Soft-Updates aware fsck available. On Oct 20, 8:22pm, Julian Elischer wrote: } Subject: Soft-Updates aware fsck available. } Kirk has supplied a 'soft-updates aware' fsck. } It requires a small tweek to compile under FreeBSD } but that's all. } } I've made the shar file available at: } http://www.freebsd.org/~julian/ } (at the bottom of the page). I now think that inoinfo(orphan)->ino_state = DFOUND; propagate(); needs to happen in pass3() even if linkup() fails (because lost+found filled or whatever), otherwise we risk tossing away files because their parent directory could not be reconnected. This gives the administrator the option of cleaning out lost+found and rerunning fsck to reconnect more stuff, and comes closer to the behavior of the current version of fsck in the tree. I agree (in both cases). I also worry that /* * If we are running with soft updates and we come * across unreferenced directories, we just leave * them in DSTATE which will cause them to be pitched * in pass 4. */ if (preen && resolved && usedsoftdep && state == DSTATE) { if (inp->i_dotdot >= ROOTINO) inoinfo(inp->i_dotdot)->ino_linkcnt++; continue; } might be too agressive. What happens if we lose a directory close to the root due to an bad block? I'd only toss the directory if it is empty, which appears to be the usual cruft left behind by a crash when softupdates is in use. If there were a bad block, then `resolved' would not be true and we would not take this action. I added the resolved variable, so if we find something fishy in the first or second pass, we will back off on the aggressive tossing in later passes. If you remove a large file tree, then some of the subdirectories may not be completely cleaned out yet, but you still want to nuke them. So using empty as a criterion is likely to put a bunch of undesirable stuff in lost+found. Does this seem reasonable? Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 00:04:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01264 for freebsd-current-outgoing; Fri, 23 Oct 1998 00:04:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01259 for ; Fri, 23 Oct 1998 00:04:09 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA10583; Fri, 23 Oct 1998 00:03:38 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id AAA19361; Fri, 23 Oct 1998 00:03:36 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA20052; Fri, 23 Oct 1998 00:03:35 -0700 (PDT) From: Don Lewis Message-Id: <199810230703.AAA20052@salsa.gv.tsc.tdk.com> Date: Fri, 23 Oct 1998 00:03:34 -0700 In-Reply-To: Kirk McKusick "Re: Soft-Updates aware fsck available." (Oct 22, 10:40pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Kirk McKusick , Don Lewis Subject: Re: Soft-Updates aware fsck available. Cc: Julian Elischer , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 22, 10:40pm, Kirk McKusick wrote: } Subject: Re: Soft-Updates aware fsck available. } If there were a bad block, then `resolved' would not be true } and we would not take this action. I added the resolved variable, } so if we find something fishy in the first or second pass, we } will back off on the aggressive tossing in later passes. If you } remove a large file tree, then some of the subdirectories may not } be completely cleaned out yet, but you still want to nuke them. } So using empty as a criterion is likely to put a bunch of } undesirable stuff in lost+found. Does this seem reasonable? Ok, I feel somewhat better about this now, though autonuking has always bothered me. My big concern is that resolved might be cleared later on, and by then it would be too late ... Something that occurred to me in another thread where I was thinking that unreferenced empty directories should be cleared (the more conservative approach), is that unless you cleared the directories in the correct order, you could end up with links (usually "..") pointing to unallocated inodes if fsck were interrupted while it was cleaning. This would be bad because a subsequent fsck run could stumble over these dangling links and require manual intervention. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 01:29:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07093 for freebsd-current-outgoing; Fri, 23 Oct 1998 01:29:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07088 for ; Fri, 23 Oct 1998 01:29:42 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id BAA11199; Fri, 23 Oct 1998 01:29:04 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id BAA20690; Fri, 23 Oct 1998 01:29:03 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA20382; Fri, 23 Oct 1998 01:29:01 -0700 (PDT) From: Don Lewis Message-Id: <199810230829.BAA20382@salsa.gv.tsc.tdk.com> Date: Fri, 23 Oct 1998 01:29:01 -0700 In-Reply-To: Doug Rabson "Re: -current NFS problem" (Oct 20, 9:01am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Doug Rabson , Terry Lambert Subject: Re: -current NFS problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 20, 9:01am, Doug Rabson wrote: } Subject: Re: -current NFS problem } On Tue, 20 Oct 1998, Terry Lambert wrote: } > My main question would be: } > } > o Do you see any reason why nfsnode locking should be necessary? } } The last time I spoke to Rick about this, he said that the reason NFS } can't use a vnode lock is to prevent a server hang from causing a lock } cascade ending up with the root vnode being locked and the whole machine } wedged. I experimented for a while with a gross hack which only locked } regular files but it was too complicated and I ditched it. Hmn, as another gross hack, how about unlocking the parent directory before locking the child when crossing a mount point? You'd have to disallow operations at the mount point that want namei() to return with the parent locked, but this doesn't look like it would be much of a loss. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 01:30:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07301 for freebsd-current-outgoing; Fri, 23 Oct 1998 01:30:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07296 for ; Fri, 23 Oct 1998 01:30:44 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id DAA29701; Fri, 23 Oct 1998 03:30:18 -0500 (CDT) Received: from aridius-100.isdn.mke.execpc.com(169.207.66.227) by peak.mountin.net via smap (V1.3) id sma029696; Fri Oct 23 03:29:50 1998 Message-Id: <3.0.3.32.19981023032536.0075034c@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 23 Oct 1998 03:25:36 -0500 To: Doug White From: "Jeffrey J. Mountin" Subject: Re: 3.0 missing some docs? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.19981021141506.00f0b3e4@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:55 AM 10/22/98 -0700, Doug White wrote: >I'd have to install 3.0 on my -STABLE workstation to test this. It may be >that the message was hidden behind bootverbose since it doesn't mean >anything and there's nothing you can do about it. My workstation spits >out an IRQ 7 each time the serial port is closed. Wacky, eh? I have a >ASUS T2P4 board. Ah, very wacky since I've only seen this before on a T2P4 with both FBSD and BSDi _and_ neither had any com ports in the kernel _nor_ was it enabled in BIOS. There was a problem when the happened too. My recollection is dim and the fix forgotten. Taking the insanity plea, since it drove me bonkers trying to find and fix the problem. FWIW, they appear within 5-10 minutes after boot (ie reboot and walk away, come back hours later ???). Damn, just realized that moused is running for my recent interest in running X, but only moused was started (via rc.conf), nothing else except the basic deamons. Not 100% positive, but think they were happening before moused was enabled. The logs were cropped, but one entry falls before moused was added. Is this worth pursing? There were no problems (AFAIK) with the strays, but if this is a bug of some sort... Simple enough to boot the aout kernel w/o mouse and see. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 03:31:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14656 for freebsd-current-outgoing; Fri, 23 Oct 1998 03:31:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14648 for ; Fri, 23 Oct 1998 03:30:58 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id DAA11822; Fri, 23 Oct 1998 03:30:22 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id DAA22475; Fri, 23 Oct 1998 03:30:21 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id DAA20574; Fri, 23 Oct 1998 03:30:19 -0700 (PDT) From: Don Lewis Message-Id: <199810231030.DAA20574@salsa.gv.tsc.tdk.com> Date: Fri, 23 Oct 1998 03:30:18 -0700 In-Reply-To: Bruce Evans "Re: gnu/usr.bin/cc/cc_tools/Makefile bug? (was Re: filesystem safety and SCSI disk write caching)" (Oct 14, 6:05pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Bruce Evans , Don.Lewis@tsc.tdk.com Subject: Re: gnu/usr.bin/cc/cc_tools/Makefile bug? (was Re: filesystem safety and SCSI disk write caching) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 14, 6:05pm, Bruce Evans wrote: } Subject: Re: gnu/usr.bin/cc/cc_tools/Makefile bug? (was Re: filesystem saf } >} All rules that build multiple targets may have the same problem. Some } >} have been fixed by using .ORDER, but this is ugly , and it isn't necessary } >} unless the command[s] that build the files need to built them all together. } > } >Is it possible for make to determin that all the files will be built } >together? If so, then make could be fixed to avoid running these } >commands multiple times in the parallel case. } } No. Not without telling it using something like .ORDER. What if the commands to build the targets don't reference .TARGET, .PREFIX, and so on? Even .PREFIX should be OK if all the targets have the same prefix. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 03:31:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14679 for freebsd-current-outgoing; Fri, 23 Oct 1998 03:31:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14674 for ; Fri, 23 Oct 1998 03:31:47 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id DAA00506; Fri, 23 Oct 1998 03:30:42 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "John Saunders" cc: "FreeBSD current" Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) In-reply-to: Your message of "Fri, 23 Oct 1998 12:12:09 +1000." <002a01bdfe2a$89f55480$6cb611cb@saruman.scitec.com.au> Date: Fri, 23 Oct 1998 03:30:42 -0700 Message-ID: <503.909138642@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How about changing passwd check for the existance of a magic > file such as /etc/create_md5_passwords. Just like adjkerntz > checks for the /etc/wall_cmos_clock file. This should do it... Gross. What's wrong with just creating a new field in /etc/auth.conf? That's what it's there for, after all. I see absolutely no reason to create another file in /etc just for this purpose. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 05:41:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23864 for freebsd-current-outgoing; Fri, 23 Oct 1998 05:41:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23858 for ; Fri, 23 Oct 1998 05:41:30 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA31913; Fri, 23 Oct 1998 22:40:56 +1000 Date: Fri, 23 Oct 1998 22:40:56 +1000 From: Bruce Evans Message-Id: <199810231240.WAA31913@godzilla.zeta.org.au> To: bde@zeta.org.au, Don.Lewis@tsc.tdk.com Subject: Re: gnu/usr.bin/cc/cc_tools/Makefile bug? (was Re: filesystem safety and SCSI disk write caching) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >} >Is it possible for make to determin that all the files will be built >} >together? If so, then make could be fixed to avoid running these >} >commands multiple times in the parallel case. >} >} No. Not without telling it using something like .ORDER. > >What if the commands to build the targets don't reference .TARGET, .PREFIX, >and so on? Even .PREFIX should be OK if all the targets have the same >prefix. .TARGET only works if there is a single target, and .PREFIX only works properly in implicit rules (with a single target), so there is normally no problem when they are used. Otherwise, make doesn't handle multiple targets created by a single rule. I suppose `make' could handle cases where lexically identical rules are used to build multiple targets: --- all: foo bar foo bar: >foo >bar --- `make -j2' could try running the common rule non-concurrently to see if it updates foo and bar. `make' doesn't do this. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 06:55:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00441 for freebsd-current-outgoing; Fri, 23 Oct 1998 06:55:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA00435 for ; Fri, 23 Oct 1998 06:55:13 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 5989 invoked from network); 23 Oct 1998 13:54:41 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 23 Oct 1998 13:54:41 -0000 Date: Fri, 23 Oct 1998 08:54:40 -0500 (CDT) From: John Sconiers To: "David O'Brien" cc: slpalmer@email.com, freebsd-current@FreeBSD.ORG Subject: Re: Riva TNT / XF86 / FreeBSD In-Reply-To: <19981022162904.D16225@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm not implying that anyone here is not installing the patches correctly > > but on a 2.2.7 box the pathc worked. Since then he has went up to a > > -current snapshot and it still works. > > Would it be possible to put the Xserver you built up for download then? > I'll ask. JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 08:39:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10916 for freebsd-current-outgoing; Fri, 23 Oct 1998 08:39:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10907 for ; Fri, 23 Oct 1998 08:39:06 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id KAA19709; Fri, 23 Oct 1998 10:38:32 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <3630A2F7.3F7C7D5E@webwizard.org.mx> Date: Fri, 23 Oct 1998 10:38:31 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG CC: Mike Smith , Cory Kempf Subject: Re: Netscape 4.5 & ld-linux.so.2? References: <199810222058.NAA00837@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > When I make netscape 4.5 from the ports collection (or just > > downloading the it from netscape's web site), I get the following when > > I try to run: > > > > % netscape > > ELF interpreter /compat/linux/lib/ld-linux.so.2 not found > > zsh: abort netscape > > > > /compat/linux/lib contains a ld-linux.so.1, and a ld-linux.so.1.7.14, > > but no .2 version. Where does the missing version come from? > > > > This is on a -current from a few days ago. > > The linux_lib port hasn't been upgraded for glibc binaries yet. > Is anyone running this with an elf kernel? I have my doubts as how to load the linux_mod.o, that is if it is possible. Can an LKM be loaded from the new boot.config? Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 09:14:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15445 for freebsd-current-outgoing; Fri, 23 Oct 1998 09:14:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from miris.lcs.mit.edu (miris.lcs.mit.edu [18.111.0.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15440 for ; Fri, 23 Oct 1998 09:14:20 -0700 (PDT) (envelope-from beng@miris.lcs.mit.edu) Received: from miris.lcs.mit.edu (beng@localhost [127.0.0.1]) by miris.lcs.mit.edu (8.8.7/8.8.7) with ESMTP id MAA18156; Fri, 23 Oct 1998 12:13:19 -0400 (EDT) Message-Id: <199810231613.MAA18156@miris.lcs.mit.edu> To: dg@root.com cc: Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: Re: VM bug triggered by X server death In-reply-to: Your message of "Thu, 22 Oct 1998 22:51:30 PDT." <199810230551.WAA12963@implode.root.com> From: Benjamin Greenwald X-Sender: beng@lcs.mit.edu Date: Fri, 23 Oct 1998 12:13:19 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The fix did the trick. Thanks DG. -Ben > >problem was caused by two bugs, actually. Fixed in rev 1.131 of vm_object.c. > > Oops, make that rev 1.132 of vm_object.c. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 10:14:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21289 for freebsd-current-outgoing; Fri, 23 Oct 1998 10:14:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21284 for ; Fri, 23 Oct 1998 10:14:08 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA00487; Fri, 23 Oct 1998 10:13:32 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 23 Oct 1998 10:13:31 -0700 (PDT) From: Doug White To: "Jeffrey J. Mountin" cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 missing some docs? In-Reply-To: <3.0.3.32.19981023032536.0075034c@207.227.119.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Oct 1998, Jeffrey J. Mountin wrote: > At 08:55 AM 10/22/98 -0700, Doug White wrote: > >I'd have to install 3.0 on my -STABLE workstation to test this. It may be > >that the message was hidden behind bootverbose since it doesn't mean > >anything and there's nothing you can do about it. My workstation spits > >out an IRQ 7 each time the serial port is closed. Wacky, eh? I have a > >ASUS T2P4 board. > > Ah, very wacky since I've only seen this before on a T2P4 with both FBSD > and BSDi _and_ neither had any com ports in the kernel _nor_ was it enabled > in BIOS. You'll see it if your lpt port is in polled mode, like mine is. I discovered this tidbit the hard way with the qcam driver; every time I logged out of X the system would panic. I finally got a VT320 and ran a serial console and figured out what was going on. At first I thoguht the motherboard was bad and hd it replaced, and it did the same thing. > Is this worth pursing? There were no problems (AFAIK) with the strays, but > if this is a bug of some sort... It's a hardware-ism. IRQ 7 is the generic junk IRQ. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 10:27:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22450 for freebsd-current-outgoing; Fri, 23 Oct 1998 10:27:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22436 for ; Fri, 23 Oct 1998 10:27:12 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id MAA25952 for ; Fri, 23 Oct 1998 12:25:58 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <3630BC26.4049265C@webwizard.org.mx> Date: Fri, 23 Oct 1998 12:25:58 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: Netscape 4.5 & ld-linux.so.2? References: <199810222058.NAA00837@dingo.cdrom.com> <3630A2F7.3F7C7D5E@webwizard.org.mx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote: > Mike Smith wrote: > > > > When I make netscape 4.5 from the ports collection (or just > > > downloading the it from netscape's web site), I get the following when > > > I try to run: > > > > > > % netscape > > > ELF interpreter /compat/linux/lib/ld-linux.so.2 not found > > > zsh: abort netscape > > > > > > /compat/linux/lib contains a ld-linux.so.1, and a ld-linux.so.1.7.14, > > > but no .2 version. Where does the missing version come from? > > > > > > This is on a -current from a few days ago. > > > > The linux_lib port hasn't been upgraded for glibc binaries yet. > > > > Is anyone running this with an elf kernel? I have my doubts as how to load > the linux_mod.o, that is if it is possible. > > Can an LKM be loaded from the new boot.config? > > Thanks > > ed > Muy current status. Thanks to Zach Heilig from the multimedia list who gave me these tips. > [ make sure your system is post-3.0 release ] > # cd /sys/modules > # make obj > # make depend > # make > # make install > # kldload /modules/linux.ko > [ I don't think modules are built by default ] Exellent information, Zach. Thanks a lot. Everything built fine the module seemed to load (acording to kldstat ), so we are advancing. Netscape first doesn't find ELF interpreter /lib/ld-linux.so.1 not found and NOT ?? ELF interpreter /compat/linux/lib/ld-linux.so.2 not found as in the above example. I did a ln -s /usr/compat/linux/lib /lib and it tried to run but I got a Memory fault (core dumped) Back to the old drawing board :-), but this time with a pocket full of kld modules, Thanks a lot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 11:15:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26665 for freebsd-current-outgoing; Fri, 23 Oct 1998 11:15:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26653 for ; Fri, 23 Oct 1998 11:15:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00391; Fri, 23 Oct 1998 11:19:24 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810231819.LAA00391@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Edwin Culp cc: freebsd-current@FreeBSD.ORG, Mike Smith , Cory Kempf Subject: Re: Netscape 4.5 & ld-linux.so.2? In-reply-to: Your message of "Fri, 23 Oct 1998 10:38:31 CDT." <3630A2F7.3F7C7D5E@webwizard.org.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Oct 1998 11:19:24 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > When I make netscape 4.5 from the ports collection (or just > > > downloading the it from netscape's web site), I get the following when > > > I try to run: > > > > > > % netscape > > > ELF interpreter /compat/linux/lib/ld-linux.so.2 not found > > > zsh: abort netscape > > > > > > /compat/linux/lib contains a ld-linux.so.1, and a ld-linux.so.1.7.14, > > > but no .2 version. Where does the missing version come from? > > > > > > This is on a -current from a few days ago. > > > > The linux_lib port hasn't been upgraded for glibc binaries yet. > > > > Is anyone running this with an elf kernel? I have my doubts as how to load > the linux_mod.o, that is if it is possible. You would have to load linux_mod.ko, eg. 'kldload /modules/linux_mod.ko'. > Can an LKM be loaded from the new boot.config? No. LKMs only work with a.out kernels anyway. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 12:58:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04234 for freebsd-current-outgoing; Fri, 23 Oct 1998 12:58:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04226 for ; Fri, 23 Oct 1998 12:58:41 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id PAA20565 for ; Fri, 23 Oct 1998 15:57:53 -0400 (EDT) Date: Fri, 23 Oct 1998 15:57:53 -0400 (EDT) From: Brian Feldman To: current@FreeBSD.ORG Subject: Let's get if_plip.c to shut up. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, ifconfig -a generates lotsa LP:ioctl(0xc0286938), and I got it down to SIOCGIFMEDIA. Well, that shouldn't even be valid on plip, should it? Well, no! So handle that case. Diff follows. Cheers, Brian Feldman --- /usr/src/sys/dev/ppbus/if_plip.c Wed Oct 7 10:42:24 1998 +++ if_plip.c Fri Oct 23 15:52:54 1998 @@ -393,6 +393,13 @@ } break; + case SIOCGIFMEDIA: /* + * This should be an invalid case, so at least get + * the driver to SHUT UP ABOUT IT! Yay, no more + * LP:ioctl(0xc0286938)! + */ + return EINVAL; + default: lprintf("LP:ioctl(0x%lx)\n", cmd); return EINVAL; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 13:45:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08328 for freebsd-current-outgoing; Fri, 23 Oct 1998 13:45:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dewdrop2.mindspring.com (dewdrop2.mindspring.com [207.69.200.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08312 for ; Fri, 23 Oct 1998 13:45:44 -0700 (PDT) (envelope-from stevensl@mindspring.net) Received: from freelove.mindspring.net (freelove.mindspring.net [207.69.192.92]) by dewdrop2.mindspring.com (8.8.5/8.8.5) with SMTP id QAA23357 for ; Fri, 23 Oct 1998 16:45:05 -0400 (EDT) Date: Fri, 23 Oct 1998 16:51:19 -0400 (EDT) From: steven To: current@FreeBSD.ORG Subject: Re: 3.0-Current/3Com 509B ether problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Um, disable the ethernet card drivers you're not using? Some ether card > probes are destructive. Ican't say I've noticed the same thing on my > systems with ie and ep both turned on, it sees no ie0 but the ep0 at IRQ > 10 port 0x300 is detected properly. well i updated my src again, i disabled all unecessary probes. same thing.. my two last tries are turn off PNP (bad since it makes my tuner card and sound work so nicely) or get another card (not a good choice since it will have to be ISA). anyone have any other ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 13:54:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09131 for freebsd-current-outgoing; Fri, 23 Oct 1998 13:54:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09123 for ; Fri, 23 Oct 1998 13:54:30 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id PAA01513; Fri, 23 Oct 1998 15:54:03 -0500 (CDT) Received: from klinzhai-109.isdn.mke.execpc.com(169.207.65.237) by peak.mountin.net via smap (V1.3) id sma001511; Fri Oct 23 15:53:39 1998 Message-Id: <3.0.3.32.19981023154926.007002b0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 23 Oct 1998 15:49:26 -0500 To: Doug White From: "Jeffrey J. Mountin" Subject: Re: 3.0 missing some docs? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.19981023032536.0075034c@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:13 AM 10/23/98 -0700, Doug White wrote: >You'll see it if your lpt port is in polled mode, like mine is. I >discovered this tidbit the hard way with the qcam driver; every time I >logged out of X the system would panic. I finally got a VT320 and ran a >serial console and figured out what was going on. At first I thoguht the >motherboard was bad and hd it replaced, and it did the same thing. Er, why did I say com port. Must have been really tired. Sleep is a GoodThing. ;) The lpt is disabled and no support is compiled in. Before it's disabling, it is changed to "normal" mode, no ECP or EPP. Now that I'm awake, the problem I had was related to installing a new Adaptec 2940UW (1.5 years ago). Once installed, the system started generating stray IRQ7's and would panic. Swapped _everything_ out and disabling unused devices did in visual userconfig did nothing to help. Finally a BIOS update fixed the problem. >It's a hardware-ism. IRQ 7 is the generic junk IRQ. Why would changing to an elf kernel "fix" the strays? Nothing else has changed since the kernel went from aout -> elf. If it were a hardware-ism, as you say, this change should do nothing to eliminate the strays. Unless the new elf kernel ignores stray IRQ7's, because there are no drivers using that interrupt. The board is an older Asus TP4N using the FX chipset. Must be a common issue. I'll try a BIOS update and see if the old kernel still does this. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 14:17:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11302 for freebsd-current-outgoing; Fri, 23 Oct 1998 14:17:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from orthanc.kellogg.nwu.edu (orthanc.kellogg.nwu.edu [129.105.197.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11297 for ; Fri, 23 Oct 1998 14:17:18 -0700 (PDT) (envelope-from pcox@orthanc.kellogg.nwu.edu) Received: (from pcox@localhost) by orthanc.kellogg.nwu.edu (8.9.1/8.9.1) id QAA00420 for freebsd-current@FreeBSD.ORG; Fri, 23 Oct 1998 16:16:46 -0500 (CDT) (envelope-from pcox) Message-ID: <19981023161646.A366@kellogg.nwu.edu> Date: Fri, 23 Oct 1998 16:16:46 -0500 From: Peter Cox To: freebsd-current@FreeBSD.ORG Subject: 3c905 with -current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there. This is on a machine and kernel build from cvsup'ed sources the night before last. I've got a 3c905 card on the system (Dell Optiplex). Reading from the network is fine, but any attempts to write large volumes of data to the network are met with the following errors: Oct 23 16:01:33 orthanc /kernel: xl0: transmission error: 90 It slows down the writes to a literal crawl. Is this a known problem? Am I doing something wrong, or is it a bug in the network driver? Thanks, Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 15:22:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17160 for freebsd-current-outgoing; Fri, 23 Oct 1998 15:22:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17155 for ; Fri, 23 Oct 1998 15:22:04 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA02314 for ; Fri, 23 Oct 1998 15:21:33 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd002292; Fri Oct 23 15:21:24 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id PAA08852 for current@freebsd.org; Fri, 23 Oct 1998 15:21:23 -0700 (MST) From: Terry Lambert Message-Id: <199810232221.PAA08852@usr07.primenet.com> Subject: Interesting 3.0 bug To: current@FreeBSD.ORG Date: Fri, 23 Oct 1998 22:21:23 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is an interesting bug. Take the following: begin 644 example M Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17433 for freebsd-current-outgoing; Fri, 23 Oct 1998 15:25:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17425 for ; Fri, 23 Oct 1998 15:25:00 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA15941; Fri, 23 Oct 1998 15:24:28 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd015819; Fri Oct 23 15:24:14 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id PAA09033; Fri, 23 Oct 1998 15:24:13 -0700 (MST) From: Terry Lambert Message-Id: <199810232224.PAA09033@usr07.primenet.com> Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 23 Oct 1998 22:24:12 +0000 (GMT) Cc: john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG In-Reply-To: <503.909138642@time.cdrom.com> from "Jordan K. Hubbard" at Oct 23, 98 03:30:42 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > How about changing passwd check for the existance of a magic > > file such as /etc/create_md5_passwords. Just like adjkerntz > > checks for the /etc/wall_cmos_clock file. This should do it... > > Gross. What's wrong with just creating a new field in /etc/auth.conf? > That's what it's there for, after all. I see absolutely no reason to > create another file in /etc just for this purpose. Good thing to know that we've finally got that "proliferation of config files" problem under control... it's not resolved, but at least we're "controlling" it... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 15:27:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17592 for freebsd-current-outgoing; Fri, 23 Oct 1998 15:27:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17580 for ; Fri, 23 Oct 1998 15:27:27 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA04103; Fri, 23 Oct 1998 15:26:55 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd004058; Fri Oct 23 15:26:45 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id PAA09157; Fri, 23 Oct 1998 15:26:40 -0700 (MST) From: Terry Lambert Message-Id: <199810232226.PAA09157@usr07.primenet.com> Subject: Re: 3.0 missing some docs? To: dwhite@resnet.uoregon.edu (Doug White) Date: Fri, 23 Oct 1998 22:26:40 +0000 (GMT) Cc: jeff-ml@mountin.net, freebsd-current@FreeBSD.ORG In-Reply-To: from "Doug White" at Oct 23, 98 10:13:31 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is this worth pursing? There were no problems (AFAIK) with the strays, but > > if this is a bug of some sort... > > It's a hardware-ism. IRQ 7 is the generic junk IRQ. I was under the impression that we had registered default handlers for all IRQ's, and thus 7 was no longer the grabage bin unless there was a deassert race that indicates a real problem? You should ask Bruce Evans for confirmation. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 15:34:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18104 for freebsd-current-outgoing; Fri, 23 Oct 1998 15:34:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18099 for ; Fri, 23 Oct 1998 15:34:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01715; Fri, 23 Oct 1998 15:38:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810232238.PAA01715@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: dwhite@resnet.uoregon.edu (Doug White), jeff-ml@mountin.net, freebsd-current@FreeBSD.ORG Subject: Re: 3.0 missing some docs? In-reply-to: Your message of "Fri, 23 Oct 1998 22:26:40 -0000." <199810232226.PAA09157@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Oct 1998 15:38:01 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Is this worth pursing? There were no problems (AFAIK) with the strays, but > > > if this is a bug of some sort... > > > > It's a hardware-ism. IRQ 7 is the generic junk IRQ. > > I was under the impression that we had registered default handlers for > all IRQ's, and thus 7 was no longer the grabage bin unless there > was a deassert race that indicates a real problem? The use of 7 for stray interrupts is a hardware feature; it has nothing to do with having handlers registered or otherwise. (We must have a handler registered, as otherwise we wouldn't know it'd happened...). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 15:46:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19129 for freebsd-current-outgoing; Fri, 23 Oct 1998 15:46:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19124 for ; Fri, 23 Oct 1998 15:46:18 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id AAA06539; Sat, 24 Oct 1998 00:44:36 +0200 (CEST) To: Terry Lambert cc: dwhite@resnet.uoregon.edu (Doug White), jeff-ml@mountin.net, freebsd-current@FreeBSD.ORG Subject: Re: 3.0 missing some docs? In-reply-to: Your message of "Fri, 23 Oct 1998 22:26:40 -0000." <199810232226.PAA09157@usr07.primenet.com> Date: Sat, 24 Oct 1998 00:44:35 +0200 Message-ID: <6537.909182675@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199810232226.PAA09157@usr07.primenet.com>, Terry Lambert writes: >> > Is this worth pursing? There were no problems (AFAIK) with the strays, but >> > if this is a bug of some sort... >> >> It's a hardware-ism. IRQ 7 is the generic junk IRQ. > >I was under the impression that we had registered default handlers for >all IRQ's, and thus 7 was no longer the grabage bin unless there >was a deassert race that indicates a real problem? > >You should ask Bruce Evans for confirmation. IRQ is the i8259's garbage bin, regardless of config. If an IRQ is asserted too short for classification by the i8259 it becomes irq7. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 16:07:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20751 for freebsd-current-outgoing; Fri, 23 Oct 1998 16:07:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20744 for ; Fri, 23 Oct 1998 16:07:16 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id IAA01457; Sat, 24 Oct 1998 08:36:35 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id IAA08148; Sat, 24 Oct 1998 08:36:32 +0930 (CST) Message-ID: <19981024083632.N28824@freebie.lemis.com> Date: Sat, 24 Oct 1998 08:36:32 +0930 From: Greg Lehey To: Terry Lambert , current@FreeBSD.ORG Subject: Re: Interesting 3.0 bug References: <199810232221.PAA08852@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810232221.PAA08852@usr07.primenet.com>; from Terry Lambert on Fri, Oct 23, 1998 at 10:21:23PM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 23 October 1998 at 22:21:23 +0000, Terry Lambert wrote: > Here is an interesting bug. Take the following: > > > begin 644 example > M A9V1S9F=D#0IW92!F96%R(&1U<&QI8V%T92!D871A(0T* > ` > end > > And uudecode it to a file. > > Type: > > more example > > You should see: > > sdfgsdfgdsfgsdfgdsfgdsfg > sdfgsdfgsdfgsdfgdsfgdsfgd > we fear duplicate data! That's what I see. > But instead, you see: > > sdfgsdfgdsfgsdfgdsfgdsfg > sdfgsdfgsdfgsdfgdsfgdsfgd > we fear duplicate data! > ! No. > vi the file to see what's in it: > > sdfgsdfgdsfgsdfgdsfgdsfg^M > sdfgsdfgsdfgsdfgdsfgdsfgd^M > we fear duplicate data!^M No. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 16:19:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21733 for freebsd-current-outgoing; Fri, 23 Oct 1998 16:19:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA21727 for ; Fri, 23 Oct 1998 16:19:40 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <430914(3)>; Fri, 23 Oct 1998 16:19:00 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Fri, 23 Oct 1998 16:18:38 -0700 To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Interesting 3.0 bug In-reply-to: Your message of "Fri, 23 Oct 98 15:21:23 PDT." <199810232221.PAA08852@usr07.primenet.com> Date: Fri, 23 Oct 1998 16:18:32 PDT From: Bill Fenner Message-Id: <98Oct23.161838pdt.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199810232221.PAA08852@usr07.primenet.com> you write: >Here is an interesting bug. Looks like the problem described in PRs bin/961 and bin/7296. bin/7296 has a patch. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 17:13:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26070 for freebsd-current-outgoing; Fri, 23 Oct 1998 17:13:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26065 for ; Fri, 23 Oct 1998 17:13:53 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id UAA94912; Fri, 23 Oct 1998 20:14:08 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199810232221.PAA08852@usr07.primenet.com> Date: Fri, 23 Oct 1998 20:18:16 -0400 To: Terry Lambert , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Interesting 3.0 bug Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:21 PM +0000 10/23/98, Terry Lambert wrote: > Here is an interesting bug. Take the following: It is a long-standing bug in 'more'. I tripped over it recently, and submitted a patch for it. Someone messaged me that they were testing it some time ago (July?), so I had hoped that it would make it into 3.0 release. On the other hand, it is fixed on my system (and I haven't had the time to keep in sync with current), so I haven't been following its progress all that much... :-) (I was also going to submit a patch so 'more' behaves a bit better when hit with a control-c. maybe I'm doing something wrong, but it seems my stty settings are all screwed up if I happen to attention out of 'more'. This is pretty noticable for me, because I've been using control-c to get out of 'more' on other unix platforms for about ten years now...) --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 17:20:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26568 for freebsd-current-outgoing; Fri, 23 Oct 1998 17:20:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell3.ba.best.com (shell3.ba.best.com [206.184.139.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26560 for ; Fri, 23 Oct 1998 17:20:02 -0700 (PDT) (envelope-from schrade@schrade.com) Received: from localhost (schrade@localhost [127.0.0.1]) by shell3.ba.best.com (8.9.0/8.9.0/best.sh) with ESMTP id RAA16426; Fri, 23 Oct 1998 17:18:54 -0700 (PDT) Date: Fri, 23 Oct 1998 17:18:54 -0700 (PDT) From: Ken Krebs To: slpalmer@email.com cc: freebsd-current@FreeBSD.ORG Subject: Re: Riva TNT / XF86 / FreeBSD In-Reply-To: <9810221059415K.14741@www4.iname.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998 slpalmer@email.com wrote: >I've gotten Dave Schmenk's patches, and though they applied cleanly, >they did not build on my FreeBSD-current box... I've sent Dave Schmenk >e-mail, hoping to fix this. I will make the binary available once I've >got one ;-) I was able to successfully patch and compile the server. I actually let all of XFree86 3.3.2 compile just to get the server compiled, and then copied the server to my X11R6/bin dir manually. It ran just fine for me on a freshly installed 3.0-RELEASE PII 300 system with a Canopus SPECTRA 2500. Although I did run into that vm crash problem on exiting the server ;) Will have to cvsup and make a new kernel to get around that. Oh.. I had compiled the server on a non-ELF FreeBSD 3.0-current system so it ended up as an aout binary. It still ran fine, though. Here's the steps I had to do to make it work: # cd /usr/ports/x11/XFree86 # make patch # cd work # ln -s xc xc.org # patch slpalmer > ---- On Oct 22 "David O'Brien" wrote: >> > RIVA TNT based video card (I'm running the VGA16 server until it's >> > supported). >> >> I had a friend that had one of these. >> >> I emailed David Schmenk to see if they had a server >> for us. He has a Linux server and offered me the patches/src so I could >> make a FreeBSD one. >> >> My friend returned the card, so I didn't go thru with getting the src and >> making a FreeBSD server. But you should contact him if you are >> interested. >> -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) IRC: Schrade E-Mail: schrade@schrade.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 17:55:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28901 for freebsd-current-outgoing; Fri, 23 Oct 1998 17:55:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (limbo.rtfm.net [207.198.222.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28896 for ; Fri, 23 Oct 1998 17:55:39 -0700 (PDT) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.9.1/8.9.1) id UAA05427 for freebsd-current@FreeBSD.org; Fri, 23 Oct 1998 20:51:16 -0400 (EDT) (envelope-from nathan) Message-ID: <19981023205115.A5357@rtfm.net> Date: Fri, 23 Oct 1998 20:51:15 -0400 From: Nathan Dorfman To: freebsd-current@FreeBSD.ORG Subject: libmytinfo breaks vim-5.3 port, maybe others? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vim-5.3 (compiled from ports) won't run in -g (gvim) mode with libmytinfo. At first I thought it was vim breakage, or Motif/Athena or even X11 breakage. But read on: CPU states: 14.8% user, 0.0% nice, 84.0% system, 1.2% interrupt, 0.0% idle 5411 root 89 0 3692K 2960K RUN 0:33 92.19% 76.98% vim 243 nathan 2 0 12344K 4060K select 21:49 4.39% 4.39% XF86_SVGA After gdb vim 5411, it has this to say: (gdb) bt #0 0x283524da in tputs () #1 0x80a7146 in XtVaGetApplicationResources () #2 0x807bb81 in XtVaGetApplicationResources () #3 0x808c865 in XtVaGetApplicationResources () #4 #5 0x283524da in tputs () #6 0x80a7146 in XtVaGetApplicationResources () #7 0x80a7ab9 in XtVaGetApplicationResources () #8 0x806f84d in XtVaGetApplicationResources () #9 0x804b275 in XtVaGetApplicationResources () Anyway, I noticed something weird: libmytinfo.so.2 => /usr/lib/libmytinfo.so.2 (0x2834b000) According to find -exec grep, this library is not mentioned anywhere in the vim port or work dir. Are things being linked with it automagically for some reason? Anyway, moving libtmyinfo.so.2 to foo and rebuilding vim: built and ran fine. Anyone? Pilot error? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 18:17:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00933 for freebsd-current-outgoing; Fri, 23 Oct 1998 18:17:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00927 for ; Fri, 23 Oct 1998 18:17:44 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id SAA01142; Fri, 23 Oct 1998 18:17:11 -0700 (PDT) (envelope-from jdp) Message-Id: <199810240117.SAA01142@austin.polstra.com> To: jeff-ml@mountin.net Subject: Re: 3.0 missing some docs? In-Reply-To: <3.0.3.32.19981023154926.007002b0@207.227.119.2> References: <3.0.3.32.19981023032536.0075034c@207.227.119.2> <3.0.3.32.19981023154926.007002b0@207.227.119.2> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Fri, 23 Oct 1998 18:17:11 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3.0.3.32.19981023154926.007002b0@207.227.119.2>, Jeffrey J. Mountin wrote: > >It's a hardware-ism. IRQ 7 is the generic junk IRQ. > > Why would changing to an elf kernel "fix" the strays? Nothing else has > changed since the kernel went from aout -> elf. If it were a hardware-ism, > as you say, this change should do nothing to eliminate the strays. Unless > the new elf kernel ignores stray IRQ7's, because there are no drivers using > that interrupt. I wonder if the difference could be caused by the new bootloader. Have you tried booting an a.out kernel using the new boot code? It would be interesting to find out whether the IRQ 7s came back again. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 19:38:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06099 for freebsd-current-outgoing; Fri, 23 Oct 1998 19:38:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06094 for ; Fri, 23 Oct 1998 19:38:21 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA20100 for ; Sat, 24 Oct 1998 12:07:48 +0930 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA30610; Sat, 24 Oct 1998 12:07:47 +0930 Date: Sat, 24 Oct 1998 12:07:47 +0930 (CST) From: Kris Kennaway To: current@FreeBSD.ORG Subject: nestea v2 against freebsd 3.0-Release (fwd) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tested this against myself this morning and it panicked the machine - I had to run as root to hit the 127.0.0.1 target, but perhaps someone could confirm whether it works against remote machines? This is obviously not good to have amajor vulnerability in 3.0 known before it even ships out the door :-( Kris ---------- Forwarded message ---------- Date: Fri, 23 Oct 1998 09:41:23 +0200 From: Gilles Bruno To: freebsd-security@freebsd.org Subject: nestea v2 against freebsd 3.0-Release Hi everyone, we tested yesterday the old nestea v2 against a brand new 3.0-Release : it has prooved to be effective against it (the box rebooted - invalid page fault while in kernel mode). The same test against 2.2.[6,7]-Release didn't harm at all. Am I missing something ? some sysctl ? a special kernel config ? Let us know... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 21:49:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13992 for freebsd-current-outgoing; Fri, 23 Oct 1998 21:49:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13987 for ; Fri, 23 Oct 1998 21:49:49 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id VAA22922; Fri, 23 Oct 1998 21:49:18 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id VAA10754; Fri, 23 Oct 1998 21:49:16 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id VAA22669; Fri, 23 Oct 1998 21:49:15 -0700 (PDT) From: Don Lewis Message-Id: <199810240449.VAA22669@salsa.gv.tsc.tdk.com> Date: Fri, 23 Oct 1998 21:49:15 -0700 In-Reply-To: Julian Elischer "Soft-Updates aware fsck available." (Oct 20, 8:22pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Julian Elischer , current@FreeBSD.ORG Subject: Re: Soft-Updates aware fsck available. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 20, 8:22pm, Julian Elischer wrote: } Subject: Soft-Updates aware fsck available. } Kirk has supplied a 'soft-updates aware' fsck. } It requires a small tweek to compile under FreeBSD } but that's all. } I've made the shar file available at: } http://www.freebsd.org/~julian/ } (at the bottom of the page). Here's the 'tweak' that I'm using, along with a bug fix in case lost+found fills. --- fsck/inode.c.orig Fri Oct 23 20:09:43 1998 +++ fsck/inode.c Fri Oct 23 20:15:09 1998 @@ -520,6 +520,7 @@ register struct dinode *dp; register char *p; struct passwd *pw; + time_t t; char *ctime(); printf(" I=%lu ", ino); @@ -535,7 +536,8 @@ if (preen) printf("%s: ", cdevname); printf("SIZE=%qu ", dp->di_size); - p = ctime(&dp->di_mtime.tv_sec); + t = dp->di_mtime; + p = ctime(&t); printf("MTIME=%12.12s %4.4s ", &p[4], &p[20]); } @@ -617,8 +619,9 @@ } dp->di_mode = type; dp->di_flags = 0; - (void)time(&dp->di_atime.tv_sec); + dp->di_atime = time(NULL); dp->di_mtime = dp->di_ctime = dp->di_atime; + dp->di_mtimensec = dp->di_ctimensec = dp->di_atimensec = 0; dp->di_size = sblock.fs_fsize; dp->di_blocks = btodb(sblock.fs_fsize); n_files++; --- fsck/pass3.c.orig Fri Oct 23 20:09:56 1998 +++ fsck/pass3.c Fri Oct 23 03:00:33 1998 @@ -84,9 +84,9 @@ if (linkup(orphan, inp->i_dotdot, NULL)) { inp->i_parent = inp->i_dotdot = lfdir; inoinfo(lfdir)->ino_linkcnt--; - inoinfo(orphan)->ino_state = DFOUND; - propagate(); } + inoinfo(orphan)->ino_state = DFOUND; + propagate(); continue; } pfatal("ORPHANED DIRECTORY LOOP DETECTED I=%lu", orphan); @@ -106,8 +106,8 @@ inoinfo(orphan)->ino_linkcnt++; inp->i_parent = inp->i_dotdot = lfdir; inoinfo(lfdir)->ino_linkcnt--; - inoinfo(orphan)->ino_state = DFOUND; - propagate(); } + inoinfo(orphan)->ino_state = DFOUND; + propagate(); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 23 21:55:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14687 for freebsd-current-outgoing; Fri, 23 Oct 1998 21:55:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14682 for ; Fri, 23 Oct 1998 21:55:23 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id VAA22956; Fri, 23 Oct 1998 21:54:50 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id VAA10775; Fri, 23 Oct 1998 21:54:49 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id VAA22687; Fri, 23 Oct 1998 21:54:47 -0700 (PDT) From: Don Lewis Message-Id: <199810240454.VAA22687@salsa.gv.tsc.tdk.com> Date: Fri, 23 Oct 1998 21:54:47 -0700 In-Reply-To: Don Lewis "Re: Soft-Updates aware fsck available." (Oct 23, 9:49pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Don Lewis , Julian Elischer , current@FreeBSD.ORG Subject: Re: Soft-Updates aware fsck available. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 23, 9:49pm, Don Lewis wrote: } Subject: Re: Soft-Updates aware fsck available. } On Oct 20, 8:22pm, Julian Elischer wrote: } } Subject: Soft-Updates aware fsck available. } } Kirk has supplied a 'soft-updates aware' fsck. } } It requires a small tweek to compile under FreeBSD } } but that's all. } } } I've made the shar file available at: } } http://www.freebsd.org/~julian/ } } (at the bottom of the page). } } Here's the 'tweak' that I'm using, along with a bug fix in case lost+found } fills. [ deleted ] Oh, and the fsdb patch in bin/8427 will need to be committed when this new version of fsck is integrated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 00:16:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22293 for freebsd-current-outgoing; Sat, 24 Oct 1998 00:16:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22288 for ; Sat, 24 Oct 1998 00:16:04 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA23552; Sat, 24 Oct 1998 00:15:27 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id AAA12970; Sat, 24 Oct 1998 00:15:25 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA23010; Sat, 24 Oct 1998 00:15:24 -0700 (PDT) From: Don Lewis Message-Id: <199810240715.AAA23010@salsa.gv.tsc.tdk.com> Date: Sat, 24 Oct 1998 00:15:22 -0700 In-Reply-To: Kris Kennaway "nestea v2 against freebsd 3.0-Release (fwd)" (Oct 24, 12:07pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Kris Kennaway , current@FreeBSD.ORG Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 24, 12:07pm, Kris Kennaway wrote: } Subject: nestea v2 against freebsd 3.0-Release (fwd) } I tested this against myself this morning and it panicked the machine - I had } to run as root to hit the 127.0.0.1 target, but perhaps someone could confirm } whether it works against remote machines? Huh? The copy of nestea2 that I've got (from a bugtraq message) won't even run under 3.0. The last sendto() fails with errno == EINVAL. If I bypass the sanity check in rip_output() that looks for the bogus length in the IP header, then the program runs but I don't see any crashes. All that happens is that the equivalent sanity check in ip_input() detects the problem and increments ipstat.ips_tooshort. I can see this in netstat -s ip: 6814 total packets received 0 bad header checksums ---> 2000 with size smaller than minimum ---> 2000 with data size < data length To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 01:04:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24407 for freebsd-current-outgoing; Sat, 24 Oct 1998 01:04:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24402 for ; Sat, 24 Oct 1998 01:04:14 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id BAA03815; Sat, 24 Oct 1998 01:03:33 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Terry Lambert cc: john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) In-reply-to: Your message of "Fri, 23 Oct 1998 22:24:12 -0000." <199810232224.PAA09033@usr07.primenet.com> Date: Sat, 24 Oct 1998 01:03:33 -0700 Message-ID: <3812.909216213@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Good thing to know that we've finally got that "proliferation of > config files" problem under control... it's not resolved, but at > least we're "controlling" it... "ok", I "guess" I understand what "you" are trying to say here. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 01:45:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26157 for freebsd-current-outgoing; Sat, 24 Oct 1998 01:45:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26151 for ; Sat, 24 Oct 1998 01:45:02 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from photon (photon [129.127.36.4]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id SAA20189; Sat, 24 Oct 1998 18:14:28 +0930 (CST) Received: from localhost by photon; (5.65/1.1.8.2/04Aug95-0645PM) id AA00793; Sat, 24 Oct 1998 18:14:25 +0930 Date: Sat, 24 Oct 1998 18:14:23 +0930 (CST) From: Kris Kennaway To: Don Lewis Cc: current@FreeBSD.ORG Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) In-Reply-To: <199810240715.AAA23010@salsa.gv.tsc.tdk.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Oct 1998, Don Lewis wrote: > On Oct 24, 12:07pm, Kris Kennaway wrote: > } Subject: nestea v2 against freebsd 3.0-Release (fwd) > } I tested this against myself this morning and it panicked the machine - I had > } to run as root to hit the 127.0.0.1 target, but perhaps someone could confirm > } whether it works against remote machines? > > Huh? The copy of nestea2 that I've got (from a bugtraq message) won't even > run under 3.0. The last sendto() fails with errno == EINVAL. If I bypass > the sanity check in rip_output() that looks for the bogus length in the IP > header, then the program runs but I don't see any crashes. All that happens > is that the equivalent sanity check in ip_input() detects the problem and > increments ipstat.ips_tooshort. I can see this in netstat -s rootshell.com has a .tgz containing a linux compiled binary - that's the one I ran [1]. Perhaps it was the linuxulator which crashed me, instead of what the program itself did. Kris [1] This might not have been so bright :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 01:57:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26614 for freebsd-current-outgoing; Sat, 24 Oct 1998 01:57:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26609 for ; Sat, 24 Oct 1998 01:57:32 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id BAA24215; Sat, 24 Oct 1998 01:56:55 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id BAA14383; Sat, 24 Oct 1998 01:56:54 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA23322; Sat, 24 Oct 1998 01:56:53 -0700 (PDT) From: Don Lewis Message-Id: <199810240856.BAA23322@salsa.gv.tsc.tdk.com> Date: Sat, 24 Oct 1998 01:56:53 -0700 In-Reply-To: Kris Kennaway "Re: nestea v2 against freebsd 3.0-Release (fwd)" (Oct 24, 6:14pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Kris Kennaway , Don Lewis Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 24, 6:14pm, Kris Kennaway wrote: } Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) } rootshell.com has a .tgz containing a linux compiled binary - that's the one I } ran [1]. Perhaps it was the linuxulator which crashed me, instead of what the } program itself did. Could be. Can you get a stack trace, either with DDB, or with a crash dump and gdb? } [1] This might not have been so bright :-) Hmn, yes. Running binaries of unknown origin as root. I wonder what backdoors it installed ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 05:37:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08828 for freebsd-current-outgoing; Sat, 24 Oct 1998 05:37:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08823 for ; Sat, 24 Oct 1998 05:37:48 -0700 (PDT) (envelope-from green@janus.syracuse.net) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id IAA23879 for ; Sat, 24 Oct 1998 08:37:13 -0400 (EDT) Date: Sat, 24 Oct 1998 08:37:13 -0400 (EDT) From: Brian Feldman To: current@FreeBSD.ORG Subject: kern_linker.c typoes Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1197355383-909232633=:23877" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1197355383-909232633=:23877 Content-Type: TEXT/PLAIN; charset=US-ASCII I think the patch is self-explanatory. Cheers, Brian Feldman P.S.: [File /home2/green/kl.diff attached as type TEXT/PLAIN] So if it doesn't come out as such, it's time to blame the pine people. --0-1197355383-909232633=:23877 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="kl.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="kl.diff" LS0tIC91c3Ivc3JjL3N5cy9rZXJuL2tlcm5fbGlua2VyLmMgICAgIFRodSBP Y3QgMTUgMjM6NDU6MjMgMTk5OA0KKysrIC90bXAva2Vybl9saW5rZXIuYyAg U2F0IE9jdCAyNCAwMDoyOToxOCAxOTk4DQpAQCAtNzAyLDE0ICs3MDIsMTQg QEANCiAgICAgICAgbW9kbmFtZSA9IChjaGFyICopcHJlbG9hZF9zZWFyY2hf aW5mbyhtb2RwdHIsIE1PRElORk9fTkFNRSk7DQogICAgICAgIG1vZHR5cGUg PSAoY2hhciAqKXByZWxvYWRfc2VhcmNoX2luZm8obW9kcHRyLCBNT0RJTkZP X1RZUEUpOw0KICAgICAgICBpZiAobW9kbmFtZSA9PSBOVUxMKSB7DQotICAg ICAgICAgICBwcmludGYoIlByZWxvYWRlZCBtb2R1bGUgYXQgMHglcCBkb2Vz IG5vdCBoYXZlIGEgbmFtZSFcbiIsIG1vZHB0cik7DQorICAgICAgICAgICBw cmludGYoIlByZWxvYWRlZCBtb2R1bGUgYXQgJXAgZG9lcyBub3QgaGF2ZSBh IG5hbWUhXG4iLCBtb2RwdHIpOw0KICAgICAgICAgICAgY29udGludWU7DQog ICAgICAgIH0NCiAgICAgICAgaWYgKG1vZHR5cGUgPT0gTlVMTCkgew0KLSAg ICAgICAgICAgcHJpbnRmKCJQcmVsb2FkZWQgbW9kdWxlIGF0IDB4JXAgZG9l cyBub3QgaGF2ZSBhIHR5cGUhXG4iLCBtb2RwdHIpOw0KKyAgICAgICAgICAg cHJpbnRmKCJQcmVsb2FkZWQgbW9kdWxlIGF0ICVwIGRvZXMgbm90IGhhdmUg YSB0eXBlIVxuIiwgbW9kcHRyKTsNCiAgICAgICAgICAgIGNvbnRpbnVlOw0K ICAgICAgICB9DQotICAgICAgIHByaW50ZigiUHJlbG9hZGVkICVzIFwiJXNc IiBhdCAweCVwLlxuIiwgbW9kdHlwZSwgbW9kbmFtZSwgbW9kcHRyKTsNCisg ICAgICAgcHJpbnRmKCJQcmVsb2FkZWQgJXMgXCIlc1wiIGF0ICVwLlxuIiwg bW9kdHlwZSwgbW9kbmFtZSwgbW9kcHRyKTsNCiAgICAgICAgbGYgPSBsaW5r ZXJfZmluZF9maWxlX2J5X25hbWUobW9kbmFtZSk7DQogICAgICAgIGlmIChs Zikgew0KICAgICAgICAgICAgbGYtPnVzZXJyZWZzKys7DQo= --0-1197355383-909232633=:23877-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 06:38:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12340 for freebsd-current-outgoing; Sat, 24 Oct 1998 06:38:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from marvin.spacequest.hs (in26.fto.de [193.197.153.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12327 for ; Sat, 24 Oct 1998 06:38:37 -0700 (PDT) (envelope-from hschaefer@fto.de) Received: from daneel.spacequest.hs (daneel.spacequest.hs [192.168.0.98]) by marvin.spacequest.hs (8.8.8/8.8.7) with ESMTP id PAA25878 for ; Sat, 24 Oct 1998 15:38:23 +0200 (CEST) (envelope-from hschaefer@fto.de) Date: Sat, 24 Oct 1998 15:37:42 +0200 (CEST) From: Heiko Schaefer X-Sender: heiko@daneel.spacequest.hs To: freebsd-current@FreeBSD.ORG Subject: Problem with SCSI Harddisk Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, after checking the archives of this list (as well as freebsd-scsi), i finally decided to post a problem that i have here. i hope this is the right place and way to search for advice (and/or help). I am using FreeBSD 3.0-CURRENT (of today), and have a problem with one of my scsi-harddisks. /var/log/messages says: Oct 24 10:00:56 daneel /kernel: (da3:ahc0:0:3:0): SCB 0xe1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Oct 24 10:00:56 daneel /kernel: SEQADDR == 0xb Oct 24 10:00:56 daneel /kernel: SSTAT1 == 0xa Oct 24 10:00:56 daneel /kernel: (da3:ahc0:0:3:0): Queuing a BDR SCB Oct 24 10:00:56 daneel /kernel: (da3:ahc0:0:3:0): Bus Device Reset Message Sent Oct 24 10:00:56 daneel /kernel: (da3:ahc0:0:3:0): no longer in timeout, status = 34b Oct 24 10:00:56 daneel /kernel: ahc0: Bus Device Reset on A:3. 64 SCBs aborted Oct 24 10:00:56 daneel /kernel: (da3:ahc0:0:3:0): tagged openings now 64 this message is then repeated for zillions of times (exactly once every 60 seconds), once it has occured once (it occurs for the first time, when the harddisk is used a bit more heavily). eventually the whole system hangs (responds to ping, but not to telnet or anything similar, although the filesystem on the harddisk contains no part of the system, just data of a samba-fileserver). first i thought that my harddisk might be dieing, but then i read that other ppl had similar problems when switching to the CAM driver (when using 'strange' harddisks, as far as i understood). i have used this harddisk for quite some time without any problems that i could notice under 2.2-STABLE. the problem seems to have started exactly when updating my system to 3.0-CURRENT. (by the way is there a 3.0-STABLE or will there be sometime soon ?!) here is the output of dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #4: Sat Oct 24 13:14:43 CEST 1998 heiko@daneel.spacequest.hs:/usr/src/sys/compile/DANEEL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 166587138 Hz CPU: Pentium/P55C (166.59-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 63082496 (61604K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 xl0: <3Com 3c900 Etherlink XL 10BaseT Combo> rev 0x00 int a irq 12 on pci0.10.0 xl0: Ethernet address: 00:10:4b:4e:7d:4d xl0: selecting BNC port, half duplex ahc0: rev 0x00 int a irq 10 on pci0.12.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround Waiting 15 seconds for SCSI devices to settle changing root device to da0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 1034MB (2118144 512 byte sectors: 255H 63S/T 131C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da2: 2014MB (4124736 512 byte sectors: 255H 63S/T 256C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI2 device da3: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da3: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 08:13:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18018 for freebsd-current-outgoing; Sat, 24 Oct 1998 08:13:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18011 for ; Sat, 24 Oct 1998 08:13:41 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id AAA17644; Sun, 25 Oct 1998 00:43:06 +0930 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA01871; Sun, 25 Oct 1998 00:43:05 +0930 Date: Sun, 25 Oct 1998 00:43:05 +0930 (CST) From: Kris Kennaway To: Brian Somers Cc: current@FreeBSD.ORG Subject: Re: Improper sharing of modem bandwidth In-Reply-To: <199810211031.LAA01095@woof.lan.awfulhak.org> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998, Brian Somers wrote: > > If you're interested, you could try doing a ``s/20/100/'' in bundle.c > > in src/usr.sbin/ppp and rebuilding & installing ppp. Perhaps the > > ``20'' is a bit light. Making the suggested change from 20 to 100 in bundle.c didnt seem to have a noticeable effect; to recap my problem, if I start up a binary transfer which runs at full throttle (~1.65k/s on my 14.4k modem, usually), then it starves all other network connections to the point of exclusion. I've done some more checking and perhaps some of this will be helpful. If I ^Z the ftp (or http, or whatever the binary transfer is that's hogging the modem) process, the modem continues to transfer for ~11 seconds (~18k) before coming to a stop; immediately thereafter my other network sessions (telnet, ping, etc) "unfreeze" and I get normal performance from them. Restarting the FTP transfer immediately excludes everything else again. If I start a ping of a host which is ~400ms away at normal usage, restarting the FTP transfer will cause no further packets to be returned. Doing a 'tcpdump ip and not host ' where is the host I'm downloading from shows the icmp echo requests going out, but nothing at all coming in. Similarly, DNS requests to the machine on the other side of the modem link go out, but nothing comes back. In the 10 minutes I've been watching this, I've not seen a single packet come back in response to the DNS queries and other stuff I have running - in the meantime, the FTP transfer continues to run at full speed. It seems I cannot get a single packet in other than from the FTP data stream. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 08:56:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20219 for freebsd-current-outgoing; Sat, 24 Oct 1998 08:56:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20211 for ; Sat, 24 Oct 1998 08:56:05 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id BAA18754; Sun, 25 Oct 1998 01:25:31 +0930 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA00791; Sun, 25 Oct 1998 01:25:30 +0930 Date: Sun, 25 Oct 1998 01:25:30 +0930 (CST) From: Kris Kennaway To: Don Lewis Cc: current@FreeBSD.ORG Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) In-Reply-To: <199810240856.BAA23322@salsa.gv.tsc.tdk.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Oct 1998, Don Lewis wrote: > } rootshell.com has a .tgz containing a linux compiled binary - that's the one I > } ran [1]. Perhaps it was the linuxulator which crashed me, instead of what the > } program itself did. > > Could be. Can you get a stack trace, either with DDB, or with a crash dump > and gdb? GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 2801664 initial pcb at 257b1c panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x13 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0180ebc stack pointer = 0x10:0xf2c7dd3c frame pointer = 0x10:0xf2c7dd60 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 353 (nestea2) interrupt mask = panic: from debugger Fatal trap 12: page fault while in kernel mode fault virtual address = 0x13 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0180ebc stack pointer = 0x10:0xf2c7dd3c frame pointer = 0x10:0xf2c7dd60 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 353 (nestea2) interrupt mask = Fatal trap 12: page fault while in kernel mode fault virtual address = 0x13 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0180ebc stack pointer = 0x10:0xf2c7dd3c frame pointer = 0x10:0xf2c7dd60 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 353 (nestea2) interrupt mask = panic: from debugger dumping to dev 30001, offset 39104 dump 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:268 268 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:268 #1 0xf012f5e8 in at_shutdown (function=0xf0227772 , arg=0xf2c7dc34, queue=-267277140) at ../../kern/kern_shutdown.c:430 #2 0xf011acfd in db_panic (addr=-266858820, have_addr=0, count=-1, modif=0xf2c7dbbc "") at ../../ddb/db_command.c:432 #3 0xf011acac in db_command (last_cmdp=0xf0240c34, cmd_table=0xf0240a94, aux_cmd_tablep=0xf02550b4) at ../../ddb/db_command.c:332 #4 0xf011ad62 in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf011d4f3 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #6 0xf01e545d in kdb_trap (type=12, code=0, regs=0xf2c7dd00) at ../../i386/i386/db_interface.c:157 #7 0xf01f13eb in trap_fatal (frame=0xf2c7dd00) at ../../i386/i386/trap.c:874 #8 0xf01f10e4 in trap_pfault (frame=0xf2c7dd00, usermode=0) at ../../i386/i386/trap.c:772 #9 0xf01f0d27 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -263534592, tf_esi = -263533804, tf_ebp = -221782688, tf_isp = -221782744, tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -266858820, tf_cs = 8, tf_eflags = 66118, tf_esp = -263533804, tf_ss = -266075918}) at ../../i386/i386/trap.c:396 #10 0xf0180ebc in ip_reass (m=0xf04ac800, fp=0xf04acb14, where=0xf025bfc8) at ../../netinet/ip_input.c:802 #11 0xf0180c3f in ip_input (m=0xf04ac800) at ../../netinet/ip_input.c:585 #12 0xf0181bdb in ipintr () at ../../netinet/ip_input.c:669 #13 0xf01e72c9 in swi_net_next () #14 0xf0148c40 in sendit (p=0xf2c69880, s=3, mp=0xf2c7debc, flags=0) at ../../kern/uipc_syscalls.c:484 #15 0xf0148e8b in sendmsg (p=0xf2c69880, uap=0xf2c7defc) at ../../kern/uipc_syscalls.c:632 #16 0xf0222a5b in linux_sendto_hdrincl (p=0xf2c69880, bsd_args=0xf2c7df1c) at ../../i386/linux/linux_socket.c:245 #17 0xf0223435 in linux_socketcall (p=0xf2c69880, args=0xf2c7df84) at ../../i386/linux/linux_socket.c:624 #18 0xf01f15f7 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272639092, tf_esi = 0, tf_ebp = 16, tf_isp = -221782060, tf_ebx = 11, tf_edx = 11, tf_ecx = -272639160, tf_eax = 102, tf_trapno = 12, tf_err = 2, tf_eip = 671593638, tf_cs = 31, tf_eflags = 534, tf_esp = -272639180, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #19 0xf01e5dec in Xint0x80_syscall () Cannot access memory at address 0x10. (kgdb) quit > } [1] This might not have been so bright :-) > > Hmn, yes. Running binaries of unknown origin as root. I wonder what > backdoors it installed ... Would be interesting if it installed some linux backdoor and the emulator emulated it enough to work :-) I'm not all that worried in this case, though Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 09:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20874 for freebsd-current-outgoing; Sat, 24 Oct 1998 09:06:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20868 for ; Sat, 24 Oct 1998 09:06:34 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id RAA13225; Sat, 24 Oct 1998 17:05:48 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 24 Oct 1998 17:03:42 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19981024083632.N28824@freebie.lemis.com> References: <199810232221.PAA08852@usr07.primenet.com>; from Terry Lambert on Fri, Oct 23, 1998 at 10:21:23PM +0000 <199810232221.PAA08852@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 24 Oct 1998 17:03:43 +0000 To: Greg Lehey , Terry Lambert From: Bob Bishop Subject: Re: Interesting 3.0 bug Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, FWIW I get the same result as Terry both on 2.2.5R and 3.0-CURRENT. I wonder if it's a TERM thang? vt100 here At 8:36 am +0930 24/10/98, Greg Lehey wrote: >On Friday, 23 October 1998 at 22:21:23 +0000, Terry Lambert wrote: >> Here is an interesting bug. Take the following: >> >> >> begin 644 example >> M> A9V1S9F=D#0IW92!F96%R(&1U<&QI8V%T92!D871A(0T* >> ` >> end >> >> And uudecode it to a file. >> >> Type: >> >> more example >> >> You should see: >> >> sdfgsdfgdsfgsdfgdsfgdsfg >> sdfgsdfgsdfgsdfgdsfgdsfgd >> we fear duplicate data! > >That's what I see. > >> But instead, you see: >> >> sdfgsdfgdsfgsdfgdsfgdsfg >> sdfgsdfgsdfgsdfgdsfgdsfgd >> we fear duplicate data! >> ! > >No. > >> vi the file to see what's in it: >> >> sdfgsdfgdsfgsdfgdsfgdsfg^M >> sdfgsdfgsdfgsdfgdsfgdsfgd^M >> we fear duplicate data!^M > >No. > >Greg >-- >See complete headers for address, home page and phone numbers >finger grog@lemis.com for PGP public key > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 10:45:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26329 for freebsd-current-outgoing; Sat, 24 Oct 1998 10:45:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from blondie.ottawa.cc (blondie.ottawa.cc [209.112.49.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26324 for ; Sat, 24 Oct 1998 10:45:35 -0700 (PDT) (envelope-from mat@blondie.ottawa.cc) Received: from localhost (mat@localhost) by blondie.ottawa.cc (8.9.1/8.9.1) with ESMTP id NAA17619 for ; Sat, 24 Oct 1998 13:47:12 GMT (envelope-from mat@blondie.ottawa.cc) Date: Sat, 24 Oct 1998 13:47:11 +0000 (GMT) From: User MAT To: freebsd-current@FreeBSD.ORG Subject: How To Fixup A New Install -- Trivial Importance Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I remember seeing some messages about the boot loader but the didn't seem to apply here. Preamble: We just got a cable modem in my apartment and I convinced my roomate to free up a drive and install FreeBSD 3.0-REALEASE. We natd my machine and installed through it. I was very impressed that this worked so easily (you have to run the Windows Cable-Modem software first to get the IP/gateway/DNS via DHCP, once you have theses values, the cable-modem doesn't care). Three Questions : 1: He installed on a second drive. When he boots he gets F1: ??? (or something like this) but no indication of what key to push to get to drive 2. (On the secondary IDE). Mine says F3: Disk 2 (ok, maybe not exactly and my drives on channel one). Can this be fixed/changed? 2: Also his wont boot unless you explicitly type 1:wd(2,a)kernel I was under the impression that it stored this information. 3: Final question about my machine, Why does xfree86 keep disapearing from my /var/db/pkg directory. This stops me from doing package install from /stand/sysintall. All in all, 3.0 works great (including x) and is a dream to install over a cable modem (Roger@home if you want to know). Mat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 11:09:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28086 for freebsd-current-outgoing; Sat, 24 Oct 1998 11:09:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28081 for ; Sat, 24 Oct 1998 11:09:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA05142; Sat, 24 Oct 1998 11:13:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810241813.LAA05142@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: User MAT cc: freebsd-current@FreeBSD.ORG Subject: Re: How To Fixup A New Install -- Trivial Importance In-reply-to: Your message of "Sat, 24 Oct 1998 13:47:11 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 11:13:29 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Three Questions : > > 1: He installed on a second drive. When he boots he gets > F1: ??? (or something like this) > but no indication of what key to push to get to drive 2. (On the > secondary IDE). Mine says F3: Disk 2 (ok, maybe not exactly and my drives > on channel one). Can this be fixed/changed? You might need to get hold of the 'booteasy' tool from ftp.freebsd.org/pub/FreeBSD/tools and install it. You can use a different bootmanager (eg. NT, System Commander, OS-BS) instead if you prefer. We were experimenting with a new bootmanager that properly handles disks > 1024 cylinders, but it needs a little more testing; this was fixed in a subsequent rebuild where we reverted to booteasy. On the other hand, if your friend has an odd number of disks in his system (3, 5 etc) then this is a known bug in booteasy. > 2: Also his wont boot unless you explicitly type 1:wd(2,a)kernel I was > under the impression that it stored this information. No; you need to put it in the file /boot.config yourself. (There's doesn't seem to be an easy way to *obtain* this information, unfortunately). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 11:21:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28784 for freebsd-current-outgoing; Sat, 24 Oct 1998 11:21:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28779 for ; Sat, 24 Oct 1998 11:21:10 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.59.174]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA4881 for ; Sat, 24 Oct 1998 20:20:36 +0200 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 24 Oct 1998 20:24:00 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Some more info on my make world stops Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am still experiencing problems with make world of 24-10-1998 All goes well until this step: -------------------------------------------------------------- >>> Rebuilding tools necessary to build the include files -------------------------------------------------------------- cc -O -pipe -I. -I/src/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/aout/src/src/tmp/usr/include -c error_table.c cc -O -pipe -I. -I/src/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/aout/src/src/tmp/usr/include -static -o compile_et compile_et.o error_table.o -ll ld: -ll: no match *** Error code 1 I looked it up in the mailinglists and it appears to want libl.a and I tried to make and make install it from the usr.bin/lex/lib/ directory but obviously as the above points out it didn't work... Anyone have some more ideas? --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 11:51:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00590 for freebsd-current-outgoing; Sat, 24 Oct 1998 11:51:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00582 for ; Sat, 24 Oct 1998 11:51:31 -0700 (PDT) (envelope-from sjr@home.net) Received: (from sjr@localhost) by istari.home.net (8.9.1/8.8.6) id OAA11330; Sat, 24 Oct 1998 14:50:58 -0400 (EDT) Date: Sat, 24 Oct 1998 14:50:58 -0400 (EDT) From: "Stephen J. Roznowski" Message-Id: <199810241850.OAA11330@istari.home.net> To: current@FreeBSD.ORG Subject: 3.0 installation problems Cc: jkh@time.cdrom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got done doing a fresh install of 3.0 and had a few problems. [These comments are from some jotted notes, and may be incomplete]: 1) I have an "Intel EtherExpress Pro/10+" and was trying to do an FTP install (via a cable modem). I deleted all of the other network devices -- the card was recognized, but the install hung during the "adding route" step. I occasionally had problems with my prior 3.0-current setup, where this card would be probed, but didn't seem to be working. A reboot (or two) usually fixes the problem. 2) I was doing an install using the entire 2nd drive (da1) and not touching the MBR. After setup was finished, my /etc/fstab was incorrectly referencing the first drive (da0). Further, none of the /dev/da1s1? devices were made. 3) I installed the "netscape-navigator-4.07" port, and when I try to execute it, I get the following error: ld.so failed: Can't find shared library "libXt.so.6.0" Thanks, -SR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 12:01:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01190 for freebsd-current-outgoing; Sat, 24 Oct 1998 12:01:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01183 for ; Sat, 24 Oct 1998 12:01:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA05523; Sat, 24 Oct 1998 12:05:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810241905.MAA05523@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Stephen J. Roznowski" cc: current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems In-reply-to: Your message of "Sat, 24 Oct 1998 14:50:58 EDT." <199810241850.OAA11330@istari.home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 12:05:34 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just got done doing a fresh install of 3.0 and had a few problems. > [These comments are from some jotted notes, and may be incomplete]: Thanks for these; it would of course have been nice to hear these back before the release, but I guess we can alway try for next time. > 1) I have an "Intel EtherExpress Pro/10+" and was trying to do an FTP > install (via a cable modem). I deleted all of the other network > devices -- the card was recognized, but the install hung during > the "adding route" step. The 'adding route' freeze irritates the *&^%( out of me. There are several different things that can go wrong at this point and there's no easy way to tell which one it is. > I occasionally had problems with my prior 3.0-current setup, where > this card would be probed, but didn't seem to be working. A reboot > (or two) usually fixes the problem. Did it fix the problem for you here ultimately? > 2) I was doing an install using the entire 2nd drive (da1) and not > touching the MBR. After setup was finished, my /etc/fstab was > incorrectly referencing the first drive (da0). Further, none of > the /dev/da1s1? devices were made. This is one that Jordan will have to field; it looks like something has forgotten the unit number somewhere along the way. Definitely bad. > 3) I installed the "netscape-navigator-4.07" port, and when I try to > execute it, I get the following error: > > ld.so failed: Can't find shared library "libXt.so.6.0" I don't think that the a.out X libraries get installed by default. (I could be wrong about this.) If there's nothing in /usr/X11R6/lib/aout, then that's the problem. In that case, we'll need to provide them too. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 12:08:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01842 for freebsd-current-outgoing; Sat, 24 Oct 1998 12:08:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01832 for ; Sat, 24 Oct 1998 12:08:27 -0700 (PDT) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id VAA03793 for ; Sat, 24 Oct 1998 21:07:52 +0200 (CEST) Received: from cs.uni-sb.de (acc1-133.telip.uni-sb.de [134.96.113.133]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id VAA04624 for ; Sat, 24 Oct 1998 21:07:51 +0200 (CEST) Message-ID: <363225D2.F8BC6C7F@cs.uni-sb.de> Date: Sat, 24 Oct 1998 21:09:06 +0200 From: Daniel Rock X-Mailer: Mozilla 4.07 [de] (Win98; U) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: vmstat, nfsstat broken Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, vmstat doesn't seem to like ELF kernels. With aout kernels "vmstat -i" works, but with ELF ones, I get the following error message: vmstat: symbol intrcnt not defined After taking a short look at the code, I suspect it may be associated with the now missing leading "_" in ELF symbols, but I'm not sure. nfsstat seems to be broken for a.out and ELF kernels: nfsstat: sysctl: No such file or directory If I change the sysctl() call to a sysctlbyname("vfs.nfs.nfsstats",...) call in nfsstat.c, nfsstat is working again. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 12:26:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02830 for freebsd-current-outgoing; Sat, 24 Oct 1998 12:26:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02822 for ; Sat, 24 Oct 1998 12:26:44 -0700 (PDT) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t1o29p3.telia.com [194.236.214.3]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id VAA01836 for ; Sat, 24 Oct 1998 21:26:06 +0200 Received: from pegasys (pegasys.granlund.nu [192.168.0.2]) by phoenix.granlund.nu (8.9.1/8.9.1) with SMTP id VAA00455 for ; Sat, 24 Oct 1998 21:25:19 +0200 (CEST) (envelope-from johan@phoenix.granlund.nu) Message-Id: <199810241925.VAA00455@phoenix.granlund.nu> From: "Johan Granlund" To: freebsd-current@FreeBSD.ORG Date: Sat, 24 Oct 1998 20:23:47 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Exabyte EXB-8200 and CAM, Take3 X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Before anybody says anything: I know i should have tested this the last time i got help:) That over with: I have a vanilla EXB-8200 drive that works with a preCAM kernel. When trying to make a backup with dump i I'medially get "DUMP: End of tape detected" as soon dump tries to write to the tape. Tar says "tar: only wrote 0 of xxx bytes to /dev/rsa0". Known quirks with precam kernel. Dump seems to pause 10-15sec between mapping and actually writing to the drive. When using rewind device (rsa0) i get device busy a couple of times when the driver tries to rewind. No rewind is happening. When letting dump reach EOT i get (from memory) Write error I/O error and a abort. Whith a CAM kernel it probes OK now (Thank for the help). When using dump i got "DUMP: End of tape detected" Imedially after the mapping. A preCAM kernel paused here. Tried enabling the CAM debuuging statements in the kernel config but got: /kernel: xpt_config: xpt_create_path() failed for debugt /kernel: arget -1:6:-1, debugging disabled I'm currently using a preCAM kernel for backups and that is working fine for now. Tried both firmware releases that is on the Exabyte website with no change. Any idea how to get information to help to solve this? Regards /Johan ___________________________________________________________ Internet: johan@granlund.nu I don't even speak for myself To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 12:38:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03767 for freebsd-current-outgoing; Sat, 24 Oct 1998 12:38:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03759 for ; Sat, 24 Oct 1998 12:38:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA05846; Sat, 24 Oct 1998 12:42:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810241942.MAA05846@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Daniel Rock cc: current@FreeBSD.ORG Subject: Re: vmstat, nfsstat broken In-reply-to: Your message of "Sat, 24 Oct 1998 21:09:06 +0200." <363225D2.F8BC6C7F@cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 12:42:17 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > vmstat doesn't seem to like ELF kernels. With aout kernels "vmstat -i" > works, but with ELF ones, I get the following error message: > vmstat: symbol intrcnt not defined > After taking a short look at the code, I suspect it may be associated > with the now missing leading "_" in ELF symbols, but I'm not sure. It's odd that intrcnt isn't found, but eintrcnt is. If you use 'nm' on your kernel, is it present as 'intrcnt' or '_intrcnt'? If you're looking for a small project, it'd be quite neat if you could clean vmstat up... > nfsstat seems to be broken for a.out and ELF kernels: > nfsstat: sysctl: No such file or directory > > If I change the sysctl() call to a sysctlbyname("vfs.nfs.nfsstats",...) > call in nfsstat.c, nfsstat is working again. Thanks; fixed. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 13:02:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05021 for freebsd-current-outgoing; Sat, 24 Oct 1998 13:02:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05015 for ; Sat, 24 Oct 1998 13:02:10 -0700 (PDT) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.9.1/8.9.1) with SMTP id QAA05598; Sat, 24 Oct 1998 16:01:26 -0400 (EDT) Message-Id: <3.0.5.32.19981024160121.009bc430@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 24 Oct 1998 16:01:21 -0400 To: Mike Smith From: Dan Swartzendruber Subject: Re: 3.0 installation problems Cc: "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com In-Reply-To: <199810241905.MAA05523@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of irritating installation issues: why do I have to install X to use emacs? I seem to recall, back in my linux days, that there was an emacs executable that didn't require X. The standard emacs binary requires a bunch of non vty libraries that I don't really want to have to install on stripped-down servers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 13:07:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05478 for freebsd-current-outgoing; Sat, 24 Oct 1998 13:07:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jane.lfn.org (jane.lfn.org [209.16.92.240]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA05473 for ; Sat, 24 Oct 1998 13:07:47 -0700 (PDT) (envelope-from caj@lfn.org) Received: (qmail 10360 invoked by uid 100); 24 Oct 1998 20:07:00 -0000 Date: Sat, 24 Oct 1998 15:07:00 -0500 (CDT) From: Craig Johnston To: freebsd-current@FreeBSD.ORG Subject: ELF XFree86 in ports Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wanted to hear from anyone who's running ELF XFree86 from the ports collection on -current. I'm running an aout installation right now -- I'd like to upgrade but I really don't need to hose X. thx, Craig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 13:37:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06737 for freebsd-current-outgoing; Sat, 24 Oct 1998 13:37:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06731 for ; Sat, 24 Oct 1998 13:37:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA07711; Sat, 24 Oct 1998 13:40:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810242040.NAA07711@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dan Swartzendruber cc: Mike Smith , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems In-reply-to: Your message of "Sat, 24 Oct 1998 16:01:21 EDT." <3.0.5.32.19981024160121.009bc430@mail.kersur.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 13:40:20 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Speaking of irritating installation issues: why do I have to install X > to use emacs? I seem to recall, back in my linux days, that there was > an emacs executable that didn't require X. The standard emacs binary > requires a bunch of non vty libraries that I don't really want to have > to install on stripped-down servers. If the machine is "stripped down", then you sure don't want Emacs on it. Try one of the lighter clones, and save yourself the worry. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 13:52:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07548 for freebsd-current-outgoing; Sat, 24 Oct 1998 13:52:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07543 for ; Sat, 24 Oct 1998 13:52:34 -0700 (PDT) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.9.1/8.9.1) with SMTP id QAA07290; Sat, 24 Oct 1998 16:51:08 -0400 (EDT) Message-Id: <3.0.5.32.19981024165102.0095ed30@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 24 Oct 1998 16:51:02 -0400 To: Mike Smith From: Dan Swartzendruber Subject: Re: 3.0 installation problems Cc: Mike Smith , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com In-Reply-To: <199810242040.NAA07711@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:40 PM 10/24/98 -0700, Mike Smith wrote: >> >> Speaking of irritating installation issues: why do I have to install X >> to use emacs? I seem to recall, back in my linux days, that there was >> an emacs executable that didn't require X. The standard emacs binary >> requires a bunch of non vty libraries that I don't really want to have >> to install on stripped-down servers. > >If the machine is "stripped down", then you sure don't want Emacs on it. >Try one of the lighter clones, and save yourself the worry. I'm not sure I understand your point. These are headless servers. They run all kinds of server applications, but virtually no user stuff, and certainly no X apps/libraries. Emacs is handy to have to edit configuration files and such when one telnets to the machine to make a change. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 14:07:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08184 for freebsd-current-outgoing; Sat, 24 Oct 1998 14:07:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08179 for ; Sat, 24 Oct 1998 14:07:54 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id PAA02659; Sat, 24 Oct 1998 15:07:17 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810242107.PAA02659@panzer.plutotech.com> Subject: Re: Exabyte EXB-8200 and CAM, Take3 In-Reply-To: <199810241925.VAA00455@phoenix.granlund.nu> from Johan Granlund at "Oct 24, 98 08:23:47 pm" To: johan@granlund.nu (Johan Granlund) Date: Sat, 24 Oct 1998 15:07:16 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan Granlund wrote... > Hi > > Before anybody says anything: I know i should have tested this the last > time i got help:) > > That over with: > > I have a vanilla EXB-8200 drive that works with a preCAM kernel. When > trying to make a backup with dump i I'medially get "DUMP: End of tape > detected" as soon dump tries to write to the tape. Tar says "tar: only wrote > 0 of xxx bytes to /dev/rsa0". > > Known quirks with precam kernel. > Dump seems to pause 10-15sec between mapping and actually writing to > the drive. > > When using rewind device (rsa0) i get device busy a couple of times when > the driver tries to rewind. No rewind is happening. > > When letting dump reach EOT i get (from memory) Write error I/O error and > a abort. > > Whith a CAM kernel it probes OK now (Thank for the help). > When using dump i got "DUMP: End of tape detected" Imedially after the > mapping. A preCAM kernel paused here. > Tried enabling the CAM debuuging statements in the kernel config but got: > /kernel: xpt_config: xpt_create_path() failed for debugt > /kernel: arget -1:6:-1, debugging disabled Hmm, not sure why it failed to create the path. Maybe it didn't like the bus wildcard for some reason. It may be that the xpt bus isn't configured by then. I think wildcarding the bus works once the system is up and running, though. I'd suggest just enabling CAMDEBUG in your kernel, and then turn on CDB debugging for your tape drive only via camcontrol. You can see exactly what bus/target/lun it is on by typing 'camcontrol devlist'. > I'm currently using a preCAM kernel for backups and that is working fine for > now. > Tried both firmware releases that is on the Exabyte website with no change. > > Any idea how to get information to help to solve this? Well, I think your best bet for now is just to use a pre-CAM kernel with that drive. We know very well that there are problems with the CAM tape driver's interaction with older tape drives. The Exabyte 8200 in particular is one of those drives that is "broken" with the CAM tape driver. A number of other folks have also reported problems with it. I've even got an 8200 here that doesn't work with the driver. :) I don't know when this will be fixed. Justin and I are currently in a big time crunch because of our "real" jobs. I'm scheduled to work on some tape stuff sometime in the near future, so I may be able to do something about the tape driver then. If someone clued in about SCSI tape drives wants to take a shot at making the driver work properly with older drives, feel free. I'll be glad to provide some help, if someone wants to tackle it. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 14:23:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09003 for freebsd-current-outgoing; Sat, 24 Oct 1998 14:23:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08998 for ; Sat, 24 Oct 1998 14:23:47 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01659; Sat, 24 Oct 1998 14:26:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810242126.OAA01659@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dan Swartzendruber cc: Mike Smith , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems In-reply-to: Your message of "Sat, 24 Oct 1998 16:51:02 EDT." <3.0.5.32.19981024165102.0095ed30@mail.kersur.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 14:26:21 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 01:40 PM 10/24/98 -0700, Mike Smith wrote: > >> > >> Speaking of irritating installation issues: why do I have to install X > >> to use emacs? I seem to recall, back in my linux days, that there was > >> an emacs executable that didn't require X. The standard emacs binary > >> requires a bunch of non vty libraries that I don't really want to have > >> to install on stripped-down servers. > > > >If the machine is "stripped down", then you sure don't want Emacs on it. > >Try one of the lighter clones, and save yourself the worry. > > I'm not sure I understand your point. These are headless servers. They > run all kinds of server applications, but virtually no user stuff, and > certainly no X apps/libraries. Emacs is handy to have to edit configuration > files and such when one telnets to the machine to make a change. If all you're doing is editing a few configuration files, emacs is overkill. Look at the size of the package, for instance. Emacs is a full-featured editing and develpment system. You need a text editor. If you don't like vi (understandable) there are plenty of editors that look-and-feel like emacs but don't come with the enormous bulk and X dependancies. Use one of these instead; I recommend jove. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 14:27:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09159 for freebsd-current-outgoing; Sat, 24 Oct 1998 14:27:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09154 for ; Sat, 24 Oct 1998 14:27:04 -0700 (PDT) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id XAA04730; Sat, 24 Oct 1998 23:25:57 +0200 (CEST) Received: from cs.uni-sb.de (acc2-215.telip.uni-sb.de [134.96.112.215]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id XAA05918; Sat, 24 Oct 1998 23:25:56 +0200 (CEST) Message-ID: <3632462A.A9A4503A@cs.uni-sb.de> Date: Sat, 24 Oct 1998 23:27:06 +0200 From: Daniel Rock X-Mailer: Mozilla 4.07 [de] (Win98; U) MIME-Version: 1.0 To: Mike Smith CC: current@FreeBSD.ORG Subject: Re: vmstat, nfsstat broken References: <199810241942.MAA05846@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith schrieb: > > > vmstat doesn't seem to like ELF kernels. With aout kernels "vmstat -i" > > works, but with ELF ones, I get the following error message: > > vmstat: symbol intrcnt not defined > > After taking a short look at the code, I suspect it may be associated > > with the now missing leading "_" in ELF symbols, but I'm not sure. > > It's odd that intrcnt isn't found, but eintrcnt is. If you use 'nm' on > your kernel, is it present as 'intrcnt' or '_intrcnt'? The problem isn't the leading "_", but: The variables intrnames, eintrname, intrcnt, eintrcnt from the namelist have the type N_UNDF associated, although they have the right value. If I just ignore n_type, I get the right output even on ELF kernels: *** vmstat.c.orig Sat Oct 24 23:23:27 1998 --- vmstat.c Sat Oct 24 23:23:45 1998 *************** *** 916,922 **** { char *sym; ! if (namelist[nlx].n_type == 0 || namelist[nlx].n_value == 0) { sym = namelist[nlx].n_name; if (*sym == '_') ++sym; --- 916,922 ---- { char *sym; ! if (namelist[nlx].n_value == 0) { sym = namelist[nlx].n_name; if (*sym == '_') ++sym; Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 14:40:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09644 for freebsd-current-outgoing; Sat, 24 Oct 1998 14:40:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09639 for ; Sat, 24 Oct 1998 14:40:23 -0700 (PDT) (envelope-from sjr@home.net) Received: (from sjr@localhost) by istari.home.net (8.9.1/8.8.6) id RAA17175; Sat, 24 Oct 1998 17:38:18 -0400 (EDT) Date: Sat, 24 Oct 1998 17:38:18 -0400 (EDT) From: "Stephen J. Roznowski" Message-Id: <199810242138.RAA17175@istari.home.net> To: mike@smith.net.au Subject: Re: 3.0 installation problems In-Reply-To: Mail from 'Mike Smith ' dated: Sat, 24 Oct 1998 12:05:34 -0700 Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Mike Smith > > > I just got done doing a fresh install of 3.0 and had a few problems. > > [These comments are from some jotted notes, and may be incomplete]: > > Thanks for these; it would of course have been nice to hear these back > before the release, but I guess we can alway try for next time. True, but: 1. This was the first free time I've had to do this, and 2. I'm not sure that I was "brave" enough to try the BETA... :-) > > 1) I have an "Intel EtherExpress Pro/10+" and was trying to do an FTP > > install (via a cable modem). I deleted all of the other network > > devices -- the card was recognized, but the install hung during > > the "adding route" step. > > The 'adding route' freeze irritates the *&^%( out of me. There are > several different things that can go wrong at this point and there's no > easy way to tell which one it is. > > > I occasionally had problems with my prior 3.0-current setup, where > > this card would be probed, but didn't seem to be working. A reboot > > (or two) usually fixes the problem. > > Did it fix the problem for you here ultimately? I think that I still have the problem. I think that there is a "timing" problem initializing the card, since every time I look at this to try to figure it out, the added debugging code makes it go away.... [I'm willing to try to track this down, however if someone has some clues...] BTW, my fallback was to use a SCSI tape for the install, so at least that works... > > 3) I installed the "netscape-navigator-4.07" port, and when I try to > > execute it, I get the following error: > > > > ld.so failed: Can't find shared library "libXt.so.6.0" > > I don't think that the a.out X libraries get installed by default. (I > could be wrong about this.) If there's nothing in /usr/X11R6/lib/aout, > then that's the problem. In that case, we'll need to provide them too. /usr/X11R6/lib/aout didn't even exist, but I didn't select the X11 portion of the install. I built XFree86 from the ports collection. I restored my old aout libraries from tape and now netscape works.... Perhaps an "XFree86 aout library port" needs to be added? Thanks, -SR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 14:41:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09810 for freebsd-current-outgoing; Sat, 24 Oct 1998 14:41:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09805 for ; Sat, 24 Oct 1998 14:41:21 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id OAA14729; Sat, 24 Oct 1998 14:40:40 -0700 Date: Sat, 24 Oct 1998 14:40:40 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Johan Granlund cc: freebsd-current@FreeBSD.ORG Subject: Re: Exabyte EXB-8200 and CAM, Take3 In-Reply-To: <199810241925.VAA00455@phoenix.granlund.nu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll look at this this weekend/week. It turns out I have a number of tape issues to look at, and, ho ho, I have an 8200 to throw on my FreeBSD box. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 14:55:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10418 for freebsd-current-outgoing; Sat, 24 Oct 1998 14:55:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from blondie.ottawa.cc (blondie.ottawa.cc [209.112.49.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10412 for ; Sat, 24 Oct 1998 14:55:04 -0700 (PDT) (envelope-from mat@blondie.ottawa.cc) Received: from localhost (mat@localhost) by blondie.ottawa.cc (8.9.1/8.9.1) with ESMTP id RAA17918; Sat, 24 Oct 1998 17:56:37 GMT (envelope-from mat@blondie.ottawa.cc) Date: Sat, 24 Oct 1998 17:56:37 +0000 (GMT) From: User MAT To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: How To Fixup A New Install -- Trivial Importance In-Reply-To: <199810241813.LAA05142@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Oct 1998, Mike Smith wrote: > > We were experimenting with a new bootmanager that properly handles > disks > 1024 cylinders, but it needs a little more testing; this was > fixed in a subsequent rebuild where we reverted to booteasy. > It works, just unclear that you have to push F5 to get to the appropriate disk. Anyway, if the installation has changed, shouldn't there be a mention in -errata? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 14:59:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10713 for freebsd-current-outgoing; Sat, 24 Oct 1998 14:59:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10708 for ; Sat, 24 Oct 1998 14:59:31 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost by echonyc.com (8.9.1/8.9.1) with SMTP id RAA14213; Sat, 24 Oct 1998 17:58:46 -0400 (EDT) Date: Sat, 24 Oct 1998 17:58:46 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Mike Smith cc: Dan Swartzendruber , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems In-Reply-To: <199810242040.NAA07711@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would suggest compiling emacs up from the ports collection; if it doesn't detect X libraries on the system, it will link without them. On Sat, 24 Oct 1998, Mike Smith wrote: > > Speaking of irritating installation issues: why do I have to install X > > to use emacs? I seem to recall, back in my linux days, that there was > > an emacs executable that didn't require X. The standard emacs binary > > requires a bunch of non vty libraries that I don't really want to have > > to install on stripped-down servers. > > If the machine is "stripped down", then you sure don't want Emacs on it. > Try one of the lighter clones, and save yourself the worry. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 15:01:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10820 for freebsd-current-outgoing; Sat, 24 Oct 1998 15:01:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10812 for ; Sat, 24 Oct 1998 15:01:34 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA05002; Sat, 24 Oct 1998 15:01:01 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd004980; Sat Oct 24 15:00:55 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id PAA25750; Sat, 24 Oct 1998 15:00:52 -0700 (MST) From: Terry Lambert Message-Id: <199810242200.PAA25750@usr01.primenet.com> Subject: Re: 3.0 missing some docs? To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sat, 24 Oct 1998 22:00:52 +0000 (GMT) Cc: tlambert@primenet.com, dwhite@resnet.uoregon.edu, jeff-ml@mountin.net, freebsd-current@FreeBSD.ORG In-Reply-To: <6537.909182675@critter.freebsd.dk> from "Poul-Henning Kamp" at Oct 24, 98 00:44:35 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> It's a hardware-ism. IRQ 7 is the generic junk IRQ. > > > >I was under the impression that we had registered default handlers for > >all IRQ's, and thus 7 was no longer the grabage bin unless there > >was a deassert race that indicates a real problem? > > > >You should ask Bruce Evans for confirmation. > > IRQ is the i8259's garbage bin, regardless of config. If an IRQ is asserted > too short for classification by the i8259 it becomes irq7. Yeah; that's the race. I remember that when IRQ 2 was disabled in the interrupt controller, back before there were default handlers to catch and ack it if it were enabled, EGA cards with vertical retrace interrupt on IRQ 2 (for light pen support) used to get thrown onto 7 as "masked, unclassifiable". I think I remember something about unsupported portions of some sound cards throwing spurious interrupts with an open collector microphone input without a hold-down resistor, too. Anyway, my point is that it's much less "generic junk" now, and it probably indicates a real problem with some hardware that's asserting and then deasserting some other IRQ: in other words, there's some bad hardware on board that machine, it's not just an unexpected (but valid) interrupt from good hardware. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 15:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11780 for freebsd-current-outgoing; Sat, 24 Oct 1998 15:26:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11755 for ; Sat, 24 Oct 1998 15:26:54 -0700 (PDT) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.9.1/8.9.1) with SMTP id SAA09894; Sat, 24 Oct 1998 18:26:13 -0400 (EDT) Message-Id: <3.0.5.32.19981024182609.009c3c60@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 24 Oct 1998 18:26:09 -0400 To: ben@rosengart.com From: Dan Swartzendruber Subject: Re: 3.0 installation problems Cc: Mike Smith , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com In-Reply-To: References: <199810242040.NAA07711@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:58 PM 10/24/98 -0400, Snob Art Genre wrote: >I would suggest compiling emacs up from the ports collection; if it >doesn't detect X libraries on the system, it will link without them. > >On Sat, 24 Oct 1998, Mike Smith wrote: > >> > Speaking of irritating installation issues: why do I have to install X >> > to use emacs? I seem to recall, back in my linux days, that there was >> > an emacs executable that didn't require X. The standard emacs binary >> > requires a bunch of non vty libraries that I don't really want to have >> > to install on stripped-down servers. >> >> If the machine is "stripped down", then you sure don't want Emacs on it. >> Try one of the lighter clones, and save yourself the worry. I suppose that would be doable, although it's almost more of a hassle than just copying over the requisite libraries from one of the X-enabled workstations. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 15:28:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11917 for freebsd-current-outgoing; Sat, 24 Oct 1998 15:28:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11910 for ; Sat, 24 Oct 1998 15:28:48 -0700 (PDT) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.9.1/8.9.1) with SMTP id SAA09929; Sat, 24 Oct 1998 18:28:10 -0400 (EDT) Message-Id: <3.0.5.32.19981024182807.009be140@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 24 Oct 1998 18:28:07 -0400 To: Mike Smith From: Dan Swartzendruber Subject: Re: 3.0 installation problems Cc: Mike Smith , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com In-Reply-To: <199810242126.OAA01659@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:26 PM 10/24/98 -0700, Mike Smith wrote: > >If all you're doing is editing a few configuration files, emacs is >overkill. Look at the size of the package, for instance. > >Emacs is a full-featured editing and develpment system. You need a >text editor. If you don't like vi (understandable) there are plenty of >editors that look-and-feel like emacs but don't come with the enormous >bulk and X dependancies. Use one of these instead; I recommend jove. That's fine. I've never used jove. I use gnu emacs 99.999% of the time normally, and I don't want to have to keep shifting mental gears. If jove looks&feels like emacs, that would be fine by me... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 15:33:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12146 for freebsd-current-outgoing; Sat, 24 Oct 1998 15:33:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12140 for ; Sat, 24 Oct 1998 15:33:24 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id PAA05498; Sat, 24 Oct 1998 15:32:50 -0700 (PDT) (envelope-from obrien) Message-ID: <19981024153250.B4735@nuxi.com> Date: Sat, 24 Oct 1998 15:32:50 -0700 From: "David O'Brien" To: Dan Swartzendruber Cc: current@FreeBSD.ORG Subject: Re: 3.0 installation problems Reply-To: obrien@NUXI.com References: <199810241905.MAA05523@dingo.cdrom.com> <3.0.5.32.19981024160121.009bc430@mail.kersur.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3.0.5.32.19981024160121.009bc430@mail.kersur.net>; from Dan Swartzendruber on Sat, Oct 24, 1998 at 04:01:21PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Speaking of irritating installation issues: why do I have to install X > to use emacs? Because the maintainier of emacs believes that X support is desired in the general case. You aren't in the general case. You could appeal to the maintainer to change his mind. OR build the port yourself by: cd /usr/ports/editors/emacs make install distclean -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 15:37:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12417 for freebsd-current-outgoing; Sat, 24 Oct 1998 15:37:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12412 for ; Sat, 24 Oct 1998 15:37:03 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id PAA05517; Sat, 24 Oct 1998 15:36:19 -0700 (PDT) (envelope-from obrien) Message-ID: <19981024153619.C4735@nuxi.com> Date: Sat, 24 Oct 1998 15:36:19 -0700 From: "David O'Brien" To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: 3.0 installation problems Reply-To: obrien@NUXI.com References: <199810241850.OAA11330@istari.home.net> <199810241905.MAA05523@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810241905.MAA05523@dingo.cdrom.com>; from Mike Smith on Sat, Oct 24, 1998 at 12:05:34PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The 'adding route' freeze irritates the *&^%( out of me. There are > several different things that can go wrong at this point and there's no > easy way to tell which one it is. Is there *ANY* way to debug this? I never had this problem this problem in 2.2.5 days. But now I get it for *every* install of 2.2.7 or 3.0. I'm seeing "hangs" upto 5 minutes. All ranges of cards (fxp0, de0, ed0, xl0) on several different subnets with different hubs/routers on campus. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 15:43:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12881 for freebsd-current-outgoing; Sat, 24 Oct 1998 15:43:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12876 for ; Sat, 24 Oct 1998 15:43:00 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA13082; Sat, 24 Oct 1998 15:42:27 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd013047; Sat Oct 24 15:42:16 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id PAA27859; Sat, 24 Oct 1998 15:42:15 -0700 (MST) From: Terry Lambert Message-Id: <199810242242.PAA27859@usr01.primenet.com> Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 24 Oct 1998 22:42:15 +0000 (GMT) Cc: tlambert@primenet.com, john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG In-Reply-To: <3812.909216213@time.cdrom.com> from "Jordan K. Hubbard" at Oct 24, 98 01:03:33 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Good thing to know that we've finally got that "proliferation of > > config files" problem under control... it's not resolved, but at > > least we're "controlling" it... > > "ok", I "guess" I understand what "you" are trying to say here. When you are a passenger headed for an unavoidable car wreck, it's still nice to know that someone is steering. This guy had this piano halfway through a french window. He's running back and forth between the inside and the outside of his apartment, trying to move the piano through the french window. It's obvious to anyone looking at the piano, the french window, and the door, that the piano would never have fit through the door, so the window was the only practical portal through which to move the piano, but it's obviously caught on the sill, and too heavy for one man alone to get it uncaught. A sympathetic passer-by sees this guy trying to move the piano over the sill by himself, and decides to help the poor guy out. The guy is very grateful for the help, and thanks the passer-by profusely for the offer, as his brother-in-law was supposed to help him move the piano, but was unavoidably detained. They quickly seperate, with the guy on the inside of the french window and the passer-by on the outside. With a mighty "Heave!", they both lift their respective ends of the piano, but try as they might, even with two people working on it, they simply can't budge the piano from its original position. After about fifteen minutes, the guy calls a stop to the ovbiously fruitless proceedings, and comes out with two beers, gives one to the passer-by, and they both sit down together on the curb to drink them. They discuss how immovable the piano is, and the guy thanks the passer-by for his help, and says that he's sure that tomorrow, with the help of his brother-in-law and a couple buddies from work he'll be able to get the piano out of the aparment. "OUT?", cried the passer-by, "I thought you wanted it IN!" The moral: /etc/auth.conf is a new configuration file, and it seems a waste to gain yet-another-configuration-file after the long and valiant struggle to minimize the number and format of files that have to be editted in order to configure a FreeBSD box. Still, even if the new file must stay, it would be nice to know that at least it was the result of someone is steering, instead of being the result of people not communicating. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 15:57:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13309 for freebsd-current-outgoing; Sat, 24 Oct 1998 15:57:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13304 for ; Sat, 24 Oct 1998 15:57:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA25534; Sat, 24 Oct 1998 15:59:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810242259.PAA25534@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com cc: Mike Smith , current@FreeBSD.ORG Subject: Re: 3.0 installation problems In-reply-to: Your message of "Sat, 24 Oct 1998 15:36:19 PDT." <19981024153619.C4735@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 15:59:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The 'adding route' freeze irritates the *&^%( out of me. There are > > several different things that can go wrong at this point and there's no > > easy way to tell which one it is. > > Is there *ANY* way to debug this? I never had this problem this problem > in 2.2.5 days. But now I get it for *every* install of 2.2.7 or 3.0. > I'm seeing "hangs" upto 5 minutes. > > All ranges of cards (fxp0, de0, ed0, xl0) on several different subnets > with different hubs/routers on campus. Sysinstall ifconfig's the interface, then exec's "route -n add default x.x.x.x" I added the '-n' in an attempt to reduce the delay in the case where the nameserver was slow or unreachable (eg. due to error). Debugging it is relatively straightforward; build yourself a copy of sysinstall (cd src/release/sysinstall; make), then run it. You can experiment with taking various interfaces down before you start it, reboot and come up single-user, etc. If you can nail this one, there'll be plenty of Very Happy people. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 16:03:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13840 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:03:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13834 for ; Sat, 24 Oct 1998 16:03:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA29400; Sat, 24 Oct 1998 16:07:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810242307.QAA29400@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: User MAT cc: freebsd-current@FreeBSD.ORG Subject: Re: How To Fixup A New Install -- Trivial Importance In-reply-to: Your message of "Sat, 24 Oct 1998 17:56:37 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 16:07:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Sat, 24 Oct 1998, Mike Smith wrote: > > > > > We were experimenting with a new bootmanager that properly handles > > disks > 1024 cylinders, but it needs a little more testing; this was > > fixed in a subsequent rebuild where we reverted to booteasy. > > > It works, just unclear that you have to push F5 to get to the > appropriate disk. Anyway, if the installation has changed, shouldn't > there be a mention in -errata? The release tag was slid forwards, so the feature's not present in the "real" release. I'm trying to resolve a couple of other potential errata items before a new update at the moment. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 16:04:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14030 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:04:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14025 for ; Sat, 24 Oct 1998 16:04:34 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA29107; Sat, 24 Oct 1998 16:04:01 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd029089; Sat Oct 24 16:03:52 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA28873; Sat, 24 Oct 1998 16:03:50 -0700 (MST) From: Terry Lambert Message-Id: <199810242303.QAA28873@usr01.primenet.com> Subject: Re: Improper sharing of modem bandwidth To: kkennawa@physics.adelaide.edu.au (Kris Kennaway) Date: Sat, 24 Oct 1998 23:03:50 +0000 (GMT) Cc: brian@awfulhak.org, current@FreeBSD.ORG In-Reply-To: from "Kris Kennaway" at Oct 25, 98 00:43:05 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Making the suggested change from 20 to 100 in bundle.c didnt seem to have > a noticeable effect; to recap my problem, if I start up a binary transfer > which runs at full throttle (~1.65k/s on my 14.4k modem, usually), then it > starves all other network connections to the point of exclusion. I've done > some more checking and perhaps some of this will be helpful. > > If I ^Z the ftp (or http, or whatever the binary transfer is that's > hogging the modem) process, the modem continues to transfer for ~11 > seconds (~18k) before coming to a stop; immediately thereafter my other > network sessions (telnet, ping, etc) "unfreeze" and I get normal > performance from them. Restarting the FTP transfer immediately excludes > everything else again. > > If I start a ping of a host which is ~400ms away at normal usage, > restarting the FTP transfer will cause no further packets to be returned. I assume (by the http reference) that this is a transfer *to* your machine, instead of a transfer *from* your machine? It appears to me that the problem is that your ISP's buffers for your port are about 16k, and that data in transit from the remote host is monopolizing them. There are two remedies that are immediately obvious; one is to use Julian Elisher's version of the bandwidth control code, and the other is to set a smaller MTU and end-to-end window size, and then delay FTP ACK's. In any case, it appears that the problem is that there is no remaining buffer space for inbound (to you) packets at the ISP, and that controlling the monopolization of that space by FTP data is the only remedy that will work to resolve your problem. That's actually best done by the ISP by setting port/priority bands for various protocols, with emphasis placed on protocols most likely to have a human on the other end of them. This means that HTTP would probably still be capable of knocking you out, and that FTP in a URL in a browser would be unexpectedly slow, but at least your telnet would be more responsive (your ping does not establish a virtual circuit, so it can't reserve bandwidth). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 16:05:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14067 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:05:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14056 for ; Sat, 24 Oct 1998 16:05:05 -0700 (PDT) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t1o29p4.telia.com [194.236.214.4]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id BAA01872; Sun, 25 Oct 1998 01:04:28 +0200 Received: from pegasys (pegasys.granlund.nu [192.168.0.2]) by phoenix.granlund.nu (8.9.1/8.9.1) with SMTP id BAA00411; Sun, 25 Oct 1998 01:01:14 +0200 (CEST) (envelope-from johan@phoenix.granlund.nu) Message-Id: <199810242301.BAA00411@phoenix.granlund.nu> From: "Johan Granlund" To: Craig Johnston , freebsd-current@FreeBSD.ORG Date: Sat, 24 Oct 1998 23:59:41 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: ELF XFree86 in ports In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Wanted to hear from anyone who's running ELF XFree86 from the ports > collection on -current. I'm running an aout installation right now -- I'd > like to upgrade but I really don't need to hose X. No problems (for me). I only installed the port over my old installation. Make sure that you have run the "move-aout-libs" target to move the aout libs to aout before reinstalling X. /Johan > > thx, > Craig. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ___________________________________________________________ Internet: johan@granlund.nu I don't even speak for myself To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 16:05:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14073 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:05:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14059 for ; Sat, 24 Oct 1998 16:05:06 -0700 (PDT) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t1o29p4.telia.com [194.236.214.4]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id BAA01873; Sun, 25 Oct 1998 01:04:29 +0200 Received: from pegasys (pegasys.granlund.nu [192.168.0.2]) by phoenix.granlund.nu (8.9.1/8.9.1) with SMTP id AAA00377; Sun, 25 Oct 1998 00:52:56 +0200 (CEST) (envelope-from johan@phoenix.granlund.nu) Message-Id: <199810242252.AAA00377@phoenix.granlund.nu> From: "Johan Granlund" To: "Kenneth D. Merry" Date: Sat, 24 Oct 1998 23:51:23 +0200 MIME-Version: 1.0 Content-type: Multipart/Mixed; boundary=Message-Boundary-7355 Subject: Re: Exabyte EXB-8200 and CAM, Take3 CC: freebsd-current@FreeBSD.ORG In-reply-to: <199810242107.PAA02659@panzer.plutotech.com> References: <199810241925.VAA00455@phoenix.granlund.nu> from Johan Granlund at "Oct 24, 98 08:23:47 pm" X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Message-Boundary-7355 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body > Johan Granlund wrote... > > I'm currently using a preCAM kernel for backups and that is working fine > > for now. Tried both firmware releases that is on the Exabyte website > > with no change. > > > > Any idea how to get information to help to solve this? > > Well, I think your best bet for now is just to use a pre-CAM kernel with > that drive. We know very well that there are problems with the CAM tape > driver's interaction with older tape drives. The Exabyte 8200 in > particular is one of those drives that is "broken" with the CAM tape > driver. A number of other folks have also reported problems with it. > I've even got an 8200 here that doesn't work with the driver. :) > > I don't know when this will be fixed. Justin and I are currently in a big > time crunch because of our "real" jobs. I'm scheduled to work on some > tape stuff sometime in the near future, so I may be able to do something > about the tape driver then. > > If someone clued in about SCSI tape drives wants to take a shot at making > the driver work properly with older drives, feel free. I'll be glad to > provide some help, if someone wants to tackle it. > I know all about time crunch:) As long as you know that it's broken everything is fine. I searched the archives and didn't find any noice about the Exabyte and wanted to tell someone that it was broke for me. I got a CDB trace? that is not telling me much, but if anyone is interested its attached. I used the following script: ------------------------------------------ dump -0ub 32 -af /dev/nrsa0 /exports sleep 60 mt -f /dev/rsa0 rewind ------------------------------------------ I've got both 2644 and 2618 firmware if someone want me to test something. /Johan > Ken > -- > Kenneth Merry > ken@plutotech.com > ___________________________________________________________ Internet: johan@granlund.nu I don't even speak for myself --Message-Boundary-7355 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Text from file 'sa0.log' Oct 25 00:15:28 phoenix /kernel: Waiting 2 seconds for SCSI devices to settle Oct 25 00:15:28 phoenix /kernel: (pr Oct 25 00:15:28 phoenix /kernel: obe6:ahc0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 Oct 25 00:15:28 phoenix /kernel: (probe6:ahc0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Oct 25 00:15:28 phoenix /kernel: sa0 at ahc0 bus 0 target 6 lun 0 Oct 25 00:15:28 phoenix /kernel: sa0: Removable Sequential Access SCSI1 device Oct 25 00:15:28 phoenix /kernel: sa0: 3.300MB/s transfers Oct 25 00:16:47 phoenix /kernel: (sa0:ahc0:0:6:0): RESERVE(06). CDB: 16 0 0 0 0 0 Oct 25 00:16:47 phoenix /kernel: (sa0:ahc0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Oct 25 00:16:47 phoenix /kernel: (sa0:ahc0:0:6:0): READ BLOCK LIMITS. CDB: 5 0 0 0 0 0 Oct 25 00:16:47 phoenix /kernel: (sa0:ahc0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 Oct 25 00:16:47 phoenix /kernel: (sa0:ahc0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 Oct 25 00:16:47 phoenix /kernel: (sa0:ahc0:0:6:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 Oct 25 00:16:48 phoenix /kernel: (sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 Oct 25 00:16:48 phoenix /kernel: (sa0:ahc0:0:6:0): WRITE(06). CDB: a 0 0 80 0 0 Oct 25 00:17:05 phoenix last message repeated 149 times Oct 25 00:17:06 phoenix /kernel: (sa0:ahc0:0:6:0): WRITE FILEMARKS. CDB: 10 0 0 0 1 0 Oct 25 00:17:53 phoenix /kernel: (sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 0 0 Oct 25 00:17:53 phoenix /kernel: (sa0:ahc0:0:6:0): RELEASE(06). CDB: 17 0 0 0 0 0 Oct 25 00:17:53 phoenix /kernel: (sa0:ahc0:0:6:0): RESERVE(06). CDB: 16 0 0 0 0 0 Oct 25 00:17:54 phoenix /kernel: (sa0:ahc0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Oct 25 00:17:54 phoenix /kernel: (sa0:ahc0:0:6:0): READ BLOCK LIMITS. CDB: 5 0 0 0 0 0 Oct 25 00:17:54 phoenix /kernel: (sa0:ahc0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 Oct 25 00:17:54 phoenix /kernel: (sa0:ahc0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 Oct 25 00:17:54 phoenix /kernel: (sa0:ahc0:0:6:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 Oct 25 00:17:54 phoenix /kernel: (sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 Oct 25 00:17:54 phoenix /kernel: (sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 0 0 Oct 25 00:17:54 phoenix /kernel: (sa0:ahc0:0:6:0): RELEASE(06). CDB: 17 0 0 0 0 0 Oct 25 00:19:07 phoenix /kernel: (sa0:ahc0:0:6:0): RESERVE(06). CDB: 16 0 0 0 0 0 Oct 25 00:19:08 phoenix /kernel: (sa0:ahc0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Oct 25 00:19:08 phoenix /kernel: (sa0:ahc0:0:6:0): READ BLOCK LIMITS. CDB: 5 0 0 0 0 0 Oct 25 00:19:08 phoenix /kernel: (sa0:ahc0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 Oct 25 00:19:08 phoenix /kernel: (sa0:ahc0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 Oct 25 00:19:08 phoenix /kernel: (sa0:ahc0:0:6:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 Oct 25 00:19:08 phoenix /kernel: (sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 Oct 25 00:19:08 phoenix /kernel: (sa0:ahc0:0:6:0): REWIND. CDB: 1 0 0 0 0 0 Oct 25 00:19:40 phoenix /kernel: (sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 0 0 Oct 25 00:19:40 phoenix /kernel: (sa0:ahc0:0:6:0): REWIND. CDB: 1 0 0 0 0 0 Oct 25 00:19:41 phoenix /kernel: (sa0:ahc0:0:6:0): RELEASE(06). CDB: 17 0 0 0 0 0 --Message-Boundary-7355-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 16:05:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14112 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:05:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14100 for ; Sat, 24 Oct 1998 16:05:33 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id TAA07849; Sat, 24 Oct 1998 19:04:01 -0400 (EDT) Date: Sat, 24 Oct 1998 19:04:01 -0400 (EDT) From: Chuck Robey To: "David O'Brien" cc: Dan Swartzendruber , current@FreeBSD.ORG Subject: Re: 3.0 installation problems In-Reply-To: <19981024153250.B4735@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Oct 1998, David O'Brien wrote: > > Speaking of irritating installation issues: why do I have to install X > > to use emacs? > > Because the maintainier of emacs believes that X support is desired in > the general case. You aren't in the general case. You could appeal to > the maintainer to change his mind. OR build the port yourself by: > > cd /usr/ports/editors/emacs > make install distclean It's not terribly difficult to make it build without X11. A primary requirement, however, is to have absolutely NO X11 stuff on your machine, because emacs will hunt it down and use X11 if it finds any vestiges around. If you _have_ any pieces of X11 around, then making emacs ignore it is a PITA. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 16:07:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14268 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:07:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14248 for ; Sat, 24 Oct 1998 16:07:32 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01103; Sat, 24 Oct 1998 16:11:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810242311.QAA01103@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Stephen J. Roznowski" cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: 3.0 installation problems In-reply-to: Your message of "Sat, 24 Oct 1998 17:38:18 EDT." <199810242138.RAA17175@istari.home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 16:11:19 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > From: Mike Smith > > > > > I just got done doing a fresh install of 3.0 and had a few problems. > > > [These comments are from some jotted notes, and may be incomplete]: > > > > Thanks for these; it would of course have been nice to hear these back > > before the release, but I guess we can alway try for next time. > > True, but: > > 1. This was the first free time I've had to do this, and > 2. I'm not sure that I was "brave" enough to try the BETA... Fair enough. How do you feel about giving the beta for the next release a try? We *really* do value betatester feedback, and we never get enough... > I think that I still have the problem. I think that there is a "timing" > problem initializing the card, since every time I look at this to try > to figure it out, the added debugging code makes it go away.... [I'm > willing to try to track this down, however if someone has some clues...] You could try putting some DELAY() calls in where you normally would put your debugging code, and see if that helps it along. > BTW, my fallback was to use a SCSI tape for the install, so at least > that works... Great! It's something that's not on the "supported" list anymore, so it's wonderful to know it's still working properly. > > > 3) I installed the "netscape-navigator-4.07" port, and when I try to > > > execute it, I get the following error: > > > > > > ld.so failed: Can't find shared library "libXt.so.6.0" > > > > I don't think that the a.out X libraries get installed by default. (I > > could be wrong about this.) If there's nothing in /usr/X11R6/lib/aout, > > then that's the problem. In that case, we'll need to provide them too. > > /usr/X11R6/lib/aout didn't even exist, but I didn't select the X11 portion > of the install. I built XFree86 from the ports collection. I restored > my old aout libraries from tape and now netscape works.... Oh geez. You gave me a complete heart attack there; I was thinking that the standard install didn't include a.out libs when it installed X. > Perhaps an "XFree86 aout library port" needs to be added? Feel like rolling one and submitting it? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 16:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14731 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:17:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14725 for ; Sat, 24 Oct 1998 16:17:24 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA19401; Sat, 24 Oct 1998 16:16:50 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd019362; Sat Oct 24 16:16:47 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA29528; Sat, 24 Oct 1998 16:16:29 -0700 (MST) From: Terry Lambert Message-Id: <199810242316.QAA29528@usr01.primenet.com> Subject: Re: 3.0 installation problems To: mike@smith.net.au (Mike Smith) Date: Sat, 24 Oct 1998 23:16:29 +0000 (GMT) Cc: obrien@NUXI.com, mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: <199810242259.PAA25534@dingo.cdrom.com> from "Mike Smith" at Oct 24, 98 03:59:33 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The 'adding route' freeze irritates the *&^%( out of me. There are > > > several different things that can go wrong at this point and there's no > > > easy way to tell which one it is. > > > > Is there *ANY* way to debug this? I never had this problem this problem > > in 2.2.5 days. But now I get it for *every* install of 2.2.7 or 3.0. > > I'm seeing "hangs" upto 5 minutes. > > Debugging it is relatively straightforward; build yourself a copy of > sysinstall (cd src/release/sysinstall; make), then run it. You can > experiment with taking various interfaces down before you start it, > reboot and come up single-user, etc. > > If you can nail this one, there'll be plenty of Very Happy people. On a potentially related not, we have one Cyrix based system at work that occasionally "loses" its default route for no reason that we have been able to determine. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 16:21:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14993 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:21:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14988 for ; Sat, 24 Oct 1998 16:21:18 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA02647; Sat, 24 Oct 1998 16:20:45 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd002634; Sat Oct 24 16:20:37 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA29640; Sat, 24 Oct 1998 16:20:36 -0700 (MST) From: Terry Lambert Message-Id: <199810242320.QAA29640@usr01.primenet.com> Subject: Re: 3.0 installation problems To: mike@smith.net.au (Mike Smith) Date: Sat, 24 Oct 1998 23:20:36 +0000 (GMT) Cc: sjr@home.net, mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: <199810242311.QAA01103@dingo.cdrom.com> from "Mike Smith" at Oct 24, 98 04:11:19 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Fair enough. How do you feel about giving the beta for the next > release a try? We *really* do value betatester feedback, and we never > get enough... Well, personally, how I feel about it depends on the answer to the question "how do you feel about a slightly longer beta cycle next time?", since I basically do work stuff during the week, and if you want something reported, and then shook down afterwards, you will have to give me two weekends for it to be worth my while to expend effort on searching out problems. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 16:38:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15833 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:38:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from luomat.peak.org (port-56-ts2-gnv.da.fdt.net [209.212.132.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15828 for ; Sat, 24 Oct 1998 16:38:20 -0700 (PDT) (envelope-from luomat@luomat.peak.org) Message-Id: <199810242337.TAA01175@ocalhost> Content-Type: text/plain MIME-Version: 1.0 In-Reply-To: From: Timothy J Luoma Date: Sat, 24 Oct 1998 19:37:40 -0400 To: freebsd-current@FreeBSD.ORG Subject: Re: How To Fixup A New Install -- Trivial Importance References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Author: User MAT Date: Sat, 24 Oct 1998 13:47:11 +0000 (GMT) ID: > I was very impressed that this worked so easily (you have to run > the Windows Cable-Modem software first to get the IP/gateway/DNS > via DHCP, once you have theses values, the cable-modem doesn't > care). FWIW Comcast@Home gave me the information I needed to install w/out my having to run Windows. @Home Unix customers are wise to report themselves as Mac users -- Mac's DHCP apparently doesn't work well w/ @Home, so if they ever need to change your settings, they supposedly inform Mac folks ahead of time. (@Home's policy is basically that the IP won't change unless they have to renumber your entire node, so it is "static" for 99% of the people). But there's a list for Unix@Home folks if anyone is interested in more of that... TjL, who had a cable modem for a year, then moved to a new place where they don't exist yet :-(((((( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 16:40:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16133 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:40:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16105 for ; Sat, 24 Oct 1998 16:40:04 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.05 #3) id 0zXAJm-0000cv-00; Sat, 24 Oct 1998 21:29:46 +0100 Date: Sat, 24 Oct 1998 21:29:46 +0100 From: Ben Smithurst To: Craig Johnston Cc: freebsd-current@FreeBSD.ORG Subject: Re: ELF XFree86 in ports Message-ID: <19981024212946.A2151@scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: User-Agent: Mutt/0.94.12i (FreeBSD/3.0-CURRENT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Craig Johnston wrote: > Wanted to hear from anyone who's running ELF XFree86 from the ports > collection on -current. I'm running an aout installation right now -- I'd > like to upgrade but I really don't need to hose X. I'm running it, what do you want to know? It all seems to work fine, if that's all you wanted to know :-) -- Ben Smithurst ben@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 17:09:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17834 for freebsd-current-outgoing; Sat, 24 Oct 1998 17:09:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17828 for ; Sat, 24 Oct 1998 17:09:16 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id BAA14735; Sun, 25 Oct 1998 01:13:08 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 25 Oct 1998 01:13:07 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: Daniel Rock , current@FreeBSD.ORG Subject: Re: vmstat, nfsstat broken In-Reply-To: <199810241942.MAA05846@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Oct 1998, Mike Smith wrote: > > vmstat doesn't seem to like ELF kernels. With aout kernels "vmstat -i" > > works, but with ELF ones, I get the following error message: > > vmstat: symbol intrcnt not defined > > After taking a short look at the code, I suspect it may be associated > > with the now missing leading "_" in ELF symbols, but I'm not sure. > > It's odd that intrcnt isn't found, but eintrcnt is. If you use 'nm' on > your kernel, is it present as 'intrcnt' or '_intrcnt'? > > If you're looking for a small project, it'd be quite neat if you could > clean vmstat up... IMVHO, things like vmstat shouldn't use libkvm at all, especially because most of the info they report is already available via sysctl(3). If some structures and figures still need to be exported, perhaps better just do this, and not invest additional efforts in using libkvm... Also, as an additional bonus you'd get chmod g-s. The argument that "libkvm allows you to read this info from other images" is important, but it just shows that we need some relatively versatile tool for examining coredumps. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 17:19:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18888 for freebsd-current-outgoing; Sat, 24 Oct 1998 17:19:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18880 for ; Sat, 24 Oct 1998 17:19:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA20987; Sat, 24 Oct 1998 17:22:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810250022.RAA20987@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Mike Smith , Daniel Rock , current@FreeBSD.ORG Subject: Re: vmstat, nfsstat broken In-reply-to: Your message of "Sun, 25 Oct 1998 01:13:07 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 17:22:54 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 24 Oct 1998, Mike Smith wrote: > > > > vmstat doesn't seem to like ELF kernels. With aout kernels "vmstat -i" > > > works, but with ELF ones, I get the following error message: > > > vmstat: symbol intrcnt not defined > > > After taking a short look at the code, I suspect it may be associated > > > with the now missing leading "_" in ELF symbols, but I'm not sure. > > > > It's odd that intrcnt isn't found, but eintrcnt is. If you use 'nm' on > > your kernel, is it present as 'intrcnt' or '_intrcnt'? > > > > If you're looking for a small project, it'd be quite neat if you could > > clean vmstat up... > > IMVHO, things like vmstat shouldn't use libkvm at all, especially because > most of the info they report is already available via sysctl(3). If some > structures and figures still need to be exported, perhaps better just do > this, and not invest additional efforts in using libkvm... Also, as an > additional bonus you'd get chmod g-s. This won't work until someone writes a standalone sysctl library that runs using the kernel sysctl datastructures. It'll get harder if/when we go for a more method-based sysctl replacement. > The argument that "libkvm allows you to read this info from other images" > is important, but it just shows that we need some relatively versatile > tool for examining coredumps. Actually, I don't think many people use these tools on coredumps, but they're very loud. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 17:54:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20751 for freebsd-current-outgoing; Sat, 24 Oct 1998 17:54:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fani.fidata.fi (fani.fidata.fi [193.64.102.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20743 for ; Sat, 24 Oct 1998 17:54:07 -0700 (PDT) (envelope-from tomppa@fidata.fi) Received: from zeta.fidata.fi (zeta.fidata.fi [193.64.103.213]) by fani.fidata.fi (8.8.8/8.8.8) with ESMTP id DAA03679 for ; Sun, 25 Oct 1998 03:53:31 +0300 (EET DST) Received: (from tomppa@localhost) by zeta.fidata.fi (8.9.1/8.9.1) id DAA04647; Sun, 25 Oct 1998 03:53:30 +0300 (EET DST) From: Tomi Vainio MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13874.30346.672379.147233@zeta.fidata.fi> Date: Sun, 25 Oct 1998 03:53:30 +0300 (EET DST) To: freebsd-current@FreeBSD.ORG Subject: 3.0 + CAM + xmcd-2.3 X-Mailer: VM 6.47 under 20.4 "Emerald" XEmacs Lucid Reply-To: tomppa@fidata.fi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried to use xmcd with my current system and it won't work. First I compiled it from ports and then I also tried package but either one can't see my cdrom. Xmcd worked fine with my 2.2-stable+cam system. Has anybody got this work? Tomppa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 18:19:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22537 for freebsd-current-outgoing; Sat, 24 Oct 1998 18:19:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22532 for ; Sat, 24 Oct 1998 18:19:17 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id SAA15386; Sat, 24 Oct 1998 18:18:38 -0700 Date: Sat, 24 Oct 1998 18:18:38 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Johan Granlund cc: "Kenneth D. Merry" , freebsd-current@FreeBSD.ORG Subject: Re: Exabyte EXB-8200 and CAM, Take3 In-Reply-To: <199810242252.AAA00377@phoenix.granlund.nu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There's a bit of a contradiction between your first email and the last one. The first email says that dump exits right away: ...I'medially get "DUMP: End of tape detected" as soon dump tries to write to the tape. The last email implies that that dump succeeded (150 or so writes succeeded). What did the dump program for the script in the last email say? More importantly, are there any log messages that correlate with the initial error messages you report? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 18:56:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25144 for freebsd-current-outgoing; Sat, 24 Oct 1998 18:56:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net ([207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25139 for ; Sat, 24 Oct 1998 18:56:47 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id UAA07518; Sat, 24 Oct 1998 20:56:09 -0500 (CDT) Received: from harkol-32.isdn.mke.execpc.com(169.207.64.160) by peak.mountin.net via smap (V1.3) id sma007516; Sat Oct 24 20:55:55 1998 Message-Id: <3.0.3.32.19981024205624.00f6b2b4@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 24 Oct 1998 20:56:24 -0500 To: John Polstra From: "Jeffrey J. Mountin" Subject: Re: 3.0 missing some docs? Cc: current@FreeBSD.ORG In-Reply-To: <199810240117.SAA01142@austin.polstra.com> References: <3.0.3.32.19981023154926.007002b0@207.227.119.2> <3.0.3.32.19981023032536.0075034c@207.227.119.2> <3.0.3.32.19981023154926.007002b0@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:17 PM 10/23/98 -0700, John Polstra wrote: >I wonder if the difference could be caused by the new bootloader. >Have you tried booting an a.out kernel using the new boot code? >It would be interesting to find out whether the IRQ 7s came back >again. Got a chance to check on this and booted the old aout kernel with the new boot code, let the system run for about an hour, and no strays. They should have occured within 10 minutes of booting. Nada. The system is going to be wiped once more. I may be able to duplicate the strays with a fresh install. Should they come back a newer bios can be installed, which is what fixed the stray problem from a long time back. I'll post the results, but regardless the new boot code was probably long overdue and may have "fixed" something. However, one variable that did change. The CPU was downgraded from a P166 -> P133, but that wouldn't affect the strays would it? Would have been more correct to try before the CPU swap. It was needed for a trade, which means I now have a Tyan 1662D dual-PPro 200 w/128 and can keep current... faster. 8-) Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 19:27:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27509 for freebsd-current-outgoing; Sat, 24 Oct 1998 19:27:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27504 for ; Sat, 24 Oct 1998 19:27:53 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id TAA12585; Sat, 24 Oct 1998 19:27:07 -0700 (PDT) Message-ID: <19981024192707.C183@Alameda.net> Date: Sat, 24 Oct 1998 19:27:07 -0700 From: Ulf Zimmermann To: Mike Smith , "Stephen J. Roznowski" Cc: current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems Reply-To: ulf@Alameda.net References: <199810241850.OAA11330@istari.home.net> <199810241905.MAA05523@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810241905.MAA05523@dingo.cdrom.com>; from Mike Smith on Sat, Oct 24, 1998 at 12:05:34PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 24, 1998 at 12:05:34PM -0700, Mike Smith wrote: > > I just got done doing a fresh install of 3.0 and had a few problems. > > [These comments are from some jotted notes, and may be incomplete]: > > Thanks for these; it would of course have been nice to hear these back > before the release, but I guess we can alway try for next time. > > > 1) I have an "Intel EtherExpress Pro/10+" and was trying to do an FTP > > install (via a cable modem). I deleted all of the other network > > devices -- the card was recognized, but the install hung during > > the "adding route" step. > > The 'adding route' freeze irritates the *&^%( out of me. There are > several different things that can go wrong at this point and there's no > easy way to tell which one it is. I have problems with the 3.0-R install on a net 10 install. The company I work at uses 10.0/16 as the local address space and then a NAT/Firewall wall. Adding a default route to 10.0.1.1 hangs for ever, even with a nameserver configured. Installing with no DNS settings and using just plain IPs, the install works fine. > > > I occasionally had problems with my prior 3.0-current setup, where > > this card would be probed, but didn't seem to be working. A reboot > > (or two) usually fixes the problem. > > Did it fix the problem for you here ultimately? > > > 2) I was doing an install using the entire 2nd drive (da1) and not > > touching the MBR. After setup was finished, my /etc/fstab was > > incorrectly referencing the first drive (da0). Further, none of > > the /dev/da1s1? devices were made. > > This is one that Jordan will have to field; it looks like something has > forgotten the unit number somewhere along the way. Definitely bad. > > > 3) I installed the "netscape-navigator-4.07" port, and when I try to > > execute it, I get the following error: > > > > ld.so failed: Can't find shared library "libXt.so.6.0" > > I don't think that the a.out X libraries get installed by default. (I > could be wrong about this.) If there's nothing in /usr/X11R6/lib/aout, > then that's the problem. In that case, we'll need to provide them too. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 19:47:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28545 for freebsd-current-outgoing; Sat, 24 Oct 1998 19:47:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iworks.interworks.org (iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28540 for ; Sat, 24 Oct 1998 19:47:31 -0700 (PDT) (envelope-from deischen@iworks.interworks.org) Received: (from deischen@localhost) by iworks.interworks.org (8.8.7/8.8.7) id VAA06346; Sat, 24 Oct 1998 21:57:49 -0500 (CDT) Date: Sat, 24 Oct 1998 21:57:49 -0500 (CDT) From: "Daniel M. Eischen" Message-Id: <199810250257.VAA06346@iworks.interworks.org> To: tomppa@fidata.fi Subject: Re: 3.0 + CAM + xmcd-2.3 Cc: freebsd-current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I tried to use xmcd with my current system and it won't work. First I > compiled it from ports and then I also tried package but either one > can't see my cdrom. Xmcd worked fine with my 2.2-stable+cam system. > Has anybody got this work? It works OK for me. I just rebuilt it from ports just to be sure. My system is -current from Oct 18. Are you sure you're using the passN device? Dan Eischen deischen@iworks.InterWorks.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 20:44:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02114 for freebsd-current-outgoing; Sat, 24 Oct 1998 20:44:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup2.gaffaneys.com [208.155.161.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02109 for ; Sat, 24 Oct 1998 20:44:43 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id DAA04748; Sun, 25 Oct 1998 03:45:09 GMT (envelope-from zach) Message-ID: <19981024224509.A2339@znh.org> Date: Sat, 24 Oct 1998 22:45:09 -0500 From: Zach Heilig To: "Justin T. Gibbs" Cc: current@FreeBSD.ORG Subject: Re: cam and ncr ? Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: Your message of "Wed, 16 Sep 1998 11:28:47 -0600." <199809161735.LAA04593@pluto.plutotech.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know this message was OLD, but: >>>> ncr0: SCSI phase error fixup: CCB already dequeued >>>> ncr: timeout uccb ... (skip) >>>> from here on repeats endless with the "timeout" line > I can't seem to reproduce this one here on a DDRS drive. I did fix > another bug in the ncr driver though which may affect you. If rev > 1.126 doesn't address your problem, I'll try to poke around and add > some debugging info that may help me diagnose the problem. For what it's worth, I'm seeing this now as well (I first noticed Friday night Oct 23). Last system update was Oct 21 (and now Oct 24, to see if there was anything that fixed this). Before that was -current from Oct 10, which did not seem show these symptoms (there was only a one-line change.. Hm..). The only thing on that bus is my CD-R: ncr0: rev 0x04 int a irq 11 on pci0.13.0 cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed And this error message ncr0: SCSI phase error fixup: CCB already dequeued (0xf0a53400) ncr0: timeout nccb=0xf0a53400 (skip) ... ncr0: timeout nccb=0xf0a53400 (skip) (cd0:ncr0:0:5:0): lost device (cd0:ncr0:0:5:0): removing device entry ncr0: timeout nccb=0xf0a53400 (skip) ... After quite a while (hours), it eventually "resets" and is usable again. I notice there is at least one (audio) CD that will trigger this behavior 100% of the time. -- Zach Heilig If it looks like a duck, and quacks like a duck, we have to at least consider the possibility that we have a small aquatic bird of the family Anatidæ on our hands (Douglas Adams -- Dirk Gently's Holistic Detective Agency) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 20:54:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02739 for freebsd-current-outgoing; Sat, 24 Oct 1998 20:54:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02734 for ; Sat, 24 Oct 1998 20:54:21 -0700 (PDT) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.1/8.9.1) with ESMTP id XAA15319; Sat, 24 Oct 1998 23:53:39 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Sat, 24 Oct 1998 23:53:39 -0400 (EDT) From: "Alok K. Dhir" To: Craig Johnston cc: freebsd-current@FreeBSD.ORG Subject: Re: ELF XFree86 in ports In-Reply-To: <24B44A49A76D721D852566A7006EC52F.006D07A5852566A7@worldbank.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Its been working perfectly for me for weeks now... On Sat, 24 Oct 1998, Craig Johnston wrote: > Wanted to hear from anyone who's running ELF XFree86 from the ports > collection on -current. I'm running an aout installation right now -- I'd > like to upgrade but I really don't need to hose X. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 22:06:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07316 for freebsd-current-outgoing; Sat, 24 Oct 1998 22:06:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07311 for ; Sat, 24 Oct 1998 22:06:57 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id WAA18696; Sat, 24 Oct 1998 22:06:20 -0700 (PDT) Message-ID: <19981024220619.A12748@Alameda.net> Date: Sat, 24 Oct 1998 22:06:19 -0700 From: Ulf Zimmermann To: "Daniel M. Eischen" , tomppa@fidata.fi Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 + CAM + xmcd-2.3 Reply-To: ulf@Alameda.net References: <199810250257.VAA06346@iworks.interworks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810250257.VAA06346@iworks.interworks.org>; from Daniel M. Eischen on Sat, Oct 24, 1998 at 09:57:49PM -0500 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 24, 1998 at 09:57:49PM -0500, Daniel M. Eischen wrote: > > I tried to use xmcd with my current system and it won't work. First I > > compiled it from ports and then I also tried package but either one > > can't see my cdrom. Xmcd worked fine with my 2.2-stable+cam system. > > Has anybody got this work? > > It works OK for me. I just rebuilt it from ports just to > be sure. My system is -current from Oct 18. > > Are you sure you're using the passN device? I got the package to work, but only after installing Kerberus and DES libs. Wth does it need libdes.so.3 and libker.so.3 ? > > Dan Eischen > deischen@iworks.InterWorks.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 22:39:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09053 for freebsd-current-outgoing; Sat, 24 Oct 1998 22:39:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles32.castles.com [208.214.165.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09048 for ; Sat, 24 Oct 1998 22:39:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA04006; Sat, 24 Oct 1998 22:42:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810250542.WAA04006@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: ulf@Alameda.net cc: Mike Smith , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems In-reply-to: Your message of "Sat, 24 Oct 1998 19:27:07 PDT." <19981024192707.C183@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 22:42:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > The 'adding route' freeze irritates the *&^%( out of me. There are > > several different things that can go wrong at this point and there's no > > easy way to tell which one it is. > > I have problems with the 3.0-R install on a net 10 install. The company I > work at uses 10.0/16 as the local address space and then a NAT/Firewall wall. > Adding a default route to 10.0.1.1 hangs for ever, even with a nameserver > configured. Installing with no DNS settings and using just plain IPs, the > install works fine. ... so it is the nameserver lookup that's the problem? Grr. I added the '-n' arg to try to work around this. 8( I presume 'route add default' works properly normally? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 22:56:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09526 for freebsd-current-outgoing; Sat, 24 Oct 1998 22:56:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09521 for ; Sat, 24 Oct 1998 22:56:19 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id WAA20530; Sat, 24 Oct 1998 22:55:41 -0700 (PDT) Message-ID: <19981024225541.B12748@Alameda.net> Date: Sat, 24 Oct 1998 22:55:41 -0700 From: Ulf Zimmermann To: Mike Smith Cc: "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems Reply-To: ulf@Alameda.net References: <19981024192707.C183@Alameda.net> <199810250542.WAA04006@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810250542.WAA04006@dingo.cdrom.com>; from Mike Smith on Sat, Oct 24, 1998 at 10:42:33PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 24, 1998 at 10:42:33PM -0700, Mike Smith wrote: > > > > > > The 'adding route' freeze irritates the *&^%( out of me. There are > > > several different things that can go wrong at this point and there's no > > > easy way to tell which one it is. > > > > I have problems with the 3.0-R install on a net 10 install. The company I > > work at uses 10.0/16 as the local address space and then a NAT/Firewall wall. > > Adding a default route to 10.0.1.1 hangs for ever, even with a nameserver > > configured. Installing with no DNS settings and using just plain IPs, the > > install works fine. > > ... so it is the nameserver lookup that's the problem? > > Grr. I added the '-n' arg to try to work around this. 8( I presume > 'route add default' works properly normally? Later I point to the name server via /etc/resolv.conf and have 10.0.1.1 in the /etc/rc.conf, works fine, no long delay at boot time. > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 24 23:16:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10874 for freebsd-current-outgoing; Sat, 24 Oct 1998 23:16:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10869 for ; Sat, 24 Oct 1998 23:16:50 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id XAA10643; Sat, 24 Oct 1998 23:16:11 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Terry Lambert cc: john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) In-reply-to: Your message of "Sat, 24 Oct 1998 22:42:15 -0000." <199810242242.PAA27859@usr01.primenet.com> Date: Sat, 24 Oct 1998 23:16:10 -0700 Message-ID: <10639.909296170@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When you are a passenger headed for an unavoidable car wreck, it's > still nice to know that someone is steering. Cold comfort indeed, perhaps, to have anyone pretending to do anything effective in avoiding an unavoidable solution. ;) > Still, even if the new file must stay, it would be nice to know > that at least it was the result of someone is steering, instead > of being the result of people not communicating. "Dear Terry, we were here and we waited for you, but you didn't show up. What happened? Signed - Jordan & Mark" This _was_ discussed in -current. I raised the issue of disabling things like kerberos authentication for kerberized binaries and setting the default password time. Discussion ensued. Code was thrown indiscriminately around. Things evolved and Mark subsequently committed the kerberos knob. The password knob remains to follow. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message