From owner-freebsd-current Sun Oct 11 00:33:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27980 for freebsd-current-outgoing; Sun, 11 Oct 1998 00:33: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 AAA27975 for ; Sun, 11 Oct 1998 00:33:41 -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 AAA10138; Sun, 11 Oct 1998 00:32:18 -0700 (PDT) Message-Id: <199810110732.AAA10138@implode.root.com> To: Manfred Antar cc: current@FreeBSD.ORG Subject: Re: Version 1.56 of if_fxp.c causes fatal trap 12 In-reply-to: Your message of "Sat, 10 Oct 1998 23:39:01 PDT." <4.1.19981010233724.00a4b820@192.168.0.1> From: David Greenman Reply-To: dg@root.com Date: Sun, 11 Oct 1998 00:32:18 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>With version 1.55 there is no problems with any of the above configurations >>>The motherboard is an Intel PR440FX with 2 200mhz-ppro and built in eithernet >> >> Please apply the attached patch and let me know if it fixes the problem >>for you. Thanks. >> >>-DG >> >>David Greenman >>Co-founder/Principal Architect, The FreeBSD Project >> >>Index: if_fxp.c >>=================================================================== >>RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v >>retrieving revision 1.55 >>diff -c -r1.55 if_fxp.c >>*** if_fxp.c 1998/08/04 08:53:12 1.55 >>--- if_fxp.c 1998/10/11 06:08:30 >>*************** >>*** 641,646 **** >>--- 641,647 ---- >> M_DEVBUF, M_NOWAIT); >> if (sc->cbl_base == NULL) >> goto fail; >>+ bzero(sc->cbl_base, sizeof(struct fxp_cb_tx) * FXP_NTXCB); >> >> sc->fxp_stats = malloc(sizeof(struct fxp_stats), M_DEVBUF, M_NOWAIT); >> if (sc->fxp_stats == NULL) >> >I applied the patch to version 1.55 and just make an elf kernel >It booted without a problem Actually, I wanted you to apply it to rev 1.56. We already know that rev 1.55 works okay for you. Alternatively, you can just update to -current (rev 1.57 of if_fxp.c) since I've already committed the fix. -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 11 00:38:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28327 for freebsd-current-outgoing; Sun, 11 Oct 1998 00:38:43 -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 AAA28311 for ; Sun, 11 Oct 1998 00:38:40 -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 RAA17061; Sun, 11 Oct 1998 17:38:27 +1000 Date: Sun, 11 Oct 1998 17:38:27 +1000 From: Bruce Evans Message-Id: <199810110738.RAA17061@godzilla.zeta.org.au> To: garbanzo@hooked.net, mark@grondar.za Subject: Re: /usr/include/sys/cam/scsi... Cc: current@FreeBSD.ORG, perlsta@fs3.ny.genx.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This kinda piqued my interest, I've been cvsuping and making world, but >> I'm still left with a scsi.h, and a bunch of header files in /usr/include >> with old datestamps. How can I tell what files should have been cleaned >> out? >> 1) read commit mail, etc., or 2) rm -rf lots of files and reinstall, or 3) install in a temporary directory and compare what you have with what gets installed, or ... >cd /usr/include; find . -type f -ctime +N -delete > >Where N (in days) is chosen to be a bit longer than the number of days >between now and your last "make world". Don't do that. Includes are installed by `install -C', so most of them should be very old. 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 11 00:43:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28685 for freebsd-current-outgoing; Sun, 11 Oct 1998 00:43:36 -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 AAA28673 for ; Sun, 11 Oct 1998 00:43:31 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:y2YUJsnhpGUJUwdHRQ73QE325krzXkhH@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id JAA22541; Sun, 11 Oct 1998 09:42:52 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810110742.JAA22541@gratis.grondar.za> To: Bruce Evans cc: garbanzo@hooked.net, current@FreeBSD.ORG, perlsta@fs3.ny.genx.net Subject: Re: /usr/include/sys/cam/scsi... In-Reply-To: Your message of " Sun, 11 Oct 1998 17:38:27 +1000." <199810110738.RAA17061@godzilla.zeta.org.au> References: <199810110738.RAA17061@godzilla.zeta.org.au> Date: Sun, 11 Oct 1998 09:42:50 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >cd /usr/include; find . -type f -ctime +N -delete > > > >Where N (in days) is chosen to be a bit longer than the number of days > >between now and your last "make world". > > Don't do that. Includes are installed by `install -C', so most of them > should be very old. Huh!!?? Why does it work, then? 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 Sun Oct 11 00:56:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29650 for freebsd-current-outgoing; Sun, 11 Oct 1998 00:56:58 -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 AAA29645 for ; Sun, 11 Oct 1998 00:56:54 -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 AAA00289; Sun, 11 Oct 1998 00:56:38 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <4.1.19981011005524.00a54420@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 11 Oct 1998 00:56:39 -0700 To: dg@root.com From: Manfred Antar Subject: Re: Version 1.56 of if_fxp.c causes fatal trap 12 Cc: current@FreeBSD.ORG In-Reply-To: <199810110732.AAA10138@implode.root.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 12:32 AM 10/11/98 -0700, David Greenman wrote: >>>>With version 1.55 there is no problems with any of the above configurations >>>>The motherboard is an Intel PR440FX with 2 200mhz-ppro and built in >eithernet >>> >>> Please apply the attached patch and let me know if it fixes the problem >>>for you. Thanks. >>> >>>-DG >>> >>>David Greenman >>>Co-founder/Principal Architect, The FreeBSD Project >>> >>>Index: if_fxp.c >>>=================================================================== >>>RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v >>>retrieving revision 1.55 >>>diff -c -r1.55 if_fxp.c >>>*** if_fxp.c 1998/08/04 08:53:12 1.55 >>>--- if_fxp.c 1998/10/11 06:08:30 >>>*************** >>>*** 641,646 **** >>>--- 641,647 ---- >>> M_DEVBUF, M_NOWAIT); >>> if (sc->cbl_base == NULL) >>> goto fail; >>>+ bzero(sc->cbl_base, sizeof(struct fxp_cb_tx) * FXP_NTXCB); >>> >>> sc->fxp_stats = malloc(sizeof(struct fxp_stats), M_DEVBUF, M_NOWAIT); >>> if (sc->fxp_stats == NULL) >>> >>I applied the patch to version 1.55 and just make an elf kernel >>It booted without a problem > > Actually, I wanted you to apply it to rev 1.56. We already know that rev >1.55 works okay for you. Alternatively, you can just update to -current (rev >1.57 of if_fxp.c) since I've already committed the fix. > I was wondering if that's what you wanted. Anyway rev. 1.57 works fine Thanks 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 Sun Oct 11 01:03:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00227 for freebsd-current-outgoing; Sun, 11 Oct 1998 01:03:34 -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 BAA00218 for ; Sun, 11 Oct 1998 01:03:29 -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 KAA09151; Sun, 11 Oct 1998 10:03:10 +0200 (SAT) From: John Hay Message-Id: <199810110803.KAA09151@zibbi.mikom.csir.co.za> Subject: Re: /usr/include/sys/cam/scsi... In-Reply-To: <199810110742.JAA22541@gratis.grondar.za> from Mark Murray at "Oct 11, 98 09:42:50 am" To: mark@grondar.za (Mark Murray) Date: Sun, 11 Oct 1998 10:03:10 +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 > > >cd /usr/include; find . -type f -ctime +N -delete > > > > > >Where N (in days) is chosen to be a bit longer than the number of days > > >between now and your last "make world". > > > > Don't do that. Includes are installed by `install -C', so most of them > > should be very old. > > Huh!!?? Why does it work, then? Because you did a make installworld (or something to that effect) just after that? (Or at least before you needed one of the includes that you have deleted.) What I do once in a while to get rid of old stuff is something like this: cd /usr/src make world mv /usr/include /usr/include.old mv /usr/share /usr/share.old make -m share/mk installworld rm -rf /usr/include.old /usr/share.old This will give me a clean /usr/include and /usr/share. Then for the rest of the directories (/bin /sbin /lkm /usr/{bin,sbin,libdata,libexec,lib}) I just look for the old ones and remove them with find. 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 11 01:04:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00307 for freebsd-current-outgoing; Sun, 11 Oct 1998 01:04:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00298 for ; Sun, 11 Oct 1998 01:04:20 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:L5Vg8msHSMX6qLzDJV3cf5vuZAdJPs6H@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id RAA04121 for ; Sun, 11 Oct 1998 17:04:10 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id RAA09175; Sun, 11 Oct 1998 17:05:21 +0900 (JST) Message-Id: <199810110805.RAA09175@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.ORG cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: PS/2 mouse problem with 440BX chipset? Date: Sun, 11 Oct 1998 17:05:20 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There recently was a report that the PS/2 mouse is not recognized on a 440BX-based motherboard. The problem was reported with 2.2.7-RELEASE, but 3.0-CURRENT may have the same difficulty (because the PS/2 mouse driver is almost identical in both versions). When you enable the psm driver and boot the kernel, giving -v option at the "boot:" prompt, you may see: psm0: current command byte:0047 kbdio: TEST_AUX_PORT status:00fa ~~~~ kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:00fa ~~~~ psm: keyboard port failed. psm0: the aux port is not functioning (250). psm0 not found at 0x60 I don't know if this problem is present in 440BX-based system in general, or it is peculiar to this specific motherboard. Please contact me if you have a 440BX-based system and tell me if you have the same problem or not. Thank you Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 01:25:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01981 for freebsd-current-outgoing; Sun, 11 Oct 1998 01:25:30 -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 BAA01973 for ; Sun, 11 Oct 1998 01:25: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 SAA19450; Sun, 11 Oct 1998 18:25:04 +1000 Date: Sun, 11 Oct 1998 18:25:04 +1000 From: Bruce Evans Message-Id: <199810110825.SAA19450@godzilla.zeta.org.au> To: bde@zeta.org.au, mark@grondar.za Subject: Re: /usr/include/sys/cam/scsi... Cc: current@FreeBSD.ORG, garbanzo@hooked.net, perlsta@fs3.ny.genx.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >cd /usr/include; find . -type f -ctime +N -delete >> > >> >Where N (in days) is chosen to be a bit longer than the number of days >> >between now and your last "make world". >> >> Don't do that. Includes are installed by `install -C', so most of them >> should be very old. > >Huh!!?? Why does it work, then? Oops. It does work. `install -C' should attempt to avoid modifying ctimes, since incremental backups should be based on ctimes, so modifying ctimes mainly bloats such backups. I forgot that it doesn't actually avoid modifying them. It always does the following operations on the target file: fchown(), fchmod(), fchflags(); and at least some of these are required to clobber the ctime even when nothing has changed. 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 11 01:31:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02311 for freebsd-current-outgoing; Sun, 11 Oct 1998 01:31:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgate.aist-nara.ac.jp (fse4.aist-nara.ac.jp [163.221.76.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02301 for ; Sun, 11 Oct 1998 01:31:48 -0700 (PDT) (envelope-from takas-su@is.aist-nara.ac.jp) Received: from decpc20.aist-nara.ac.jp (decpc20.aist-nara.ac.jp [163.221.172.33]) by mailgate.aist-nara.ac.jp (8.8.5+2.7Wbeta5/3.6W/NAIST/GATE-3.4c-fake) with ESMTP id RAA14244 for ; Sun, 11 Oct 1998 17:31:13 +0900 (JST) Received: from is (takas-su@localhost) by decpc20.aist-nara.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl5/NAIST/2.0) id RAA09462; Sun, 11 Oct 1998 17:32:11 +0900 (JST) Date: Sun, 11 Oct 1998 17:32:11 +0900 (JST) Message-Id: <199810110832.RAA09462@decpc20.aist-nara.ac.jp> From: takas-su@is.aist-nara.ac.jp (SUGIMURA Takashi/ =?ISO-2022-JP?B?GyRCP3lCPDUuO04bKEI=?=) To: current@FreeBSD.ORG Subject: make buildworld fails Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For last few days, make buildworld fails at the last stage. -------------------------------------------------------------- >>> Building legacy boot -------------------------------------------------------------- (snip) ===> i386/btx ===> i386/btx/btx Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/btx ===> i386/btx/btxldr Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/btxldr ===> i386/btx/lib ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o btxcsu.o: file not recognized: File format not recognized *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Thanks in advance, --- SUGIMURA Takashi (takas-su@is.aist-nara.ac.jp) URL: http://hawk.aist-nara.ac.jp/%7Etakas-su/ (sorry only in Japanese) Software Engineering lab. of NAIST, 2nd grade of Master, The FreeBSD Japanese Documentation 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 11 01:57:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03811 for freebsd-current-outgoing; Sun, 11 Oct 1998 01:57:53 -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 BAA03806 for ; Sun, 11 Oct 1998 01:57:44 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:M96hRVVpVQ3gxk3xdlQMGByOk3GZ0fPM@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id KAA22775; Sun, 11 Oct 1998 10:57:25 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810110857.KAA22775@gratis.grondar.za> To: John Hay cc: current@FreeBSD.ORG Subject: Re: /usr/include/sys/cam/scsi... In-Reply-To: Your message of " Sat, 11 Oct 1998 10:03:10 +0200." <199810110803.KAA09151@zibbi.mikom.csir.co.za> References: <199810110803.KAA09151@zibbi.mikom.csir.co.za> Date: Sun, 11 Oct 1998 10:57:22 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > > Huh!!?? Why does it work, then? > > Because you did a make installworld (or something to that effect) just > after that? (Or at least before you needed one of the includes that you > have deleted.) Nope. I use this procedure regularly, and I often check it by leaving off the -delete to see what will go; this is always reasonable. 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 Sun Oct 11 02:12:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05071 for freebsd-current-outgoing; Sun, 11 Oct 1998 02:12:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-34-dbn.dial-up.net [196.34.155.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05044 for ; Sun, 11 Oct 1998 02:12:09 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA22467; Sun, 11 Oct 1998 11:10:08 +0200 (SAT) From: Robert Nordier Message-Id: <199810110910.LAA22467@ceia.nordier.com> Subject: Re: make buildworld fails In-Reply-To: <199810110832.RAA09462@decpc20.aist-nara.ac.jp> from "SUGIMURA Takashi/ [?ISO-2022-JP?]" at "Oct 11, 98 05:32:11 pm" To: takas-su@is.aist-nara.ac.jp Date: Sun, 11 Oct 1998 11:10:05 +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 SUGIMURA Takashi wrote: > For last few days, make buildworld fails at the last stage. > > -------------------------------------------------------------- > >>> Building legacy boot > -------------------------------------------------------------- > (snip) > ===> i386/btx > ===> i386/btx/btx > Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/btx > ===> i386/btx/btxldr > Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/btxldr > ===> i386/btx/lib > ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o > btxcsu.o: file not recognized: File format not recognized > *** Error code 1 Should be fixed by /usr/src/Makefile.inc1 1.29. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 02:30:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06068 for freebsd-current-outgoing; Sun, 11 Oct 1998 02:30:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgate.aist-nara.ac.jp (fse4.aist-nara.ac.jp [163.221.76.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06063 for ; Sun, 11 Oct 1998 02:30:16 -0700 (PDT) (envelope-from takas-su@is.aist-nara.ac.jp) Received: from decpc20.aist-nara.ac.jp (decpc20.aist-nara.ac.jp [163.221.172.33]) by mailgate.aist-nara.ac.jp (8.8.5+2.7Wbeta5/3.6W/NAIST/GATE-3.4c-fake) with ESMTP id SAA00094 for ; Sun, 11 Oct 1998 18:29:35 +0900 (JST) Received: from is (takas-su@localhost) by decpc20.aist-nara.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl5/NAIST/2.0) id SAA09520; Sun, 11 Oct 1998 18:30:34 +0900 (JST) Date: Sun, 11 Oct 1998 18:30:34 +0900 (JST) Message-Id: <199810110930.SAA09520@decpc20.aist-nara.ac.jp> From: takas-su@is.aist-nara.ac.jp (SUGIMURA Takashi/ =?ISO-2022-JP?B?GyRCP3lCPDUuO04bKEI=?=) To: current@FreeBSD.ORG Subject: Re: make buildworld fails In-Reply-To: Your message of "Sun, 11 Oct 1998 11:10:05 +0200 (SAT)". <199810110910.LAA22467@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article of <199810110910.LAA22467@ceia.nordier.com>, rnordier@nordier.com wrote: >> Should be fixed by /usr/src/Makefile.inc1 1.29. >> nnn.. It is 1.29. ryo2402 # cat /usr/src/Makefile.inc1 | grep Id: # $Id: Makefile.inc1,v 1.29 1998/10/10 19:56:59 jkh Exp $ And, make buildworld contains "make legacy-build", is it needed for ELF system? ryo2402# make -n -f Makefile.inc0 -m /usr/src/share/mk buildworld cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/elf make -m /usr/src/share/mk -f Makefile.inc1 buildworld cd /usr/src; PATH=/usr/obj/elf/usr/src/tmp/sbin:/usr/obj/elf/usr/src/tmp/bin:/usr/obj/elf/usr/src/tmp/usr/sbin:/usr/obj/elf/usr/src/tmp/usr/bin:/usr/obj/elf/usr/src/tmp/usr/games OBJFORMAT=aout NOTOOLS=1 TOOLROOT=/usr/obj/elf/usr/src/tmp MAKEOBJDIRPREFIX=/usr/obj/aout /usr/obj/elf/usr/src/tmp/usr/bin/make -m /usr/src/share/mk -f Makefile.inc1 legacy-build On the second process of this, why OBJFORMAT=aout? It seems strange that PATH is for ELF but OBJFORMAT=aout, I think. Of course /etc/objformat is right, other previous making stage is done properly for ELF. --- SUGIMURA Takashi (takas-su@is.aist-nara.ac.jp) URL: http://hawk.aist-nara.ac.jp/%7Etakas-su/ (sorry only in Japanese) Software Engineering lab. of NAIST, 2nd grade of Master, The FreeBSD Japanese Documentation 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 11 03:04:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA08113 for freebsd-current-outgoing; Sun, 11 Oct 1998 03:04:40 -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 DAA08091 for ; Sun, 11 Oct 1998 03:04:29 -0700 (PDT) (envelope-from ozz.etrust.ru!etrust.ru!osa@serv.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 OAA01503 for ; Sun, 11 Oct 1998 14:04:17 +0400 (MSD) Received: by sunny.aha.ru id OAA22542; (8.8.8/vak/1.9) Sun, 11 Oct 1998 14:03:31 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma022529; Sun Oct 11 14:03:27 1998 Received: from ozz.etrust.ru by serv.etrust.ru with ESMTP id OAA21827; (8.9.1/vak/1.9) Sun, 11 Oct 1998 14:06:14 +0400 (MSD) Received: from localhost by ozz.etrust.ru with ESMTP id OAA07399; (8.9.1/vak/1.9) Sun, 11 Oct 1998 14:06:52 +0400 (MSD) Date: Sun, 11 Oct 1998 14:06:51 +0400 (MSD) From: oZZ!!! To: current@FreeBSD.ORG Subject: make buildworld is dead... 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! I use FreeBSD-3.0-BETA-ELF. Last cvsup - 11.10.1998 05:10 MSD # make buildworld ........ ........ ===> i386/btx/lib ld -elf -i -o crt.0 btxcsu.o btxsys.o btxv86.o btxcsu.o: file not recognized: File format not recognized *** Error code 1 Stop. ......... ......... What does it mean ? How i may doing # make world ? 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 Sun Oct 11 03:24:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10506 for freebsd-current-outgoing; Sun, 11 Oct 1998 03:24:12 -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 DAA10455 for ; Sun, 11 Oct 1998 03:24:01 -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 DAA04058; Sun, 11 Oct 1998 03:22:53 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <362086FC.A755F7D7@gorean.org> Date: Sun, 11 Oct 1998 03:22:52 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1009 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Hay CC: Mark Murray , current@FreeBSD.ORG Subject: Re: /usr/include/sys/cam/scsi... References: <199810110803.KAA09151@zibbi.mikom.csir.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > > > > >cd /usr/include; find . -type f -ctime +N -delete > > > > > > > >Where N (in days) is chosen to be a bit longer than the number of days > > > >between now and your last "make world". > > > > > > Don't do that. Includes are installed by `install -C', so most of them > > > should be very old. > > > > Huh!!?? Why does it work, then? > > Because you did a make installworld (or something to that effect) just > after that? (Or at least before you needed one of the includes that you > have deleted.) > > What I do once in a while to get rid of old stuff is something like this: > > cd /usr/src > make world > mv /usr/include /usr/include.old > mv /usr/share /usr/share.old > make -m share/mk installworld > rm -rf /usr/include.old /usr/share.old > > This will give me a clean /usr/include and /usr/share. Then for the rest > of the directories (/bin /sbin /lkm /usr/{bin,sbin,libdata,libexec,lib}) > I just look for the old ones and remove them with find. You can take care of /usr/include by doing 'make -DCLOBBER world'. I've long thought it would be nice to have similar targets for other directories, especially /usr/lib and the various binary directories. Of course it's easy to do with find, although I'd prefer to avoid the extra step. 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 Sun Oct 11 03:28:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11017 for freebsd-current-outgoing; Sun, 11 Oct 1998 03:28:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peotl.tuebingen.netsurf.de (host-383.tuebingen.netsurf.de [195.180.140.183]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA10915 for ; Sun, 11 Oct 1998 03:28:15 -0700 (PDT) (envelope-from thz@tuebingen.netsurf.de) Received: (from thz@localhost) by peotl.tuebingen.netsurf.de (8.8.8/8.8.8) id MAA00686; Sun, 11 Oct 1998 12:27:32 +0200 (MET DST) (envelope-from thz) Message-ID: <19981011122731.40870@tuebingen.netsurf.de> Date: Sun, 11 Oct 1998 12:27:31 +0200 From: Thomas Zenker To: current@FreeBSD.ORG Subject: system hangs on concurrent rm Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a running two concurrent "rm -rf " in obj tree the two processes locked up. This is on 3.0 current cvsupped at 7. Oct. With SOFTUPDATES enabled, including the changes of 3. of Oct. The disk this happened on is a SCSI disk (IBM DCAS). No other active processes were running, also disk activity only on this disk. I could switch vtys, but was unable to login. It seemed to me that both processes were blocked in the kernel, any process accessing filesystem or disk blocked immediately also. I left the system alone for a while, in case it there would have been a lockup on the SCSI bus it would have run into a timeout. Getting status with ^T showed me load avr going down to 0, after trying the tree finger magic to reboot, ^T showed a little load which went down quickly, but no disk activity. So did it the hard way, reset. It costed 4 hours of fsck to recover :-( but recovered :-) The problem with fsck was, that the lost+found directory got full quickly (nearly a whole obj tree), so fsck choked, only chance was fsck -y which was very slow obviously. Thomas Zenker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 04:01:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA15369 for freebsd-current-outgoing; Sun, 11 Oct 1998 04:01:36 -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 EAA15344 for ; Sun, 11 Oct 1998 04:01:20 -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 VAA10456 for current@FreeBSD.ORG; Sun, 11 Oct 1998 21:00:55 +1000 (EST) Date: Sun, 11 Oct 1998 21:00:55 +1000 (EST) From: Tony Maher Message-Id: <199810111100.VAA10456@morgan.angis.su.OZ.AU> To: current@FreeBSD.ORG Subject: scsi message Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, after last cvsup and make world (around Oct 10 5:00 GMT) on shutdown it now reports: syncing disk ... 3 3 done. (da1:ahc0:0:1:0): SYNCHRONISE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc0:0:1:0): ILLEGAL REQUEST asc:20,0 (da1:ahc0:0:1:0): Invalid command operation code sks:c0,0 So booting -v --------------------------------------------------------------------------- ahc0: target 0 synchronous at 10.0MHz, offset = 0xf ahc0: target 2 synchronous at 10.0MHz, offset = 0xf (probe6:ahc0:0:6:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe6:ahc0:0:6:0): ILLEGAL REQUEST asc:24,0 (probe6:ahc0:0:6:0): Invalid field in CDB ahc0: target 6 synchronous at 5.0MHz, offset = 0xf ahc0: target 6 using asynchronous transfers ahc0: target 6 synchronous at 5.0MHz, offset = 0xf (probe1:ahc0:0:1:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe1:ahc0:0:1:0): ILLEGAL REQUEST asc:24,0 (probe1:ahc0:0:1:0): Invalid field in CDB sks:c8,1 ahc0: target 1 synchronous at 10.0MHz, offset = 0xf ... pass1: Fixed Direct Access SCSI2 device pass1: 10.0MB/s transfers (10.0MHz, offset 15) --------------------------------------------------------------------------- Ok Id 6 is CDROM no problems Id 1 is the FreeBSD disk and it works fine apart from the fact it doesn't do tagged queuing (as reported Thu Sep 17). All the disk scsi params are at the default settings. As I read it from the Seagate Medalist Pro 2160N Product Manual, Rev B the CDB (command Descriptor Block) is 12 Inquiry Command 1 Enable Vital Product Data (1 means enabled) 80 The page of the vital product information (since EVPD is set) 0 page code continued ff Allocation length in bytes 0 a CDB must end in zero According to the manual this looks like a valid CDB but ... it reports Illegal Request error code 24,0 which is "The drive received a CDB that contains an invalid bit" And how do you interpret "invalid field c8,1"? This probably explains why the disk doesn't do tagged queuing. System is working ok, but if I could get rid of the message and get tagged queuing it would be nice. A quirk entry? thanks tonym To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 04:36:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19178 for freebsd-current-outgoing; Sun, 11 Oct 1998 04:36:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-47-dbn.dial-up.net [196.34.155.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19167 for ; Sun, 11 Oct 1998 04:36:19 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA23073; Sun, 11 Oct 1998 13:34:51 +0200 (SAT) From: Robert Nordier Message-Id: <199810111134.NAA23073@ceia.nordier.com> Subject: Re: make buildworld fails In-Reply-To: <199810110930.SAA09520@decpc20.aist-nara.ac.jp> from "SUGIMURA Takashi/ [?ISO-2022-JP?]" at "Oct 11, 98 06:30:34 pm" To: takas-su@is.aist-nara.ac.jp (SUGIMURA Takashi/ =?ISO-2022-JP?B?GyRCP3lCPDUuO04bKEI=?=) Date: Sun, 11 Oct 1998 13:34:40 +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 SUGIMURA Takashi/ [?ISO-2022-JP?] wrote: > In article of <199810110910.LAA22467@ceia.nordier.com>, > rnordier@nordier.com wrote: > >> Should be fixed by /usr/src/Makefile.inc1 1.29. > >> > > nnn.. It is 1.29. > > ryo2402 # cat /usr/src/Makefile.inc1 | grep Id: > # $Id: Makefile.inc1,v 1.29 1998/10/10 19:56:59 jkh Exp $ OK. I've committed a fix. Try it with /usr/src/sys/boot/i386/btx/lib/Makefile 1.2. > And, make buildworld contains "make legacy-build", > is it needed for ELF system? At the moment, yes. > ryo2402# make -n -f Makefile.inc0 -m /usr/src/share/mk buildworld > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/elf make -m /usr/src/share/mk -f Makefile.inc1 buildworld > cd /usr/src; PATH=/usr/obj/elf/usr/src/tmp/sbin:/usr/obj/elf/usr/src/tmp/bin:/usr/obj/elf/usr/src/tmp/usr/sbin:/usr/obj/elf/usr/src/tmp/usr/bin:/usr/obj/elf/usr/src/tmp/usr/games OBJFORMAT=aout NOTOOLS=1 TOOLROOT=/usr/obj/elf/usr/src/tmp MAKEOBJDIRPREFIX=/usr/obj/aout /usr/obj/elf/usr/src/tmp/usr/bin/make -m /usr/src/share/mk -f Makefile.inc1 legacy-build > > > On the second process of this, why OBJFORMAT=aout? > It seems strange that PATH is for ELF but OBJFORMAT=aout, I think. The /sys/i386/boot code understands only aout. > > Of course /etc/objformat is right, > other previous making stage is done properly for ELF. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 04:43:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19644 for freebsd-current-outgoing; Sun, 11 Oct 1998 04:43:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-47-dbn.dial-up.net [196.34.155.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19637 for ; Sun, 11 Oct 1998 04:43:39 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA23266; Sun, 11 Oct 1998 13:41:59 +0200 (SAT) From: Robert Nordier Message-Id: <199810111141.NAA23266@ceia.nordier.com> Subject: Re: make buildworld is dead... In-Reply-To: from ! at "Oct 11, 98 02:06:51 pm" To: osa@etrust.ru Date: Sun, 11 Oct 1998 13:41:57 +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: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA19640 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oZZ!!! wrote: > > Hello! > I use FreeBSD-3.0-BETA-ELF. > Last cvsup - 11.10.1998 05:10 MSD > # make buildworld > ........ ........ ===> i386/btx/lib > ld -elf -i -o crt.0 btxcsu.o btxsys.o btxv86.o > btxcsu.o: file not recognized: File format not recognized > *** Error code 1 > > Stop. > ......... ......... What does it mean ? > How i may doing # make world ? I've committed a fix (sys/boot/i386/btx/lib/Makefile). Try it again. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 04:53:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20347 for freebsd-current-outgoing; Sun, 11 Oct 1998 04:53:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgate.aist-nara.ac.jp (fse4.aist-nara.ac.jp [163.221.76.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20342 for ; Sun, 11 Oct 1998 04:53:42 -0700 (PDT) (envelope-from takas-su@is.aist-nara.ac.jp) Received: from decpc20.aist-nara.ac.jp (decpc20.aist-nara.ac.jp [163.221.172.33]) by mailgate.aist-nara.ac.jp (8.8.5+2.7Wbeta5/3.6W/NAIST/GATE-3.4c-fake) with ESMTP id UAA07813 for ; Sun, 11 Oct 1998 20:53:07 +0900 (JST) Received: from is (takas-su@localhost) by decpc20.aist-nara.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl5/NAIST/2.0) id UAA09603; Sun, 11 Oct 1998 20:54:06 +0900 (JST) Date: Sun, 11 Oct 1998 20:54:06 +0900 (JST) Message-Id: <199810111154.UAA09603@decpc20.aist-nara.ac.jp> From: takas-su@is.aist-nara.ac.jp (SUGIMURA Takashi/ =?ISO-2022-JP?B?GyRCP3lCPDUuO04bKEI=?=) To: current@FreeBSD.ORG Subject: Re: make buildworld fails In-Reply-To: Your message of "Sun, 11 Oct 1998 13:34:40 +0200 (SAT)". <199810111134.NAA23073@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article of <199810111134.NAA23073@ceia.nordier.com>, rnordier@nordier.com wrote: >> OK. I've committed a fix. Try it with >> /usr/src/sys/boot/i386/btx/lib/Makefile 1.2. >> Sure. I will test it again after I can get it. >> > And, make buildworld contains "make legacy-build", >> > is it needed for ELF system? >> >> At the moment, yes. >> I see. Thank you very much. --- SUGIMURA Takashi (takas-su@is.aist-nara.ac.jp) URL: http://hawk.aist-nara.ac.jp/%7Etakas-su/ (sorry only in Japanese) Software Engineering lab. of NAIST, 2nd grade of Master, The FreeBSD Japanese Documentation 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 11 07:21:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28923 for freebsd-current-outgoing; Sun, 11 Oct 1998 07:21:37 -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 HAA28918 for ; Sun, 11 Oct 1998 07:21:35 -0700 (PDT) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id KAA02541; Sun, 11 Oct 1998 10:20:51 -0400 (EDT) To: freebsd-current@FreeBSD.ORG Subject: What is a BSP, and why does SMP panic about it? 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: 11 Oct 1998 10:20:50 -0400 Message-ID: Lines: 33 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This may be more properly sent to the SMP list... I have an Intel DK440LX motherboard with 1 CPU (the second is on order). I decided to try making the kernel with SMP turned on, to make sure everything works before plugging in the second CPU. One of the SMP web pages seemed to imply that one could run a SMP kernel on a uniprocessor box, with some performance degredation. >From my config file: #SMP: options SMP options APIC_IO options NCPU=1 options NBUS=3 options NAPIC=1 options NINTR=24 When I attempted to boot, I got a panic: no BSP found. Uh, what is a BSP, and where can they be found? Thanks, +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 Sun Oct 11 07:32:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29587 for freebsd-current-outgoing; Sun, 11 Oct 1998 07:32:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cockatoo.aus.org (cockatoo.aus.org [199.166.246.189]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29571 for ; Sun, 11 Oct 1998 07:32:29 -0700 (PDT) (envelope-from lh@cockatoo.aus.org) Received: (from lh@localhost) by cockatoo.aus.org (8.8.8/8.8.8) id KAA00672; Sun, 11 Oct 1998 10:32:16 -0400 (EDT) (envelope-from lh) Message-ID: X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 11 Oct 1998 10:32:16 -0400 (EDT) From: Luke To: current@FreeBSD.ORG Subject: libm typo Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hi I just cvsupd src/lib/libm/common_source/lgamma.c (twice to make sure) there seems to be a extra /* @line 94 (should i post this here or somewhere else?) - --- E-Mail: Luke Sent by XFMail - ---------------------------------- -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNiDBcO6GmDnHtZHpAQEQXwQAnthTlguWZORf1D6NgcqaIdVuPFGCxEmJ GCPRov58pz4cQREjoH/in4EXr4D+/aPJALEMEruYdJaupykK9A1iByXqrmDMNn4k RI90zkUvX5/C9/hPJ6kC6oYMwjMkw6qNBnfB0muils2iZ3HBn0dt7Dr52PpSclVe Du7aCIGyz9s= =E8yP -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 08:08:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03906 for freebsd-current-outgoing; Sun, 11 Oct 1998 08:08:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from online.no (pilt-s.online.no [193.212.1.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03882 for ; Sun, 11 Oct 1998 08:08:39 -0700 (PDT) (envelope-from zerium@webindex.no) Received: from zerium.dyn.ml.org (ti34a24-0114.dialup.online.no [130.67.64.242]) by online.no (8.9.1/8.9.1) with ESMTP id RAA13166; Sun, 11 Oct 1998 17:08:25 +0200 (MET DST) Received: from localhost (zerium@localhost) by zerium.dyn.ml.org (8.9.1/8.9.1) with SMTP id RAA08149; Sat, 10 Oct 1998 17:14:16 +0200 (CEST) (envelope-from zerium@zerium.dyn.ml.org) Date: Sat, 10 Oct 1998 17:14:16 +0200 (CEST) From: Hans Petter Bieker X-Sender: zerium@zerium.dyn.ml.org To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: Locales? 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 9 Oct 1998, Cory Kempf wrote: > I tried reading perllocale(1), and set the LC_ALL and LANG shell > variables, but I still get the error messages. FWIW, en_US.ISO_8859.1 ^^ should be - $ LANG=en_US.ISO_8859-1; export LANG -bieker- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 08:54:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08368 for freebsd-current-outgoing; Sun, 11 Oct 1998 08:54:01 -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 IAA08342 for ; Sun, 11 Oct 1998 08:53:58 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id QAA26601 for ; Sun, 11 Oct 1998 16:53:36 +0100 (BST) Message-ID: <3620D44C.FF6E6143@tdx.co.uk> Date: Sun, 11 Oct 1998 16:52:44 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Makeworld breakage... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup'd (12:00 BST) and 'make buildworld' failed... Looking at recent messages I saw people said the bootloader may still have problems, so I cvs'upd again at 13:40 - and tried another build world... It failed as well.. The last cvsup I did was at around 15.00 - and showed a diff for the makefile of the bootstrap code... Unfortunately it still fails to build... I was careful to delete /usr/obj between builds (just in case)... Regards, Karl " Warning: Object directory not changed from original /usr/src/sys/boot/i386/loader --- vers.o --- sh /usr/src/sys/boot/i386/loader/newvers.sh /usr/src/sys/boot/i386/loader/version "bootstrap loader" head: not found tail: not found " (Which is slightly worrying, and further on...) " cc -c /usr/src/sys/boot/i386/loader/../../common/gensetdefs.c --- gensetdefs --- cc -static gensetdefs.o -o gensetdefs /usr/lib/crt1.o: In function `_start': /usr/lib/crt1.o(.text+0x2f): undefined reference to `atexit' /usr/lib/crt1.o(.text+0x3c): undefined reference to `atexit' /usr/lib/crt1.o(.text+0x4f): undefined reference to `exit' gensetdefs.o: In function `main': gensetdefs.o(.text+0x7d): undefined reference to `printf' gensetdefs.o(.text+0x94): undefined reference to `free' gensetdefs.o(.text+0xa0): undefined reference to `free' gensetdefs.o: In function `enter': gensetdefs.o(.text+0x10e): undefined reference to `strcmp' gensetdefs.o: In function `enter_sets': [SNIP loads of 'undefined references' deleted ] *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 08:55:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08552 for freebsd-current-outgoing; Sun, 11 Oct 1998 08:55:41 -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 IAA08527 for ; Sun, 11 Oct 1998 08:55:36 -0700 (PDT) (envelope-from ozz.etrust.ru!etrust.ru!osa@serv.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 TAA08333 for ; Sun, 11 Oct 1998 19:55:21 +0400 (MSD) Received: by sunny.aha.ru id TAA01423; (8.8.8/vak/1.9) Sun, 11 Oct 1998 19:54:28 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma001401; Sun Oct 11 19:54:18 1998 Received: from ozz.etrust.ru by serv.etrust.ru with ESMTP id TAA22151; (8.9.1/vak/1.9) Sun, 11 Oct 1998 19:57:05 +0400 (MSD) Received: from localhost by ozz.etrust.ru with ESMTP id TAA14860; (8.9.1/vak/1.9) Sun, 11 Oct 1998 19:57:46 +0400 (MSD) Date: Sun, 11 Oct 1998 19:57:45 +0400 (MSD) From: oZZ!!! To: current@FreeBSD.ORG Subject: make world is DEAD! 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! I have FreeBSD-3.0-BETA-ELF. After today cvsup... # make world ....... ===> i386/btx/lib ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o btxcsu.o: file not recognized: File not recognized *** Error code 1 Stop. .... 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 Sun Oct 11 09:22:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10470 for freebsd-current-outgoing; Sun, 11 Oct 1998 09:22:22 -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 JAA10457 for ; Sun, 11 Oct 1998 09:22:19 -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 MAA03492 for ; Sun, 11 Oct 1998 12:22:08 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA03768; Sun, 11 Oct 1998 12:22:08 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id MAA07811 for freebsd-current@freebsd.org; Sun, 11 Oct 1998 12:22:08 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199810111622.MAA07811@bb01f39.unx.sas.com> Subject: aout 'make release' fails (boot0 problem) To: freebsd-current@FreeBSD.ORG Date: Sun, 11 Oct 1998 12:22:08 -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, On an aout system, 'make release' has been failing for the past few days as follows. I am current as of 2am EDT when this build was run. I know we've made alot of changes in the boot area so I held off saying anything. Would someone please check this out? Thanks! John -------------------------------------------------------------- >>> Installing legacy boot -------------------------------------------------------------- cd /usr/src/sys/boot && make -DNOMAN install ===> i386 ===> i386/boot0 install -c -o root -g wheel -m 555 boot0 /R/stage/trees/bin/boot install: boot0: No such file or directory *** Error code 71 Stop. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 09:33:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11578 for freebsd-current-outgoing; Sun, 11 Oct 1998 09:33:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pyrl.eye (ppp-140.isl.net [199.3.25.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11566 for ; Sun, 11 Oct 1998 09:33:52 -0700 (PDT) (envelope-from ortmann@sparc.isl.net) Received: (from ortmann@localhost) by pyrl.eye (8.9.1/8.9.1) id LAA01235 for freebsd-current@freebsd.org; Sun, 11 Oct 1998 11:33:37 -0500 (CDT) (envelope-from ortmann) From: Daniel Ortmann Message-Id: <199810111633.LAA01235@pyrl.eye> Subject: problems very slow time on -current? To: freebsd-current@FreeBSD.ORG Date: Sun, 11 Oct 1998 11:33:32 -0500 (CDT) 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 Is anyone able to clue me in on this problem? This time rate problem has been happening for the past several months. I was sure it is misconfiguration ... but I'm not sure. Symptoms: 1) My system time is running at (about) 50% of what it should. 2) The hardware clock is working fine. Date/time is ok on bootup. 3) When connected to the net xntpd keeps it adjusted ok. 4) After dropping the net the time gets slow again. 5) The problem happens even when not running xntpd. System: a) Vanilla Cyrix 586 IDE system. b) Running -current Elf with an aout kernel. The following text, grep'ped from /sys/i386/conf/LINT makes me wonder: # CPU_BLUELIGHTNING_3X enables triple-clock mode on IBM Blue Lightning # CPU if CPU supports it. The default is double-clock mode on # CPU_IORT defines I/O clock delay time (NOTE 1). Default vaules of # I/O clock delay time on Cyrix 5x86 and 6x86 are 0 and 7,respectively # (no clock delay). Thank you for any help you can provide! -- Daniel Ortmann 507.288.7732 (h) ortmann@isl.net 2414 30 av NW, #D 507.253.6795 (w) ortmann@vnet.ibm.com Rochester, MN 55901 "PERL: The Swiss Army Chainsaw" "The answers are so simple and we all know where to look, but it's easier just to avoid the question." -- Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 10:14:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14402 for freebsd-current-outgoing; Sun, 11 Oct 1998 10:14:27 -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 KAA14397 for ; Sun, 11 Oct 1998 10:14:26 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id LAA03389; Sun, 11 Oct 1998 11:07:24 -0600 (MDT) Date: Sun, 11 Oct 1998 11:07:24 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199810111707.LAA03389@narnia.plutotech.com> To: Tony Maher cc: current@FreeBSD.ORG Subject: Re: scsi message Newsgroups: pluto.freebsd.current In-Reply-To: <199810111100.VAA10456@morgan.angis.su.OZ.AU> 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 <199810111100.VAA10456@morgan.angis.su.OZ.AU> you wrote: > Hello, > > after last cvsup and make world (around Oct 10 5:00 GMT) on shutdown > it now reports: > > syncing disk ... 3 3 done. > (da1:ahc0:0:1:0): SYNCHRONISE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da1:ahc0:0:1:0): ILLEGAL REQUEST asc:20,0 > (da1:ahc0:0:1:0): Invalid command operation code sks:c0,0 It doesn't support the sync cache command. We'll be silencing that, non-fatal, error shortly. > So booting -v > --------------------------------------------------------------------------- > ahc0: target 0 synchronous at 10.0MHz, offset = 0xf > ahc0: target 2 synchronous at 10.0MHz, offset = 0xf > (probe6:ahc0:0:6:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe6:ahc0:0:6:0): ILLEGAL REQUEST asc:24,0 > (probe6:ahc0:0:6:0): Invalid field in CDB > ahc0: target 6 synchronous at 5.0MHz, offset = 0xf > ahc0: target 6 using asynchronous transfers > ahc0: target 6 synchronous at 5.0MHz, offset = 0xf > (probe1:ahc0:0:1:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe1:ahc0:0:1:0): ILLEGAL REQUEST asc:24,0 > (probe1:ahc0:0:1:0): Invalid field in CDB sks:c8,1 > ahc0: target 1 synchronous at 10.0MHz, offset = 0xf These devices do not export a serial number. No big deal. We would print them out in 'non-verbose mode' if they were something you should worry about. > This probably explains why the disk doesn't do tagged queuing. It has nothing to do with tagged queuing. We won't tag if: 1) tagged queing is not listed as supported in the device's inquiry response 2) disconnection is disabled 3) the DQUE bit is set in the control page 4) the device matches a quirk that tells us not to perform tagged queuing -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 10:19:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14797 for freebsd-current-outgoing; Sun, 11 Oct 1998 10:19:41 -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 KAA14783 for ; Sun, 11 Oct 1998 10:19:38 -0700 (PDT) (envelope-from ozz.etrust.ru!etrust.ru!osa@serv.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 VAA11415 for ; Sun, 11 Oct 1998 21:19:23 +0400 (MSD) Received: by sunny.aha.ru id VAA10638; (8.8.8/vak/1.9) Sun, 11 Oct 1998 21:18:38 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma010568; Sun Oct 11 21:18:07 1998 Received: from ozz.etrust.ru by serv.etrust.ru with ESMTP id VAA22258; (8.9.1/vak/1.9) Sun, 11 Oct 1998 21:20:55 +0400 (MSD) Received: from localhost by ozz.etrust.ru with ESMTP id VAA15012; (8.9.1/vak/1.9) Sun, 11 Oct 1998 21:21:36 +0400 (MSD) Date: Sun, 11 Oct 1998 21:21:35 +0400 (MSD) From: oZZ!!! To: current@FreeBSD.ORG Subject: netscape-4.07 can't work under FreeBSD-3.0-ELF with XFree86-ELF... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R X-MIME-Autoconverted: from 8bit to quoted-printable by serv.etrust.ru id VAA22258 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA14790 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! How can i run netscape-4.07 under FreeBSD-3.0-ELF with XFree86-ELF ?? If it not possible - how can i run another X-browser ? Opera or somethink else? Rgdz, Осокин Сергей aka 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 Sun Oct 11 10:21:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14948 for freebsd-current-outgoing; Sun, 11 Oct 1998 10:21:04 -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 KAA14941 for ; Sun, 11 Oct 1998 10:21:02 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id KAA22071; Sun, 11 Oct 1998 10:20:49 -0700 (PDT) (envelope-from jdp) Message-Id: <199810111720.KAA22071@austin.polstra.com> To: lh@aus.org Subject: Re: libm typo In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Sun, 11 Oct 1998 10:20:48 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Luke wrote: > Hi I just cvsupd src/lib/libm/common_source/lgamma.c (twice to make sure) > there seems to be a extra /* @line 94 Thanks, I just fixed it. N.B., this code is not used or compiled. Our math library sources are in "src/lib/msun". The header file in "src/include" also is not used. The actual one is in "src/lib/msun/src". It's quite confusing. > (should i post this here or somewhere else?) In the future, use send-pr to file a bug report, if you want to make sure it doesn't get lost. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 10:38:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16394 for freebsd-current-outgoing; Sun, 11 Oct 1998 10:38:54 -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 KAA16354 for ; Sun, 11 Oct 1998 10:38:29 -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 MAA08553; Sun, 11 Oct 1998 12:37:49 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <3620ECEC.A8D5940E@webwizard.org.mx> Date: Sun, 11 Oct 1998 12:37:48 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: "oZZ!!!" CC: current@FreeBSD.ORG Subject: Re: netscape-4.07 can't work under FreeBSD-3.0-ELF with XFree86-ELF... 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 "oZZ!!!" wrote: > Hello! > How can i run netscape-4.07 under FreeBSD-3.0-ELF with XFree86-ELF ?? > If it not possible - how can i run another X-browser ? > Opera or somethink else? > > Rgdz, > Осокин Сергей aka oZZ, > osa@etrust.ru > I don't now about 4.07 but we run 4.5b2 right out of the box in the default directory /usr/lib with no problems. We have are on everthing even kernel. I think there is a port for both that should work. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 11:02:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18166 for freebsd-current-outgoing; Sun, 11 Oct 1998 11:02:45 -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 LAA18151 for ; Sun, 11 Oct 1998 11:02:38 -0700 (PDT) (envelope-from ozz.etrust.ru!etrust.ru!osa@serv.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 WAA12395; Sun, 11 Oct 1998 22:02:23 +0400 (MSD) Received: by sunny.aha.ru id WAA15930; (8.8.8/vak/1.9) Sun, 11 Oct 1998 22:02:17 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma015876; Sun Oct 11 22:01:46 1998 Received: from ozz.etrust.ru by serv.etrust.ru with ESMTP id WAA22322; (8.9.1/vak/1.9) Sun, 11 Oct 1998 22:04:30 +0400 (MSD) Received: from localhost by ozz.etrust.ru with ESMTP id WAA15222; (8.9.1/vak/1.9) Sun, 11 Oct 1998 22:05:08 +0400 (MSD) Date: Sun, 11 Oct 1998 22:05:03 +0400 (MSD) From: oZZ!!! To: Edwin Culp cc: current@FreeBSD.ORG Subject: Re: netscape-4.07 can't work under FreeBSD-3.0-ELF with XFree86-ELF... In-Reply-To: <3620ECEC.A8D5940E@webwizard.org.mx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R X-MIME-Autoconverted: from 8bit to quoted-printable by serv.etrust.ru id WAA22322 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA18157 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Oct 1998, Edwin Culp wrote: > "oZZ!!!" wrote: > > > Hello! > > How can i run netscape-4.07 under FreeBSD-3.0-ELF with XFree86-ELF ?? > > If it not possible - how can i run another X-browser ? > > Opera or somethink else? > > > > Rgdz, > > Осокин Сергей aka oZZ, > > osa@etrust.ru > > > > I don't now about 4.07 but we run 4.5b2 right out of the box in the > default directory /usr/lib with no problems. We have are on everthing > even kernel. I think there is a port for both that should work. > > ed Are your version is -ELF? or a.out? And what about X-libs? Do you have a.out X-libs? I haven't X-libs, my X in ELF ONLY! 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 Sun Oct 11 11:22:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20299 for freebsd-current-outgoing; Sun, 11 Oct 1998 11:22:46 -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 LAA20257 for ; Sun, 11 Oct 1998 11:22:40 -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 NAA08636 for ; Sun, 11 Oct 1998 13:22:21 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <3620F75C.91F79B2F@webwizard.org.mx> Date: Sun, 11 Oct 1998 13:22:20 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.ORG Subject: Latest elf make world. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At least I can see some humor in lines 4 & 5. Would that be like not knowing which end is up? :-) > ===> i386/loader > sh /usr/src/sys/boot/i386/loader/newvers.sh /usr/src/sys/boot/i386/loader/versio > n "bootstrap loader" > head: not found :-) Which > tail: not found :-) end is up > cc -c vers.c > cc -c /usr/src/sys/boot/i386/loader/../../common/gensetdefs.c > cc -static gensetdefs.o -o gensetdefs > /usr/lib/crt1.o: In function `_start': > /usr/lib/crt1.o(.text+0x2f): undefined reference to `atexit' > /usr/lib/crt1.o(.text+0x3c): undefined reference to `atexit' > /usr/lib/crt1.o(.text+0x4f): undefined reference to `exit' What should a person do to make world without resorting to modifying the Makefile and not making the boot loader? Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 11:29:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21266 for freebsd-current-outgoing; Sun, 11 Oct 1998 11:29:38 -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 LAA21250 for ; Sun, 11 Oct 1998 11:29:30 -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 TAA03802 for ; Sun, 11 Oct 1998 19:29:18 +0100 (BST) Date: Sun, 11 Oct 1998 19:29:18 +0100 (BST) From: Karl Pielorz To: current@FreeBSD.ORG Subject: Never ending 'make clean' in kde port? 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 just started to compile kde on my system - which failed (I thought I had XF86 installed, but I didn't)... What I did notice though, was a 'make clean' from /usr/ports/x11/kde never ends, it goes through a continous cycle of cleaning qt, gmake, Mesa-3.0, XFree86-3.3.2 (twice!), giflib, jpeg - and then back to qt... I'm not very good with makefiles - I guess this is going to be unrelated to me not actually having XFree86 installed - isn't it?? 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 11 11:33:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21741 for freebsd-current-outgoing; Sun, 11 Oct 1998 11:33:31 -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 LAA21732 for ; Sun, 11 Oct 1998 11:33:24 -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 TAA03817; Sun, 11 Oct 1998 19:32:29 +0100 (BST) Date: Sun, 11 Oct 1998 19:32:28 +0100 (BST) From: Karl Pielorz To: Edwin Culp cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Latest elf make world. In-Reply-To: <3620F75C.91F79B2F@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 Sun, 11 Oct 1998, Edwin Culp wrote: > At least I can see some humor in lines 4 & 5. Would that be like not > knowing which end is up? :-) > > ===> i386/loader > > sh /usr/src/sys/boot/i386/loader/newvers.sh /usr/src/sys/boot/i386/loader/versio > > n "bootstrap loader" > > head: not found :-) Which > > tail: not found :-) end is up I've seen this (and other problems) with the bootloader all weekend... I've managed to notch up around 6-7 failed 'make buildworlds' ... > What should a person do to make world without resorting to modifying the > Makefile and not making the boot loader? Wait? :) The way things are going - someones probably working on fixing this at the moment, or they will once they see the posts... ;-) 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 11 12:10:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26386 for freebsd-current-outgoing; Sun, 11 Oct 1998 12:10:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgw1.lmco.com (mailgw1.lmco.com [192.31.106.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26381 for ; Sun, 11 Oct 1998 12:10:48 -0700 (PDT) (envelope-from george.w.dinolt@lmco.com) Received: from emss02g01.ems.lmco.com (relay2.ems.lmco.com [198.7.15.39]) by mailgw1.lmco.com (8.8.8/8.8.8) with ESMTP id NAA25661; Sun, 11 Oct 1998 13:09:58 -0600 (MDT) Received: from wdl1.wdl.lmco.com ([137.249.32.1]) by lmco.com (PMDF V5.1-10 #20543) with SMTP id <0F0O005ARFWL9Z@lmco.com>; Sun, 11 Oct 1998 13:09:57 -0600 (MDT) Received: from lmco.com by wdl1.wdl.lmco.com (SMI-8.6/WDL-5.0) id MAA13100; Sun, 11 Oct 1998 12:09:49 -0700 Date: Sun, 11 Oct 1998 12:08:22 -0700 From: "George W. Dinolt" Subject: Re: netscape-4.07 can't work under FreeBSD-3.0-ELF with XFree86-ELF... To: oZZ!!! Cc: current@FreeBSD.ORG Message-id: <36210225.588CD0D1@lmco.com> Organization: Lockheed Martin Western Development Labs MIME-version: 1.0 X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-19980930-BETA i386) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8BIT References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oZZ!!! wrote: > Hello! > How can i run netscape-4.07 under FreeBSD-3.0-ELF with XFree86-ELF ?? > If it not possible - how can i run another X-browser ? > Opera or somethink else? > > Rgdz, > Осокин Сергей aka oZZ, > osa@etrust.ru > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I am writting this using 2.07 netscape on an current-"elf" system . But I am using "aout" X libraries which I copied over to /usr/X11R6/lib/aout/ from my 2.7 system. Seems to work fine. George Dinolt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 12:19:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27276 for freebsd-current-outgoing; Sun, 11 Oct 1998 12:19:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-29-dbn.dial-up.net [196.34.155.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27263 for ; Sun, 11 Oct 1998 12:19:38 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA26931; Sun, 11 Oct 1998 21:17:15 +0200 (SAT) From: Robert Nordier Message-Id: <199810111917.VAA26931@ceia.nordier.com> Subject: Re: Latest elf make world. In-Reply-To: from Karl Pielorz at "Oct 11, 98 07:32:28 pm" To: kpielorz@tdx.co.uk (Karl Pielorz) Date: Sun, 11 Oct 1998 21:17:13 +0200 (SAT) Cc: eculp@webwizard.org.mx, 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 Karl Pielorz wrote: > > On Sun, 11 Oct 1998, Edwin Culp wrote: > > > At least I can see some humor in lines 4 & 5. Would that be like not > > knowing which end is up? :-) > > > ===> i386/loader > > > sh /usr/src/sys/boot/i386/loader/newvers.sh /usr/src/sys/boot/i386/loader/versio > > > n "bootstrap loader" > > > head: not found :-) Which > > > tail: not found :-) end is up > > I've seen this (and other problems) with the bootloader all weekend... > I've managed to notch up around 6-7 failed 'make buildworlds' ... > > > What should a person do to make world without resorting to modifying the > > Makefile and not making the boot loader? > > Wait? :) > > The way things are going - someones probably working on fixing this at > the moment, or they will once they see the posts... ;-) I've just finished a successful buildworld and installworld here, based on latest commits. Sorry for the problems, folks. Someone plugged the new boot code into make world way before it was expecting this to happen. Things should be better now, though you probably want to wait a few hours while things are check through again. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 12:35:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28667 for freebsd-current-outgoing; Sun, 11 Oct 1998 12:35:51 -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 MAA28661 for ; Sun, 11 Oct 1998 12:35:49 -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 VAA22757; Sun, 11 Oct 1998 21:34:44 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA09981; Sun, 11 Oct 1998 21:34:43 +0200 (MET DST) Message-ID: <19981011213443.08052@follo.net> Date: Sun, 11 Oct 1998 21:34:43 +0200 From: Eivind Eklund To: Karl Pielorz , current@FreeBSD.ORG Subject: Re: Never ending 'make clean' in kde port? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Karl Pielorz on Sun, Oct 11, 1998 at 07:29:18PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 11, 1998 at 07:29:18PM +0100, Karl Pielorz wrote: > > Hi, > > I just started to compile kde on my system - which failed (I thought I had > XF86 installed, but I didn't)... > > What I did notice though, was a 'make clean' from /usr/ports/x11/kde never > ends, it goes through a continous cycle of cleaning qt, gmake, Mesa-3.0, > XFree86-3.3.2 (twice!), giflib, jpeg - and then back to qt... > > I'm not very good with makefiles - I guess this is going to be unrelated > to me not actually having XFree86 installed - isn't it?? Probably. However, are you _sure_ it was an endless loop? KDE does a pretty large series of cleans that look like they may be looping, but in my experience it terminate after a short while (as it is just cleaning out the same dependencies through multiple ports)... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 12:44:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29198 for freebsd-current-outgoing; Sun, 11 Oct 1998 12:44:15 -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 MAA29187 for ; Sun, 11 Oct 1998 12:44:10 -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 UAA03994; Sun, 11 Oct 1998 20:43:46 +0100 (BST) Date: Sun, 11 Oct 1998 20:43:46 +0100 (BST) From: Karl Pielorz To: Robert Nordier cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Latest elf make world. In-Reply-To: <199810111917.VAA26931@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 Sun, 11 Oct 1998, Robert Nordier wrote: > I've just finished a successful buildworld and installworld here, based > on latest commits. > > Sorry for the problems, folks. Someone plugged the new boot code > into make world way before it was expecting this to happen. No problem :) > Things should be better now, though you probably want to wait a few > hours while things are check through again. OK, will do... If nothing else I now have some pretty good timings for how long both my systems take to build the world ;-) (Well, almost build it ) Thanks, 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 11 12:47:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29344 for freebsd-current-outgoing; Sun, 11 Oct 1998 12:47:17 -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 MAA29339 for ; Sun, 11 Oct 1998 12:47:13 -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 UAA04004; Sun, 11 Oct 1998 20:46:53 +0100 (BST) Date: Sun, 11 Oct 1998 20:46:53 +0100 (BST) From: Karl Pielorz To: Eivind Eklund cc: current@FreeBSD.ORG Subject: Re: Never ending 'make clean' in kde port? In-Reply-To: <19981011213443.08052@follo.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, 11 Oct 1998, Eivind Eklund wrote: > > What I did notice though, was a 'make clean' from /usr/ports/x11/kde never > > ends, it goes through a continous cycle of cleaning qt, gmake, Mesa-3.0, > > XFree86-3.3.2 (twice!), giflib, jpeg - and then back to qt... > However, are you _sure_ it was an endless loop? KDE does a pretty > large series of cleans that look like they may be looping, but in my > experience it terminate after a short while (as it is just cleaning > out the same dependencies through multiple ports)... Nope, your right - I let it run again, it wasn't quite endless - just 60+ lines... Following the files through I think I can see what's happening, dependants that depend on stuff that's already depended on (but gets cleaned again anyway)... ;-) Not quite a mess, just a bit convoluted 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 11 13:36:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03943 for freebsd-current-outgoing; Sun, 11 Oct 1998 13:36:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03938 for ; Sun, 11 Oct 1998 13:36:42 -0700 (PDT) (envelope-from randy@rip.psg.com) Received: (from randy@localhost) by rip.psg.com (8.9.1/8.9.1) id NAA17243; Sun, 11 Oct 1998 13:36:32 -0700 (PDT) (envelope-from randy) Date: Sun, 11 Oct 1998 13:36:32 -0700 (PDT) Message-Id: <199810112036.NAA17243@rip.psg.com> From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@FreeBSD.ORG Subject: buildworld failure with j4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG buildworld of 1998.09.25 had the following failure on 3.0CAM-19980712-SNAP with j4, but succeeded when no j4 --- lib/re.pm --- --- autosplit --- --- lib/re.pm --- cat /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/ext/re/re.pm > /usr/obj/aout/usr/src/gnu/usr.bin/perl/perl/lib/re.pm --- autosplit --- miniperl -I/usr/obj/aout/usr/src/gnu/usr.bin/perl/perl/lib -e 'use AutoSplit; autosplit_lib_modules(@ARGV)' lib/*.pm lib/*/*.pm --- Config.pm --- miniperl /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm Config.pm Porting/Glossary myconfig config.sh --- autosplit --- Config.pm did not return a true value at /usr/obj/aout/usr/src/gnu/usr.bin/perl/perl/lib/AutoSplit.pm line 4. BEGIN failed--compilation aborted at /usr/obj/aout/usr/src/gnu/usr.bin/perl/perl/lib/AutoSplit.pm line 4. BEGIN failed--compilation aborted at -e line 1. *** Error code 2 1 error randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 13:40:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04368 for freebsd-current-outgoing; Sun, 11 Oct 1998 13:40:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04351; Sun, 11 Oct 1998 13:40:07 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id WAA29659; Sun, 11 Oct 1998 22:39:53 +0200 (MET DST) Message-ID: <19981011223952.A29651@cons.org> Date: Sun, 11 Oct 1998 22:39:52 +0200 From: Martin Cracauer To: Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Any chance of a dynamically linked jdk-1.1.6 (a.out version) References: <199810101752.BAA10216@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199810101752.BAA10216@ariadne.tensor.pgs.com>; from Stephen Hocking-Senior Programmer PGS Tensor Perth on Sun, Oct 11, 1998 at 01:52:58AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199810101752.BAA10216@ariadne.tensor.pgs.com>, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > Because libawt.so is demanding to have xmDrawingAreaWidgetClass, which hasn't > been staically linked with the rest of the Motif library, would be possible to > either a) get this function linked in or b) have a version with the Motif > stuff dynamically linked in. The binary has been replaced a few days ago. Do you still have problems with the newest one? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.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 11 13:55:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06361 for freebsd-current-outgoing; Sun, 11 Oct 1998 13:55:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assurance.rstcorp.com (assurance.rstcorp.com [206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06350 for ; Sun, 11 Oct 1998 13:54:59 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id QAA22602 for ; Sun, 11 Oct 1998 16:54:32 -0400 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma022597; Sun, 11 Oct 98 16:53:31 -0400 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id QAA27153 for ; Sun, 11 Oct 1998 16:53:29 -0400 (EDT) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id QAA00317; Sun, 11 Oct 1998 16:53:31 -0400 (EDT) Date: Sun, 11 Oct 1998 16:53:31 -0400 (EDT) Message-Id: <199810112053.QAA00317@jabberwock.rstcorp.com> From: "Viren R. Shah" To: freebsd-current@FreeBSD.ORG Subject: 3.0-19981009-BETA install report X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is on an old Compaq 486DX2/50 w/ 8MB RAM and a 160M IDE drive. It has an Etherlink III (ep0) card in it. I brought it up using the boot floppy. It probed the ep0 card correctly, but when configuring the network in preparation for doing an ftp install, the install would hang on setting up the default route. So, i aborted the install, rebooted, and went into fixit mode, used ifconfig and ping to make sure that the card was set up (using the same info I had given to sysinstall), and then I returned to the install. At this point it apparently assummed that I wanted to do an install thru floppies. It asked me to insert a floppy (I assummed it was asking for the boot.flp back, and so I inserted the boot floppy). It couldn't find the "bin" dist, so it continued, and came up with the "congrats! you have successfully installed FreeBSD" screen. I then went into the post-config mode, and changed the media to ftp, and installed the bin dist + the sys src. I rebooted, but for some reason the copying of kernel.GENERIC to kernel hadn't happenned, and therefore I had to explicitly boot from kernel.GENERIC. Otherwise everything went well. It's currently compiling a kernel (been over 15 minutes so far). This is easily verifiable thru the following steps: 1. boot with boot.flp 2. use fixit mode and fixit.flp to startup network card 3. when returned to the install menu, perform a novice install. 4. It assumes the media is floppy. BTW: the original NIC I had in this machine was a SMC EZCARD10 (SMC1660BTA). It was recognized (after I changed it to irq 5 and 0x300), but it could never sucessfully use it since I couldn't find the right combination of link[0-2] options to make it choose 10baseT/UTP (and I couldn't do it thru the "media" option). anyone have one of these working with FreeBSD? (This card has 3 ports, BNC, AUI and the UTP one). Thanks Viren -- Viren R. Shah "I merely note, if you want to catch something, running after it isn't always the best way." -- Miles Vorkosigan (Lois McMaster Bujold, "The Mountains of Mourning") To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 14:02:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07011 for freebsd-current-outgoing; Sun, 11 Oct 1998 14:02:28 -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 OAA06990 for ; Sun, 11 Oct 1998 14:02:25 -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 HAA27790; Mon, 12 Oct 1998 07:02:12 +1000 (EST) Date: Mon, 12 Oct 1998 07:02:12 +1000 (EST) From: Tony Maher Message-Id: <199810112102.HAA27790@morgan.angis.su.OZ.AU> To: gibbs@narnia.plutotech.com Subject: Re: scsi message Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It has nothing to do with tagged queuing. We won't tag if: > > 1) tagged queing is not listed as supported in the device's inquiry response > 2) disconnection is disabled > 3) the DQUE bit is set in the control page > 4) the device matches a quirk that tells us not to perform tagged queuing Ok. Thanks for the info. tonym To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 14:11:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08644 for freebsd-current-outgoing; Sun, 11 Oct 1998 14:11:00 -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 OAA08639 for ; Sun, 11 Oct 1998 14:10:57 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id WAA15213 for ; Sun, 11 Oct 1998 22:10:45 +0100 (BST) Message-ID: <36211EA1.E913752F@tdx.co.uk> Date: Sun, 11 Oct 1998 22:09:53 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Buildworld failed with -current as of 10/11/98, 21:00 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, Pesky boot loader failure rear's it's ugly head again... :-( - I've just re cvsup'd as of 22:00 - in case I'd missed anything that was still 'being changed' from earlier, but no luck... :-( Regards, Karl " ld -nostdlib -static -Ttext 0x1000 -o loader.bin /usr/obj/elf/usr/src/sys/boot/i386/loader/../btx/lib/crt0.o setdef0.o main.o conf.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic. o vers.o setdef1.o -lstand /usr/obj/elf/usr/src/sys/boot/i386/loader/../libi386/libi386.a -lstand conf.o(.data+0xc): undefined reference to `dosfs_fsops' /usr/lib/libstand.a(strcasecmp.o): In function `strcasecmp': strcasecmp.o(.text+0x19): undefined reference to `___tolower' strcasecmp.o(.text+0x25): undefined reference to `_CurrentRuneLocale' strcasecmp.o(.text+0x3e): undefined reference to `___tolower' strcasecmp.o(.text+0x49): undefined reference to `_CurrentRuneLocale' strcasecmp.o(.text+0x71): undefined reference to `___tolower' strcasecmp.o(.text+0x7d): undefined reference to `_CurrentRuneLocale' strcasecmp.o(.text+0x96): undefined reference to `___tolower' strcasecmp.o(.text+0x9d): undefined reference to `_CurrentRuneLocale' /usr/lib/libstand.a(strcasecmp.o): In function `strncasecmp': strcasecmp.o(.text+0xd9): undefined reference to `___tolower' strcasecmp.o(.text+0xe5): undefined reference to `_CurrentRuneLocale' strcasecmp.o(.text+0xfe): undefined reference to `___tolower' strcasecmp.o(.text+0x109): undefined reference to `_CurrentRuneLocale' strcasecmp.o(.text+0x125): undefined reference to `___tolower' strcasecmp.o(.text+0x131): undefined reference to `_CurrentRuneLocale' strcasecmp.o(.text+0x14a): undefined reference to `___tolower' strcasecmp.o(.text+0x151): undefined reference to `_CurrentRuneLocale' *** Error code 1 1 error Stop. " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 14:20:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09983 for freebsd-current-outgoing; Sun, 11 Oct 1998 14:20:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09972 for ; Sun, 11 Oct 1998 14:20:30 -0700 (PDT) (envelope-from asami@sunrise.cs.berkeley.edu) Received: from bubble.didi.com (sjx-ca115-40.ix.netcom.com [207.223.162.104]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id OAA28020; Sun, 11 Oct 1998 14:20:12 -0700 (PDT) Received: (from asami@localhost) by bubble.didi.com (8.8.8/8.8.8) id OAA14918; Sun, 11 Oct 1998 14:20:06 -0700 (PDT) (envelope-from asami) Date: Sun, 11 Oct 1998 14:20:06 -0700 (PDT) Message-Id: <199810112120.OAA14918@bubble.didi.com> To: kpielorz@tdx.co.uk CC: eivind@yes.no, current@FreeBSD.ORG In-reply-to: (message from Karl Pielorz on Sun, 11 Oct 1998 20:46:53 +0100 (BST)) Subject: Re: Never ending 'make clean' in kde port? From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Nope, your right - I let it run again, it wasn't quite endless - just 60+ * lines... Following the files through I think I can see what's happening, * dependants that depend on stuff that's already depended on (but gets * cleaned again anyway)... ;-) Not quite a mess, just a bit convoluted Well, if someone wants to submit a patch to fix this, I'm all ears. :) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 14:34:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11100 for freebsd-current-outgoing; Sun, 11 Oct 1998 14:34:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bar.bz ([136.224.58.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA10989; Sun, 11 Oct 1998 14:33:06 -0700 (PDT) (envelope-from foo@bar.net) Date: Sun, 11 Oct 1998 14:33:06 -0700 (PDT) From: foo@bar.net Message-Id: <199810112133.OAA10989@hub.freebsd.org> Subject: Motif for ELF? To: undisclosed-recipients:; Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahem. ftp://cdrom.com/pub/FreeBSD/incoming/Motif-2.0-FreeBSD-3.0-ELF.tgz a5f0428de1a496a23671c7e1694786b5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 14:35:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11318 for freebsd-current-outgoing; Sun, 11 Oct 1998 14:35:51 -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 OAA11302 for ; Sun, 11 Oct 1998 14:35:45 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id OAA23285; Sun, 11 Oct 1998 14:35:30 -0700 (PDT) (envelope-from jdp) Message-Id: <199810112135.OAA23285@austin.polstra.com> To: eculp@webwizard.org.mx Subject: Re: Latest elf make world. In-Reply-To: <3620F75C.91F79B2F@webwizard.org.mx> References: <3620F75C.91F79B2F@webwizard.org.mx> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Sun, 11 Oct 1998 14:35:30 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3620F75C.91F79B2F@webwizard.org.mx>, Edwin Culp wrote: > What should a person do to make world without resorting to modifying the > Makefile and not making the boot loader? In situations like this, where something is broken for a while, "make -k" is very useful for getting on with your business. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 15:42:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29266 for freebsd-current-outgoing; Sun, 11 Oct 1998 15:42:44 -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 PAA29261 for ; Sun, 11 Oct 1998 15:42:42 -0700 (PDT) (envelope-from ozz.etrust.ru!etrust.ru!osa@serv.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 CAA19386 for ; Mon, 12 Oct 1998 02:42:26 +0400 (MSD) Received: by sunny.aha.ru id CAA29748; (8.8.8/vak/1.9) Mon, 12 Oct 1998 02:41:58 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma029683; Mon Oct 12 02:41:30 1998 Received: from ozz.etrust.ru by serv.etrust.ru with ESMTP id CAA22858; (8.9.1/vak/1.9) Mon, 12 Oct 1998 02:44:17 +0400 (MSD) Received: from localhost by ozz.etrust.ru with ESMTP id CAA20926; (8.9.1/vak/1.9) Mon, 12 Oct 1998 02:44:55 +0400 (MSD) Date: Mon, 12 Oct 1998 02:44:54 +0400 (MSD) From: oZZ!!! To: current@FreeBSD.ORG Subject: Re: Buildworld failed with -current as of 10/11/98, 21:00 In-Reply-To: <36211EA1.E913752F@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 Sun, 11 Oct 1998, Karl Pielorz wrote: > Hi All, > Pesky boot loader failure rear's it's ugly head again... :-( - I've just re > cvsup'd as of 22:00 - in case I'd missed anything that was still 'being > changed' from earlier, but no luck... > > ld -nostdlib -static -Ttext 0x1000 -o loader.bin > /usr/obj/elf/usr/src/sys/boot/i386/loader/../btx/lib/crt0.o setdef0.o main.o > conf.o > boot.o commands.o console.o devopen.o interp.o interp_backslash.o > interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic. > o vers.o setdef1.o -lstand > /usr/obj/elf/usr/src/sys/boot/i386/loader/../libi386/libi386.a -lstand > conf.o(.data+0xc): undefined reference to `dosfs_fsops' > /usr/lib/libstand.a(strcasecmp.o): In function `strcasecmp': > strcasecmp.o(.text+0x19): undefined reference to `___tolower' > strcasecmp.o(.text+0x25): undefined reference to `_CurrentRuneLocale' > strcasecmp.o(.text+0x3e): undefined reference to `___tolower' > strcasecmp.o(.text+0x49): undefined reference to `_CurrentRuneLocale' > strcasecmp.o(.text+0x71): undefined reference to `___tolower' > strcasecmp.o(.text+0x7d): undefined reference to `_CurrentRuneLocale' > strcasecmp.o(.text+0x96): undefined reference to `___tolower' > strcasecmp.o(.text+0x9d): undefined reference to `_CurrentRuneLocale' > /usr/lib/libstand.a(strcasecmp.o): In function `strncasecmp': > strcasecmp.o(.text+0xd9): undefined reference to `___tolower' > strcasecmp.o(.text+0xe5): undefined reference to `_CurrentRuneLocale' > strcasecmp.o(.text+0xfe): undefined reference to `___tolower' > strcasecmp.o(.text+0x109): undefined reference to `_CurrentRuneLocale' > strcasecmp.o(.text+0x125): undefined reference to `___tolower' > strcasecmp.o(.text+0x131): undefined reference to `_CurrentRuneLocale' > strcasecmp.o(.text+0x14a): undefined reference to `___tolower' > strcasecmp.o(.text+0x151): undefined reference to `_CurrentRuneLocale' > *** Error code 1 > 1 error > > Stop. > Yeah... :-((( I have this problem 2.... :-((( 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 Sun Oct 11 15:49:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00134 for freebsd-current-outgoing; Sun, 11 Oct 1998 15:49:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hotjobs.com (fs3.ny.genx.net [206.64.4.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA00128 for ; Sun, 11 Oct 1998 15:49:46 -0700 (PDT) (envelope-from perlsta@hotjobs.com) Received: (qmail 21003 invoked by uid 1288); 11 Oct 1998 22:47:25 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 11 Oct 1998 22:47:25 -0000 Date: Sun, 11 Oct 1998 18:47:25 -0400 (EDT) From: Alfred X-Sender: perlsta@fs3.ny.genx.net To: current@FreeBSD.ORG Subject: bitten 3 times already. 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 this is the third time freebsd has decided that wd0s1b wasn't "comfy" enough for a crashdump and ate a different partition while dumping. i even checked sysctl for the dumpdev and then checked against my /dev entry. this is on 2 seperate systems, i got yelled at for using DEVFS so i haven't been using it. anyhow i'm reinstalling yet again, i think i'm going to buy myself a tapebackup though. i was still having my hangs during deleting mail over NFS so i enabled DDB. the hangup happened (it had happened 3 times in about an hour)but i was able to get out of it and into DDB, i was kinda unsure of what to do at this point so i told the kernel to panic hoping for a useful backtrace i could send in from a crashdump. instead i'm doing a reinstall as the crash went to my /usr *sigh* i'm NOT enabling crash dumps again, but if anyone wants me to do _anything_ from DDB to give some sense of why the lockups happen i will. (can ping the box and ports that are open allow connections but then hang not allowing the accepting process to do anything, closed ports get connection refused) i'm using the xl0 driver over 100mbit, so i'm wondering if Bill would be interested in this. the really odd part is that the machine is just about rock solid, make world, large compiles over NFS (well not _that_ large), playing mp3s over NFS and all, but deleting mail in pine makes it just wedge the userland from what i can see. also, anyone have something i can do to get a dump of my partitions to examine why it's confusing the crashdump mechanism? thanks, Alfred (greatful it wasn't my homedir) Perlstein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 16:08:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01854 for freebsd-current-outgoing; Sun, 11 Oct 1998 16:08:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles306.castles.com [208.214.167.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01847 for ; Sun, 11 Oct 1998 16:08:24 -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 QAA01867; Sun, 11 Oct 1998 16:13:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810112313.QAA01867@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: oZZ!!! cc: current@FreeBSD.ORG Subject: Re: Buildworld failed with -current as of 10/11/98, 21:00 In-reply-to: Your message of "Mon, 12 Oct 1998 02:44:54 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Oct 1998 16:12:59 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > ld -nostdlib -static -Ttext 0x1000 -o loader.bin > > /usr/obj/elf/usr/src/sys/boot/i386/loader/../btx/lib/crt0.o setdef0.o main.o > > conf.o > > boot.o commands.o console.o devopen.o interp.o interp_backslash.o > > interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic. > > o vers.o setdef1.o -lstand > > /usr/obj/elf/usr/src/sys/boot/i386/loader/../libi386/libi386.a -lstand > > conf.o(.data+0xc): undefined reference to `dosfs_fsops' > > /usr/lib/libstand.a(strcasecmp.o): In function `strcasecmp': > > strcasecmp.o(.text+0x19): undefined reference to `___tolower' > > strcasecmp.o(.text+0x25): undefined reference to `_CurrentRuneLocale' > > strcasecmp.o(.text+0x3e): undefined reference to `___tolower' > > strcasecmp.o(.text+0x49): undefined reference to `_CurrentRuneLocale' > > strcasecmp.o(.text+0x71): undefined reference to `___tolower' > > strcasecmp.o(.text+0x7d): undefined reference to `_CurrentRuneLocale' > > strcasecmp.o(.text+0x96): undefined reference to `___tolower' > > strcasecmp.o(.text+0x9d): undefined reference to `_CurrentRuneLocale' > > /usr/lib/libstand.a(strcasecmp.o): In function `strncasecmp': > > strcasecmp.o(.text+0xd9): undefined reference to `___tolower' > > strcasecmp.o(.text+0xe5): undefined reference to `_CurrentRuneLocale' > > strcasecmp.o(.text+0xfe): undefined reference to `___tolower' > > strcasecmp.o(.text+0x109): undefined reference to `_CurrentRuneLocale' > > strcasecmp.o(.text+0x125): undefined reference to `___tolower' > > strcasecmp.o(.text+0x131): undefined reference to `_CurrentRuneLocale' > > strcasecmp.o(.text+0x14a): undefined reference to `___tolower' > > strcasecmp.o(.text+0x151): undefined reference to `_CurrentRuneLocale' > > *** Error code 1 > > 1 error > > > > Stop. > > > > Yeah... :-((( > I have this problem 2.... :-((( Rebuild and reinstall libstand. Also, you *must* read the -current list. -- \\ 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 11 16:11:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02333 for freebsd-current-outgoing; Sun, 11 Oct 1998 16:11:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02328 for ; Sun, 11 Oct 1998 16:11:57 -0700 (PDT) (envelope-from jamesh@swcp.com) Received: from localhost (jamesh@localhost) by kitsune.swcp.com (8.8.8/1.2.3) with SMTP id RAA04376; Sun, 11 Oct 1998 17:10:30 -0600 (MDT) Date: Sun, 11 Oct 1998 17:10:29 -0600 (MDT) From: James Hamilton To: Karl Pielorz cc: current@FreeBSD.ORG Subject: Re: Makeworld breakage... In-Reply-To: <3620D44C.FF6E6143@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 Could you shed some light on the difference between make world and make buildworld please? On Sun, 11 Oct 1998, Karl Pielorz wrote: --> -->I cvsup'd (12:00 BST) and 'make buildworld' failed... Looking at recent -->messages I saw people said the bootloader may still have problems, so I -->cvs'upd again at -->13:40 - and tried another build world... It failed as well.. The last cvsup I -->did was at around 15.00 - and showed a diff for the makefile of the bootstrap -->code... Unfortunately it still fails to build... --> -->I was careful to delete /usr/obj between builds (just in case)... --> -->Regards, --> -->Karl --> -->" -->Warning: Object directory not changed from original -->/usr/src/sys/boot/i386/loader -->--- vers.o --- -->sh /usr/src/sys/boot/i386/loader/newvers.sh -->/usr/src/sys/boot/i386/loader/version "bootstrap loader" -->head: not found -->tail: not found -->" --> -->(Which is slightly worrying, and further on...) --> -->" -->cc -c /usr/src/sys/boot/i386/loader/../../common/gensetdefs.c -->--- gensetdefs --- -->cc -static gensetdefs.o -o gensetdefs -->/usr/lib/crt1.o: In function `_start': -->/usr/lib/crt1.o(.text+0x2f): undefined reference to `atexit' -->/usr/lib/crt1.o(.text+0x3c): undefined reference to `atexit' -->/usr/lib/crt1.o(.text+0x4f): undefined reference to `exit' -->gensetdefs.o: In function `main': -->gensetdefs.o(.text+0x7d): undefined reference to `printf' -->gensetdefs.o(.text+0x94): undefined reference to `free' -->gensetdefs.o(.text+0xa0): undefined reference to `free' -->gensetdefs.o: In function `enter': -->gensetdefs.o(.text+0x10e): undefined reference to `strcmp' -->gensetdefs.o: In function `enter_sets': -->[SNIP loads of 'undefined references' deleted ] -->*** Error code 1 -->1 error -->*** Error code 2 -->1 error -->*** Error code 2 -->1 error -->*** Error code 2 -->1 error -->*** Error code 2 -->1 error -->*** Error code 2 -->1 error -->" --> -->To Unsubscribe: send mail to majordomo@FreeBSD.org -->with "unsubscribe freebsd-current" in the body of the message --> James Hamilton SWCP Technical Support (505)-232-7992 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 16:13:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02484 for freebsd-current-outgoing; Sun, 11 Oct 1998 16:13:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rgate.ricochet.net (rgate.ricochet.net [204.179.143.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02476 for ; Sun, 11 Oct 1998 16:12:54 -0700 (PDT) (envelope-from enkhyl@scient.com) Received: from mg136-056.ricochet.net (mg136-056.ricochet.net [204.179.136.56]) by rgate.ricochet.net (8.8.8/8.8.8) with ESMTP id SAA25652; Sun, 11 Oct 1998 18:12:29 -0500 (CDT) Date: Sun, 11 Oct 1998 16:11:34 -0700 (PDT) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: enkhyl@hayseed.net To: Alfred cc: current@FreeBSD.ORG Subject: Re: bitten 3 times already. 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, 11 Oct 1998, Alfred wrote: > Date: Sun, 11 Oct 1998 18:47:25 -0400 (EDT) > From: Alfred > To: current@FreeBSD.ORG > Subject: bitten 3 times already. > > > this is the third time freebsd has decided that wd0s1b wasn't "comfy" > enough for a crashdump and ate a different partition while dumping. > > i even checked sysctl for the dumpdev and then checked against my /dev > entry. > > this is on 2 seperate systems, i got yelled at for using DEVFS so i > haven't been using it. To provide another data point, I'm running -current (as of Friday) with DEVFS (yes, I like to live dangerously ;-) on my Dell Latitude CPi laptop. I've done a few crash dumps and they DTRT. 252 ender:~> sysctl kern.dumpdev kern.dumpdev: { major = 0, minor = 262145 } 253 ender:~> uname -a FreeBSD ender.sf.scient.com 3.0-BETA FreeBSD 3.0-BETA #1: Fri Oct 9 23:41:16 PDT 1998 enkhyl@ender.sf.scient.com:/usr/src/sys/compile/ENDER-aout i386 -- Christopher Nielsen Scient: The Art and Science of Electronic Business cnielsen@scient.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 11 16:19:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03150 for freebsd-current-outgoing; Sun, 11 Oct 1998 16:19:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03134; Sun, 11 Oct 1998 16:19:29 -0700 (PDT) (envelope-from dmaddox@scsn.net) Received: from rhiannon.scsn.net ([209.12.57.92]) by mail.scsn.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-41950U6000L1100S0) with ESMTP id AAA191; Sun, 11 Oct 1998 19:10:03 -0400 Received: (from dmaddox@localhost) by rhiannon.scsn.net (8.9.1/8.9.1) id TAA00760; Sun, 11 Oct 1998 19:19:46 GMT (envelope-from dmaddox) Message-ID: <19981011191945.A703@scsn.net> Date: Sun, 11 Oct 1998 19:19:45 +0000 From: dmaddox@scsn.net (Donald J. Maddox) To: Satoshi Asami , kpielorz@tdx.co.uk Cc: eivind@yes.no, current@FreeBSD.ORG Subject: Re: Never ending 'make clean' in kde port? Reply-To: dmaddox@scsn.net References: <199810112120.OAA14918@bubble.didi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810112120.OAA14918@bubble.didi.com>; from Satoshi Asami on Sun, Oct 11, 1998 at 02:20:06PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 11, 1998 at 02:20:06PM -0700, Satoshi Asami wrote: > * Nope, your right - I let it run again, it wasn't quite endless - just 60+ > * lines... Following the files through I think I can see what's happening, > * dependants that depend on stuff that's already depended on (but gets > * cleaned again anyway)... ;-) Not quite a mess, just a bit convoluted > > Well, if someone wants to submit a patch to fix this, I'm all ears. :) You don't need a patch... You just need 'make -DNOCLEANDEPENDS clean' :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 16:39:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06091 for freebsd-current-outgoing; Sun, 11 Oct 1998 16:39:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.videotron.ab.ca (cloak.videotron.ab.ca [206.75.216.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06066 for ; Sun, 11 Oct 1998 16:39:46 -0700 (PDT) (envelope-from rward@netcom.ca) Received: from blade ([24.108.23.151]) by mail.videotron.ab.ca (Netscape Messaging Server 3.6) with SMTP id AAA3FC4 for ; Sun, 11 Oct 1998 17:38:49 -0600 Reply-To: From: "Ryan Ward" To: "FreeBSD Current" Subject: aout-to-elf Date: Sun, 11 Oct 1998 17:41:00 -0600 Message-ID: <000101bdf570$9a21f1a0$97176c18@blade.v-wave.com> 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.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I had some problems with my system, being partially aout and elf. Is there a way to make sure that my system is all elf vs aout? Besides doing aout-to-elf? When i did the aout-to-elf it broke in a few places. Maybe my system was already completely elf? Who knows, but I had problems with my make world with current and thought that this was the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 17:06:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09660 for freebsd-current-outgoing; Sun, 11 Oct 1998 17:06:42 -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 RAA09655 for ; Sun, 11 Oct 1998 17:06:39 -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 JAA16411; Mon, 12 Oct 1998 09:36:26 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id JAA26405; Mon, 12 Oct 1998 09:36:25 +0930 (CST) Message-ID: <19981012093625.H24503@freebie.lemis.com> Date: Mon, 12 Oct 1998 09:36:25 +0930 From: Greg Lehey To: James Hamilton , Karl Pielorz Cc: current@FreeBSD.ORG Subject: buildworld (was: Makeworld breakage...) References: <3620D44C.FF6E6143@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from James Hamilton on Sun, Oct 11, 1998 at 05:10:29PM -0600 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, 11 October 1998 at 17:10:29 -0600, James Hamilton wrote: > Could you shed some light on the difference between make world and make > buildworld please? 'make world' has two targets: buildworld and installworld. I consider the names self-explanatory. 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 11 17:12:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10359 for freebsd-current-outgoing; Sun, 11 Oct 1998 17:12:18 -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 RAA10349 for ; Sun, 11 Oct 1998 17:12:08 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id TAA13196; Sun, 11 Oct 1998 19:11:50 -0500 (CDT) Received: from harkol-31.isdn.mke.execpc.com(169.207.64.159) by peak.mountin.net via smap (V1.3) id sma013194; Sun Oct 11 19:11:49 1998 Message-Id: <3.0.3.32.19981011190058.006f58d0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 11 Oct 1998 19:00:58 -0500 To: James Hamilton From: "Jeffrey J. Mountin" Subject: Re: Makeworld breakage... Cc: current@FreeBSD.ORG In-Reply-To: References: <3620D44C.FF6E6143@tdx.co.uk> 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:10 PM 10/11/98 -0600, James Hamilton wrote: >Could you shed some light on the difference between make world and make >buildworld please? If you check out: http://www.freebsd.org/docs.html#tutorial There is a handy link to: http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html make buildworld + make installworld = make world Is better to successfully make before trying to install, no? Especially if your server isn't local and you are not going to wait around. Not that I care to try a remote installworld when it's a long drive. enjoy! 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 Sun Oct 11 17:43:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13958 for freebsd-current-outgoing; Sun, 11 Oct 1998 17:43:39 -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 RAA13949 for ; Sun, 11 Oct 1998 17:43:34 -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 KAA07935; Mon, 12 Oct 1998 10:13:09 +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: <199810110805.RAA09175@zodiac.mech.utsunomiya-u.ac.jp> Date: Mon, 12 Oct 1998 10:13:09 +0930 (CST) From: "Daniel O'Connor" To: Kazutaka YOKOTA Subject: RE: PS/2 mouse problem with 440BX chipset? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Oct-98 Kazutaka YOKOTA wrote: > I don't know if this problem is present in 440BX-based system in general, > or it is peculiar to this specific motherboard. > Please contact me if you have a 440BX-based system and tell me if you > have the same problem or not. We have 4 440BX (SuperMicro P6SBS) boards here, and 1 of them has a PS/2 kbd & mouse, and the other 3 have PS/2 keyboards and serial mice. All of them work fine. --------------------------------------------------------------------- |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 Sun Oct 11 19:06:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21221 for freebsd-current-outgoing; Sun, 11 Oct 1998 19:06:20 -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 TAA21213 for ; Sun, 11 Oct 1998 19:06:15 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id MAA28539; Mon, 12 Oct 1998 12:10:05 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810120210.MAA28539@cimlogic.com.au> Subject: Re: aout-to-elf In-Reply-To: <000101bdf570$9a21f1a0$97176c18@blade.v-wave.com> from Ryan Ward at "Oct 11, 98 05:41:00 pm" To: rward@netcom.ca Date: Mon, 12 Oct 1998 12:10:05 +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 Ryan Ward wrote: > I think I had some problems with my system, being partially aout and elf. Is > there a way to make sure that my system is all elf vs aout? Besides doing Erm, if you haven't hacked things, your system should handle a mixture of elf and aout things. The upgrade procedure clearly flags which stages it has done (look in /usr/obj). > aout-to-elf? When i did the aout-to-elf it broke in a few places. Maybe my > system was already completely elf? Who knows, but I had problems with my > make world with current and thought that this was the problem. If you had not upgraded, a simple `make world' should have worked, subject to the endless breakages caused by developers including a new boot loader in the build at a time when there is supposed to be a feature freeze. This is not supposed to be happening, regardless of any "OK'd by jkh" claims, IMHO. It's not as though the bootloader will be enabled for the release! If you _had_ upgraded, /etc/objformat would contain OBJFORMAT=elf, and typing objformat would show that the system has defaulted to elf. On a system in that state, setting OBJFORMAT=aout in your environment or in /etc/objformat and doing a `make world' would install binaries in aout format, without updating the elf libraries. Conversely, setting OBJFORMAT=elf and doing a `make world' would install elf binaries again. That's how it is supposed to work. When the tree builds, that is. Sigh. -- 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 Sun Oct 11 20:28:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26475 for freebsd-current-outgoing; Sun, 11 Oct 1998 20:28:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.insolwwb.net (ns.insolwwb.net [206.31.149.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26470 for ; Sun, 11 Oct 1998 20:28:37 -0700 (PDT) (envelope-from mgrommet@insolwwb.net) Received: from mike (fl11.insolwwb.net [206.31.149.80]) by ns.insolwwb.net (8.8.8/8.8.5) with SMTP id WAA21894 for ; Sun, 11 Oct 1998 22:21:06 -0500 (CDT) Message-ID: <001a01bdf590$8252c480$50951fce@mike> From: "Mike Grommet" To: Subject: Problems with DPT RAID (bug?) in oct4 snapshot Date: Sun, 11 Oct 1998 22:29:23 -0500 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.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys... I've been working with Simon Shapiro with a problem occuring with freebsd 2.2.7 and a dpt raid controller that apparently raises its ugly head on some systems... Simon has told me to try out the Oct 4th snapshot as he has not been able to reproduce the problems on this version... however, I've been running into some problems trying to install the snapshot... i downloaded the boot.flp, booted it, then proceed to go through the normal install... I tell it to use the entire drive, then begin to slice it up into filesystems... I tell it which versions to install, and such, set up the network interface so I can install from the internet as always, the problem I have occurs when it tries to newfs the swap partition (and doesnt get any further) Debug reports "DEBUG: unknown major/minor for devtype -" ( I believe this is in reference to da0, disk array 0, for raid array) I get the message on the debug console where it gives "Cross device link" error in newfs and then a rewrite label error. Install then dies at this point, and never continues... The install program returns an error, and I get booted back to the menu system. Please advise? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 21:02:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29475 for freebsd-current-outgoing; Sun, 11 Oct 1998 21:02:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29470 for ; Sun, 11 Oct 1998 21:02:19 -0700 (PDT) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id MAA26432; Mon, 12 Oct 1998 12:38:45 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98021914) with ESMTP id MAA07249; Mon, 12 Oct 1998 12:38:44 +0900 (JST) Message-Id: <199810120338.MAA07249@hotaka.csl.sony.co.jp> To: Brian Somers cc: current@FreeBSD.ORG Subject: Re: Improper sharing of modem bandwidth In-reply-to: Your message of "Fri, 09 Oct 1998 10:58:48 +0100." <199810090958.KAA00774@woof.lan.awfulhak.org> Date: Mon, 12 Oct 1998 12:38:44 +0900 From: Kenjiro Cho Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian, How hard do you think it is to add the following feature to the userland ppp? The issll working group at IETF (http://www.ietf.org/html.charters/issll-charter.html) proposes a suspend/resume style transmission method: "PPP in a real-time oriented HDLC-like framing". (http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-rtf-03.txt) The basic idea is that, if a FIFO based serial chip is used, we are able to control the transmission of each byte so that we can suspend a low-priority packet in the middle of the transmission. In the above draft, the frame format and the negotiation format is defined as an extension to the PPP Multilink fragmentation protocol. With the packet-by-packet control, the latency is more than 500 ms over 64Kbps with 1500-byte MTU. I believe that the latency of telnet will be less than 50 ms even in the middle of ftp, if the suspend/resume is implemented. --Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 21:04:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29746 for freebsd-current-outgoing; Sun, 11 Oct 1998 21:04:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29741 for ; Sun, 11 Oct 1998 21:04:01 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-10-89.camtech.net.au [203.28.1.217]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id NAA21224; Mon, 12 Oct 1998 13:32:54 +0930 (CST) Message-ID: <36217F5B.B03218D3@camtech.net.au> Date: Mon, 12 Oct 1998 13:32:35 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.06 [en] (X11; U; FreeBSD 3.0-BETA i386) MIME-Version: 1.0 To: "oZZ!!!" CC: Edwin Culp , current@FreeBSD.ORG Subject: Re: netscape-4.07 can't work under FreeBSD-3.0-ELF with XFree86-ELF... 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 When you convert your -CURRENT system to ELF (using "make auto-to-elf"), as part of that process it will move any a.out libraries from the /usr/lib, /usr/local/lib and /usr/X11R6/lib directories into subdirectories called aout. If you update your /etc directory properly after this including /etc/rc and /etc/rc.conf, the linker will also search these aout directories for libraries at run time so your Netscape binary will still be able to find the a.out XFree86 libraries and will still run. To avoid having heaps of old a.out libraries lying around, I removed all my ports (except XFree86) using pkg_delete port-name so that when I ran "make aout-to-elf", it would only move the XFree86 libraries into the aout subdirectory. After the conversion to ELF I them removed XFree86 (but it left the a.out libraries behind as it didn't expect them to be in an aout subdirectory). I then rebuilt XFree86, kde, tcsh etc so they'd be in ELF. oZZ!!! wrote: > > On Sun, 11 Oct 1998, Edwin Culp wrote: > > > "oZZ!!!" wrote: > > > > > Hello! > > > How can i run netscape-4.07 under FreeBSD-3.0-ELF with XFree86-ELF ?? > > > If it not possible - how can i run another X-browser ? > > > Opera or somethink else? > > > > > > Rgdz, > > > Осокин Сергей aka oZZ, > > > osa@etrust.ru > > > > > > > I don't now about 4.07 but we run 4.5b2 right out of the box in the > > default directory /usr/lib with no problems. We have are on everthing > > even kernel. I think there is a port for both that should work. > > > > ed > Are your version is -ELF? or a.out? > And what about X-libs? Do you have a.out X-libs? > I haven't X-libs, my X in ELF ONLY! > > Rgdz, > oZZ, > osa@etrust.ru > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 11 23:44:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14266 for freebsd-current-outgoing; Sun, 11 Oct 1998 23:44:07 -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 XAA14252 for ; Sun, 11 Oct 1998 23:44:02 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:3I9fquCgUj4LEYCH4MtctsFhKU0GgdPc@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA28268; Mon, 12 Oct 1998 08:43:30 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810120643.IAA28268@gratis.grondar.za> To: Randy Bush cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure with j4 In-Reply-To: Your message of " Sun, 11 Oct 1998 13:36:32 MST." <199810112036.NAA17243@rip.psg.com> References: <199810112036.NAA17243@rip.psg.com> Date: Mon, 12 Oct 1998 08:43:29 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randy Bush wrote: > buildworld of 1998.09.25 had the following failure on 3.0CAM-19980712-SNAP > with j4, but succeeded when no j4 I have done a _massive_ cleanup of Perl5. This should be fixed as of this message's date/time. 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 12 00:03:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15957 for freebsd-current-outgoing; Mon, 12 Oct 1998 00:03:48 -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 AAA15952 for ; Mon, 12 Oct 1998 00:03:45 -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 QAA17375 for ; Mon, 12 Oct 1998 16:33:30 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA21919; Mon, 12 Oct 1998 16:33:29 +0930 (CST) Message-ID: <19981012163328.B12313@freebie.lemis.com> Date: Mon, 12 Oct 1998 16:33:28 +0930 From: Greg Lehey To: FreeBSD current users Subject: Today's make world breakage 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 ===> gnu/usr.bin/perl/perl dirname: not found ln: lib/CVS/Root: No such file or directory *** Error code 1 I've tried resupping, same 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 Mon Oct 12 00:13:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17089 for freebsd-current-outgoing; Mon, 12 Oct 1998 00:13:56 -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 AAA17084 for ; Mon, 12 Oct 1998 00:13:51 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:tyKxZbNP4S3eT+oxhBS9kypCrVNsAIud@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id JAA28414; Mon, 12 Oct 1998 09:08:12 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810120708.JAA28414@gratis.grondar.za> To: Greg Lehey cc: FreeBSD current users Subject: Re: Today's make world breakage In-Reply-To: Your message of " Mon, 12 Oct 1998 16:33:28 +0930." <19981012163328.B12313@freebie.lemis.com> References: <19981012163328.B12313@freebie.lemis.com> Date: Mon, 12 Oct 1998 09:08:10 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > ===> gnu/usr.bin/perl/perl > dirname: not found > ln: lib/CVS/Root: No such file or directory > *** Error code 1 > > I've tried resupping, same problem. Fixed now. 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 12 00:30:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18711 for freebsd-current-outgoing; Mon, 12 Oct 1998 00:30:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup8.gaffaneys.com [208.155.161.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18701 for ; Mon, 12 Oct 1998 00:30:41 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id HAA20300; Mon, 12 Oct 1998 07:30:23 GMT (envelope-from zach) Message-ID: <19981012023022.A18715@znh.org> Date: Mon, 12 Oct 1998 02:30:22 -0500 From: Zach Heilig To: Alfred , current@FreeBSD.ORG Subject: Re: bitten 3 times already. 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 Alfred on Sun, Oct 11, 1998 at 06:47:25PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 11, 1998 at 06:47:25PM -0400, Alfred wrote: > this is the third time freebsd has decided that wd0s1b wasn't "comfy" > enough for a crashdump and ate a different partition while dumping. ... > also, anyone have something i can do to get a dump of my partitions to > examine why it's confusing the crashdump mechanism? A few questions that maybe might help to sort this out (You can mail these answers to me if you want me to check them): Is that swap partition at least 64K bigger than the amount of RAM you have? (It is good to make at least one swap partition ~25-50% bigger than physical ram if you have multiple swap partitions.. and at least twice as big if you have only one swap partition). Does /usr and the swap device overlap (check 'disklabel wd0s1', /usr is usually on the next partition after the swap partition in the default install)? (size + offset should be equal to the offset of the next used partition) check what 'dumpon -v /dev/wd0s1b' says. make sure 'sysctl kern.dumpdev' matches. -- 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 Mon Oct 12 00:40:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19690 for freebsd-current-outgoing; Mon, 12 Oct 1998 00:40:50 -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 AAA19673 for ; Mon, 12 Oct 1998 00:40:47 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id IAA17137; Mon, 12 Oct 1998 08:34:31 +0100 (BST) Message-ID: <3621B0D1.6BB3D6AD@tdx.co.uk> Date: Mon, 12 Oct 1998 08:33:37 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith CC: "oZZ!!!" , current@FreeBSD.ORG Subject: Re: Buildworld failed with -current as of 10/11/98, 21:00 References: <199810112313.QAA01867@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: > > > strcasecmp.o(.text+0x14a): undefined reference to `___tolower' > > > strcasecmp.o(.text+0x151): undefined reference to `_CurrentRuneLocale' > > > *** Error code 1 > > > 1 error > > > > > > Stop. > > > > > > > Yeah... :-((( > > I have this problem 2.... :-((( > > Rebuild and reinstall libstand. Also, you *must* read the -current > list. Hmmm... I do read -current... Maybe I missed something? - Surely if libstand needs rebuilding part of the 'build world' should be to build it? - It rebuilds all the other tools and stuff it needs to ensure a 'build world' will succeed...? Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 01:48:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27052 for freebsd-current-outgoing; Mon, 12 Oct 1998 01:48:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27029 for ; Mon, 12 Oct 1998 01:47:58 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id BAA00239 for ; Mon, 12 Oct 1998 01:47:53 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id KAA21715 for freebsd-current@freefall.cdrom.com; Mon, 12 Oct 1998 10:47:43 +0200 (MEST) (envelope-from kuku) Date: Mon, 12 Oct 1998 10:47:43 +0200 (MEST) From: Christoph Kukulies Message-Id: <199810120847.KAA21715@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.cdrom.com Subject: /usr/lib/libskey.so.2: Undefined symbol "crypt" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since a couple of days my -current (elf) system (the 19981004 SNAP) suffers from the fact that I cannot su nor login as root at the console any longer (despite from going single user). I built the international descrypt stuff, installed it , created the links in /usr/lib and since then I'm getting /usr/libexec/ld-elf.so.1: /usr/lib/libskey.so.2: Undefined symbol "crypt". What can I do to repair this? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.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 12 03:16:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03182 for freebsd-current-outgoing; Mon, 12 Oct 1998 03:16:00 -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 DAA03171 for ; Mon, 12 Oct 1998 03:15:58 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id LAA10376 for ; Mon, 12 Oct 1998 11:15:43 +0100 (BST) Message-ID: <3621D69A.4B520050@tdx.co.uk> Date: Mon, 12 Oct 1998 11:14:50 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Make 'installworld' problem... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sources current as of 09:40 BST, 12/10/98... Buildworld went OK, and just as I thought I was out of the woods, 'install world' fails with: " ===> lib/csu/i386-elf install -c -o root -g wheel -m 444 crt1.o /usr/lib/crt1.o install -c -o root -g wheel -m 444 crtbegin.o /usr/lib/crtbegin.o install -c -o root -g wheel -m 444 crtend.o /usr/lib/crtend.o install -c -o root -g wheel -m 444 crti.o /usr/lib/crti.o install -c -o root -g wheel -m 444 crtn.o /usr/lib/crtn.o install -c -o root -g wheel -m 444 gcrt1.o /usr/lib/gcrt1.o install -c -o root -g wheel -m 444 crtbegin.so /usr/lib/crtbeginS.o install -c -o root -g wheel -m 444 crtend.so /usr/lib/crtendS.o ===> lib/libcom_err install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/com_err.h /usr/include install -c -o root -g wheel -m 444 libcom_err.a /usr/lib install -c -o root -g wheel -m 444 libcom_err_p.a /usr/lib install: libcom_err_p.a: No such file or directory " Unfortunately I've run out of time today to do any more, or try to figure this one out a little more... :-( Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 04:49:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12610 for freebsd-current-outgoing; Mon, 12 Oct 1998 04:49:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12603; Mon, 12 Oct 1998 04:49:56 -0700 (PDT) (envelope-from rkw@Dataplex.NET) Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id IAA07522; Mon, 12 Oct 1998 08:29:29 -0500 (CDT) (envelope-from rkw@dataplex.net) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199810112120.OAA14918@bubble.didi.com> References: (message from Karl Pielorz on Sun, 11 Oct 1998 20:46:53 +0100 (BST)) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 12 Oct 1998 06:49:26 -0500 To: asami@FreeBSD.ORG (Satoshi Asami) From: Richard Wackerbarth Subject: Re: Never ending 'make clean' in kde port? Cc: kpielorz@tdx.co.uk, eivind@yes.no, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:20 PM -0500 10/11/98, Satoshi Asami wrote: > * Nope, your right - I let it run again, it wasn't quite endless - just 60+ > * lines... Following the files through I think I can see what's happening, > * dependants that depend on stuff that's already depended on (but gets > * cleaned again anyway)... ;-) Not quite a mess, just a bit convoluted > >Well, if someone wants to submit a patch to fix this, I'm all ears. :) This is a clear case of the evils of "recursive make". http://www.canb.auug.org.au/~millerp/rmch/recu-make-cons-harm.html The recommended solution is to transfer the "clean" operation to the top of the ports tree and do it in one "make" at that point. This allows "make" to resolve the multiple target references and do them only once. I can supply a prototype. I will offer to implement it (post 3.0 release) if the changes will get committed. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 05:00:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13294 for freebsd-current-outgoing; Mon, 12 Oct 1998 05:00:35 -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 FAA13288; Mon, 12 Oct 1998 05:00:28 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:Yg8luHc6i/7rhfKIVBE1MGtD8XQRetWr@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id NAA01144; Mon, 12 Oct 1998 13:59:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810121159.NAA01144@gratis.grondar.za> To: Richard Wackerbarth cc: asami@FreeBSD.ORG (Satoshi Asami), kpielorz@tdx.co.uk, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Never ending 'make clean' in kde port? In-Reply-To: Your message of " Mon, 12 Oct 1998 06:49:26 EST." References: (message from Karl Pielorz on Sun, 11 Oct 1998 20:46:53 +0100 (BST)) Date: Mon, 12 Oct 1998 13:59:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Wackerbarth wrote: > The recommended solution is to transfer the "clean" operation to the top > of the ports tree and do it in one "make" at that point. This allows "make" > to resolve the multiple target references and do them only once. > > I can supply a prototype. I will offer to implement it (post 3.0 release) if > the changes will get committed. There already exists a knob; NOCLEANDEPENDS=yes. Perhaps it needs some refinement? Write the code, and if folk like it, they'll commit 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 Mon Oct 12 05:21:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14439 for freebsd-current-outgoing; Mon, 12 Oct 1998 05:21:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14433; Mon, 12 Oct 1998 05:21:54 -0700 (PDT) (envelope-from rkw@Dataplex.NET) Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id JAA07575; Mon, 12 Oct 1998 09:01:59 -0500 (CDT) (envelope-from rkw@dataplex.net) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199810121159.NAA01144@gratis.grondar.za> References: Your message of " Mon, 12 Oct 1998 06:49:26 EST." (message from Karl Pielorz on Sun, 11 Oct 1998 20:46:53 +0100 (BST)) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 12 Oct 1998 07:20:25 -0500 To: Mark Murray From: Richard Wackerbarth Subject: Re: Never ending 'make clean' in kde port? Cc: asami@FreeBSD.ORG (Satoshi Asami), kpielorz@tdx.co.uk, eivind@yes.no, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:59 AM -0500 10/12/98, Mark Murray wrote: >There already exists a knob; NOCLEANDEPENDS=yes. Perhaps it needs some >refinement? >Write the code, and if folk like it, they'll commit it. Sorry, Mark. Although I think that the default should be reversed such that the clean is not recursive, this does not address the problem. The problem occurs when someone wants to do a recursive clean. The present methodology repeatedly cleans subtrees because they appear multiple times in the full walk of the dependancy tree. The desired behavior would recognize the common subtree and truncate the repeated walks of those subtrees. One method to accomplish this is to allow "make" to establish a target for each of the nodes. Another method would be to have the individual "Makefile"s test to see if there is anything to clean and reccur only if there were. This method would produce slightly different results. Assume that "A" requires "B". Start from a 'clean' tree. Make "B". Now clean "A". In the present methodology, you clean not only "A", but also everything that it requires. Thus "B" would also be cleaned. In the latter methodology, "B" would not be examined because it was not make dirty as a result of building "A". It is unclear which result is "correct". Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 05:41:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15740 for freebsd-current-outgoing; Mon, 12 Oct 1998 05:41:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15735 for ; Mon, 12 Oct 1998 05:41:23 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id FAA01473; Mon, 12 Oct 1998 05:40:52 -0700 (PDT) Message-Id: <199810121240.FAA01473@mailgate.cadence.com> Received: from symnt3.cadence.com(194.32.101.100) by mailgate.cadence.com via smap (mjr-v1.2) id xma908196046.001441; Mon, 12 Oct 98 05:40:46 -0700 Received: from pc287-cam.cadence.com (d194032096136.Cadence.COM [194.32.96.136]) by symnt3.Cadence.COM with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id Q4J1CCBM; Mon, 12 Oct 1998 13:41:06 +0100 Comments: Authenticated sender is From: "Duncan Barclay" To: Richard Wackerbarth Date: Mon, 12 Oct 1998 13:40:23 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Never ending 'make clean' in kde port? Reply-to: dmlb@ragnet.demon.co.uk CC: current@FreeBSD.ORG In-reply-to: References: <199810112120.OAA14918@bubble.didi.com> X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Richard > > This is a clear case of the evils of "recursive make". > http://www.canb.auug.org.au/~millerp/rmch/recu-make-cons-harm.html Warning: this paper will chnage your make files forever. I put together a build system based on this which also puts together a package and a port. It makes like so much easier. Duncan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 05:49:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16515 for freebsd-current-outgoing; Mon, 12 Oct 1998 05:49:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16509 for ; Mon, 12 Oct 1998 05:49:31 -0700 (PDT) (envelope-from Pierre.David@prism.uvsq.fr) Received: from guillotin.prism.uvsq.fr (guillotin.prism.uvsq.fr [193.51.25.1]) by soleil.uvsq.fr (8.9.1/jtpda-5.3.1) with ESMTP id OAA29307 for ; Mon, 12 Oct 1998 14:49:02 +0200 (METDST) Received: from gibet.prism.uvsq.fr (gibet.prism.uvsq.fr [193.51.25.3]) by guillotin.prism.uvsq.fr (8.8.4/jtpda-5.2) with ESMTP id OAA28788 for ; Mon, 12 Oct 1998 14:49:01 +0200 (MET DST) Received: from (pda@localhost) by gibet.prism.uvsq.fr (8.8.8/jtpda-5.2) id OAA22669 for current@FreeBSD.ORG; Mon, 12 Oct 1998 14:49:01 +0200 (CEST) Message-ID: <19981012144900.A22619@gibet.prism.uvsq.fr> Date: Mon, 12 Oct 1998 14:49:00 +0200 From: Pierre DAVID To: current@FreeBSD.ORG Subject: Make buildworld error Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Since a few days, I cannot make world. Even since last commits (which solved other problems), the problem is still there. So, is anybody aware of it? ------------------------------------------------------------------------------ $ make -j 4 -DNOGAMES -DNOSECURE -DNOPROFILE buildworld ... -------------------------------------------------------------- >>> Building legacy boot -------------------------------------------------------------- ... ===> rawboot --- all --- ===> biosboot --- boot --- cc -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mno-486 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 -DDO_BAD144 -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -nostdinc -I/usr/src/sys/i386/boot/biosboot/../../../../include -I/usr/src/sys/i386/boot/biosboot/../../.. -I/usr/obj/aout/usr/src/sys/i386/boot/biosboot -I/usr/obj/aout/usr/src/tmp/usr/include -N -T 0 -nostdlib -static -o boot start.o table.o boot2.o boot.o asm.o bios.o serial.o probe_keyboard.o io.o disk.o sys.o /usr/obj/elf/usr/src/tmp/usr/libexec/aout/ld: start.o: malformed input file (not rel or archive) *** Error code 1 1 error ------------------------------------------------------------------------------ Where does this "-T 0" come from, in /usr/src/sys/i386/boot/biosboot/Makefile ? Thanks in advance, Pierre David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 06:06:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18349 for freebsd-current-outgoing; Mon, 12 Oct 1998 06:06:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA18344 for ; Mon, 12 Oct 1998 06:06:35 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 1435 invoked by uid 1000); 12 Oct 1998 14:09:48 -0000 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: <001a01bdf590$8252c480$50951fce@mike> Date: Mon, 12 Oct 1998 10:09:48 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Grommet Subject: RE: Problems with DPT RAID (bug?) in oct4 snapshot Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Grommet, On 12-Oct-98 you wrote: > Hi guys... I've been working with Simon Shapiro with a problem occuring > with > freebsd 2.2.7 and a dpt raid controller > that apparently raises its ugly head on some systems... > > Simon has told me to try out the Oct 4th snapshot as he has not been > able to > reproduce the problems > on this version... > > however, I've been running into some problems trying to install the > snapshot... > i downloaded the boot.flp, booted it, then proceed to go through the > normal > install... > > I tell it to use the entire drive, then begin to slice it up into > filesystems... > I tell it which versions to install, and such, set up the network > interface > so I can install from the internet as always, > > the problem I have occurs when it tries to newfs the swap partition (and > doesnt get any further) > > Debug reports "DEBUG: unknown major/minor for devtype -" > ( I believe this is in reference to da0, disk array 0, for raid array) > > I get the message on the debug console where it gives "Cross device > link" > error in newfs and then a > rewrite label error. > > Install then dies at this point, and never continues... The install > program > returns an error, and I get booted back to the menu system. > > Please advise? Clarification: The make release of the 4th of October installs correctly for me. I see these error messages but the installation works fine otherwise. Maybe because the partitions I specifiy already exist. Maybe because I have fdisk, with a DOS slice underneath the BSD partitions. I don't think this is a DPT problem, but again, this may be a large partition (> 4GB) problem. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 07:18:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28372 for freebsd-current-outgoing; Mon, 12 Oct 1998 07:18:08 -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 HAA28365 for ; Mon, 12 Oct 1998 07:18:05 -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 JAA01627; Mon, 12 Oct 1998 09:16:23 -0500 (EST) Date: Mon, 12 Oct 1998 09:16:23 -0500 (EST) From: John Fieber To: Matthew Thyer cc: oZZ!!! , Edwin Culp , current@FreeBSD.ORG Subject: Re: netscape-4.07 can't work under FreeBSD-3.0-ELF with XFree86-ELF... In-Reply-To: <36217F5B.B03218D3@camtech.net.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, 12 Oct 1998, Matthew Thyer wrote: > To avoid having heaps of old a.out libraries lying around, I removed all > my ports (except XFree86) using pkg_delete port-name so that when I ran > "make aout-to-elf", it would only move the XFree86 libraries into the aout > subdirectory. Be very careful doing that though! There are a distressingly large number of ports that are broken on ELF systems, so check the current port status before you nuke important applications. -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 12 08:24:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08738 for freebsd-current-outgoing; Mon, 12 Oct 1998 08:24:30 -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 IAA08571 for ; Mon, 12 Oct 1998 08:23:06 -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 LAA13243; Mon, 12 Oct 1998 11:23:57 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Mon, 12 Oct 1998 11:23:57 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Zach Heilig cc: current@FreeBSD.ORG Subject: Re: bitten 3 times already. In-Reply-To: <19981012023022.A18715@znh.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 Mon, 12 Oct 1998, Zach Heilig wrote: > > this is the third time freebsd has decided that wd0s1b wasn't "comfy" > > enough for a crashdump and ate a different partition while dumping. > .... > > also, anyone have something i can do to get a dump of my partitions to > > examine why it's confusing the crashdump mechanism? > > A few questions that maybe might help to sort this out (You can mail these > answers to me if you want me to check them): > > Is that swap partition at least 64K bigger than the amount of RAM you have? > (It is good to make at least one swap partition ~25-50% bigger than physical > ram if you have multiple swap partitions.. and at least twice as big if > you have only one swap partition). > > Does /usr and the swap device overlap (check 'disklabel wd0s1', /usr is usually > on the next partition after the swap partition in the default install)? > (size + offset should be equal to the offset of the next used partition) > > check what 'dumpon -v /dev/wd0s1b' says. > make sure 'sysctl kern.dumpdev' matches. disklabel -r wd0s1 a: 81920 0 4.2BSD 0 0 0 # (Cyl. 0 - 5*) b: 614400 163840 swap # (Cyl. 10*-48*) c: 8385867 0 unused 0 0 # (Cyl. 0 -521*) e: 81920 81920 4.2BSD 0 0 0 # (Cyl. 5*-10*) f: 4096000 778240 4.2BSD 0 0 0 # (Cyl. 48*-303*) g: 3511627 4874240 4.2BSD 0 0 0 # (Cyl. 303*-521*) /dev/wd0s1a on / (local, soft-updates, writes: sync 4 async 375) /dev/wd0s1f on /usr (local, soft-updates, writes: sync 12 async 7952) /dev/wd0s1e on /var (local, soft-updates, writes: sync 77 async 350) /dev/wd0s1g on /usr/home (local, soft-updates, writes: sync 201 async1131) /dev/wd0s2e on /spare (local, soft-updates, writes: sync 2 async 0) Please for the love of god don't tell me all my partitions overlap by one cyl :( (well, unless they do, so i can dump them quick and fix this) :) top: Mem: 44M Active, 29M Inact, 16M Wired, 33M Cache, 7340K Buf, 616K Free Swap: 300M Total, 300M Free So i have plenty of swap vs RAM which is 128megs I double checked the dump device before _the bad thing_ happened. it said: kern.dumpdev: { major = 0, minor = 131073 } brw-r----- 1 root operator 0, 0x00020001 Oct 11 14:58 /dev/wd0s1b Also: wdc0 at 0x1f0-0x1f7 irq 14 flags 0x7fff7fff on isa wdc0: unit 0 (wd0): , LBA, DMA, multi-block-16, sleep-hack wd0: 8063MB (16514064 sectors), 17475 cyls, 15 heads, 63 S/T, 512 B/S i'm quite sure i have LBA translations going on, however i'm kinda certain that the disk driver isn't running amok because all my other partitions were fine (except /usr) thank you for taking the time to help me with this, go an idea of what's going on here? thanks, 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 12 08:46:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11918 for freebsd-current-outgoing; Mon, 12 Oct 1998 08:46:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgate.aist-nara.ac.jp (fse4.aist-nara.ac.jp [163.221.76.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11912 for ; Mon, 12 Oct 1998 08:46:21 -0700 (PDT) (envelope-from takas-su@is.aist-nara.ac.jp) Received: from decpc20.aist-nara.ac.jp (decpc20.aist-nara.ac.jp [163.221.172.33]) by mailgate.aist-nara.ac.jp (8.8.5+2.7Wbeta5/3.6W/NAIST/GATE-3.4c-fake) with ESMTP id AAA15407 for ; Tue, 13 Oct 1998 00:45:22 +0900 (JST) Received: from is (takas-su@localhost) by decpc20.aist-nara.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl5/NAIST/2.0) id AAA11964; Tue, 13 Oct 1998 00:46:28 +0900 (JST) Date: Tue, 13 Oct 1998 00:46:28 +0900 (JST) Message-Id: <199810121546.AAA11964@decpc20.aist-nara.ac.jp> From: takas-su@is.aist-nara.ac.jp (SUGIMURA Takashi/ =?ISO-2022-JP?B?GyRCP3lCPDUuO04bKEI=?=) To: current@FreeBSD.ORG Subject: Re: make buildworld fails In-Reply-To: Your message of "Sun, 11 Oct 1998 20:54:06 +0900 (JST)". <199810111154.UAA09603@decpc20.aist-nara.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199810111154.UAA09603@decpc20.aist-nara.ac.jp> I wrote: >> >> OK. I've committed a fix. Try it with >> >> /usr/src/sys/boot/i386/btx/lib/Makefile 1.2. >> >> >> >> Sure. >> I will test it again after I can get it. >> Today I succeeded to make buildworld/installworld. Thank you. --- SUGIMURA Takashi (takas-su@is.aist-nara.ac.jp) URL: http://hawk.aist-nara.ac.jp/%7Etakas-su/ (sorry only in Japanese) Software Engineering lab. of NAIST, 2nd grade of Master, The FreeBSD Japanese Documentation 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 12 09:14:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17824 for freebsd-current-outgoing; Mon, 12 Oct 1998 09:14: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 JAA17819 for ; Mon, 12 Oct 1998 09:14:24 -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 CAA12373; Tue, 13 Oct 1998 02:14:03 +1000 Date: Tue, 13 Oct 1998 02:14:03 +1000 From: Bruce Evans Message-Id: <199810121614.CAA12373@godzilla.zeta.org.au> To: bright@hotjobs.com, zach@gaffaneys.com Subject: Re: bitten 3 times already. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Also: >wdc0 at 0x1f0-0x1f7 irq 14 flags 0x7fff7fff on isa >wdc0: unit 0 (wd0): , LBA, DMA, multi-block-16, sleep-hack >wd0: 8063MB (16514064 sectors), 17475 cyls, 15 heads, 63 S/T, 512 B/S > >i'm quite sure i have LBA translations going on, however i'm kinda certain >that the disk driver isn't running amok because all my other partitions >were fine (except /usr) > >thank you for taking the time to help me with this, go an idea of what's >going on here? Dumps and LBA mode should't be mixed, since the dump routine doesn't support LBA mode and it uses CHS mode with nominal geometry if LBA mode is configured. Dumps only work if the nominal geometry is the same as the actual one. Otherwise, dumps write sectors to the wrong places, possibly outside the partition. I don't know how the geometry can be H=15/S=63. This looks like the actual geometry, but the probe should report the nominal one which should be H=255/S=63 for this size of drive. It's suprising that this size of drive is made. It's only 31MB over the 1024*255*63 limit, and exceeding this limit causes problems. Fix: don't use LBA mode. CHS mode should work up to size 65535*255*63 sectors if it works at all. 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 12 09:28:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19249 for freebsd-current-outgoing; Mon, 12 Oct 1998 09:28:14 -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 JAA19244 for ; Mon, 12 Oct 1998 09:28:11 -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 MAA13507; Mon, 12 Oct 1998 12:29:19 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Mon, 12 Oct 1998 12:29:19 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Bruce Evans cc: zach@gaffaneys.com, current@FreeBSD.ORG Subject: Re: bitten 3 times already. In-Reply-To: <199810121614.CAA12373@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 > >Also: > >wdc0 at 0x1f0-0x1f7 irq 14 flags 0x7fff7fff on isa > >wdc0: unit 0 (wd0): , LBA, DMA, multi-block-16, sleep-hack > >wd0: 8063MB (16514064 sectors), 17475 cyls, 15 heads, 63 S/T, 512 B/S > > > >i'm quite sure i have LBA translations going on, however i'm kinda certain > >that the disk driver isn't running amok because all my other partitions > >were fine (except /usr) > > > >thank you for taking the time to help me with this, go an idea of what's > >going on here? > > Dumps and LBA mode should't be mixed, since the dump routine doesn't > support LBA mode and it uses CHS mode with nominal geometry if LBA mode > is configured. Dumps only work if the nominal geometry is the same as > the actual one. Otherwise, dumps write sectors to the wrong places, > possibly outside the partition. > > I don't know how the geometry can be H=15/S=63. This looks like the > actual geometry, but the probe should report the nominal one which should > be H=255/S=63 for this size of drive. It's suprising that this size of > drive is made. It's only 31MB over the 1024*255*63 limit, and exceeding > this limit causes problems. > > Fix: don't use LBA mode. CHS mode should work up to size 65535*255*63 > sectors if it works at all. no, this is a fix: /usr/src % diff -u /usr/src/etc/rc.conf ~/rc.conf --- /usr/src/etc/rc.conf Thu Oct 8 17:20:48 1998 +++ /usr/home/bright/rc.conf Mon Oct 12 12:23:52 1998 @@ -158,6 +158,7 @@ lpd_flags="" # Flags to lpd (if enabled). sendmail_enable="YES" # Run the sendmail daemon (or NO). sendmail_flags="-bd -q30m" # -bd is pretty mandatory. +# don't enable dumping on IDE disks that are using LBA addressing! dumpdev="NO" # Device name to crashdump to (if enabled). check_quotas="NO" # Check quotas (or NO). accounting_enable="NO" # Turn on process accounting (or NO). -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 09:31:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19635 for freebsd-current-outgoing; Mon, 12 Oct 1998 09:31:45 -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 JAA19614 for ; Mon, 12 Oct 1998 09:31:30 -0700 (PDT) (envelope-from pam@polynet.lviv.ua) From: pam@polynet.lviv.ua Received: (qmail 518 invoked by alias); 12 Oct 1998 16:31:11 -0000 Received: (qmail 513 invoked from network); 12 Oct 1998 16:31:10 -0000 Received: from postoffice.polynet.lviv.ua (194.44.138.1) by guard.polynet.lviv.ua with SMTP; 12 Oct 1998 16:31:10 -0000 Received: (qmail 12603 invoked by uid 1001); 12 Oct 1998 16:31:10 -0000 Date: 12 Oct 1998 19:31:10 +0300 Date: Mon, 12 Oct 1998 19:31:10 +0300 (EEST) X-Sender: pam@NetSurfer.lp.lviv.ua To: current@FreeBSD.ORG Subject: Buildworld breaks on usr.bin/chpass/pw_yp.c 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! For almost a week I can't build new world (updating via cvsup daily). Everytime build bombs out like this: cc -nostdinc -O -pipe -I/usr/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb -I/usr/src/usr.bin/chpass/../../usr.sbin/vipw -DYP -I. -I/usr/src/usr.bin/chpass/../../libexec/ypxfr -I/usr/src/usr.bin/chpass/../../usr.sbin/rpc.yppasswdd -Dyp_error=warnx -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/chpass/pw_yp.c /usr/src/usr.bin/chpass/pw_yp.c:68: yppasswd_private.h: No such file or directory /usr/src/usr.bin/chpass/pw_yp.c: In function `get_yp_master': /usr/src/usr.bin/chpass/pw_yp.c:341: `YP_SOCKNAME' undeclared (first use this function) /usr/src/usr.bin/chpass/pw_yp.c:341: (Each undeclared identifier is reported only once /usr/src/usr.bin/chpass/pw_yp.c:341: for each function it appears in.) /usr/src/usr.bin/chpass/pw_yp.c: In function `yp_submit': /usr/src/usr.bin/chpass/pw_yp.c:419: storage size of `master_yppasswd' isn't known /usr/src/usr.bin/chpass/pw_yp.c:424: `YP_SOCKNAME' undeclared (first use this function) It can't find yppasswd_private.h which really resides in usr.bin/passwd/ I've already tried ro remove entire usr.bin directory and re-sup but it didn't bring me any futher. Any upcoming fixes? suggestions? 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 Mon Oct 12 09:32:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19802 for freebsd-current-outgoing; Mon, 12 Oct 1998 09:32:12 -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 JAA19786 for ; Mon, 12 Oct 1998 09:32:08 -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 CAA13430; Tue, 13 Oct 1998 02:31:49 +1000 Date: Tue, 13 Oct 1998 02:31:49 +1000 From: Bruce Evans Message-Id: <199810121631.CAA13430@godzilla.zeta.org.au> To: bde@zeta.org.au, bright@hotjobs.com, zach@gaffaneys.com Subject: Re: bitten 3 times already. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>wdc0 at 0x1f0-0x1f7 irq 14 flags 0x7fff7fff on isa ^ ^ >>wdc0: unit 0 (wd0): , LBA, DMA, multi-block-16, sleep-hack >>wd0: 8063MB (16514064 sectors), 17475 cyls, 15 heads, 63 S/T, 512 B/S >... I wrote: >I don't know how the geometry can be H=15/S=63. This looks like the >actual geometry, but the probe should report the nominal one which should >be H=255/S=63 for this size of drive. It's suprising that this size of >drive is made. It's only 31MB over the 1024*255*63 limit, and exceeding >this limit causes problems. The geometry is forced to a possibly wrong value, er shape, using the WDOPT_FORCEHD bits (0x0f000f00). Normally this is a no-op, since the driver tells the drive which geometry to use, but the driver doesn't bother to tell the drive this if LBA mode is configured, so a mismatch is possible. 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 12 09:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21602 for freebsd-current-outgoing; Mon, 12 Oct 1998 09:46:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21576 for ; Mon, 12 Oct 1998 09:46:33 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.8.8) with SMTP id JAA07663 for ; Mon, 12 Oct 1998 09:48:39 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Date: Mon, 12 Oct 1998 09:48:39 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: current@FreeBSD.ORG Subject: devstat warning 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 following appeared in the kernel log (I don't know what was going on at the time, as I didn't notice it until I read this morning's security check): devstat_end_transaction: HELP!! busy_count is < 0! Can someone tell me what this means? -- Brian Buchanan brian@smarter.than.nu brian@soda.CSUA.Berkeley.EDU "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 09:52:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22524 for freebsd-current-outgoing; Mon, 12 Oct 1998 09:52:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA22518 for ; Mon, 12 Oct 1998 09:52:31 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA09030; Mon, 12 Oct 1998 12:57:15 -0400 From: Bill Paul Message-Id: <199810121657.MAA09030@skynet.ctr.columbia.edu> Subject: Re: Buildworld breaks on usr.bin/chpass/pw_yp.c To: pam@polynet.lviv.ua Date: Mon, 12 Oct 1998 12:57:14 -0400 (EDT) Cc: current@FreeBSD.ORG In-Reply-To: from "pam@polynet.lviv.ua" at Oct 12, 98 07:31:10 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, pam@polynet.lviv.ua had to walk into mine and say: > > Hi everybody! > > For almost a week I can't build new world (updating via cvsup daily). > Everytime build bombs out like this: > > cc -nostdinc -O -pipe -I/usr/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb > -I/usr/src/usr.bin/chpass/../../usr.sbin/vipw -DYP -I. > -I/usr/src/usr.bin/chpass/../../libexec/ypxfr > -I/usr/src/usr.bin/chpass/../../usr.sbin/rpc.yppasswdd -Dyp_error=warnx > -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/chpass/pw_yp.c > /usr/src/usr.bin/chpass/pw_yp.c:68: yppasswd_private.h: No such file or > directory > /usr/src/usr.bin/chpass/pw_yp.c: In function `get_yp_master': > /usr/src/usr.bin/chpass/pw_yp.c:341: `YP_SOCKNAME' undeclared (first use > this function) > /usr/src/usr.bin/chpass/pw_yp.c:341: (Each undeclared identifier is > reported only once > /usr/src/usr.bin/chpass/pw_yp.c:341: for each function it appears in.) > /usr/src/usr.bin/chpass/pw_yp.c: In function `yp_submit': > /usr/src/usr.bin/chpass/pw_yp.c:419: storage size of `master_yppasswd' > isn't known > /usr/src/usr.bin/chpass/pw_yp.c:424: `YP_SOCKNAME' undeclared (first use > this function) > > It can't find yppasswd_private.h which really resides in usr.bin/passwd/ *Bzzzt!* Wrong. yppasswd_private.h is supposed to be generated by rpcgen from src/usr.sbin/rpc.yppasswdd/yppasswd_private.x. However you have not shown the part of the compilation where it tries to generate that header file, so I can't tell you what the real problem is. I'm suspicious of your particular sources since body else has complained of these problems (and there have been full BETA builds during the last week). If you have a copy of yppasswd_private.h in usr.bin/passwd, then that's a mistake: remove it. Both the passwd and chpass builds generate the file since they need it, however it should go in the 'obj' directory and be removed by a make clean. > I've already tried ro remove entire usr.bin directory and re-sup but it > didn't bring me any futher. Any upcoming fixes? suggestions? Try resup-ing usr.sbin instead. That's where yppasswd_private.x lives. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 10:10:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24953 for freebsd-current-outgoing; Mon, 12 Oct 1998 10:10:10 -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 KAA24865 for ; Mon, 12 Oct 1998 10:10:04 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id LAA25293; Mon, 12 Oct 1998 11:09:48 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810121709.LAA25293@panzer.plutotech.com> Subject: Re: devstat warning In-Reply-To: from "Brian W. Buchanan" at "Oct 12, 98 09:48:39 am" To: brian@CSUA.Berkeley.EDU (Brian W. Buchanan) Date: Mon, 12 Oct 1998 11:09:48 -0600 (MDT) Cc: 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 Brian W. Buchanan wrote... > The following appeared in the kernel log (I don't know what was going on > at the time, as I didn't notice it until I read this morning's security > check): > > devstat_end_transaction: HELP!! busy_count is < 0! > > Can someone tell me what this means? It means: - you don't have the latest kernel (which indicates which driver ran into the problem) - The driver has a bug in its devstat implementation. I know for sure that there are problems in the wd driver w.r.t. devstat. Mike hasn't been able to track them down, though. Don't worry, it's not a harmful bug, it just means that your disk statistics will be a little off. I plan on disabling this warning before 3.0, so people don't get confused, upset, distraught, etc. over it. I'll re-enable it after 3.0, though. It has exposed bugs in the devstat implementation of several drivers that might not have been found otherwise. 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 12 10:12:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25226 for freebsd-current-outgoing; Mon, 12 Oct 1998 10:12:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monterosa.urbanet.ch (monterosa-Core1.urbanet.ch [195.202.193.104]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA25216 for ; Mon, 12 Oct 1998 10:12:23 -0700 (PDT) (envelope-from fjaccard@urbanet.ch) Received: (qmail 706 invoked from network); 12 Oct 1998 17:12:01 -0000 Received: from unknown (HELO sicel-3-213) (195.202.196.213) by monterosa.urbanet.ch with SMTP; 12 Oct 1998 17:12:01 -0000 Reply-To: From: "Francois E Jaccard" To: Subject: [GIMPS] /proc/net/route needed Date: Mon, 12 Oct 1998 19:11:49 +0200 Message-ID: <000001bdf603$663ab460$0100a8c0@sicel-3-213.urbanet.ch> 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.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am trying to run the linux version of the GIMPS (mprime 16.4). It works but does not connect top the server. I did a ktrace and it fails to read /proc/net/route. Is there anyway to have this /proc/net emulated or any way to have mprime connect? I have installed the linux_lib version 2.5. Thanks! -- Francois Jaccard Public Key: http://keys.pgp.com:11371/pks/lookup?op=get&-search=0x3D7B9109 PGP Key Fingerprint:9F69 61FA 0681 C632 0B4A 3F37 D655 477B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 10:35:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29258 for freebsd-current-outgoing; Mon, 12 Oct 1998 10:35:37 -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 KAA29250 for ; Mon, 12 Oct 1998 10:35:34 -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 TAA23076 for ; Mon, 12 Oct 1998 19:40:28 +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 TAA17331 for ; Mon, 12 Oct 1998 19:54:39 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id TAA15664; Mon, 12 Oct 1998 19:47:16 +0200 (CEST) Message-ID: <19981012194716.53997@deepo.prosa.dk> Date: Mon, 12 Oct 1998 19:47:16 +0200 From: Philippe Regnauld To: freebsd-current@FreeBSD.ORG Subject: 3.0-19981009-BETA + 2840 AHA + camcontrol stop/start = panic 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 Conf: 486-100 16MB SCSI: AHA-2840 (Vesa controller) Seagate 1GB HAWK Symptom: - insalled 3.0-19981009-BETA, dedicated (entire disk) partition - rebooted, changed to root and typed (all this with the GENERIC kernel): # camcontrol stop (click... spin down)... [pause] I get the prompt back # camcontrol start (spins up) camcontrol start/stop takes 0/1 argument # couple of seconds later: panic... virtual address: 0x24 code: sup. read, page not present inst pointer: 0x8:0xf010553d stack pointer: 0x10:0xf0277ee4 frame pointer: 0x10:0xf0277eec code seg: base 0x0, limit 0xfffff, type 0x1b dpl 0, pres 1, def32 1, gran 1 ... interrupt mask: cam trap #: 12 panic: page fault syncing disks... 1 1 1 1 1 1 1 ... 1 1 giving up -- -[ 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 12 10:38:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29789 for freebsd-current-outgoing; Mon, 12 Oct 1998 10:38:08 -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 KAA29660 for ; Mon, 12 Oct 1998 10:37:58 -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 SAA05320; Mon, 12 Oct 1998 18:37:43 +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 LAA00663; Mon, 12 Oct 1998 11:21:07 +0100 (BST) (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199810121021.LAA00663@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Kenjiro Cho cc: Brian Somers , current@FreeBSD.ORG Subject: Re: Improper sharing of modem bandwidth In-reply-to: Your message of "Mon, 12 Oct 1998 12:38:44 +0900." <199810120338.MAA07249@hotaka.csl.sony.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 11:21:06 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Brian, > > How hard do you think it is to add the following feature to the > userland ppp? > > The issll working group at IETF > (http://www.ietf.org/html.charters/issll-charter.html) > proposes a suspend/resume style transmission method: > "PPP in a real-time oriented HDLC-like framing". > (http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-rtf-03.txt) > > The basic idea is that, if a FIFO based serial chip is used, we are > able to control the transmission of each byte so that we can suspend a > low-priority packet in the middle of the transmission. > In the above draft, the frame format and the negotiation format is > defined as an extension to the PPP Multilink fragmentation protocol. > > With the packet-by-packet control, the latency is more than 500 ms > over 64Kbps with 1500-byte MTU. > I believe that the latency of telnet will be less than 50 ms even in > the middle of ftp, if the suspend/resume is implemented. This is all quite plausible, but with a couple of caveats, both of which, after a cursory glance at the above pages, I didn't see included. The first problem is the tty buffer. Ppp, when passed a fragment, will (usually) attempt to write the whole thing to a non-blocking tty. The tty will already have reported (via select()) that it's writable. Short writes will be continued the next time the descriptor tells select() it's writable. This phenomena is likely to affect latency calculations - the bigger the tty buffer, the greater the latency would be - despite suspend/resume. I don't know if a kernel implementation would have any more control over this sort of thing though, and this isn't a show-stopper by any means. The second problem is that a packet/fragment must be compressed (if (link level) CCP has been negotiated) prior to transmission. Any traffic that wants to be sent during the transmission of a compressed fragment must either a) be sent uncompressed b) be sent compressed using a different dictionary c) wait for the rest of the interrupted packet on the remote end so that the remote can decompress in the correct order. a) Problems may arise for the server->client traffic as it may increase to a point where we're better off avoiding the suspend/resume altogether. Even the client->server traffic may cause problems as VJ compression would become difficult to implement. Maybe a way out would be to insist that only VJ-compressed (if VJ was negotiated) packets may cause a suspend/resume - but this may cause even more problems on a ppp implementation that doesn't update its VJ slots 'till *after* a packet has been received (rather than doing so as soon as it receives the new TCP/IP header). b) Treating interactive & non-interactive traffic as two completely separate streams would be quite clean. VJ and CCP would need to duplicate their slots/dictionaries - one interactive and one non-interactive set. c) This option is useless - it shows why we'd need to do either a) or b). Having said all that, I've talked myself into b) being a good method. The memory overhead isn't outrageous, the duplicated dictionaries will have no adverse effect AFAICT, and it will work for both uni and multi-link mode. I wonder if it would be necessary to allow interactive-fragment VJ and CCP options - ie, someone wants VJ and no CCP for interactive traffic, but CCP and no VJ for non-interactive traffic. This might improve interactive latency further. > --Kenjiro -- 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 Mon Oct 12 10:51:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03496 for freebsd-current-outgoing; Mon, 12 Oct 1998 10:51:37 -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 KAA03489 for ; Mon, 12 Oct 1998 10:51:33 -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 TAA23287 for ; Mon, 12 Oct 1998 19:56:26 +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 UAA17371 for ; Mon, 12 Oct 1998 20:10:37 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id UAA15765; Mon, 12 Oct 1998 20:03:15 +0200 (CEST) Message-ID: <19981012200315.57827@deepo.prosa.dk> Date: Mon, 12 Oct 1998 20:03:15 +0200 From: Philippe Regnauld To: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-19981009-BETA + 2840 AHA + camcontrol stop/start = panic References: <19981012194716.53997@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19981012194716.53997@deepo.prosa.dk>; from Philippe Regnauld on Mon, Oct 12, 1998 at 07:47:16PM +0200 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 Philippe Regnauld writes: > Conf: 486-100 16MB > SCSI: AHA-2840 (Vesa controller) > Seagate 1GB HAWK > > ... > interrupt mask: cam > trap #: 12 > panic: page fault > > syncing disks... 1 1 1 1 1 1 1 ... 1 1 giving up > Tried again. Had to fiddle a bit more with camcontrol: double fault! inst point: 0x8:0xf014a92f stck point: 0x10:0xf0277b28 fram point: 0x10:0xf0277b3c curr. proc: Idle int mask: bio double fault! eip = 0xf012406f esp = 0xf0276000 ebp = 0xf0276000 -- -[ 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 12 10:58:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05215 for freebsd-current-outgoing; Mon, 12 Oct 1998 10:58:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles238.castles.com [208.214.165.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05189 for ; Mon, 12 Oct 1998 10:58: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 LAA07056; Mon, 12 Oct 1998 11:03:02 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810121803.LAA07056@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: bright@hotjobs.com, zach@gaffaneys.com, current@FreeBSD.ORG Subject: Re: bitten 3 times already. In-reply-to: Your message of "Tue, 13 Oct 1998 02:14:03 +1000." <199810121614.CAA12373@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 11:03:01 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Also: > >wdc0 at 0x1f0-0x1f7 irq 14 flags 0x7fff7fff on isa You installed this while sysinstall was broken a while back. Start by changing the 'flags' value for wdc0 to 0x40004000 (just enable DMA). -- \\ 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 12 10:59:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05350 for freebsd-current-outgoing; Mon, 12 Oct 1998 10:59:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05309; Mon, 12 Oct 1998 10:59:16 -0700 (PDT) (envelope-from son@cezanne.prism.uvsq.fr) Received: from cezanne.prism.uvsq.fr (rtc102.reseau.uvsq.fr [193.51.24.18]) by soleil.uvsq.fr (8.9.1/jtpda-5.3.1) with ESMTP id TAA18906 ; Mon, 12 Oct 1998 19:58:46 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.9.1/8.8.5) id TAA00489; Mon, 12 Oct 1998 19:56:35 GMT Message-ID: <19981012195634.06516@breizh.prism.uvsq.fr> Date: Mon, 12 Oct 1998 19:56:35 +0000 From: Nicolas Souchu To: FreeBSD Hackers Cc: -current , Luigi Rizzo , Roger Hardiman , Mike Smith Subject: bktr over new I2C framework, ready Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=SLDf9lqlvOQaIe6s X-Mailer: Mutt 0.81e X-Operating-System: FreeBSD breizh 3.0-BETA FreeBSD 3.0-BETA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Hi there, bktr over the new I2C framework is now ready. Although, no man page is available :( This is my next priority. But it works. Ready to test it? -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org --SLDf9lqlvOQaIe6s Content-Type: application/x-tar-gz Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="i2c_distrib.tgz" H4sIAKBdIjYAA+w9+3PbNtL9Vf4rUOfSShZlk9RbbnJ1HKX1nGOnlpN2pu1oJIqKeKFElaT8 +BJ/f/vtLgASfMmS82hvrspMJBK7i8VisVgsFrBjWsOJE4S+Mz746jN9WENvN5vsK4YfPfUt HlirZeiNZqverDNmGPVW6yvW/FwMqZ9VEI58xr7yPS9cB3c9s233SzD0ZT+O0v8TZzoNPkMd hq63Go2C/jdM06y3Zf8327qB75qNxldM/wy8ZD7/4/1/spjYNz0W3AYHlreYHkwd1w52nnz8 Z+fieMCQWo8dzLy5fbCwroKDwLcOknVpVzu+DepnXzmLt8yHr8DxFszYN5rdHdRIVluxmk/P jHNXq9X4r5LR7XYO9O6BqTO91TPavUa3xDGr1Woaps2Meq+u95r1ne+/ZzWwMVqLVfGrzb7/ fodN7KuD5XK8Cg6ulp7j7VslbxkCLyOXwQu13JnP15dPh0vXWaoQ+LxTjUHc5XisluPzDgvm UDZ0pvteKS6ilyX8/LbDShN7aUOfLazb0m4Ebu1G5ZY3X0K7a9dOOCvt/uP92fnFy6PT4fGd BKG2NxvU9mZTM42o8USO/6+yRi9SEFCeAODFjmNR8x2Lg0QQ/A1vfww0TsOACKr0lRYBvRT8 VxMiiMAjEVTvF0G1tPBqzhz6xHLCmr9ybeZ61shVarfya2ep6v8xOHhn+4uD+eidDY3zlsF+ MGPwNt1SpDnfZVn2OHgOkZp1Dx1ogzf+N8s0ZWxPPd+ucTZ5w6RgXHu0KCWEpjR59uc3+T46 GzW5VNTa2e4O44Tz9KtgjMUI2w6ypm7iIGsaHWFglpZzMJpZQ/hO6Be8w+HjWNAC37my/Rw2 Ro7Vvrm5Gfr2232SUoLYLic+hknsXejbdqfRUYfWGF4ma9ipEnwIgENwARLs5EBz6mGG83GY BzhZZiHhmcH7PHDrNgNt3aYAlWlKVY/p0AHeP/90la2zeNrCf8mJC/8xyStOXuJ3NDXpdWbC vGT0mnpJUsAJLA2HU5jZMwCuRRpmGnVQrSr/Qg0rlYCplb9g/bPzZ69fDA7hFTpZdztsp0a/ hDr7dmCH5eXItxehxk5OjocvjgaX/cFl5RBGziaAGtM1dvb69BQwmKjGmS5rT4HpqTt6G7AP T9jJixfDi9dnZydnPyArd0X9+OV7cW0f1hP9V2dO3HPJfusyo9Nrtntmo4RY1Gd5PdboNXTR Y13eY13RYyCVAKyINWNlaz6psPdoXUaBzU7M48Hl0cVlDzquZPu+57MnslPQZY07JbBqTwNr OJpMfOq9jaGhC7HzSqWxb4/e8W6M6z5/1eMsm21imb64kuXAXwwuj48unudxm1QhPZfHFExC uRL1TezpaOWGvWJNIu/lSysTVbq9TZDcCtXijte9ViEBaOgHhsmMbk/v9kyuZNy5g/9FfzmL EJEmQ8sdBcEhzC4He4wbVgadELijK1vYW0YgbO+AJrlFEDJrBsujPUKf2IF1yJE5ML7wnWUI RAhjNSRoAkYF48D4ywai3pSFs6giQKjGnF2PnHBkveMI+MBgQmfwhoXO3PZWITI6sd3RLa8p Qhy50AzRJDSykvzUW4Hzg7B3qDgolpahdVi1ZQqxsD127M3n0EGgvpJJWF0wwnoEiuYsSLWH P/TP+hc4vR+dnpb0G32nppa+RHt4MTx6/vyiPxhA+WiUBDg5618mi6uy+NXxi1x8FjPw8uiX wenRmz4zwejzhrQbmmGwKn7VZVNcWMOjhN8tvOuFEIJsC6zuV1Yoh5oQkHiyZo4LLV/8+jsM xvcwet8zdHl2ydY/ez0YPr84eQPsHZ8eDQYa2/3BXtg+zNDHI9dFoJR42J0GvcNpgMdfSAZF Hnps8PIZG/vO5K29q2IqaP03J8f9CA3k1Wm2G0ygd9jYCQMGZgO4scGNO/AAtdUAUjkNySHV abBRwAeAaEyyN1hEqZjQwg6vPf8dA5W0/enIkpTUbkc61QdwlNWPmNJ2HBVQegQjRs9jbete rz4CX9WZUh+i5QYTjm5HNPq6BhqlrvRUYFIKHYuJcYyaOArBAszKXD2HIVp+AXTlORMJtfQB hWttBKqxHCSFMswek6FzNfIjDBajaAipsdXQ9cBo7+HslKVw7TuhvRkJ7g4JEgJiboczbzKM yPHnQIy5KAoaG9ao53D80oJdR7NVNfSmtF4xDlBMIkSFoBcv+5c/nj8vp0Sn8fKsTCtaEXYk RE2Wp6ULuLV83Fh8EhnfvkWlciylFChUN6WQ6Zli1i1gEYEWocRWq1dK15DwFgvbChUaCRJK KdLgXWa0tKYOfQa+XqeZ6LTA+T/bm5aTdjnwpqGF2DRkFCXkS3TqJ29sxwoIPyo71fcwenGS da9Ht2AK0ZFCvZ0ygp7weVasCsrkfN3tVOMZCKYXtAclnF1Sig/0hzSN/iqAfj9ETAWIOONs iWklwR0OCXIIyDXlrCKaBURD9AKpcHwb2kS4BEyXywjLvmFGhT15As4iQyRsoBPIwYFdPhq7 9j952wjt64SvS3WXeeUV6ekKUqUI0lsiIHdHIwkZ/BlkVLpjtgvObZYB1PgiBsauZ72jMZHH xTfYWI0Z8IuEUKnkVE79k+0yGOowvvbYUci+JZF/S76Rxq5tFDBogKv4VwG7njmwqoBCdAnY aIxOFMyZAEJk0IVk7BIQhBYzboCZD4CoGdcOEKSK2AhcKVEK6HPULvi+JTrgsjNywvZh7O6x nzdmhsPfx0BOtWqV0sGJxkpt3VjJn2l4Ia28ckYk2wssMNMC+K0d8tdCddIo0rnlw+eQFiyi FrKvh2IIcHXIGwi4UAdt++WXX1gw81buhP2xsv1bxtdG2NxaCddw4ObRUHmS47ZQLerCilSx cPFeWw9MSklzxLS8+wrkiqubqedHnQsuNCfweNLb1VRRrRYO0auIehCrzGUTr/2kC3oojE7t KXn2i9Hclq+qVT56QTBSI2+j6mkQEmUhEOOQ5Mu+k9aNP0siNF7zDFdytEYGQzadfff45im0 L15o3/HRGkH8ttilhnKLzDU34ZArvD5YCqwUi0GQ1djCC8WKTizeoqhCghqt7gQRvnLPOpC0 hC8yqglqkZQQocCuFss6hxSyRYSUAhzn1KdUyx2BiHhANdMMxWsVzUhXAqSU0XMoZ4TcCtNV RbEHLFiOFo5V3n0c9NhqwTuZpPs1aMhw+OL12fHlyfnZcMgjGDwAV6JOjq0JsBC7slq24zXw IuTrCglAIMIwpdV4WXhzCUws4NIXwk81Tur1tswQEn0SXOHb7di6o1BgDdqjTnI1epVjynPN dQ11WPXBYiiUePSJf6p1kX/WphWJqXc1o8MDJSoIxUyrqvu1WLnu0IKZbTyy3qUcHXKZMCIF Rh0VC9+PwpFwerLuV4auby/RDZ3Eg22tGyUpopnun51fDl6/ehU5CsqyaWfdugl9gHgVE02D XDgdrYtBv47WSccpcy1KKYoFFliUyIrCbPEYZgpuouH7cZCcM1DX0OfG5USsWtFsQiVZ48GB c7X9n2yX3Nhd1oO1sRfy2NAu18V8tvSbxzeFXFU356ogvJpnrXh02NQaIPWWoRndIpXMWRjk LU8zfZtQUrHcvRq5QqHy3Jg9Fk1S0J2X55xvadwRSWoEEuVmJbKR1ditBQXtn12u9W2FLF6e P3992i9zLjS2tKZaxBLNbprCIakeDxYjnXwStPn3sUTGoWNaGxNZG5me/RmR6dlDI9MzNTI9 2zQyHQMadYa7Vd2e0SYFrxsYxaij4eVGJc/hfk9zpbB5cqLOiyTDKmwZ2iL2HKk6YNgCnpPl b+Tijde48u04OLyuw2jz+U/oM6r3gd3GeY57jp437LwkLG5fGb1GtLNg8t0ruXl1cgaLjhdH x32BTHHrndojdoLhqCXwLkJZ/moJ1kp5r7wGDMYjLcJAhT45qKrt4jN2vUNxb/gSSSvUe4AP lEVXy+kZXu1UFaryvbBRKmWxC4E6QEsxZfpG60SWDlh8xAaYTnHRf9U/uuw/H9LmHKzgFhMH N63TzUjO5zkNinZLKNYr2RC7HYdx22hDhzyVliHErlTzKai3Oki93RUzPV+M7o1X00Ox0eLC qkT83MNFaiDpgdkL5W/anElRbhPlruR7C8r5nHZaOD0aui7sR0Le4HyuFcTStmn5rThTyuOe 5074K6yx0CJ4i+mX31ykSh9iCzi3whDQwyZWIAmIJqDda5g90+R9SroI/5spp5nHj9d4KUvP dfNinhhh4c7JzLtWwoS0RZx0NBCAhjD5UeT9/nx0csk+ULwCzNFFpafuLoeBa9vLMtIHgFcX Jx9eHR9dHv+o0XaHb/+xG21IRwu9AuJn5xuQX0831zf6+fz16fNnp+fH/0rCp1wlqlINBeKm XxS2+WNlB+EQfpcrWMAHS0MzmzhaWpqp864qDm/l90slE/VCP1eOWPB4pCD0KOoxdfwg1Ngo eEdTNDjatu/eosqCecDoBA/iMcEzRlW9dzwsMvH4wlQSFW4ybjA9Ozr+V1lhhgfDFH8cPthJ F/2fXvcHl0PA00AjuSmvfINqEy2IuSQJK5WEwBUUOlPC32Hc0rUV6UPTxauv+TseSwkwrLB0 Z87bWblyiGshqkpEGmwJVgKYmzJKsEbLlZRa46t1ik1hlm1Vm5CEUtWKq4jUe30l91OPlJyK 8tU8gcWjOhv0B4ZRZEiehCmly2MYcqPRMOu4z280dM1okN5Hw8S1oek0TO5ZAn+6oVLjQ0XO a3LMPGC8EPPqeNlynDA+QE77R4M+HyAiACy3XuKBkTE6KJCEiqMJUBWcfU19IIeDVHOeawyr WdwHw3wFYYiUORjJUgLKN+z/TwfPpHGJpFTj20K5OU3UeTx0WJH7R+sBaSOooiTKRW3EmlK4 tKzmuOCzaOitaAy318g4bAossqywXUqEVBhSEWwxNcMECXWb+F0ooQ/sLyYg2uZKNRnf5cmn CJbr5ekRWO2L/tFzKS3aBMEktNjFJmmyURit+1z7ynZFIlGOaFm2CXdc3t0WyRuz8LiFKOEA wuqHJ2+OLqI8NLkTgqVYQPsrGvtGhnaUKhI7BzKYyd9FgUwckTBahmIZmzBCFNGsfTqzowRX lXg3l8Fa7/aLByio0od6tzPVu90oQJEERO+2BVA9Q6TO0QIX/jf4jn2UxyW2w0r6jZl926eC Otp0tShSaig0hNuGe57RYpQWnfjqIImouDEcNVkYmXDiBsy3dAflmprBwFiEmVQ2mOBl2g6S xRH2ViT2IEsgdst2rnjOAHmQ5Op35MJQZQK4O7okBppIBr19WH3zIZ+oE2Ffnz3vX7w4Pf8Z wFsETuYMR/8tbSTOPd+mBXcW9/xNhNpG1NDz2HwFTpMET8hGhsIBuoPQ0svEqG+wWi49PxQp ESksyoHQb7qItPCiQNMoCJy3C0DhG+epNJvYD78awUxteRM74LlOpmbSQhW++UrVvgHERexo yK0N1/WshEPCzYoAVxOfMC6iZDxRxhFfufIpXKAoSUvr9hXkngLiFmBmdjpkpcKrJistxRgZ +URtaO6pryvsNzBIZWFKkzGUQn+FY1YylaylvRnJ6oZ8ayIOUaHTJw/hX5OhjJxaN6psyzpY pg4xIzI8URITPX9VQDNH4DwtgPjEIEq6Mwf9NfwRQpZk7C2hN4DOAPlVCco/X5xc9gsppzyy PK6Fw1FcA9rmzSvIKk1CLBq5TyKMlFaYe2UkvS+Jn60uX2T5SrON6NZpaK4MNQz7aRTvSzdz Y3FqFDvUeNQQ1TayeYoZ4rlUvN1pwyWNnzBKFEFEk1RERWZkbUQkIhMntEv/DTtHNda1Qsg8 T48TF5myhW4YHZ780m4YVfoQN4xzK9wwfu5zAzdMAcQTDAYGGeudnmnIfYYW7TOIyFU002by xtF7IqeqfzOaL6Gl0QtKtJyP2TgMr6IXjP3GDuInfrQ1LjxgqND8kTPJ9/4UkA/Rb7HnIR8B 90OETtuOuH/J9vf3JYhA5Ud9hQfxyFlY7mpis++wSzCTfb4/e8ojrXR8sNNKZkxLnwB42yAZ Ohct4UrEW8PkNMohAcM1mwqNyFsmQGQSspHGHysnQ0Ddr4ijwbnoYEAm47XoUT5dPgFwdK82 ILAnKJBL16YD04Y8PVKK84MVB02jZCIpY0oFZuTwop4lvceqQoGf45aS1UopUSOdDDTJMK6P HnMBSVoxID3mApJUYkB6BEB+BqxOA7Le1eo8QHGn6JYM8j9APXi0P4IVSY6JdEsxi8hkoyj2 wcPO/AWoSmFGAoU7wWCoq6qeyOmV6wMl7CY2EnlmL9CFavbKfGYQW4I5h9fi+HsidBDFndOb C5ydaB0Xs8ODfEXsZOqNA5pKvWv3HSSJ/snZm6PTe/YZ1F2c7cfuTnI77t6+JUWr67THa2JI zEhnHok4OYuF+BN5OhuckVRCjJscklTAC09JUv3o82xaPcXvNq6doPMqj7qTBNakqCrMla0o urq5yJVQIvfLcsN894hyW0mK2HG8gZKVHvf5JA0laz6Kvm6FEVecCBRy6Ao/mUzCbBs8w8Co y72DhwoT/c2NhRkrxpZ6IYK/QpS5Z2/B7ZX4sVCiIG2yI/JMTCF+QeC2WiBjbmhyY7I8Cm52 mlz43AT8t2oyvUgH2VPaac0nijpXqOMeMAS2rkoE93O22j7J8KnrPK5exx0fU0n5cGkaLVPA qXzt+RMQo34znRIuQeC2Ugyiwuh6hT19yjr5OxB/4Q7F6xDuxwTR5GAyth4LxfUJteEBrKrI 23G7sTaZTcyCrdbbepTA8BH2QDXJxftguZrEe+WtBwtPmZOyJYlYWnm7anm07lOwfA426G6W bElR/amIaN58VcjF/bjb8lI8ia1hYpuZK48Z/quX2l1U9LRwKkMDaKIhhFWjWY8vYchTR3H2 azX91fz9b+38r9dOjHKaWyqnirOpbiq5I2LbjpF9Dmf2gs+mqPM8NXqPptMn7NnrF+bgx/OL yzKqm/47Vf2r8XvlI7W9DVoOhrphNrS6/re2f4S2q90a8NvbCvqU92DsMgW0H6q4VbxrFZ9K hUg5VfezH+noNm1OIP09wD/jAPepbz/bCG/gGbk6jPBmW1458/FLs+0H/gNH+obd/GfPaTlj B+OOFTok/pCRl8Eu1rV8ucbaAVikB3U6mFZttLvyCMbfLvnfTk9W27Y1jhnk+LDxZ3TVUxuw 0eW2X/KUR6rSrTdgY3ZxBzZ6Sm/Bmr1mI7EFm4WMD3oYDz3owfeR1HMeYgvq4455YKBdpKrj z7XnMAAgkQsPDKw/5pEifs8xD05+Pd1PfsxDbs9td8ojJXolhTRR8uee8QB5bnHEI7WLt80R D1U1/wonPPJ1uujwxVqtLjrhUaTZ6yu5n/qnOOGR2x1bHPBoiwMe3BmVA2T78x0fOUgKT3dU P9npjs1GSHpHeYvDHWybwx1rp8wvlDqeqvTBU+YsMWVmkscLp8xZnLak45SpG71GR/jHtBeL X8mUaTnEefr4ZongKWOXTARPdXcqEZzSo2Q+djoNHFHxRoaLC7rLNPkeaPGCVF1KYrWZKQG9 FOnvcsb60btmP2GiALO8+RyvDwPNtm9sawU+aKESfbmLexNVPkSBolt75V9L2EB5knf2kuqY 9Z7RkHf2tunO3u4WN7pyGyUvNuBJRMn7XMUFn3SxKr+PVU9f57nJ5Z145Nps8Yx2EeJTU0OE Nc+5co0ph1oS3O7BE9n0WuaGtJq8KIyDRLNFfEMWL6g9xW9xQxZ/xW/Iqt1/1VKGAr9qib+u rLtqKYEp7jSq0XVG1QwKVbU7uA1Ce85ejhajt/Yc18jPVsFuYlkS3e6SI9ai2+pqxXNYZraS jdom0Wptr1UzvZa8zbG0GgYzzw/FMXtcRt5zgxxOg8Ju9cQ9asX3O1Xjm2vvIUvsP54gycKb 6cRkza9UK7qv7aHKiMQ/UhmrWykjLSnkeL7nHix5IK7Z1OowuluGOA9Hqpi8C4earYksME2q hbgKJ1KStdfpCBLiNp2NKBRPFV/wYpZ0rQ+bMOJbWeLHzaaNJCjeqdPpNRr33ski/m7Px13J wvOG19zJQnmx8L84MBclfCRSO1KHVqNbVaB+nhr7qe9tia4NURTIqXda/A9PnYKQPr/qJOsr VJpGp5VQGXhmxCCqCv5QfQa85L/ZM8wSx0MVSYLQnwKoN3oNfluH0eg0KXEZv0VODhdjqXTj 6vHDdDlSnuagJp6vUyexZ/Kvysi/GTAbBWxs2wsmztOJw3EL+5ry86c+mDC8gHyfXc5gwCON W2/1resCiI03yTJc7cgDGuKOLrpklntJlLbvLdxbggcMMPVAAOlcjxZ0iy2INfQ9l3lQsU+1 UigTD+HRVcwxV/x8Bh5x5CVgy70pKR50GOiXPwn26YIf2Xb88zd6fOeM0TSbtNxs1g15EBIZ hPkROAZ05ng0YB6xQXTCMMr0Dno49sRRgpzDC8VlDP+2EN1zKlKAI5qI9Z/2nrQ7jSTJ/gq/ Im1NW2CBBOi05KMRwjavJaEF3G6/2X4MAiTVGgHLYcnT7vntG1dmZdYBSJbdO9PUm2mjqjwj IiMjI+PAQSbsdD/UACy3zg1Gx/XL4sgEWD2AFAE4p6W67S0OlbC9bY7SMyYCH4bti8QZbD3e cKx0uPpKvZilJWx6iR8gSiOBATIXqCIe93Ugp/OEDgmMlc69Sfa81b/EdYM+liolZHH+mXwp MtRZOjhVBhvQcODdOSFXBBqvnUu0NCW+8l8H3jO0dtgHYHtX89oVSuuWONP5B0KB96nI0EuI wJ0dTkfDAUYA3KiqFIjh3Y/qDAD9OM0Fx4mzKao/hoipLjq+q4Z3jfOu2MjHSRs0DC4uvLaH GZb0KBB1IcC5FDELxcN2QqPUbdIvuK40Ae0KSJ7l/CR6tIoQMARCSnf3yvow9GLej+33a/o9 TtapYCMZagmixq1XqgP/Pe91ebSv1GQCa2f0v2pXfeJ1D4VxJ3M1/8SloeIG0Pb3OH66/cWL Eq4YoXh0uCXQL0dwyKMKooB7AgsNVgk5acKu8Ww/x/LCFsXg29JBuXwHpE7YLf+l9d3KhIaJ 1Hx/y0blpFx910g8w4f0tBK/2tZm2IUCZUhtoOrsQk4JPeDUW88DNC7hCAxLIYU3QrQhpB1N Rv/wEFUYeWoMhvZZ3eDlOFqbgqC8wSHBgEmgt+sG+dGKY/sOXWOv7ewG3fwp00qzUSue1k8q DRCkSBMS+Fwrl8oo1iZEm+Nkczkqvy6+O+bEH5LsxRzXAS9WiEOWiPDdeWusU9gAYTD50sFD /CqwjB8E0fcisvLWMByzpkmJLO6/sLwRuRk85diVTUnaSJvXwGgPxCmFrA8oVdBk1OqPr72J RF1c8yvhtWK3c+Dn4eHIdIHgHYxtX5BjkuJauFm3ByMY0BArOb4vKM6xHmKTI6XkjDRjeXcR nGZnEcEiC3jNZQOtzveiD9aId7e/W9N0YxZRbXbpIFR0UG7jtRr4HvSxjXSLDQPFcaldrM4Y IA9SyiKQmT+oOODMHZn/O6p23BiD/2pn4ZhkL9hWINOLlTvLC6V4yZPTa76QD7sYsnrNkG0m EaBj39MwKCwGXQ2FiTu+hvjCCfkQcA+MtCHIRFBvdD0unkgYso0rNhiaUoOheB7mdzhT7c6u nzBPtg7MM4FMA71sBagi82MuZ7wGUsAEvR4xVVKH38J+ItwOKrE6J6SS0ZUz6jEUekzzzL7E YaHOyL9Y0VyMI9vDWUDzHm7adieQN0G7BZrf3g5uQmv5Z8bKnXHr6FJNA9bVlb+bPEUI+DdX 1ofwvZUZHPNunJKrBSTFmDUFk41iMvqsOgMoOgFpCrV+Q9xeibxolyAppqtwMzMby8VocE3g 96BVEFK9f7YoWOpaAp204T92nospXoBRJBU6+qAwh+7VCe7DYIE6eEEggaP+33G8v/lfeMhB dRnPx8qxReKxc2jheOA0E5wX7UYwR9O5zxZ0Y04+jeDe76TXoLHLyjRWMH7sFwsn82BtPL6s JskUylzDkl+nTZ93BYIK66VJzZQjn7g1jFEuW2/EfvstKDV7F0q9Gx1mkQ6zC9FhNsG5Vxam w7WF0a60I56D1LUopDL3i8rKY0tLs1iT6UDf7RQKOVQCYH7PvHO1w/kD4iSmmJv1ta9DOg8M p3mPwPzZGXH5z6OjcqQd9XqgGlmlGXyHgr75S+NZnpbGZi6X2WIQzqJ+iqVfr75ulELUi6sc Nz9LbkYsd/t0rq00mASR19TLjWY9n6II+WeV0y/leu5L+bTyBc46X4piZLQhPJYCVwdi6eHh kq5c3DDW6qZFScQ+eYPpuPeZpPZ1aQUb8MYsyJN2btCHLRejRqC833LsRtNYEsUJ1PddTFAn hG20+o4NYHp9fR3a6/pCW3rfbOmo5Bnjjk6G8PgWW+Z2ON83vcQ4MizhQY/YxrrZMnBNGfTJ CcVPKLYIrKHkYsAm65ZgXzpCgev4Kjx1bfFjhtKc2/azT4fk1v4A4y5EUh2LvTrOD69TfENV tCzwEc2BuMhGPie2bGKvRQXhO0LjjYFGWj1Rx7VD3/2QirHhlTFwA0nvuPghlYd5W+d+yvEK /EbHNjCGWB+zWbmS0wDjRsMhCe4MsgAU1u68SIPBJ8T/JU9a1M0tnSvFNXqlowzMtolXowS1 aDNbAEz7qgtQBoridY7NRALcJMPiCjpVrk30Qg2EexPfie2q9MB06LvSzweh8RgfzB1K2GBC z0cb0s4+/C5IvndH4N25bBCBNMetPHst7+4Yp3+KPYqMkfgcbalxfADKWTwgggXkzbbt5zUW sYRtwNEKDtUdrIX5/qQjlR6YdLZ2dshXYBvkRu0Dae2bEcwveOwOkQDFkpt/XI+s5yRR8g/w Otza3WkplKHEiHGmTeB9ugNGpi9IGJow8qqtjyNxFYU5E+FWrPD9pH8xIo0t4EkGTRSL/Hqo kjSBH8wwnbEJm7dPM+RL3xt3o8rK5BPRa8QwfSN5d1G3K4rAgB6yvlp9/jIXEHJy3JaewsuX itNkBgu445JiOv5St0cHKQwF5+uVZ6zrvMSj2c5xQNhtfb8RNNLJhjVVhv5MJC3mWxT8jtRP 5DGSXLtvVYcNou6cNtF780NKvJEJssXtAhszbu9s6fMeLvUg1HGMa2taArKZHApn5KIGvAFO KyTFcWrChXhciMnN42k+U0NplPDsh7MVAWU2d4tjbwH+Jgxue2uXYwXnZNuPJA1HFTkfveQ4 w5Rxj5ryDiMrGv8ZT+dm+WaEsr2HcNjJFRwNHbC1S6aBKUnxl6JUIZNojt5L1OH1VT3n730w ISvuBvyFTCyf1gjUL9STJzRPJhXo7n+maC3Z90mO7oyY3kJrHPbtNF86YKxflpxYltve2SND x518Af0qaNeiaYvAp30DZJia6FGiZSDL1fRVlxNMrYVWBYDlku6utfPm/OUg1DnUinwLLRG0 mQ0BTzJq8bXPRw69aWGg1eNIzAYTsbBeW6wNTEfKl1PtiffJm3yminBsgyNWv3s78U8RuVRa 4yhidjRmpHX74EF8R0JA4V25NdJCaKTUmwNyUun4WF+Low7u3bgj6JSouicO2bNQF1Qwuo+s xgoRqwvSDK8gpBnqwoe1tMmcNwo0Wc5Ma13e2S1Sa7qhtVntEMPHGWezRFu8ENbWHLO8Ydvb OB+RlQewrMvv4QQQ6jL2Fr1QcK7RCwXlDhXv05035l59M0f36jtskAft4MV6RFGxudqjJGmb fKDYoYsc/Ec2TsXxDwGX183bCQgj2kANrVg73QtMGAvtHtaPmk2Ub4kxo1FL0yu0zZXxWuje 1H5Flj1iWqetP5Nq8nnYxQ7sNts9b+j/aqI79sZTSbCWo5Hv7WgzdIyRKnkHxi28MOFRdQ6Q uCr1or54wUVsF+5PRleoTeHiVwfm4prC07M9hj7z6OtzQGvbo63OQ0NQtuczk4kEldVlAFz0 q039nk/2tvbwkz1Y20CWCwwnaD4od/FQ7RDf+sLi8Orz2Gu3es6lOT6frpuDiwvUsk+okFzn L9ZCaCH5BlPfwxgl3GfsUtp2rRS3d1RgsLyW7FdmheTyaLi4ub2/tZeglngxRZZlC0YonstL LB3y9sJ/xETNtlm5brWvgHY2vEF70muy2aJrthIoQriGEogfNA3s4/RIQHGbYOMVJzgvmia6 TYcY0Uu7Dn3VtBf41gn7MYW+h2xx/O+PjV3w1WP7tWui4w4f/g8TpBlYJ2geIJ6fYQfI5g8i Pk6m7IKHX/miOq+D4W4akQ97C69P4xBEguBgwKcWub8YgegNiFlnnxZuefMZGSTmt3YkxR+v U5RdrYbl+Ij7p9OD3IZENby7yUOmvMYk1l1M+yRveU2EL4vbk9ZlBo7IWxx003zjQ5r5mFFY 94scMM2lHeXQsJnNEMbepZQ1dPmS1gPztS2mtL6g4Stm5GXZl8hHMBYf/cH8jAMW6KsR/PJj Z1/59fdhEP1V3SP5PGCLvJcLgg5r1erPjVq53KzU/os4Hakb2Pymf+FdTkd0OUZcg6WzQa/T REu6SHCdlSpNMjqvvTtDL/03cnTeyu+IpRlshNuMTRSF1GEDJ31UbBSbpcZxEwTFeulYfUn8 d/z3o2JadkvFm0UnZZFDWlzf0KWuAdMIm8Hi3QAIo1PA0GeysRW3tLH43DmBjAvt94Rv3lJk W4CffLpi/ZE+DuX9nwUlTu10RGtfd3znS0FhB0VHH/w4y8qR+vIFLyxwG4op9QxKEd6hTTyc FkrNUvXkpHh6ZKtlQh+be7t71hBohI9wFctxmVw8r02IipuUTWjr4qvBs8WgFSQqp8ipJ51K SXsSb0g9f6720rAi6HVev9axJrXOOJsXn2sRqsODOF9oEBzQKNBVZE/atUfeV0XRyX+mVE5F XCsQBdSQvOMJwEE17OXT3uTg/yvmtXN0qzMPuhh6A6fihkXJajZnUl3htaiU1OBbIZSSdVN4 efJBWDNqnytvFbbIOWFrM1fIOEEmUsIaeax49GnC3sUhqwTlykSg8LeIR9x7VOc26yBYoYbj fbFWbp7VqodllRbvVXbj3aHYF1tbhZz25HVpRjoWwbV4WC+fNoAws/m0S0m00R2R1JkKEZOl kLbCYXBIHIR2C9Hq0KLkctP6Wy7yQvoHclL6Tc7BYC5woZYPBphA3UxLYaqjFmXGlvzaKBXQ d2oWd7d8YU8NB+Oxh1ekuMnxF5Znu6K4RpNcqD+aEp40RElJtLW1+Uw2dsVd48b5uvLrSXmf 7C5YkgYUkwGrao0uxeU1Gwls110Sxl/Ci4DodctN828JNcMYeIo1FWnFeKwkI8BY/Qu9BJT4 u7pVv+l7P8VOgfAKX8A/z7nNAzge3ypLgxVEYKoAk75NqzWVh2KPDPIsphwkGqgkNpJcGetq JamMa0Ptwdi+vADcIi9O3aofcaVoXYCi+AsBGua5PoNDKiEGEKRPq5zPItW9VL94ne7geHAJ IC61hhPvUwvt6GHHx5PBuiq8ZmUH7djFtHFONgIk6WObACqSccSpMoQflQZw8Rn5NqMm3eth k1eBvCT5ptdr5vg2LfC2dT5mV1a8aJNWDvBoFsIQUK+NH7+n8Dpz0IRQ5BC5fo1HuMjYodIe Xo6GpyJKM57T4WHn9HJeFO/WyibWrBQp/bjPlBlNGhlCyu0undZbIQ+UuLa8YfCFPZI1U8Tw jntIKXt7eglTjwHI5W7bu2l7wrrD2/YODVb+htOEYgUsny8uYPmwwpZms4KxMi6kkSQ5sAqz QqO40TWyAs2j4CgJstwGmqz3ZKybm8xunm0bdoOiMV5EAJvpsFkJ3Qm18H6w7V0YA16MSnYJ rfbwiM6ckKq3ppMBG+RpUxFLpUCEPl5fhFeJWRUiewa3+tQdnaOnkM+Wtrbo1LW1nTNHGLoG QujxEULUCnKO8z1+W/3P9vqDAjPWpTLbC57XZBhG//4o0BaLXfaBZF8rfwUyhNdHxqObVCIv rBMOc1PZ7S+H3qAJh6QmqlmRRn9YPt/2IVx648nIO7eVFQ/aRz6X29naUj8QMeYC/ypV2C1s K7Wzk89tbW+DKKhUfrOwlf9B5R50FDHPFC01lPoBzb5nlbu56nZ732NA3/fZeJpNAnMrDYaf R97l1USl2mmFujh16rUHvdZY1QfT9tUUCxUxRygWGpOR9OhTtwMc7yl+qnWFiKaGO5IZbV+N B9NRm41Vz71+a0QZP6/h3EGSA2zR+C8seWwFODgyYlI/gKw7Ik9IcjfqIMP85OHV2uSqJTeJ g15vcMNeoWLBN8ZWsN51d7KPv/PrgaERS5cxkTPpNV4cwp7U8jgGRet88Ak/CTySLA31BxPa GiZX3thEZvG7pem5Y4JO272Wd90dIYxUITwQ6NCCiB4IzLMzbXe/0VgUz1Ja6gzaUwxI0tJI 20DvaHKpvm7BLuu1emMf8IQwbNiehiaAxttKXekzlYLfcKz6pXJUPlKHH+BjWRXfNd5WawqO p6pUPW3UKofvGtVaXf3jH8U6lF9dxU9EZacfVPnXs1q5XldQoXJydlyBZqDdWvG0USnXM6py Wjp+d1Q5fZNR0Io6rTbUceWk0oBijWoGu8OGwjVV9bU6KddKb+HP4mHluNL4QAN6XWmcYnev cYDqrFhrVErvjos1dfaudlatU2s4raNKvXRcrJyUj9YVDAI6VuVfUHqvvy0eH9vThP85s4QT 5nGleHhMTVE3MMujSq1cauB0/F8lgBkM7jij6mflUgV/lH8tw0yKtQ8ZabaOUaFgQsVjbO2o eFJ8A3NLzYEKIKT0rlY+wfECHOrvDuuNSuNdo6zeVKtHdWwKmq+Xa79USuX6gTqu1glg7+rl jEJtHHUPrQC04DP8PnxXrxDcjPqvUj1NY0Nvq+8BMDDYItQ+IhhXT2nOAKNq7QO2i/AgFGTU +7dleF9DkBLUigiLOkCv1MDWrJLQK8CzYU1WnZbfHFfelE9LZfxaxYbeV+rlNGCsUscCFe75 ffEDzfEdTR9xBWPjnxbpZgijqvJaFY9+qeDgpTDQQb0iNFN9jS3V35XeCvRlFST+Vun8jX9u JFe8CxJhm6zPRJ3D26SWDJ2XSStpZUgjTI5q1g1VJubCC33RknKrdQf+H73/tx90j5m9/xc2 4cQd2v+3d5f7//d4lvv/cv9f7v/L/X+5/z/0/p/coIVBYW842IpvFosR0LRbp15Br8no2zGK UM8vxtfDny7g74tWr7c+GF2+5LZj0ga7rz+CUNHthd/D/ycRxYH7Tnvd8Huxe3BfapuEYNGI l1NvENEZ+UHi+2TYVIPstAPf0JoC/v+pNXIbk/difjHfMuQhDENmWoAEv9oWIMk5Fh5xnwUF yTkGJEnXEuRcDEGizUas1zBOtxzKllLmQqVOD39u1NRLENmePFGnqP1/iTdMRphFKZacvBJb Of/tYYPfH757k7pNi7kDqw7Pp5dpBS+Tjq2J+caqv6SWcye2EVwyEbLWgnce53ZGVwgKQmKi kNywY4XrH8uxmq/PZxaH71I8GTKyCxvi/WGPly4sYawRQ4VygWLnE3IfJhj/Rq0EQOKGAkgf hEuEY57YIU90K3OCnoSbRYCG0jlL5Awdbe9pZGdYEzhbD8hgHKzJMTciO7vsEiyw2sz5Ylny 0l8sQke4gchE1fEzcyuKoYLt+RyZPZxu1O1E5PGt3SzYGodUxWxecc3xNf8dxqZznOvmOhKB s+mvSH7hFHHinHA5N9JJXKATK+yH7aOeSSQsYk9nIsoxkWcSNslDwaTEfortJhQ6JbQedCsc hjCuHWaoftyU8Bpxh83l9Sqwy+t3UeWtJWBXsV5H1aLFYGBolgcWTcakn5+RfT68Rtw+bXsd 06m/MmIL34QL30QVJhp2ytIbns3vFBlW/SEclwmSwlL6FMtRKokMH9Orx5lkwqFS7JVD0zY+ nJWbJyDXw6ux98/u4CIV3nega+yOBToMms1nL5ANhrAyWKSzw02I/QRdpzmRabC+IAkEQMoB wDeJvnMct941wTlaIyBSvHWcjrok+6GtQ5SWSIntYGDPidUXiUVh8nd7O9MkYu9x594Eowge 0N7rx7pYlwAYeg8OROXB8fsUFx2YB+QOIkx23P+s92apMzs2jyBWOUF5aBQ4Ajv0oY4lScf9 QR/d0Uj+dteDzDKqV1MwI3LVYw7QbHcaHZLDr3jT5eCn3gQOZu+TFMQgGNcSjRR74wG31bEa Yx+22Kgeppv0QXwhmZ8eL8Yc1XfYpv6YdCetTy2vR0EQ/PMK3trieYUGLpFU44EMIDaRHhip 2jIBc0rER0TRY0ynk4n42TrN6Pn4Np84Icvak2LJIj/wD14u4p2xMafUQb79kfkgXmhsVJ2G ZttT+DzkdICGB0D0PUY20QdGHmf9CrMMCVc19vqiDpL3Vy1Sc1EEXiBSHWGDpdZpG9A4vpj2 aHVx6+vENyxTqSjBkiO4+MwgEMSeSeAtQHmjDvyDlrcbNygw12S4w8hI9tBjhKDv5mJxvoSD xrC7mOFA0WF8hNdgGFD+JVsBESsBLckuaucDNCm57l4PRsyREKGa1zH/C4aLwQEwP4wHA5l9 xMviUeF0ADTBKDhxsW9CcZHIAdwfTTRCIuVgFho9HVvbkohx7g+IsGAwBvr7CiOHEyonmDqq S6wUfQb4dKb9DK9Alt3A/6C1u3+6IxQiQukw0oGiqEmg14hIScZE80IbME6UFEi0sp8UUxdh MnxKpOLiUsdZrQJnykTiirLcP01x7EOOQ245FZvAN34aL5+NZRjqnAdJfA0l/xT+mXDGwrZu aNhnwqw4UzFpYfRUYmfCWYdCMwkN2U+sFBjyYqPNhUZrckj5nXGQKyj5h7WGdJiRKOqNPJ/+ e1Ivh+q/D/Giq3oc8RoVRzTx8l63EO2GM9CZXW4RyjUDiadcnkck5UZOw6dcexrB8bp06493 saF+O7J1tRfuMX1GtBJlQov8nnRDjTiRRnIHTnxlf1g6rsHRUS1ub4pU3fiLqj0Z9fjXQy8n 59yCNfi8gfIa4LOtjQXlXcAxALNcw8jQ9jmPfihCwBx5yqgn5+6HcUqoB5ZUFp+rRlzUnNEN Ih9DY+ywFuoGKak3wAtBjTz+O5G4FbbVhhUzIktVHYubzkbSPUgt+AnnK/YLp41mDeMHfVH+ C4D3UfW0TNC2lcBalrn5sUcx/HAMWm6jAfOdp5yh8XBCClJ7AC7OGctJJ75Ce3A97HXpPhMr Wjbgt7sX/Byo2wOVzZIZOB2FWhfdyWf1qdX7xCcCNtwPTvpJeIqK+IZwB2IAUYGVuLlHt2iP /Sg1q1kEZVoxm4uC3I/tH/HIm3p0m361ura6v5pdzeAIUgs0a2qkiflpyvJTuKVpCpH9rj02 iHI8qVyHgjgJ854K0wdcbxbVExfnZOmplM4HbZzYClvkxUa+Zfb7/A6+J8+uwKKUpaYXrU/W f+izHvupnXeBMuGAjcHpqfXBBSlydYmCKeHndveLRJzevkZ5/K1Aa5L/ZCTrTzLRI8FCXPaw cw1WKE0zNR/tr7lcmp29FkMXdhLEFtB4KkU9BJ0Uw/6l7zcP741edDg9nOzt7hHHwl/PFDrK d0fdjs5rNgEOMaHMb4BSuvrV7qexqL2nIv/bbFIJ2aTc7SJqw/oGW0jMfh9HDYLFKDY2go1n 4zG51eA00I01vpG0vzf9JfaW0XfYXJIJolJrzUch1/byxHrRo71de5wRoo9SPrmZ50T6QfVx xrklyARuuUziubtbUv57Prb9p7EZuH7YPub4f2wWtneM/edugew/N3e3lvaf3+NZSa4sYPy5 Em37iZUfwPJz5SEMP1d8u8+VBzD7XPl6q8+VhzH6/OqRaJvPlQcz+US8P5DB58oD2XuuPKS5 58qDWXuuPKSx58qD2XquPJCp58pDWnquPKCh58pD2XmuuGaeQPls5LmSTPqZVmnjTNKyED26 yWe6kozOZhpIZmrnMg2kMsVbQ2y53p0YowBSz/ltk8JYa+1iGkf9mPx0230T0a4zaksjFm5b t1KjrCnmmtRtgVOqhMdlqzz9PzmgcCIQopm6+rN3y/+8JyT/PbDvDz6z5b/8TgE+uvIfugQv 5b/v8Sz9f5b+P0v/n6X/z9L/5xv5/7yZkcla1k75toWKxX1pRExZ4JfaUOq/lSxWNk8eti/k b/UFPvJv1sRipmTbl+jY609vqV9tnOeLZ1DGMPo33VFH/dwfjEbq+cdR67bb+6k9Xp9Ms+fd EQh9653uS73Iq0fVfc5Pe4ZReFbHpumQMePzzpTuyn+66rTW24Prv6zj0ndw9DE+PdH+P9rl REzSxZOGjwLT6+vPB7YxtbjSQMFZjidcYrbjiW7lDo4nrpF9jGtG1Ehmp8ONKO7mww0VWDz3 bKjq3ZLPRlS/s2NL0CGDG/pahwyLCGY6ZNikcC+HjBCd2A4ZMxqKTGUb57QQyEVrUU1kuWCu 23nlJXmtT12RpYiqTDH6K6b3VscUo5Qg0aXY68OiG4LcTBcJLuy4SIhJezLh0M0iLhIWQxEX ibAXkXQY8iKK4zNz7JDt7czec3hGc+yQo9mW6XGG4W48L4sx3DXWgb4mwygytCEFJ35yHAWC Od3tlDSHaNtZLzdS1KOTfRYQ/kTbgh3wpaBU9JPZoNEX3f6FMmtetzA+fRZzncXm1kxEJ8kk eJuAvmKbB/Q/co156OZz9hRk+JZXxX1SgMYM0zRvXSv69nqEbduZFUeI5EbWbnTjD5KWjB++ HaPUm7L6ATEGTlF0cZ4REzm2sHJafcOtpskOD1qCv1GsxtZiGkunXep1HWRd91t2s9URGW0n 24hNeRBl3GbPPJdB0zLnVT78SkqFTeqsrv7ZHQ3m9ZUL9xV6JaWsvli+ft+CY2//Ul+Kn1bf H5ePjESu3l+hlwSncobj8nkXy+qAtR3UP1y1xn6qKLI18SZw1u1h3vDxFDUXdPzzm1bDKZD7 Olp+jPw8pCdIyDV9ivfNUxHFpFclmZuUpBO08iXTFMrvltYn9r5TsXRcLf1MNdfZZeQGa1L7 To6t+nHxlzL5ok3Fdcx0iaY4VLmovWHEIIVyMpH6YDD4iEqEjzDPUC7Y8QB1DVcIsavWcNjt i99Ju8WhelnL0GpPfJ1MpbQ65r/QvBmrGz8VgThqZzoDaBPbkuYdZPlzQszgpEjp443NlGx4 E6ImrY8WzLAlU9SA1m+WqtiQrh8VVYqXuQb3RsSuEWllbpJRCs+XjKqRCVXx0LbgMkty5lU/ 8arNQA60kbekW7XsRJxkq26qVTGSDiRajR1P0PJQPc5Qd69Ws6v7q2urrtWFztEayQIw9Rul s4o0ZzK2qATqaCjR0id7G+/F7oHyXr7IwX9hAmjlhQ08SeWfP/fSafXK5XBptR/gQ9Hzu/kx V4BdhUKbaxOvCL4mQ/YFs4hpeZKCzZ5TYtrH6NRAyGbKL2YRRNRUoSQSRARLJmKwCYRIglgZ hYRGyBwEqkpHfyQTlHbqnmAbIdiINgzkMtieTSSaRuTWaZHzXqwTh6EVy6IddtJS8fj4EDh0 7J4szVjGe3POXQub5NsW+e6gWNCJG5G0yY3pRmKGFsiMG2ELGMWJRPqMQttzsee9+44fuzGz UynmeLRlvvD6z0j6X20sGExgTLTsMFw3TWN0kkY3DZ4l2pEsn6T3+0nreKZJeqbDRpSy4Csk mHwcc3352F4nsceWQKrQjp8OUsUlCk1KAsggbYQzOSbtNIeBLIcJg1udNi4RhVkdrdykBE0m olE8H8cxSHaxzK45Jiedn6oO8a9R/lSirFO5BRHuZt6cA2c6q2s4U+pNdo/BbJAuvBcAsuW+ 6vXH3ZFO3anTSVrZ+tiCMrwTZezEj69UHjg5r89YUCWeSgz8IIwiTSmpx4z2J7HVCZnAWd/Y UkY2gNrqBev/2Xek/8mPff+PKPkG1/9z7/93Ny37T/ydL+zklvE/v8uz6P1/Rp20Rm11OJiC KLM0BlgaAyyNAZbGAEtjgHsEAz30JtlDubWgwDR4Cd7rdXt0sf5XviUfDvGaG/4bvub+ylt0 9zrcv1oUH7gNfUOOEpAValLewogk3w0XMIav1slBPmCgrlS4sWAYQvo0636dCsy+Xpc27nC7 TjXuGtGRZ7FoMEcqPT+OIxW73023vlfUmJgTnJCKfe1VuI+umTfhFtLudREexOj9AhM6WJ4d k9DB7dxwhEHczopE6CN4/pU0Y9K+kcY3eCFtI2+R+2h/xTkR+07wegCkvHG39wlOwJjSGqOb gWzbUsRzZCy23j+09BNPGT1DvXDtEhSnAH45VJ7QhDM0SznMUJ6yIspc5p0Ufz0+OzxM7Pkh PPAS5RpkcHXeBeF39Cg8SpvT4G8KUiUt/eYsvD5+Fo2P5AP+uVw7LR8noybOOKEWffSgrOiC IqMC88woRiHigPysUQUGnwXllIbRbzVtEldgQjgeDu2ClmN0BMMMBuWwgUDuzgYSwRthrAhg ia7YGU8sV2mHh1vtRAYeQ9mct5R19QHnKMQlvGZMntKab2WAN8g943mXQv/Ay+xLVhKrG7yy 4upShKQDzlyHYne/exMKD8mO1jiK1LidUTQX+CduifA1U6SVhRFJglaLhgk9dgMfdgZAu+ef ZcgmnGXLOEvHx4aL2urm4vYu+AlFssyYsM0JEzAy1o5xTmxIhldcVEgdDFPEDcEdRgs36vHZ kRAtFM2L6GjpDs/psG0buzyaHUDSD6UYwBMz0N7QZX3pmZwSRN5FWGUsenEY8UhWLFqmZnD+ BD8nzQaclTLqpHlafV+sNLRlzKNx2zWEwcqUOZ04LTUvCQvdHLqocD6nCzFaXjPXlWE+xHF/ ozAJjCha65oz6BTxesWMW3yOTpjIg5pfrHsd4l7QEjV5EPiMRjCa6RFbpTfBUtAvZnEfhqoD JMxNAAHJEWjbopfHTAQ0eYatAyGhex2qoPoxoy4HSPL97u1EM0HgBvQncw2cI+9IqJU2VHwz wpAirXZ7MOrgOqQ2wuxuXaCIcVVpbQkfZUYpINSje2LPNpoHzd+nk787q9o5uEUHvKVVb5Y7 wjXEQayYtiz38EYg6BZ+kg6Qoj+xcAioaDF/8cB4X8dsZ4TFWzyEXSBSHeOZ7j+iA9XpDhFh dpS6J+6Oq4PUzQ09FwgxZ/Xv9uTHlwvS19cFjdPSYP2oiOlQVe52L+e/LB3Ly9yeUxJ4frgk v7RKFo8rJ6SAvy3kbBuyn8sf8OV2zjkzAn6h6SgK4NjR3kUqRbCAEgEgPOExpV+8kB8mI63J OKzCT5JsCec8wZZykS39EZpJ6fieMyFA4kz4x583E+3qG4sUuav81OrJpODXixc5f8g4x5tO cI5+smmhOSDEeeNfuMl/+W1GzCQOKRjb27aamTOldnz/jNdQgfSTf8laSi8w27kAuMcAvvj9 B8l1jkJJIrdT3vDZTO/s7LB5VD1tkAgUI/isThSJPa2JMLsY8Ucsl9GKUXNETYuALjJv0BiV v3mIcQtLPRHOg8nKKWJXfEHkW5xYHH+EN8R5HHnulvkQQTkfYgu9D5AXivAZrcpbJLjnV87H Gi72oWcgM6LOIjGySCzOrxyaBpze59rpGLj9WUG7XeMJtprgOFaW3kz/cXfLCfv+v1YuHp2U H/6OeU78J7W7vanv/3d2ctt4/7+5mVve/3+PZ2NDMdrVxkYy+RaNqwdoezTBPCRkGjodwhrs mqQmeMy5GAEN3wxGH831MqU6wWPQfjLZHvpZbNefqg26wmp7+J4tTPiVufHBD6SreOp/EB/Y ZLujNqbj0cZ41E4OW3h6yJbUc/WvDZtuMdziOJFYAWmii5ozzgKhP6PiDa3PPg+mySSagmfQ SaJF9v1q8DEj7UY2mkw2BgIArD9SJ8XS28ppWV14vS5Zb8J8Vwgmck4UTfJK0k+OINqdXPDV OSZLw5Dts+qS6ycUbNDARxgjdAh9ryeTxT6bP6xi1pAevBCDDfiVzSb7YzTb+Ok1nD0P60eY OXBpRrV8ls/yWT7LZ/ksn+WzfJbP8lk+y2f5LJ/ls3yWz/JZPn+l5/8AdEbDYgBAAQA= --SLDf9lqlvOQaIe6s-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 11:01:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05754 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:01:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles238.castles.com [208.214.165.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05734 for ; Mon, 12 Oct 1998 11:01:37 -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 LAA07090; Mon, 12 Oct 1998 11:06:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810121806.LAA07090@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: fjaccard@urbanet.ch cc: current@FreeBSD.ORG Subject: Re: [GIMPS] /proc/net/route needed In-reply-to: Your message of "Mon, 12 Oct 1998 19:11:49 +0200." <000001bdf603$663ab460$0100a8c0@sicel-3-213.urbanet.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 11:06:11 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > I am trying to run the linux version of the GIMPS (mprime 16.4). It works > but does not connect top the server. I did a ktrace and it fails to read > /proc/net/route. Is there anyway to have this /proc/net emulated or any way > to have mprime connect? Not immediately. We need to start building an emulation of the (supremely bogus) linux /proc hierarchy. I can't imagine why a user-space application needs to access *routing* information. Why not complain to the people that wrote 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 Mon Oct 12 11:06:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06433 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:06:26 -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 LAA06427 for ; Mon, 12 Oct 1998 11:06:20 -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 OAA00480; Mon, 12 Oct 1998 14:07:30 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Mon, 12 Oct 1998 14:07:29 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: bitten 3 times already. In-Reply-To: <199810121803.LAA07056@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 ok, thanks, what about multiblock transactions though? anyhow fixing and rebooting. thanks again. 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, 12 Oct 1998, Mike Smith wrote: > > >Also: > > >wdc0 at 0x1f0-0x1f7 irq 14 flags 0x7fff7fff on isa > > You installed this while sysinstall was broken a while back. Start by > changing the 'flags' value for wdc0 to 0x40004000 (just enable DMA). > > -- > \\ 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 12 11:11:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06958 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:11:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles238.castles.com [208.214.165.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06937 for ; Mon, 12 Oct 1998 11:10:46 -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 LAA07175; Mon, 12 Oct 1998 11:15:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810121815.LAA07175@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: Mike Smith , current@FreeBSD.ORG Subject: Re: bitten 3 times already. In-reply-to: Your message of "Mon, 12 Oct 1998 14:07:29 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 11:15:07 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ok, thanks, what about multiblock transactions though? > anyhow fixing and rebooting. thanks again. DMA implicitly implies multiblock (as I understand 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 Mon Oct 12 11:19:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07747 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:19:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07739 for ; Mon, 12 Oct 1998 11:19:21 -0700 (PDT) (envelope-from bhilton@vpop.net) Received: from vpop.net (gandalf.vpop.net [206.117.152.3]) by boromir.vpop.net (8.9.1/8.8.5) with ESMTP id LAA10543 for ; Mon, 12 Oct 1998 11:19:09 -0700 (PDT) Message-ID: <3622481D.2200E666@vpop.net> Date: Mon, 12 Oct 1998 11:19:09 -0700 From: Brad Hilton X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: perl5 & gdbm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am running 3.0-current as of 10/12/1998 (ELF), and have been unable to get perl5 to link against gdbm. I noticed the port for perl5 is marked as broken, and yet when I compile perl from within the source tree, it won't link against gdbm either (I have installed gdbm from ports). I can always just build perl5 from the tar ball, but I thought I'd mention this as a possible "bug fix" to address before the release date. Thanks for all the great work on current. -Brad -- Brad Hilton VPOP Technologies To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 11:22:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08210 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:22:25 -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 LAA08205 for ; Mon, 12 Oct 1998 11:22:22 -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 TAA12130; Mon, 12 Oct 1998 19:21:59 +0100 (BST) Date: Mon, 12 Oct 1998 19:21:59 +0100 (BST) From: Karl Pielorz To: Philippe Regnauld cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-19981009-BETA + 2840 AHA + camcontrol stop/start = panic In-Reply-To: <19981012200315.57827@deepo.prosa.dk> 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, 12 Oct 1998, Philippe Regnauld wrote: > Philippe Regnauld writes: > > Tried again. Had to fiddle a bit more with camcontrol: > double fault! > > inst point: 0x8:0xf014a92f > stck point: 0x10:0xf0277b28 > fram point: 0x10:0xf0277b3c Hmmm... Are you sure it's wise to spin the drive down? - My laptop running FreeBSD rarely survives it's pre-CAM ide drive spinning down and backup again? At the risk of being _way out_ - If spinning the drive down, then up kills the system, don't do it? ;-) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 11:28:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09178 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:28:45 -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 LAA09170 for ; Mon, 12 Oct 1998 11:28:44 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id LAA29285; Mon, 12 Oct 1998 11:28:33 -0700 (PDT) Message-ID: <19981012112832.A28262@Alameda.net> Date: Mon, 12 Oct 1998 11:28:32 -0700 From: Ulf Zimmermann To: Cory Kempf , freebsd-current@FreeBSD.ORG Subject: Re: What is a BSP, and why does SMP panic about it? Reply-To: ulf@Alameda.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Cory Kempf on Sun, Oct 11, 1998 at 10:20:50AM -0400 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 11, 1998 at 10:20:50AM -0400, Cory Kempf wrote: > This may be more properly sent to the SMP list... > > I have an Intel DK440LX motherboard with 1 CPU (the second is on > order). > > I decided to try making the kernel with SMP turned on, to make sure > everything works before plugging in the second CPU. One of the SMP > web pages seemed to imply that one could run a SMP kernel on a > uniprocessor box, with some performance degredation. > > >From my config file: > #SMP: > options SMP > options APIC_IO > options NCPU=1 > options NBUS=3 > options NAPIC=1 > options NINTR=24 > > > When I attempted to boot, I got a panic: no BSP found. > > Uh, what is a BSP, and where can they be found? > > Thanks, Can't tell anything about BSP, but about the Intel Dk440LX board. I use the same board with two PII-300 and it works great. Have been doing make buildworlds in below 1 hour fine. > > +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 -- 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 12 11:30:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09386 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:30:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09379 for ; Mon, 12 Oct 1998 11:30:38 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id UAA13332; Mon, 12 Oct 1998 20:28:28 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id UAA04383; Mon, 12 Oct 1998 20:25:19 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199810121825.UAA04383@semyam.dinoco.de> To: Alfred Perlstein Cc: Zach Heilig , current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: wd, crash dumps and strange geometries (was: Re: bitten 3 times already. ) In-reply-to: Your message of "Mon, 12 Oct 1998 19:10:00 +0200." <199810121710.TAA28992@semyam.dinoco.de> Date: Mon, 12 Oct 1998 20:25:16 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What I see here is what I'd expect for about 16.000 sectors/cylinder. > That's not a reasonable number and I guess the driver thinks it has 16 > heads and 1023 sectors/cylinder due to using LBA. I took a closer look, thought about this and noticed that the para- meters you get are from the enforcement of 15 heads with the flags you set. This in itself doesn't matter for normal accesses as you use LBA and that doesn't need a geometry. Now comes the fun part. If the drive thinks it has 16 heads (that is the shipping default for the DHEA-38451 according to the web site) and you use the geometry for 15 heads the CHS addressing will be wrong and maybe this is what somehow caused the failure you saw. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 11:31:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09436 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:31:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09410 for ; Mon, 12 Oct 1998 11:31:03 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id UAA13331; Mon, 12 Oct 1998 20:28:24 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id TAA28992; Mon, 12 Oct 1998 19:10:01 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199810121710.TAA28992@semyam.dinoco.de> To: Alfred Perlstein cc: Zach Heilig , current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: bitten 3 times already. In-reply-to: Your message of "Mon, 12 Oct 1998 11:23:57 EDT." Date: Mon, 12 Oct 1998 19:10:00 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > a: 81920 0 4.2BSD 0 0 0 # (Cyl. 0 - 5*) > b: 614400 163840 swap # (Cyl. 10*-48*) > wdc0: unit 0 (wd0): , LBA, DMA, multi-block-16, sleep-hack > wd0: 8063MB (16514064 sectors), 17475 cyls, 15 heads, 63 S/T, 512 B/S You have 63 sectors/track which makes 945 sectors/cylinder for 15 heads. Taking this into account I'd expect the start cylinder for the swap partition to be somewhere around cylinder 173 and not 10. What I see here is what I'd expect for about 16.000 sectors/cylinder. That's not a reasonable number and I guess the driver thinks it has 16 heads and 1023 sectors/cylinder due to using LBA. It would be interesting to see what disklabel has to say about the geometry. Seeing these numbers I expect them to be totally wrong and not trustworthy. Now when you do a dump the wd driver does *NOT* use LBA but relies on this geometry and uses CHS addressing. Wrong geo- metry and crash dump makes *boom* then. :-( The fix to avoid getting caught by this again (if my theory is right) I think is pretty obvious. During dump use LBA when we use it for the normal disk accesses. And one could put the propper geometry in which would make CHS addressing work in that case unless something forbibs that. And of course in normal use it works as you use LBA all the time and never rely on any geometry. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 11:32:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09556 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:32:08 -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 LAA09550 for ; Mon, 12 Oct 1998 11:32:05 -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 EAA20019; Tue, 13 Oct 1998 04:31:47 +1000 Date: Tue, 13 Oct 1998 04:31:47 +1000 From: Bruce Evans Message-Id: <199810121831.EAA20019@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: bitten 3 times already. Cc: bright@hotjobs.com, current@FreeBSD.ORG, zach@gaffaneys.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >Also: >> >wdc0 at 0x1f0-0x1f7 irq 14 flags 0x7fff7fff on isa > >You installed this while sysinstall was broken a while back. Start by >changing the 'flags' value for wdc0 to 0x40004000 (just enable DMA). DMA is 0x20002000. 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 12 11:46:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11466 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:46:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles203.castles.com [208.214.165.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11443 for ; Mon, 12 Oct 1998 11:46: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 LAA07390 for ; Mon, 12 Oct 1998 11:51:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810121851.LAA07390@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: bitten 3 times already. In-reply-to: Your message of "Tue, 13 Oct 1998 04:31:47 +1000." <199810121831.EAA20019@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 11:51:13 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> >Also: > >> >wdc0 at 0x1f0-0x1f7 irq 14 flags 0x7fff7fff on isa > > > >You installed this while sysinstall was broken a while back. Start by > >changing the 'flags' value for wdc0 to 0x40004000 (just enable DMA). > > DMA is 0x20002000. Foo, what I get for not doing my mental hex arithmetic. -- \\ 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 12 11:46:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11484 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:46:42 -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 LAA11457 for ; Mon, 12 Oct 1998 11:46:34 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id MAA25828; Mon, 12 Oct 1998 12:46:10 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810121846.MAA25828@panzer.plutotech.com> Subject: Re: 3.0-19981009-BETA + 2840 AHA + camcontrol stop/start = panic In-Reply-To: <19981012194716.53997@deepo.prosa.dk> from Philippe Regnauld at "Oct 12, 98 07:47:16 pm" To: regnauld@deepo.prosa.dk (Philippe Regnauld) Date: Mon, 12 Oct 1998 12:46:10 -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 Philippe Regnauld wrote... > Conf: 486-100 16MB > SCSI: AHA-2840 (Vesa controller) > Seagate 1GB HAWK > > Symptom: > > - insalled 3.0-19981009-BETA, dedicated (entire disk) partition > - rebooted, changed to root and typed (all this with the GENERIC kernel): > > # camcontrol stop (click... spin down)... > [pause] > > I get the prompt back > > # camcontrol start (spins up) > camcontrol start/stop takes 0/1 argument > # > > couple of seconds later: panic... > > virtual address: 0x24 > code: sup. read, page not present > inst pointer: 0x8:0xf010553d > stack pointer: 0x10:0xf0277ee4 > frame pointer: 0x10:0xf0277eec > code seg: base 0x0, limit 0xfffff, type 0x1b > dpl 0, pres 1, def32 1, gran 1 > ... > interrupt mask: cam > trap #: 12 > panic: page fault > > syncing disks... 1 1 1 1 1 1 1 ... 1 1 giving up Patient: "Doctor, I shot myself in the foot and it hurts!" Doctor: "Well then, don't do that!" It's generally not a good idea to spin down your boot drive. I'm not sure what's going on here, though. Unless you can provide a stack trace, or at least the functions around the given instruction pointer, there's no way to know where the panic is. Try setting up a serial console and DDB so you can get a stack trace. 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 12 11:54:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12726 for freebsd-current-outgoing; Mon, 12 Oct 1998 11:54:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsmangler.inet.tele.dk (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12697 for ; Mon, 12 Oct 1998 11:54:36 -0700 (PDT) (envelope-from bofh@newsmangler.int.tele.dk) Received: from localhost (bofh@localhost) by newsmangler.inet.tele.dk (8.9.1/8.8.8) with SMTP id UAA04263 for ; Mon, 12 Oct 1998 20:52:46 +0200 (CEST) (envelope-from bofh@newsmangler.int.tele.dk) X-Authentication-Warning: newsmangler.inet.tele.dk: bofh owned process doing -bs Date: Mon, 12 Oct 1998 20:52:10 +0200 (CEST) From: Fluffy XXX X-Sender: bofh@newsmangler.inet.tele.dk To: freebsd-current@FreeBSD.ORG Subject: sysinstall Bug or Feature? 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 DON'T REPLY TO ME BY MAIL, B0RKEN ADDRESS ABOVE Just installed a recent BETA for laughs, and also to test out some bugs I've seen before. Can't reproduce one of 'em, and figured out what's happening with another. When running sysinstall to actually download and install the distribution parts, I am presented with a spiffy screen for network configuration of my ethernet card. Here's what happens: When I initially enter the values and use the down- arrow to move between fields (a bad habit I know), all is peachy-keen. However, if I find I've botched an entry, when I go through the config screen again, this time making the changes to the afflicted entries and then using the down-arrow to move along, results in the field being returned to its previous contents. However, if I use the return key to enter the correction and move down, it works as expected. It took me a while to figure this out. Is it supposed to work this way? Should the down-arrow revert to the previous contents, or should changes made take effect? Is it a Bug or a Feature? And if the desired behavior is that at present, maybe a note to that effect should be put into the F1 help screen, in case others do things the same way, since it took me quite a while to even notice that my changes weren't taking. I believe that in the past, when I've botched something like the IP address or gateway or whatever, and I notice it after the system is trying to use the wrong values, there's no easy way to ^C escape from this and get back to the config screen to fix it, unless one either waits for something to time out, or interrupts it and starts afresh from the beginning, but I didn't verify that with this present installation. I guess I should, as it's an easy trap for unwary beginners... thanks, barry bouwsma, tele danmark internet NO E-MAIL YET, reply to the list only, I follow along by news if at all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 12:11:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15998 for freebsd-current-outgoing; Mon, 12 Oct 1998 12:11:28 -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 MAA15981 for ; Mon, 12 Oct 1998 12:11:23 -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 FAA22479; Tue, 13 Oct 1998 05:11:04 +1000 Date: Tue, 13 Oct 1998 05:11:04 +1000 From: Bruce Evans Message-Id: <199810121911.FAA22479@godzilla.zeta.org.au> To: bright@hotjobs.com, seggers@semyam.dinoco.de Subject: Re: wd, crash dumps and strange geometries (was: Re: bitten 3 times already. ) Cc: current@FreeBSD.ORG, zach@gaffaneys.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> What I see here is what I'd expect for about 16.000 sectors/cylinder. >> That's not a reasonable number and I guess the driver thinks it has 16 >> heads and 1023 sectors/cylinder due to using LBA. LBA is essentially equivalent to CHS with 65536 cylinders, 16 heads, and 256 sectors/track (except CHS can't actually handle 64 sectors/track; sector numbers start at 1 and there are 8 sector bits, so the limit is 255 sectors/track). The 1023 "sectors/cylinder" limit is actually 1024 total cylinders in the partition table and 65536 cylinders in the IDE interface. >I took a closer look, thought about this and noticed that the para- >meters you get are from the enforcement of 15 heads with the flags you >set. This in itself doesn't matter for normal accesses as you use LBA >and that doesn't need a geometry. >Now comes the fun part. If the drive thinks it has 16 heads (that is >the shipping default for the DHEA-38451 according to the web site) and >you use the geometry for 15 heads the CHS addressing will be wrong and >maybe this is what somehow caused the failure you saw. Now I understand this. There is an off by 1 error in the WDOPT_FORCEHD() rule. 15 should mean that the maximum head number is 15 and the total number of heads is 16, like it does almost everywhere else. As it is there is no way to force the normal (maximum and best) value of 16 heads. Big drives should all use this for their default translation mode; anything less reduces the usable drive size to even less than the 504MB limit under ancient BIOSes. Please ignore previous mail where I got the maximum number of heads and sectors/track wrong :-). The limits are 255 heads and 63 sectors/track only in the partition table, but they are 16 heads and 255 sectors/track at the IDE interface level. The head limit should be 256 in the partition table, but so many entities are confused about this that the natural limit can't be used. 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 12 12:30:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20926 for freebsd-current-outgoing; Mon, 12 Oct 1998 12:30:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20903 for ; Mon, 12 Oct 1998 12:30:37 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id VAA19441; Mon, 12 Oct 1998 21:28:34 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id VAA26752; Mon, 12 Oct 1998 21:27:58 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199810121927.VAA26752@semyam.dinoco.de> To: Alfred Perlstein Cc: Zach Heilig , current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: wd, crash dumps and strange geometries (was: Re: bitten 3 times already. ) In-reply-to: Your message of "Mon, 12 Oct 1998 20:25:16 +0200." <199810121825.UAA04383@semyam.dinoco.de> Date: Mon, 12 Oct 1998 21:27:56 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > you use the geometry for 15 heads the CHS addressing will be wrong and > maybe this is what somehow caused the failure you saw. I looked at where exactly the system puts the crash dump. At the *end* of the partition you give it. With 15 heads you get to larger cylinders (nearer your /usr) faster than with the correct 16 heads so what happens I suppose is that it overwrites most of the start of /usr due to taking the wrong geometry. I am pretty convinced that using the same mode for crash dumps as for normal block reads/writes prevents this kind of disaster. Maybe some- one can commit a fix? Or shall I send a PR with my suggestion in- stead? Why was it that one put the at partitions end in the first place? Am I right when I guess it was so that one could enable swapping, do a little bit of it and still get reasonable crash dumps? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 12:38:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22864 for freebsd-current-outgoing; Mon, 12 Oct 1998 12:38:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA22839 for ; Mon, 12 Oct 1998 12:38:41 -0700 (PDT) (envelope-from brian@hyperreal.org) Received: (qmail 13377 invoked by uid 24); 12 Oct 1998 19:38:27 -0000 Message-ID: <19981012193827.13376.qmail@hyperreal.org> X-Sender: brian@hyperreal.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Mon, 12 Oct 1998 12:09:48 -0700 To: freebsd-current@FreeBSD.ORG From: Brian Behlendorf Subject: build failures in lib/libutil/auth.c Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> lib/libutil [...] cc -O -pipe -Wall -DLIBC_SCCS -I/usr/src/lib/libutil -I/usr/src/lib/libutil/../../sys -c /usr/src/lib/libutil/auth.c -o auth.o /usr/src/lib/libutil/auth.c: In function `auth_getval': /usr/src/lib/libutil/auth.c:67: `_PATH_AUTHCONF' undeclared (first use this function) /usr/src/lib/libutil/auth.c:67: (Each undeclared identifier is reported only once /usr/src/lib/libutil/auth.c:67: for each function it appears in.) *** Error code 1 Willing to help track this down... where are the various _PATH_ variables supposed to be defined? Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- Where will YOU be Oct 14-16? | brian@apache.org ApacheCon '98! http://www.apachecon.com/ | brian@hyperreal.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 12 12:52:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25820 for freebsd-current-outgoing; Mon, 12 Oct 1998 12:52: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 MAA25720 for ; Mon, 12 Oct 1998 12:52:03 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:Y5FcFmnQ4B+AFfx3CsBx8TRrXwwC6NdY@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id VAA02992; Mon, 12 Oct 1998 21:51:26 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810121951.VAA02992@gratis.grondar.za> To: Brad Hilton cc: current@FreeBSD.ORG Subject: Re: perl5 & gdbm In-Reply-To: Your message of " Mon, 12 Oct 1998 11:19:09 MST." <3622481D.2200E666@vpop.net> References: <3622481D.2200E666@vpop.net> Date: Mon, 12 Oct 1998 21:51:25 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Hilton wrote: > I am running 3.0-current as of 10/12/1998 (ELF), and have been unable to > get perl5 to link against gdbm. I was wondering when this was going to raise its ugly head :-) > I can always just build perl5 from the tar ball, but I thought I'd > mention this as a possible "bug fix" to address before the release date. I'll do my best; no promises. 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 12 12:56:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26923 for freebsd-current-outgoing; Mon, 12 Oct 1998 12:56:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26891 for ; Mon, 12 Oct 1998 12:56:36 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id VAA20419; Mon, 12 Oct 1998 21:50:10 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id VAA28350; Mon, 12 Oct 1998 21:35:02 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199810121935.VAA28350@semyam.dinoco.de> To: Bruce Evans cc: bright@hotjobs.com, zach@gaffaneys.com, current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: bitten 3 times already. In-reply-to: Your message of "Tue, 13 Oct 1998 02:14:03 +1000." <199810121614.CAA12373@godzilla.zeta.org.au> Date: Mon, 12 Oct 1998 21:35:02 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Dumps and LBA mode should't be mixed, since the dump routine doesn't > support LBA mode and it uses CHS mode with nominal geometry if LBA mode Why is this so? I don't see why it shouldn't use LBA, too if LBA is on for the drive. That it doesn't support that now seems pretty easy to fix to me. Just change the way it calculates the numbers and that's it as far as I can see from my docs and what wd does. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 13:10:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29826 for freebsd-current-outgoing; Mon, 12 Oct 1998 13:10:31 -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 NAA29815 for ; Mon, 12 Oct 1998 13:10:25 -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 NAA14883; Mon, 12 Oct 1998 13:10:10 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 12 Oct 1998 13:10:09 -0700 (PDT) From: Doug White To: Ryan Ward cc: FreeBSD Current Subject: Re: Question about make world In-Reply-To: <000101bdf49c$8e18afe0$97176c18@blade.v-wave.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, 10 Oct 1998, Ryan Ward wrote: > Not sure where this type of mail would best fit in. I been trying to do a > make world for the last week and it craps out on me in the same place. I > have CVSup running to grab the current source tree. This is no problem. In general -CURRENT questions belong on current@freebsd.org. 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 12 13:48:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08242 for freebsd-current-outgoing; Mon, 12 Oct 1998 13:48:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08112; Mon, 12 Oct 1998 13:47:48 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.1/8.9.1) id AAA18816; Tue, 13 Oct 1998 00:47:31 +0400 (MSD) (envelope-from ache) Message-ID: <19981013004730.A17881@nagual.pp.ru> Date: Tue, 13 Oct 1998 00:47:30 +0400 From: "Andrey A. Chernov" To: current@FreeBSD.ORG Cc: jdp@FreeBSD.ORG Subject: a.out: ld errors building libatm Mail-Followup-To: current@freebsd.org, jdp@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With all -current recently builded tools I got in libatm building shared atm library (version 2.0) ld: /usr/lib/aout/libmd.a(md5c.o): RRS text relocation at 0x1710 for "_memset" ld: /usr/lib/aout/libmd.a(md5c.o): RRS text relocation at 0x1079 for "_memset" ld: /usr/lib/aout/libmd.a(md5c.o): RRS text relocation at 0xfeb for "_memcpy" ld: /usr/lib/aout/libmd.a(md5c.o): RRS text relocation at 0xfa0 for "_memcpy" what this diagnostics means and how to fix it? -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 13:53:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09580 for freebsd-current-outgoing; Mon, 12 Oct 1998 13:53:09 -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 NAA09496 for ; Mon, 12 Oct 1998 13:52:34 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id OAA07467; Mon, 12 Oct 1998 14:45:26 -0600 (MDT) Date: Mon, 12 Oct 1998 14:45:26 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199810122045.OAA07467@narnia.plutotech.com> To: Karl Pielorz cc: current@FreeBSD.ORG Subject: Re: 3.0-19981009-BETA + 2840 AHA + camcontrol stop/start = panic Newsgroups: pluto.freebsd.current 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 > Hmmm... Are you sure it's wise to spin the drive down? - My laptop running > FreeBSD rarely survives it's pre-CAM ide drive spinning down and backup > again? It shouldn't cause a problem. I'd be very interested in knowing where the panic is occuring. -- 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 12 14:10:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15105 for freebsd-current-outgoing; Mon, 12 Oct 1998 14:10:14 -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 OAA15042 for ; Mon, 12 Oct 1998 14:10: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 OAA17358; Mon, 12 Oct 1998 14:09:56 -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 OAA22470; Mon, 12 Oct 1998 14:09:55 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id OAA12095; Mon, 12 Oct 1998 14:09:53 -0700 (PDT) From: Don Lewis Message-Id: <199810122109.OAA12095@salsa.gv.tsc.tdk.com> Date: Mon, 12 Oct 1998 14:09:53 -0700 X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: freebsd-current@FreeBSD.ORG, jb@cimlogic.com.au Subject: gnu/usr.bin/cc/cc_tools/Makefile bug? (was Re: filesystem safety and SCSI disk write caching) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From a thread I started on the scsi and fs lists ... On Oct 12, 6:18am, Don Lewis wrote: } Subject: Re: filesystem safety and SCSI disk write caching } I haven't yet had time to try to track down why "make -j4 buildworld" } fails with the standard mount options. Found it. --- gcc.o --- In file included from /usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/gcc.c:706: /usr/obj/elf/usr/src/gnu/usr.bin/cc/cc/../cc_tools/specs.h:2: `lude' undeclared here (not in a function) /usr/obj/elf/usr/src/gnu/usr.bin/cc/cc/../cc_tools/specs.h:2: initializer element for `default_compilers[21]' is not constant /usr/obj/elf/usr/src/gnu/usr.bin/cc/cc/../cc_tools/specs.h:2: parse error before string constant In file included from /usr/obj/elf/usr/src/gnu/usr.bin/cc/cc/../cc_tools/specs.h:3, from /usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/gcc.c:706: /usr/src/gnu/usr.bin/cc/cc/f2c-specs.h:3: parse error before `{' *** Error code 1 1 error *** Error code 2 1 error Taking a look at specs.h: % cat /usr/obj/elf/usr/src/gnu/usr.bin/cc/cc/../cc_tools/specs.h #include "cp/lang-specs.h" lude "f2c-specs.h" #include "f2c-specs.h" Taking a look at the log file from make -j4 buildworld: ===> cc_tools --- config.h --- --- hconfig.h --- --- tconfig.h --- --- options.h --- --- config.h --- echo '#include "i386/freebsd.h"' > tm.h echo '#include "i386/xm-freebsd.h"' > config.h echo '#include "i386/xm-freebsd.h"' > hconfig.h --- hconfig.h --- echo '#include "i386/freebsd.h"' > tm.h echo '#include "i386/xm-freebsd.h"' > config.h --- tconfig.h --- echo '#include "i386/freebsd.h"' > tm.h --- options.h --- echo '#include "i386/freebsd.h"' > tm.h --- tconfig.h --- echo '#include "i386/xm-freebsd.h"' > config.h --- hconfig.h --- echo '#include "i386/xm-freebsd.h"' > hconfig.h --- options.h --- echo '#include "i386/xm-freebsd.h"' > config.h --- tconfig.h --- echo '#include "i386/xm-freebsd.h"' > hconfig.h --- config.h --- echo '#include "i386/xm-freebsd.h"' > tconfig.h --- hconfig.h --- echo '#include "i386/xm-freebsd.h"' > tconfig.h --- tconfig.h --- echo '#include "i386/xm-freebsd.h"' > tconfig.h --- options.h --- echo '#include "i386/xm-freebsd.h"' > hconfig.h --- config.h --- echo '#include "cp/lang-options.h"' > options.h --- hconfig.h --- echo '#include "cp/lang-options.h"' > options.h --- options.h --- echo '#include "i386/xm-freebsd.h"' > tconfig.h --- tconfig.h --- echo '#include "cp/lang-options.h"' > options.h --- config.h --- echo '#include "cp/lang-specs.h"' > specs.h --- hconfig.h --- echo '#include "cp/lang-specs.h"' > specs.h --- options.h --- echo '#include "cp/lang-options.h"' > options.h --- tconfig.h --- echo '#include "cp/lang-specs.h"' > specs.h --- config.h --- echo '#include "f2c-specs.h"' >> specs.h --- hconfig.h --- echo '#include "f2c-specs.h"' >> specs.h --- bi-parser.c --- --- tconfig.h --- echo '#include "f2c-specs.h"' >> specs.h --- options.h --- echo '#include "cp/lang-specs.h"' > specs.h --- bi-parser.c --- bison -d /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bi-parser.y -o bi-parser.c --- options.h --- echo '#include "f2c-specs.h"' >> specs.h Taking a look at gnu/usr.bin/cc/cc_tools/Makefile: # the host/target compiler config. COMMONHDRS= config.h hconfig.h tconfig.h tm.h options.h specs.h ${COMMONHDRS}: echo '#include "${MACHINE_ARCH}/freebsd.h"' > tm.h echo '#include "${MACHINE_ARCH}/xm-freebsd.h"' > config.h echo '#include "${MACHINE_ARCH}/xm-freebsd.h"' > hconfig.h echo '#include "${MACHINE_ARCH}/xm-freebsd.h"' > tconfig.h echo '#include "cp/lang-options.h"' > options.h echo '#include "cp/lang-specs.h"' > specs.h echo '#include "f2c-specs.h"' >> specs.h GENSRCS+= ${COMMONHDRS} It sure looks like if you do a parallel make, these .h files get built in parallel multiple times. Most of the time we appear to get lucky and they happen to come out correct. If we don't want to rely on luck, then this Makefile should have a separate rule for each of these .h files. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 14:12:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15633 for freebsd-current-outgoing; Mon, 12 Oct 1998 14:12:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sockratte.schell.de (polz.de [195.20.238.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15527 for ; Mon, 12 Oct 1998 14:12:18 -0700 (PDT) (envelope-from sas@schell.de) Received: from guerilla.foo.bar (hennen32s.iserlohn.netsurf.de [194.195.194.226]) by sockratte.schell.de (8.9.1/8.9.1) with ESMTP id XAA13994 for ; Mon, 12 Oct 1998 23:11:57 +0200 Received: from localhost (localhost.foo.bar [127.0.0.1]) by guerilla.foo.bar (8.9.1/8.9.1) with ESMTP id XAA02296 for ; Mon, 12 Oct 1998 23:11:44 +0200 (CEST) Date: Mon, 12 Oct 1998 23:11:44 +0200 (CEST) From: Sascha Schumann To: freebsd-current@FreeBSD.ORG Subject: real >= user + sys? 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 Maybe I donn't understand process accounting information after years of using them, but while time'ing a simple program: real 0m2.348s user 0m2.988s sys 0m0.162s And later: real 0m2.315s user 0m3.013s sys 0m0.121s Pretty weird. The program is memory/cpu intensive (sorting and searching in a binary tree with about 50000 entries). This has happened on -current, last make world on Oct 10 with a kernel from Sep 26. Sascha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 14:28:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19150 for freebsd-current-outgoing; Mon, 12 Oct 1998 14:28:18 -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 OAA18920; Mon, 12 Oct 1998 14:27:58 -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 OAA06986; Mon, 12 Oct 1998 14:27:40 -0700 (PDT) (envelope-from jdp) Message-Id: <199810122127.OAA06986@austin.polstra.com> To: "Andrey A. Chernov" cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: a.out: ld errors building libatm In-reply-to: Your message of "Tue, 13 Oct 1998 00:47:30 +0400." <19981013004730.A17881@nagual.pp.ru> Date: Mon, 12 Oct 1998 14:27:40 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With all -current recently builded tools I got in libatm > > building shared atm library (version 2.0) > ld: /usr/lib/aout/libmd.a(md5c.o): RRS text relocation at 0x1710 for "_memset" > ld: /usr/lib/aout/libmd.a(md5c.o): RRS text relocation at 0x1079 for "_memset" > ld: /usr/lib/aout/libmd.a(md5c.o): RRS text relocation at 0xfeb for "_memcpy" > ld: /usr/lib/aout/libmd.a(md5c.o): RRS text relocation at 0xfa0 for "_memcpy" > > what this diagnostics means and how to fix it? This is because Peter added a dependency on libmd, but there is no shared version of it on a.out systems. So the .a library, which is non-PIC, gets linked in. I think the correct solution is to build a shared libmd on a.out systems too. I.e., delete these lines from src/lib/libmd/Makefile: .if ${OBJFORMAT} != elf NOPIC= true .endif Peter, do you see any reason not to make that change? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 14:34:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20534 for freebsd-current-outgoing; Mon, 12 Oct 1998 14:34:21 -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 OAA20529 for ; Mon, 12 Oct 1998 14:34:19 -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 OAA17660; Mon, 12 Oct 1998 14:32: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 OAA22848; Mon, 12 Oct 1998 14:32:17 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id OAA12453; Mon, 12 Oct 1998 14:32:12 -0700 (PDT) From: Don Lewis Message-Id: <199810122132.OAA12453@salsa.gv.tsc.tdk.com> Date: Mon, 12 Oct 1998 14:32:12 -0700 In-Reply-To: Terry Lambert "Re: installworld and softupdates" (Oct 8, 10:39pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Terry Lambert , thomma@BayNetworks.COM (Tamiji Homma) Subject: Re: installworld and softupdates Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 8, 10:39pm, Terry Lambert wrote: } Subject: Re: installworld and softupdates } Disk space held by uncommitted deletes depending on other operations } is, by definition, not reusable until such time as the operations are } committed. } } Another fix would be to explicitly call "sync" at the appropriate } places to ensure the soft clock is drained (and thus deleted file } space was recovered before it was needed. Calling sync() can be pretty costly, and you still need to wait for a while for all the I/O has actually drained. } You can see this in action very easily by copying a full X11 tree } to a soft updates parition, syncing it out, deleting it, and then } doing a "df" once a second and watching the space "drain back". I've heard of software (diablo?) being bitten by a feature like this, though I don't remember the OS. For whatever reason it decided that it was out of space and that it needed to deleted some "old stuff" to make room. It started deleting "old stuff" and checking the amount of free space available. The amount of free space didn't go up, so it kept on deleting, until it had nuked almost everything on the partition. It was only after a fairly long interval that the OS started reporting the space that had been freed. } The soft updates code should arguably advance the slot clock at } an accelerated rate in the case that new entries are not being } made. Feel free to submit code. 8-). IMHO, statfs() should report the amount of free space on the disk that will be there after all the pending filesystem updates are complete, just like stat() tells you a file is gone after it has been unlinked even though its directory entry and inode haven't yet been cleared on disk. If a process wants to claim disk space that has not yet been freed on disk, at worst the process should sleep. Heck, you might even be able to optimize out some free space bitmap writes in the case where you delete a file and create a new file of the same size. It's just a small matter of programming ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 14:48:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23004 for freebsd-current-outgoing; Mon, 12 Oct 1998 14:48:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22998 for ; Mon, 12 Oct 1998 14:48:39 -0700 (PDT) (envelope-from tom@gorilla.net) Received: from silverback.gorilla.net (silverback.gorilla.net [208.128.8.1]) by freefall.freebsd.org (8.8.8/8.8.5) with SMTP id OAA03329 for ; Mon, 12 Oct 1998 14:48:37 -0700 (PDT) Received: from peeper.TOJ.org [208.143.84.89] by silverback.gorilla.net with ESMTP (SMTPD32-4.06) id A7583D2023E; Mon, 12 Oct 1998 16:40:40 CDT Received: (from tom@localhost) by peeper.TOJ.org (8.9.1/8.8.8) id QAA07306; Mon, 12 Oct 1998 16:45:05 -0500 (CDT) (envelope-from tom) Message-ID: <19981012164435.A7209@TOJ.org> Date: Mon, 12 Oct 1998 16:44:35 -0500 From: Tom Jackson To: Christoph Kukulies , freebsd-current@freefall.cdrom.com Subject: Re: /usr/lib/libskey.so.2: Undefined symbol "crypt" References: <199810120847.KAA21715@gilberto.physik.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810120847.KAA21715@gilberto.physik.RWTH-Aachen.DE>; from Christoph Kukulies on Mon, Oct 12, 1998 at 10:47:43AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try man vipw. While were at it, is the proper way to change from des to md5, to change the libcrypt link to libscrypt and then just invoke vipw and then close it to have the pwd_mkdb run? Maybe this will simplify when auth.conf is fully implemented. Cheers, On Mon, Oct 12, 1998 at 10:47:43AM +0200, Christoph Kukulies wrote: > > Since a couple of days my -current (elf) system (the 19981004 SNAP) > suffers from the fact that I cannot su nor login as root at the > console any longer (despite from going single user). > > I built the international descrypt stuff, installed it , created > the links in /usr/lib and since then I'm getting > > /usr/libexec/ld-elf.so.1: /usr/lib/libskey.so.2: Undefined symbol "crypt". > > What can I do to repair this? > > -- > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Tom -- IMail Server for Windows NT. Evaluation version. Copyright (c) 1995-98 Ipswitch, Inc. http://www.ipswitch.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 12 15:14:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27148 for freebsd-current-outgoing; Mon, 12 Oct 1998 15:14:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27142 for ; Mon, 12 Oct 1998 15:14:23 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id RAA16386; Mon, 12 Oct 1998 17:14:03 -0500 (CDT) Date: Mon, 12 Oct 1998 17:14:02 -0500 From: Dan Nelson To: Sascha Schumann , freebsd-current@FreeBSD.ORG Subject: Re: real >= user + sys? Message-ID: <19981012171402.A16177@emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: ; from "Sascha Schumann" on Mon Oct 12 23:11:44 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 12), Sascha Schumann said: > > Maybe I donn't understand process accounting information after years > of using them, but while time'ing a simple program: > > real 0m2.348s > user 0m2.988s > sys 0m0.162s That 'time' output looks weird. It doesn't match /usr/bin/time's format. Make sure that is isn't a bug in your shells' builtin time function if it has one. -Dan Nelson dnelson@emsphone.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 12 15:16:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27354 for freebsd-current-outgoing; Mon, 12 Oct 1998 15:16:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27341 for ; Mon, 12 Oct 1998 15:16:24 -0700 (PDT) (envelope-from rkw@Dataplex.NET) Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id TAA08678; Mon, 12 Oct 1998 19:14:58 -0500 (CDT) (envelope-from rkw@dataplex.net) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199810121806.LAA07090@dingo.cdrom.com> References: Your message of "Mon, 12 Oct 1998 19:11:49 +0200." <000001bdf603$663ab460$0100a8c0@sicel-3-213.urbanet.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 12 Oct 1998 17:14:11 -0500 To: Mike Smith From: Richard Wackerbarth Subject: Re: [GIMPS] /proc/net/route needed Cc: fjaccard@urbanet.ch, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:06 PM -0500 10/12/98, Mike Smith wrote: >> Hi, >> I am trying to run the linux version of the GIMPS (mprime 16.4). It works >> but does not connect top the server. I did a ktrace and it fails to read >> /proc/net/route. Is there anyway to have this /proc/net emulated or any way >> to have mprime connect? > >Not immediately. We need to start building an emulation of the >(supremely bogus) linux /proc hierarchy. > >I can't imagine why a user-space application needs to access *routing* >information. Why not complain to the people that wrote it? >From what I know about the GIMPS project, it is probably attempting to determine if there is an active route to the outside. It does this so that it can decide whether, or not, to attempt to connect to its external server. I suspect that this was done to avoid bringing up a dialup connection, etc. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 15:42:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01012 for freebsd-current-outgoing; Mon, 12 Oct 1998 15:42:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00997 for ; Mon, 12 Oct 1998 15:42:41 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id RAA16865; Mon, 12 Oct 1998 17:42:07 -0500 (CDT) Date: Mon, 12 Oct 1998 17:42:07 -0500 From: Dan Nelson To: Richard Wackerbarth , Mike Smith Cc: fjaccard@urbanet.ch, current@FreeBSD.ORG Subject: Re: [GIMPS] /proc/net/route needed Message-ID: <19981012174207.A16615@emsphone.com> References: <000001bdf603$663ab460$0100a8c0@sicel-3-213.urbanet.ch> <199810121806.LAA07090@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: ; from "Richard Wackerbarth" on Mon Oct 12 17:14:11 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 12), Richard Wackerbarth said: > At 1:06 PM -0500 10/12/98, Mike Smith wrote: > >I can't imagine why a user-space application needs to access *routing* > >information. Why not complain to the people that wrote it? > > From what I know about the GIMPS project, it is probably attempting > to determine if there is an active route to the outside. It does this > so that it can decide whether, or not, to attempt to connect to its > external server. > > I suspect that this was done to avoid bringing up a dialup > connection, etc. In which case, an active-filter on pppd (or a dfilter on user-ppp, but Linux doesn't have user-ppp :) would be a better solution. Think of a two-machine network; the second machine has its default route always pointing to the one with the modem on it, so GIMPS's route test wouldn't help. I say create a dummy /compat/linux/proc/net/route with a suitable default gateway defined. Iface Destination Gateway Flags RefCnt Use Metric Mask MTU Window IRTT eth0 00000000 0100000A 03 0 1 0 00000000 1500 0 0 should provide a default route via 10.0.0.1 for any program that thinks it needs to know. -Dan Nelson dnelson@emsphone.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 12 15:46:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01638 for freebsd-current-outgoing; Mon, 12 Oct 1998 15:46:03 -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 PAA01581; Mon, 12 Oct 1998 15:46:01 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA27905; Mon, 12 Oct 1998 15:42:32 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdT27898; Mon Oct 12 22:42:31 1998 Date: Mon, 12 Oct 1998 15:42:26 -0700 (PDT) From: Julian Elischer To: Nicolas Souchu cc: FreeBSD Hackers , -current , Luigi Rizzo , Roger Hardiman , Mike Smith Subject: Re: bktr over new I2C framework, ready In-Reply-To: <19981012195634.06516@breizh.prism.uvsq.fr> 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 yes but what IS it? I have an I2C device attached to some programmable pins and I understand the protocol, but 'bktr' means nothing to me.. What is it? julian On Mon, 12 Oct 1998, Nicolas Souchu wrote: > Hi there, > > bktr over the new I2C framework is now ready. Although, no man page is > available :( This is my next priority. > > But it works. Ready to test it? > > -- > Nicolas.Souchu@prism.uvsq.fr > FreeBSD - Turning PCs into workstations - 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 Mon Oct 12 15:56:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03384 for freebsd-current-outgoing; Mon, 12 Oct 1998 15:56:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03355; Mon, 12 Oct 1998 15:56:05 -0700 (PDT) (envelope-from netmonger@genesis.ispace.com) Received: from Celeris (56k-port4007.ime.net [209.90.195.17]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id SAA15484; Mon, 12 Oct 1998 18:55:27 -0400 (EDT) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.0.67.19981012185256.00a2c9c0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.67 (Beta) Date: Mon, 12 Oct 1998 18:53:40 -0400 To: Julian Elischer , Nicolas Souchu From: Drew Baxter Subject: Re: bktr over new I2C framework, ready Cc: FreeBSD Hackers , -current , Luigi Rizzo , Roger Hardiman , Mike Smith In-Reply-To: References: <19981012195634.06516@breizh.prism.uvsq.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Isn't it the Brooktree 848K driver? BKTR0 points to my Brooktree card that I got from my Intel beta kit ages ago. Made in Ireland.. Go figure.. But it works.. I think. :-) At 03:42 PM 10/12/98 -0700, Julian Elischer wrote: >yes but what IS it? > >I have an I2C device attached to some programmable pins >and I understand the protocol, >but 'bktr' means nothing to me.. What is it? > >julian > >On Mon, 12 Oct 1998, Nicolas Souchu wrote: > >> Hi there, >> >> bktr over the new I2C framework is now ready. Although, no man page is >> available :( This is my next priority. >> >> But it works. Ready to test it? >> >> -- >> Nicolas.Souchu@prism.uvsq.fr >> FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org >> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 16:28:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09325 for freebsd-current-outgoing; Mon, 12 Oct 1998 16:28:05 -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 QAA09268 for ; Mon, 12 Oct 1998 16:28: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 QAA00540; Mon, 12 Oct 1998 16:31:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810122331.QAA00540@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Richard Wackerbarth cc: Mike Smith , fjaccard@urbanet.ch, current@FreeBSD.ORG Subject: Re: [GIMPS] /proc/net/route needed In-reply-to: Your message of "Mon, 12 Oct 1998 17:14:11 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 16:31:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 1:06 PM -0500 10/12/98, Mike Smith wrote: > >> Hi, > >> I am trying to run the linux version of the GIMPS (mprime 16.4). It works > >> but does not connect top the server. I did a ktrace and it fails to read > >> /proc/net/route. Is there anyway to have this /proc/net emulated or any way > >> to have mprime connect? > > > >Not immediately. We need to start building an emulation of the > >(supremely bogus) linux /proc hierarchy. > > > >I can't imagine why a user-space application needs to access *routing* > >information. Why not complain to the people that wrote it? > > >From what I know about the GIMPS project, it is probably attempting to > determine if there is an active route to the outside. It does this so > that it can decide whether, or not, to attempt to connect to its external > server. > > I suspect that this was done to avoid bringing up a dialup connection, etc. Sorry, I'll try that again. I can't imagine why anyone would choose this approach, which is clearly unnecessarily system-dependant. -- \\ 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 12 16:35:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11231 for freebsd-current-outgoing; Mon, 12 Oct 1998 16:35:22 -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 QAA11176; Mon, 12 Oct 1998 16:35: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 QAA00592; Mon, 12 Oct 1998 16:37:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810122337.QAA00592@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: Nicolas Souchu , FreeBSD Hackers , -current , Luigi Rizzo , Roger Hardiman , Mike Smith Subject: Re: bktr over new I2C framework, ready In-reply-to: Your message of "Mon, 12 Oct 1998 15:42:26 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 16:37:53 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > yes but what IS it? > > I have an I2C device attached to some programmable pins > and I understand the protocol, > but 'bktr' means nothing to me.. What is it? It's the brooktree video capture driver. Most cards featuring this animal also have tuners onboard, and the tuner is normally accessed via an I2C interface. -- \\ 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 12 16:46:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13343 for freebsd-current-outgoing; Mon, 12 Oct 1998 16:46:48 -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 QAA13335 for ; Mon, 12 Oct 1998 16:46:46 -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 QAA29209; Mon, 12 Oct 1998 16:45:48 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Viren R. Shah" cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-19981009-BETA install report In-reply-to: Your message of "Sun, 11 Oct 1998 16:53:31 EDT." <199810112053.QAA00317@jabberwock.rstcorp.com> Date: Mon, 12 Oct 1998 16:45:47 -0700 Message-ID: <29205.908235947@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is easily verifiable thru the following steps: > > 1. boot with boot.flp > 2. use fixit mode and fixit.flp to startup network card > 3. when returned to the install menu, perform a novice install. > 4. It assumes the media is floppy. Thanks for this bug report - I've found and fixed the problem! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 17:32:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19145 for freebsd-current-outgoing; Mon, 12 Oct 1998 17:32:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19138; Mon, 12 Oct 1998 17:32:24 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id RAA05831; Mon, 12 Oct 1998 17:31:55 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199810130031.RAA05831@rah.star-gate.com> To: Julian Elischer cc: Nicolas Souchu , FreeBSD Hackers , -current , Luigi Rizzo , Roger Hardiman , Mike Smith , hasty@rah.star-gate.com Subject: Re: bktr over new I2C framework, ready In-reply-to: Your message of "Mon, 12 Oct 1998 15:42:26 PDT." Date: Mon, 12 Oct 1998 17:31:55 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bktr -- the bt848 video capture driver for freebsd. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 18:05:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23991 for freebsd-current-outgoing; Mon, 12 Oct 1998 18:05:26 -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 SAA23986 for ; Mon, 12 Oct 1998 18:05:23 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id DAA28279; Tue, 13 Oct 1998 03:05:01 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 13 Oct 1998 03:05:00 +0200 (MET DST) Mime-Version: 1.0 To: Sascha Schumann Cc: freebsd-current@FreeBSD.ORG Subject: Re: real >= user + sys? References: 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: 13 Oct 1998 03:04:59 +0200 In-Reply-To: Sascha Schumann's message of "Mon, 12 Oct 1998 23:11:44 +0200 (CEST)" Message-ID: Lines: 19 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 SAA23987 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sascha Schumann writes: > Maybe I donn't understand process accounting information after years of > using them, but while time'ing a simple program: > > real 0m2.348s > user 0m2.988s > sys 0m0.162s > > And later: > > real 0m2.315s > user 0m3.013s > sys 0m0.121s Known Obi-Wan bug in bash. Use /usr/bin/time. 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 12 18:07:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24304 for freebsd-current-outgoing; Mon, 12 Oct 1998 18:07:20 -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 SAA24286 for ; Mon, 12 Oct 1998 18:07: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 TAA22177 for ; Mon, 12 Oct 1998 19:39:21 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <3622A139.833751BD@webwizard.org.mx> Date: Mon, 12 Oct 1998 19:39:21 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.ORG Subject: Make elf release Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Due to a parity error in my memory:-) I forgot to remove my KERNFORMAT=elf system variable before making release and much to my surprise it made it through kernel creation. It looks like we will soon be able to make a 100% elf release. Has anyone done it? How important is it. Here's the result from my log before I redo it with an out kernel, if anyone is interested. Thanks, ed sh ../../conf/newvers.sh BOOTMFS cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitializ ed -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../inc lude -DKERNEL -include opt_global.h -elf vers.c loading kernel text data bss dec hex filename 1432928 102748 112540 1648216 192658 kernel ./dumpnlist /R/stage/boot.std/kernel > /tmp/mnt_xx/stand/symbols kzip -v /R/stage/boot.std/kernel kzip: bad magic in file /R/stage/boot.std/kernel, probably not a kernel kzip: extract returned 200 real kernel start address will be: 0x1 real kernel end address will be: 0x65aac68a *** Error code 3 Stop. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 18:10:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24967 for freebsd-current-outgoing; Mon, 12 Oct 1998 18:10: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 SAA24961 for ; Mon, 12 Oct 1998 18:10:55 -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 SAA01114; Mon, 12 Oct 1998 18:15:43 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810130115.SAA01114@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Viren R. Shah" cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-19981009-BETA install report In-reply-to: Your message of "Sun, 11 Oct 1998 16:53:31 EDT." <199810112053.QAA00317@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 18:15:43 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > BTW: the original NIC I had in this machine was a SMC EZCARD10 > (SMC1660BTA). It was recognized (after I changed it to irq 5 and > 0x300), but it could never sucessfully use it since I couldn't find > the right combination of link[0-2] options to make it choose > 10baseT/UTP (and I couldn't do it thru the "media" option). anyone > have one of these working with FreeBSD? (This card has 3 ports, BNC, > AUI and the UTP one). If this is an 'ed' family card, there are no link options because there's no standard for setting the media on these devices. If it doesn't automatically detect (and it probably ought to), you will have to set it with the DOS utility. -- \\ 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 12 18:14:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25414 for freebsd-current-outgoing; Mon, 12 Oct 1998 18:14:47 -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 SAA25402 for ; Mon, 12 Oct 1998 18:14:43 -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 SAA01131; Mon, 12 Oct 1998 18:17:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810130117.SAA01131@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Edwin Culp cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release In-reply-to: Your message of "Mon, 12 Oct 1998 19:39:21 CDT." <3622A139.833751BD@webwizard.org.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 18:17:44 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Due to a parity error in my memory:-) I forgot to remove my > KERNFORMAT=elf system variable before making release and much to my > surprise it made it through kernel creation. It looks like we will soon > be able to make a 100% elf release. Has anyone done it? How important > is it. Here's the result from my log before I redo it with an out > kernel, if anyone is interested. There's some (understandable) resistance to putting an ELF kernel in 3.0, so the changeover will probably happen a few weeks afterwards. At that stage we'll shift to the new bootloader as well. I don't expect that ELF kernels will be supported for 3.0-RELEASE, although you will be able to build and experiment with them. -- \\ 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 12 19:26:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07955 for freebsd-current-outgoing; Mon, 12 Oct 1998 19:26:00 -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 TAA07943 for ; Mon, 12 Oct 1998 19:25:48 -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 WAA06253; Mon, 12 Oct 1998 22:25:13 -0400 (EDT) (envelope-from wollman) Date: Mon, 12 Oct 1998 22:25:13 -0400 (EDT) From: Garrett Wollman Message-Id: <199810130225.WAA06253@khavrinen.lcs.mit.edu> To: Mark Murray Cc: Brad Hilton , current@FreeBSD.ORG Subject: Re: perl5 & gdbm In-Reply-To: <199810121951.VAA02992@gratis.grondar.za> References: <3622481D.2200E666@vpop.net> <199810121951.VAA02992@gratis.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> I am running 3.0-current as of 10/12/1998 (ELF), and have been unable to >> get perl5 to link against gdbm. > I was wondering when this was going to raise its ugly head :-) > I'll do my best; no promises. I would just advise users of p5-gdbm to get the GDBM_File module from CPAN and install it separately. -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 12 20:24:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15541 for freebsd-current-outgoing; Mon, 12 Oct 1998 20:24:18 -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 UAA15484 for ; Mon, 12 Oct 1998 20:24:09 -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 UAA16248 for ; Mon, 12 Oct 1998 20:24:07 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: current@FreeBSD.ORG Subject: ftp://current.freebsd.org/pub/FreeBSD/ Date: Mon, 12 Oct 1998 20:24:06 -0700 Message-ID: <16244.908249046@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is back up on a new machine and producing 3.0-BETA snapshots as usual. Just FYI! I won't be copying every snapshot from here to ftp.freebsd.org, so please return to your former habit of checking current.freebsd.org first. Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 21:05:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20347 for freebsd-current-outgoing; Mon, 12 Oct 1998 21:05:23 -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 VAA20342 for ; Mon, 12 Oct 1998 21:05:22 -0700 (PDT) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id VAA18347; Mon, 12 Oct 1998 21:05:08 -0700 (PDT) Date: Mon, 12 Oct 1998 21:05:08 -0700 (PDT) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199810130405.VAA18347@math.berkeley.edu> To: current@FreeBSD.ORG Subject: -current NFS problem Cc: dan@math.berkeley.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't reported this before because it is kind of hard to be very specific about the cause and because I am under the impression that people are aware of NFS problems in a general way. I am reporting this now necause I believe this to be very important and I haven't heard any discussion of this specific problem. There is some sort of NFS problem that causes processes to wedge in a high priority (i.e. non-interruptable) wait state. I encounter this problem whenever I use the ncftp2 program on a 3.0-SNAP or BETA system to make copy of a FreeBSD release in a remotely mounted file system. It doesn't happen immediately, but it always happens before the copy is complete. The ncftp2 program just stops reporting any progress and a ps shows it to be in a "disk" wait state. The ncftp2 program is normally not killable and attempts (on the 3.0-SNAP or BETA system) to examine the directory it was copying into also wedge in a "disk" wait state. Eventually the entire 3.0-SNAP or BETA system will wedge. I suspect the NFS problem, which initially is localized to one file or directory, cascades through the automounter. The NFS server, a sun workstation running Solaris 2.5, does not appear to be affected. The directory that is wedged on the 3.0-SNAP or BETA FreeBSD system is visible and behaves normally on the server even after the FreeBSD NFS client system locks up. The only (temporary) fix is to reboot the FreeBSD 3.0-SNAP or BETA system and restart the ncftp2 program where it left off. Eventually it will finish. I normally avoid the problem entirely by doing my FreeBSD release copies on a 2.2.7-RELEASE system which never hangs. Note: after a NFS wedge, I never find a partially written file. The wedge always seems to happen "between" files. Dan Strick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 21:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22541 for freebsd-current-outgoing; Mon, 12 Oct 1998 21:17:58 -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 VAA22535 for ; Mon, 12 Oct 1998 21:17:56 -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 VAA11918; Mon, 12 Oct 1998 21:16:23 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <3622D416.E2E627AC@gorean.org> Date: Mon, 12 Oct 1998 21:16:22 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1009 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith CC: Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release References: <199810130117.SAA01131@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: > There's some (understandable) resistance to putting an ELF kernel in > 3.0, so the changeover will probably happen a few weeks afterwards. At > that stage we'll shift to the new bootloader as well. I still think getting the pain over now is a good idea. Leaving a major change for after the "release" will just postpone by one more quarter the time when 3.0 has a chance of being stable. 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 12 21:30:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24296 for freebsd-current-outgoing; Mon, 12 Oct 1998 21:30:13 -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 VAA24291 for ; Mon, 12 Oct 1998 21:30:10 -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 OAA05137; Tue, 13 Oct 1998 14:29:49 +1000 Date: Tue, 13 Oct 1998 14:29:49 +1000 From: Bruce Evans Message-Id: <199810130429.OAA05137@godzilla.zeta.org.au> To: bde@zeta.org.au, seggers@semyam.dinoco.de Subject: Re: bitten 3 times already. Cc: bright@hotjobs.com, current@FreeBSD.ORG, zach@gaffaneys.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Dumps and LBA mode should't be mixed, since the dump routine doesn't >> support LBA mode and it uses CHS mode with nominal geometry if LBA mode > >Why is this so? I don't see why it shouldn't use LBA, too if LBA is >on for the drive. That it doesn't support that now seems pretty easy >to fix to me. Just change the way it calculates the numbers and that's >it as far as I can see from my docs and what wd does. Because no one implemented it, and there is not much point in implementing LBA mode in any part of the driver until there is a drive that doesn't support CHS mode. 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 12 21:38:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25256 for freebsd-current-outgoing; Mon, 12 Oct 1998 21:38:08 -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 VAA25251 for ; Mon, 12 Oct 1998 21:38:04 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id OAA02736; Tue, 13 Oct 1998 14:41:31 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810130441.OAA02736@cimlogic.com.au> Subject: Re: gnu/usr.bin/cc/cc_tools/Makefile bug? (was Re: filesystem safety and SCSI disk write caching) In-Reply-To: <199810122109.OAA12095@salsa.gv.tsc.tdk.com> from Don Lewis at "Oct 12, 98 02:09:53 pm" To: Don.Lewis@tsc.tdk.com (Don Lewis) Date: Tue, 13 Oct 1998 14:41:31 +1000 (EST) Cc: 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 Don Lewis wrote: > ${COMMONHDRS}: > echo '#include "${MACHINE_ARCH}/freebsd.h"' > tm.h > echo '#include "${MACHINE_ARCH}/xm-freebsd.h"' > config.h > echo '#include "${MACHINE_ARCH}/xm-freebsd.h"' > hconfig.h > echo '#include "${MACHINE_ARCH}/xm-freebsd.h"' > tconfig.h > echo '#include "cp/lang-options.h"' > options.h > echo '#include "cp/lang-specs.h"' > specs.h > echo '#include "f2c-specs.h"' >> specs.h > > GENSRCS+= ${COMMONHDRS} > > > It sure looks like if you do a parallel make, these .h files get built > in parallel multiple times. Most of the time we appear to get lucky > and they happen to come out correct. If we don't want to rely on luck, > then this Makefile should have a separate rule for each of these .h files. Can this wait until the possible/probable (?) compiler upgrade after 3.0? -- 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 12 22:20:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02063 for freebsd-current-outgoing; Mon, 12 Oct 1998 22:20:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01835 for ; Mon, 12 Oct 1998 22:19:53 -0700 (PDT) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id OAA06990; Tue, 13 Oct 1998 14:19:36 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98021914) with ESMTP id OAA16223; Tue, 13 Oct 1998 14:19:35 +0900 (JST) Message-Id: <199810130519.OAA16223@hotaka.csl.sony.co.jp> To: Brian Somers cc: current@FreeBSD.ORG Subject: Re: Improper sharing of modem bandwidth In-reply-to: Your message of "Mon, 12 Oct 1998 11:21:06 +0100." <199810121021.LAA00663@woof.lan.awfulhak.org> Date: Tue, 13 Oct 1998 14:19:34 +0900 From: Kenjiro Cho Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian, Thanks for your input. > How hard do you think it is to add the following feature to the > userland ppp? > [snip] >> This is all quite plausible, but with a couple of caveats, both of >> which, after a cursory glance at the above pages, I didn't see >> included. >> The first problem is the tty buffer. Ppp, when passed a fragment, >> will (usually) attempt to write the whole thing to a non-blocking tty. >> The tty will already have reported (via select()) that it's writable. >> Short writes will be continued the next time the descriptor tells >> select() it's writable. This phenomena is likely to affect latency >> calculations - the bigger the tty buffer, the greater the latency >> would be - despite suspend/resume. I don't know if a kernel >> implementation would have any more control over this sort of thing >> though, and this isn't a show-stopper by any means. Surely, once the packet queueing delay is reduced, we need to reduce the tty delay. The current kernel doesn't have ioctls for the buffer size but slip uses a smaller tty buffer and has a better response time than ppp. When I was playing with ppp back in May, I used a smaller tty buffer and a smaller sio buffer, and found it helpful. (the code is available from http://www.csl.sony.co.jp/person/kjc/kjc/software.html#altq4ppp) >> The second problem is that a packet/fragment must be compressed (if >> (link level) CCP has been negotiated) prior to transmission. Any >> traffic that wants to be sent during the transmission of a compressed >> fragment must either >> a) be sent uncompressed >> b) be sent compressed using a different dictionary >> c) wait for the rest of the interrupted packet on the remote end so >> that the remote can decompress in the correct order. >> a) Problems may arise for the server->client traffic as it may >> increase to a point where we're better off avoiding the >> suspend/resume altogether. Even the client->server traffic may >> cause problems as VJ compression would become difficult to >> implement. Maybe a way out would be to insist that only >> VJ-compressed (if VJ was negotiated) packets may cause a >> suspend/resume - but this may cause even more problems on a ppp >> implementation that doesn't update its VJ slots 'till *after* a >> packet has been received (rather than doing so as soon as it >> receives the new TCP/IP header). >> b) Treating interactive & non-interactive traffic as two completely >> separate streams would be quite clean. VJ and CCP would need to >> duplicate their slots/dictionaries - one interactive and one >> non-interactive set. >> c) This option is useless - it shows why we'd need to do either a) or >> b). >> Having said all that, I've talked myself into b) being a good method. >> The memory overhead isn't outrageous, the duplicated dictionaries will >> have no adverse effect AFAICT, and it will work for both uni and >> multi-link mode. I don't know much about this area but it seems to me that approach b) is reasonable and doable. >> I wonder if it would be necessary to allow interactive-fragment VJ >> and CCP options - ie, someone wants VJ and no CCP for interactive >> traffic, but CCP and no VJ for non-interactive traffic. This might >> improve interactive latency further. Isn't the sender allowed to switch encoding according to the priority and packet size? Anyway, this improvement seems to have a much smaller impact on the total performance. --Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 22:41:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04925 for freebsd-current-outgoing; Mon, 12 Oct 1998 22:41:40 -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 WAA04916 for ; Mon, 12 Oct 1998 22:41:36 -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 PAA12787; Tue, 13 Oct 1998 15:41:01 +1000 Date: Tue, 13 Oct 1998 15:41:01 +1000 From: Bruce Evans Message-Id: <199810130541.PAA12787@godzilla.zeta.org.au> To: brian@Awfulhak.org, kjc@csl.sony.co.jp Subject: Re: Improper sharing of modem bandwidth Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Surely, once the packet queueing delay is reduced, we need to reduce >the tty delay. The current kernel doesn't have ioctls for the >buffer size but slip uses a smaller tty buffer and has a better >response time than ppp. User ppp is behind a _lot_ of output buffering, including (at speeds >= 57600 Kbps) a 4KB tty buffer (up from 2KB in FreeBSD-2.2). Perhaps the increase from 2KB to 4KB is especially significant when the MTU is 1500. Kernel ppp doesn't have this problem. Kernel ppp also has a fast path for incoming packets to avoid the average 5ms latency for polling the pseudo-DMA input buffer. This only seems to be important for local connections. 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 12 22:41:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05007 for freebsd-current-outgoing; Mon, 12 Oct 1998 22:41:59 -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 WAA05002 for ; Mon, 12 Oct 1998 22:41:57 -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 AAA28463 for ; Tue, 13 Oct 1998 00:41:45 -0500 (CDT) X-Authentication-Warning: eesn17.ews.uiuc.edu: ramasubr owned process doing -bs Date: Tue, 13 Oct 1998 00:41:44 -0500 (CDT) From: Vijay Ramasubramanian To: freebsd-current@FreeBSD.ORG Subject: Installation probs w/3.0-BETA 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. I am trying to install the 3.0-19981009-BETA release. Here is my hardware configuration: AMD K6-233 (one of the latest revisions) Intel TX chipset motherboard w/512KB cache 64 MB SDRAM 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 I have a dedicated internet connection via the ethernet. I have tried and failed many times to get this installed on the computer. At first, the way I partitioned and labeled the drives for installation is as follows: Drive 0 (IBM 2.2 GB): 400MB FAT16 (Windows 95 resides here) Remainder FreeBSD FS, mount at: / Leave MBR alone (I had planned on installing System Commander later) Drive 1 (IBM 2.2 GB): Dedicated FreeBSD FS, mount at: /home Drive 2 (Fujitsu 405 MB): Dedicated FreeBSD 202 MB SWAP 202 MB FreeBSD FS, mount at: /scratch I had planned to run the /var and /usr directories off the root FS partition. At boot-time, I configure the kernel and disable all devices that I don't have (including ISA ethernet and SCSI cards, etc). Once I get the installation via FTP started (from ftp.freebsd.org), it progresses to 34% and then crashes. The progress bar reads "Extracting bin into / directory..." The stats bar at the bottom reads: "9438208 bytes read from bin dist, chunk 40 of 116 @ 13.4kB/sec" The error messages are as follows: Panic: ufs_dirbad: bad dir Syncing disks... 143 143 143 70 40 1 1 1 1 1 1 1 1 1 1 1 1 giving up (da2:adv0:0:2:0): . CDB: 35 0 0 0 0 0 0 0 0 0 (da2:adv0:0:2:0): ILLEGAL REQUEST asc: 20,0 (da2:adv0:0:2:0): And then of course, the automatic reboot stuff, etc. It seemed that it was having problems with SCSI device 2, which is the Fujitsu drive. I scanned the drive for bad sectors with Norton Utils and SpinRite (there weren't any). I have also used the disk heavily under Windows 95 and NT and there have been no problems with it. Thus I don't know why it would have problems with the Fujitsu. So, I tried yanking the Fujitsu and just installing the / FS to the 1st IBM drive, and putting Swap on the 2nd drive. The installation then died at 35% with the message: Panic: ffs_alloccg : bad map This may not be exactly the error message (the part after ffs_alloccg) as the machine rebooted before I could get of the info, and I have no desire to try a 15th installation attempt to get the message again. The hardware has been run under 95 so far without any problems, although most people would probably say that running under 95 is not much of a test of hardware. Can anyone tell me how to go about getting this resolved? If you think it may be bad hardware, can you suggest diagnostic-type programs that I can test with? I have relatively limited hardware resources, and can't do stuff like swapping out the CPU, RAM, etc. 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 12 23:12:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07659 for freebsd-current-outgoing; Mon, 12 Oct 1998 23:12:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07654 for ; Mon, 12 Oct 1998 23:12:56 -0700 (PDT) (envelope-from c5666305@b1.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by smtp.hkstar.com (8.8.8/8.8.4) with ESMTP id OAA26400 for ; Tue, 13 Oct 1998 14:12:42 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8/8.8.8) id OAA11017 for current@FreeBSD.org; Tue, 13 Oct 1998 14:14:38 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199810130614.OAA11017@b1.hkstar.com> Subject: does FreeBSD support DE660 PCMCIA card (DLink) To: current@FreeBSD.ORG Date: Tue, 13 Oct 1998 14:14:38 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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, This is a little of off topic. I would like to know if freebsd suports de660 PCMCIA card (Dlink). Please share your experience with me. Thanks. Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 23:16:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07955 for freebsd-current-outgoing; Mon, 12 Oct 1998 23:16: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 XAA07950 for ; Mon, 12 Oct 1998 23:16: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 CAA14067; Tue, 13 Oct 1998 02:17:36 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Tue, 13 Oct 1998 02:17:35 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Dan Strick cc: current@FreeBSD.ORG Subject: Re: -current NFS problem In-Reply-To: <199810130405.VAA18347@math.berkeley.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 this has been a problem for me sorta, if you are using UDP mounts to solaris boxen and seeing this try using tcp mounts instead. solaris _should_ allow that. you might want to try these options: tcp,nfsv3,intr,bg,rw in your /etc/fstab file or to your -o options then again i'm still having pine knock my system for a loop recently while deleting mail. so maybe, nfsv2 for mail and nfsv3 for ftp? 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, 12 Oct 1998, Dan Strick wrote: > I haven't reported this before because it is kind of hard to be > very specific about the cause and because I am under the impression > that people are aware of NFS problems in a general way. I am reporting > this now necause I believe this to be very important and I haven't > heard any discussion of this specific problem. > > There is some sort of NFS problem that causes processes to wedge > in a high priority (i.e. non-interruptable) wait state. I encounter > this problem whenever I use the ncftp2 program on a 3.0-SNAP or BETA > system to make copy of a FreeBSD release in a remotely mounted file > system. It doesn't happen immediately, but it always happens before > the copy is complete. The ncftp2 program just stops reporting any > progress and a ps shows it to be in a "disk" wait state. The ncftp2 > program is normally not killable and attempts (on the 3.0-SNAP or BETA > system) to examine the directory it was copying into also wedge in a > "disk" wait state. Eventually the entire 3.0-SNAP or BETA system > will wedge. I suspect the NFS problem, which initially is localized > to one file or directory, cascades through the automounter. > > The NFS server, a sun workstation running Solaris 2.5, does not > appear to be affected. The directory that is wedged on the > 3.0-SNAP or BETA FreeBSD system is visible and behaves normally > on the server even after the FreeBSD NFS client system locks up. > > The only (temporary) fix is to reboot the FreeBSD 3.0-SNAP or BETA > system and restart the ncftp2 program where it left off. Eventually > it will finish. I normally avoid the problem entirely by doing > my FreeBSD release copies on a 2.2.7-RELEASE system which never > hangs. > > Note: after a NFS wedge, I never find a partially written file. > The wedge always seems to happen "between" files. > > Dan Strick > > 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 12 23:19:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08145 for freebsd-current-outgoing; Mon, 12 Oct 1998 23:19:22 -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 XAA08138 for ; Mon, 12 Oct 1998 23:19:15 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:gTBEnD49PR9iNoBYYwHnbcXVXxWYw/Al@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA05487; Tue, 13 Oct 1998 08:15:56 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810130615.IAA05487@gratis.grondar.za> To: Garrett Wollman cc: Brad Hilton , current@FreeBSD.ORG Subject: Re: perl5 & gdbm In-Reply-To: Your message of " Mon, 12 Oct 1998 22:25:13 -0400." <199810130225.WAA06253@khavrinen.lcs.mit.edu> References: <3622481D.2200E666@vpop.net> <199810121951.VAA02992@gratis.grondar.za> <199810130225.WAA06253@khavrinen.lcs.mit.edu> Date: Tue, 13 Oct 1998 08:15:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > I would just advise users of p5-gdbm to get the GDBM_File module from > CPAN and install it separately. I was thinking of making the gdbm port use GDBM_File if >= 3.0. Your idea sounds more sane, though... 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 12 23:21:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08424 for freebsd-current-outgoing; Mon, 12 Oct 1998 23:21:16 -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 XAA08416 for ; Mon, 12 Oct 1998 23:21:11 -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 IAA14536 for current@FreeBSD.ORG; Tue, 13 Oct 1998 08:20:56 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 71F661526; Tue, 13 Oct 1998 08:16:05 +0200 (CEST) Date: Tue, 13 Oct 1998 08:16:05 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: ftp://current.freebsd.org/pub/FreeBSD/ Message-ID: <19981013081605.A11390@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <16244.908249046@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: <16244.908249046@time.cdrom.com>; from Jordan K. Hubbard on Mon, Oct 12, 1998 at 08:24:06PM -0700 X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4722 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > Is back up on a new machine and producing 3.0-BETA snapshots > as usual. Just FYI! I won't be copying every snapshot from > here to ftp.freebsd.org, so please return to your former habit > of checking current.freebsd.org first. Thanks! Am I the only one to have problem with "make world" in the old boot blocks? $Id: Makefile,v 1.220 1998/09/29 22:03:12 jkh Exp $ $Id: Makefile.inc0,v 1.10 1998/09/29 22:03:13 jkh Exp $ $Id: Makefile.inc1,v 1.32 1998/10/11 19:02:27 rnordier Exp $ $Id: Makefile.upgrade,v 1.6 1998/09/23 01:46:25 jb Exp $ I need to set OBJFORMAT=aout before making anything inside "/sys/i386/boot". Sources from cvs-cur CTM_BEGIN 2.0 cvs-cur 4722 1998/10/12 15:14:42 . -=-=- cc -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mno-486 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 -DDO_BAD144 -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -nostdinc -I/src/src/sys/i386/boot/biosboot/../../../../include -I/src/src/sys/i386/boot/biosboot/../../.. -I/usr/obj/aout/src/src/sys/i386/boot/biosboot -I/usr/obj/aout/src/src/tmp/usr/include -N -T 0 -nostdlib -static -o boot start.o table.o boot2.o boot.o asm.o bios.o serial.o probe_keyboard.o io.o disk.o sys.o /usr/obj/elf/src/src/tmp/usr/libexec/aout/ld: start.o: malformed input file (not rel or archive) *** Error code 1 Stop. -=-=- -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-BETA #2: Sat Oct 3 11:34:55 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 12 23:51:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10614 for freebsd-current-outgoing; Mon, 12 Oct 1998 23:51:22 -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 XAA10607 for ; Mon, 12 Oct 1998 23:51:21 -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 XAA23054; Mon, 12 Oct 1998 23:50:59 -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 XAA02105; Mon, 12 Oct 1998 23:50:58 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id XAA14754; Mon, 12 Oct 1998 23:50:57 -0700 (PDT) From: Don Lewis Message-Id: <199810130650.XAA14754@salsa.gv.tsc.tdk.com> Date: Mon, 12 Oct 1998 23:50:56 -0700 In-Reply-To: John Birrell "Re: gnu/usr.bin/cc/cc_tools/Makefile bug? (was Re: filesystem safety and SCSI disk write caching)" (Oct 13, 2:41pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: John Birrell , Don.Lewis@tsc.tdk.com (Don Lewis) 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 13, 2:41pm, John Birrell wrote: } Subject: Re: gnu/usr.bin/cc/cc_tools/Makefile bug? (was Re: filesystem saf } Don Lewis wrote: } > } > It sure looks like if you do a parallel make, these .h files get built } > in parallel multiple times. Most of the time we appear to get lucky } > and they happen to come out correct. If we don't want to rely on luck, } > then this Makefile should have a separate rule for each of these .h files. } } Can this wait until the possible/probable (?) compiler upgrade after 3.0? Probably, though a caution sign should probably be posted until it is fixed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 00:14:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12127 for freebsd-current-outgoing; Tue, 13 Oct 1998 00:14:06 -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 AAA12122 for ; Tue, 13 Oct 1998 00:14:03 -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 RAA21592; Tue, 13 Oct 1998 17:13:46 +1000 Date: Tue, 13 Oct 1998 17:13:46 +1000 From: Bruce Evans Message-Id: <199810130713.RAA21592@godzilla.zeta.org.au> To: Don.Lewis@tsc.tdk.com, jb@cimlogic.com.au 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 >} > and they happen to come out correct. If we don't want to rely on luck, >} > then this Makefile should have a separate rule for each of these .h files. >} >} Can this wait until the possible/probable (?) compiler upgrade after 3.0? > >Probably, though a caution sign should probably be posted until it is >fixed. It's easier to just fix it. Splitting the rules is obviously safe since it is essentially a no-op for -j1. 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. 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 13 01:08:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18102 for freebsd-current-outgoing; Tue, 13 Oct 1998 01:08:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18092 for ; Tue, 13 Oct 1998 01:08:22 -0700 (PDT) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id RAA08973; Tue, 13 Oct 1998 17:07:54 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98021914) with ESMTP id RAA11582; Tue, 13 Oct 1998 17:07:53 +0900 (JST) Message-Id: <199810130807.RAA11582@hotaka.csl.sony.co.jp> To: Bruce Evans cc: brian@Awfulhak.org, current@FreeBSD.ORG Subject: Re: Improper sharing of modem bandwidth In-reply-to: Your message of "Tue, 13 Oct 1998 15:41:01 +1000." <199810130541.PAA12787@godzilla.zeta.org.au> Date: Tue, 13 Oct 1998 17:07:52 +0900 From: Kenjiro Cho Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans said: > Surely, once the packet queueing delay is reduced, we need to reduce > the tty delay. The current kernel doesn't have ioctls for the > buffer size but slip uses a smaller tty buffer and has a better > response time than ppp. >> User ppp is behind a _lot_ of output buffering, including (at speeds >= >> 57600 Kbps) a 4KB tty buffer (up from 2KB in FreeBSD-2.2). Perhaps the >> increase from 2KB to 4KB is especially significant when the MTU is 1500. Hmmm, when I tried, user ppp on a 200MHz PentiumPro apparently had no problem filling up 2x 57600bps with small (~100) output buffers. However, I monitored the throughput inside the ppp program and didn't directly observe the kernel buffers. --Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 01:16:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19400 for freebsd-current-outgoing; Tue, 13 Oct 1998 01:16:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from poboxer.pobox.com (port17.prairietech.net [208.141.230.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19391; Tue, 13 Oct 1998 01:16:09 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.1/8.7.3) id DAA08359; Tue, 13 Oct 1998 03:15:07 -0500 (CDT) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 13 Oct 1998 03:15:06 -0500 (CDT) X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: eivind@yes.no Cc: current@FreeBSD.ORG, dg@FreeBSD.ORG Subject: Re: inetd is ill? syslogd is anemic? References: <13854.19308.314677.685227@avalon.east> <199810092335.TAA25121@khavrinen.lcs.mit.edu> <13854.56585.707371.316487@avalon.east> <19981010200607.56951@follo.net> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13859.2587.145715.385630@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Eivind Eklund on Sat, 10 October: : This is a known, OLD bug. It was one of the bugs introduced or : exposed by John Dysons changes to the VM system. He was working on : this at the time he left, if I understood correctly. Thanks. I can confirm that you have correctly diagnosed the problem, in as much as killing and restarting inetd stopped it from happenning to inetd -- the disease moved on to syslogd. Similarly, restarting syslogd fixed that, and a few hours later it moved on to sendmail. Restarting sendmail has kept it away for the past hour or two. : My machine is a PPro-based box - I don't know if this matter. I seem : to remember it also happening after I upgraded to 80MB; I know it : happened when I had 64MB, at least. Mine is dual PPro 64MB as well, so this config is likely to make it easier to reproduce. Meanwhile, I think I'll upgrade my memory (as Garrett Wollman suggested) after all, and see if it goes away -- although like as not a kernel update and recompile will suffice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 01:16:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19563 for freebsd-current-outgoing; Tue, 13 Oct 1998 01:16:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp4.nwnexus.com (smtp4.nwnexus.com [206.63.63.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19556 for ; Tue, 13 Oct 1998 01:16:55 -0700 (PDT) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx100-ip24.nwnexus.net [204.57.235.24]) by smtp4.nwnexus.com (8.8.8/8.8.8) with ESMTP id BAA30905; Tue, 13 Oct 1998 01:16:40 -0700 (PDT) Received: (from wrsomsky@localhost) by gramarye (8.9.1/8.8.8) id BAA00812; Tue, 13 Oct 1998 01:14:11 -0700 (PDT) (envelope-from wrsomsky) Message-ID: <19981013011411.A690@halcyon.com> Date: Tue, 13 Oct 1998 01:14:11 -0700 From: "William R. Somsky" To: "Kenneth D. Merry" , Alex Cc: perlsta@fs3.ny.genx.net, current@FreeBSD.ORG Subject: Re: /usr/include/sys/cam/scsi... References: <199810102228.QAA08330@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810102228.QAA08330@panzer.plutotech.com>; from Kenneth D. Merry on Sat, Oct 10, 1998 at 04:28:11PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 10, 1998 at 04:28:11PM -0600, Kenneth D. Merry wrote: > Alex wrote... > > On Sat, 10 Oct 1998, Alfred wrote: > > [..] > > > a lot of applications broke during compile just because of the renameing. > > > when the scsi.h was replaced by cam/scsi_all.h it compiled and worked, > > > notably kscd (the kde CD player) > > > > This kinda piqued my interest, I've been cvsuping and making world, but > > I'm still left with a scsi.h, and a bunch of header files in /usr/include > > with old datestamps. How can I tell what files should have been cleaned > > out? > > Probably just watch the commits and see which files get removed. Someone > probably has a script to do this.. Well, I'm sure there's probably a better answer, but what I've been doing is, in addition to doing a normal "make installworld", installing a "parallel world" in something like /home/newworld -- similar to what is suggested for /usr/src/etc to merge the /etc changes -- and then comparing the two trees to see if there is any file that shold be deleted -- modulo, of course, /usr/local, and anything I've added. ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 01:54:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24657 for freebsd-current-outgoing; Tue, 13 Oct 1998 01:54:33 -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 BAA24647 for ; Tue, 13 Oct 1998 01:54:30 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 29166 invoked by uid 1001); 13 Oct 1998 08:54:16 +0000 (GMT) To: bde@zeta.org.au Cc: bright@hotjobs.com, current@FreeBSD.ORG, zach@gaffaneys.com Subject: Re: bitten 3 times already. In-Reply-To: Your message of "Tue, 13 Oct 1998 14:29:49 +1000" References: <199810130429.OAA05137@godzilla.zeta.org.au> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 13 Oct 1998 10:54:16 +0200 Message-ID: <29164.908268856@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Dumps and LBA mode should't be mixed, since the dump routine doesn't > >> support LBA mode and it uses CHS mode with nominal geometry if LBA mode > > > >Why is this so? I don't see why it shouldn't use LBA, too if LBA is > >on for the drive. That it doesn't support that now seems pretty easy > >to fix to me. Just change the way it calculates the numbers and that's > >it as far as I can see from my docs and what wd does. > > Because no one implemented it, and there is not much point in implementing > LBA mode in any part of the driver until there is a drive that doesn't > support CHS mode. If dumps and LBA mode shouldn't be used together, it would be useful to have a warning about that somewhere, since a lot of BIOSes seem to want to use LBA as default for newer big IDE disks. Below is a suggested patch to the dumpon.8 manual page to include such a warning. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- *** sbin/dumpon/dumpon.8.orig Mon Aug 31 18:41:06 1998 --- sbin/dumpon/dumpon.8 Tue Oct 13 10:50:46 1998 *************** *** 116,121 **** --- 116,124 ---- Because the filesystem layer is already dead by the time a crash dump is taken, it is not possible to send crash dumps directly to a file. .Pp + The kernel crash dump is written using CHS addressing. Kernel crash + dumps should not be enabled for disks running in LBA mode. + .Pp .Nm Dumpon currently allows only devices with minor number 1 to be used as dump devices. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 02:23:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27669 for freebsd-current-outgoing; Tue, 13 Oct 1998 02:23:20 -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 CAA27662 for ; Tue, 13 Oct 1998 02:23:17 -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 TAA31384; Tue, 13 Oct 1998 19:22:57 +1000 Date: Tue, 13 Oct 1998 19:22:57 +1000 From: Bruce Evans Message-Id: <199810130922.TAA31384@godzilla.zeta.org.au> To: bde@zeta.org.au, sthaug@nethelp.no Subject: Re: bitten 3 times already. Cc: bright@hotjobs.com, current@FreeBSD.ORG, zach@gaffaneys.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >If dumps and LBA mode shouldn't be used together, it would be useful to >have a warning about that somewhere, since a lot of BIOSes seem to want >to use LBA as default for newer big IDE disks. This doesn't follow, since the driver's use of LBA has nothing to do with the BIOS's use of LBA. The driver should simply not use LBA (as in 2.2). 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 13 02:32:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28602 for freebsd-current-outgoing; Tue, 13 Oct 1998 02:32:10 -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 CAA28591 for ; Tue, 13 Oct 1998 02:32:06 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id LAA07720; Tue, 13 Oct 1998 11:31:38 +0200 (CEST) (envelope-from sos) Message-Id: <199810130931.LAA07720@sos.freebsd.dk> Subject: Re: bitten 3 times already. In-Reply-To: <199810130922.TAA31384@godzilla.zeta.org.au> from Bruce Evans at "Oct 13, 98 07:22:57 pm" To: bde@zeta.org.au (Bruce Evans) Date: Tue, 13 Oct 1998 11:31:38 +0200 (CEST) Cc: bde@zeta.org.au, sthaug@nethelp.no, bright@hotjobs.com, current@FreeBSD.ORG, zach@gaffaneys.com 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 Bruce Evans who wrote: > >If dumps and LBA mode shouldn't be used together, it would be useful to > >have a warning about that somewhere, since a lot of BIOSes seem to want > >to use LBA as default for newer big IDE disks. > > This doesn't follow, since the driver's use of LBA has nothing to do > with the BIOS's use of LBA. The driver should simply not use LBA (as > in 2.2). Exactly, maybe I should remove the LBA support in current, there is no use for it actually, just the change needed to use >8G drives (like I did it in 2.2.7+).. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Tue Oct 13 02:34:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29077 for freebsd-current-outgoing; Tue, 13 Oct 1998 02:34:16 -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 CAA28938 for ; Tue, 13 Oct 1998 02:33:49 -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 RAA29497; Tue, 13 Oct 1998 17:03:26 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810130903.RAA29497@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release In-reply-to: Your message of "Mon, 12 Oct 1998 18:17:44 MST." <199810130117.SAA01131@dingo.cdrom.com> Date: Tue, 13 Oct 1998 17:03:25 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Due to a parity error in my memory:-) I forgot to remove my > > KERNFORMAT=elf system variable before making release and much to my > > surprise it made it through kernel creation. It looks like we will soon > > be able to make a 100% elf release. Has anyone done it? How important > > is it. Here's the result from my log before I redo it with an out > > kernel, if anyone is interested. > > There's some (understandable) resistance to putting an ELF kernel in > 3.0, so the changeover will probably happen a few weeks afterwards. At > that stage we'll shift to the new bootloader as well. > > I don't expect that ELF kernels will be supported for 3.0-RELEASE, > although you will be able to build and experiment with them. ELF kernels have been fully functional for about a week. LKM's don't work with ELF though, you have to use kldload instead of modload, and that's not cooked enough yet. For example, you can't load a VFS (eg the nfs module) via kldload yet. Or, more to the point, you can load it but it has no way to attach itself to the VFS switch. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 02:40:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29921 for freebsd-current-outgoing; Tue, 13 Oct 1998 02:40:45 -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 CAA29755 for ; Tue, 13 Oct 1998 02:40:01 -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 RAA29552; Tue, 13 Oct 1998 17:09:31 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810130909.RAA29552@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Studded cc: Mike Smith , Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release In-reply-to: Your message of "Mon, 12 Oct 1998 21:16:22 MST." <3622D416.E2E627AC@gorean.org> Date: Tue, 13 Oct 1998 17:09:30 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Studded wrote: > Mike Smith wrote: > > > There's some (understandable) resistance to putting an ELF kernel in > > 3.0, so the changeover will probably happen a few weeks afterwards. At > > that stage we'll shift to the new bootloader as well. > > I still think getting the pain over now is a good idea. Leaving a major > change for after the "release" will just postpone by one more quarter > the time when 3.0 has a chance of being stable. Unfortunately, I agree, in part at least. The biggest difficulty in doing a changeover is upgrading the stage2 bootblocks. If we get the 3.0 CD installing ELF-capable bootblocks (even if it's a hacked biosboot), then it's going to make the transition *so* much easier. It's not a question of flipping a switch, we've got to get the bootblocks upgraded. If we could get the 3.0 release sysinstall to do this for us it would be a big win. Ideally there should be a choice in sysinstall, and sysinstall could change them on the fly. If somebody installed a system and the new bootblocks didn't work, it'd be nice if it was as simple as booting the floppy and downgrading to the older system. IMHO, whether /kernel is a.out or elf is far less of an issue than which bootblocks we use. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 03:02:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03225 for freebsd-current-outgoing; Tue, 13 Oct 1998 03:02:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03220 for ; Tue, 13 Oct 1998 03:02:22 -0700 (PDT) (envelope-from c5666305@b1.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by smtp.hkstar.com (8.8.8/8.8.4) with ESMTP id SAA24413 for ; Tue, 13 Oct 1998 18:02:08 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8/8.8.8) id SAA24511 for current@freebsd.org; Tue, 13 Oct 1998 18:04:05 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199810131004.SAA24511@b1.hkstar.com> Subject: How to config pcmcia network adapter for laptop To: current@FreeBSD.ORG Date: Tue, 13 Oct 1998 18:04:05 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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, Sorry for cross post as I cannot subscribe freebsd-mobile after several trials. I am newbie to use laptop using FreeBSD and I want to config the pcmcia network adapter de660 (D-Link) for my laptop. Can anyone show me the steps. cheers. Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 03:49:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07325 for freebsd-current-outgoing; Tue, 13 Oct 1998 03:49:11 -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 DAA07318; Tue, 13 Oct 1998 03:49:05 -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 MAA29466; Tue, 13 Oct 1998 12:48:48 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA17917; Tue, 13 Oct 1998 12:48:45 +0200 (MET DST) Message-ID: <19981013124845.25955@follo.net> Date: Tue, 13 Oct 1998 12:48:45 +0200 From: Eivind Eklund To: alk@pobox.com Cc: current@FreeBSD.ORG, dg@FreeBSD.ORG Subject: Re: inetd is ill? syslogd is anemic? References: <13854.19308.314677.685227@avalon.east> <199810092335.TAA25121@khavrinen.lcs.mit.edu> <13854.56585.707371.316487@avalon.east> <19981010200607.56951@follo.net> <13859.2587.145715.385630@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <13859.2587.145715.385630@avalon.east>; from Tony Kimball on Tue, Oct 13, 1998 at 03:15:06AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 13, 1998 at 03:15:06AM -0500, Tony Kimball wrote: > Quoth Eivind Eklund on Sat, 10 October: > : This is a known, OLD bug. It was one of the bugs introduced or > : exposed by John Dysons changes to the VM system. He was working on > : this at the time he left, if I understood correctly. > > Thanks. I can confirm that you have correctly diagnosed the problem, > in as much as killing and restarting inetd stopped it from happenning > to inetd -- the disease moved on to syslogd. Similarly, restarting > syslogd fixed that, and a few hours later it moved on to sendmail. > Restarting sendmail has kept it away for the past hour or two. Check out what is eating your memory. Likely a restart of X will free up enough memory that it won't re-occur for a long time - netscape tend to make X leak (in what may be an interaction with the VM system, possibly through vfork()). > : My machine is a PPro-based box - I don't know if this matter. I seem > : to remember it also happening after I upgraded to 80MB; I know it > : happened when I had 64MB, at least. > > Mine is dual PPro 64MB as well, so this config is likely to make it > easier to reproduce. Meanwhile, I think I'll upgrade my memory > (as Garrett Wollman suggested) after all, and see if it goes away -- > although like as not a kernel update and recompile will suffice. I've not seen any commits that should fix it, and I've been on the lookout for them. 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 13 03:49:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07403 for freebsd-current-outgoing; Tue, 13 Oct 1998 03:49:18 -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 DAA07394 for ; Tue, 13 Oct 1998 03:49:15 -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 MAA15935; Tue, 13 Oct 1998 12:54:05 +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 NAA18504; Tue, 13 Oct 1998 13:08:25 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id NAA20958; Tue, 13 Oct 1998 13:01:06 +0200 (CEST) Message-ID: <19981013130106.43997@deepo.prosa.dk> Date: Tue, 13 Oct 1998 13:01:06 +0200 From: Philippe Regnauld To: "Kenneth D. Merry" , gibbs@plutotech.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-19981009-BETA + 2840 AHA + camcontrol stop/start = panic References: <19981012194716.53997@deepo.prosa.dk> <199810121846.MAA25828@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88e In-Reply-To: <199810121846.MAA25828@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Oct 12, 1998 at 12:46:10PM -0600 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 Kenneth D. Merry writes: > > Unless you can provide a stack trace, or at least the functions around the > given instruction pointer, there's no way to know where the panic is. 1st panic: (i.p. = 0xf010553d) nm.aout /kernel | sort ... f0105448 T _xpt_done <---> f01055b4 T _xpt_alloc_ccb ... 2nd panic: (i.p. = 0xf014a92f) ... f014a914 T _tsleep <---> f014ab6c t _endtsleep ... > Try setting up a serial console and DDB so you can get a stack trace. Ok, but onФy because it's you ;-) panic-on-demand (with DDB): [doing start/stop stuff]: panic: biodone: buffer not busy - trace: _biodone at _biodone+0x24 _dadone at _dadone+0x23d _camisr at _damisr+0x1fb _swi_cambio at _swi_cambio+0xd doreti_swi() at doreti_swi+0xf (machine still in DDB -- anything more precise ? I don't have a serial cross cable right now). -- -[ 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 Tue Oct 13 03:54:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07780 for freebsd-current-outgoing; Tue, 13 Oct 1998 03:54: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 DAA07770 for ; Tue, 13 Oct 1998 03:54:49 -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 DAA12263; Tue, 13 Oct 1998 03:52:55 -0700 (PDT) Message-Id: <199810131052.DAA12263@implode.root.com> To: Eivind Eklund cc: alk@pobox.com, current@FreeBSD.ORG Subject: Re: inetd is ill? syslogd is anemic? In-reply-to: Your message of "Tue, 13 Oct 1998 12:48:45 +0200." <19981013124845.25955@follo.net> From: David Greenman Reply-To: dg@root.com Date: Tue, 13 Oct 1998 03:52:55 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> : My machine is a PPro-based box - I don't know if this matter. I seem >> : to remember it also happening after I upgraded to 80MB; I know it >> : happened when I had 64MB, at least. >> >> Mine is dual PPro 64MB as well, so this config is likely to make it >> easier to reproduce. Meanwhile, I think I'll upgrade my memory >> (as Garrett Wollman suggested) after all, and see if it goes away -- >> although like as not a kernel update and recompile will suffice. > >I've not seen any commits that should fix it, and I've been on the >lookout for them. There's a non-zero chance that the stuff I committed earlier this morning might have an effect on it. -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 Tue Oct 13 04:48:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13902 for freebsd-current-outgoing; Tue, 13 Oct 1998 04:48:01 -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 EAA13879; Tue, 13 Oct 1998 04:47:56 -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 HAA01262; Tue, 13 Oct 1998 07:46:23 -0400 (EDT) Date: Tue, 13 Oct 1998 07:46:21 -0400 (EDT) From: Chuck Robey To: David Greenman cc: freebsd-current@FreeBSD.ORG Subject: Re: 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_bio.c ... In-Reply-To: <199810130824.BAA23019@freefall.freebsd.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 Tue, 13 Oct 1998, David Greenman wrote: > dg 1998/10/13 01:24:45 PDT > > Modified files: > sys/cam/scsi scsi_da.c > sys/i386/i386 busdma_machdep.c vm_machdep.c > sys/i386/ibcs2 imgact_coff.c > sys/i386/include param.h > sys/i386/isa isa.c wd.c > sys/kern imgact_elf.c sys_pipe.c sysv_shm.c > vfs_bio.c vfs_subr.c > sys/vm default_pager.c device_pager.c > swap_pager.c vm_glue.c vm_map.c vm_mmap.c > vm_pager.c vm_pager.h vm_unix.c > vnode_pager.c vnode_pager.h > 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. > > 1) The vnode pager wasn't properly tracking the file size due to > "size" being page rounded in some cases and not in others. > This sometimes resulted in corrupted files. First noticed by > Terry Lambert. > Fixed by changing the "size" pager_alloc parameter to be a 64bit > byte value (as opposed to a 32bit page index) and changing the > pagers and their callers to deal with this properly. > 2) Fixed a bogus type cast in round_page() and trunc_page() that > caused some 64bit offsets and sizes to be scrambled. Removing > the cast required adding casts at a few dozen callers. > There may be problems with other bogus casts in close-by > macros. A quick check seemed to indicate that those were okay, > however. ----------------------------+----------------------------------------------- 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 13 04:48:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13981 for freebsd-current-outgoing; Tue, 13 Oct 1998 04:48:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA13882 for ; Tue, 13 Oct 1998 04:47:59 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 14897 invoked by uid 1003); 13 Oct 1998 11:47:39 -0000 Message-ID: <19981013134739.A26388@rucus.ru.ac.za> Date: Tue, 13 Oct 1998 13:47:39 +0200 From: Neil Blakey-Milner To: current@FreeBSD.ORG Subject: Some SCSI(?) problems whilst running SMP 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 We're in the unfortunate position of having to run a non-SMP kernel on our dual-processor machine, due to the following: uname -a: (of the non-SMP kernel) FreeBSD rucus.ru.ac.za 3.0-BETA FreeBSD 3.0-BETA #0: Mon Oct 5 04:49:12 SAT 1998 nbm@rucus.ru.ac.za:/usr/src/sys/compile/RUCUS i386 Sources are from October 4th, without softupdates, devfs, and other fun things. //--------------------------------------------------------------------- /usr/src/sys/i386/conf/RUCUS: # SMP-GENERIC -- Smp machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: SMP-GENERIC,v 1.16 1998/09/25 17:34:48 peter Exp $ machine "i386" # SMP does NOT support 386/486 CPUs. #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident GENERIC maxusers 256 # Create a SMP capable kernel (mandatory options): #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O options "MAXDSIZ=(512*1048576)" # Max allowed size of process options "DFLDSIZ=(256*1048576)" # Default Max size of process # Optional, these are the defaults: #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs # Lets always enable the kernel debugger for SMP. #options DDB # SMP shouldn't need x87 emulation, disable by default. #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INCLUDE_CONFIG_FILE options "MD5" options IPFIREWALL options IPFIREWALL_VERBOSE options QUOTA config kernel root on wd0 controller isa0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # Unless you know very well what you're doing, leave ft0 at drive 2, or # remove the line entirely if you don't need it. Trying to configure # it on another unit might cause surprises, see PR kern/7176. tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. #controller ncr0 #controller amd0 #controller ahb0 controller ahc0 #controller isp0 options AHC_ALLOW_MEMIO # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. The options # line following dpt0 here is also currently a *required* option for it. # controller dpt0 # options DPT_MEASURE_PERFORMANCE #controller adv0 at isa? port ? cam irq ? #controller bt0 at isa? port ? cam irq ? #controller aha0 at isa? port ? cam irq ? #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr controller matcd0 at isa? port 0x230 bio device scd0 at isa? port 0x230 bio #options PNP # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options XSERVER # include code for XFree86 #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std options MAXCONS=16 #options SC_DISABLE_REBOOT device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device lpt1 at isa? port? tty device mse0 at isa? port 0x23c tty irq 5 vector mseintr device psm0 at isa? disable port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device de0 #device fxp0 #device tl0 device tx0 #device vx0 #device xl0 device ed0 at isa? port 0x300 net irq 3 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device ex0 at isa? port? net irq? vector exintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr #device cs0 at isa? port 0x300 net irq ? vector csintr pseudo-device loop pseudo-device ether pseudo-device sl 1 #pseudo-device ppp 1 pseudo-device tun 4 pseudo-device pty 256 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM options SYSVSEM options SYSVMSG //-------------------------------------------------------------- diff RUCUS RUCUS-SMP //-------------------------------------------------------------- 23c23 < ident GENERIC --- > ident SMP-GENERIC 27,28c27,28 < #options SMP # Symmetric MultiProcessor Kernel < #options APIC_IO # Symmetric (APIC) I/O --- > options SMP # Symmetric MultiProcessor > Kernel > options APIC_IO # Symmetric (APIC) I/O 40c40 < #options DDB --- > options DDB //--------------------------------------------------------------- /var/run/dmesg.boot: //--------------------------------------------------------------- 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-BETA #0: Mon Oct 5 04:49:12 SAT 1998 nbm@rucus.ru.ac.za:/usr/src/sys/compile/RUCUS Timecounter "i8254" frequency 1193182 Hz cost 2170 ns CPU: Pentium/P54C (200.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x3bf real memory = 134217728 (131072K bytes) avail memory = 127762432 (124768K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ahc0: rev 0x00 int a irq 11 on pci0.12.0 ahc0: Using left over BIOS settings ahc0: aic7880 Wide Channel A, SCSI Id=5, 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> ed0 at 0x300-0x31f irq 3 on isa ed0: address 00:00:e8:1c:7b:57, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found mse0 not found at 0x23c 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: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 wt0 not probed due to I/O address conflict with ed0 at 0x300 mcd0 not probed due to I/O address conflict with ed0 at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround IP packet filtering initialized, divert disabled, rule-based forwarding disabled, unlimited logging Sending WDTR! (probe2:ahc0:0:2:0): Sending SDTR!! sa0 at ahc0 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 10.0MB/s transfers (10.0MHz, offset 15) changing root device to da1s1a da1 at ahc0 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C) da0 at ahc0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit) da0: 4157MB (8515173 512 byte sectors: 64H 32S/T 4157C) //--------------------------------------------------------------- Ok, the problem is this: When we enable SMP support, within any time from an hour to 6 days, we will die with SCSI errors - of late "SCB timeout handled by another timeout" I think is the proferred explanation. The "death" seems to occur quickly after extensive access to the disks, but it also just dies arbitrarily, usually after the machine has been up for a few days. It doesn't seem to be specific to any drive failing either. (we've swapped drives around, etc) ("die" is a technical term here meaning either a reboot just after a SCSI error pops up for a few seconds, or just hangs after a SCSI error pops up.) The motherboard is a GigaByte GA586DX with onboard AIC7880 SCSI controller. The BIOS has been updated from 1.0 to 3.43 to no avail. I'm looking for anything to do with the SCSI controller too, but nothing seems to be out there. We have both 16bit and 8bit devices on it, and is terminated correctly according to both the motherboard manual, and tons of testing. (terminator on last device on each SCSI connection, and high-bit termination on and low-bit termination off on the motherboard). These errors have been occuring much more often recently, happening only occasionally about a year ago, and now happening _extremely_ fast (usually within 4 days, sometimes a whole week) if we have SMP enabled. We've yet to have the same problem without SMP though. I realize that it's incredibly likely to be the hardware, I was just hoping that I'm wrong in this regard, since we're stuck with this hardware for a few months, and we're kinda used to having huge uptimes, CPU power, and similar things, compared to the Microsoft house that is the Information Systems department. Anyway, any and all help would be appreciated. (although I'll understand if everyone ignores this for a few days whilst furious coding occurs on the new release) Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 04:53:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14273 for freebsd-current-outgoing; Tue, 13 Oct 1998 04:53:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bsd.mbp.ee (bsd.mbp.ee [194.204.12.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14257; Tue, 13 Oct 1998 04:53:51 -0700 (PDT) (envelope-from mauri@mbp.ee) Received: from nw1.mbp.ee (nw1.mbp.ee [194.204.12.68]) by bsd.mbp.ee (8.9.1/8.9.1) with ESMTP id OAA20366; Tue, 13 Oct 1998 14:53:34 +0300 (EEST) (envelope-from mauri@mbp.ee) Message-Id: <199810131153.OAA20366@bsd.mbp.ee> Received: from SERVER/SpoolDir by nw1.mbp.ee (Mercury 1.43); 13 Oct 98 14:53:34 +0300 Received: from SpoolDir by SERVER (Mercury 1.43); 13 Oct 98 14:53:18 +0300 From: "Lauri Laupmaa" Organization: =?ISO-8859-1?Q?ripeva_Kirjastuse_AS?= To: current@FreeBSD.ORG, ports@FreeBSD.ORG Date: Tue, 13 Oct 1998 14:53:06 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Subject: 12.10.1998 ELF current & mysqld port X-mailer: Pegasus Mail for Win32 (v3.01b) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from Quoted-printable to 8bit by hub.freebsd.org id EAA14258 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... still does not compile: bash-2.02# cd /usr/ports/databases/mysql321 bash-2.02# make ===> mysql-3.21.33 is broken for ELF: build. bash-2.02# cd /usr/ports/databases/mysql322 bash-2.02# make ===> mysql-3.22.6a is broken for ELF: build. bash-2.02# ______________ Lauri Laupmaa дripДev mauri@mbp.ee Ph. +372 66 70 369 +372 50 13 369 Fx. +372 66 70 165 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 04:55:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14414 for freebsd-current-outgoing; Tue, 13 Oct 1998 04:55:57 -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 EAA14407 for ; Tue, 13 Oct 1998 04:55:56 -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 EAA12696; Tue, 13 Oct 1998 04:54:05 -0700 (PDT) Message-Id: <199810131154.EAA12696@implode.root.com> To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: 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_bio.c ... In-reply-to: Your message of "Tue, 13 Oct 1998 07:46:21 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 13 Oct 1998 04:54:04 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Tue, 13 Oct 1998, David Greenman wrote: > >> dg 1998/10/13 01:24:45 PDT >> >> Modified files: >> sys/cam/scsi scsi_da.c >> sys/i386/i386 busdma_machdep.c vm_machdep.c >> sys/i386/ibcs2 imgact_coff.c >> sys/i386/include param.h >> sys/i386/isa isa.c wd.c >> sys/kern imgact_elf.c sys_pipe.c sysv_shm.c >> vfs_bio.c vfs_subr.c >> sys/vm default_pager.c device_pager.c >> swap_pager.c vm_glue.c vm_map.c vm_mmap.c >> vm_pager.c vm_pager.h vm_unix.c >> vnode_pager.c vnode_pager.h >> 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. If the problem persists for them, then you'll save some porting work. -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 Tue Oct 13 05:13:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15993 for freebsd-current-outgoing; Tue, 13 Oct 1998 05:13:06 -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 FAA15988 for ; Tue, 13 Oct 1998 05:13:04 -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 HAA12702; Tue, 13 Oct 1998 07:12:37 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <362343B5.D45924D4@webwizard.org.mx> Date: Tue, 13 Oct 1998 07:12:37 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith CC: FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release References: <199810130117.SAA01131@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: > > Due to a parity error in my memory:-) I forgot to remove my > > KERNFORMAT=elf system variable before making release and much to my > > surprise it made it through kernel creation. It looks like we will soon > > be able to make a 100% elf release. Has anyone done it? How important > > is it. Here's the result from my log before I redo it with an out > > kernel, if anyone is interested. > > There's some (understandable) resistance to putting an ELF kernel in > 3.0, so the changeover will probably happen a few weeks afterwards. At > that stage we'll shift to the new bootloader as well. > > I don't expect that ELF kernels will be supported for 3.0-RELEASE, > although you will be able to build and experiment with them. Thanks for the info. I understand but don't necessarily agree. Why put it off? I have 100% elf machines running in different environments and one as a production server. I have only had a few problems with the boot loader and the elf kernel at the beginning. I 'm using the standard complementary programs, compiled as elf, X11, samba, shlight, tac_plus, apache1.3.3, squid, mysql3.22 and everything works better than expected. Everyone should be very proud. Just one persons opinion:-) ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 05:13:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16061 for freebsd-current-outgoing; Tue, 13 Oct 1998 05:13:28 -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 FAA16044; Tue, 13 Oct 1998 05:13:25 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id NAA00392; Tue, 13 Oct 1998 13:11:10 +0100 (BST) Message-ID: <36234326.BD6349B3@tdx.co.uk> Date: Tue, 13 Oct 1998 13:10:14 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Lauri Laupmaa CC: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: 12.10.1998 ELF current & mysqld port References: <199810131153.OAA20366@bsd.mbp.ee> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lauri Laupmaa wrote: > > ... still does not compile: > > bash-2.02# cd /usr/ports/databases/mysql321 > bash-2.02# make > ===> mysql-3.21.33 is broken for ELF: build. > bash-2.02# cd /usr/ports/databases/mysql322 > bash-2.02# make > ===> mysql-3.22.6a is broken for ELF: build. > bash-2.02# Hi, I've spoken to the mainter for this - they have finished a 321 'elf' version, which can be found at: http://www.physik.TU-Berlin.DE/~ibex/ports/mysql321.tar.gz To quote his email, " A version of mysql322 which builds under ELF is almost finished. The PLIST might be wrong and you have to rename /usr/local/lib/mysql/libmysqlclient.so.4.0 to /usr/local/lib/mysql/libmysqlclient.so.4 . It's available under: http://www.physik.TU-Berlin.DE/~ibex/ports/mysql322-pre.tar.gz " I don't know when these will be committed to the ports tree... Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 05:29:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17278 for freebsd-current-outgoing; Tue, 13 Oct 1998 05:29: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 FAA17258; Tue, 13 Oct 1998 05:29:26 -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 IAA01339; Tue, 13 Oct 1998 08:26:15 -0400 (EDT) Date: Tue, 13 Oct 1998 08:26:14 -0400 (EDT) From: Chuck Robey To: Lauri Laupmaa cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: 12.10.1998 ELF current & mysqld port In-Reply-To: <199810131153.OAA20366@bsd.mbp.ee> Message-ID: 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 On Tue, 13 Oct 1998, Lauri Laupmaa wrote: > ... still does not compile: > > bash-2.02# cd /usr/ports/databases/mysql321 > bash-2.02# make > ===> mysql-3.21.33 is broken for ELF: build. > bash-2.02# cd /usr/ports/databases/mysql322 > bash-2.02# make > ===> mysql-3.22.6a is broken for ELF: build. > bash-2.02# > 1st thing, this is a ports problem, not current, and should have been posted to freebsd-ports. Second thing, the port has been marked broken for elf, it's known (it clearly says that above) and will be fixed but there's a stack of 1500 ports to go thru in not enough time. > ______________ > Lauri Laupmaa > дripДev > mauri@mbp.ee > Ph. +372 66 70 369 > +372 50 13 369 > Fx. +372 66 70 165 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-ports" 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 Tue Oct 13 05:29:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17373 for freebsd-current-outgoing; Tue, 13 Oct 1998 05:29:49 -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 FAA17360 for ; Tue, 13 Oct 1998 05:29:44 -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 HAA25418; Tue, 13 Oct 1998 07:29:02 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <3623478E.5D795AEC@webwizard.org.mx> Date: Tue, 13 Oct 1998 07:29:02 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm CC: Studded , Mike Smith , FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release References: <199810130909.RAA29552@spinner.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > Studded wrote: > > Mike Smith wrote: > > > > > There's some (understandable) resistance to putting an ELF kernel in > > > 3.0, so the changeover will probably happen a few weeks afterwards. At > > > that stage we'll shift to the new bootloader as well. > > > > I still think getting the pain over now is a good idea. Leaving a major > > change for after the "release" will just postpone by one more quarter > > the time when 3.0 has a chance of being stable. > > Unfortunately, I agree, in part at least. The biggest difficulty in doing > a changeover is upgrading the stage2 bootblocks. If we get the 3.0 CD > installing ELF-capable bootblocks (even if it's a hacked biosboot), then > it's going to make the transition *so* much easier. It's not a question > of flipping a switch, we've got to get the bootblocks upgraded. If we > could get the 3.0 release sysinstall to do this for us it would be a big > win. > > Ideally there should be a choice in sysinstall, and sysinstall could > change them on the fly. If somebody installed a system and the new > bootblocks didn't work, it'd be nice if it was as simple as booting the > floppy and downgrading to the older system. > > IMHO, whether /kernel is a.out or elf is far less of an issue than which > bootblocks we use. > > Cheers, > -Peter > I agree 100%. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 05:34:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17711 for freebsd-current-outgoing; Tue, 13 Oct 1998 05:34:52 -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 FAA17705 for ; Tue, 13 Oct 1998 05:34:48 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id NAA00470; Tue, 13 Oct 1998 13:32:20 +0100 (BST) Message-ID: <3623481C.15FAA691@tdx.co.uk> Date: Tue, 13 Oct 1998 13:31:24 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Neil Blakey-Milner CC: current@FreeBSD.ORG Subject: Re: Some SCSI(?) problems whilst running SMP References: <19981013134739.A26388@rucus.ru.ac.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neil Blakey-Milner wrote: > [MEGA-Snip] ;-) - Nice to see someone provide _all_ the details though > > I realize that it's incredibly likely to be the hardware, I was just hoping > that I'm wrong in this regard, since we're stuck with this hardware for a > few months, and we're kinda used to having huge uptimes, CPU power, and > similar things, compared to the Microsoft house that is the Information > Systems department. Hi, I run a -current box with SMP, and it has three 7880's in it... I also have what could probably be called a 'vast array of inexpensive and dodgy' drives in it (14 odd in total)... I have seen few problems with CAM or the SCSI side of things - your symptoms sound extreemly hardware related... I had problems in the past with my old setup, all of which was caused by termination problems (and boy did it cause weird symptoms)... If no one else can suggest anything, or your stuck let me know... But I have a feeling it's going to turn into one of those "What's terminated and what isn't terminated, and what type of cable is it" type sessions ;-) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 05:35:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17780 for freebsd-current-outgoing; Tue, 13 Oct 1998 05:35:36 -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 FAA17772 for ; Tue, 13 Oct 1998 05:35:33 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id NAA00480; Tue, 13 Oct 1998 13:34:38 +0100 (BST) Message-ID: <362348A6.5BA573DD@tdx.co.uk> Date: Tue, 13 Oct 1998 13:33:42 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Edwin Culp CC: Peter Wemm , Studded , Mike Smith , FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release References: <199810130909.RAA29552@spinner.netplex.com.au> <3623478E.5D795AEC@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: > > Peter Wemm wrote: > > > Studded wrote: > > > Mike Smith wrote: > > > > > > > There's some (understandable) resistance to putting an ELF kernel in > > > > 3.0, so the changeover will probably happen a few weeks afterwards. At > > > > that stage we'll shift to the new bootloader as well. The last I heard we weren't able to debug ELF kernels? (or at least LDK's running in ELF kernels)? I know that's one of the reasons why I've left my system running a.out kernels at the moment... (and I at least hope it's a good reason ;-) Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 06:07:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20906 for freebsd-current-outgoing; Tue, 13 Oct 1998 06:07: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 GAA20891 for ; Tue, 13 Oct 1998 06:07:09 -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 IAA28980; Tue, 13 Oct 1998 08:06:43 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <36235062.564A9A15@webwizard.org.mx> Date: Tue, 13 Oct 1998 08:06:43 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Studded CC: Mike Smith , FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release References: <199810130117.SAA01131@dingo.cdrom.com> <3622D416.E2E627AC@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Studded wrote: > Mike Smith wrote: > > > There's some (understandable) resistance to putting an ELF kernel in > > 3.0, so the changeover will probably happen a few weeks afterwards. At > > that stage we'll shift to the new bootloader as well. > > I still think getting the pain over now is a good idea. Leaving a major > change for after the "release" will just postpone by one more quarter > the time when 3.0 has a chance of being stable. > > Doug > -- > *** Chief Operations Officer, DALnet IRC network *** Seems much more logical. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 06:17:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21917 for freebsd-current-outgoing; Tue, 13 Oct 1998 06:17:59 -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 GAA21893 for ; Tue, 13 Oct 1998 06:17:54 -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 IAA29019; Tue, 13 Oct 1998 08:16:15 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <3623529F.D5251FA0@webwizard.org.mx> Date: Tue, 13 Oct 1998 08:16:15 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Karl Pielorz CC: Peter Wemm , Studded , Mike Smith , FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release References: <199810130909.RAA29552@spinner.netplex.com.au> <3623478E.5D795AEC@webwizard.org.mx> <362348A6.5BA573DD@tdx.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Pielorz wrote: > Edwin Culp wrote: > > > > Peter Wemm wrote: > > > > > Studded wrote: > > > > Mike Smith wrote: > > > > > > > > > There's some (understandable) resistance to putting an ELF kernel in > > > > > 3.0, so the changeover will probably happen a few weeks afterwards. At > > > > > that stage we'll shift to the new bootloader as well. > > The last I heard we weren't able to debug ELF kernels? (or at least LDK's > running in ELF kernels)? > > I know that's one of the reasons why I've left my system running a.out kernels > at the moment... (and I at least hope it's a good reason ;-) > > Karl The wonderful part of it is that I haven't had anything to debug :-) What % of the folks running current/beta debug their kernels? The way to find the problems is to have more people using it in its most complete form. IMO. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 06:25:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22848 for freebsd-current-outgoing; Tue, 13 Oct 1998 06:25:43 -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 GAA22843 for ; Tue, 13 Oct 1998 06:25:41 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id OAA00698; Tue, 13 Oct 1998 14:25:23 +0100 (BST) Message-ID: <3623548A.E4A9FE0F@tdx.co.uk> Date: Tue, 13 Oct 1998 14:24:26 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Edwin Culp CC: FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release References: <199810130909.RAA29552@spinner.netplex.com.au> <3623478E.5D795AEC@webwizard.org.mx> <362348A6.5BA573DD@tdx.co.uk> <3623529F.D5251FA0@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: > > I know that's one of the reasons why I've left my system running a.out kernels > > at the moment... (and I at least hope it's a good reason ;-) > > > > Karl > > The wonderful part of it is that I haven't had anything to debug :-) What % of > the folks running current/beta debug their kernels? The way to find the problems > is to have more people using it in its most complete form. IMO. Hmmm.. Well if I'm right about not being able to debug LDK's with an ELF kernel, I have to keep my kernel a.out... An LKM I'm betaing has a few problems, which means it's gotta be debug(able)... Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 06:42:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24837 for freebsd-current-outgoing; Tue, 13 Oct 1998 06:42:55 -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 GAA24831 for ; Tue, 13 Oct 1998 06:42:53 -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 IAA29171; Tue, 13 Oct 1998 08:42:36 -0500 (CDT) (envelope-from eculp@webwizard.org.mx) Message-ID: <362358CB.377ACD3F@webwizard.org.mx> Date: Tue, 13 Oct 1998 08:42:35 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Karl Pielorz CC: FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release References: <199810130909.RAA29552@spinner.netplex.com.au> <3623478E.5D795AEC@webwizard.org.mx> <362348A6.5BA573DD@tdx.co.uk> <3623529F.D5251FA0@webwizard.org.mx> <3623548A.E4A9FE0F@tdx.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Pielorz wrote: > Edwin Culp wrote: > > > > I know that's one of the reasons why I've left my system running a.out kernels > > > at the moment... (and I at least hope it's a good reason ;-) > > > > > > Karl > > > > The wonderful part of it is that I haven't had anything to debug :-) What % of > > the folks running current/beta debug their kernels? The way to find the problems > > is to have more people using it in its most complete form. IMO. > > Hmmm.. Well if I'm right about not being able to debug LDK's with an ELF > kernel, I have to keep my kernel a.out... An LKM I'm betaing has a few > problems, which means it's gotta be debug(able)... > > Karl I understand and agree, but the other ??% that doesn't? Have a great afternoon, for you folks in the UK. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 07:21:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27955 for freebsd-current-outgoing; Tue, 13 Oct 1998 07:21:37 -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 HAA27947; Tue, 13 Oct 1998 07:21:34 -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 KAA14462; Tue, 13 Oct 1998 10:22:56 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Tue, 13 Oct 1998 10:22:56 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= cc: Bruce Evans , sthaug@nethelp.no, current@FreeBSD.ORG, zach@gaffaneys.com Subject: Re: bitten 3 times already. In-Reply-To: <199810130931.LAA07720@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id HAA27948 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could you please include a heads up that explains this to user and how to make sure you don't get bitten by the driver getting confused? I understand the concept of LBA but fixing my drive to work non-LBA is something I don't know now to do. It would be much appreciated. thank you, 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, 13 Oct 1998, SЬren Schmidt wrote: > In reply to Bruce Evans who wrote: > > >If dumps and LBA mode shouldn't be used together, it would be useful to > > >have a warning about that somewhere, since a lot of BIOSes seem to want > > >to use LBA as default for newer big IDE disks. > > > > This doesn't follow, since the driver's use of LBA has nothing to do > > with the BIOS's use of LBA. The driver should simply not use LBA (as > > in 2.2). > > Exactly, maybe I should remove the LBA support in current, there is > no use for it actually, just the change needed to use >8G drives > (like I did it in 2.2.7+).. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > 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 Tue Oct 13 07:35:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29266 for freebsd-current-outgoing; Tue, 13 Oct 1998 07:35:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA29259 for ; Tue, 13 Oct 1998 07:35:07 -0700 (PDT) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id JBMHTQQJ; Tue, 13 Oct 98 14:34:52 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981013162954.0091e800@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 13 Oct 1998 16:29:54 +0200 To: freebsd-current@FreeBSD.ORG From: Marius Bendiksen Subject: Re: bitten 3 times already. Mime-Version: 1.0 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 HAA29262 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't been tracking this too closely, but doesn't such a thing as SЬren Schmidt suggested (removing LBA support) mean that people with LBA drives will end up in heaps of trouble? I have 8.4 + 3.2 gigs on LBA-formatted IDE drives, and would certainly not appreciate losing those. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 08:15:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03576 for freebsd-current-outgoing; Tue, 13 Oct 1998 08:15:04 -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 IAA03564 for ; Tue, 13 Oct 1998 08:14:55 -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 RAA24626 for ; Tue, 13 Oct 1998 17:14:30 +0200 (CEST) Received: from cs.uni-sb.de (acc2-156.telip.uni-sb.de [134.96.112.156]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id RAA26455 for ; Tue, 13 Oct 1998 17:14:29 +0200 (CEST) Message-ID: <36236E98.43A3CDC6@cs.uni-sb.de> Date: Tue, 13 Oct 1998 17:15:36 +0200 From: Daniel Rock X-Mailer: Mozilla 4.06 [de] (Win98; U) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: -current NFS problem References: <199810130405.VAA18347@math.berkeley.edu> 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 also seen NFS problems for some months now: (NFS Server is a Solaris 2.6 box) - During a "make release" with the chroot direcory mounted NFS or a "make world" with /usr/obj mounted NFS (I patched /sys/nfs/nfs_vnops.c not return an error on "chflags" system calls), cap_mkdb determinstically dumps core while processing termcap: ===> share/termcap ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > /dev/ null cap_mkdb termcap *** Signal 11 This only happens with NFS v3, not NFS v2 - If the shell output (e.g. for tcsh and XFree86 "make World >&! World.log) is on an NFS mounted drive, and I watch the file with less (less World.log) go to the end of file (Shift-G), sometimes the output gets filled up with 0 characters. This happens with both NFS v2 and v3. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 08:20:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04348 for freebsd-current-outgoing; Tue, 13 Oct 1998 08:20:57 -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 IAA04343 for ; Tue, 13 Oct 1998 08:20: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 LAA08350; Tue, 13 Oct 1998 11:20:31 -0400 (EDT) (envelope-from wollman) Date: Tue, 13 Oct 1998 11:20:31 -0400 (EDT) From: Garrett Wollman Message-Id: <199810131520.LAA08350@khavrinen.lcs.mit.edu> To: sthaug@nethelp.no Cc: current@FreeBSD.ORG Subject: Re: bitten 3 times already. In-Reply-To: <29164.908268856@verdi.nethelp.no> References: <199810130429.OAA05137@godzilla.zeta.org.au> <29164.908268856@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < Below is a suggested patch to the dumpon.8 manual page to include such > a warning. > + The kernel crash dump is written using CHS addressing. Kernel crash > + dumps should not be enabled for disks running in LBA mode. > + .Pp Doesn't belong in a machine-independent manual page. -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 13 08:42:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06928 for freebsd-current-outgoing; Tue, 13 Oct 1998 08:42:01 -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 IAA06909 for ; Tue, 13 Oct 1998 08:41:58 -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 RAA03958 for ; Tue, 13 Oct 1998 17:46:51 +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 SAA19146 for ; Tue, 13 Oct 1998 18:01:13 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id RAA24010; Tue, 13 Oct 1998 17:53:55 +0200 (CEST) Message-ID: <19981013175355.39221@deepo.prosa.dk> Date: Tue, 13 Oct 1998 17:53:55 +0200 From: Philippe Regnauld To: freebsd-current@FreeBSD.ORG Subject: 981009-BETA + options "VM86" + options VESA = no SCSI ? 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 Sorry if this popped up already, but: 1) 486/100, 16MB 2) Aha 2840 (VLB) 3) Seagate 1GB Hawk If I add VM86 and VESA, AHC does not show up in userconfig, and is not probed. (i.e. disappears from system). Something BIOS related ? I haven't seen anything relevant in LINT. -- -[ 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 Tue Oct 13 08:48:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07797 for freebsd-current-outgoing; Tue, 13 Oct 1998 08:48:14 -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 IAA07750 for ; Tue, 13 Oct 1998 08:48:05 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id RAA00285; Tue, 13 Oct 1998 17:47:40 +0200 (CEST) (envelope-from sos) Message-Id: <199810131547.RAA00285@sos.freebsd.dk> Subject: Re: bitten 3 times already. In-Reply-To: <3.0.5.32.19981013162954.0091e800@mail.scancall.no> from Marius Bendiksen at "Oct 13, 98 04:29:54 pm" To: Marius.Bendiksen@scancall.no (Marius Bendiksen) Date: Tue, 13 Oct 1998 17:47:40 +0200 (CEST) Cc: 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 Marius Bendiksen who wrote: > I haven't been tracking this too closely, but doesn't such a thing as SЬren > Schmidt suggested (removing LBA support) mean that people with LBA drives > will end up in heaps of trouble? I have 8.4 + 3.2 gigs on LBA-formatted IDE > drives, and would certainly not appreciate losing those. You dont need to run the drive in LBA mode to coexist with DOS or whatever. Also you dont need to run the drive in LBA mode to use >8G, infact using LBA has nothing to do with >8G support. >8G support has something to do with us probing the drive correctly and using it that way. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Tue Oct 13 09:01:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09082 for freebsd-current-outgoing; Tue, 13 Oct 1998 09:01:11 -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 JAA09077 for ; Tue, 13 Oct 1998 09:01:09 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id SAA00347; Tue, 13 Oct 1998 18:00:51 +0200 (CEST) (envelope-from sos) Message-Id: <199810131600.SAA00347@sos.freebsd.dk> Subject: Re: 981009-BETA + options "VM86" + options VESA = no SCSI ? In-Reply-To: <19981013175355.39221@deepo.prosa.dk> from Philippe Regnauld at "Oct 13, 98 05:53:55 pm" To: regnauld@deepo.prosa.dk (Philippe Regnauld) Date: Tue, 13 Oct 1998 18:00:51 +0200 (CEST) Cc: 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 Philippe Regnauld who wrote: > Sorry if this popped up already, but: > > 1) 486/100, 16MB > 2) Aha 2840 (VLB) > 3) Seagate 1GB Hawk > > If I add VM86 and VESA, AHC does not show up in userconfig, and is not probed. > (i.e. disappears from system). > Something BIOS related ? I haven't seen anything relevant in LINT. Hmm, no AHC controller here, sorry, but it works fine with my NCR... Anybody else with that same controller?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Tue Oct 13 09:03:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09282 for freebsd-current-outgoing; Tue, 13 Oct 1998 09:03:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09277 for ; Tue, 13 Oct 1998 09:03:44 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id JAA20244; Tue, 13 Oct 1998 09:03:13 -0700 (PDT) (envelope-from dhw) Date: Tue, 13 Oct 1998 09:03:13 -0700 (PDT) From: David Wolfskill Message-Id: <199810131603.JAA20244@pau-amma.whistle.com> To: sthaug@nethelp.no, wollman@khavrinen.lcs.mit.edu Subject: Re: bitten 3 times already. Cc: current@FreeBSD.ORG In-Reply-To: <199810131520.LAA08350@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 13 Oct 1998 11:20:31 -0400 (EDT) >From: Garrett Wollman >> + The kernel crash dump is written using CHS addressing. Kernel crash >> + dumps should not be enabled for disks running in LBA mode. >Doesn't belong in a machine-independent manual page. OK.... That leaves a couple of options: * Don't provide such a (machine-dependent) warning, or * Provide one somewhere else. Now, it may well be that anyone running certain flavors of an OS should be expected to know the arcana of each instantiation of the hardware on which it happens to be implemented. If so, I'd appreciate a pointer to such information, since I'm finding PC hardware very strange and prone to peculiar forms of misbehavior. (My prior experience has been mostly with Sun boxen & IBM mainframes.) If not, it would seem that providing a place for warnings of a machine- dependent nature would be a Good Thing. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 09:48:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14923 for freebsd-current-outgoing; Tue, 13 Oct 1998 09:48:41 -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 JAA14917 for ; Tue, 13 Oct 1998 09:48:40 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id MAA03517; Tue, 13 Oct 1998 12:48:24 -0400 (EDT) Date: Tue, 13 Oct 1998 12:48:24 -0400 (EDT) Message-Id: <199810131648.MAA03517@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: libc_r changes broke stuff. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have reason to believe that recent changes to libc_r have caused problems with our application. I'd like to be able to figure out what the "diffs" were. We are using cvsup, so, we have an up-to-date tree. Question: What do I type to find out the diffs in a particular ".c" file from the remote CVS tree? -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 13 09:55:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15851 for freebsd-current-outgoing; Tue, 13 Oct 1998 09:55:46 -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 JAA15839 for ; Tue, 13 Oct 1998 09:55:42 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA03427; Tue, 13 Oct 1998 10:55:22 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810131655.KAA03427@panzer.plutotech.com> Subject: Re: 3.0-19981009-BETA + 2840 AHA + camcontrol stop/start = panic In-Reply-To: <19981013130106.43997@deepo.prosa.dk> from Philippe Regnauld at "Oct 13, 98 01:01:06 pm" To: regnauld@deepo.prosa.dk (Philippe Regnauld) Date: Tue, 13 Oct 1998 10:55:22 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (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 Philippe Regnauld wrote... > Kenneth D. Merry writes: > > > > Unless you can provide a stack trace, or at least the functions around the > > given instruction pointer, there's no way to know where the panic is. > > 1st panic: (i.p. = 0xf010553d) > > nm.aout /kernel | sort > > ... > f0105448 T _xpt_done > <---> > f01055b4 T _xpt_alloc_ccb > ... I think I've been able to reproduce that one. I think it's in xpt_done(). I've got an idea of why it's happening, it'll just take a while to track it down. > 2nd panic: (i.p. = 0xf014a92f) > > ... > f014a914 T _tsleep > <---> > f014ab6c t _endtsleep > ... Haven't been able to reproduce that one. > > Try setting up a serial console and DDB so you can get a stack trace. > > Ok, but onФy because it's you ;-) > > panic-on-demand (with DDB): > > [doing start/stop stuff]: > > panic: biodone: buffer not busy > > - trace: > > _biodone at _biodone+0x24 > _dadone at _dadone+0x23d > _camisr at _damisr+0x1fb > _swi_cambio at _swi_cambio+0xd > doreti_swi() at doreti_swi+0xf > > (machine still in DDB -- anything more precise ? I don't have a serial > cross cable right now). That won't be necessary, I can reproduce this one as well. I'm not really sure of the cause on this one, it'll take some investigation to find out. BTW, in your first message you exposed a bug in camcontrol. It's fixed now. The reason your drive started was because the error recovery code kicked in and started it when you typed 'camcontrol'. (the kernel tried to access the disk, which wasn't spun up, so it sent a start unit command to 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 Tue Oct 13 09:57:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16002 for freebsd-current-outgoing; Tue, 13 Oct 1998 09:57:16 -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 JAA15997 for ; Tue, 13 Oct 1998 09:57:14 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id MAA00477; Tue, 13 Oct 1998 12:56:59 -0400 (EDT) Message-ID: <19981013125659.A305@netmonger.net> Date: Tue, 13 Oct 1998 12:56:59 -0400 From: Christopher Masto To: HighWind Software Information , current@FreeBSD.ORG Subject: Re: libc_r changes broke stuff. References: <199810131648.MAA03517@highwind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810131648.MAA03517@highwind.com>; from HighWind Software Information on Tue, Oct 13, 1998 at 12:48:24PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 13, 1998 at 12:48:24PM -0400, HighWind Software Information wrote: > > I have reason to believe that recent changes to libc_r have caused > problems with our application. I'd like to be able to figure out what > the "diffs" were. > > We are using cvsup, so, we have an up-to-date tree. > > Question: > What do I type to find out the diffs in a particular ".c" file > from the remote CVS tree? Are you using cvsup to get the full CVS tree or just -current? If the former, $ cd /usr/src/... $ cvs log file.c $ cvs diff -r1.47 -r1.48 file.c Otherwise, use the excellent web interface at http://www.freebsd.org/cgi/cvsweb.cgi -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ 640K ought to be enough for anybody. - BILL GATES, 1981 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 10:04:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16721 for freebsd-current-outgoing; Tue, 13 Oct 1998 10:04:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16716 for ; Tue, 13 Oct 1998 10:04:09 -0700 (PDT) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id MAA17548; Tue, 13 Oct 1998 12:03:46 -0500 (CDT) Message-ID: <19981013120346.A17500@Denninger.Net> Date: Tue, 13 Oct 1998 12:03:46 -0500 From: Karl Denninger To: HighWind Software Information , current@FreeBSD.ORG Subject: Re: libc_r changes broke stuff. References: <199810131648.MAA03517@highwind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810131648.MAA03517@highwind.com>; from HighWind Software Information on Tue, Oct 13, 1998 at 12:48:24PM -0400 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 13, 1998 at 12:48:24PM -0400, HighWind Software Information wrote: > > I have reason to believe that recent changes to libc_r have caused > problems with our application. I'd like to be able to figure out what > the "diffs" were. > > We are using cvsup, so, we have an up-to-date tree. > > Question: > What do I type to find out the diffs in a particular ".c" file > from the remote CVS tree? > > -Rob "cvs log file.c" from the directory you're interested in. Pipe it through "more" or it'll just scroll off. -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 10:06:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16900 for freebsd-current-outgoing; Tue, 13 Oct 1998 10:06:37 -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 KAA16893 for ; Tue, 13 Oct 1998 10:06:33 -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 KAA17091; Tue, 13 Oct 1998 10:06:12 -0700 (PDT) (envelope-from jdp) Message-Id: <199810131706.KAA17091@austin.polstra.com> To: info@highwind.com Subject: Re: libc_r changes broke stuff. In-Reply-To: <199810131648.MAA03517@highwind.com> References: <199810131648.MAA03517@highwind.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 13 Oct 1998 10:06:11 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199810131648.MAA03517@highwind.com>, HighWind Software Information wrote: > I have reason to believe that recent changes to libc_r have caused > problems with our application. I'd like to be able to figure out what > the "diffs" were. > > We are using cvsup, so, we have an up-to-date tree. > > Question: > What do I type to find out the diffs in a particular ".c" file > from the remote CVS tree? CVSup can't do that directly. You might find this useful, though: http://www.freebsd.org/cgi/cvsweb.cgi John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 10:19:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19132 for freebsd-current-outgoing; Tue, 13 Oct 1998 10:19:05 -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 KAA19121 for ; Tue, 13 Oct 1998 10:18:59 -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 TAA05303; Tue, 13 Oct 1998 19:23:45 +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 TAA19246; Tue, 13 Oct 1998 19:38:08 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id TAA24671; Tue, 13 Oct 1998 19:30:51 +0200 (CEST) Message-ID: <19981013193051.46229@deepo.prosa.dk> Date: Tue, 13 Oct 1998 19:30:51 +0200 From: Philippe Regnauld To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG, gibbs@pluto.plutotech.com Subject: Re: 3.0-19981009-BETA + 2840 AHA + camcontrol stop/start = panic References: <19981013130106.43997@deepo.prosa.dk> <199810131655.KAA03427@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199810131655.KAA03427@panzer.plutotech.com>; from Kenneth D. Merry on Tue, Oct 13, 1998 at 10:55:22AM -0600 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 Kenneth D. Merry writes: > > BTW, in your first message you exposed a bug in camcontrol. It's fixed > now. The reason your drive started was because the error recovery code > kicked in and started it when you typed 'camcontrol'. (the kernel tried to > access the disk, which wasn't spun up, so it sent a start unit command to > it.) That's what I thought. So in fact the subsequent invocation of camcontrol start did nothing, right ? (it just responded that start should take an argument) -- -[ 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 Tue Oct 13 10:26:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20248 for freebsd-current-outgoing; Tue, 13 Oct 1998 10:26:15 -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 KAA20239 for ; Tue, 13 Oct 1998 10:26:11 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id LAA03687; Tue, 13 Oct 1998 11:25:50 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810131725.LAA03687@panzer.plutotech.com> Subject: Re: 3.0-19981009-BETA + 2840 AHA + camcontrol stop/start = panic In-Reply-To: <19981013193051.46229@deepo.prosa.dk> from Philippe Regnauld at "Oct 13, 98 07:30:51 pm" To: regnauld@deepo.prosa.dk (Philippe Regnauld) Date: Tue, 13 Oct 1998 11:25:50 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM908299550-3628-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM908299550-3628-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Philippe Regnauld wrote... > Kenneth D. Merry writes: > > > > BTW, in your first message you exposed a bug in camcontrol. It's fixed > > now. The reason your drive started was because the error recovery code > > kicked in and started it when you typed 'camcontrol'. (the kernel tried to > > access the disk, which wasn't spun up, so it sent a start unit command to > > it.) > > That's what I thought. So in fact the subsequent invocation > of camcontrol start did nothing, right ? (it just responded > that start should take an argument) Right. camcontrol itself did nothing, but by calling it, you caused a disk access which caused us to try to spin the disk up. I've attached a preliminary patch that fixes one of the panics you saw. (the one in xpt_done()) It may cause other problems, though, so I need to check it out a little more. In my initial tests it works fine, though. The "biodone: buffer not busy" panic seems to only happen on a mounted filesystem. This patch doesn't fix that problem. Ken -- Kenneth Merry ken@plutotech.com --ELM908299550-3628-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=cam_xpt.inq_changed.diffs.101398 Content-Description: cam_xpt.inq_changed.diffs.101398 Content-Transfer-Encoding: 7bit ==== //depot/cam/sys/cam/cam_xpt.c#167 - /usr/home/ken/perforce/cam/sys/cam/cam_xpt.c ==== *** /tmp/tmp.26937.0 Tue Oct 13 11:16:20 1998 --- /usr/home/ken/perforce/cam/sys/cam/cam_xpt.c Tue Oct 13 11:11:41 1998 *************** *** 3941,3947 **** if ((async_code == AC_SENT_BDR) || (async_code == AC_BUS_RESET) || (async_code == AC_INQ_CHANGED)) ! status = xpt_compile_path(&newpath, NULL, bus->path_id, target->target_id, device->lun_id); --- 3941,3948 ---- if ((async_code == AC_SENT_BDR) || (async_code == AC_BUS_RESET) || (async_code == AC_INQ_CHANGED)) ! status = xpt_compile_path(&newpath, ! path->periph, bus->path_id, target->target_id, device->lun_id); --ELM908299550-3628-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 13 11:21:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25446 for freebsd-current-outgoing; Tue, 13 Oct 1998 11:21:27 -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 LAA25402 for ; Tue, 13 Oct 1998 11:21:22 -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 TAA22686; Tue, 13 Oct 1998 19:21:00 +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 MAA14204; Tue, 13 Oct 1998 12:53:06 +0100 (BST) (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199810131153.MAA14204@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Richard Wackerbarth , fjaccard@urbanet.ch, current@FreeBSD.ORG Subject: Re: [GIMPS] /proc/net/route needed In-reply-to: Your message of "Mon, 12 Oct 1998 16:31:33 PDT." <199810122331.QAA00540@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Oct 1998 12:53:02 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >I can't imagine why a user-space application needs to access *routing* > > >information. Why not complain to the people that wrote it? Natd needs to know if the interface address changes (routing socket). Ppp wants to nuke all routes for a given interface when it goes away. > > >From what I know about the GIMPS project, it is probably attempting to > > determine if there is an active route to the outside. It does this so > > that it can decide whether, or not, to attempt to connect to its external > > server. > > > > I suspect that this was done to avoid bringing up a dialup connection, etc. > > Sorry, I'll try that again. I can't imagine why anyone would choose > this approach, which is clearly unnecessarily system-dependant. And doesn't work as dial-on-demand apps will have created the necessary routing entries and UPd the interface already. > -- > \\ 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 -- 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 Tue Oct 13 11:21:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25479 for freebsd-current-outgoing; Tue, 13 Oct 1998 11:21:30 -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 LAA25423 for ; Tue, 13 Oct 1998 11:21:24 -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 TAA22700; Tue, 13 Oct 1998 19:21:03 +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 JAA00674; Tue, 13 Oct 1998 09:43:48 +0100 (BST) (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199810130843.JAA00674@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: brian@Awfulhak.org, kjc@csl.sony.co.jp, current@FreeBSD.ORG Subject: Re: Improper sharing of modem bandwidth In-reply-to: Your message of "Tue, 13 Oct 1998 15:41:01 +1000." <199810130541.PAA12787@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Oct 1998 09:43:48 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Surely, once the packet queueing delay is reduced, we need to reduce > >the tty delay. The current kernel doesn't have ioctls for the > >buffer size but slip uses a smaller tty buffer and has a better > >response time than ppp. > > User ppp is behind a _lot_ of output buffering, including (at speeds >= > 57600 Kbps) a 4KB tty buffer (up from 2KB in FreeBSD-2.2). Perhaps the > increase from 2KB to 4KB is especially significant when the MTU is 1500. Heh, I *assumed* (yes, I know) that the tty buffer was around 128 or 256 bytes, but definitely less than 1500 !!! So in practice, in 3.0 with a 1500 MTU, we won't be able to skip ahead of the 4096 bytes (assuming a busy link) at the front of the queue. Without suspend/resume, we'll have to wait behind up to 1500 additional bytes (750 avg) and with suspend/resume we'd wait behind an additional 0 bytes and send 1 or 2 additional HDLC escape codes to do the suspend/resume. This gives a ~15% latency improvement, which isn't brilliant, but is better than nothing. If there was an ioctl to change the usable tty buffer size to less than 4k, ppp could set it to ``whatever the MTU is'' and get quite a reasonable interactive performance gain. > Kernel ppp doesn't have this problem. Kernel ppp also has a fast path > for incoming packets to avoid the average 5ms latency for polling the > pseudo-DMA input buffer. This only seems to be important for local > connections. > > Bruce -- 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 Tue Oct 13 11:56:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00768 for freebsd-current-outgoing; Tue, 13 Oct 1998 11:56:56 -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 LAA00762 for ; Tue, 13 Oct 1998 11:56:52 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id MAA10377; Tue, 13 Oct 1998 12:49:35 -0600 (MDT) Date: Tue, 13 Oct 1998 12:49:35 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199810131849.MAA10377@narnia.plutotech.com> To: Neil Blakey-Milner cc: current@FreeBSD.ORG Subject: Re: Some SCSI(?) problems whilst running SMP Newsgroups: pluto.freebsd.current In-Reply-To: <19981013134739.A26388@rucus.ru.ac.za> 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 > Ok, the problem is this: > > When we enable SMP support, within any time from an hour to 6 days, we will > die with SCSI errors - of late "SCB timeout handled by another timeout" I > think is the proferred explanation. The "death" seems to occur quickly after > extensive access to the disks, but it also just dies arbitrarily, usually > after the machine has been up for a few days. It doesn't seem to be specific > to any drive failing either. (we've swapped drives around, etc) Crap. I was hoping this problem had been resolved since the people who usually complain about it (Hi Mark M.!) have been silent in recent months. My guess is that the callout free list has become corrupted somehow, but I don't know enough about our SMP implementation to know where to start looking for re-entrancy problems. All reports I've seen of this problem have been only under SMP and I don't have any SMP equipment here in order to try and reproduce the problem with. Can you turn the printf in sys/dev/aic7xxx/aic7xxx.c:ahc_timeout() into a panic, drop into GDB, and examine the data structures in kern_timeout.c? -- 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 13 12:52:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10326 for freebsd-current-outgoing; Tue, 13 Oct 1998 12:52:46 -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 MAA10311 for ; Tue, 13 Oct 1998 12:52:39 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:akbs/1n0kPEY4dmbGVj9vEUQmp6VYftM@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id VAA09544; Tue, 13 Oct 1998 21:51:55 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810131951.VAA09544@gratis.grondar.za> To: "Justin T. Gibbs" cc: Neil Blakey-Milner , current@FreeBSD.ORG Subject: Re: Some SCSI(?) problems whilst running SMP In-Reply-To: Your message of " Tue, 13 Oct 1998 12:49:35 CST." <199810131849.MAA10377@narnia.plutotech.com> References: <199810131849.MAA10377@narnia.plutotech.com> Date: Tue, 13 Oct 1998 21:51:54 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Justin T. Gibbs" wrote: > Crap. I was hoping this problem had been resolved since the people who > usually complain about it (Hi Mark M.!) have been silent in recent months. I have been running in single-cpu mode to get Perl5 out. :-) (Hi!) > My guess is that the callout free list has become corrupted somehow, but > I don't know enough about our SMP implementation to know where to start > looking for re-entrancy problems. All reports I've seen of this problem > have been only under SMP and I don't have any SMP equipment here in order > to try and reproduce the problem with. Can you turn the printf in > sys/dev/aic7xxx/aic7xxx.c:ahc_timeout() into a panic, drop into GDB, and > examine the data structures in kern_timeout.c? I can still offer you a login on a box to do this if you like? I have the serial cable set up, and I've been practising doing this... 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 Tue Oct 13 13:21:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15505 for freebsd-current-outgoing; Tue, 13 Oct 1998 13:21:28 -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 NAA15491 for ; Tue, 13 Oct 1998 13:21:22 -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 NAA20169; Tue, 13 Oct 1998 13:20:56 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Christopher Masto cc: HighWind Software Information , current@FreeBSD.ORG Subject: Re: libc_r changes broke stuff. In-reply-to: Your message of "Tue, 13 Oct 1998 12:56:59 EDT." <19981013125659.A305@netmonger.net> Date: Tue, 13 Oct 1998 13:20:56 -0700 Message-ID: <20165.908310056@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are you using cvsup to get the full CVS tree or just -current? If the former , > $ cd /usr/src/... > $ cvs log file.c > $ cvs diff -r1.47 -r1.48 file.c > > Otherwise, use the excellent web interface at > http://www.freebsd.org/cgi/cvsweb.cgi As I just noted to the HighWind folks, there's also anoncvs as an option: finger anoncvs@anoncvs.freebsd.org for usage instructions. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 13:34:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18318 for freebsd-current-outgoing; Tue, 13 Oct 1998 13:34:08 -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 NAA18227 for ; Tue, 13 Oct 1998 13:33:56 -0700 (PDT) (envelope-from osa@serv.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 AAA05293 for ; Wed, 14 Oct 1998 00:33:40 +0400 (MSD) Received: by sunny.aha.ru id AAA24612; (8.8.8/vak/1.9) Wed, 14 Oct 1998 00:33:07 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma024530; Wed Oct 14 00:32:40 1998 Received: from ozz.etrust.ru by serv.etrust.ru with ESMTP id AAA02788; (8.9.1/vak/1.9) Wed, 14 Oct 1998 00:35:27 +0400 (MSD) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id AAA00749 for ; Wed, 14 Oct 1998 00:00:04 +0400 (MSD) (envelope-from osa@etrust.ru) Date: Wed, 14 Oct 1998 00:00:03 +0400 (MSD) From: oZZ!!! To: current@FreeBSD.ORG Subject: sb_reset_dsp failed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R X-MIME-Autoconverted: from 8bit to base64 by serv.etrust.ru id AAA02788 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by hub.freebsd.org id NAA18247 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I use FreeBSD-3.0-BETA-ELF with ELF-kernel. Yestarday, after cvsuped my system, i make world correctly & then recompile kernel. After reboot... # dmesg ...... sb_reset_dsp failed sb0 not found at 0x220 sb_reset_dsp failed sbxvi0 not found sbmidi not found at 0x330 ...... What does it mean? Some changes in kernel? 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 Tue Oct 13 13:34:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18418 for freebsd-current-outgoing; Tue, 13 Oct 1998 13:34:23 -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 NAA18380 for ; Tue, 13 Oct 1998 13:34:18 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id OAA10599; Tue, 13 Oct 1998 14:27:17 -0600 (MDT) Date: Tue, 13 Oct 1998 14:27:17 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199810132027.OAA10599@narnia.plutotech.com> To: Vijay Ramasubramanian cc: current@FreeBSD.ORG Subject: Re: Installation probs w/3.0-BETA Newsgroups: pluto.freebsd.current 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 > Panic: ufs_dirbad: bad dir > Syncing disks... 143 143 143 70 40 1 1 1 1 1 1 1 1 1 1 1 1 giving up > (da2:adv0:0:2:0): . CDB: 35 0 0 0 0 0 0 0 0 0 > (da2:adv0:0:2:0): ILLEGAL REQUEST asc: 20,0 > (da2:adv0:0:2:0): My guess would be bad RAM or cache. -- 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 13 13:46:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20192 for freebsd-current-outgoing; Tue, 13 Oct 1998 13:46:05 -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 NAA20171 for ; Tue, 13 Oct 1998 13:46:02 -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 PAA03986; Tue, 13 Oct 1998 15:45:47 -0500 (CDT) X-Authentication-Warning: eesn17.ews.uiuc.edu: ramasubr owned process doing -bs Date: Tue, 13 Oct 1998 15:45:47 -0500 (CDT) From: Vijay Ramasubramanian To: "Justin T. Gibbs" cc: current@FreeBSD.ORG Subject: Re: Installation probs w/3.0-BETA In-Reply-To: <199810132027.OAA10599@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, 13 Oct 1998, Justin T. Gibbs wrote: > My guess would be bad RAM or cache. That was one of my suspicions due to the circumstances. Do you (or anyone on the list) happen to know a good memory testing program to see if I can confirm this? I don't have spare RAM at my disposal that I can swap in to see if it fixes things. (Please CC replies regarding this message to me personally) .______ | 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 13 13:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20211 for freebsd-current-outgoing; Tue, 13 Oct 1998 13:46:09 -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 NAA20205 for ; Tue, 13 Oct 1998 13:46: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 NAA01261; Tue, 13 Oct 1998 13:50:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810132050.NAA01261@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Vijay Ramasubramanian cc: freebsd-current@FreeBSD.ORG Subject: Re: Installation probs w/3.0-BETA In-reply-to: Your message of "Tue, 13 Oct 1998 00:41:44 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Oct 1998 13:50:22 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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 ... > Drive 0 (IBM 2.2 GB): > > 400MB FAT16 (Windows 95 resides here) > Remainder FreeBSD FS, mount at: / > Leave MBR alone (I had planned on installing System Commander later) ... > I had planned to run the /var and /usr directories off the root FS > partition. ... > Once I get the installation via FTP started (from ftp.freebsd.org), it > progresses to 34% and then crashes. The progress bar reads "Extracting > bin into / directory..." > The stats bar at the bottom reads: "9438208 bytes read from bin dist, > chunk 40 of 116 @ 13.4kB/sec" > The error messages are as follows: > > Panic: ufs_dirbad: bad dir This is the principal problem. The filesystem that you're writing to is corrupted. The possible causes for this problem are: - Bad RAM (quite likely) - Bad cache (less likely, but still possible) - A bad disk (fairly unlikely) - A bug in the Advansys driver (possible, as it hasn't had much testing yet). > Syncing disks... 143 143 143 70 40 1 1 1 1 1 1 1 1 1 1 1 1 giving up > (da2:adv0:0:2:0): . CDB: 35 0 0 0 0 0 0 0 0 0 > (da2:adv0:0:2:0): ILLEGAL REQUEST asc: 20,0 > (da2:adv0:0:2:0): This is just the Fujitsu drive complaining about something; I suspect it's the Synchronise Cache command that we send before rebooting. It's irritating but quite harmless. > So, I tried yanking the Fujitsu and just installing the / FS to the 1st > IBM drive, and putting Swap on the 2nd drive. The installation then died > at 35% with the message: > > Panic: ffs_alloccg : bad map This is consistent again with filesystem corruption. > This may not be exactly the error message (the part after ffs_alloccg) as > the machine rebooted before I could get of the info, and I have no desire > to try a 15th installation attempt to get the message again. > > The hardware has been run under 95 so far without any problems, although > most people would probably say that running under 95 is not much of a test > of hardware. > > Can anyone tell me how to go about getting this resolved? > > If you think it may be bad hardware, can you suggest diagnostic-type > programs that I can test with? I have relatively limited hardware > resources, and can't do stuff like swapping out the CPU, RAM, etc. There's no really good RAM test, unfortunately. You might try some of the freebie ones floating around on the 'net, but these will quite often pass RAM as good when in fact it's not. The better ones will admit this in their documentation. Check you're not overclocking anything for starters, but bad RAM is the most likely problem. -- \\ 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 Tue Oct 13 14:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26616 for freebsd-current-outgoing; Tue, 13 Oct 1998 14:17:23 -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 OAA26611 for ; Tue, 13 Oct 1998 14:17:18 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id XAA14689 for current@freebsd.org; Tue, 13 Oct 1998 23:17:02 +0200 (CEST) (envelope-from sos) Message-Id: <199810132117.XAA14689@sos.freebsd.dk> Subject: MFS broken on SMP ?? To: current@FreeBSD.ORG (FreeBSD current) Date: Tue, 13 Oct 1998 23:17:02 +0200 (CEST) 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 I just tried using an MFS /tmp filesystem, and that breaks under a new (~2 hours ago) current with SMP. It makes various things like make the compiler etc segfault pretty quickly on a make -j8 world. I think I've run with a MFS /tmp before under SMP, so it might be a recent breakage..... Ideas? observations? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Tue Oct 13 14:25:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28647 for freebsd-current-outgoing; Tue, 13 Oct 1998 14:25:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28625 for ; Tue, 13 Oct 1998 14:24:57 -0700 (PDT) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.9.1/BNET-98/09/30-E) with ESMTP id OAA03399; Tue, 13 Oct 1998 14:24:32 -0700 (PDT) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with SMTP id OAA03452; Tue, 13 Oct 1998 14:20:03 -0700 (PDT) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id OAA09979; Tue, 13 Oct 1998 14:20:01 -0700 To: c5666305@b1.hkstar.com Cc: current@FreeBSD.ORG Subject: Re: does FreeBSD support DE660 PCMCIA card (DLink) In-Reply-To: Your message of "Tue, 13 Oct 1998 14:14:38 +0800 (HKT)" <199810130614.OAA11017@b1.hkstar.com> References: <199810130614.OAA11017@b1.hkstar.com> X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981013142000X.thomma@baynetworks.com> Date: Tue, 13 Oct 1998 14:20:00 -0700 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 33 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a little of off topic. I would like to know if freebsd suports > de660 PCMCIA card (Dlink). Please share your experience with me. Thanks. I use one of those cheap D-Link PCMCIA cards (I think it was $39 at Fry's) with a few weeks old -current. It works great. FTP gives me 600KB/sec off Compaq Aero 486sx/33MHz. I'm very pleased with it. # uname -a FreeBSD beagle.pochi.com 3.0-BETA FreeBSD 3.0-BETA #2: Mon Sep 28 15:55:29 PDT 1998 root@beagle.pochi.com:/usr/src/sys/compile/BEAGLE i386 # dmesg ... PC-Card VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 3 Initializing PC-card drivers: ed sio changing root device to wd0s1a Card inserted, slot 0 ffs_mountfs: superblock updated ffs_mountfs: superblock updated ed0: address 00:80:c8:89:44:4e, type NE2000 (16 bit) Here is from my /etc/pccard.conf. # D-Link DE-660 Ethernet Card card "D-Link" "DE-660" config 0x20 "ed0" 5 0x10 insert echo D-Link DE-660 inserted remove echo D-Link DE-660 removed Enjoy it. Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 14:31:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29968 for freebsd-current-outgoing; Tue, 13 Oct 1998 14:31:30 -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 OAA29958 for ; Tue, 13 Oct 1998 14:31:21 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id RAA06806; Tue, 13 Oct 1998 17:30:58 -0400 (EDT) Date: Tue, 13 Oct 1998 17:30:58 -0400 (EDT) Message-Id: <199810132130.RAA06806@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After lots of work a few months ago, we got all of our software working great under FreeBSD 3.0. In fact, it STILL works great.. That is, under: % uname -a FreeBSD zonda.highwind.com 3.0-19980831-SNAP FreeBSD 3.0-19980831-SNAP #0: Mon Aug 31 14:03:19 GMT 1998 root@make.ican.net:/usr/src/sys/compile/GENERIC i386 However, under the newer FreeBSD's it doesn't seem to work. Our application goes into 100% user space CPU and makes no progress. 3583 typhoond CALL sigprocmask(0x3,0) 3583 typhoond RET sigprocmask 0 3583 typhoond CALL sigprocmask(0x1,0) 3583 typhoond RET sigprocmask 0 3583 typhoond CALL gettimeofday(0x1574f4c,0) 3583 typhoond RET gettimeofday 0 3583 typhoond CALL setitimer(0x1,0x1574f54,0) 3583 typhoond RET setitimer 0 3583 typhoond CALL sigprocmask(0x3,0) 3583 typhoond RET sigprocmask 0 3583 typhoond CALL sigprocmask(0x1,0) 3583 typhoond RET sigprocmask 0 3583 typhoond CALL gettimeofday(0x1554f4c,0) 3583 typhoond RET gettimeofday 0 3583 typhoond CALL setitimer(0x1,0x1554f54,0) 3583 typhoond RET setitimer 0 (I'm fairly sure this is from uthread_kern.c) We are an "aout" binary and have even tried STATICALLY linking with our libc_r. It still goes into this loop. Any ideas what could have happened to cause this. It WAS working fine. Now, after a little progress, we get into an infinite loop. Typhoon uses lots of disk and network I/O. What could we have tripped on? Seems to me, statically linking in libc_r would have eliminated any of the recent changes in libc_r from blame. I'm a bit lost as to what to do. I guess we could upgrade our FreeBSD machine and begin banging our heads against the wall. I'm wondering if anyone on this list would have a guess as to what new changes to the kernel may have caused this. -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 13 14:39:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01898 for freebsd-current-outgoing; Tue, 13 Oct 1998 14:39:11 -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 OAA01850 for ; Tue, 13 Oct 1998 14:39:02 -0700 (PDT) (envelope-from osa@serv.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 BAA08689 for ; Wed, 14 Oct 1998 01:38:41 +0400 (MSD) Received: by sunny.aha.ru id BAA06178; (8.8.8/vak/1.9) Wed, 14 Oct 1998 01:38:03 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma006148; Wed Oct 14 01:37:45 1998 Received: from ozz.etrust.ru by serv.etrust.ru with ESMTP id BAA02884; (8.9.1/vak/1.9) Wed, 14 Oct 1998 01:40:33 +0400 (MSD) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id BAA00337 for ; Wed, 14 Oct 1998 01:31:52 +0400 (MSD) (envelope-from osa@etrust.ru) Date: Wed, 14 Oct 1998 01:31:51 +0400 (MSD) From: oZZ!!! To: current@FreeBSD.ORG Subject: Re: sb_reset_dsp failed 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, 14 Oct 1998, oZZ!!! wrote: > Hello! > I use FreeBSD-3.0-BETA-ELF with ELF-kernel. > Yestarday, after cvsuped my system, i make world correctly & then > recompile kernel. > After reboot... > # dmesg > ...... > sb_reset_dsp failed > sb0 not found at 0x220 > sb_reset_dsp failed > sbxvi0 not found > sbmidi not found at 0x330 > ...... > > What does it mean? > Some changes in kernel? Sorry. I today (14.10.1998, 01:10 MSD) cvsuped my souces & then recompile my kernel. Sound system work OK! 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 Tue Oct 13 14:44:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03187 for freebsd-current-outgoing; Tue, 13 Oct 1998 14:44:43 -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 OAA03144 for ; Tue, 13 Oct 1998 14:44:30 -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 HAA25030; Wed, 14 Oct 1998 07:14:05 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id HAA27873; Wed, 14 Oct 1998 07:13:59 +0930 (CST) Message-ID: <19981014071356.S21983@freebie.lemis.com> Date: Wed, 14 Oct 1998 07:13:56 +0930 From: Greg Lehey To: dg@root.com Cc: FreeBSD current users Subject: Re: 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_bio.c ... References: <199810131154.EAA12696@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810131154.EAA12696@implode.root.com>; from David Greenman on Tue, Oct 13, 1998 at 04:54:04AM -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 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. 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 Tue Oct 13 14:56:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05387 for freebsd-current-outgoing; Tue, 13 Oct 1998 14:56:10 -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 OAA05346 for ; Tue, 13 Oct 1998 14:56:02 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA05333; Wed, 14 Oct 1998 08:00:27 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810132200.IAA05333@cimlogic.com.au> Subject: Re: Recent 3.0's are Depressing In-Reply-To: <199810132130.RAA06806@highwind.com> from HighWind Software Information at "Oct 13, 98 05:30:58 pm" To: info@highwind.com (HighWind Software Information) Date: Wed, 14 Oct 1998 08:00:27 +1000 (EST) Cc: 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 HighWind Software Information wrote: > We are an "aout" binary and have even tried STATICALLY linking with our > libc_r. It still goes into this loop. > > Any ideas what could have happened to cause this. It WAS working fine. Now, > after a little progress, we get into an infinite loop. > > Typhoon uses lots of disk and network I/O. What could we have tripped on? > > Seems to me, statically linking in libc_r would have eliminated any of > the recent changes in libc_r from blame. > > I'm a bit lost as to what to do. I guess we could upgrade our FreeBSD > machine and begin banging our heads against the wall. > > I'm wondering if anyone on this list would have a guess as to what new > changes to the kernel may have caused this. The recent changes mostly affect signal handling with sigwait(). There was one change to the thread kernel, but I doubt that would be a problem. I don't see what a static link would buy you compared to a dynamic one. I also don't see what this has to do with the FreeBSD kernel since this is a user-space thread implementation. I suggest that you use CVSup's cvs mode to track the cvs repository and then checkout sources based on date to isolate which changes have bitten you. There are test programs in the tree that were submitted by the author of the signal handling changes. You should try to duplicate your problem using those tests. Providing a ktrace without a thread status dump is useless IMO. All that you've shown is that the thread scheduler can't find a thread to run. The thread status dump should tell you why. I explained that to you many months ago. -- 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 Tue Oct 13 15:13:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07319 for freebsd-current-outgoing; Tue, 13 Oct 1998 15:13:14 -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 PAA07309 for ; Tue, 13 Oct 1998 15:13:09 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id SAA07558; Tue, 13 Oct 1998 18:12:16 -0400 (EDT) Date: Tue, 13 Oct 1998 18:12:16 -0400 (EDT) Message-Id: <199810132212.SAA07558@highwind.com> From: HighWind Software Information To: jb@cimlogic.com.au CC: current@FreeBSD.ORG In-reply-to: <199810132200.IAA05333@cimlogic.com.au> (message from John Birrell on Wed, 14 Oct 1998 08:00:27 +1000 (EST)) Subject: Re: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The recent changes mostly affect signal handling with sigwait(). There was one change to the thread kernel, but I doubt that would be a problem. I don't see what a static link would buy you compared to a dynamic one. I also don't see what this has to do with the FreeBSD kernel since this is a user-space thread implementation. Hmm. Wouldn't statically linking OUR local libc_r into the application make it so the changes to libc_r at the customer site not effect us? Maybe I am missing something. I suggest that you use CVSup's cvs mode to track the cvs repository and then checkout sources based on date to isolate which changes have bitten you. There are test programs in the tree that were submitted by the author of the signal handling changes. You should try to duplicate your problem using those tests. Providing a ktrace without a thread status dump is useless IMO. All that you've shown is that the thread scheduler can't find a thread to run. The thread status dump should tell you why. I explained that to you many months ago. Can you review how to do that thread status dump again? I apologize for my ignorance. -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 13 15:14:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07629 for freebsd-current-outgoing; Tue, 13 Oct 1998 15:14:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.insolwwb.net (ns.insolwwb.net [206.31.149.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07624 for ; Tue, 13 Oct 1998 15:14:36 -0700 (PDT) (envelope-from mgrommet@insolwwb.net) Received: from work2.insolwwb.net (work2.insolwwb.net [208.150.248.12]) by ns.insolwwb.net (8.8.8/8.8.5) with SMTP id RAA22843 for ; Tue, 13 Oct 1998 17:06:39 -0500 (CDT) Message-ID: <00ca01bdf6f7$0a09a080$0cf896d0@work2.insolwwb.net> From: "Mike Grommet" To: Subject: Installation bugs 3.0BETA 10-09??? We need a can of RAID :) Date: Tue, 13 Oct 1998 17:15:51 -0500 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.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. running into some interesting problems trying to install 3.0 Beta, 10-09 release. A bit about the hardware in this machine... Pent II 350, Intel BX Chipset DPT Raid Controller (DPT PM3334UW) 128 Megs of ram, etc etc. I go in and dedicate a partition to freebsd... I then break the partition up into these chunks: 256 Megs / 512 Megs SWAP 1000 Megs /var 3200 Megs /usr/local 2400 Megs /usr basically all goes as normal until it tries to newfs the partitions... when it tries to newfs the first slice ( / filesystem) Debug reports "DEBUG: unknown major/minor for devtype -" it dies with a message on the debug console where it gives "Cross device link" error in newfs and then a rewrite label error. Install gives me an error message and then puts me back to the main install menu where I go through the procedure again. Now get this: The second time I go through all this, and the newfs takes place again, and while I get the "unknown major/minor for devtype" messages, the newfs works without any problems at all.. I just wanted to make sure you guys knew of this situation before the release date. Mike Grommet System Admin, and all around nice guy Internet Solutions, Inc. mgrommet@insolwwb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 15:16:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07856 for freebsd-current-outgoing; Tue, 13 Oct 1998 15:16:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07826; Tue, 13 Oct 1998 15:16:17 -0700 (PDT) (envelope-from son@cezanne.prism.uvsq.fr) Received: from cezanne.prism.uvsq.fr (rtc105.reseau.uvsq.fr [193.51.24.21]) by soleil.uvsq.fr (8.9.1/jtpda-5.3.1) with ESMTP id AAA03149 ; Wed, 14 Oct 1998 00:15:53 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.9.1/8.8.5) id XAA00421; Tue, 13 Oct 1998 23:52:47 GMT Message-ID: <19981013235246.02264@breizh.prism.uvsq.fr> Date: Tue, 13 Oct 1998 23:52:46 +0000 From: Nicolas Souchu To: Julian Elischer Cc: FreeBSD Hackers , -current , Luigi Rizzo , Roger Hardiman , Mike Smith , Marc Bouget Subject: Re: bktr over new I2C framework, ready References: <19981012195634.06516@breizh.prism.uvsq.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Julian Elischer on Mon, Oct 12, 1998 at 03:42:26PM -0700 X-Operating-System: FreeBSD breizh 3.0-BETA FreeBSD 3.0-BETA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 12, 1998 at 03:42:26PM -0700, Julian Elischer wrote: >yes but what IS it? > >I have an I2C device attached to some programmable pins >and I understand the protocol, >but 'bktr' means nothing to me.. What is it? > >julian > >On Mon, 12 Oct 1998, Nicolas Souchu wrote: > >> Hi there, >> >> bktr over the new I2C framework is now ready. Although, no man page is >> available :( This is my next priority. >> >> But it works. Ready to test it? >> >> -- Sorry, I'm not generous in details :) I2C is a very powerful and low-cost serial bus specified by Philips for multimedia purposes. A master chip on the bus controls slave chips (memories, voltage sensors, termometers, EEPROMs, batteries) with any byte oriented protocol. The System Management Bus found on laptops to control battery is an example of such protocols. Asus motherboards have monitoring capabilities (controling temperature, ventilators rotation speed) with rely on an I2C bus with the SMB protocol. I2C may be controled by hardware (writing to regiters to send bytes on the bus) or by software (twiggling line directly) bktr is the driver of the Brooktree848 video chipset found for example on TV video cards. The bt848 chip has I2C capabilities on-chip to control tuners, sound processors... the bt848 has both software and hardware capabilities. I2C busses are growing like mushrooms. Since the 430TX, Intel incorporates I2C to its chips. The Apollo, Aladdin chipsets may act as master over an I2C bus too. The idea of the FreeBSD I2C system is to offer a general purpose framework in order to avoid rewritting i2c common functions in every driver and propose for example generic i/o for any card that has an external I2C connector. bktr now relies on the new I2C framework. Other drivers that use I2C protocol should too. I'm about to write manpages and gather some urls on a web page. Nicolas. -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PCs into workstations - 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 13 15:17:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08039 for freebsd-current-outgoing; Tue, 13 Oct 1998 15:17: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 PAA08033 for ; Tue, 13 Oct 1998 15:17:50 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA05402; Wed, 14 Oct 1998 08:22:24 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810132222.IAA05402@cimlogic.com.au> Subject: Re: Recent 3.0's are Depressing In-Reply-To: <199810132212.SAA07558@highwind.com> from HighWind Software Information at "Oct 13, 98 06:12:16 pm" To: info@highwind.com (HighWind Software Information) Date: Wed, 14 Oct 1998 08:22:24 +1000 (EST) Cc: jb@cimlogic.com.au, 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 HighWind Software Information wrote: > Hmm. Wouldn't statically linking OUR local libc_r into the application > make it so the changes to libc_r at the customer site not effect us? > Maybe I am missing something. Ah, sorry. Yes _customer_ site changes would be ruled out by that. I thought you were meaning your development system. Are you saying that you can't duplicate the customer's problem on your system? > I suggest that you use CVSup's cvs mode to track the cvs repository and > then checkout sources based on date to isolate which changes have bitten > you. There are test programs in the tree that were submitted by the author > of the signal handling changes. You should try to duplicate your problem > using those tests. Providing a ktrace without a thread status dump is > useless IMO. All that you've shown is that the thread scheduler can't > find a thread to run. The thread status dump should tell you why. I explained > that to you many months ago. > > Can you review how to do that thread status dump again? I apologize for my > ignorance. Send the application a SIGINFO, then look in /tmp/uthread.dump. If necessary, add a diagnostic thread to check that it gets scheduled and to look at the threads that are blocked. -- 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 Tue Oct 13 15:23:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08850 for freebsd-current-outgoing; Tue, 13 Oct 1998 15:23:53 -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 PAA08841 for ; Tue, 13 Oct 1998 15:23:48 -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 HAA25174; Wed, 14 Oct 1998 07:53:18 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id HAA27965; Wed, 14 Oct 1998 07:53:11 +0930 (CST) Message-ID: <19981014075310.V21983@freebie.lemis.com> Date: Wed, 14 Oct 1998 07:53:10 +0930 From: Greg Lehey To: Peter Wemm , Studded Cc: Mike Smith , Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: ELF kernels (was: Make elf release) References: <3622D416.E2E627AC@gorean.org> <199810130909.RAA29552@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810130909.RAA29552@spinner.netplex.com.au>; from Peter Wemm on Tue, Oct 13, 1998 at 05:09:30PM +0800 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, 13 October 1998 at 17:09:30 +0800, Peter Wemm wrote: > Studded wrote: >> Mike Smith wrote: >> >>> There's some (understandable) resistance to putting an ELF kernel in >>> 3.0, so the changeover will probably happen a few weeks afterwards. At >>> that stage we'll shift to the new bootloader as well. >> >> I still think getting the pain over now is a good idea. Leaving a major >> change for after the "release" will just postpone by one more quarter >> the time when 3.0 has a chance of being stable. > > Unfortunately, I agree, in part at least. The biggest difficulty in doing > a changeover is upgrading the stage2 bootblocks. If we get the 3.0 CD > installing ELF-capable bootblocks (even if it's a hacked biosboot), then > it's going to make the transition *so* much easier. It's not a question > of flipping a switch, we've got to get the bootblocks upgraded. If we > could get the 3.0 release sysinstall to do this for us it would be a big > win. > > Ideally there should be a choice in sysinstall, and sysinstall could > change them on the fly. If somebody installed a system and the new > bootblocks didn't work, it'd be nice if it was as simple as booting the > floppy and downgrading to the older system. > > IMHO, whether /kernel is a.out or elf is far less of an issue than which > bootblocks we use. I'm not sure whether you're talking about the same issue that Doug (Studded) is. I think moving to an ELF kernel 2 days before code freeze would be a disaster. It would certainly reduce functionality by the number of LKMs which haven't been converted to KLDs, and would presumably add opportunities for bugs in that area. 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 Tue Oct 13 15:37:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11321 for freebsd-current-outgoing; Tue, 13 Oct 1998 15:37:08 -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 PAA11314 for ; Tue, 13 Oct 1998 15:37:04 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id SAA07644; Tue, 13 Oct 1998 18:36:10 -0400 (EDT) Date: Tue, 13 Oct 1998 18:36:10 -0400 (EDT) Message-Id: <199810132236.SAA07644@highwind.com> From: HighWind Software Information To: jb@cimlogic.com.au CC: jb@cimlogic.com.au, current@FreeBSD.ORG In-reply-to: <199810132222.IAA05402@cimlogic.com.au> (message from John Birrell on Wed, 14 Oct 1998 08:22:24 +1000 (EST)) Subject: Re: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HighWind Software Information wrote: > Hmm. Wouldn't statically linking OUR local libc_r into the application > make it so the changes to libc_r at the customer site not effect us? > Maybe I am missing something. Ah, sorry. Yes _customer_ site changes would be ruled out by that. I thought you were meaning your development system. Are you saying that you can't duplicate the customer's problem on your system? That is correct. It works like a charm at our site. At 2 different customer sites (both running recent 3.0's), it gets into this problem. At customers running older 3.0 SNAPSHOT's, it works fine. Quite frustrating. Send the application a SIGINFO, then look in /tmp/uthread.dump. We'll get this. -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 13 16:08:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16676 for freebsd-current-outgoing; Tue, 13 Oct 1998 16:08:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rain.futuresouth.com (rain.futuresouth.com [198.79.79.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16653 for ; Tue, 13 Oct 1998 16:08:20 -0700 (PDT) (envelope-from stormy@rain.futuresouth.com) Received: (from stormy@localhost) by rain.futuresouth.com (8.8.8/8.8.8) id SAA05067 for freebsd-current@FreeBSD.ORG; Tue, 13 Oct 1998 18:08:03 -0500 (CDT) (envelope-from stormy) Message-ID: <19981013180803.B5026@futuresouth.com> Date: Tue, 13 Oct 1998 18:08:03 -0500 From: Stormy Henderson To: freebsd-current@FreeBSD.ORG Subject: Re: Installation bugs 3.0BETA 10-09??? We need a can of RAID :) Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <00ca01bdf6f7$0a09a080$0cf896d0@work2.insolwwb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <00ca01bdf6f7$0a09a080$0cf896d0@work2.insolwwb.net>; from Mike Grommet on Tue, Oct 13, 1998 at 05:15:51PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A happy camper (Mike Grommet, mgrommet@insolwwb.net) once wrote... > 3.0 Beta, 10-09 release. > Debug reports "DEBUG: unknown major/minor for devtype -" it dies with a > message on the debug console where it gives "Cross device link" error in > newfs and then a rewrite label error. I got the same "Cross device link" as well, with an earlier BETA. Changing the order in which I declared my slices fixed it (root first instead of swap, or was it the other way around...). Be happy... -- http://www.futuresouth.com/~stormy/signature.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 16:34:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20884 for freebsd-current-outgoing; Tue, 13 Oct 1998 16:34:01 -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 QAA20837 for ; Tue, 13 Oct 1998 16:33:57 -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 QAA04981; Tue, 13 Oct 1998 16:33:20 -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 QAA18796; Tue, 13 Oct 1998 16:33:19 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id QAA16875; Tue, 13 Oct 1998 16:33:17 -0700 (PDT) From: Don Lewis Message-Id: <199810132333.QAA16875@salsa.gv.tsc.tdk.com> Date: Tue, 13 Oct 1998 16:33:17 -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 13, 5:13pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Bruce Evans , Don.Lewis@tsc.tdk.com, jb@cimlogic.com.au 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 13, 5:13pm, 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 16:36:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21489 for freebsd-current-outgoing; Tue, 13 Oct 1998 16:36:55 -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 QAA21474 for ; Tue, 13 Oct 1998 16:36:49 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id BAA23134; Wed, 14 Oct 1998 01:35:34 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Wed, 14 Oct 1998 01:35:33 +0200 (MET DST) Mime-Version: 1.0 To: Greg Lehey Cc: Peter Wemm , Studded , Mike Smith , Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: Re: ELF kernels (was: Make elf release) References: <3622D416.E2E627AC@gorean.org> <199810130909.RAA29552@spinner.netplex.com.au> <19981014075310.V21983@freebie.lemis.com> 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: 14 Oct 1998 01:35:32 +0200 In-Reply-To: Greg Lehey's message of "Wed, 14 Oct 1998 07:53:10 +0930" Message-ID: Lines: 16 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 QAA21479 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > On Tuesday, 13 October 1998 at 17:09:30 +0800, Peter Wemm wrote: > > IMHO, whether /kernel is a.out or elf is far less of an issue than which > > bootblocks we use. > I'm not sure whether you're talking about the same issue that Doug > (Studded) is. I think moving to an ELF kernel 2 days before code > freeze would be a disaster. ...but switching to Elf-aware boot blocks would not affect the kernel, and would make a later transition to an Elf kernel less painful for those who install 3.0-RELEASE from scratch. I think this is what Peter meant. 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 Tue Oct 13 16:49:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23212 for freebsd-current-outgoing; Tue, 13 Oct 1998 16:49:23 -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 QAA23196 for ; Tue, 13 Oct 1998 16:49:17 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id JAA05710; Wed, 14 Oct 1998 09:51:12 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810132351.JAA05710@cimlogic.com.au> Subject: Re: ELF kernels (was: Make elf release) In-Reply-To: from =?ISO-8859-1?Q?Dag=2DErling_C=2E_Sm=F8rgrav?= at "Oct 14, 98 01:35:32 am" To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Wed, 14 Oct 1998 09:51:12 +1000 (EST) Cc: grog@lemis.com, peter@netplex.com.au, Studded@gorean.org, mike@smith.net.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=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: > Greg Lehey writes: > > On Tuesday, 13 October 1998 at 17:09:30 +0800, Peter Wemm wrote: > > > IMHO, whether /kernel is a.out or elf is far less of an issue than which > > > bootblocks we use. > > I'm not sure whether you're talking about the same issue that Doug > > (Studded) is. I think moving to an ELF kernel 2 days before code > > freeze would be a disaster. > > ...but switching to Elf-aware boot blocks would not affect the kernel, > and would make a later transition to an Elf kernel less painful for > those who install 3.0-RELEASE from scratch. I think this is what Peter > meant. We shouldn't release code that *most* developers haven't had a chance to run. Let people run the code for a month before even considering putting it in a release. -- 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 Tue Oct 13 17:05:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26587 for freebsd-current-outgoing; Tue, 13 Oct 1998 17:05:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from qix (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26383; Tue, 13 Oct 1998 17:04:16 -0700 (PDT) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix (8.9.1/8.8.7) id CAA08410; Wed, 14 Oct 1998 02:04:31 +0200 (MET DST) Date: Wed, 14 Oct 1998 02:04:31 +0200 (MET DST) Message-Id: <199810140004.CAA08410@qix> From: Jean-Marc Zucconi To: sos@FreeBSD.ORG CC: current@FreeBSD.ORG In-reply-to: <199810132117.XAA14689@sos.freebsd.dk> Subject: Re: MFS broken on SMP ?? X-Mailer: Emacs Mime-Version: 1.0 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 RAA26579 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> SЬren writes: > I just tried using an MFS /tmp filesystem, and that breaks under a > new (~2 hours ago) current with SMP. It makes various things like > make the compiler etc segfault pretty quickly on a make -j8 world. > I think I've run with a MFS /tmp before under SMP, so it might be > a recent breakage..... > Ideas? observations? It works for me (make buildworld took 52 minutes with -j8). My kernel is from saturday. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@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 13 17:27:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01116 for freebsd-current-outgoing; Tue, 13 Oct 1998 17:27:41 -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 RAA01096 for ; Tue, 13 Oct 1998 17:27:34 -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 HAA02821; Wed, 14 Oct 1998 07:59:24 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810132359.HAA02821@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Karl Pielorz cc: Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release In-reply-to: Your message of "Tue, 13 Oct 1998 14:24:26 +0100." <3623548A.E4A9FE0F@tdx.co.uk> Date: Wed, 14 Oct 1998 07:59:23 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Pielorz wrote: > > > Edwin Culp wrote: > > > > I know that's one of the reasons why I've left my system running a.out ke rnels > > > at the moment... (and I at least hope it's a good reason ;-) > > > > > > Karl > > > > The wonderful part of it is that I haven't had anything to debug :-) What % of > > the folks running current/beta debug their kernels? The way to find the p roblems > > is to have more people using it in its most complete form. IMO. > > Hmmm.. Well if I'm right about not being able to debug LDK's with an ELF > kernel, I have to keep my kernel a.out... An LKM I'm betaing has a few > problems, which means it's gotta be debug(able)... Umm, it's the other way around.. DDB can't see a.out LKM's for debugging. DDB *can* see both a.out and elf KLD modules. KLD modules are the first time that DDB has worked with modular kernels. It's GDB that is the problem - it can't see KLD modules. Mind you, it can't see LKM's either. > Karl > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 17:47:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03472 for freebsd-current-outgoing; Tue, 13 Oct 1998 17:47:00 -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 RAA03442; Tue, 13 Oct 1998 17:46:56 -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 RAA00288; Tue, 13 Oct 1998 17:46:40 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <4.1.19981013171511.00a2b100@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 13 Oct 1998 17:46:39 -0700 To: current@FreeBSD.ORG From: Manfred Antar Subject: Panic when rebooting with current kernel Cc: smp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For the past day every time I reboot (shutdown -r now) I get boot called on cpu#0 syncing disks... 3 done panic: rslock: cpu: 1, addr:0xf5b49f88, lock: 0x01000001 mp_lock = 01000001; cpuid = 1; lapic.id = 0c000000 Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.98 This happens with both aout and elf kernels. This is an SMP Intel PR440FX with a DPT (no-raid) controller. The sources are current as 5pm Oct 13 PDT. A kernel from 24 hours ago works fine. There were alot of changes to the sys tree in the past day. I try backing out to 1 day ago. And see if i can find the change that caused this 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 Tue Oct 13 17:57:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05487 for freebsd-current-outgoing; Tue, 13 Oct 1998 17:57:16 -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 RAA05445 for ; Tue, 13 Oct 1998 17:57: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 RAA20027; Tue, 13 Oct 1998 17:56:09 -0700 (PDT) (envelope-from jdp) Message-Id: <199810140056.RAA20027@austin.polstra.com> To: peter@netplex.com.au Subject: Re: Make elf release In-Reply-To: <199810132359.HAA02821@spinner.netplex.com.au> References: <199810132359.HAA02821@spinner.netplex.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 13 Oct 1998 17:56:09 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199810132359.HAA02821@spinner.netplex.com.au>, Peter Wemm wrote: > It's GDB that is the problem - it can't see KLD modules. Mind you, it > can't see LKM's either. Just to clarify -- GDB can see them if you tell it where they are. For example, if I wanted to debug the star saver, I'd first run modstat to find out where it's loaded: Type Id Off Loadaddr Size Info Rev Module Name MISC 0 0 f2fe0000 0008 f2fe1000 1 star_saver_mod Then in GDB, I'd say: add-symbol-file /lkm/star_saver_mod.o 0xf2fe0020 Note, I had to add 0x20 to the load address to account for the size of the a.out header. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 18:15:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08774 for freebsd-current-outgoing; Tue, 13 Oct 1998 18:15:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08751; Tue, 13 Oct 1998 18:14:56 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id SAA09441; Tue, 13 Oct 1998 18:14:40 -0700 (PDT) Date: Tue, 13 Oct 1998 18:14:40 -0700 (PDT) From: Chris Timmons To: Manfred Antar cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Panic when rebooting with current kernel In-Reply-To: <4.1.19981013171511.00a2b100@192.168.0.1> 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've filed this as kern/8309, which contains a trace (I have a core, -g'd kernel and the aout gdb if anybody wants them :) I will say that this was the first time I built a kernel slightly out of sync with the world, so I am going to go back and do that to make sure there isn't something goofy in that regard. -Chris On Tue, 13 Oct 1998, Manfred Antar wrote: > For the past day every time I reboot (shutdown -r now) I get > > boot called on cpu#0 > > > syncing disks... 3 done > panic: rslock: cpu: 1, addr:0xf5b49f88, lock: 0x01000001 > mp_lock = 01000001; cpuid = 1; lapic.id = 0c000000 > Debugger("panic") > Stopped at Debugger+0x35: movb $0,in_Debugger.98 > > This happens with both aout and elf kernels. > This is an SMP Intel PR440FX with a DPT (no-raid) controller. > The sources are current as 5pm Oct 13 PDT. > A kernel from 24 hours ago works fine. There were alot of changes > to the sys tree in the past day. I try backing out to 1 day ago. > And see if i can find the change that caused this > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 18:32:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11278 for freebsd-current-outgoing; Tue, 13 Oct 1998 18:32:38 -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 SAA11248; Tue, 13 Oct 1998 18:32:34 -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 DAA14893; Wed, 14 Oct 1998 03:32:18 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id DAA29240; Wed, 14 Oct 1998 03:32:17 +0200 (MET DST) Message-ID: <19981014033216.03772@follo.net> Date: Wed, 14 Oct 1998 03:32:16 +0200 From: Eivind Eklund To: Chris Timmons , Manfred Antar Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Panic when rebooting with current kernel References: <4.1.19981013171511.00a2b100@192.168.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Chris Timmons on Tue, Oct 13, 1998 at 06:14:40PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 13, 1998 at 06:14:40PM -0700, Chris Timmons wrote: > > I've filed this as kern/8309, which contains a trace (I have a core, -g'd > kernel and the aout gdb if anybody wants them :) > > I will say that this was the first time I built a kernel slightly out of > sync with the world, so I am going to go back and do that to make sure > there isn't something goofy in that regard. You're not supposed to be able to trigger a panic() by being out of sync, so it is a bug no matter what. 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 13 18:36:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11980 for freebsd-current-outgoing; Tue, 13 Oct 1998 18:36:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11957 for ; Tue, 13 Oct 1998 18:36:33 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id SAA10425; Tue, 13 Oct 1998 18:36:16 -0700 (PDT) Date: Tue, 13 Oct 1998 18:36:16 -0700 (PDT) From: Chris Timmons To: Manfred Antar cc: current@FreeBSD.ORG Subject: Re: Panic when rebooting with current kernel In-Reply-To: <4.1.19981013171511.00a2b100@192.168.0.1> 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 Ugh, it is much worse than I first thought. I had it happen while unmounting a file system :( -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 18:37:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12057 for freebsd-current-outgoing; Tue, 13 Oct 1998 18:37:25 -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 SAA12050 for ; Tue, 13 Oct 1998 18:37:21 -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 LAA25876; Wed, 14 Oct 1998 11:06:30 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA28192; Wed, 14 Oct 1998 11:06:24 +0930 (CST) Message-ID: <19981014110624.Y21983@freebie.lemis.com> Date: Wed, 14 Oct 1998 11:06:24 +0930 From: Greg Lehey To: =?iso-8859-1?Q?Dag-Erling_C=2E_Sm=F8rgrav_?= Cc: Peter Wemm , Studded , Mike Smith , Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: Re: ELF kernels (was: Make elf release) References: <3622D416.E2E627AC@gorean.org> <199810130909.RAA29552@spinner.netplex.com.au> <19981014075310.V21983@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91.1i In-Reply-To: =?iso-8859-1?Q?=3Cxzpk924nigr=2Efsf=40hrotti=2Eifi=2Euio=2Eno=3E=3B_from?= =?iso-8859-1?Q?_Dag-Erling_C=2E_Sm=F8rgrav__on_Wed=2C_Oct_14=2C_1998_at_?= =?iso-8859-1?Q?01:35:32AM_+0200?= 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 1:35:32 +0200, Dag-Erling C. SmЬrgrav wrote: > Greg Lehey writes: >> On Tuesday, 13 October 1998 at 17:09:30 +0800, Peter Wemm wrote: >>> IMHO, whether /kernel is a.out or elf is far less of an issue than which >>> bootblocks we use. >> I'm not sure whether you're talking about the same issue that Doug >> (Studded) is. I think moving to an ELF kernel 2 days before code >> freeze would be a disaster. > > ...but switching to Elf-aware boot blocks would not affect the kernel, > and would make a later transition to an Elf kernel less painful for > those who install 3.0-RELEASE from scratch. I think this is what Peter > meant. Yes, I agree, I think that's what Peter meant. I don't think it's what Doug meant. 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 Tue Oct 13 18:40:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12570 for freebsd-current-outgoing; Tue, 13 Oct 1998 18:40:24 -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 SAA12493 for ; Tue, 13 Oct 1998 18:40:12 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA26615; Tue, 13 Oct 1998 18:39:53 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd026574; Tue Oct 13 18:39:45 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA22444; Tue, 13 Oct 1998 18:39:42 -0700 (MST) From: Terry Lambert Message-Id: <199810140139.SAA22444@usr08.primenet.com> Subject: Re: inetd is ill? syslogd is anemic? To: alk@pobox.com Date: Wed, 14 Oct 1998 01:39:42 +0000 (GMT) Cc: wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG In-Reply-To: <13854.56585.707371.316487@avalon.east> from "Tony Kimball" at Oct 9, 98 11:06:40 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 > : > This has been occurring for almost a week -- of a sudden, I get a few > : > hundred of these: > : > Oct 9 12:30:22 avalon /kernel: pid 756 (inetd), uid 0: exited on signal 11 > : > : Buy more memory. > > I don't believe it. There is more than 100MB of swap free at this point, > and it is still happening. Actually, I have seen this with relatively high repeatability on a 486DX clock multiplied box. And no, I'm not running APM + PHK's clock stuff that causes "CALCRU, negative time" errors. I was very happy, actually, to see someone else reporting the problem. Likewise on the boxes I can repeat it on, there is *not* a low memory condition. 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 Tue Oct 13 18:52:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14380 for freebsd-current-outgoing; Tue, 13 Oct 1998 18:52:50 -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 SAA14375 for ; Tue, 13 Oct 1998 18:52:46 -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 LAA25948; Wed, 14 Oct 1998 11:22:22 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA28291; Wed, 14 Oct 1998 11:22:20 +0930 (CST) Message-ID: <19981014112220.A21983@freebie.lemis.com> Date: Wed, 14 Oct 1998 11:22:20 +0930 From: Greg Lehey To: Peter Wemm , Karl Pielorz Cc: Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release References: <3623548A.E4A9FE0F@tdx.co.uk> <199810132359.HAA02821@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810132359.HAA02821@spinner.netplex.com.au>; from Peter Wemm on Wed, Oct 14, 1998 at 07:59:23AM +0800 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 [Format autorecovered at freebie.lemis.com] On Wednesday, 14 October 1998 at 7:59:23 +0800, Peter Wemm wrote: > Karl Pielorz wrote: >> Edwin Culp wrote: >>>> I know that's one of the reasons why I've left my system running a.out kernels >>>> at the moment... (and I at least hope it's a good reason ;-) >>> >>> The wonderful part of it is that I haven't had anything to debug :-) What of >>> the folks running current/beta debug their kernels? The way to find the p roblems >>> is to have more people using it in its most complete form. IMO. >> >> Hmmm.. Well if I'm right about not being able to debug LDK's with an ELF >> kernel, I have to keep my kernel a.out... An LKM I'm betaing has a few >> problems, which means it's gotta be debug(able)... > > Umm, it's the other way around.. DDB can't see a.out LKM's for debugging. > DDB *can* see both a.out and elf KLD modules. KLD modules are the first > time that DDB has worked with modular kernels. Does this mean that there's the potential to have symbol conflicts? > It's GDB that is the problem - it can't see KLD modules. Mind you, it > can't see LKM's either. That's not correct. Here's a backtrace through the Vinum LKM: (kgdb) bt #0 Debugger (msg=0xf5b8cfe0 "vinum debug") at ../../i386/i386/db_interface.c:317 #1 0xf5b8d2d6 in vinumioctl (dev=0x40001900, cmd=0xc008464b, data=0xf5b4aed0 "", flag=0x3, p=0xf5a2bbc0) at vinumioctl.c:107 #2 0xf016f44b in spec_ioctl (ap=0xf5b4ae0c) at ../../miscfs/specfs/spec_vnops.c:425 #3 0xf016ed29 in spec_vnoperate (ap=0xf5b4ae0c) at ../../miscfs/specfs/spec_vnops.c:129 #4 0xf01da0d9 in ufs_vnoperatespec (ap=0xf5b4ae0c) at ../../ufs/ufs/ufs_vnops.c:2303 Sure, there are some tricks needed to do this--see ftp://ftp.lemis.com/pub/vinum/.gdbinit for details. 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 Tue Oct 13 18:55:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14777 for freebsd-current-outgoing; Tue, 13 Oct 1998 18:55: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 SAA14701; Tue, 13 Oct 1998 18:54:19 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA02117; Tue, 13 Oct 1998 18:54:00 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd002095; Tue Oct 13 18:53:54 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA23147; Tue, 13 Oct 1998 18:53:49 -0700 (MST) From: Terry Lambert Message-Id: <199810140153.SAA23147@usr08.primenet.com> Subject: Re: inetd is ill? syslogd is anemic? To: eivind@yes.no (Eivind Eklund) Date: Wed, 14 Oct 1998 01:53:49 +0000 (GMT) Cc: alk@pobox.com, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG, dg@FreeBSD.ORG In-Reply-To: <19981010200607.56951@follo.net> from "Eivind Eklund" at Oct 10, 98 08:06:07 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 > > I don't believe it. There is more than 100MB of swap free at this point, > > and it is still happening. > > This is a known, OLD bug. It was one of the bugs introduced or > exposed by John Dysons changes to the VM system. He was working on > this at the time he left, if I understood correctly. > > In some cases, the VM system goes awry when you go out of memory. > This seems especially common if it is netscape that eats the memory > (don't ask me why; possibly it only seems that way because Netscape > eating the memory iss the most common situation on my box). The systems I run into this on are not even running X, let alone Netscape. They are also nowhere near exhausing memory. I agree that the bug came in in John Dyson's VM patches to 2.2.6-stable and -current (i.e., 2.2.7-release and -current are both affected). Modifying the trap_pfault() code in /sys/i386/i386/trap.c to cause a kernel panic, and then post-morteming the system dump image shows that, in fact, the page being referenced is not there, even though it's in the map. I haven't gone after it hard yet, having little incentive, but it seems to me that my page insertion DIAGNOSTIC patch would perhaps be useful (no, I haven't run it on a machine with the problem, since I don't have the problem on my machines at home, and I haven't run with the diagnostics on the machines that show that particular problem at work). > In these cases, at least sendmail, inetd and syslog will have problems > when forking - they'll get a sig11 right after the fork (I don't know > how 'right after' translates, sorry - timewise, it is just about at > once). Yeah, this is a sperate problem, in that it goes over the top of the list before it checks to see if it would be bad to go over the top of the list. This would take a bit of work to set right, and if you just install enough swap, it's not a problem. This is basically an unrelated bug having to do with a page being reused when there are zero pages available. It's prretty easy to see the bug just by looking at the code and "playing computer". > I can try to reproduce it if somebody that know more about the VM > system than me has some clues as to what I should do to track it down > - in that case, I'd like to get the clues by tomorrow (so I can spend > tomorrow attempt to find it; I most likely don't have time between > then and the release). Try the panic on SIGSEGV condition. It's informative. It would problably be informative for the out of memory bug, as well, but all you really have to do is look at the page table allocation vs. the backing page fill in the case of the /sys/vm/swap_pager.c code to see the memory exhaustion screwup bug. 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 Tue Oct 13 18:56:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15123 for freebsd-current-outgoing; Tue, 13 Oct 1998 18:56:20 -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 SAA15112 for ; Tue, 13 Oct 1998 18:56: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 LAA25960; Wed, 14 Oct 1998 11:25:59 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA28303; Wed, 14 Oct 1998 11:25:58 +0930 (CST) Message-ID: <19981014112557.B21983@freebie.lemis.com> Date: Wed, 14 Oct 1998 11:25:57 +0930 From: Greg Lehey To: John Polstra , peter@netplex.com.au Cc: current@FreeBSD.ORG Subject: Re: Make elf release References: <199810132359.HAA02821@spinner.netplex.com.au> <199810140056.RAA20027@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810140056.RAA20027@austin.polstra.com>; from John Polstra on Tue, Oct 13, 1998 at 05:56:09PM -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 Tuesday, 13 October 1998 at 17:56:09 -0700, John Polstra wrote: > In article <199810132359.HAA02821@spinner.netplex.com.au>, > Peter Wemm wrote: > >> It's GDB that is the problem - it can't see KLD modules. Mind you, it >> can't see LKM's either. > > Just to clarify -- GDB can see them if you tell it where they are. > For example, if I wanted to debug the star saver, I'd first run > modstat to find out where it's loaded: > > Type Id Off Loadaddr Size Info Rev Module Name > MISC 0 0 f2fe0000 0008 f2fe1000 1 star_saver_mod > > Then in GDB, I'd say: > > add-symbol-file /lkm/star_saver_mod.o 0xf2fe0020 > > Note, I had to add 0x20 to the load address to account for the size > of the a.out header. OK, you've shown yours, I'll show mine. Here's a gdb macro/function/whatever that accesses this same information internally: def tr if (lkmods[0].area != 0) printf " asf 0x%x\n", lkmods[0].area add-symbol-file /T/vinum/cybernet/vinum_mod.o lkmods[0].area + 0x20 end 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 Tue Oct 13 18:57:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15242 for freebsd-current-outgoing; Tue, 13 Oct 1998 18:57:54 -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 SAA15234 for ; Tue, 13 Oct 1998 18:57:52 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA03441; Tue, 13 Oct 1998 18:57:38 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd003345; Tue Oct 13 18:57:33 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA23385; Tue, 13 Oct 1998 18:57:27 -0700 (MST) From: Terry Lambert Message-Id: <199810140157.SAA23385@usr08.primenet.com> Subject: Re: /usr/include/sys/cam/scsi... To: garbanzo@hooked.net (Alex) Date: Wed, 14 Oct 1998 01:57:26 +0000 (GMT) Cc: perlsta@fs3.ny.genx.net, current@FreeBSD.ORG In-Reply-To: from "Alex" at Oct 10, 98 02:07:54 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 > > a lot of applications broke during compile just because of the renameing. > > when the scsi.h was replaced by cam/scsi_all.h it compiled and worked, > > notably kscd (the kde CD player) > > This kinda piqued my interest, I've been cvsuping and making world, but > I'm still left with a scsi.h, and a bunch of header files in /usr/include > with old datestamps. How can I tell what files should have been cleaned > out? Use the "-P" option to CVS to prune "empty" (gone to the attic) directories (NOTE: will delete things that I personally don't want deleted out of my tree, like LFS!!!). Save the output of a CVS update. The files which are "not in the tree" will show up with "?" to the left of them. 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 Tue Oct 13 18:59:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15529 for freebsd-current-outgoing; Tue, 13 Oct 1998 18:59:20 -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 SAA15517 for ; Tue, 13 Oct 1998 18:59:17 -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 SAA20555; Tue, 13 Oct 1998 18:58:29 -0700 (PDT) (envelope-from jdp) Message-Id: <199810140158.SAA20555@austin.polstra.com> To: Greg Lehey cc: peter@netplex.com.au, current@FreeBSD.ORG Subject: Re: Make elf release In-reply-to: Your message of "Wed, 14 Oct 1998 11:25:57 +0930." <19981014112557.B21983@freebie.lemis.com> Date: Tue, 13 Oct 1998 18:58:29 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, you've shown yours, I'll show mine. Here's a gdb > macro/function/whatever that accesses this same information > internally: > > def tr > if (lkmods[0].area != 0) > printf " asf 0x%x\n", lkmods[0].area > add-symbol-file /T/vinum/cybernet/vinum_mod.o lkmods[0].area + 0x20 > end Wow! Yours is definitely bigger. ;-) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 19:07:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17158 for freebsd-current-outgoing; Tue, 13 Oct 1998 19:07:41 -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 TAA17074 for ; Tue, 13 Oct 1998 19:07:00 -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 WAA26799; Tue, 13 Oct 1998 22:05:36 -0400 (EDT) Date: Tue, 13 Oct 1998 22:05:35 -0400 (EDT) From: Brian Feldman To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" cc: Greg Lehey , Peter Wemm , Studded , Mike Smith , Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: Re: ELF kernels (was: Make elf release) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id TAA17094 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG By all means, why not by default have sysinstall make a /boot.config with '/boot/loader' in it? Or rather, it's quite easy to make the boot block (1) just default to /boot/loader, so why not do that? IIRC, BTX now passes an a.out kernel the correct params now. Brian Feldman On 14 Oct 1998, Dag-Erling C. [iso-8859-1] SmЬrgrav wrote: > Greg Lehey writes: > > On Tuesday, 13 October 1998 at 17:09:30 +0800, Peter Wemm wrote: > > > IMHO, whether /kernel is a.out or elf is far less of an issue than which > > > bootblocks we use. > > I'm not sure whether you're talking about the same issue that Doug > > (Studded) is. I think moving to an ELF kernel 2 days before code > > freeze would be a disaster. > > ...but switching to Elf-aware boot blocks would not affect the kernel, > and would make a later transition to an Elf kernel less painful for > those who install 3.0-RELEASE from scratch. I think this is what Peter > meant. > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 19:07:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17170 for freebsd-current-outgoing; Tue, 13 Oct 1998 19:07:46 -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 TAA17100 for ; Tue, 13 Oct 1998 19:07:22 -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 TAA01398; Tue, 13 Oct 1998 19:06:06 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <4.1.19981013190417.00a37ee0@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 13 Oct 1998 19:06:06 -0700 To: Chris Timmons From: Manfred Antar Subject: Re: Panic when rebooting with current kernel Cc: current@FreeBSD.ORG In-Reply-To: References: <4.1.19981013171511.00a2b100@192.168.0.1> 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:36 PM 10/13/98 -0700, Chris Timmons wrote: > >Ugh, it is much worse than I first thought. I had it happen while >unmounting a file system :( > >-Chris > I went back to sources from 6am the 10th and built a kernel. No problem. I'll keep moving forward and see if I can find the change that caused this 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 Tue Oct 13 19:44:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21251 for freebsd-current-outgoing; Tue, 13 Oct 1998 19:44:08 -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 TAA21246 for ; Tue, 13 Oct 1998 19:44:05 -0700 (PDT) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id MAA26176; Wed, 14 Oct 1998 12:43:49 +1000 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma026135; Wed, 14 Oct 98 12:43:26 +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 MAA15831 for ; Wed, 14 Oct 1998 12:43:25 +1000 Received: by localhost with Microsoft MAPI; Wed, 14 Oct 1998 12:43:25 +1000 Message-ID: <01BDF770.3BFBAFB0.john.saunders@scitec.com.au> From: John Saunders To: "freebsd-current@FreeBSD.ORG" Subject: RE: bitten 3 times already. Date: Wed, 14 Oct 1998 12:43:23 +1000 Organization: SCITEC LIMITED X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 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 Soren Schmidt [SMTP:sos@FreeBSD.ORG] wrote: > In reply to Marius Bendiksen who wrote: > > I haven't been tracking this too closely, but doesn't such a thing as Soren > > Schmidt suggested (removing LBA support) mean that people with LBA drives > > will end up in heaps of trouble? I have 8.4 + 3.2 gigs on LBA-formatted IDE > > drives, and would certainly not appreciate losing those. > > You dont need to run the drive in LBA mode to coexist with DOS or whatever. > Also you dont need to run the drive in LBA mode to use >8G, infact using > LBA has nothing to do with >8G support. >8G support has something to do > with us probing the drive correctly and using it that way. I think people are confusing operating the physical interface to the drive (IDE interface) in LBA mode, and using the partition geometry calculated by the BIOS in LBA mode. >From what I can understand, FreeBSD uses the sector addresses rather than the CHS addresses in the partition table to determine where it's partition lives. It is then free to either put the drive into LBA mode or CHS mode as long as it ends up reading and writing to the correct sectors. If it leaves the drive in CHS mode, then it has to make absolutely sure it knows the correct geometry for the drive so it can convert the sector addresses into the exact CHS values for the drive when doing IO. P.S. The above view is based on observation of installing FreeBSD on many machines, and "manager level" IDE/ATAPI knowledge, rather than intimate knowledge of the IDE driver source code. So feel free to correct me if needed :-) 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 Tue Oct 13 21:08:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01717 for freebsd-current-outgoing; Tue, 13 Oct 1998 21:08:38 -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 VAA01702 for ; Tue, 13 Oct 1998 21:08:35 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost by echonyc.com (8.9.1/8.9.1) with SMTP id AAA06006 for ; Wed, 14 Oct 1998 00:08:16 -0400 (EDT) Date: Wed, 14 Oct 1998 00:08:16 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: finally caught my (soft updates?) 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 Sometime in the last few days, kernel core dumps started working for me again, so today I was finally able to get a backtrace on the bug that's been crashing my make -j24 world's for so long. Reader's digest version: ufs_dirbad: bad dir. Ufs_dirbad is called from ufs_lookup. For more details, see kern/8312. 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 Tue Oct 13 21:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03693 for freebsd-current-outgoing; Tue, 13 Oct 1998 21:22:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-30.ppp.wenet.net [206.15.84.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03679 for ; Tue, 13 Oct 1998 21:22:53 -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 VAA02434; Tue, 13 Oct 1998 21:24:39 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 13 Oct 1998 21:24:37 -0700 (PDT) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Terry Lambert cc: perlsta@fs3.ny.genx.net, current@FreeBSD.ORG Subject: Re: /usr/include/sys/cam/scsi... In-Reply-To: <199810140157.SAA23385@usr08.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 Wed, 14 Oct 1998, Terry Lambert wrote: [...] > Use the "-P" option to CVS to prune "empty" (gone to the attic) > directories (NOTE: will delete things that I personally don't want > deleted out of my tree, like LFS!!!). > > Save the output of a CVS update. The files which are "not in the tree" > will show up with "?" to the left of them. ?? First off I don't use or plan to use CVS (CVSup here), secondly this goes for files in the tree, but not everything that's installed in /usr/include is in /usr/src/include, correct? In that case your method would be deleting a lot of "innocent" files. - 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 13 21:43:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06377 for freebsd-current-outgoing; Tue, 13 Oct 1998 21:43:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.videotron.ab.ca (cloak.videotron.ab.ca [206.75.216.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06366 for ; Tue, 13 Oct 1998 21:43:54 -0700 (PDT) (envelope-from rward@netcom.ca) Received: from blade ([24.108.23.151]) by mail.videotron.ab.ca (Netscape Messaging Server 3.6) with SMTP id AAA6DB for ; Tue, 13 Oct 1998 22:42:55 -0600 Reply-To: From: "Ryan Ward" To: "FreeBSD Current" Subject: Ports and Current Date: Tue, 13 Oct 1998 22:45:11 -0600 Message-ID: <000101bdf72d$6d4a0b40$97176c18@blade.v-wave.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0002_01BDF6FB.22AF9B40" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MS-TNEF-Correlator: 000000006A54D52E904CD211BB2F00104BD27E2584EC2000 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_0002_01BDF6FB.22AF9B40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I had mentioned a few days ago I had probs installing ports on a clean machine, somehow I got it all fixed now. It was either a manual install of the tk/tcl stuff or adding the gtk package that somehow made most of my ports fix themselves. Weird, I would have figured that a port would normally find out what its missing and add it anyway. Ahh well I'm happy for now. Ryan ------=_NextPart_000_0002_01BDF6FB.22AF9B40 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IgsEAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAAM4HCgANABYALQAAAAIAMQEB A5AGACAGAAAnAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB AAAAEgAAAFBvcnRzIGFuZCBDdXJyZW50AAAAAgFxAAEAAAAWAAAAAb33LW0XJpX6SGLtEdK7LwAQ S9J+JQAAAgEdDAEAAAAVAAAAU01UUDpSV0FSREBORVRDT00uQ0EAAAAACwABDgAAAABAAAYOAC5p Zi33vQECAQoOAQAAABgAAAAAAAAAalTVLpBM0hG7LwAQS9J+JcKAAAALAB8OAQAAAAMABhBU6VCP AwAHECcBAAAeAAgQAQAAAGUAAABJSEFETUVOVElPTkVEQUZFV0RBWVNBR09JSEFEUFJPQlNJTlNU QUxMSU5HUE9SVFNPTkFDTEVBTk1BQ0hJTkUsU09NRUhPV0lHT1RJVEFMTEZJWEVETk9XSVRXQVNF SVRIRVJBAAAAAAIBCRABAAAApAEAAKABAAD1AQAATFpGdcw71EkDAAoAcmNwZzEyNRYyAPgLYG4O EDAzM50B9yACpAPjAgBjaArAYHNldDAgBxMCgH0ZCoF1YwBQCwN1bG5FAiBlC6YgSSARAGQ2IAeA AjBpEvET8GEgImYH0WRheQQgYWdqbxOlcANgYgQgC4Bz6QGQbGwLgGcV8AkRBCBjAiAUoWNsZQOR AMFoIQuAZSwgcwNwZWjebwfgE7AVcAVAaQVAFqGZFMBpeBSBEuB3LhOgqQVAd2EEIGUZkGgEkDsU oQOBdQdAFlYXYGYgYxtBHMBrL3QXwBigdM51ASAXYBtxZGQW0hzS7mcdEBXwANBrFWAc8REA3wVA GLYAwAEAFABvFoAcklxteRcFGgEcwm0RMGz2dgeQGpBXGyALIBiQE7B6dwhgbBPwEQAiYBnxZ38I cBSBH4MUsBcSIzUS4HLvAMAWsCEwGgBuE/AIYBrB9x+SGZAEIG0EARbSAHAUkVMeIBmDbnka4Hka kEEcaGga0CJAAyBJJ235E8FwcCYBBbEaYgqiCoS5CoBSeQBwKqQR8QAsQAMAEBAAAAAAAwAREAAA AAALAAGACCAGAAAAAADAAAAAAAAARgAAAAADhQAAAAAAAAMAA4AIIAYAAAAAAMAAAAAAAABGAAAA ABCFAAAAAAAAAwAHgAggBgAAAAAAwAAAAAAAAEYAAAAAUoUAAPATAAAeAAiACCAGAAAAAADAAAAA AAAARgAAAABUhQAAAQAAAAQAAAA4LjUACwAMgAggBgAAAAAAwAAAAAAAAEYAAAAABoUAAAAAAAAD AA2ACCAGAAAAAADAAAAAAAAARgAAAAABhQAAAAAAAAsAFoAIIAYAAAAAAMAAAAAAAABGAAAAAA6F AAAAAAAAAwAXgAggBgAAAAAAwAAAAAAAAEYAAAAAEYUAAAAAAAADABmACCAGAAAAAADAAAAAAAAA RgAAAAAYhQAAAAAAAB4AKIAIIAYAAAAAAMAAAAAAAABGAAAAADaFAAABAAAAAQAAAAAAAAAeACmA CCAGAAAAAADAAAAAAAAARgAAAAA3hQAAAQAAAAEAAAAAAAAAHgAqgAggBgAAAAAAwAAAAAAAAEYA AAAAOIUAAAEAAAABAAAAAAAAAAsAMoAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABAAAACwA0gAsg BgAAAAAAwAAAAAAAAEYAAAAAAIgAAAAAAAALADaACyAGAAAAAADAAAAAAAAARgAAAAAFiAAAAAAA AAIB+A8BAAAAEAAAAGpU1S6QTNIRuy8AEEvSfiUCAfoPAQAAABAAAABqVNUukEzSEbsvABBL0n4l AgH7DwEAAABzAAAAAAAAADihuxAF5RAaobsIACsqVsIAAFBTVFBSWC5ETEwAAAAAAAAAAE5JVEH5 v7gBAKoAN9luAAAAQzpcV0lORE9XU1xBcHBsaWNhdGlvbiBEYXRhXE1pY3Jvc29mdFxPdXRsb29r XG91dGxvb2sucHN0AAADAP4PBQAAAAMADTT9NwAAAgF/AAEAAAAxAAAAMDAwMDAwMDA2QTU0RDUy RTkwNENEMjExQkIyRjAwMTA0QkQyN0UyNTg0RUMyMDAwAAAAAPEv ------=_NextPart_000_0002_01BDF6FB.22AF9B40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 22:42:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13728 for freebsd-current-outgoing; Tue, 13 Oct 1998 22:42:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sarah.albany.edu (sarah.albany.edu [169.226.1.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13721 for ; Tue, 13 Oct 1998 22:42:54 -0700 (PDT) (envelope-from sr0939@csc.albany.edu) Received: from fuzzy.albany.edu ([169.226.15.7]) by sarah.albany.edu (8.8.8/8.8.8) with SMTP id BAA06700 for ; Wed, 14 Oct 1998 01:42:34 -0400 (EDT) Received: (sr0939@localhost) by fuzzy.albany.edu (IBM OS/2 SENDMAIL VERSION 2.0/8.6.9) id BAA000.65; Wed, 14 Oct 1998 01:42:36 -0400 To: FreeBSD-current@FreeBSD.ORG Subject: Stableish 3.0 to run.? X-Attribution: SRR From: sr0939@csc.albany.edu (Stephen R. Reimer) Date: 14 Oct 1998 01:41:35 -0500 In-Reply-To: Greg Lehey's message of Wed, 14 Oct 1998 11:06:24 +0930 Message-ID: Lines: 19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am wondering which date's build is a good one to install and start with? I have a SMP/ PPro machine and Intel IDE with most HDs running off of an Adaptec 2940. I also have an Initio UW card running my 2 big HDs. -- Stephen R. Reimer @ home CSI BS - Linguistics Minor sr0939@csc.albany.edu pursuing Bio!! APO - ADH CorSec spr '97 UAlbany OS/2 Freak SpeedFreak if it ain't broke I'll fix it anyway... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 22:53:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14577 for freebsd-current-outgoing; Tue, 13 Oct 1998 22:53:07 -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 WAA14571 for ; Tue, 13 Oct 1998 22:53:05 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id AAA05808; Wed, 14 Oct 1998 00:52:49 -0500 (CDT) Received: from harkol-103.isdn.mke.execpc.com(169.207.64.231) by peak.mountin.net via smap (V1.3) id sma005806; Wed Oct 14 00:52:38 1998 Message-Id: <3.0.3.32.19981014004150.0103ae24@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, 14 Oct 1998 00:41:50 -0500 To: Vijay Ramasubramanian , "Mike Grommet" From: "Jeffrey J. Mountin" Subject: Re: Installation probs w/3.0-BETA Cc: current@FreeBSD.ORG In-Reply-To: References: <199810132027.OAA10599@narnia.plutotech.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 03:45 PM 10/13/98 -0500, Vijay Ramasubramanian wrote: >That was one of my suspicions due to the circumstances. Do you (or anyone >on the list) happen to know a good memory testing program to see if I can >confirm this? I don't have spare RAM at my disposal that I can swap in to >see if it fixes things. Don't know any good testers, but swapping memory around can help you locate the bad SIMM/DIMM, which is probably faster than locating a test program and running it (if it works). Done it a few times myself. If you only have one DIMM, like I do in one system, it's worth lowering the timings and see if that helps. Mine are all max'd, but then quality memory should do that. 8-) Anyone know how much memory an install can use up? 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 Tue Oct 13 23:15:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17227 for freebsd-current-outgoing; Tue, 13 Oct 1998 23:15:51 -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 XAA17220 for ; Tue, 13 Oct 1998 23:15:50 -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 0zTKDG-0001fi-00; Tue, 13 Oct 1998 23:15:10 -0700 Date: Tue, 13 Oct 1998 23:15:06 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Jeffrey J. Mountin" cc: Vijay Ramasubramanian , Mike Grommet , current@FreeBSD.ORG Subject: Re: Installation probs w/3.0-BETA In-Reply-To: <3.0.3.32.19981014004150.0103ae24@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, 14 Oct 1998, Jeffrey J. Mountin wrote: > At 03:45 PM 10/13/98 -0500, Vijay Ramasubramanian wrote: > >That was one of my suspicions due to the circumstances. Do you (or anyone > >on the list) happen to know a good memory testing program to see if I can > >confirm this? I don't have spare RAM at my disposal that I can swap in to > >see if it fixes things. > > Don't know any good testers, but swapping memory around can help you locate > the bad SIMM/DIMM, which is probably faster than locating a test program > and running it (if it works). Done it a few times myself. Or use parity SIMM/DIMM and then there is zero guess work. Rather than a mysterious non-reproducable crash, you will get a parity failed panic. Everyone should use parity memory all the time. > If you only have one DIMM, like I do in one system, it's worth lowering the > timings and see if that helps. Mine are all max'd, but then quality memory > should do that. 8-) > > Anyone know how much memory an install can use up? Just like any other FreeBSD app: as much as is available. Since the install does a lot of i/o most of memory will probably put to work as a disk cache. > Jeff Mountin - Unix Systems TCP/IP networking > jeff@mountin.net Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 23:28:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18492 for freebsd-current-outgoing; Tue, 13 Oct 1998 23:28: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 XAA18487 for ; Tue, 13 Oct 1998 23:28: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 PAA26775; Wed, 14 Oct 1998 15:57:50 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id PAA00525; Wed, 14 Oct 1998 15:57:44 +0930 (CST) Message-ID: <19981014155744.A516@freebie.lemis.com> Date: Wed, 14 Oct 1998 15:57:44 +0930 From: Greg Lehey To: "Stephen R. Reimer" , FreeBSD-current@FreeBSD.ORG Subject: Re: Stableish 3.0 to run.? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Stephen R. Reimer on Wed, Oct 14, 1998 at 01:41:35AM -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, 14 October 1998 at 1:41:35 -0500, Stephen R. Reimer wrote: > > I am wondering which date's build is a good one to install and start > with? We're told that 15 October is a propitious date. 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 Tue Oct 13 23:35:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19380 for freebsd-current-outgoing; Tue, 13 Oct 1998 23:35:25 -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 XAA19351 for ; Tue, 13 Oct 1998 23:34: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 NAA04261; Wed, 14 Oct 1998 13:59:55 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810140559.NAA04261@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Karl Pielorz , Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: Re: Make elf release In-reply-to: Your message of "Wed, 14 Oct 1998 11:22:20 +0930." <19981014112220.A21983@freebie.lemis.com> Date: Wed, 14 Oct 1998 13:59:55 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > [Format autorecovered at freebie.lemis.com] > > On Wednesday, 14 October 1998 at 7:59:23 +0800, Peter Wemm wrote: > > Karl Pielorz wrote: > >> Edwin Culp wrote: > >>>> I know that's one of the reasons why I've left my system running a.out k ernels > >>>> at the moment... (and I at least hope it's a good reason ;-) > >>> > >>> The wonderful part of it is that I haven't had anything to debug :-) Wha t of > >>> the folks running current/beta debug their kernels? The way to find the p roblems > >>> is to have more people using it in its most complete form. IMO. > >> > >> Hmmm.. Well if I'm right about not being able to debug LDK's with an ELF > >> kernel, I have to keep my kernel a.out... An LKM I'm betaing has a few > >> problems, which means it's gotta be debug(able)... > > > > Umm, it's the other way around.. DDB can't see a.out LKM's for debugging. > > DDB *can* see both a.out and elf KLD modules. KLD modules are the first > > time that DDB has worked with modular kernels. > > Does this mean that there's the potential to have symbol conflicts? Only if you have multiple symbols with the same name.. DDB can't be reasonably be expected to figure out which "static int debug" you mean if you've got several of them loaded in seperate modules. In a backtrace from DDB though, it has no problem with multiple symbols of the same name because it's keyed from the address. > > It's GDB that is the problem - it can't see KLD modules. Mind you, it > > can't see LKM's either. > > That's not correct. Here's a backtrace through the Vinum LKM: > > (kgdb) bt > #0 Debugger (msg=0xf5b8cfe0 "vinum debug") at ../../i386/i386/db_interface.c :317 > #1 0xf5b8d2d6 in vinumioctl (dev=0x40001900, cmd=0xc008464b, data=0xf5b4aed0 "", flag=0x3, p=0xf5a2bbc0) > at vinumioctl.c:107 > #2 0xf016f44b in spec_ioctl (ap=0xf5b4ae0c) at ../../miscfs/specfs/spec_vnop s.c:425 > #3 0xf016ed29 in spec_vnoperate (ap=0xf5b4ae0c) at ../../miscfs/specfs/spec_ vnops.c:129 > #4 0xf01da0d9 in ufs_vnoperatespec (ap=0xf5b4ae0c) at ../../ufs/ufs/ufs_vnop s.c:2303 OK, but don't forget that the /usr/bin/gdb in 3.0 release is the elf version.. It doesn't understand a.out (ether user binaries or kernels/ lkm's): /tmp-102> gdb /kernel.aout 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... "/kernel": not in executable format: File format not recognized (kgdb) /tmp-103> file /kernel /kernel: unknown pure executable On the other hand, your trick works just fine with ELF as well, with one variation: pwroot@overcee[2:17pm]~peter/sys_elf/alpha/alpha-140# gdb -k /kernel /dev/mem 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...(no debugging symbols found)... IdlePTD 2641920 initial pcb at 13aa000 panic messages: --- --- #0 0xf013ce65 in mi_switch () (kgdb) add-symbol-file /modules/testmod.ko 0xf02782a0 add symbol table from file "/modules/testmod.ko" at text_addr = 0xf02782a0? (y or n) y (no debugging symbols found)... (kgdb) disassemble test_function Dump of assembler code for function test_function: 0xf02782a0 : pushl %ebp 0xf02782a1 : movl %esp,%ebp 0xf02782a3 : pushl $0xf02782fc 0xf02782a8 : call 0xf01419bc 0xf02782ad : leave 0xf02782ae : ret 0xf02782af : nop End of assembler dump. pwroot@overcee[2:18pm]~peter/sys_elf/alpha/alpha-141# objdump --all-headers /modules/testmod.ko | more /modules/testmod.ko: file format elf32-i386 /modules/testmod.ko architecture: i386, flags 0x00000150: HAS_SYMS, DYNAMIC, D_PAGED start address 0x000002a0 ^^^^^^^^^^ [..] The gotcha was that under ELF there is a variable amount of header information. It shouldn't be too much trouble to teach GDB about this (as with LKM's). DDB does not see LKM's though. Also, DDB still has enough access to symbols even on a strip(1)ed kernel and modules. Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 13 23:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19754 for freebsd-current-outgoing; Tue, 13 Oct 1998 23:39:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA19746 for ; Tue, 13 Oct 1998 23:39:24 -0700 (PDT) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id JCACSOZJ; Wed, 14 Oct 98 06:39:07 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981014083411.00923cd0@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 14 Oct 1998 08:34:11 +0200 To: sos@FreeBSD.ORG From: Marius Bendiksen Subject: Re: bitten 3 times already. Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199810131547.RAA00285@sos.freebsd.dk> References: <3.0.5.32.19981013162954.0091e800@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >You dont need to run the drive in LBA mode to coexist with DOS or whatever. >Also you dont need to run the drive in LBA mode to use >8G, infact using >LBA has nothing to do with >8G support. >8G support has something to do >with us probing the drive correctly and using it that way. I know I don't need to run the drive in LBA mode, and that LBA has nothing to do with >8G support. I *have* written an IDE driver before, you know. What I fail to recall, is whether harddrives that are already LBA formatted will lose their data if accessed in CHS mode? Otoh, I suppose we've got code to make sure we follow the 'right' layout anyhow.. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 00:24:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24293 for freebsd-current-outgoing; Wed, 14 Oct 1998 00:24:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from emma.eng.uct.ac.za (emma.eng.uct.ac.za [137.158.128.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24284 for ; Wed, 14 Oct 1998 00:24:26 -0700 (PDT) (envelope-from shaun@emma.eng.uct.ac.za) Received: (from shaun@localhost) by emma.eng.uct.ac.za (8.8.8/8.8.8) id JAA22948; Wed, 14 Oct 1998 09:23:58 +0200 (SAT) (envelope-from shaun) Message-ID: <19981014092358.A22926@emma.eng.uct.ac.za> Date: Wed, 14 Oct 1998 09:23:58 +0200 From: Shaun Courtney To: current@FreeBSD.ORG Cc: "Dag-Erling C. Smf8rgrav " Subject: Re: ELF kernels ---> Switching to ELF aware boot block... Mail-Followup-To: current@freebsd.org, "Dag-Erling C. Smf8rgrav " References: <3622D416.E2E627AC@gorean.org> <199810130909.RAA29552@spinner.netplex.com.au> <19981014075310.V21983@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93i In-Reply-To: =?iso-8859-1?Q?=3Cxzpk924nigr=2Efsf=40hrotti=2Eifi=2Euio=2Eno=3E=3B_from?= =?iso-8859-1?Q?_Dag-Erling_C=2E_Sm=F8rgrav__on_Wed=2C_Oct_14=2C_1998_at_?= =?iso-8859-1?Q?01:35:32AM_+0200?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi On Wed Oct 14 01:35:32 1998 Dag-Erling C. SmЬrgrav wrote: > Greg Lehey writes: > > On Tuesday, 13 October 1998 at 17:09:30 +0800, Peter Wemm wrote: > > (Studded) is. I think moving to an ELF kernel 2 days before code > > freeze would be a disaster. > ...but switching to Elf-aware boot blocks would not affect the kernel, > and would make a later transition to an Elf kernel less painful for How does one go about doing this? I'm running current (build on 12 Oct '98), elf binaries .... Thanks Shaun > those who install 3.0-RELEASE from scratch. I think this is what Peter > meant. > > 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 -- Department of Electrical Engineering and CERECAM System Administrator and Unix/NT support http://www.eng.uct.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 00:30:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24807 for freebsd-current-outgoing; Wed, 14 Oct 1998 00:30:43 -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 AAA24778; Wed, 14 Oct 1998 00:30:34 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id JAA09355; Wed, 14 Oct 1998 09:30:15 +0200 (CEST) (envelope-from sos) Message-Id: <199810140730.JAA09355@sos.freebsd.dk> Subject: Re: bitten 3 times already. In-Reply-To: <3.0.5.32.19981014083411.00923cd0@mail.scancall.no> from Marius Bendiksen at "Oct 14, 98 08:34:11 am" To: Marius.Bendiksen@scancall.no (Marius Bendiksen) Date: Wed, 14 Oct 1998 09:30:15 +0200 (CEST) Cc: 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 Marius Bendiksen who wrote: > >You dont need to run the drive in LBA mode to coexist with DOS or whatever. > >Also you dont need to run the drive in LBA mode to use >8G, infact using > >LBA has nothing to do with >8G support. >8G support has something to do > >with us probing the drive correctly and using it that way. > > I know I don't need to run the drive in LBA mode, and that LBA has nothing > to do with >8G support. I *have* written an IDE driver before, you know. Great! anything we could use perhaps ?? > What I fail to recall, is whether harddrives that are already LBA formatted > will lose their data if accessed in CHS mode? Otoh, I suppose we've got > code to make sure we follow the 'right' layout anyhow.. There is no difference in formatting, its only a question on what you call the track/head/sector registers, which you should know if you have written an IDE driver ;) The only thing thats important is to know the geometry used when the data was written onto disk, then use that to calculate a sequential sector number, then recalc that back to the current geometry. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Wed Oct 14 01:05:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26834 for freebsd-current-outgoing; Wed, 14 Oct 1998 01:05:30 -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 BAA26823 for ; Wed, 14 Oct 1998 01:05:23 -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 SAA08631; Wed, 14 Oct 1998 18:05:04 +1000 Date: Wed, 14 Oct 1998 18:05:04 +1000 From: Bruce Evans Message-Id: <199810140805.SAA08631@godzilla.zeta.org.au> To: bde@zeta.org.au, Don.Lewis@tsc.tdk.com, jb@cimlogic.com.au 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 >} 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 01:45:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29468 for freebsd-current-outgoing; Wed, 14 Oct 1998 01:45: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 BAA29461; Wed, 14 Oct 1998 01:45:23 -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 SAA12607; Wed, 14 Oct 1998 18:45:04 +1000 Date: Wed, 14 Oct 1998 18:45:04 +1000 From: Bruce Evans Message-Id: <199810140845.SAA12607@godzilla.zeta.org.au> To: Marius.Bendiksen@scancall.no, sos@FreeBSD.ORG Subject: Re: bitten 3 times already. Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> What I fail to recall, is whether harddrives that are already LBA formatted >> will lose their data if accessed in CHS mode? Otoh, I suppose we've got >> code to make sure we follow the 'right' layout anyhow.. > >There is no difference in formatting, its only a question on what >you call the track/head/sector registers, which you should know if >you have written an IDE driver ;) >The only thing thats important is to know the geometry used when the >data was written onto disk, then use that to calculate a sequential >sector number, then recalc that back to the current geometry. The geometry or geometries used by previously active driver(s) are almost irrelevant, as you should know if you have written an IDE driver :-). The only thing that's important (for the driver) to know is that the drive actually uses the geometry that the driver programs it to use. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 01:50:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29963 for freebsd-current-outgoing; Wed, 14 Oct 1998 01:50:10 -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 BAA29907 for ; Wed, 14 Oct 1998 01:50:04 -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 SAA12884; Wed, 14 Oct 1998 18:49:24 +1000 Date: Wed, 14 Oct 1998 18:49:24 +1000 From: Bruce Evans Message-Id: <199810140849.SAA12884@godzilla.zeta.org.au> To: bde@zeta.org.au, brian@Awfulhak.org Subject: Re: Improper sharing of modem bandwidth Cc: current@FreeBSD.ORG, kjc@csl.sony.co.jp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >If there was an ioctl to change the usable tty buffer size to less than >4k, ppp could set it to ``whatever the MTU is'' and get quite a >reasonable interactive performance gain. Maybe not. Kernel ppp doesn't have the 4KB buffer between it and the driver, but its interactive performance is not reasonable when just one scp is using the link. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 01:56:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00778 for freebsd-current-outgoing; Wed, 14 Oct 1998 01:56:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kremvax.demos.su (kremvax.demos.su [194.87.0.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA00229 for ; Wed, 14 Oct 1998 01:52:16 -0700 (PDT) (envelope-from sinbin.demos.su!bag@kremvax.demos.su) Received: by kremvax.demos.su (8.6.13/D) from 0@sinbin.demos.su [194.87.5.31] with ESMTP id LAA15499; Wed, 14 Oct 1998 11:38:47 +0400 Received: by sinbin.demos.su id LAA13612; (8.6.12/D) Wed, 14 Oct 1998 11:37:18 +0400 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199810140737.LAA13612@sinbin.demos.su> Subject: Re: -current NFS problem In-Reply-To: <36236E98.43A3CDC6@cs.uni-sb.de> from "Daniel Rock" at "Oct 13, 98 05:15:36 pm" X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: rock@cs.uni-sb.de (Daniel Rock) Date: Wed, 14 Oct 1998 11:37:18 +0400 (MSD) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > *** Signal 11 > This only happens with NFS v3, not NFS v2 > > - If the shell output (e.g. for tcsh and XFree86 "make World >&! World.log) > is on an NFS mounted drive, and I watch the file with less (less World.log) > go to the end of file (Shift-G), sometimes the output gets filled up > with 0 characters. > This happens with both NFS v2 and v3. another known problem exist for nfsv3 we use www server working over nfs with about 1500000 hits/day it work fine with nfsv2 (load 0.1 - 0.8), but with nfsv3 we see load > 130 and server replay is very slow ... i think this is a bug in fbsd nfsv3 realization, the same scheme with solaris/sparc nfsv3 client/server work without this problems ... Alex. > > Daniel > > 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 14 02:02:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01253 for freebsd-current-outgoing; Wed, 14 Oct 1998 02:02:14 -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 CAA01248 for ; Wed, 14 Oct 1998 02:02:09 -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 CAA03518; Wed, 14 Oct 1998 02:00:07 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <36246816.31AEB990@gorean.org> Date: Wed, 14 Oct 1998 02:00:06 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1009 i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey CC: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , Peter Wemm , Mike Smith , Edwin Culp , FreeBSD-current@FreeBSD.ORG Subject: Re: ELF kernels (was: Make elf release) References: <3622D416.E2E627AC@gorean.org> <199810130909.RAA29552@spinner.netplex.com.au> <19981014075310.V21983@freebie.lemis.com> <19981014110624.Y21983@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: Someone wrote: > > ...but switching to Elf-aware boot blocks would not affect the kernel, > > and would make a later transition to an Elf kernel less painful for > > those who install 3.0-RELEASE from scratch. I think this is what Peter > > meant. > > Yes, I agree, I think that's what Peter meant. I don't think it's > what Doug meant. No, I suggested going the whole hog, but my understanding about the readiness of the elf kernel, etc. was mistaken. If doing just the bootblocks now will get most of the pain out of the way, I will gladly settle for that. :) 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 14 02:05:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01449 for freebsd-current-outgoing; Wed, 14 Oct 1998 02:05:26 -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 CAA01436; Wed, 14 Oct 1998 02:05:10 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id LAA29428; Wed, 14 Oct 1998 11:04:41 +0200 (CEST) (envelope-from sos) Message-Id: <199810140904.LAA29428@sos.freebsd.dk> Subject: Re: bitten 3 times already. In-Reply-To: <199810140845.SAA12607@godzilla.zeta.org.au> from Bruce Evans at "Oct 14, 98 06:45:04 pm" To: bde@zeta.org.au (Bruce Evans) Date: Wed, 14 Oct 1998 11:04:41 +0200 (CEST) Cc: Marius.Bendiksen@scancall.no, 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 Bruce Evans who wrote: > >> What I fail to recall, is whether harddrives that are already LBA formatted > >> will lose their data if accessed in CHS mode? Otoh, I suppose we've got > >> code to make sure we follow the 'right' layout anyhow.. > > > >There is no difference in formatting, its only a question on what > >you call the track/head/sector registers, which you should know if > >you have written an IDE driver ;) > >The only thing thats important is to know the geometry used when the > >data was written onto disk, then use that to calculate a sequential > >sector number, then recalc that back to the current geometry. > > The geometry or geometries used by previously active driver(s) are almost > irrelevant, as you should know if you have written an IDE driver :-). > The only thing that's important (for the driver) to know is that the > drive actually uses the geometry that the driver programs it to use. Erhm, and where is the difference ? :) It not so important that the geometry matches the drive, as its important that its the same geometry that was used when the data was written.. This is getting into a word game, now isn't it :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Wed Oct 14 02:51:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04535 for freebsd-current-outgoing; Wed, 14 Oct 1998 02:51:24 -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 CAA04527; Wed, 14 Oct 1998 02:51:19 -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 TAA17421; Wed, 14 Oct 1998 19:50:59 +1000 Date: Wed, 14 Oct 1998 19:50:59 +1000 From: Bruce Evans Message-Id: <199810140950.TAA17421@godzilla.zeta.org.au> To: bde@zeta.org.au, sos@FreeBSD.ORG Subject: Re: bitten 3 times already. Cc: freebsd-current@FreeBSD.ORG, Marius.Bendiksen@scancall.no Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The geometry or geometries used by previously active driver(s) are almost >> irrelevant, as you should know if you have written an IDE driver :-). >> The only thing that's important (for the driver) to know is that the >> drive actually uses the geometry that the driver programs it to use. > >Erhm, and where is the difference ? :) Everywhere. The driver gets to choose the geometry. There is no need for it to match previous choices; the choice just needs to be acceptable to the drive, and have enough sectors and heads for all physical sectors to be addressable. The FreeBSD driver chooses to use the default geometry because this is most likely to satisfy both constraints. On drives larger than 504MB, the default geometry is very _un_likely to match previous choices (except choices by the same driver, of course). >It not so important that the geometry matches the drive, as its important >that its the same geometry that was used when the data was written.. No, the current geometry is very important, but the geometry used to write the data is unimportant. The driver may changes the geometry between transactions. This would be silly, but old versions of the FreeBSD driver actually changed the geometry 2 or 3 times during first-opens. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 03:16:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06645 for freebsd-current-outgoing; Wed, 14 Oct 1998 03:16:58 -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 DAA06640 for ; Wed, 14 Oct 1998 03:16:55 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id LAA00382 for ; Wed, 14 Oct 1998 11:16:38 +0100 (BST) Message-ID: <362479CB.635AC1CC@tdx.co.uk> Date: Wed, 14 Oct 1998 11:15:39 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Panic on Shutdown / SMP, 10/13/98 Sources Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Has anyone else running -current seen this? - When I shut the machine down I get: " # shutdown -r now Shutdown NOW! shutdown: [pid 4414] # Oct 14 10:16:45 shutdown: reboot by root: System shutdown time has arrived boot() called on cpu#1 syncing disks... done panic: rslock: cpu: 1, addr: 0xfae1cb48, lock: 0x01000001 mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 boot() called on cpu#1 dumping to dev 20009, offset 262144 dump [snip] succeeded Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot <-- Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs cpu_reset: Restarting BSP cpu_reset_proxy: Grabbed mp lock for BSP cpu_reset_proxy: Stopped CPU 1 " This happens all the time now, but didn't happen with previous kernels... Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 03:38:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA08628 for freebsd-current-outgoing; Wed, 14 Oct 1998 03:38:53 -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 DAA08623 for ; Wed, 14 Oct 1998 03:38:51 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id MAA25481; Wed, 14 Oct 1998 12:38:14 +0200 (CEST) (envelope-from sos) Message-Id: <199810141038.MAA25481@sos.freebsd.dk> Subject: Re: Panic on Shutdown / SMP, 10/13/98 Sources In-Reply-To: <362479CB.635AC1CC@tdx.co.uk> from Karl Pielorz at "Oct 14, 98 11:15:39 am" To: kpielorz@tdx.co.uk (Karl Pielorz) Date: Wed, 14 Oct 1998 12:38:14 +0200 (CEST) Cc: 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 Karl Pielorz who wrote: > Hi, > > Has anyone else running -current seen this? - When I shut the machine down I > get: [snip] > syncing disks... done > panic: rslock: cpu: 1, addr: 0xfae1cb48, lock: 0x01000001 > mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 > boot() called on cpu#1 [snip]> > This happens all the time now, but didn't happen with previous kernels... Yep I see this too.. Initially I thought it was due to the problems I have with having switched to CAM for my SCSI disks, but it is still there now I'm back on my EIDE drives. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Wed Oct 14 04:05:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11507 for freebsd-current-outgoing; Wed, 14 Oct 1998 04:05:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sco.svf.stuba.sk (sco.svf.stuba.sk [147.175.16.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11502 for ; Wed, 14 Oct 1998 04:05:36 -0700 (PDT) (envelope-from gal@svf.stuba.sk) Received: from svf.stuba.sk (localhost [127.0.0.1]) by sco.svf.stuba.sk (8.8.8/8.6.12) with ESMTP id NAA01695 for ; Wed, 14 Oct 1998 13:05:06 +0200 (CEST) Message-ID: <36248562.CDEAF3EE@svf.stuba.sk> Date: Wed, 14 Oct 1998 13:05:06 +0200 From: Ondrej Gal X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: subscribe freebsd-current Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 04:51:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA15082 for freebsd-current-outgoing; Wed, 14 Oct 1998 04:51:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.singtel-yp.com (mail.singtel-yp.com [165.21.60.44]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA15073 for ; Wed, 14 Oct 1998 04:51:43 -0700 (PDT) (envelope-from ktsin@singtel-yp.com) Received: (qmail 10667 invoked from network); 14 Oct 1998 11:51:09 -0000 Received: from unknown (HELO daffodil.singtel-yp.com) (165.21.60.245) by mail.singtel-yp.com with SMTP; 14 Oct 1998 11:51:09 -0000 Received: (from ktsin@localhost) by daffodil.singtel-yp.com (8.8.8/8.8.8) id TAA00537; Wed, 14 Oct 1998 19:51:10 +0800 (SGT) (envelope-from ktsin) Message-Id: <199810141151.TAA00537@daffodil.singtel-yp.com> Subject: RE: 19981002-BETA Apache/Mouse problems To: jon@minotaur.com, freebsd-current@FreeBSD.ORG Date: Wed, 14 Oct 1998 19:51:10 +0800 (SGT) Cc: ulf@Alameda.net, netchild@wurzelausix.CS.Uni-SB.DE, jerry@reillyplating.com Expires: Wed, 21 Oct 1998 From: Sin Key Teck 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 tried compiling Apache13 which seemed to work well, but when I attempted > to run it, I ran into some module problems when trying > /usr/local/sbin/apachectl start -- I get the following error: > > Syntax error on line 26 of /usr/local/etc/apache/httpd.conf: > Cannot load /usr/local/libexec/apache/mod_mime_magic.so into server: > /usr/local/libexec/apache/mod_mime_magic.so: Undefined symbol > "ap_make_sub_pool" I believe the problem is caused by two things: dynamic loading and ELF. Guess Apache's configuration programs are unable to handle the recent changes to -current. Try putting the patch below as patch-am into PORTSDIR/www/apache13/patches/ (apache-1.3.2) and rebuild. It is ugly but it solves the problem. I wonder if anyone has come up with a more elegant solution. -------------------------------cut here--------------------------------- --- src/Configure.orig Sun Sep 20 23:48:57 1998 +++ src/Configure Wed Oct 14 19:09:21 1998 @@ -889,10 +889,16 @@ LDFLAGS_SHLIB_EXPORT="-rdynamic" SHLIB_SUFFIX_DEPTH=0 ;; - *-freebsd*) + *-freebsd2*) CFLAGS_SHLIB="-fpic" LDFLAGS_SHLIB="-Bshareable" LDFLAGS_SHLIB_EXPORT="" + SHLIB_SUFFIX_DEPTH=2 + ;; + *-freebsd3*) + CFLAGS_SHLIB="-fpic" + LDFLAGS_SHLIB="-Bshareable" + LDFLAGS_SHLIB_EXPORT="-rdynamic" SHLIB_SUFFIX_DEPTH=2 ;; *-openbsd*) --- src/os/unix/os.h.orig Wed Sep 16 14:49:44 1998 +++ src/os/unix/os.h Wed Oct 14 17:20:54 1998 @@ -121,7 +121,7 @@ #define RTLD_GLOBAL 0 #endif -#if defined(__FreeBSD__) || defined(__OpenBSD__) || defined(__NetBSD__) +#if __FreeBSD__ < 3 || defined(__OpenBSD__) || defined(__NetBSD__) #define DLSYM_NEEDS_UNDERSCORE #endif -------------------------------cut here--------------------------------- kt > Doing file /usr/local/libexec/apache/mod_mime_magic.so, I get: > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 05:47:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19023 for freebsd-current-outgoing; Wed, 14 Oct 1998 05:47:03 -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 FAA19017 for ; Wed, 14 Oct 1998 05:47:01 -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 OAA14677; Wed, 14 Oct 1998 14:46:24 +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: <362479CB.635AC1CC@tdx.co.uk> Date: Wed, 14 Oct 1998 14:46:24 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: Karl Pielorz Subject: RE: Panic on Shutdown / SMP, 10/13/98 Sources Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Oct-98 Karl Pielorz wrote: > Hi, > > Has anyone else running -current seen this? - When I shut the machine down I > get: > > " ># shutdown -r now > Shutdown NOW! > shutdown: [pid 4414] ># Oct 14 10:16:45 shutdown: reboot by root: > > System shutdown time has arrived > boot() called on cpu#1 > > syncing disks... done > panic: rslock: cpu: 1, addr: 0xfae1cb48, lock: 0x01000001 > mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 > boot() called on cpu#1 > dumping to dev 20009, offset 262144 > dump [snip] succeeded > Automatic reboot in 15 seconds - press a key on the console to abort > --> Press a key on the console to reboot <-- > Rebooting... > cpu_reset called on cpu#1 > cpu_reset: Stopping other CPUs > cpu_reset: Restarting BSP > cpu_reset_proxy: Grabbed mp lock for BSP > cpu_reset_proxy: Stopped CPU 1 > " > > This happens all the time now, but didn't happen with previous kernels... > > Regards, > > Karl > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- Same here with sources from today (Oct. 14) . Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 05:49:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19157 for freebsd-current-outgoing; Wed, 14 Oct 1998 05:49: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 FAA19147; Wed, 14 Oct 1998 05:49:46 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id NAA00925; Wed, 14 Oct 1998 13:49:30 +0100 (BST) Message-ID: <36249D9F.8A6A963D@tdx.co.uk> Date: Wed, 14 Oct 1998 13:48:31 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: sos@FreeBSD.ORG CC: current@FreeBSD.ORG Subject: Re: Panic on Shutdown / SMP, 10/13/98 Sources References: <199810141038.MAA25481@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 Karl Pielorz who wrote: > > Hi, > > > > Has anyone else running -current seen this? - When I shut the machine down I > > get: > [snip] > > syncing disks... done > > panic: rslock: cpu: 1, addr: 0xfae1cb48, lock: 0x01000001 > > mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 > > boot() called on cpu#1 > [snip]> > > This happens all the time now, but didn't happen with previous kernels... > > Yep I see this too.. Initially I thought it was due to the problems > I have with having switched to CAM for my SCSI disks, but it is still > there now I'm back on my EIDE drives. Hmmm... It didn't happen with sources from the 10th... I've got some crashdumps to look at (but they got saved to disk suspiciously quickly) - I'll see what I can figure out... Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 05:53:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19618 for freebsd-current-outgoing; Wed, 14 Oct 1998 05:53:50 -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 FAA19602; Wed, 14 Oct 1998 05:53:43 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id NAA00964; Wed, 14 Oct 1998 13:53:11 +0100 (BST) Message-ID: <36249E7D.2C06B16E@tdx.co.uk> Date: Wed, 14 Oct 1998 13:52:13 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Werner Griessl CC: current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: Panic on Shutdown / SMP, 10/13/98 Sources References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Werner Griessl wrote: > Same here with sources from today (Oct. 14) . > Werner The crashdumps aren't very revealing to me... (Then again, I'm not too hot with this kind of stuff):- " #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 268 dumppcb.pcb_cr3 = rcr3(); asf 0x0 #0 boot (howto=0x100) at ../../kern/kern_shutdown.c:268 #1 0xf01370f4 in panic (fmt=0xf01c4a19 "rslock: cpu: %d, addr: 0x%08x, lock: 0x%08x") at ../../kern/kern_shutdown.c:430 #2 0xf01c4a19 in bsl1 () #3 0xf01a7fac in vm_object_terminate (object=0xfae2e440) at ../../vm/vm_object.c:444 #4 0xf0158d31 in vrele (vp=0xfae1cae0) at ../../kern/vfs_subr.c:1310 #5 0xf0196cea in ffs_unmount (mp=0xf1ee7400, mntflags=0x80000, p=0xfadb0f40) at ../../ufs/ffs/ffs_vfsops.c:847 #6 0xf015b1e6 in dounmount (mp=0xf1ee7400, flags=0x80000, p=0xfadb0f40) at ../../kern/vfs_syscalls.c:468 #7 0xf0159c95 in vfs_unmountall () at ../../kern/vfs_subr.c:2193 #8 0xf0136d07 in boot (howto=0x0) at ../../kern/kern_shutdown.c:253 #9 0xf0136a91 in reboot (p=0xfadb0f40, uap=0xfaf00f94) at ../../kern/kern_shutdown.c:147 #10 0xf01c65ff in syscall (frame={tf_es = 0x27, tf_ds = 0x27, tf_edi = 0x0, tf_esi = 0x0, tf_ebp = 0xefbfde18, tf_isp = 0xfaf00fe4, tf_ebx = 0x2, tf_edx = 0xffffffff, tf_ecx = 0x3, tf_eax = 0x37, tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x80488b0, tf_cs = 0x1f, tf_eflags = 0x246, tf_esp = 0xefbfde00, tf_ss = 0x27}) at ../../i386/i386/trap.c:1031 #11 0xf01b506c in Xint0x80_syscall () " Doesn't mean a lot to me, maybe it will to someone else? ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 05:55:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19795 for freebsd-current-outgoing; Wed, 14 Oct 1998 05:55:52 -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 FAA19787 for ; Wed, 14 Oct 1998 05:55: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 HAA23864 for freebsd-current@freebsd.org; Wed, 14 Oct 1998 07:55:35 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.8.8/8.8.7) id HAA16878; Wed, 14 Oct 1998 07:54:16 -0500 (CDT) From: Bruce Albrecht Date: Wed, 14 Oct 1998 07:54:15 -0500 (CDT) To: freebsd-current@FreeBSD.ORG Subject: New build problem? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13860.40343.489454.292871@zuhause.zuhause.mn.org> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to do an upgrade from an ancient version of 3.0-current (12/31/97), cvsupped src about 10 hours ago, and my build died when I did: make -f Makefile.upgrade aout-to-elf-build (most lines deleted) -------------------------------------------------------------- >>> Rebuilding bootstrap libraries -------------------------------------------------------------- cd /usr/src; PATH=/usr/obj/aout/usr/src/tmp/sbin:/usr/obj/aout/usr/src/tmp/usr/sbin:/usr/obj/aout/usr/src/tmp/bin:/usr/obj/aout/usr/src/tmp/usr/bin:/usr/obj/aout/usr/src/tmp/usr/games:/bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/gnu/bin:/usr/local/bin:/usr/local/sbin:/usr/libexec/uucp:/home/bruce/bin:/home/bruce/tbd.new:.:/usr/games BISON_SIMPLE=/usr/obj/aout/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/aout/usr/src/tmp/usr/libexec:/usr/obj/aout/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH=/usr/obj/aout/usr/src/tmp/usr/libexec:/usr/libexec /usr/obj/aout/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/aout/usr/src/tmp -f Makefile.inc1 bootstrap-libraries cd /usr/src/lib/csu/i386; /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj make: don't know how to make /usr/obj/usr/src/tmp/usr/include/sys/param.h. Stop *** Error code 2 I had run another attempt a couple of days ago that had failed because I ran out of space in /usr/obj, and it had gone much further. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 06:01:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20273 for freebsd-current-outgoing; Wed, 14 Oct 1998 06:01:03 -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 GAA20267 for ; Wed, 14 Oct 1998 06:00:59 -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 IAA02078; Wed, 14 Oct 1998 08:00:10 -0500 (CDT) Message-Id: <199810141300.IAA02078@ns.tar.com> From: "Richard Seaman, Jr." To: "John Birrell" Cc: "info@highwind.com" , "current@FreeBSD.ORG" Date: Wed, 14 Oct 98 08:00:09 -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: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Oct 1998 08:00:27 +1000 (EST), John Birrell wrote: >Providing a ktrace without a thread status dump is >useless IMO. All that you've shown is that the thread scheduler can't >find a thread to run. The thread status dump should tell you why. I would have thought that if the scheduler can't find a thread to run then "select" would get called. The kernel trace provided didn't show select being called, so I would have assumed that a thread *is* being scheduled. It would appear to me that a thread or threads are just hard looping into the thread scheduler, as might be the case if pthread_yield is being called repeatedly. But, you know more about this than I do. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 06:12:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22058 for freebsd-current-outgoing; Wed, 14 Oct 1998 06:12:11 -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 GAA22053 for ; Wed, 14 Oct 1998 06:12:09 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id JAA12654; Wed, 14 Oct 1998 09:11:19 -0400 (EDT) Date: Wed, 14 Oct 1998 09:11:19 -0400 (EDT) Message-Id: <199810141311.JAA12654@highwind.com> From: HighWind Software Information To: lists@tar.com CC: jb@cimlogic.com.au, current@FreeBSD.ORG In-reply-to: <199810141300.IAA02078@ns.tar.com> (lists@tar.com) Subject: Re: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rich, >I would have thought that if the scheduler can't find a thread to run >then "select" would get called. The kernel trace provided didn't show >select being called, so I would have assumed that a thread *is* being >scheduled. It would appear to me that a thread or threads are just hard >looping into the thread scheduler, as might be the case if pthread_yield >is being called repeatedly. But, you know more about this than I do. I can certainly say that we don't call "pthread_yield" anywhere. Also, the fact that the static linked version also doesn't work on these new FreeBSD's is EXTREMELY troubling. We are going to get that status dump today. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 06:14:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22254 for freebsd-current-outgoing; Wed, 14 Oct 1998 06:14:53 -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 GAA22245; Wed, 14 Oct 1998 06:14:44 -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 PAA15310; Wed, 14 Oct 1998 15:09:03 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.3.p0.FreeBSD:981014150903:2320=_" In-Reply-To: <36249E7D.2C06B16E@tdx.co.uk> Date: Wed, 14 Oct 1998 15:09:03 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: Karl Pielorz Subject: Re: Panic on Shutdown / SMP, 10/13/98 Sources Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:981014150903:2320=_ Content-Type: text/plain; charset=us-ascii On 14-Oct-98 Karl Pielorz wrote: > > Werner Griessl wrote: > >> Same here with sources from today (Oct. 14) . >> Werner > > The crashdumps aren't very revealing to me... (Then again, I'm not too hot > with this kind of stuff):- > > " >#0 boot (howto=256) at ../../kern/kern_shutdown.c:268 > 268 dumppcb.pcb_cr3 = rcr3(); > asf 0x0 >#0 boot (howto=0x100) at ../../kern/kern_shutdown.c:268 >#1 0xf01370f4 in panic (fmt=0xf01c4a19 "rslock: cpu: %d, addr: 0x%08x, lock: > 0x%08x") > at ../../kern/kern_shutdown.c:430 >#2 0xf01c4a19 in bsl1 () >#3 0xf01a7fac in vm_object_terminate (object=0xfae2e440) at > ../../vm/vm_object.c:444 >#4 0xf0158d31 in vrele (vp=0xfae1cae0) at ../../kern/vfs_subr.c:1310 >#5 0xf0196cea in ffs_unmount (mp=0xf1ee7400, mntflags=0x80000, p=0xfadb0f40) > at ../../ufs/ffs/ffs_vfsops.c:847 >#6 0xf015b1e6 in dounmount (mp=0xf1ee7400, flags=0x80000, p=0xfadb0f40) at > ../../kern/vfs_syscalls.c:468 >#7 0xf0159c95 in vfs_unmountall () at ../../kern/vfs_subr.c:2193 >#8 0xf0136d07 in boot (howto=0x0) at ../../kern/kern_shutdown.c:253 >#9 0xf0136a91 in reboot (p=0xfadb0f40, uap=0xfaf00f94) at > ../../kern/kern_shutdown.c:147 >#10 0xf01c65ff in syscall (frame={tf_es = 0x27, tf_ds = 0x27, tf_edi = 0x0, > tf_esi = 0x0, tf_ebp = 0xefbfde18, > tf_isp = 0xfaf00fe4, tf_ebx = 0x2, tf_edx = 0xffffffff, tf_ecx = 0x3, > tf_eax = 0x37, tf_trapno = 0x7, > tf_err = 0x2, tf_eip = 0x80488b0, tf_cs = 0x1f, tf_eflags = 0x246, > tf_esp = 0xefbfde00, tf_ss = 0x27}) > at ../../i386/i386/trap.c:1031 >#11 0xf01b506c in Xint0x80_syscall () ---------------------------------- Appended is my very similar crashdump from today. Werner --_=XFMail.1.3.p0.FreeBSD:981014150903:2320=_ Content-Disposition: attachment; filename="gdb4.log" Content-Transfer-Encoding: base64 Content-Description: gdb4.log Content-Type: application/octet-stream; name=gdb4.log; SizeOnDisk=2309 R0RCIGlzIGZyZWUgc29mdHdhcmUgYW5kIHlvdSBhcmUgd2VsY29tZSB0byBkaXN0cmlidXRlIGNv cGllcyBvZiBpdAogdW5kZXIgY2VydGFpbiBjb25kaXRpb25zOyB0eXBlICJzaG93IGNvcHlpbmci IHRvIHNlZSB0aGUgY29uZGl0aW9ucy4KVGhlcmUgaXMgYWJzb2x1dGVseSBubyB3YXJyYW50eSBm b3IgR0RCOyB0eXBlICJzaG93IHdhcnJhbnR5IiBmb3IgZGV0YWlscy4KR0RCIDQuMTYgKGkzODYt dW5rbm93bi1mcmVlYnNkKSwgCkNvcHlyaWdodCAxOTk2IEZyZWUgU29mdHdhcmUgRm91bmRhdGlv biwgSW5jLi4uCklkbGVQVEQgMjgxMzk1Mgppbml0aWFsIHBjYiBhdCAyNGI0ZTQKcGFuaWNzdHI6 IHJzbG9jazogY3B1OiAxLCBhZGRyOiAweGY1ZjRkMTg4LCBsb2NrOiAweDAxMDAwMDAxCnBhbmlj IG1lc3NhZ2VzOgotLS0KcGFuaWM6IHJzbG9jazogY3B1OiAxLCBhZGRyOiAweGY1ZjRkMTg4LCBs b2NrOiAweDAxMDAwMDAxCm1wX2xvY2sgPSAwMTAwMDAwMTsgY3B1aWQgPSAxOyBsYXBpYy5pZCA9 IDAxMDAwMDAwCmJvb3QoKSBjYWxsZWQgb24gY3B1IzEKCmR1bXBpbmcgdG8gZGV2IDMwNDAxLCBv ZmZzZXQgMjI5Mzc2CmR1bXAgMTI4IDEyNyAxMjYgMTI1IDEyNCAxMjMgMTIyIDEyMSAxMjAgMTE5 IDExOCAxMTcgMTE2IDExNSAxMTQgMTEzIDExMiAxMTEgMTEwIDEwOSAxMDggMTA3IDEwNiAxMDUg MTA0IDEwMyAxMDIgMTAxIDEwMCA5OSA5OCA5NyA5NiA5NSA5NCA5MyA5MiA5MSA5MCA4OSA4OCA4 NyA4NiA4NSA4NCA4MyA4MiA4MSA4MCA3OSA3OCA3NyA3NiA3NSA3NCA3MyA3MiA3MSA3MCA2OSA2 OCA2NyA2NiA2NSA2NCA2MyA2MiA2MSA2MCA1OSA1OCA1NyA1NiA1NSA1NCA1MyA1MiA1MSA1MCA0 OSA0OCA0NyA0NiA0NSA0NCA0MyA0MiA0MSA0MCAzOSAzOCAzNyAzNiAzNSAzNCAzMyAzMiAzMSAz MCAyOSAyOCAyNyAyNiAyNSAyNCAyMyAyMiAyMSAyMCAxOSAxOCAxNyAxNiAxNSAxNCAxMyAxMiAx MSAxMCA5IDggNyA2IDUgNCAzIDIgMSAKLS0tCiMwICBib290IChob3d0bz0yNTYpIGF0IC4uLy4u L2tlcm4va2Vybl9zaHV0ZG93bi5jOjI2OAoyNjgJCQlkdW1wcGNiLnBjYl9jcjMgPSByY3IzKCk7 CihrZ2RiKSBidAojMCAgYm9vdCAoaG93dG89MjU2KSBhdCAuLi8uLi9rZXJuL2tlcm5fc2h1dGRv d24uYzoyNjgKIzEgIDB4ZjAxMzc5ZTQgaW4gcGFuaWMgKAogICAgZm10PTB4ZjAxZjhlYjkgInJz bG9jazogY3B1OiAlZCwgYWRkcjogMHglMDh4LCBsb2NrOiAweCUwOHgiKQogICAgYXQgLi4vLi4v a2Vybi9rZXJuX3NodXRkb3duLmM6NDMwCiMyICAweGYwMWY4ZWI5IGluIGJzbDEgKCkKIzMgIDB4 ZjAxZGMwMWMgaW4gdm1fb2JqZWN0X3Rlcm1pbmF0ZSAob2JqZWN0PTB4ZjVmNjkxMTApCiAgICBh dCAuLi8uLi92bS92bV9vYmplY3QuYzo0NDQKIzQgIDB4ZjAxNTkyNTEgaW4gdnJlbGUgKHZwPTB4 ZjVmNGQxMjApIGF0IC4uLy4uL2tlcm4vdmZzX3N1YnIuYzoxMzEwCiM1ICAweGYwMWM5ZmRhIGlu IGZmc191bm1vdW50IChtcD0weGYwYzIyODAwLCBtbnRmbGFncz01MjQyODgsIHA9MHhmNjAyOGQ4 MCkKICAgIGF0IC4uLy4uL3Vmcy9mZnMvZmZzX3Zmc29wcy5jOjg0NwojNiAgMHhmMDE1YjZmNiBp biBkb3VubW91bnQgKG1wPTB4ZjBjMjI4MDAsIGZsYWdzPTUyNDI4OCwgcD0weGY2MDI4ZDgwKQog ICAgYXQgLi4vLi4va2Vybi92ZnNfc3lzY2FsbHMuYzo0NjgKIzcgIDB4ZjAxNWExYjUgaW4gdmZz X3VubW91bnRhbGwgKCkgYXQgLi4vLi4va2Vybi92ZnNfc3Vici5jOjIxOTMKIzggIDB4ZjAxMzc1 ZjcgaW4gYm9vdCAoaG93dG89MCkgYXQgLi4vLi4va2Vybi9rZXJuX3NodXRkb3duLmM6MjUzCiM5 ICAweGYwMTM3MzgxIGluIHJlYm9vdCAocD0weGY2MDI4ZDgwLCB1YXA9MHhmNjAyZWY4NCkKICAg IGF0IC4uLy4uL2tlcm4va2Vybl9zaHV0ZG93bi5jOjE0NwojMTAgMHhmMDFmYjFmZiBpbiBzeXNj YWxsIChmcmFtZT17dGZfZXMgPSAzOSwgdGZfZHMgPSAzOSwgdGZfZWRpID0gMCwgCiAgICAgIHRm X2VzaSA9IDAsIHRmX2VicCA9IC0yNzI2NDExMjQsIHRmX2lzcCA9IC0xNjc1Nzk2OTIsIHRmX2Vi eCA9IDIsIAogICAgICB0Zl9lZHggPSAtMSwgdGZfZWN4ID0gMywgdGZfZWF4ID0gNTUsIHRmX3Ry YXBubyA9IDcsIHRmX2VyciA9IDIsIAogICAgICB0Zl9laXAgPSAxMzQ1MTQ4NjQsIHRmX2NzID0g MzEsIHRmX2VmbGFncyA9IDU4MiwgdGZfZXNwID0gLTI3MjY0MTE0OCwgCiAgICAgIHRmX3NzID0g Mzl9KSBhdCAuLi8uLi9pMzg2L2kzODYvdHJhcC5jOjEwMzEKIzExIDB4ZjAxZTkxMWMgaW4gWGlu dDB4ODBfc3lzY2FsbCAoKQooa2dkYikgcXVpdAo= --_=XFMail.1.3.p0.FreeBSD:981014150903:2320=_-- End of MIME 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 14 06:15:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22300 for freebsd-current-outgoing; Wed, 14 Oct 1998 06:15: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 GAA22293 for ; Wed, 14 Oct 1998 06:15:22 -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 IAA02149; Wed, 14 Oct 1998 08:15:01 -0500 (CDT) Message-Id: <199810141315.IAA02149@ns.tar.com> From: "Richard Seaman, Jr." To: "HighWind Software Information" Cc: "current@FreeBSD.ORG" Date: Wed, 14 Oct 98 08:15:01 -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: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Oct 1998 17:30:58 -0400 (EDT), HighWind Software Information wrote: > >After lots of work a few months ago, we got all of our software working >great under FreeBSD 3.0. > >In fact, it STILL works great.. That is, under: > >% uname -a >FreeBSD zonda.highwind.com 3.0-19980831-SNAP FreeBSD 3.0-19980831-SNAP #0: Mon Aug 31 14:03:19 GMT 1998 root@make.ican.net:/usr/src/sys/compile/GENERIC i386 > >However, under the newer FreeBSD's it doesn't seem to work. Our >application goes into 100% user space CPU and makes no progress. [snip] >We are an "aout" binary and have even tried STATICALLY linking with our >libc_r. It still goes into this loop. > >Any ideas what could have happened to cause this. It WAS working fine. Now, >after a little progress, we get into an infinite loop. > >Typhoon uses lots of disk and network I/O. What could we have tripped on? > >Seems to me, statically linking in libc_r would have eliminated any of >the recent changes in libc_r from blame. > >I'm a bit lost as to what to do. I guess we could upgrade our FreeBSD >machine and begin banging our heads against the wall. > >I'm wondering if anyone on this list would have a guess as to what new >changes to the kernel may have caused this. I'm not quite clear about what you're saying. Are you saying that your app, statically linked with a pre Sep 1 libc_r works ok on a pre Sep 1 3.0-current, but that this same statically linked app does not work on newer 3.0-current systems? If so, I'd agree that recent changes to libc_r are probably not the cause of the change in behavior. Are you still doing lots of forks and execs? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 06:31:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23599 for freebsd-current-outgoing; Wed, 14 Oct 1998 06:31:25 -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 GAA23593 for ; Wed, 14 Oct 1998 06:31:22 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id JAA12813; Wed, 14 Oct 1998 09:30:34 -0400 (EDT) Date: Wed, 14 Oct 1998 09:30:34 -0400 (EDT) Message-Id: <199810141330.JAA12813@highwind.com> From: HighWind Software Information To: lists@tar.com CC: current@FreeBSD.ORG In-reply-to: <199810141315.IAA02149@ns.tar.com> (lists@tar.com) Subject: Re: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not quite clear about what you're saying. Are you saying that your app, statically linked with a pre Sep 1 libc_r works ok on a pre Sep 1 3.0-current, but that this same statically linked app does not work on newer 3.0-current systems? Yes. That is exactly what I am saying. If so, I'd agree that recent changes to libc_r are probably not the cause of the change in behavior. Are you still doing lots of forks and execs? Yes. We are. However, we do close our file descriptors after the fork and before the exec. Could this be a aout vs ELF thing? Our binary is aout. I'm thinking about doing a fresh install of the latest 3.0 and rebuilding. I assume the latest stuff will make us produce ELF binaries. Right? -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 07:00:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25934 for freebsd-current-outgoing; Wed, 14 Oct 1998 07:00:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tor-dev1.nbc.netcom.ca (tor-dev1.nbc.netcom.ca [207.181.89.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25928 for ; Wed, 14 Oct 1998 07:00:57 -0700 (PDT) (envelope-from taob@tor-dev1.nbc.netcom.ca) Received: (from taob@localhost) by tor-dev1.nbc.netcom.ca (8.8.8/8.8.8) id KAA08099; Wed, 14 Oct 1998 10:00:18 -0400 (EDT) Date: Wed, 14 Oct 1998 10:00:18 -0400 (EDT) From: Brian Tao X-Sender: taob@tor-dev1.nbc.netcom.ca To: "Richard Seaman, Jr." cc: "current@FreeBSD.ORG" Subject: Re: Recent 3.0's are Depressing In-Reply-To: <199810141315.IAA02149@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 Wed, 14 Oct 1998, Richard Seaman, Jr. wrote: > > I'm not quite clear about what you're saying. Are you saying that > your app, statically linked with a pre Sep 1 libc_r works ok on a > pre Sep 1 3.0-current, but that this same statically linked app does > not work on newer 3.0-current systems? I believe that is what they have tried with beta testers. I've seen the same problem with binary dynamically linked to /usr/lib/aout/libc_r.so.3.0, the library dated Oct 1 (the last time I did a make world without -DNOAOUT). I'm going to try backing down just the a.out libc_r to Aug 31 or so to see what the effects are. > If so, I'd agree that recent changes to libc_r are probably not the > cause of the change in behavior. Are you still doing lots of forks > and execs? AFAIK, no other processes are spawned by typhoond after the initial startup phase. I've got 250 reader instances aimed at my FreeBSD Typhoon server right now, waiting for the bug to resurface. -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in'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 14 07:04:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26381 for freebsd-current-outgoing; Wed, 14 Oct 1998 07:04:52 -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 HAA26376 for ; Wed, 14 Oct 1998 07:04:48 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id KAA13073; Wed, 14 Oct 1998 10:03:47 -0400 (EDT) Date: Wed, 14 Oct 1998 10:03:47 -0400 (EDT) Message-Id: <199810141403.KAA13073@highwind.com> From: HighWind Software Information To: jb@cimlogic.com.au CC: current@FreeBSD.ORG In-reply-to: <199810132200.IAA05333@cimlogic.com.au> (message from John Birrell on Wed, 14 Oct 1998 08:00:27 +1000 (EST)) Subject: Re: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, The application is certainly pegged at 100% CPU doing: sigprocmask() gettimeofday() setitimer() (I'm fairly sure this is from uthread_kern.c) This is even with our statically linked binary using the libc_r from August 31st. Here is that uthread.dump you wanted to see. -Rob ============= ACTIVE THREADS -------------------- Thread 0x2941000 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21fde00 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_select.c:129] -------------------- Thread 0x21fdc00 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_select.c:129] -------------------- Thread 0x21fda00 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_select.c:129] -------------------- Thread 0x21fd800 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_select.c:129] -------------------- Thread 0x21fd600 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21fd400 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21fd200 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21fd000 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21f9e00 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21f9c00 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21f9a00 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_select.c:129] -------------------- Thread 0x21f9800 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_cond.c:289] This is the running thread -------------------- Thread 0x21f9600 () prio 64 state Waiting on a condition variable [/usr/src/lib/libc_r/uthread/uthread_cond.c:164] -------------------- Thread 0x21f9400 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_cond.c:289] -------------------- Thread 0x21f9200 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_mutex.c:349] -------------------- Thread 0x21f9000 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_cond.c:289] -------------------- Thread 0x21f4e00 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21f4c00 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21f4a00 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21f4800 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21f4600 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21f4400 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21f4200 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21f4000 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21efe00 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21efc00 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21efa00 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21ef800 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21ef600 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_cond.c:289] -------------------- Thread 0x21ef400 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_select.c:129] -------------------- Thread 0x21ef200 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21ef000 () prio 64 state Waiting on select [/usr/src/lib/libc_r/uthread/uthread_select.c:129] -------------------- Thread 0x21eee00 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_kern.c:271] -------------------- Thread 0x21eec00 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21eea00 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_cond.c:289] -------------------- Thread 0x21ee800 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21ee600 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_cond.c:289] -------------------- Thread 0x21ee400 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_select.c:129] -------------------- Thread 0x21ee200 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0x21ee000 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_select.c:129] -------------------- Thread 0xecc00 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0xece00 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread_cond.c:289] -------------------- Thread 0xec600 () prio 64 state Waiting on a condition variable [/usr/src/lib/libc_r/uthread/uthread_cond.c:164] -------------------- Thread 0xec400 () prio 64 state Waiting on a mutex [/usr/src/lib/libc_r/uthread/uthread_mutex.c:264] -------------------- Thread 0xec200 () prio 64 state Waiting process [/usr/src/lib/libc_r/uthread/uthread_wait4.c:50] -------------------- Thread 0xec000 () prio 64 state Waiting on select [/usr/src/lib/libc_r/uthread/uthread_select.c:129] This is the initial thread THERE ARE NO DEAD THREADS ============= FILE DESCRIPTOR TABLE (table size 8192) fd[ 0] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 5] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 7] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 8] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 9] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 10] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 11] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 12] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 13] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 14] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 15] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 16] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 17] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 18] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 19] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 20] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 21] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 22] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 23] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 24] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 25] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 26] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 27] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 28] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 29] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 30] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 31] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 32] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 33] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 34] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 35] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 36] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 37] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 38] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 39] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 40] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 41] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 42] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 43] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 44] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 45] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 46] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 47] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 48] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 49] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 50] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 51] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 52] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 53] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 54] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 55] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 56] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 57] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 58] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 59] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 60] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 61] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 62] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 63] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 64] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 65] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 66] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 67] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 68] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 69] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 70] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 71] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 72] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 73] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 74] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 75] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 76] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 77] read owner 0x21fde00 count 1 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 78] read owner 0x21ee400 count 1 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 79] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 80] read owner 0x21fdc00 count 1 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 81] read owner 0x21f9a00 count 1 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 82] read owner 0x21fd800 count 1 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 83] read owner 0x21ef400 count 1 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 84] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 85] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 86] read owner 0x21fda00 count 1 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 87] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 88] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 90] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 91] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 92] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 93] read owner 0x21ee000 count 1 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 94] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 95] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 96] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 97] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 98] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[ 99] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[100] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[101] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[102] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[103] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[104] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[105] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] fd[106] read owner 0x0 count 0 [(null):0] write owner 0x0 count 0 [(null):0] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 07:05:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26494 for freebsd-current-outgoing; Wed, 14 Oct 1998 07:05:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sage1.sagecorp.com ([204.250.198.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26489 for ; Wed, 14 Oct 1998 07:05:43 -0700 (PDT) (envelope-from djw@sage1.sagecorp.com) Received: from localhost (djw@localhost) by sage1.sagecorp.com (8.7.5/8.7.3) with SMTP id IAA08735; Wed, 14 Oct 1998 08:12:04 -0600 (MDT) Date: Wed, 14 Oct 1998 08:12:03 -0600 (MDT) From: Darren Whittaker To: Mike Smith cc: freebsd-current@FreeBSD.ORG, john.young@openmarket.com Subject: Re: problem in 3.0 In-Reply-To: <199810080530.WAA01135@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 Thank you for your email. I have taken your code and modified it to run as a cgi: #include #include #include int main(int argc, char *argv[]) { int i, j; char buf[256]; FILE *p; /* output the head */ printf("Content-type: text/html\n"); fflush(stdout); printf("\nTESTING"); printf("

TESTING

\n"); printf("

\n");
  fflush(stdout);

/* loop using popen */
  for (i = 0; i < 10; i++)
  {
     buf[0] = '\0';
     if ((p = popen("/bin/date", "r")) == NULL)
     {
       printf("popen error: %s\n",strerror(errno));
       continue;
     }
     fgets(buf, sizeof(buf) - 1, p);
     printf(buf);

     if ((j = pclose(p)) != 0)
       printf("pclose error: %s [%d]\n",strerror(j),j);
  }

/* output the tail */
  fflush(stdout);
  printf("
Copyright © 1998 Open Market, Inc. All Rights Reserved.\n"); printf("
\n"); fflush(stdout); } Here is some of the output when I run it from the web browser: Wed Oct 14 07:00:13 PDT 1998 pclose error: No child processes [10] pclose error: No child processes [10] pclose error: No child processes [10] pclose error: No child processes [10] pclose error: No child processes [10] pclose error: No child processes [10] pclose error: No child processes [10] pclose error: No child processes [10] pclose error: No child processes [10] What do you think the problem might be? -Darren ------------------ Darren Whittaker Senior Software Engineer Small Enterprise Group Open Market, Inc. On Wed, 7 Oct 1998, Mike Smith wrote: > > We have found a problem with popen. The first popen is executed just fine > > with a good pclose. The second popen appears to work (though nothing > > happens) and the pclose returns a 138. This also applies to the system > > call. The first one works but any after sustem call after the first > > one fails. We even forked the process but in the child only the first > > popen work. > > I'm not sure that I can follow your problem here. Have you reduced the > program to its simplest form, eg: > > dingo:/tmp>cat p.c > #include > #include > > void main(void) > { > int i, j; > char buf[256]; > FILE *p; > > for (i = 0; i < 10; i++) { > if ((p = popen("/bin/date", "r")) == NULL) > err(1, "popen"); > fgets(buf, sizeof(buf) - 1, p); > printf(buf); > if ((j = pclose(p)) != 0) > errx(1, "pclose %d", j); > } > } > dingo:/tmp>gcc -o p p.c > dingo:/tmp>./p > Wed Oct 7 22:28:04 PDT 1998 > Wed Oct 7 22:28:04 PDT 1998 > Wed Oct 7 22:28:04 PDT 1998 > Wed Oct 7 22:28:04 PDT 1998 > Wed Oct 7 22:28:04 PDT 1998 > Wed Oct 7 22:28:04 PDT 1998 > Wed Oct 7 22:28:04 PDT 1998 > Wed Oct 7 22:28:04 PDT 1998 > Wed Oct 7 22:28:04 PDT 1998 > Wed Oct 7 22:28:04 PDT 1998 > dingo:/tmp>uname -a > FreeBSD dingo.cdrom.com 3.0-CURRENT FreeBSD 3.0-CURRENT #2: Wed Sep 16 16:38:28 PDT 1998 mike@dingo.cdrom.com:/local0/src/sys/compile/DINGO i386 > > What do you mean by "this also applies to the system call"? Which > system call? > > > Now our program is running as a cgi under Apache and works on your 2.x > > versions just fine. > > I'm afraid you're going to have to supply some more detail before we > can help you further here. > -- > \\ 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 14 07:18:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27659 for freebsd-current-outgoing; Wed, 14 Oct 1998 07:18:25 -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 HAA27652; Wed, 14 Oct 1998 07:18:23 -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 HAA10890; Wed, 14 Oct 1998 07:18:05 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <4.1.19981014071415.00a10620@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 14 Oct 1998 07:18:04 -0700 To: sos@FreeBSD.ORG, kpielorz@tdx.co.uk (Karl Pielorz) From: Manfred Antar Subject: Re: Panic on Shutdown / SMP, 10/13/98 Sources Cc: current@FreeBSD.ORG In-Reply-To: <199810141038.MAA25481@sos.freebsd.dk> References: <362479CB.635AC1CC@tdx.co.uk> Mime-Version: 1.0 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 HAA27654 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:38 PM 10/14/98 +0200, SЬren" Schmidt wrote: >In reply to Karl Pielorz who wrote: >> Hi, >> >> Has anyone else running -current seen this? - When I shut the machine down I >> get: >[snip] >> syncing disks... done >> panic: rslock: cpu: 1, addr: 0xfae1cb48, lock: 0x01000001 >> mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 >> boot() called on cpu#1 >[snip]> >> This happens all the time now, but didn't happen with previous kernels... > >Yep I see this too.. Initially I thought it was due to the problems >I have with having switched to CAM for my SCSI disks, but it is still >there now I'm back on my EIDE drives. > There were some changes made to vfs_subr.c on the 12th, sources from before 12 noon pacific time work OK for me. Any thing after that causes the problem. 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 Wed Oct 14 07:25:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28641 for freebsd-current-outgoing; Wed, 14 Oct 1998 07:25:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28636 for ; Wed, 14 Oct 1998 07:25:30 -0700 (PDT) (envelope-from wscott@ichips.intel.com) Received: from ichips-ra.pdx.intel.com (ichips-ra.pdx.intel.com [137.102.192.31]) by ganymede.or.intel.com (8.8.6/8.8.5) with ESMTP id OAA17572 for ; Wed, 14 Oct 1998 14:25:15 GMT Received: from pdxcs565.pdx.intel.com (pdxcs565.pdx.intel.com [137.102.209.215]) by ichips-ra.pdx.intel.com (8.8.8/8.8.7) with ESMTP id HAA12203 for ; Wed, 14 Oct 1998 07:25:14 -0700 (PDT) Received: from ichips.intel.com by pdxcs565.pdx.intel.com (8.8.8/WW2.2 (Ronler Acres)) id HAA26802; Wed, 14 Oct 1998 07:25:14 -0700 Message-Id: <199810141425.HAA26802@pdxcs565.pdx.intel.com> To: current@FreeBSD.ORG Subject: simple popen() bug and solution (PATCH) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Date: Wed, 14 Oct 1998 07:25:14 -0700 From: Wayne Scott Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a restatement of PR misc/7810. Since that PR is making NO progress I thought I would restate the problem in terms everyone can understand. The Problem ----------- The following program hangs on all current versions of FreeBSD, but works on Linux, AIX, and HPUX. #include #include main() { FILE *file1; FILE *file2; file1 = popen("gzip > file1.gz", "w"); file2 = popen("gzip > file2.gz", "w"); fprintf(file1, "This is a test\n"); fprintf(file2, "This is also a test\n"); pclose(file1); pclose(file2); } The Cause --------- When popen exec's the second gzip process, that process inherits the open filehandle 'file1'. When 'pclose(file1)' is executed the first gzip does not exit because the second gzip is still holding an open handle for its input. The Workaround -------------- If you reverse the order of the 'pclose()' calls then the program works correctly, but this is not possible in the big program I am really trying to get work. The other Workaround -------------------- If you set the 'close_on_exec' flag on the 'file1' then the second gzip will not inheret open file handle. ex. fcntl(fileno(file1), F_SETFD, 1) This works, but is changes the semantics of popen(). What POSIX says --------------- /* Posix.2: "popen() shall ensure that any streams from previous popen() calls that remain open in the parent process are closed in the new child process." */ The Solution ------------ popen() already maintains a list of filehandles that have be previously returned. We just need to walk that list and close all the files. No need to deallocate the list because we are just about the exec() anyway. Index: popen.c =================================================================== RCS file: /home/ncvs/src/lib/libc/gen/popen.c,v retrieving revision 1.9 diff -u -r1.9 popen.c --- popen.c 1997/04/22 09:44:06 1.9 +++ popen.c 1998/09/02 18:47:49 @@ -62,6 +62,7 @@ struct pid *cur; FILE *iop; int pdes[2], pid, twoway; + struct pid *p; /* * Lite2 introduced two-way popen() pipes using socketpair(). @@ -115,6 +116,9 @@ (void)close(pdes[0]); } (void)close(pdes[1]); + } + for (p = pidlist; p; p = p->next) { + close(fileno(p->fp)); } execl(_PATH_BSHELL, "sh", "-c", command, NULL); I would love to have this fixed in the 3.0 release of FreeBSD. Note I sent the PR with the patch in plenty of time... Wayne Scott MD6 Architecture - Intel Corp. wscott@ichips.intel.com Work #: (503) 613-5063 Disclaimer: All views expressed are my own opinions, and not necessarily those of Intel Corporation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 07:59:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02471 for freebsd-current-outgoing; Wed, 14 Oct 1998 07:59:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02464; Wed, 14 Oct 1998 07:59:34 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199810141459.HAA02464@hub.freebsd.org> Subject: Re: How to config pcmcia network adapter for laptop In-Reply-To: <199810131004.SAA24511@b1.hkstar.com> from Chan Yiu Wah at "Oct 13, 98 06:04:05 pm" To: c5666305@b1.hkstar.com (Chan Yiu Wah) Date: Wed, 14 Oct 1998 07:59:34 -0700 (PDT) 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 Chan Yiu Wah wrote: > > Hello, > > Sorry for cross post as I cannot subscribe freebsd-mobile after several > trials. please send me directly a more detailed description of the problem. jmb -- Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG FreeBSD--The Power to Serve JMB193 http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 08:07:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03762 for freebsd-current-outgoing; Wed, 14 Oct 1998 08:07:20 -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 IAA03729 for ; Wed, 14 Oct 1998 08:07:09 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from bombur.ifi.uio.no (2602@bombur.ifi.uio.no [129.240.64.200]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with SMTP id RAA07949 for ; Wed, 14 Oct 1998 17:06:48 +0200 (MET DST) Received: from localhost (dag-erli@localhost) by bombur.ifi.uio.no ; Wed, 14 Oct 1998 15:06:47 GMT Mime-Version: 1.0 To: current@FreeBSD.ORG Subject: SoftUpdates anomaly: what happens when you 'mount -u -o ro /usr'? 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: 14 Oct 1998 17:06:45 +0200 Message-ID: Lines: 50 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 IAA03743 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I woke up to find my nightly doc build had failed due to a full /usr partition. It's a 256MB partition with 160MB of data on it, so there had to be a catch somewhere. I ran 'fsck -n' which revealed 13,500 unreferenced files. I got a little scared and fsck'ed all my other file systems. Only one had errors: /mp3 (where I keep my MP3 archive). Both /usr and /mp3 were supposedly clean. I had a power outage a couple of days ago and fsck -p at bootup revealed nothing, which isn't surprising since they're usually mounted ro so they were marked as clean. /mp3 *may* have been hit by the fsck bug since it's "old enough", but /usr was newfs'ed after it had gone totally bananas (remember the problems I had with my streamer timing out during 'mt fsf'? That was when I restored /usr after newfs'ing it). At the time I thought it had been hit by the fsck bug which had just been fixed. I thought a little more about it and found that /usr and /mp3 had one thing in common: they're both usually mounted ro, but I occasionally mount them rw for specific thing (make installworld, building the docs, dumping a CD). To take installworld as an example, what I do is: # cd /usr/src # mount -u -o rw /usr # make installworld # mount -u -o ro /usr (I have a script which does this of course) Now looking through the fsck output (I scripted it) it seems that the unreferenced files were mostly binaries, and I bet if I looked closer I'd find out the mtimes are consistent with days I've run make world. What's more, I'm not missing any files; my bet is that the unreferenced files are files which have been deleted (replaced) by installworld. They're unreferenced because they were unlinked, but for some reason they were never freed. I think somebody with more fs experience than I have should take a look at what happens to a softupdates fs when it is switched from rw to ro. It seems obvious to me that pending writes should be flushed; it also appears that this doesn't actually happen. OBTW, I didn't lose anything; I just newfsed both /usr and /mp3, restored /mp3 from tape and /usr from disk, and kicked off a make world. I have /usr/local on a separate filesystem. 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 Wed Oct 14 08:17:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05396 for freebsd-current-outgoing; Wed, 14 Oct 1998 08:17: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 IAA05390; Wed, 14 Oct 1998 08:17: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 IAA00738; Wed, 14 Oct 1998 08:21:58 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810141521.IAA00738@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Marius Bendiksen cc: sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: bitten 3 times already. In-reply-to: Your message of "Wed, 14 Oct 1998 08:34:11 +0200." <3.0.5.32.19981014083411.00923cd0@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Oct 1998 08:21:57 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >You dont need to run the drive in LBA mode to coexist with DOS or whatever. > >Also you dont need to run the drive in LBA mode to use >8G, infact using > >LBA has nothing to do with >8G support. >8G support has something to do > >with us probing the drive correctly and using it that way. > > I know I don't need to run the drive in LBA mode, and that LBA has nothing > to do with >8G support. I *have* written an IDE driver before, you know. > > What I fail to recall, is whether harddrives that are already LBA formatted > will lose their data if accessed in CHS mode? Otoh, I suppose we've got > code to make sure we follow the 'right' layout anyhow.. Your second paragraph contradicts the first, as if you had "written an IDE driver before", you would know that "LBA formatted" doesn't mean anything, and that LBA and CHS are just two ways of feeding the same numbers to the disk. You'd also know that reading a disk won't cause it to "lose" its data. -- \\ 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 14 08:29:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07002 for freebsd-current-outgoing; Wed, 14 Oct 1998 08:29: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 IAA06993 for ; Wed, 14 Oct 1998 08:29: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 IAA00811; Wed, 14 Oct 1998 08:30:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810141530.IAA00811@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: bag@sinbin.demos.su (Alex G. Bulushev) cc: rock@cs.uni-sb.de (Daniel Rock), current@FreeBSD.ORG Subject: Re: -current NFS problem In-reply-to: Your message of "Wed, 14 Oct 1998 11:37:18 +0400." <199810140737.LAA13612@sinbin.demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Oct 1998 08:30:17 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > another known problem exist for nfsv3 > > we use www server working over nfs with about 1500000 hits/day > it work fine with nfsv2 (load 0.1 - 0.8), but with nfsv3 > we see load > 130 and server replay is very slow ... > i think this is a bug in fbsd nfsv3 realization, the > same scheme with solaris/sparc nfsv3 client/server work > without this problems ... The problem here is almost certainly that we don't cache the results of ACCESS RPC calls. There's an outstanding request from NetApp for us to address this; their testing indicates that 80% or more of NFS traffic generated by FreeBSD systems consists of ACCESS RPC calls. -- \\ 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 14 08:31:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07384 for freebsd-current-outgoing; Wed, 14 Oct 1998 08:31:03 -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 IAA07360 for ; Wed, 14 Oct 1998 08:30:54 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 18817 invoked by uid 1001); 14 Oct 1998 15:30:37 +0000 (GMT) To: dag-erli@ifi.uio.no Cc: current@FreeBSD.ORG Subject: Re: SoftUpdates anomaly: what happens when you 'mount -u -o ro /usr'? In-Reply-To: Your message of "14 Oct 1998 17:06:45 +0200" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 14 Oct 1998 17:30:36 +0200 Message-ID: <18815.908379036@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I thought a little more about it and found that /usr and /mp3 had one > thing in common: they're both usually mounted ro, but I occasionally > mount them rw for specific thing (make installworld, building the > docs, dumping a CD). To take installworld as an example, what I do is: > > # cd /usr/src > # mount -u -o rw /usr > # make installworld > # mount -u -o ro /usr This sounds similar to problems I had more than a year ago. I was trying to run with a readonly /usr, and needed to mount it rw occasionally to install things etc. The long and short of it was that I was never able to get this to work reliably, because I had fairly frequent kernel panics and inconsistent file systems. As soon as I stopped trying to change /usr between ro and rw, the problems disappeared. 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 14 08:42:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08276 for freebsd-current-outgoing; Wed, 14 Oct 1998 08:42:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08270 for ; Wed, 14 Oct 1998 08:42:22 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id IAA11118; Wed, 14 Oct 1998 08:41:54 -0700 (PDT) Date: Wed, 14 Oct 1998 08:41:54 -0700 (PDT) From: Chris Timmons To: Werner Griessl cc: current@FreeBSD.ORG Subject: Re: Panic on Shutdown / SMP, 10/13/98 Sources 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 wouldn't spend too much more time on this - Tor Egge analyzed the dump yesterday and identified the changes which caused the problem. Those changes were very recently reverted in version 1.166 of src/sys/kern/vfs_subr.c. See if this helps you... -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 08:52:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10251 for freebsd-current-outgoing; Wed, 14 Oct 1998 08:52:47 -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 IAA10205; Wed, 14 Oct 1998 08:52:37 -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 TAA15569; Wed, 14 Oct 1998 19:52:01 +0400 (MSD) Message-Id: <199810141552.TAA15569@arc.hq.cti.ru> X-Mailer: exmh version 2.0zeta 7/24/97 To: Manfred Antar cc: sos@FreeBSD.ORG, kpielorz@tdx.co.uk (Karl Pielorz), current@FreeBSD.ORG Subject: Re: Panic on Shutdown / SMP, 10/13/98 Sources In-reply-to: Your message of "Wed, 14 Oct 1998 07:18:04 PDT." <4.1.19981014071415.00a10620@192.168.0.1> Date: Wed, 14 Oct 1998 19:51:57 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There were some changes made to vfs_subr.c on the 12th, sources from before > 12 noon pacific time > work OK for me. Any thing after that causes the problem. Yep, I broke vfs_subr.c in rev. 1.164 :-( I backed out this commit, so everything should be OK now. Sorry, folks... Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 08:53:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10355 for freebsd-current-outgoing; Wed, 14 Oct 1998 08:53:10 -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 IAA10332 for ; Wed, 14 Oct 1998 08:53:06 -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 KAA02913; Wed, 14 Oct 1998 10:52:42 -0500 (CDT) Message-Id: <199810141552.KAA02913@ns.tar.com> From: "Richard Seaman, Jr." To: "Brian Tao" Cc: "current@FreeBSD.ORG" Date: Wed, 14 Oct 98 10:52:42 -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: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Oct 1998 10:00:18 -0400 (EDT), Brian Tao wrote: > > I believe that is what they have tried with beta testers. I've >seen the same problem with binary dynamically linked to >/usr/lib/aout/libc_r.so.3.0, the library dated Oct 1 (the last time I >did a make world without -DNOAOUT). I'm going to try backing down >just the a.out libc_r to Aug 31 or so to see what the effects are. I'd be curious if the problem still exists with a libc_r that is completely up to date. There were some changes to the thread scheduler after October 1. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 14 08:53:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10452 for freebsd-current-outgoing; Wed, 14 Oct 1998 08:53:43 -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 IAA10436 for ; Wed, 14 Oct 1998 08:53:37 -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 LAA15203; Wed, 14 Oct 1998 11:52:14 -0400 (EDT) Date: Wed, 14 Oct 1998 11:52:14 -0400 (EDT) From: Brian Feldman To: Mike Smith cc: "Alex G. Bulushev" , Daniel Rock , current@FreeBSD.ORG Subject: Re: -current NFS problem In-Reply-To: <199810141530.IAA00811@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 Perhaps this could be the problem with NFS "hanging" certain people all the time? (not the pine thing) The system spending way too much time inside the kernel transmitting NFS packets.... Brian Feldman On Wed, 14 Oct 1998, Mike Smith wrote: > > another known problem exist for nfsv3 > > > > we use www server working over nfs with about 1500000 hits/day > > it work fine with nfsv2 (load 0.1 - 0.8), but with nfsv3 > > we see load > 130 and server replay is very slow ... > > i think this is a bug in fbsd nfsv3 realization, the > > same scheme with solaris/sparc nfsv3 client/server work > > without this problems ... > > The problem here is almost certainly that we don't cache the results of > ACCESS RPC calls. There's an outstanding request from NetApp for us to > address this; their testing indicates that 80% or more of NFS traffic > generated by FreeBSD systems consists of ACCESS RPC calls. > > -- > \\ 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 14 08:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11542 for freebsd-current-outgoing; Wed, 14 Oct 1998 08:57: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 IAA11524 for ; Wed, 14 Oct 1998 08:57:52 -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 JAA01049; Wed, 14 Oct 1998 09:01:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810141601.JAA01049@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Darren Whittaker cc: Mike Smith , freebsd-current@FreeBSD.ORG, john.young@openmarket.com Subject: Re: problem in 3.0 In-reply-to: Your message of "Wed, 14 Oct 1998 08:12:03 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Oct 1998 09:01:30 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thank you for your email. I have taken your code and modified it to run as > a cgi: > > #include > #include > #include > > int main(int argc, char *argv[]) > { > int i, j; > char buf[256]; > FILE *p; > > /* output the head */ > printf("Content-type: text/html\n"); > fflush(stdout); > printf("\nTESTING"); > printf("

TESTING

\n"); > printf("

\n");
>   fflush(stdout);
> 
> /* loop using popen */
>   for (i = 0; i < 10; i++)
>   {
>      buf[0] = '\0';
>      if ((p = popen("/bin/date", "r")) == NULL)
>      {
>        printf("popen error: %s\n",strerror(errno));
>        continue;
>      }
>      fgets(buf, sizeof(buf) - 1, p);
>      printf(buf);
> 
>      if ((j = pclose(p)) != 0)
>        printf("pclose error: %s [%d]\n",strerror(j),j);

This is incorrect; it should read

      if (pclose(p) == -1)
        printf("pclose error: %s [%d]\n", strerror(errno), errno);

See the manpage for pclose().

> Here is some of the output when I run it from the web browser:
> 
> Wed Oct 14 07:00:13 PDT 1998
> pclose error: No child processes [10]
...
> What do you think the problem might be?

A return value of 10 from pclose() is not an error; it's the exit code 
of the child process.  /bin/date does not appear to reliably set its 
exit code.

-- 
\\  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 14 09:04:22 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA12812
          for freebsd-current-outgoing; Wed, 14 Oct 1998 09:04:22 -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 JAA12806
          for ; Wed, 14 Oct 1998 09:04:21 -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 JAA01077;
	Wed, 14 Oct 1998 09:04:20 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810141604.JAA01077@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman 
cc: Mike Smith , "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem 
In-reply-to: Your message of "Wed, 14 Oct 1998 11:52:14 EDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 14 Oct 1998 09:04:20 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Perhaps this could be the problem with NFS "hanging" certain people all
> the time? (not the pine thing) The system spending way too much time
> inside the kernel transmitting NFS packets....

No.  Lack of ACCESS caching makes us slow and eats the network (because 
we are very good at generating/sending/receiving them).

If there's someone out there that wants to work with the very best NFS 
people in the business to sort out our problems, please let me know.  
NetApp are keen to see our issues resolved (it will mean less angst 
for them in the long run, as they have many FreeBSD-using customers).

Right now, we are accumulating a bad NFS reputation. 8(

> Brian Feldman
> 
> On Wed, 14 Oct 1998, Mike Smith wrote:
> 
> > > another known problem exist for nfsv3
> > > 
> > > we use www server working over nfs with about 1500000 hits/day
> > > it work fine with nfsv2 (load 0.1 - 0.8), but with nfsv3
> > > we see load > 130 and server replay is very slow ...
> > > i think this is a bug in fbsd nfsv3 realization, the
> > > same scheme with solaris/sparc nfsv3 client/server work
> > > without this problems ...
> > 
> > The problem here is almost certainly that we don't cache the results of 
> > ACCESS RPC calls.  There's an outstanding request from NetApp for us to 
> > address this; their testing indicates that 80% or more of NFS traffic 
> > generated by FreeBSD systems consists of ACCESS RPC calls.
> > 
> > -- 
> > \\  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
> > 
> 
> 

-- 
\\  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 14 09:06:34 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA13150
          for freebsd-current-outgoing; Wed, 14 Oct 1998 09:06:34 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sage1.sagecorp.com ([204.250.198.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13142
          for ; Wed, 14 Oct 1998 09:06:31 -0700 (PDT)
          (envelope-from djw@sage1.sagecorp.com)
Received: from localhost (djw@localhost) by sage1.sagecorp.com (8.7.5/8.7.3) with SMTP id KAA09450; Wed, 14 Oct 1998 10:12:57 -0600 (MDT)
Date: Wed, 14 Oct 1998 10:12:57 -0600 (MDT)
From: Darren Whittaker 
To: Mike Smith 
cc: freebsd-current@FreeBSD.ORG, john.young@openmarket.com
Subject: Re: problem in 3.0 
In-Reply-To: <199810141601.JAA01049@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

The fact of the matter is that date only returned output once, why did it
not return output 10 times?


-Darren
------------------
Darren Whittaker
Senior Software Engineer
Small Enterprise Group
Open Market, Inc.

On Wed, 14 Oct 1998, Mike Smith wrote:

> > Thank you for your email. I have taken your code and modified it to run as
> > a cgi:
> > 
> > #include 
> > #include 
> > #include 
> > 
> > int main(int argc, char *argv[])
> > {
> >   int     i, j;
> >   char    buf[256];
> >   FILE    *p;
> > 
> > /* output the head */
> >   printf("Content-type: text/html\n");
> >   fflush(stdout);
> >   printf("\nTESTING");
> >   printf("
TESTING
\n");
> >   printf("
\n");
> >   fflush(stdout);
> > 
> > /* loop using popen */
> >   for (i = 0; i < 10; i++)
> >   {
> >      buf[0] = '\0';
> >      if ((p = popen("/bin/date", "r")) == NULL)
> >      {
> >        printf("popen error: %s\n",strerror(errno));
> >        continue;
> >      }
> >      fgets(buf, sizeof(buf) - 1, p);
> >      printf(buf);
> > 
> >      if ((j = pclose(p)) != 0)
> >        printf("pclose error: %s [%d]\n",strerror(j),j);
> 
> This is incorrect; it should read
> 
>       if (pclose(p) == -1)
>         printf("pclose error: %s [%d]\n", strerror(errno), errno);
> 
> See the manpage for pclose().
> 
> > Here is some of the output when I run it from the web browser:
> > 
> > Wed Oct 14 07:00:13 PDT 1998
> > pclose error: No child processes [10]
> ...
> > What do you think the problem might be?
> 
> A return value of 10 from pclose() is not an error; it's the exit code 
> of the child process.  /bin/date does not appear to reliably set its 
> exit code.
> 
> -- 
> \\  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 14 09:16:33 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA14463
          for freebsd-current-outgoing; Wed, 14 Oct 1998 09:16:33 -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 JAA14444
          for ; Wed, 14 Oct 1998 09:16:31 -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 JAA01488;
	Wed, 14 Oct 1998 09:20:07 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810141620.JAA01488@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Darren Whittaker 
cc: Mike Smith , freebsd-current@FreeBSD.ORG,
        john.young@openmarket.com
Subject: Re: problem in 3.0 
In-reply-to: Your message of "Wed, 14 Oct 1998 10:12:57 MDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 14 Oct 1998 09:20:07 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> The fact of the matter is that date only returned output once, why did it
> not return output 10 times?

No idea.  I can't make it fail in that fashion here, on a range of 
-current systems from mid-September through yesterday's snapshot.

Does the following:

#include 
#include 

void main(void) 
{
        int     i, j;
        char    buf[256];
        FILE    *p;

        for (i = 0; i < 100; i++) {
                if ((p = popen("/bin/date", "r")) == NULL)
                        err(1, "popen");
                fgets(buf, sizeof(buf) - 1, p);
                printf(buf);
                if ((pclose(p)) == -1)
                        err(1, "pclose");
        }
}

do the "right" or the "wrong" thing?

> -Darren

-- 
\\  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 14 09:38:49 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA17629
          for freebsd-current-outgoing; Wed, 14 Oct 1998 09:38:49 -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 JAA17624
          for ; Wed, 14 Oct 1998 09:38:47 -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 JAA23926;
          Wed, 14 Oct 1998 09:38:16 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Date: Wed, 14 Oct 1998 09:38:15 -0700 (PDT)
From: Doug White 
To: Nicolas Souchu 
cc: -current 
Subject: Re: bktr over new I2C framework, ready
In-Reply-To: <19981013235246.02264@breizh.prism.uvsq.fr>
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 bashed the cc: down a bit.

On Tue, 13 Oct 1998, Nicolas Souchu wrote:

> Sorry, I'm not generous in details :)
> 
> I2C is a very powerful and low-cost serial bus specified by Philips for
> multimedia purposes. A master chip on the bus controls slave chips (memories,
> voltage sensors, termometers, EEPROMs, batteries) with any byte oriented
> protocol.

If you want an I2C device to play with check out the Matrix Orbital LCD
displays.  They're normally driven by RS232 but they do have I2C pins
through the power connector. :)

The display is very smart and if you throw it characters it'll display
them, no silly intercharacter timing or any of that stuff.  

They're available in multiple sizes, up to 20 char X 4 lines.  You can
pick these up through linuxcentral.com.  Matrix Orbital is very responsive
to developer questions and is free-software friendly.

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 14 09:55:21 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA20117
          for freebsd-current-outgoing; Wed, 14 Oct 1998 09:55:21 -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 JAA20068
          for ; Wed, 14 Oct 1998 09:55:11 -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 MAA01502;
	Wed, 14 Oct 1998 12:56:32 -0400 (EDT)
	(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Wed, 14 Oct 1998 12:56:32 -0400 (EDT)
From: Alfred Perlstein 
X-Sender: bright@porkfriedrice.ny.genx.net
To: Brian Feldman 
cc: current@FreeBSD.ORG
Subject: Re: -current NFS 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, 14 Oct 1998, Brian Feldman wrote:

> Perhaps this could be the problem with NFS "hanging" certain people all
> the time? (not the pine thing) The system spending way too much time
> inside the kernel transmitting NFS packets....
> 
> Brian Feldman
> 

The way I understand it, unless you aren't running nfsiod processes this
shouldn't be an issue, all NFS requests except close are done async and
passed off to the nfsiod's to handle for the client.

btw, my pine problem *might* have somehow gone with my last kernel
build, I'm not sure 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


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 09:56:40 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA20405
          for freebsd-current-outgoing; Wed, 14 Oct 1998 09:56:40 -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 JAA20397
          for ; Wed, 14 Oct 1998 09:56:38 -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 KAA01731;
	Wed, 14 Oct 1998 10:00:44 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810141700.KAA01731@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Doug White 
cc: -current 
Subject: Re: bktr over new I2C framework, ready 
In-reply-to: Your message of "Wed, 14 Oct 1998 09:38:15 PDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 14 Oct 1998 10:00:44 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> If you want an I2C device to play with check out the Matrix Orbital LCD
> displays.  They're normally driven by RS232 but they do have I2C pins
> through the power connector. :)
> 
> The display is very smart and if you throw it characters it'll display
> them, no silly intercharacter timing or any of that stuff.  
> 
> They're available in multiple sizes, up to 20 char X 4 lines.  You can
> pick these up through linuxcentral.com.  Matrix Orbital is very responsive
> to developer questions and is free-software friendly.

... unfortunately their stuff is stupidly expensive.  You might want to 
check out http://www.seetron.com/ for a wider and cheaper range.  No 
i2c though, but much better gear.

-- 
\\  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 14 10:21:54 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA24641
          for freebsd-current-outgoing; Wed, 14 Oct 1998 10:21:54 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sage1.sagecorp.com ([204.250.198.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24636
          for ; Wed, 14 Oct 1998 10:21:52 -0700 (PDT)
          (envelope-from djw@sage1.sagecorp.com)
Received: from localhost (djw@localhost) by sage1.sagecorp.com (8.7.5/8.7.3) with SMTP id LAA10112; Wed, 14 Oct 1998 11:28:11 -0600 (MDT)
Date: Wed, 14 Oct 1998 11:28:10 -0600 (MDT)
From: Darren Whittaker 
To: Mike Smith 
cc: freebsd-current@FreeBSD.ORG, john.young@openmarket.com
Subject: Re: problem in 3.0 
In-Reply-To: <199810141620.JAA01488@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

The code appeared to work until I set buf[0] = '\0'; at the start of the
loop, then only one message was displayed. Since err displays to std error
and I have to run this program from a browers I did not see any error
messages.

-Darren

------------------
Darren Whittaker
Senior Software Engineer
Small Enterprise Group
Open Market, Inc.

On Wed, 14 Oct 1998, Mike Smith wrote:

> > The fact of the matter is that date only returned output once, why did it
> > not return output 10 times?
> 
> No idea.  I can't make it fail in that fashion here, on a range of 
> -current systems from mid-September through yesterday's snapshot.
> 
> Does the following:
> 
> #include 
> #include 
> 
> void main(void) 
> {
>         int     i, j;
>         char    buf[256];
>         FILE    *p;
> 
>         for (i = 0; i < 100; i++) {
>                 if ((p = popen("/bin/date", "r")) == NULL)
>                         err(1, "popen");
>                 fgets(buf, sizeof(buf) - 1, p);
>                 printf(buf);
>                 if ((pclose(p)) == -1)
>                         err(1, "pclose");
>         }
> }
> 
> do the "right" or the "wrong" thing?
> 
> > -Darren
> 
> -- 
> \\  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 14 10:35:03 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA26482
          for freebsd-current-outgoing; Wed, 14 Oct 1998 10:35:03 -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 KAA26477
          for ; Wed, 14 Oct 1998 10:35:01 -0700 (PDT)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id KAA07415;
	Wed, 14 Oct 1998 10:28:19 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpdrH7407; Wed Oct 14 17:28:17 1998
Date: Wed, 14 Oct 1998 10:28:14 -0700 (PDT)
From: Julian Elischer 
To: Mike Smith 
cc: Brian Feldman ,
        "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem 
In-Reply-To: <199810141604.JAA01077@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 thought kirk was doing that....


On Wed, 14 Oct 1998, Mike Smith wrote:

> > Perhaps this could be the problem with NFS "hanging" certain people all
> > the time? (not the pine thing) The system spending way too much time
> > inside the kernel transmitting NFS packets....
> 
> No.  Lack of ACCESS caching makes us slow and eats the network (because 
> we are very good at generating/sending/receiving them).
> 
> If there's someone out there that wants to work with the very best NFS 
> people in the business to sort out our problems, please let me know.  
> NetApp are keen to see our issues resolved (it will mean less angst 
> for them in the long run, as they have many FreeBSD-using customers).
> 
> Right now, we are accumulating a bad NFS reputation. 8(
> 
> > Brian Feldman
> > 
> > On Wed, 14 Oct 1998, Mike Smith wrote:
> > 
> > > > another known problem exist for nfsv3
> > > > 
> > > > we use www server working over nfs with about 1500000 hits/day
> > > > it work fine with nfsv2 (load 0.1 - 0.8), but with nfsv3
> > > > we see load > 130 and server replay is very slow ...
> > > > i think this is a bug in fbsd nfsv3 realization, the
> > > > same scheme with solaris/sparc nfsv3 client/server work
> > > > without this problems ...
> > > 
> > > The problem here is almost certainly that we don't cache the results of 
> > > ACCESS RPC calls.  There's an outstanding request from NetApp for us to 
> > > address this; their testing indicates that 80% or more of NFS traffic 
> > > generated by FreeBSD systems consists of ACCESS RPC calls.
> > > 
> > > -- 
> > > \\  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
> > > 
> > 
> > 
> 
> -- 
> \\  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 14 11:07:15 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA00109
          for freebsd-current-outgoing; Wed, 14 Oct 1998 11:07:15 -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 LAA00102
          for ; Wed, 14 Oct 1998 11:07:13 -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 OAA03664;
	Wed, 14 Oct 1998 14:07:36 -0400 (EDT)
	(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Wed, 14 Oct 1998 14:07:35 -0400 (EDT)
From: Alfred Perlstein 
X-Sender: bright@porkfriedrice.ny.genx.net
To: Darren Whittaker 
cc: Mike Smith , freebsd-current@FreeBSD.ORG,
        john.young@openmarket.com
Subject: Re: problem in 3.0 
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


urm, first of all, on my box, setting  buf[0] = '\0' worked fine for me,
second why aren't you using dup2() to get proper semantics
on stderr so that it goes to the same place as stdin?

hint:

#include 

...
#ifdef CGI_DEBUG
	         dup2(STDOUT_FILENO, STDERR_FILENO);
#endif /* CGI_DEBUG */
...


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, 14 Oct 1998, Darren Whittaker wrote:

> The code appeared to work until I set buf[0] = '\0'; at the start of the
> loop, then only one message was displayed. Since err displays to std error
> and I have to run this program from a browers I did not see any error
> messages.
> 
> -Darren
> 
> ------------------
> Darren Whittaker
> Senior Software Engineer
> Small Enterprise Group
> Open Market, Inc.
> 
> On Wed, 14 Oct 1998, Mike Smith wrote:
> 
> > > The fact of the matter is that date only returned output once, why did it
> > > not return output 10 times?
> > 
> > No idea.  I can't make it fail in that fashion here, on a range of 
> > -current systems from mid-September through yesterday's snapshot.
> > 
> > Does the following:
> > 
> > #include 
> > #include 
> > 
> > void main(void) 
> > {
> >         int     i, j;
> >         char    buf[256];
> >         FILE    *p;
> > 
> >         for (i = 0; i < 100; i++) {
> >                 if ((p = popen("/bin/date", "r")) == NULL)
> >                         err(1, "popen");
> >                 fgets(buf, sizeof(buf) - 1, p);
> >                 printf(buf);
> >                 if ((pclose(p)) == -1)
> >                         err(1, "pclose");
> >         }
> > }
> > 
> > do the "right" or the "wrong" thing?
> > 
> > > -Darren
> > 
> > -- 
> > \\  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 14 12:24:57 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA11714
          for freebsd-current-outgoing; Wed, 14 Oct 1998 12:24:57 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp1.jps.net (smtp1.jps.net [209.63.224.236])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11700
          for ; Wed, 14 Oct 1998 12:24:53 -0700 (PDT)
          (envelope-from gseward@jps.net)
Received: from default (209-239-195-35.oak.jps.net [209.239.195.35])
	by smtp1.jps.net (8.8.5/8.8.5) with SMTP id MAA07856
	for ; Wed, 14 Oct 1998 12:24:34 -0700 (PDT)
Message-Id: <199810141924.MAA07856@smtp1.jps.net>
From: "Gil" 
To: current@FreeBSD.ORG
Date: Wed, 14 Oct 1998 12:24:26 -0700
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Novice question
Reply-to: gseward@jps.net
X-mailer: Pegasus Mail for Win32 (v3.01b)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I am trying to install FreeBSD over a FTP connection, and I have 
been unable to get it to recognise my PnP modem.  I set it in the 
kernel configuration at the com port address and IRQ identified by 
BIOS and it is never found.  Any ideas?

             Gil Seward

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 13:14:48 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA18600
          for freebsd-current-outgoing; Wed, 14 Oct 1998 13:14:48 -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 NAA18591
          for ; Wed, 14 Oct 1998 13:14:45 -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 VAA03407;
	Wed, 14 Oct 1998 21:12:54 +0100 (BST)
Date: Wed, 14 Oct 1998 21:12:54 +0100 (BST)
From: Doug Rabson 
To: Peter Wemm 
cc: Karl Pielorz , Edwin Culp ,
        FreeBSD-current@FreeBSD.ORG
Subject: Re: Make elf release 
In-Reply-To: <199810132359.HAA02821@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 Wed, 14 Oct 1998, Peter Wemm wrote:

> Karl Pielorz wrote:
> > 
> > 
> > Edwin Culp wrote:
> > 
> > > > I know that's one of the reasons why I've left my system running a.out ke
>     rnels
> > > > at the moment... (and I at least hope it's a good reason ;-)
> > > >
> > > > Karl
> > > 
> > > The wonderful part of it is that I haven't had anything to debug :-)  What 
>     % of
> > > the folks running current/beta debug their kernels?   The way to find the p
>     roblems
> > > is to have more people using it in its most complete form. IMO.
> > 
> > Hmmm.. Well if I'm right about not being able to debug LDK's with an ELF
> > kernel, I have to keep my kernel a.out... An LKM I'm betaing has a few
> > problems, which means it's gotta be debug(able)...
> 
> Umm, it's the other way around..  DDB can't see a.out LKM's for debugging. 
> DDB *can* see both a.out and elf KLD modules.  KLD modules are the first 
> time that DDB has worked with modular kernels.
> 
> It's GDB that is the problem - it can't see KLD modules.  Mind you, it 
> can't see LKM's either.

It should be possible to debug both with GDB with judicious use of
'add-symbol-file' with the module filename and the load address (I believe
that there is normally a fixed offset from the load address).  I have a
vague memory of writing something about this in the handbook.  Maybe I
was dreaming...

--
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 14 14:19:32 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA26940
          for freebsd-current-outgoing; Wed, 14 Oct 1998 14:19:32 -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 OAA26935
          for ; Wed, 14 Oct 1998 14:19:30 -0700 (PDT)
          (envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id QAA09437;
	Wed, 14 Oct 1998 16:19:07 -0500 (CDT)
Received: from klinzhai-104.isdn.mke.execpc.com(169.207.65.232) by peak.mountin.net via smap (V1.3)
	id sma009434; Wed Oct 14 16:18:37 1998
Message-Id: <3.0.3.32.19981014160746.0105f178@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, 14 Oct 1998 16:07:46 -0500
To: Tom 
From: "Jeffrey J. Mountin" 
Subject: Re: Installation probs w/3.0-BETA
Cc: Vijay Ramasubramanian ,
        Mike Grommet , current@FreeBSD.ORG
In-Reply-To: 
References: <3.0.3.32.19981014004150.0103ae24@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 11:15 PM 10/13/98 -0700, Tom wrote:
>  Or use parity SIMM/DIMM and then there is zero guess work.  Rather than
>a mysterious non-reproducable crash, you will get a parity failed panic.
>Everyone should use parity memory all the time.

True, but how many actually do install parity memory in their servers, let
alone workstations.  Had I waited one week longer for a 128MB DIMM, the
price dropped enough to where I would have paid the same for parity.  Not a
server, which should have parity, but paying 50% more for a workstation...

>  Just like any other FreeBSD app:  as much as is available.  Since the
>install does a lot of i/o most of memory will probably put to work as a
>disk cache.

Though so.


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 14 14:21:28 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA27326
          for freebsd-current-outgoing; Wed, 14 Oct 1998 14:21:28 -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 OAA27310
          for ; Wed, 14 Oct 1998 14:21:21 -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 RAA14039;
	Wed, 14 Oct 1998 17:20:50 -0400 (EDT)
	(envelope-from wollman)
Date: Wed, 14 Oct 1998 17:20:50 -0400 (EDT)
From: Garrett Wollman 
Message-Id: <199810142120.RAA14039@khavrinen.lcs.mit.edu>
To: "Jeffrey J. Mountin" 
Cc: Tom , Vijay Ramasubramanian ,
        Mike Grommet , current@FreeBSD.ORG
Subject: Re: Installation probs w/3.0-BETA
In-Reply-To: <3.0.3.32.19981014160746.0105f178@207.227.119.2>
References: <3.0.3.32.19981014004150.0103ae24@207.227.119.2>
	
	<3.0.3.32.19981014160746.0105f178@207.227.119.2>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

< said:

> price dropped enough to where I would have paid the same for parity.  Not a
> server, which should have parity, but paying 50% more for a workstation...

No, a server should have ECC.

-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  Wed Oct 14 14:36:53 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA00322
          for freebsd-current-outgoing; Wed, 14 Oct 1998 14:36: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 OAA00317
          for ; Wed, 14 Oct 1998 14:36:52 -0700 (PDT)
          (envelope-from obrien@NUXI.com)
Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id OAA02900; Wed, 14 Oct 1998 14:36:28 -0700 (PDT)
Message-ID: <19981014143628.A2881@nuxi.com>
Date: Wed, 14 Oct 1998 14:36:28 -0700
From: "David O'Brien" 
To: Dan Strick , current@FreeBSD.ORG
Subject: Re: two other nits in 3.0-19981009-BETA
Reply-To: obrien@NUXI.com
References: <199810101342.GAA01558@math.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199810101342.GAA01558@math.berkeley.edu>; from Dan Strick on Sat, Oct 10, 1998 at 06:42:34AM -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

> So far I have not noticed any X11 related problems with the ports,

this belongs in freebsd-ports@freebsd.org

-- 
-- 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  Wed Oct 14 14:40:27 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA00953
          for freebsd-current-outgoing; Wed, 14 Oct 1998 14:40:27 -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 OAA00944
          for ; Wed, 14 Oct 1998 14:40:25 -0700 (PDT)
          (envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id QAA09608;
	Wed, 14 Oct 1998 16:40:08 -0500 (CDT)
Received: from klinzhai-104.isdn.mke.execpc.com(169.207.65.232) by peak.mountin.net via smap (V1.3)
	id sma009603; Wed Oct 14 16:39:44 1998
Message-Id: <3.0.3.32.19981014162850.01060ba8@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, 14 Oct 1998 16:28:50 -0500
To: Garrett Wollman 
From: "Jeffrey J. Mountin" 
Subject: Re: Installation probs w/3.0-BETA
Cc: current@FreeBSD.ORG
In-Reply-To: <199810142120.RAA14039@khavrinen.lcs.mit.edu>
References: <3.0.3.32.19981014160746.0105f178@207.227.119.2>
 <3.0.3.32.19981014004150.0103ae24@207.227.119.2>
 
 <3.0.3.32.19981014160746.0105f178@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 05:20 PM 10/14/98 -0400, Garrett Wollman wrote:
>> price dropped enough to where I would have paid the same for parity.  Not a
>> server, which should have parity, but paying 50% more for a workstation...
>
>No, a server should have ECC.

Oops!  There is a difference., but it's a habit to say parity.  Rolls off
the tongue easier, but George Carlin would like ECC better. 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 14 14:41:41 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA01098
          for freebsd-current-outgoing; Wed, 14 Oct 1998 14:41:41 -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 OAA01091
          for ; Wed, 14 Oct 1998 14:41:38 -0700 (PDT)
          (envelope-from sthaug@nethelp.no)
From: sthaug@nethelp.no
Received: (qmail 22036 invoked by uid 1001); 14 Oct 1998 21:41:20 +0000 (GMT)
To: jeff-ml@mountin.net
Cc: current@FreeBSD.ORG
Subject: Re: Installation probs w/3.0-BETA
In-Reply-To: Your message of "Wed, 14 Oct 1998 16:07:46 -0500"
References: <3.0.3.32.19981014160746.0105f178@207.227.119.2>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Wed, 14 Oct 1998 23:41:20 +0200
Message-ID: <22034.908401280@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> True, but how many actually do install parity memory in their servers, let

Everybody who cares about their data?

> alone workstations.  Had I waited one week longer for a 128MB DIMM, the
> price dropped enough to where I would have paid the same for parity.  Not a
> server, which should have parity, but paying 50% more for a workstation...

I take ECC memory for granted in servers, and that's what I've installed
in all my servers. The only exception being my first Pentium server which
had a 430FX chipset and couldn't use parity/ECC.

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 14 14:47:49 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA02165
          for freebsd-current-outgoing; Wed, 14 Oct 1998 14:47:49 -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 OAA02142
          for ; Wed, 14 Oct 1998 14:47: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 PAA08251;
	Wed, 14 Oct 1998 15:47:22 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id PAA07468; Wed, 14 Oct 1998 15:47:21 -0600
Date: Wed, 14 Oct 1998 15:47:21 -0600
Message-Id: <199810142147.PAA07468@mt.sri.com>
From: Nate Williams 
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Sheldon Hearn 
Cc: current@FreeBSD.ORG
Subject: Re: syslog.conf comment about tabs
In-Reply-To: <20150.908397220@iafrica.com>
References: <20150.908397220@iafrica.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[ Moved to -current, this is certainly not security related ]

> It's a pity that, after all the discussion about syslog's
> differentiation between tabs and spaces, nothing was actually done about
> it. This is especially sad given that 3.0-RELEASE is about to be
                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^ 
> snapped.
  ^^^^^^^^
> 
> When someone with commit privs has some time (does this sound like
> millenium hype? ;) it'd be great to see PR8162 making it into the
> repository.

Given that we're about to 'release' FreeBSD, a change that affects a
critical part of the system that is not a bugfix should never be
committed since it might break something.

It is being ignored *because* it's too late to commit a fix that isn't
necessary and has potentially 'huge' destablizing possibilities.




Nate

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 15:03:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA04557
          for freebsd-current-outgoing; Wed, 14 Oct 1998 15:03:58 -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 PAA04541
          for ; Wed, 14 Oct 1998 15:03:54 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id XAA09039
	for ; Wed, 14 Oct 1998 23:03:37 +0100 (BST)
Message-ID: <36251F7D.FF67BC99@tdx.co.uk>
Date: Wed, 14 Oct 1998 23:02:37 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: current@FreeBSD.ORG
Subject: R-Day, 15th October, 1998 (BST or similar ;-)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In less than 2 hours it will be the 15th of October BST...

Jordan has been quiet the last couple of days... (rather ominously perhaps)?

The questions are? 1. Is 'it' still happening (3.0-Release), and 2. What's
happening? (with respect to 3.0-Release)

Kp

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 15:38:19 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA09975
          for freebsd-current-outgoing; Wed, 14 Oct 1998 15:38:19 -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 PAA09961
          for ; Wed, 14 Oct 1998 15:38:13 -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 PAA29897;
	Wed, 14 Oct 1998 15:38:05 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Karl Pielorz 
cc: current@FreeBSD.ORG
Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) 
In-reply-to: Your message of "Wed, 14 Oct 1998 23:02:37 BST."
             <36251F7D.FF67BC99@tdx.co.uk> 
Date: Wed, 14 Oct 1998 15:38:05 -0700
Message-ID: <29893.908404685@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> In less than 2 hours it will be the 15th of October BST...

My release target date is in PST. :)

> Jordan has been quiet the last couple of days... (rather ominously perhaps)?

Naw, just rather busy...

> The questions are? 1. Is 'it' still happening (3.0-Release), and 2. What's
> happening? (with respect to 3.0-Release)

1. I'm still trying to hit my target time of October 15th, 20:00 PST
   for putting down the release tag, after which I'll announce the
   end of code free^H^H^H^Hslush and people can dive back into -current
   with all their experimental goodies.

2. We've been known to slip our dates in the past, and if the tree
   is broken or otherwise "unready" at that time, it may not happen
   on the 15th.  I'll send mail either way when the tag is going down
   or has been postponed.

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 15:41:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA10394
          for freebsd-current-outgoing; Wed, 14 Oct 1998 15:41:35 -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 PAA10381
          for ; Wed, 14 Oct 1998 15:41:33 -0700 (PDT)
          (envelope-from obrien@NUXI.com)
Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id PAA03476; Wed, 14 Oct 1998 15:40:36 -0700 (PDT)
Message-ID: <19981014154036.A3425@nuxi.com>
Date: Wed, 14 Oct 1998 15:40:36 -0700
From: "David O'Brien" 
To: "Viren R. Shah" 
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: 3.0-19981009-BETA install report
Reply-To: obrien@NUXI.com
References: <199810112053.QAA00317@jabberwock.rstcorp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199810112053.QAA00317@jabberwock.rstcorp.com>; from Viren R. Shah on Sun, Oct 11, 1998 at 04:53:31PM -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

> BTW: the original NIC I had in this machine was a SMC EZCARD10
> (SMC1660BTA). It was recognized (after I changed it to irq 5 and
> 0x300), but it could never sucessfully use it since I couldn't find

The default for ed0 is irq 10, I/O addr 0x280, mem addr 0xd8000.
Why was the change to irq 5 & I/O 0x300 necessary?

-- 
-- 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  Wed Oct 14 15:48:29 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA11437
          for freebsd-current-outgoing; Wed, 14 Oct 1998 15:48:29 -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 PAA11430
          for ; Wed, 14 Oct 1998 15:48:25 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from localhost (kpielorz@localhost)
	by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id XAA09186;
	Wed, 14 Oct 1998 23:47:55 +0100 (BST)
Date: Wed, 14 Oct 1998 23:47:55 +0100 (BST)
From: Karl Pielorz 
To: "Jordan K. Hubbard" 
cc: current@FreeBSD.ORG
Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) 
In-Reply-To: <29893.908404685@time.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 Wed, 14 Oct 1998, Jordan K. Hubbard wrote:

> > In less than 2 hours it will be the 15th of October BST...
> 
> My release target date is in PST. :)

Hmmm... It's still within +/- 12 Hours isn't it (wost case)? - Unless
theres something you haven't been telling us? 

> > Jordan has been quiet the last couple of days... (rather ominously perhaps)?
> 
> Naw, just rather busy...

Yeah, tell me about it, and I don't even have to look after FBSD on a
regular basis :-)

> 1. I'm still trying to hit my target time of October 15th, 20:00 PST
>    for putting down the release tag, after which I'll announce the
>    end of code free^H^H^H^Hslush and people can dive back into -current
>    with all their experimental goodies.

Sounds good (digs out documentation to convert PST to BST ;-) ...

> 2. We've been known to slip our dates in the past, and if the tree
>    is broken or otherwise "unready" at that time, it may not happen
>    on the 15th.  I'll send mail either way when the tag is going down
>    or has been postponed.

Thanks! - At least I'll know either way - and when to start hitting people
with "Hey, why _aren't_ you running FreeBSD 3.0"  etc. ;-)

I must admit I was at least sceptical at first, but 3.0 (including all the
rough edges) seems to be taking shape quite nicely... The ports tree is
still a bit 'in transition' but a.out to elf is no 24hr feat... ;-)

Regards,

Karl


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 16:22:41 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA16854
          for freebsd-current-outgoing; Wed, 14 Oct 1998 16:22:41 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.dyn.ml.org (sf3-72.ppp.wenet.net [206.15.84.72])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16849
          for ; Wed, 14 Oct 1998 16:22:39 -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 QAA00946;
	Wed, 14 Oct 1998 16:24:10 -0700 (PDT)
	(envelope-from garbanzo@hooked.net)
X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs
Date: Wed, 14 Oct 1998 16:24:09 -0700 (PDT)
From: Alex Zepeda 
X-Sender: garbanzo@zippy.dyn.ml.org
To: Terry Lambert 
cc: perlsta@fs3.ny.genx.net, current@FreeBSD.ORG
Subject: Re: /usr/include/sys/cam/scsi...
In-Reply-To: <199810142222.PAA00628@usr04.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 Wed, 14 Oct 1998, Terry Lambert wrote:
[...]
> CVS is the tree archive format.  CVSup is merely a transport and
> synchronization method.

Welp, split hairs if you want to, but I don't keep a copy of the RCS files
locally.


> Well, you could rm -rf /usr/include and then cd /usr/src/include
> and make install.

Nope.  This misses stuff like zlib.h, and perhaps a few more.

> By definition, files stuffed into /usr/include instead of /usr/local/include
> are not innocent.

This is not what I'm talking about.

- 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 14 16:59:09 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA21809
          for freebsd-current-outgoing; Wed, 14 Oct 1998 16:59:09 -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 QAA21791
          for ; Wed, 14 Oct 1998 16:59:03 -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 HAA08409;
	Thu, 15 Oct 1998 07:30:47 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810142330.HAA08409@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Alex Zepeda 
cc: Terry Lambert , perlsta@fs3.ny.genx.net,
        current@FreeBSD.ORG
Subject: Re: /usr/include/sys/cam/scsi... 
In-reply-to: Your message of "Wed, 14 Oct 1998 16:24:09 MST."
              
Date: Thu, 15 Oct 1998 07:30:46 +0800
From: Peter Wemm 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alex Zepeda wrote:
[..]
> > Well, you could rm -rf /usr/include and then cd /usr/src/include
> > and make install.
> 
> Nope.  This misses stuff like zlib.h, and perhaps a few more.

This is what 'cd /usr/src; make -DCLOBBER includes' is for..  It catches
all the known include files.

Cheers,
-Peter




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 18:16:52 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA03576
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:16:52 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheops.anu.edu.au (cheops.anu.edu.au [150.203.224.24])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03564
          for ; Wed, 14 Oct 1998 18:16:49 -0700 (PDT)
          (envelope-from bryan@coombs.anu.edu.au)
Message-Id: <199810150116.SAA03564@hub.freebsd.org>
Received: by cheops.anu.edu.au
	(1.37.109.16/16.2) id AA138694181; Thu, 15 Oct 1998 11:16:21 +1000
From: bryan collins 
Subject: /usr/sbin/arp: actual retrieval of routing table
To: freebsd-current@FreeBSD.ORG
Date: Thu, 15 Oct 1998 11:16:21 +1000 (EST)
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,

I'm running FreeBSD 3.0-19980925-BETA on a P133.
Its not doing much but monitoring the network for IP usage.
(a few scripts to force arp requests for each IP iin a subnet)

I run a script from cron to compare the machines arp table with
my arp database.

occasionaly I get the error message in the subject

/usr/sbin/arp: actual retrieval of routing table
 
and doesnt print the arp table.

the command is '/usr/sbin/arp -an' which runs every 60 seconds.
the arp table has around 300-400 entries all the time.

have i come across some limitation for the table?

I dont know if this is related to being -current, but thought I'd try
here since thats what I'm running.

Any ideas?

Thanks

Bry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 18:22:42 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA04969
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:22:42 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04958
          for ; Wed, 14 Oct 1998 18:22:40 -0700 (PDT)
          (envelope-from karl@Genesis.Denninger.Net)
Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id UAA00212 for current@freebsd.org; Wed, 14 Oct 1998 20:22:22 -0500 (CDT)
Message-ID: <19981014202222.A208@Denninger.Net>
Date: Wed, 14 Oct 1998 20:22:22 -0500
From: Karl Denninger 
To: current@FreeBSD.ORG
Subject: Uh, guys, BETA 3.0 right now panics on boot
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
Organization: Karl's Sushi and Packet Smashers
X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Immediate panic, no dump, "supervisor page not present".  Never even starts
probing devices.

Bad, bad stuff!

--
-- 
Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl
I ain't even *authorized* to speak for anyone other than myself, so give
up now on trying to associate my words with any particular organization.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 18:23:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA05104
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:23:58 -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 SAA05094
          for ; Wed, 14 Oct 1998 18:23:55 -0700 (PDT)
          (envelope-from dag-erli@ifi.uio.no)
Received: from hindarfjell.ifi.uio.no (2602@hindarfjell.ifi.uio.no [129.240.64.130])
	by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id DAA18763
	for ; Thu, 15 Oct 1998 03:23:33 +0200 (MET DST)
Received: (from dag-erli@localhost) by hindarfjell.ifi.uio.no ; Thu, 15 Oct 1998 03:23:33 +0200 (MET DST)
Mime-Version: 1.0
To: current@FreeBSD.ORG
Subject: Warning: libc breakage
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: 15 Oct 1998 03:23:32 +0200
Message-ID: 
Lines: 20
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 SAA05095
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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 $

If you have 1.8 you have the bug. Recompile libc by running:

# cd /usr/src/lib/libc
# make all && make install -DNOMAN

I'll blame it on Bruce, who reviewed my code but didn't spot the 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  Wed Oct 14 18:24:21 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA05306
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:24:21 -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 SAA05206
          for ; Wed, 14 Oct 1998 18:24:15 -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 SAA00583;
	Wed, 14 Oct 1998 18:27:51 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810150127.SAA00583@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Darren Whittaker 
cc: Mike Smith , freebsd-current@FreeBSD.ORG,
        john.young@openmarket.com
Subject: Re: problem in 3.0 
In-reply-to: Your message of "Wed, 14 Oct 1998 11:28:10 MDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 14 Oct 1998 18:27:51 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> The code appeared to work until I set buf[0] = '\0'; at the start of the
> loop, then only one message was displayed. Since err displays to std error
> and I have to run this program from a browers I did not see any error
> messages.

I specifically asked what the exact code below does when built as a 
program and run on your system.

If setting buf[0] to 0 kills all but the first output, you should be 
checking the return from fgets, as it's likely that it's not returning 
anything.

> -Darren
> 
> ------------------
> Darren Whittaker
> Senior Software Engineer
> Small Enterprise Group
> Open Market, Inc.
> 
> On Wed, 14 Oct 1998, Mike Smith wrote:
> 
> > > The fact of the matter is that date only returned output once, why did it
> > > not return output 10 times?
> > 
> > No idea.  I can't make it fail in that fashion here, on a range of 
> > -current systems from mid-September through yesterday's snapshot.
> > 
> > Does the following:
> > 
> > #include 
> > #include 
> > 
> > void main(void) 
> > {
> >         int     i, j;
> >         char    buf[256];
> >         FILE    *p;
> > 
> >         for (i = 0; i < 100; i++) {
> >                 if ((p = popen("/bin/date", "r")) == NULL)
> >                         err(1, "popen");
> >                 fgets(buf, sizeof(buf) - 1, p);
> >                 printf(buf);
> >                 if ((pclose(p)) == -1)
> >                         err(1, "pclose");
> >         }
> > }
> > 
> > do the "right" or the "wrong" thing?
> > 
> > > -Darren
> > 
> > -- 
> > \\  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
> 

-- 
\\  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 14 18:24:27 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA05348
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:24:27 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cockatoo.aus.org (cockatoo.aus.org [199.166.246.189])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05245
          for ; Wed, 14 Oct 1998 18:24:18 -0700 (PDT)
          (envelope-from lh@cockatoo.aus.org)
Received: (from lh@localhost)
	by cockatoo.aus.org (8.9.1/8.8.8) id VAA11481
	for current@freebsd.org; Wed, 14 Oct 1998 21:23:49 -0400 (EDT)
	(envelope-from lh)
Message-ID: 
X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Wed, 14 Oct 1998 21:23:48 -0400 (EDT)
From: Luke 
To: current@FreeBSD.ORG
Subject: 3.0-BETA man/groff/troff problem
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have been running 3.0-BETA for a couple of days now and haven't had any luck
with any version of man/groff/troff working. man seems fine, then groff cant
find 'DESC' files. giving groff a path with the -F option works but then troff
coredumps. I'm not 100% sure what I am doing but I ran gdb troff it says:

Program received signal SIGSEGV, Segmentation fault.
0x805f5bb in input_stack::get_location (allow_macro=1, filenamep=0x808604c,
    linenop=0x8086050)
    at
/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:514
514         if (p->get_location(allow_macro, filenamep, linenop))

bt after that shows:

#0  0x805f5bb in input_stack::get_location (allow_macro=1,
    filenamep=0x808604c, linenop=0x8086050)
    at
/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:514
#1  0x8063b02 in macro::macro (this=0x8086040)
    at
/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:2407
#2  0x806b6bc in set_string (name=0x807ef5d ".T", value=0x8081260 "ps")
    at
/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:5302
#3  0x806bc5c in main (argc=1, argv=0xefbfdbd8)
    at
/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:5452
#4  0x8048d6e in _start ()

one other note, I tried to build the groff in contrib and it gave the following
error when running configure:

checking that C++ static constructors and destructors are called... no
configure: error: a working C++ compiler is required

I hope the information helps, If someone needs more detail I can try and help


---

E-Mail: Luke 
Sent by XFMail
----------------------------------

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 18:24:56 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA05403
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:24: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 SAA05394
          for ; Wed, 14 Oct 1998 18:24:51 -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 KAA03225;
	Thu, 15 Oct 1998 10:53:06 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.1/8.9.0) id KAA01861;
	Thu, 15 Oct 1998 10:52:46 +0930 (CST)
Message-ID: <19981015105245.H586@freebie.lemis.com>
Date: Thu, 15 Oct 1998 10:52:45 +0930
From: Greg Lehey 
To: Julian Elischer , Mike Smith 
Cc: Brian Feldman ,
        "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem
References: <199810141604.JAA01077@dingo.cdrom.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: ; from Julian Elischer on Wed, Oct 14, 1998 at 10:28:14AM -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 Wednesday, 14 October 1998 at 10:28:14 -0700, Julian Elischer wrote:
> On Wed, 14 Oct 1998, Mike Smith wrote:
>>> Perhaps this could be the problem with NFS "hanging" certain people all
>>> the time? (not the pine thing) The system spending way too much time
>>> inside the kernel transmitting NFS packets....
>>
>> No.  Lack of ACCESS caching makes us slow and eats the network (because
>> we are very good at generating/sending/receiving them).
>>
>> If there's someone out there that wants to work with the very best NFS
>> people in the business to sort out our problems, please let me know.
>> NetApp are keen to see our issues resolved (it will mean less angst
>> for them in the long run, as they have many FreeBSD-using customers).
>>
>> Right now, we are accumulating a bad NFS reputation. 8(
>
> I thought kirk was doing that....

I hope not.

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 14 18:26:32 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA05683
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:26:32 -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 SAA05634
          for ; Wed, 14 Oct 1998 18:26:26 -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 KAA03232;
	Thu, 15 Oct 1998 10:54:54 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.1/8.9.0) id KAA01892;
	Thu, 15 Oct 1998 10:54:51 +0930 (CST)
Message-ID: <19981015105450.I586@freebie.lemis.com>
Date: Thu, 15 Oct 1998 10:54:50 +0930
From: Greg Lehey 
To: Doug Rabson , Peter Wemm 
Cc: Karl Pielorz , Edwin Culp ,
        FreeBSD-current@FreeBSD.ORG
Subject: Re: Make elf release
References: <199810132359.HAA02821@spinner.netplex.com.au> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: ; from Doug Rabson on Wed, Oct 14, 1998 at 09:12:54PM +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, 14 October 1998 at 21:12:54 +0100, Doug Rabson wrote:
> On Wed, 14 Oct 1998, Peter Wemm wrote:
>> Karl Pielorz wrote:
>>> Hmmm.. Well if I'm right about not being able to debug LDK's with an ELF
>>> kernel, I have to keep my kernel a.out... An LKM I'm betaing has a few
>>> problems, which means it's gotta be debug(able)...
>>
>> Umm, it's the other way around..  DDB can't see a.out LKM's for debugging.
>> DDB *can* see both a.out and elf KLD modules.  KLD modules are the first
>> time that DDB has worked with modular kernels.
>>
>> It's GDB that is the problem - it can't see KLD modules.  Mind you, it
>> can't see LKM's either.
>
> It should be possible to debug both with GDB with judicious use of
> 'add-symbol-file' with the module filename and the load address (I believe
> that there is normally a fixed offset from the load address).  I have a
> vague memory of writing something about this in the handbook.  Maybe I
> was dreaming...

What you describe is pretty much the way it works with LKMs today.
What I've understood is that KLDs will be different.

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 14 18:31:24 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA06760
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:31:24 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06744
          for ; Wed, 14 Oct 1998 18:31:19 -0700 (PDT)
          (envelope-from karl@Genesis.Denninger.Net)
Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id UAA00258 for current@freebsd.org; Wed, 14 Oct 1998 20:31:03 -0500 (CDT)
Message-ID: <19981014203102.A254@Denninger.Net>
Date: Wed, 14 Oct 1998 20:31:02 -0500
From: Karl Denninger 
To: current@FreeBSD.ORG
Subject: More info
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
Organization: Karl's Sushi and Packet Smashers
X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On the crash I'm getting on boot now.

A kernel from 8 October works fine.

--
-- 
Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl
I ain't even *authorized* to speak for anyone other than myself, so give
up now on trying to associate my words with any particular organization.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 18:33:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA07162
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:33:58 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from tor-dev1.nbc.netcom.ca (tor-dev1.nbc.netcom.ca [207.181.89.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07156
          for ; Wed, 14 Oct 1998 18:33:56 -0700 (PDT)
          (envelope-from taob@tor-dev1.nbc.netcom.ca)
Received: (from taob@localhost)
	by tor-dev1.nbc.netcom.ca (8.8.8/8.8.8) id VAA09992;
	Wed, 14 Oct 1998 21:33:15 -0400 (EDT)
Date: Wed, 14 Oct 1998 21:33:15 -0400 (EDT)
From: Brian Tao 
X-Sender: taob@tor-dev1.nbc.netcom.ca
To: "Richard Seaman, Jr." 
cc: "current@FreeBSD.ORG" 
Subject: Re: Recent 3.0's are Depressing
In-Reply-To: <199810141552.KAA02913@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 Wed, 14 Oct 1998, Richard Seaman, Jr. wrote:
> 
> I'd be curious if the problem still exists with a libc_r that is
> completely up to date.  There were some changes to the thread
> scheduler after October 1.  

    Trying that right now, with a newsfeed and an artificial load of
100 NNTP readers.  cvsupped around noon today and rebuilt the a.out
libraries:

% ldd /depot/news/bin/typhoond-1.1.7-dynamic 
/depot/news/bin/typhoond-1.1.7-dynamic:
        -lcrypt.2 => /usr/lib/aout/libcrypt.so.2.0 (0x20097000)
        -lc_r.3 => /usr/lib/aout/libc_r.so.3.0 (0x2009a000)

% ls -l /usr/lib/aout/libc_r.so.3.0
-r--r--r--  1 root  wheel  547350 Oct 14 14:04 /usr/lib/aout/libc_r.so.3.0

-- 
Brian Tao (BT300, taob@risc.org)
"Though this be madness, yet there is method in'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 14 18:37:36 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA07680
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:37:36 -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 SAA07671
          for ; Wed, 14 Oct 1998 18:37:35 -0700 (PDT)
          (envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id UAA10398;
	Wed, 14 Oct 1998 20:36:43 -0500 (CDT)
Received: from harkol-12.isdn.mke.execpc.com(169.207.64.140) by peak.mountin.net via smap (V1.3)
	id sma010396; Wed Oct 14 20:36:41 1998
Message-Id: <3.0.3.32.19981014202548.01070e84@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, 14 Oct 1998 20:25:48 -0500
To: obrien@NUXI.com, Dan Strick , current@FreeBSD.ORG
From: "Jeffrey J. Mountin" 
Subject: Re: two other nits in 3.0-19981009-BETA
Cc: "Jordan K. Hubbard" 
In-Reply-To: <19981014143628.A2881@nuxi.com>
References: <199810101342.GAA01558@math.berkeley.edu>
 <199810101342.GAA01558@math.berkeley.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 02:36 PM 10/14/98 -0700, David O'Brien wrote:
>> So far I have not noticed any X11 related problems with the ports,
>
>this belongs in freebsd-ports@freebsd.org

Ummmm... not really.  Just replied to the wrong message.


----
Date: Sat, 10 Oct 1998 00:56:11 -0700 (PDT)
From: "Jordan K. Hubbard" 
Message-Id: <199810100756.AAA14823@time.cdrom.com>
To: current@FreeBSD.ORG
Subject: ftp://ftp.freebsd.org/pub/FreeBSD/3.0-19981009-BETA now available
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.ORG

Release day is less than a week away - please test this one as much
as you can, including the various X bits.  There's still a bit of contraversy
over the X11/config hacks we've made, so tell us how the X11-using ports
work in this release also.

- Jordan
----


FWIW, Installed X for the first time in ages and kde (first time) as well,
not a hitch with -current as of 5:30PM CDT yesterday.  Before that I had
the scsi.h problem.  Time to sup, build, and install once more. 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 14 18:54:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA09531
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:54:59 -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 SAA09514
          for ; Wed, 14 Oct 1998 18:54:55 -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 SAA00818;
	Wed, 14 Oct 1998 18:57:11 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810150157.SAA00818@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Karl Denninger 
cc: current@FreeBSD.ORG
Subject: Re: Uh, guys, BETA 3.0 right now panics on boot 
In-reply-to: Your message of "Wed, 14 Oct 1998 20:22:22 CDT."
             <19981014202222.A208@Denninger.Net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 14 Oct 1998 18:57:11 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Immediate panic, no dump, "supervisor page not present".  Never even starts
> probing devices.

If you're using the new bootloader, go slap Peter Wemm; it's breakage 
in his changes to the preload code (specifically, relocations).

-- 
\\  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 14 18:57:31 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA09999
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:57:31 -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 SAA09970
          for ; Wed, 14 Oct 1998 18:57:26 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp02.primenet.com (8.8.8/8.8.8) id SAA16458;
	Wed, 14 Oct 1998 18:57:04 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp02.primenet.com, id smtpd016436; Wed Oct 14 18:56:57 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id SAA17973;
	Wed, 14 Oct 1998 18:56:55 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810150156.SAA17973@usr04.primenet.com>
Subject: Re: SoftUpdates anomaly: what happens when you 'mount -u -o ro /usr'?
To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=)
Date: Thu, 15 Oct 1998 01:56:54 +0000 (GMT)
Cc: current@FreeBSD.ORG
In-Reply-To:  from "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" at Oct 14, 98 05:06:45 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

What happens is that dependent data on the FS itself gets written out,
but depedent data on the device vnode that the FS is mounted on does
not.

Basically, this is a systemic problem which has not been addressed,
and it's the primary reason soft updates is a tunefs parameter
instead of a mount option.

I basically think that this is the wrong implementation, and I
have argued with both Kirk and Julian about it on occasion (my
personal take is that the act of a mount update should in fact
unmount and then remount the device, syncing all buffers on the
unmount).

If you explicitly unmount the partition, then re-mount it, I
believe it should work (obviously, you will have to try this
with a partition other than /usr).

The place to hide this is in the kernel in the common mount
code, and then to instance the mounts seperately from their
mappings into the FS hierarchy, so that the FS specific mount
code can get a hell of a lot more simple.  This turns a -o
into a call to the FS specific unmount, then the FS specific
mount, while leaving the objects allocated on the FS intact
(it becomes the job of the common mount code to do the object
destruction).

The only wierd thing this implies is that, if the FS is managing
it's own vnode pool, that there be seperate entry points for
initialization and destruction of the pool, other than the
ones that would have been implied by the mount/unmount.  This
is only an issue for things like CODA and TFS, so it's not a
worry that has to be dealt with immediately.


> I woke up to find my nightly doc build had failed due to a full /usr
> partition. It's a 256MB partition with 160MB of data on it, so there
> had to be a catch somewhere. I ran 'fsck -n' which revealed 13,500
> unreferenced files.

Sounds like the soft clock had not had an opportunity to drain.
You should have done a vmstat to see how many soft updates buffers
were in use, and if the number was decreasing, or if there was a
real problem (for a mounted FS with uncommitted softclock contents,
what you saw is pretty much expected behaviour).


> Now looking through the fsck output (I scripted it) it seems that the
> unreferenced files were mostly binaries, and I bet if I looked closer
> I'd find out the mtimes are consistent with days I've run make world.
> What's more, I'm not missing any files; my bet is that the
> unreferenced files are files which have been deleted (replaced) by
> installworld. They're unreferenced because they were unlinked, but for
> some reason they were never freed. I think somebody with more fs
> experience than I have should take a look at what happens to a
> softupdates fs when it is switched from rw to ro. It seems obvious to
> me that pending writes should be flushed; it also appears that this
> doesn't actually happen.

This may be a real dependency issue, actually, or it may just be that
the programs were used in the buildworld, and were still cached, so
the cache was holding a reference on them, and they would eventually
go away.

I would be kind of surprised if there were a real dependency issue,
unless the recent vfs_subr.c changes were at fault.


					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 14 18:58:47 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA10277
          for freebsd-current-outgoing; Wed, 14 Oct 1998 18:58:47 -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 SAA10272
          for ; Wed, 14 Oct 1998 18:58:43 -0700 (PDT)
          (envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id UAA10446;
	Wed, 14 Oct 1998 20:58:13 -0500 (CDT)
Received: from harkol-12.isdn.mke.execpc.com(169.207.64.140) by peak.mountin.net via smap (V1.3)
	id sma010444; Wed Oct 14 20:58:09 1998
Message-Id: <3.0.3.32.19981014204717.0107000c@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, 14 Oct 1998 20:47:17 -0500
To: "Jordan K. Hubbard" ,
        Karl Pielorz 
From: "Jeffrey J. Mountin" 
Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) 
Cc: current@FreeBSD.ORG
In-Reply-To: <29893.908404685@time.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 03:38 PM 10/14/98 -0700, Jordan K. Hubbard wrote:
>> In less than 2 hours it will be the 15th of October BST...
>
>My release target date is in PST. :)
>
>> Jordan has been quiet the last couple of days... (rather ominously
perhaps)?
>
>Naw, just rather busy...

Wonder why. ;)

>> The questions are? 1. Is 'it' still happening (3.0-Release), and 2. What's
>> happening? (with respect to 3.0-Release)
>
>1. I'm still trying to hit my target time of October 15th, 20:00 PST
>   for putting down the release tag, after which I'll announce the
>   end of code free^H^H^H^Hslush and people can dive back into -current
>   with all their experimental goodies.
>
>2. We've been known to slip our dates in the past, and if the tree
>   is broken or otherwise "unready" at that time, it may not happen
>   on the 15th.  I'll send mail either way when the tag is going down
>   or has been postponed.

One wonders if Jordan has been busy on working on the bootloader issue...
Have yet to hear more than "we should" or "we shouldn't" and kernel ELF vs
aout (ad naseum - which certainly isn't going to happen) are getting rather
stale.

Was anything definitive decided?  Or is it going to wait for the next release?


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 14 19:00:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA10600
          for freebsd-current-outgoing; Wed, 14 Oct 1998 19:00:35 -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 TAA10552
          for ; Wed, 14 Oct 1998 19:00:23 -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 JAA08855;
	Thu, 15 Oct 1998 09:29:57 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810150129.JAA08855@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Greg Lehey 
cc: Doug Rabson , Karl Pielorz ,
        Edwin Culp , FreeBSD-current@FreeBSD.ORG
Subject: Re: Make elf release 
In-reply-to: Your message of "Thu, 15 Oct 1998 10:54:50 +0930."
             <19981015105450.I586@freebie.lemis.com> 
Date: Thu, 15 Oct 1998 09:29:56 +0800
From: Peter Wemm 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Greg Lehey wrote:
> On Wednesday, 14 October 1998 at 21:12:54 +0100, Doug Rabson wrote:
> > On Wed, 14 Oct 1998, Peter Wemm wrote:
> >> Karl Pielorz wrote:
> >>> Hmmm.. Well if I'm right about not being able to debug LDK's with an ELF
> >>> kernel, I have to keep my kernel a.out... An LKM I'm betaing has a few
> >>> problems, which means it's gotta be debug(able)...
> >>
> >> Umm, it's the other way around..  DDB can't see a.out LKM's for debugging.
> >> DDB *can* see both a.out and elf KLD modules.  KLD modules are the first
> >> time that DDB has worked with modular kernels.
> >>
> >> It's GDB that is the problem - it can't see KLD modules.  Mind you, it
> >> can't see LKM's either.
> >
> > It should be possible to debug both with GDB with judicious use of
> > 'add-symbol-file' with the module filename and the load address (I believe
> > that there is normally a fixed offset from the load address).  I have a
> > vague memory of writing something about this in the handbook.  Maybe I
> > was dreaming...
> 
> What you describe is pretty much the way it works with LKMs today.
> What I've understood is that KLDs will be different.

This works the same with KLD as well, see my previous mail on the subject
which included a demo.  The major difference between LKM's and KLD's is
that DDB works with KLD with full symbols.

> Greg

Cheers,
-Peter




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 19:05:45 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA11554
          for freebsd-current-outgoing; Wed, 14 Oct 1998 19:05:45 -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 TAA11547
          for ; Wed, 14 Oct 1998 19:05:43 -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 WAA21103;
	Wed, 14 Oct 1998 22:05:27 -0400 (EDT)
Date: Wed, 14 Oct 1998 22:05:26 -0400 (EDT)
From: Brian Feldman 
To: Gil 
cc: current@FreeBSD.ORG
Subject: Re: Novice question
In-Reply-To: <199810141924.MAA07856@smtp1.jps.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

All I know is that sysinstall (hence the GENERIC kernel too) disk does NOT
have PnP, and I don't see one goddamned reason it shouldn't have PnP in
3.0-RELEASE! Along with installing ELF bootability. HEAR ME JKH? 

Brian Feldman

On Wed, 14 Oct 1998, Gil wrote:

> I am trying to install FreeBSD over a FTP connection, and I have 
> been unable to get it to recognise my PnP modem.  I set it in the 
> kernel configuration at the com port address and IRQ identified by 
> BIOS and it is never found.  Any ideas?
> 
>              Gil Seward
> 
> 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 14 19:13:44 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA12705
          for freebsd-current-outgoing; Wed, 14 Oct 1998 19:13:44 -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 TAA12700
          for ; Wed, 14 Oct 1998 19:13:42 -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 TAA04464;
	Wed, 14 Oct 1998 19:13:39 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: "Jeffrey J. Mountin" 
cc: Karl Pielorz , current@FreeBSD.ORG
Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) 
In-reply-to: Your message of "Wed, 14 Oct 1998 20:47:17 CDT."
             <3.0.3.32.19981014204717.0107000c@207.227.119.2> 
Date: Wed, 14 Oct 1998 19:13:39 -0700
Message-ID: <4460.908417619@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> One wonders if Jordan has been busy on working on the bootloader issue...
> Have yet to hear more than "we should" or "we shouldn't" and kernel ELF vs
> aout (ad naseum - which certainly isn't going to happen) are getting rather
> stale.

The kernel with 3.0 will be a.out with a full transition to ELF happening
almost immediately afterwards.

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 19:15:46 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA13056
          for freebsd-current-outgoing; Wed, 14 Oct 1998 19:15:46 -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 TAA13050
          for ; Wed, 14 Oct 1998 19:15:44 -0700 (PDT)
          (envelope-from info@highwind.com)
Received: (from info@localhost)
	by highwind.com (8.8.6/8.8.6) id WAA22134;
	Wed, 14 Oct 1998 22:15:13 -0400 (EDT)
Date: Wed, 14 Oct 1998 22:15:13 -0400 (EDT)
Message-Id: <199810150215.WAA22134@highwind.com>
From: HighWind Software Information 
To: taob@risc.org
CC: lists@tar.com, current@FreeBSD.ORG
In-reply-to: 
	(message from Brian Tao on Wed, 14 Oct 1998 21:33:15 -0400 (EDT))
Subject: Re: Recent 3.0's are Depressing
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Well... I think we have a test program that illustrates a (perhaps
"the") bug in the new libc_r.a's. It appears that
pthread_cond_timedwait() is now broken.

We updated our machine to the latest libc_r. Check out the following
program.

Haven't looked at the libc_r code yet.

-Rob

---

/*
   Illustration of FreeBSD pthread_cond_wait() bug
   
   This program sets up a timed conditional wait. It just calls
   pthread_cond_timedwait(). This should BLOCK for 15 seconds and the program
   should terminate normally.

   However, because of some bugs in FreeBSD, the pthread_cond_timedwait()
   returns with no error. It looks as if someone has signaled the
   condition. Clearly, that is impossible and there is some kind of bug!

   This early return is causing Typhoon to SPIN endlessly.

   g++ -o condBug -D_REENTRANT -D_THREAD_SAFE -g -Wall condBug.C -pthread 

*/

#include 
#include 
#include 

int main(int, char **)
{
    pthread_mutex_t lock;
    pthread_cond_t condition;

    // 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));

    // Grab current time
    time_t currentTime = ::time(0);

    // Lock the lock
    assert(!::pthread_mutex_lock(&lock));

    // Wait in the condition for 15 seconds
    timespec timeOut;
    timeOut.tv_sec = currentTime + 15;
    timeOut.tv_nsec = 0;
    
    int err = ::pthread_cond_timedwait(&condition, &lock, &timeOut);

    // We better get an error (we should have TIMED OUT!)
    assert(err);

    // 15 seconds SHOULD have passed, so 5 seconds DEFINATELY should have!!
    assert(::time(0) >= currentTime + 5);

    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  Wed Oct 14 19:19:04 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA13557
          for freebsd-current-outgoing; Wed, 14 Oct 1998 19:19:04 -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 TAA13546
          for ; Wed, 14 Oct 1998 19:19:00 -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 WAA21205;
	Wed, 14 Oct 1998 22:16:21 -0400 (EDT)
Date: Wed, 14 Oct 1998 22:16:21 -0400 (EDT)
From: Brian Feldman 
To: Greg Lehey 
cc: Julian Elischer , Mike Smith ,
        "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem
In-Reply-To: <19981015105245.H586@freebie.lemis.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

Well, according to Jordan's "non-verification" to my alluding that since
Dr. McKusick was committing NFS deltas, he was the mysterious contracted
NFS fixer-upper. Last time I checked, he didn't really do his entire job
if that was to totally fix NFS.... but hey, I don't use NFS much if ever,
so I won't Complain...

Brian Feldman

On Thu, 15 Oct 1998, Greg Lehey wrote:

> On Wednesday, 14 October 1998 at 10:28:14 -0700, Julian Elischer wrote:
> > On Wed, 14 Oct 1998, Mike Smith wrote:
> >>> Perhaps this could be the problem with NFS "hanging" certain people all
> >>> the time? (not the pine thing) The system spending way too much time
> >>> inside the kernel transmitting NFS packets....
> >>
> >> No.  Lack of ACCESS caching makes us slow and eats the network (because
> >> we are very good at generating/sending/receiving them).
> >>
> >> If there's someone out there that wants to work with the very best NFS
> >> people in the business to sort out our problems, please let me know.
> >> NetApp are keen to see our issues resolved (it will mean less angst
> >> for them in the long run, as they have many FreeBSD-using customers).
> >>
> >> Right now, we are accumulating a bad NFS reputation. 8(
> >
> > I thought kirk was doing that....
> 
> I hope not.
> 
> 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 14 19:23:04 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA14313
          for freebsd-current-outgoing; Wed, 14 Oct 1998 19:23:04 -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 TAA14286
          for ; Wed, 14 Oct 1998 19:23:00 -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 LAA03566;
	Thu, 15 Oct 1998 11:51:56 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.1/8.9.0) id LAA02229;
	Thu, 15 Oct 1998 11:51:55 +0930 (CST)
Message-ID: <19981015115155.O586@freebie.lemis.com>
Date: Thu, 15 Oct 1998 11:51:55 +0930
From: Greg Lehey 
To: Brian Feldman 
Cc: Julian Elischer , Mike Smith ,
        "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem
References: <19981015105245.H586@freebie.lemis.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: ; from Brian Feldman on Wed, Oct 14, 1998 at 10:16:21PM -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, 14 October 1998 at 22:16:21 -0400, Brian Feldman wrote:
> On Thu, 15 Oct 1998, Greg Lehey wrote:
>
>> On Wednesday, 14 October 1998 at 10:28:14 -0700, Julian Elischer wrote:
>>> On Wed, 14 Oct 1998, Mike Smith wrote:
>>>>> Perhaps this could be the problem with NFS "hanging" certain people all
>>>>> the time? (not the pine thing) The system spending way too much time
>>>>> inside the kernel transmitting NFS packets....
>>>>
>>>> No.  Lack of ACCESS caching makes us slow and eats the network (because
>>>> we are very good at generating/sending/receiving them).
>>>>
>>>> If there's someone out there that wants to work with the very best NFS
>>>> people in the business to sort out our problems, please let me know.
>>>> NetApp are keen to see our issues resolved (it will mean less angst
>>>> for them in the long run, as they have many FreeBSD-using customers).
>>>>
>>>> Right now, we are accumulating a bad NFS reputation. 8(
>>>
>>> I thought kirk was doing that....
>>
>> I hope not.
>
> Well, according to Jordan's "non-verification" to my alluding that since
> Dr. McKusick was committing NFS deltas, he was the mysterious contracted
> NFS fixer-upper.

Yes, I think you're probably right, though I don't know why nobody has
confirmed or denied it.  My comment related to Julian's undirected
comment, and wasn't intended seriously.

> Last time I checked, he didn't really do his entire job if that was
> to totally fix NFS.... but hey, I don't use NFS much if ever, so I
> won't Complain...

I use NFS.  I'd really like to see it fixed.

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 14 19:27:43 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA15226
          for freebsd-current-outgoing; Wed, 14 Oct 1998 19:27: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 TAA15217
          for ; Wed, 14 Oct 1998 19:27:41 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp02.primenet.com (8.8.8/8.8.8) id TAA25635;
	Wed, 14 Oct 1998 19:27:24 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp02.primenet.com, id smtpd025613; Wed Oct 14 19:27:19 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id TAA19874;
	Wed, 14 Oct 1998 19:27:16 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810150227.TAA19874@usr04.primenet.com>
Subject: Re: Novice question
To: green@zone.syracuse.NET (Brian Feldman)
Date: Thu, 15 Oct 1998 02:27:16 +0000 (GMT)
Cc: gseward@jps.net, current@FreeBSD.ORG
In-Reply-To:  from "Brian Feldman" at Oct 14, 98 10:05:26 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

> All I know is that sysinstall (hence the GENERIC kernel too) disk does NOT
> have PnP, and I don't see one goddamned reason it shouldn't have PnP in
> 3.0-RELEASE! Along with installing ELF bootability. HEAR ME JKH? 
> 
> > I am trying to install FreeBSD over a FTP connection, and I have 
> > been unable to get it to recognise my PnP modem.  I set it in the 
> > kernel configuration at the com port address and IRQ identified by 
> > BIOS and it is never found.  Any ideas?

Disable PnP in the BIOS.  For all PnP devices for which PnP is enabled
in the BIOS, if the device is not in the boot path, the BIOS disables
the device.

If this does not help, then your modem is probably a "softmodem",
which is a modem that relies on the host processor for some
aspects of signal processing, whether MNP only, or all the way
to actually signal processing the modem signal stream after merely
line converting, ADAC'ing the signal, and maybe buffering at a
given clock.

FreeBSD won't work with modems like this (nor will Linux, nor will
nearly any non-MS OS) because it requires drivers from the modem
vendor (and said drivers suck your CPU through a hole in the floor).


Anyway, if it works with PnP disabled in the BIOS, be sure to
add your voice to Brian's (personally, I think FreeBSD should
manage PnP hadrware by doing *all* the PnP work, even for PnP
cards plugged into machines without PnP BIOS; actually, Windows
95/98 recommends disabling the PnP BIOS on the theory that the
OS knows the hardware better than the hardware vendor does.
Many times, this is right, e.g., ALR's BIOS does not properly
reserve IRQ 12 for the built-in bus mouse).


					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 14 19:28:23 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA15415
          for freebsd-current-outgoing; Wed, 14 Oct 1998 19:28:23 -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 TAA15409
          for ; Wed, 14 Oct 1998 19:28:18 -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 WAA21319;
	Wed, 14 Oct 1998 22:27:35 -0400 (EDT)
Date: Wed, 14 Oct 1998 22:27:35 -0400 (EDT)
From: Brian Feldman 
To: Greg Lehey 
cc: Julian Elischer , Mike Smith ,
        "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem
In-Reply-To: <19981015115155.O586@freebie.lemis.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've done some NFS experimentation on my box, and basically, I try to test
a lot of the new technologies (and older) in FreeBSD. Some of the less
successful combos I've tried were:
	mount_union anything
	NFS mounting and beating on the FS
	floppies with softupdates
	2 vnode pan60's on 2 SoftUpdates partitions, CCD'd, and made ino a
new fs, beat on
	etc.
And beating on as defined something like:
#!/bin/sh
i=0
while [ $i -le 100 ]; do
        mkdir $i
        cd $i
        i=`expr $i + 1`
        p=0
        while [ $p -le 100 ]; do
                date > a$p
                p=`expr $p + 1`
        done
done
But I fear these are just the wild experiments of a 15-year-old :-)

Brian Feldman

On Thu, 15 Oct 1998, Greg Lehey wrote:

> On Wednesday, 14 October 1998 at 22:16:21 -0400, Brian Feldman wrote:
> > On Thu, 15 Oct 1998, Greg Lehey wrote:
> >
> >> On Wednesday, 14 October 1998 at 10:28:14 -0700, Julian Elischer wrote:
> >>> On Wed, 14 Oct 1998, Mike Smith wrote:
> >>>>> Perhaps this could be the problem with NFS "hanging" certain people all
> >>>>> the time? (not the pine thing) The system spending way too much time
> >>>>> inside the kernel transmitting NFS packets....
> >>>>
> >>>> No.  Lack of ACCESS caching makes us slow and eats the network (because
> >>>> we are very good at generating/sending/receiving them).
> >>>>
> >>>> If there's someone out there that wants to work with the very best NFS
> >>>> people in the business to sort out our problems, please let me know.
> >>>> NetApp are keen to see our issues resolved (it will mean less angst
> >>>> for them in the long run, as they have many FreeBSD-using customers).
> >>>>
> >>>> Right now, we are accumulating a bad NFS reputation. 8(
> >>>
> >>> I thought kirk was doing that....
> >>
> >> I hope not.
> >
> > Well, according to Jordan's "non-verification" to my alluding that since
> > Dr. McKusick was committing NFS deltas, he was the mysterious contracted
> > NFS fixer-upper.
> 
> Yes, I think you're probably right, though I don't know why nobody has
> confirmed or denied it.  My comment related to Julian's undirected
> comment, and wasn't intended seriously.
> 
> > Last time I checked, he didn't really do his entire job if that was
> > to totally fix NFS.... but hey, I don't use NFS much if ever, so I
> > won't Complain...
> 
> I use NFS.  I'd really like to see it fixed.
> 
> 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 14 20:03:00 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA20081
          for freebsd-current-outgoing; Wed, 14 Oct 1998 20:03:00 -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 UAA20044
          for ; Wed, 14 Oct 1998 20:02:50 -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 TAA07046;
	Wed, 14 Oct 1998 19:58:42 -0700 (PDT)
Message-Id: <199810150258.TAA07046@implode.root.com>
To: Brian Feldman 
cc: Greg Lehey , Julian Elischer ,
        Mike Smith ,
        "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem 
In-reply-to: Your message of "Wed, 14 Oct 1998 22:16:21 EDT."
              
From: David Greenman 
Reply-To: dg@root.com
Date: Wed, 14 Oct 1998 19:58:41 -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Well, according to Jordan's "non-verification" to my alluding that since
>Dr. McKusick was committing NFS deltas, he was the mysterious contracted
>NFS fixer-upper. Last time I checked, he didn't really do his entire job
>if that was to totally fix NFS.... but hey, I don't use NFS much if ever,
>so I won't Complain...

   Kirk was contracted to fix the problems that he could fix in a short amount
of time. He did that and confirmed my own analysis of the remaining problems,
which basically all stem from lack of FS node locking in the NFS code. Adding
such locking opens a very large can of worms and everyone who has tried to
do this has failed.

-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 14 20:58:11 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA26787
          for freebsd-current-outgoing; Wed, 14 Oct 1998 20:58:11 -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 UAA26772
          for ; Wed, 14 Oct 1998 20:58:07 -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 WAA00945
	for freebsd-current@FreeBSD.ORG; Wed, 14 Oct 1998 22:57:47 -0500 (CDT)
Received: (from bruce@localhost)
	by zuhause.mn.org (8.8.8/8.8.7) id WAA26157;
	Wed, 14 Oct 1998 22:56:28 -0500 (CDT)
From: Bruce Albrecht 
Date: Wed, 14 Oct 1998 22:56:28 -0500 (CDT)
To: freebsd-current@FreeBSD.ORG
Subject: Re: New build problem?
In-Reply-To: <13860.40343.489454.292871@zuhause.zuhause.mn.org>
References: <13860.40343.489454.292871@zuhause.zuhause.mn.org>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <13861.28800.895129.468668@zuhause.zuhause.mn.org>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bruce Albrecht writes:
 > I'm trying to do an upgrade from an ancient version of 3.0-current
 > (12/31/97), cvsupped src about 10 hours ago, and my build died when I did:
 > 
 > make -f Makefile.upgrade  aout-to-elf-build
 > (most lines deleted)
 > --------------------------------------------------------------
 > >>> Rebuilding bootstrap libraries
 > --------------------------------------------------------------
 > cd /usr/src; PATH=/usr/obj/aout/usr/src/tmp/sbin:/usr/obj/aout/usr/src/tmp/usr/sbin:/usr/obj/aout/usr/src/tmp/bin:/usr/obj/aout/usr/src/tmp/usr/bin:/usr/obj/aout/usr/src/tmp/usr/games:/bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/gnu/bin:/usr/local/bin:/usr/local/sbin:/usr/libexec/uucp:/home/bruce/bin:/home/bruce/tbd.new:.:/usr/games BISON_SIMPLE=/usr/obj/aout/usr/src/tmp/usr/share/misc/bison.simple  COMPILER_PATH=/usr/obj/aout/usr/src/tmp/usr/libexec:/usr/obj/aout/usr/src/tmp/usr/bin  GCC_EXEC_PREFIX=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib/  LD_LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout  LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib NOEXTRADEPEND=t  OBJFORMAT_PATH=/usr/obj/aout/usr/src/tmp/usr/libexec:/usr/libexec /usr/obj/aout/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/aout/usr/src/tmp -f Makefile.inc1 bootstrap-libraries
 > cd /usr/src/lib/csu/i386;  /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend;  /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all;  /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj
 > make: don't know how to make /usr/obj/usr/src/tmp/usr/include/sys/param.h. Stop
 > *** Error code 2
 > 
 > I had run another attempt a couple of days ago that had failed because 
 > I ran out of space in /usr/obj, and it had gone much further.

I was looking at this further, and it looks to me like the problem is
that the make depend for /usr/src/lib/csu/i386 is looking for
the includes in /usr/obj/usr/src/tmp/usr/include instead of
/usr/obj/aout/usr/src/tmp/usr/include.  The reason why it got further
in the previous build is because I hadn't started out with a totally
empty /usr/obj, and I think it was finding an old param.h.

Is this something that needs to be fixed before the release?  I
suspect that it may not be an issue for elf builds on an elf machine,
but I haven't gotten far enough to check.  I was hoping to upgrade my
system from source, but maybe I'll have to resort to installing the
3.0 release.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 21:09:06 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA27901
          for freebsd-current-outgoing; Wed, 14 Oct 1998 21:09:06 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27892
          for ; Wed, 14 Oct 1998 21:09:04 -0700 (PDT)
          (envelope-from ggm@dstc.edu.au)
Received: from dstc.edu.au (sleet.dstc.edu.au [130.102.176.45])
	by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id OAA09465;
	Thu, 15 Oct 1998 14:00:29 +1000 (EST)
X-Mailer: exmh version 2.0.2 2/24/98
To: Greg Lehey 
cc: Brian Feldman ,
        Julian Elischer , Mike Smith ,
        "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem 
In-reply-to: Your message of "Thu, 15 Oct 1998 11:51:55 +0930."
             <19981015115155.O586@freebie.lemis.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 14:00:28 +1000
Message-ID: <6710.908424028@dstc.edu.au>
From: George Michaelson 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


  
  I use NFS.  I'd really like to see it fixed.

Gee. I see history about to repeat itself. Exit stateless filesystems left
and enter 'the Newcastle connection' stage right. Then we can argue about
who invented the acronym DFS and why RFS failed.

Greg: we'd *all* like to see NFS 'fixed' but thats like asking for a cure
      for cancer.

How about scoping which problems in NFS you can agree are sufficiently
intractable to limit scope to less unfixable ones?

I'd like a working rpc.lockd ... on every machine I use at work, vendor and
freeware included. I dream on. 

Sheesh. Its only been 20 years of research so far :-)

Roll on CODA.

-George
--
George Michaelson         |  DSTC Pty Ltd
Email: ggm@dstc.edu.au    |  University of Qld 4072
Phone: +61 7 3365 4310    |  Australia
  Fax: +61 7 3365 4311    |  http://www.dstc.edu.au



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 21:11:04 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA28195
          for freebsd-current-outgoing; Wed, 14 Oct 1998 21:11:04 -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 VAA28190
          for ; Wed, 14 Oct 1998 21:11:02 -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 VAA04827;
	Wed, 14 Oct 1998 21:11:02 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Brian Feldman 
cc: Gil , current@FreeBSD.ORG
Subject: Re: Novice question 
In-reply-to: Your message of "Wed, 14 Oct 1998 22:05:26 EDT."
              
Date: Wed, 14 Oct 1998 21:11:01 -0700
Message-ID: <4824.908424661@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> All I know is that sysinstall (hence the GENERIC kernel too) disk does NOT
> have PnP, and I don't see one goddamned reason it shouldn't have PnP in
> 3.0-RELEASE! Along with installing ELF bootability. HEAR ME JKH? 

Yes Brian, I hear you.  Yeesh, it's no wonder you keep getting
yourself banned from #freebsd with an attitude like that! :-)

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 21:15:14 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA28681
          for freebsd-current-outgoing; Wed, 14 Oct 1998 21:15:14 -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 VAA28676
          for ; Wed, 14 Oct 1998 21:15:13 -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 VAA04850;
	Wed, 14 Oct 1998 21:14:08 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Brian Feldman 
cc: Greg Lehey , Julian Elischer ,
        Mike Smith ,
        "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem 
In-reply-to: Your message of "Wed, 14 Oct 1998 22:16:21 EDT."
              
Date: Wed, 14 Oct 1998 21:14:08 -0700
Message-ID: <4845.908424848@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Well, according to Jordan's "non-verification" to my alluding that since
> Dr. McKusick was committing NFS deltas, he was the mysterious contracted
> NFS fixer-upper. Last time I checked, he didn't really do his entire job
> if that was to totally fix NFS.... but hey, I don't use NFS much if ever,
> so I won't Complain...

Kirk did some of the tasks but wasn't keen to jump in and become our
NFS guru for everything.  I can't say I blame him.  In any case, he's
finished the work he was willing to do and blaming him for NFS's
problems or saying he "didn't do his entire job" is simply lameness
incarnate (not that Brian surprises me here since he's already widely
known in the FreeBSD community for the concentrated doses of lameness
he emits from time to time :).

In any case, 24 hours before the release is NOT the time to be
bringing this kind of thing up and I'll thank Mr. Feldman for crawling
back under the slimey rock from which he's most recently emerged.
Knock it off, green!

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 21:38:14 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA00973
          for freebsd-current-outgoing; Wed, 14 Oct 1998 21:38:14 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from m4.stox.sa.enteract.com (stox.sa.enteract.com [207.229.132.161])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00965
          for ; Wed, 14 Oct 1998 21:38:09 -0700 (PDT)
          (envelope-from ken@stox.sa.enteract.com)
Received: from localhost (ken@localhost.stox.sa.enteract.com [127.0.0.1]) by m4.stox.sa.enteract.com (8.9.1/8.6.12) with ESMTP id XAA00797; Wed, 14 Oct 1998 23:37:38 -0500 (CDT)
Date: Wed, 14 Oct 1998 23:37:37 -0500 (CDT)
From: "Kenneth P. Stox" 
Reply-To: stox@enteract.com
To: Karl Denninger 
cc: current@FreeBSD.ORG
Subject: Re: Uh, guys, BETA 3.0 right now panics on boot
In-Reply-To: <19981014202222.A208@Denninger.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


Karl:
	You have been active here for how many years ? This is the type of
bug report one would expect from needinfo@juno.com. How about reporting
something useful ? Examples would include: machine configuration, dmesg
output, kernel configuration, what time you cvsup'ed, etc.

	BTW, I have 4 machines here, from a 486 laptop to a dual PII SMP
that I cvsup'ed early this morning and at 10PM CDT this evening, and none
exhibit the panic you describe. I am also running aout and ELF
configurations. 

	I am not, as of yet, running the new boot loader, however. As we
run down to the deadline, if you have a problem, detailed bug reports are
crucial. I am sure that nobody wants to see 3.0 be released in anything
less than workable form. ( Well except the boys in Redmond, that is )

	I am very tempted to say that if 3.0 only panics for Karl, this
might be considered a feature. ;->


-Ken Stox
 stox@imagescape.com
 stox@fnal.gov

On Wed, 14 Oct 1998, Karl Denninger wrote:

> Immediate panic, no dump, "supervisor page not present".  Never even starts
> probing devices.
> 
> Bad, bad stuff!
> 
> --
> -- 
> Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 21:48:46 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA01741
          for freebsd-current-outgoing; Wed, 14 Oct 1998 21:48: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 VAA01736
          for ; Wed, 14 Oct 1998 21:48:45 -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 AAA22695;
	Thu, 15 Oct 1998 00:45:40 -0400 (EDT)
Date: Thu, 15 Oct 1998 00:45:40 -0400 (EDT)
From: Brian Feldman 
To: "Jordan K. Hubbard" 
cc: Greg Lehey , Julian Elischer ,
        Mike Smith ,
        "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem 
In-Reply-To: <4845.908424848@time.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

Hey hey, now now, no need to get hostile ;) It seems, Mr. Hubbard, that
noone actually clued anyone but the core team in on the contract (correct
me if I am wrong, please). I was thinking more along the lines of "is Kirk
still working on NFS?" than "Why won't Kirk fix NFS, NOW!?", and do not
mean to be rude about it; it seems those of us who aren't actually a core
member don't get clued in on these things, but maybe I should read
-hackers, if that'd be the correct place to find those discussions etc.
Don't take a bit of sardonicism so harshly, I was by no means blaming any
of the FreeBSD team or Kirk himself for anything.

Brian Feldman

On Wed, 14 Oct 1998, Jordan K. Hubbard wrote:

> > Well, according to Jordan's "non-verification" to my alluding that since
> > Dr. McKusick was committing NFS deltas, he was the mysterious contracted
> > NFS fixer-upper. Last time I checked, he didn't really do his entire job
> > if that was to totally fix NFS.... but hey, I don't use NFS much if ever,
> > so I won't Complain...
> 
> Kirk did some of the tasks but wasn't keen to jump in and become our
> NFS guru for everything.  I can't say I blame him.  In any case, he's
> finished the work he was willing to do and blaming him for NFS's
> problems or saying he "didn't do his entire job" is simply lameness
> incarnate (not that Brian surprises me here since he's already widely
> known in the FreeBSD community for the concentrated doses of lameness
> he emits from time to time :).
> 
> In any case, 24 hours before the release is NOT the time to be
> bringing this kind of thing up and I'll thank Mr. Feldman for crawling
> back under the slimey rock from which he's most recently emerged.
> Knock it off, green!
> 
> - Jordan
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 21:51:47 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA02081
          for freebsd-current-outgoing; Wed, 14 Oct 1998 21:51:47 -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 VAA02073
          for ; Wed, 14 Oct 1998 21:51:45 -0700 (PDT)
          (envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id XAA11257;
	Wed, 14 Oct 1998 23:51:16 -0500 (CDT)
Received: from harkol-12.isdn.mke.execpc.com(169.207.64.140) by peak.mountin.net via smap (V1.3)
	id sma011253; Wed Oct 14 23:50:52 1998
Message-Id: <3.0.3.32.19981014233959.010725dc@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, 14 Oct 1998 23:39:59 -0500
To: Mike Smith 
From: "Jeffrey J. Mountin" 
Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) 
Cc: "Jordan K. Hubbard" ,
        Karl Pielorz , current@FreeBSD.ORG
In-Reply-To: <199810150208.TAA00947@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 07:08 PM 10/14/98 -0700, Mike Smith wrote:
>Actually, Jordan's load is currently split between testing (where most 
>of my effort right now is) and trying to have something ready for the 
>Alpha at about the same time.

Alpha?

>> Was anything definitive decided?  Or is it going to wait for the next
release?
>
>To the very best of my knowledge, it will not be sprung on the
>unsuspecting 3.0 release.  Instead, it will probably be turned on as the
>default a couple of weeks after the release, so that people tracking 3.0
>will transition, but those using 3.0 flat will not. 

OK, I'm still a bit unclear.  There have been dozens of messages concerning
the loader et all w/wo an ELF kernel.

So, for 3.0 will sysinstall install the new loader and boot blocks _or_
will this have to be done manually.

This only matters _if_ someone wants to build an ELF kernel.  If the new
loader is installed with 3.0, then there is no need to manually install the
new loader, which already can handle an aout or ELF kernel.

Thus making the transition smoother to full ELF (ie kernel) for the next
release.

Or did I a) miss the point of all the loader related threads, b) become so
confused with all the opinions on what *should* be done, and hence c)
re-reading the threads did not help one iota.

The CVS list isn't clearer, but seems just as chaotic.

Aw hell....

Further will 'make world'/'make buildworld' automagically install the new
load on 3.0 if the sysinstall does not?

Finally, if the new loader is not installed and/or building world does not,
will this be documented for those that want to build an ELF kernel with 3.0
(certainly they should track -current)?


>From what I read it seemed less painful to install the new loader, even if
it's setup as a transitionary measure to avoid the above confusion.  And
when the next release comes out it can install an ELF kernel from the start.

Whew!  Think I got that right.

And then all hell breaks loose after the freeze. 8-O


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 14 22:03:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA03281
          for freebsd-current-outgoing; Wed, 14 Oct 1998 22:03:59 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03276
          for ; Wed, 14 Oct 1998 22:03:58 -0700 (PDT)
          (envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.8.8/8.8.7) with SMTP id BAA09739
	for ; Thu, 15 Oct 1998 01:03:28 -0400 (EDT)
Date: Thu, 15 Oct 1998 01:03:27 -0400 (EDT)
From: "Matthew N. Dodd" 
To: current@FreeBSD.ORG
Subject: kernel dependancies broken?
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


Anyone seen this?

1. edit src/sys/cam/cam_xpt.c
2. add a quirk entry
3. cd src/sys/compile/KERNEL/
4. 'make'
5. wait while most of the kernel source is rebuilt.

Note that I'm typing 'make' in a kernel compile directory that had just
finished building a kernel.  No other files where changed.

This is really annoying as it takes 30+ minutes for a 486 to chug through
a kernel compile that should only take about a minute for a simple 1 file
change.

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 22:12:26 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA04126
          for freebsd-current-outgoing; Wed, 14 Oct 1998 22:12:26 -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 WAA04120
          for ; Wed, 14 Oct 1998 22:12:24 -0700 (PDT)
          (envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA06685; Wed, 14 Oct 1998 22:12:07 -0700 (PDT)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
	id sma006683; Wed Oct 14 22:11:52 1998
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA11878; Wed, 14 Oct 1998 22:11:52 -0700 (PDT)
From: Archie Cobbs 
Message-Id: <199810150511.WAA11878@bubba.whistle.com>
Subject: Re: syslog.conf comment about tabs
In-Reply-To: <199810142147.PAA07468@mt.sri.com> from Nate Williams at "Oct 14, 98 03:47:21 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Wed, 14 Oct 1998 22:11:52 -0700 (PDT)
Cc: axl@iafrica.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

Nate Williams writes:
> > It's a pity that, after all the discussion about syslog's
> > differentiation between tabs and spaces, nothing was actually done about
> > it. This is especially sad given that 3.0-RELEASE is about to be
>                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^ 
> > snapped.
>   ^^^^^^^^
> > 
> > When someone with commit privs has some time (does this sound like
> > millenium hype? ;) it'd be great to see PR8162 making it into the
> > repository.
> 
> Given that we're about to 'release' FreeBSD, a change that affects a
> critical part of the system that is not a bugfix should never be
> committed since it might break something.
> 
> It is being ignored *because* it's too late to commit a fix that isn't
> necessary and has potentially 'huge' destablizing possibilities.

PR8162 (which is just a two line patch to add a comment to the default
/etc/syslog.conf) has already been committed, according to the
audit trail.

-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 14 22:13:30 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA04219
          for freebsd-current-outgoing; Wed, 14 Oct 1998 22:13:30 -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 WAA04214
          for ; Wed, 14 Oct 1998 22:13:29 -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 BAA23013;
	Thu, 15 Oct 1998 01:13:14 -0400 (EDT)
Date: Thu, 15 Oct 1998 01:13:13 -0400 (EDT)
From: Brian Feldman 
To: "Matthew N. Dodd" 
cc: current@FreeBSD.ORG
Subject: Re: kernel dependancies broken?
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

As a curiosity, what happens if you try 'make cam_xpt.o kernel'?

Brian Feldman

On Thu, 15 Oct 1998, Matthew N. Dodd wrote:

> 
> Anyone seen this?
> 
> 1. edit src/sys/cam/cam_xpt.c
> 2. add a quirk entry
> 3. cd src/sys/compile/KERNEL/
> 4. 'make'
> 5. wait while most of the kernel source is rebuilt.
> 
> Note that I'm typing 'make' in a kernel compile directory that had just
> finished building a kernel.  No other files where changed.
> 
> This is really annoying as it takes 30+ minutes for a 486 to chug through
> a kernel compile that should only take about a minute for a simple 1 file
> change.
> 
> -- 
> | Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
> | winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
> | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |
> 
> 
> 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 14 22:16:37 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA04396
          for freebsd-current-outgoing; Wed, 14 Oct 1998 22:16:37 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04390
          for ; Wed, 14 Oct 1998 22:16:34 -0700 (PDT)
          (envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.8.8/8.8.7) with SMTP id BAA09848;
	Thu, 15 Oct 1998 01:16:11 -0400 (EDT)
Date: Thu, 15 Oct 1998 01:16:11 -0400 (EDT)
From: "Matthew N. Dodd" 
To: Brian Feldman 
cc: current@FreeBSD.ORG
Subject: Re: kernel dependancies broken?
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, 15 Oct 1998, Brian Feldman wrote:
> As a curiosity, what happens if you try 'make cam_xpt.o kernel'?

It compiles cam_xpt.o before embarking on its systamatic recimpile of most
of the rest of the kernel.

Don't tell me you can't reproduce this.

> On Thu, 15 Oct 1998, Matthew N. Dodd wrote:
> 
> > 
> > Anyone seen this?
> > 
> > 1. edit src/sys/cam/cam_xpt.c
> > 2. add a quirk entry
> > 3. cd src/sys/compile/KERNEL/
> > 4. 'make'
> > 5. wait while most of the kernel source is rebuilt.
> > 
> > Note that I'm typing 'make' in a kernel compile directory that had just
> > finished building a kernel.  No other files where changed.
> > 
> > This is really annoying as it takes 30+ minutes for a 486 to chug through
> > a kernel compile that should only take about a minute for a simple 1 file
> > change.
> > 
> > -- 
> > | Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
> > | winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
> > | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> > 
> 

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 22:20:30 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA04939
          for freebsd-current-outgoing; Wed, 14 Oct 1998 22:20:30 -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 WAA04926
          for ; Wed, 14 Oct 1998 22:20:29 -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 BAA23091;
	Thu, 15 Oct 1998 01:20:13 -0400 (EDT)
Date: Thu, 15 Oct 1998 01:20:13 -0400 (EDT)
From: Brian Feldman 
To: "Matthew N. Dodd" 
cc: current@FreeBSD.ORG
Subject: Re: kernel dependancies broken?
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

Okay, I won't yell you I can't reproduce this. But seriously, I wanted to
see if that would work. It seems cam_xpt.c may be more important than
other files to you, does it not? Why don't you look at Makefile,
bsd.kern.mk, and friends and check out the dependencies, looking closely
at cam_xpt.[co]? If changing _any_ random single source file (not header)
causes a complete rebuild (try it!) then this is cause for a bit more
concern.

Brian Feldman

On Thu, 15 Oct 1998, Matthew N. Dodd wrote:

> On Thu, 15 Oct 1998, Brian Feldman wrote:
> > As a curiosity, what happens if you try 'make cam_xpt.o kernel'?
> 
> It compiles cam_xpt.o before embarking on its systamatic recimpile of most
> of the rest of the kernel.
> 
> Don't tell me you can't reproduce this.
> 
> > On Thu, 15 Oct 1998, Matthew N. Dodd wrote:
> > 
> > > 
> > > Anyone seen this?
> > > 
> > > 1. edit src/sys/cam/cam_xpt.c
> > > 2. add a quirk entry
> > > 3. cd src/sys/compile/KERNEL/
> > > 4. 'make'
> > > 5. wait while most of the kernel source is rebuilt.
> > > 
> > > Note that I'm typing 'make' in a kernel compile directory that had just
> > > finished building a kernel.  No other files where changed.
> > > 
> > > This is really annoying as it takes 30+ minutes for a 486 to chug through
> > > a kernel compile that should only take about a minute for a simple 1 file
> > > change.
> > > 
> > > -- 
> > > | Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
> > > | winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
> > > | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |
> > > 
> > > 
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-current" in the body of the message
> > > 
> > 
> 
> -- 
> | Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
> | winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
> | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |
> 
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 22:22:01 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA05057
          for freebsd-current-outgoing; Wed, 14 Oct 1998 22:22:01 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05049
          for ; Wed, 14 Oct 1998 22:21:57 -0700 (PDT)
          (envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.8.8/8.8.7) with SMTP id BAA09886;
	Thu, 15 Oct 1998 01:21:25 -0400 (EDT)
Date: Thu, 15 Oct 1998 01:21:25 -0400 (EDT)
From: "Matthew N. Dodd" 
To: Tony Maher 
cc: current@FreeBSD.ORG
Subject: Re: kernel dependancies broken?
In-Reply-To: <199810150515.PAA03479@morgan.angis.su.OZ.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, 15 Oct 1998, Tony Maher wrote:
> > 3. cd src/sys/compile/KERNEL/
> > 4. 'make'
> > 5. wait while most of the kernel source is rebuilt.
> > 
> > Note that I'm typing 'make' in a kernel compile directory that had just
> > finished building a kernel.  No other files where changed.
> 
> and "make depend" doesn't help?

But the dependancies haven't changed! (make depend && make don't alter
this behavior any though.)

This reeks of makefile breakage.  'touch *.o ; make' should relink the
kernel from existing .o files even if the .c file has been changed.

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 22:34:42 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA06152
          for freebsd-current-outgoing; Wed, 14 Oct 1998 22:34:42 -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 WAA06145
          for ; Wed, 14 Oct 1998 22:34:34 -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 PAA05419;
	Thu, 15 Oct 1998 15:34:03 +1000
Date: Thu, 15 Oct 1998 15:34:03 +1000
From: Bruce Evans 
Message-Id: <199810150534.PAA05419@godzilla.zeta.org.au>
To: bruce@zuhause.mn.org, freebsd-current@FreeBSD.ORG
Subject: Re: New build problem?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>I was looking at this further, and it looks to me like the problem is
>that the make depend for /usr/src/lib/csu/i386 is looking for
>the includes in /usr/obj/usr/src/tmp/usr/include instead of
>/usr/obj/aout/usr/src/tmp/usr/include.  The reason why it got further
>in the previous build is because I hadn't started out with a totally
>empty /usr/obj, and I think it was finding an old param.h.
>
>Is this something that needs to be fixed before the release?  I
>suspect that it may not be an issue for elf builds on an elf machine,
>but I haven't gotten far enough to check.  I was hoping to upgrade my
>system from source, but maybe I'll have to resort to installing the
>3.0 release.

You apparently have a stale .depend file in the source directory.
The `make clean' step won't remove this if an obj directory exists.
`make clean' can be run twice to first rm -rf any obj directories
and then to clean the source tree, but `make world' only runs it
once since this is sufficient for files created by `make world',
modulo bugs in (possibly previous versions of) `make world'.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Wed Oct 14 22:38:00 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA06577
          for freebsd-current-outgoing; Wed, 14 Oct 1998 22:38:00 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06572
          for ; Wed, 14 Oct 1998 22:37:58 -0700 (PDT)
          (envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.8.8/8.8.7) with SMTP id BAA12396;
	Thu, 15 Oct 1998 01:37:38 -0400 (EDT)
Date: Thu, 15 Oct 1998 01:37:38 -0400 (EDT)
From: "Matthew N. Dodd" 
To: Brian Feldman 
cc: current@FreeBSD.ORG
Subject: Re: kernel dependancies broken?
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, 15 Oct 1998, Brian Feldman wrote:
> Okay, I won't yell you I can't reproduce this. But seriously, I wanted
> to see if that would work. It seems cam_xpt.c may be more important
> than other files to you, does it not? Why don't you look at Makefile,
> bsd.kern.mk, and friends and check out the dependencies, looking
> closely at cam_xpt.[co]? If changing _any_ random single source file
> (not header) causes a complete rebuild (try it!) then this is cause
> for a bit more concern.

It isn't just cam_xpt.[co].  This isn't something that just cropped up
either.  I finally managed to do an aout-to-elf and am running on a system
that is maybe a day old but am still having this problem.  I attributed my
earlier experiences to a somewhat munged aout env trying to compile a
newish SUP of current.

'touch *.o' in the kernel build directory and 'make' should relink the
kernel without recompiling any .o files.  (And does, under stable)

> On Thu, 15 Oct 1998, Matthew N. Dodd wrote:
> 
> > On Thu, 15 Oct 1998, Brian Feldman wrote:
> > > As a curiosity, what happens if you try 'make cam_xpt.o kernel'?
> > 
> > It compiles cam_xpt.o before embarking on its systamatic recimpile of most
> > of the rest of the kernel.
> > 
> > Don't tell me you can't reproduce this.
> > 
> > > On Thu, 15 Oct 1998, Matthew N. Dodd wrote:
> > > 
> > > > 
> > > > Anyone seen this?
> > > > 
> > > > 1. edit src/sys/cam/cam_xpt.c
> > > > 2. add a quirk entry
> > > > 3. cd src/sys/compile/KERNEL/
> > > > 4. 'make'
> > > > 5. wait while most of the kernel source is rebuilt.
> > > > 
> > > > Note that I'm typing 'make' in a kernel compile directory that had just
> > > > finished building a kernel.  No other files where changed.
> > > > 
> > > > This is really annoying as it takes 30+ minutes for a 486 to chug through
> > > > a kernel compile that should only take about a minute for a simple 1 file
> > > > change.
> > > > 
> > > > -- 
> > > > | Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
> > > > | winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
> > > > | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |
> > > > 
> > > > 
> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > > with "unsubscribe freebsd-current" in the body of the message
> > > > 
> > > 
> > 
> > -- 
> > | Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
> > | winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
> > | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |
> > 
> > 
> 

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 00:16:05 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA15643
          for freebsd-current-outgoing; Thu, 15 Oct 1998 00:16:05 -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 AAA15636
          for ; Thu, 15 Oct 1998 00:16:03 -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 JAA15832
	for ; Thu, 15 Oct 1998 09:21:15 +0200 (CEST)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Thu, 15 Oct 1998 09:21:15 +0200 (CEST)
From: Andrzej Bialecki 
X-Sender: abial@korin.warman.org.pl
To: freebsd-current@FreeBSD.ORG
Subject: Minor glitch in /boot/loader
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,

Using sources two days old, together with new boot1/boot2.

If I don't type anything at the boot: prompt, later when /boot/loader
starts I can start loading immediately by pressing Enter, or abort loading
to get to its prompt (as the message advertises). However, if I type
anything at the boot: prompt (even if I type it and the delete), then
/boot/loader ignores all key presses.

My system is a Shuttle HOT-553 motherboard with K5 PR 133 CPU.

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 15 00:32:44 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA17444
          for freebsd-current-outgoing; Thu, 15 Oct 1998 00:32:44 -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 AAA17436
          for ; Thu, 15 Oct 1998 00:32:36 -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 JAA25142;
	Thu, 15 Oct 1998 09:37:34 +0200 (CEST)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Thu, 15 Oct 1998 09:37:33 +0200 (CEST)
From: Andrzej Bialecki 
X-Sender: abial@korin.warman.org.pl
To: bryan collins 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: /usr/sbin/arp: actual retrieval of routing table
In-Reply-To: <199810150116.SAA03564@hub.freebsd.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 Thu, 15 Oct 1998, bryan collins wrote:

> occasionaly I get the error message in the subject
> 
> /usr/sbin/arp: actual retrieval of routing table
>  
> and doesnt print the arp table.
> 
> the command is '/usr/sbin/arp -an' which runs every 60 seconds.
> the arp table has around 300-400 entries all the time.
> 
> have i come across some limitation for the table?

If your machine is quite busy adding/deleteing routes, I can understand
this. When you retrieve a bigger chunk of data from the kernel, you first
do the "sizing" of the memory needed, then you actually retrieve the data
- 'arp' does exactly this. If the actual routing table grows between these
two sysctl(3) calls, the data wouldn't fit and sysctl(3) refuses to
transfer them to your buffer.

Perhaps the programs which use this double sysctl(3) calls should allocate
somewhat bigger buffer than that calculated on basis of previous call,
anticipating for unexpected change in data size...

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 15 00:37:47 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA17905
          for freebsd-current-outgoing; Thu, 15 Oct 1998 00:37:47 -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 AAA17896
          for ; Thu, 15 Oct 1998 00:37:41 -0700 (PDT)
          (envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.awfulhak.org [172.16.0.7])
	by awfulhak.org (8.8.8/8.8.8) with ESMTP id IAA14099;
	Thu, 15 Oct 1998 08:13:44 +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 IAA00515;
	Thu, 15 Oct 1998 08:12:19 +0100 (BST)
	(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199810150712.IAA00515@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bruce Evans 
cc: brian@Awfulhak.org, current@FreeBSD.ORG, kjc@csl.sony.co.jp
Subject: Re: Improper sharing of modem bandwidth 
In-reply-to: Your message of "Wed, 14 Oct 1998 18:49:24 +1000."
             <199810140849.SAA12884@godzilla.zeta.org.au> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 08:12:18 +0100
From: Brian Somers 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >If there was an ioctl to change the usable tty buffer size to less than 
> >4k, ppp could set it to ``whatever the MTU is'' and get quite a 
> >reasonable interactive performance gain.
> 
> Maybe not.  Kernel ppp doesn't have the 4KB buffer between it and the
> driver, but its interactive performance is not reasonable when just
> one scp is using the link.

But kernel ppp doesn't do any interactive queue jumping does it ?

> Bruce

-- 
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  Thu Oct 15 00:55:47 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA19749
          for freebsd-current-outgoing; Thu, 15 Oct 1998 00:55:47 -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 AAA19740
          for ; Thu, 15 Oct 1998 00:55:45 -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 AAA05697
	for ; Thu, 15 Oct 1998 00:55:48 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: current@FreeBSD.ORG
Subject: Last call for release notes and related 3.0 docs!
Date: Thu, 15 Oct 1998 00:55:48 -0700
Message-ID: <5693.908438148@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The release notes, as well as all the other relevant docs for 3.0, are
nearing the point of completion and, if you have any feedback on this,
now is the time to give it (preferably as context diffs relative to
-current :-).

The files of primary interest are:

/usr/src/release/sysinstall/help/XF86.hlp
/usr/src/release/sysinstall/help/hardware.hlp
/usr/src/release/sysinstall/help/install.hlp
/usr/src/release/sysinstall/help/readme.hlp
/usr/src/release/sysinstall/help/relnotes.hlp
/usr/src/release/sysinstall/help/trouble.hlp
/usr/src/release/sysinstall/help/upgrade.hlp
/usr/src/release/*.TXT

Thanks!

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 01:23:04 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA22444
          for freebsd-current-outgoing; Thu, 15 Oct 1998 01:23:04 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from www.scancall.no (www.scancall.no [195.139.183.5])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA22438
          for ; Thu, 15 Oct 1998 01:23:00 -0700 (PDT)
          (envelope-from Marius.Bendiksen@scancall.no)
Received: from super2.langesund.scancall.no [195.139.183.29]
	by www with smtp
	id JCTLZQTJ; Thu, 15 Oct 98 08:22:42 GMT
	(PowerWeb version 4.04r6)
Message-Id: <3.0.5.32.19981015101745.00941bf0@mail.scancall.no>
X-Sender: Marius@mail.scancall.no
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Thu, 15 Oct 1998 10:17:45 +0200
To: freebsd-current@FreeBSD.ORG
From: Marius Bendiksen 
Subject: Re: bitten 3 times already.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Great! anything we could use perhaps ??

I don't think that's very likely. It was just necessary to get my pet OS
project to work some years back :)

>There is no difference in formatting, its only a question on what
>you call the track/head/sector registers, which you should know if
>you have written an IDE driver ;)

As I said, some years back, at which point I (as I recall) only used LBA,
so the issue is not something I've considered.

>The only thing thats important is to know the geometry used when the
>data was written onto disk, then use that to calculate a sequential
>sector number, then recalc that back to the current geometry.

Okay. Let's mv LBA /dev/null then.
---
Marius Bendiksen, IT-Trainee, ScanCall AS

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 01:25:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA22677
          for freebsd-current-outgoing; Thu, 15 Oct 1998 01:25:35 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from www.scancall.no (www.scancall.no [195.139.183.5])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA22670
          for ; Thu, 15 Oct 1998 01:25:31 -0700 (PDT)
          (envelope-from Marius.Bendiksen@scancall.no)
Received: from super2.langesund.scancall.no [195.139.183.29]
	by www with smtp
	id JCTMPBEJ; Thu, 15 Oct 98 08:25:13 GMT
	(PowerWeb version 4.04r6)
Message-Id: <3.0.5.32.19981015102016.0093aa20@mail.scancall.no>
X-Sender: Marius@mail.scancall.no
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Thu, 15 Oct 1998 10:20:16 +0200
To: Mike Smith 
From: Marius Bendiksen 
Subject: Re: bitten 3 times already. 
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <199810141521.IAA00738@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

>Your second paragraph contradicts the first, as if you had "written an 
>IDE driver before", you would know that "LBA formatted" doesn't mean 
>anything, and that LBA and CHS are just two ways of feeding the same 
>numbers to the disk.

Actually, working from disassembled bios code and some crappy command
tables doesn't give you much of an idea as to how things work. I knew I ran
LBA on all my drives, and thus assumed that accessing them as such would be
a good idea.

>You'd also know that reading a disk won't cause it to "lose" its data.

I was more concerned about -writing- to the disk. :)
---
Marius Bendiksen, IT-Trainee, ScanCall AS

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 02:12:28 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA26394
          for freebsd-current-outgoing; Thu, 15 Oct 1998 02:12:28 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bsd.mbp.ee (bsd.mbp.ee [194.204.12.74])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26386
          for ; Thu, 15 Oct 1998 02:12:22 -0700 (PDT)
          (envelope-from mauri@mbp.ee)
Received: from nw1.mbp.ee (nw1.mbp.ee [194.204.12.68])
	by bsd.mbp.ee (8.9.1/8.9.1) with ESMTP id MAA25239
	for ; Thu, 15 Oct 1998 12:11:56 +0300 (EEST)
	(envelope-from mauri@mbp.ee)
Message-Id: <199810150911.MAA25239@bsd.mbp.ee>
Received: from SERVER/SpoolDir by nw1.mbp.ee (Mercury 1.43);
    15 Oct 98 12:11:56 +0300
Received: from SpoolDir by SERVER (Mercury 1.43); 15 Oct 98 12:11:47 +0300
From: "Lauri Laupmaa" 
Organization: =?ISO-8859-1?Q?ripeva_Kirjastuse_AS?=
To: current@FreeBSD.ORG
Date: Thu, 15 Oct 1998 12:11:41 +0300
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Subject: sysinstall build error
X-mailer: Pegasus Mail for Win32 (v3.01b)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from Quoted-printable to 8bit by hub.freebsd.org id CAA26390
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

hi

it dies with:

file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp
cannot open /boot/boot0: no such file
*** Error code 2

where does one get this boot0 ?

______________
Lauri Laupmaa
дripДev
mauri@mbp.ee
Ph. +372 66 70 369
    +372 50 13 369
Fx. +372 66 70 165

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 04:59:55 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA12011
          for freebsd-current-outgoing; Thu, 15 Oct 1998 04:59:55 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12006
          for ; Thu, 15 Oct 1998 04:59:53 -0700 (PDT)
          (envelope-from karl@Genesis.Denninger.Net)
Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id GAA15243; Thu, 15 Oct 1998 06:59:35 -0500 (CDT)
Message-ID: <19981015065935.A15239@Denninger.Net>
Date: Thu, 15 Oct 1998 06:59:35 -0500
From: Karl Denninger 
To: stox@enteract.com
Cc: current@FreeBSD.ORG
Subject: Re: Uh, guys, BETA 3.0 right now panics on boot
References: <19981014202222.A208@Denninger.Net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: ; from Kenneth P. Stox on Wed, Oct 14, 1998 at 11:37:37PM -0500
Organization: Karl's Sushi and Packet Smashers
X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Well, if I could get a dump, or something other than "current as of last
night", I would!

Machine is irrelavent (it happens on both Ppro 200s and P166s).  There is no
dmesg; the machine panics INSTANTLY on start; as I said, you don't even get
into the device probes!

It sounds like the bootloader might be responsible for this - I'm going to
shut off the new boot loader and see if that makes it go away.

--
-- 
Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl
I ain't even *authorized* to speak for anyone other than myself, so give
up now on trying to associate my words with any particular organization.


On Wed, Oct 14, 1998 at 11:37:37PM -0500, Kenneth P. Stox wrote:
> 
> Karl:
> 	You have been active here for how many years ? This is the type of
> bug report one would expect from needinfo@juno.com. How about reporting
> something useful ? Examples would include: machine configuration, dmesg
> output, kernel configuration, what time you cvsup'ed, etc.
> 
> 	BTW, I have 4 machines here, from a 486 laptop to a dual PII SMP
> that I cvsup'ed early this morning and at 10PM CDT this evening, and none
> exhibit the panic you describe. I am also running aout and ELF
> configurations. 
> 
> 	I am not, as of yet, running the new boot loader, however. As we
> run down to the deadline, if you have a problem, detailed bug reports are
> crucial. I am sure that nobody wants to see 3.0 be released in anything
> less than workable form. ( Well except the boys in Redmond, that is )
> 
> 	I am very tempted to say that if 3.0 only panics for Karl, this
> might be considered a feature. ;->
> 
> 
> -Ken Stox
>  stox@imagescape.com
>  stox@fnal.gov
> 
> On Wed, 14 Oct 1998, Karl Denninger wrote:
> 
> > Immediate panic, no dump, "supervisor page not present".  Never even starts
> > probing devices.
> > 
> > Bad, bad stuff!
> > 
> > --
> > -- 
> > Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl
> 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 05:59:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA17091
          for freebsd-current-outgoing; Thu, 15 Oct 1998 05:59:59 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17075
          for ; Thu, 15 Oct 1998 05:59:50 -0700 (PDT)
          (envelope-from karl@Genesis.Denninger.Net)
Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id HAA00247; Thu, 15 Oct 1998 07:59:14 -0500 (CDT)
Message-ID: <19981015075914.A243@Denninger.Net>
Date: Thu, 15 Oct 1998 07:59:14 -0500
From: Karl Denninger 
To: Mike Smith 
Cc: current@FreeBSD.ORG
Subject: Re: Uh, guys, BETA 3.0 right now panics on boot
References: <19981014202222.A208@Denninger.Net> <199810150157.SAA00818@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199810150157.SAA00818@dingo.cdrom.com>; from Mike Smith on Wed, Oct 14, 1998 at 06:57:11PM -0700
Organization: Karl's Sushi and Packet Smashers
X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Oct 14, 1998 at 06:57:11PM -0700, Mike Smith wrote:
> > Immediate panic, no dump, "supervisor page not present".  Never even starts
> > probing devices.
> 
> If you're using the new bootloader, go slap Peter Wemm; it's breakage 
> in his changes to the preload code (specifically, relocations).

That's it.  I shut off the new bootloader and the kernel now comes up.

--
-- 
Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl
I ain't even *authorized* to speak for anyone other than myself, so give
up now on trying to associate my words with any particular organization.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 06:32:07 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA20812
          for freebsd-current-outgoing; Thu, 15 Oct 1998 06:32:07 -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 GAA20807
          for ; Thu, 15 Oct 1998 06:32:05 -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 IAA25456;
	Thu, 15 Oct 1998 08:31:36 -0500 (CDT)
Message-Id: <199810151331.IAA25456@ns.tar.com>
From: "Richard Seaman, Jr." 
To: "HighWind Software Information" 
Cc: "current@freebsd.org" 
Date: Thu, 15 Oct 98 08:31:35 -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: Recent 3.0's are Depressing
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 14 Oct 1998 22:15:13 -0400 (EDT), HighWind Software Information wrote:

>
>Well... I think we have a test program that illustrates a (perhaps
>"the") bug in the new libc_r.a's. It appears that
>pthread_cond_timedwait() is now broken.
>
>We updated our machine to the latest libc_r. Check out the following
>program.
>
>Haven't looked at the libc_r code yet.

Hmm..  I ran your test program and it works ok here.  It blocks for
15 seconds, and pthread_cond_timewait returns ETIMEDOUT.  I'm not 
running the most current kernel and system, but I did update libc_r
to -current as of yesterday.

dick@ns$ uname -a                                                                                                                
FreeBSD ns.tar.com 3.0-BETA FreeBSD 3.0-BETA #15: Sat Sep 26 11:33:35 CDT 1998




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 06:53:28 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA23820
          for freebsd-current-outgoing; Thu, 15 Oct 1998 06:53:28 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sage1.sagecorp.com ([204.250.198.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23815
          for ; Thu, 15 Oct 1998 06:53:27 -0700 (PDT)
          (envelope-from djw@sage1.sagecorp.com)
Received: from localhost (djw@localhost) by sage1.sagecorp.com (8.7.5/8.7.3) with SMTP id HAA15568; Thu, 15 Oct 1998 07:59:52 -0600 (MDT)
Date: Thu, 15 Oct 1998 07:59:51 -0600 (MDT)
From: Darren Whittaker 
To: Mike Smith 
cc: freebsd-current@FreeBSD.ORG, john.young@openmarket.com
Subject: Re: problem in 3.0 
In-Reply-To: <199810150127.SAA00583@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 Wed, 14 Oct 1998, Mike Smith wrote:

> > The code appeared to work until I set buf[0] = '\0'; at the start of the
> > loop, then only one message was displayed. Since err displays to std error
> > and I have to run this program from a browers I did not see any error
> > messages.
> 
> I specifically asked what the exact code below does when built as a 
> program and run on your system.
> 
> If setting buf[0] to 0 kills all but the first output, you should be 
> checking the return from fgets, as it's likely that it's not returning 
> anything.
You are right, when I check the return value of fgets, it's NULL, and
feof() returns a non-zero value meaning at end of file. So is this more of
an I/O problem than a popen error?

 -Darren

PS
  Thanks for your help 
------------------
Darren Whittaker
Senior Software Engineer
Small Enterprise Group
Open Market, Inc.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 07:02:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA25217
          for freebsd-current-outgoing; Thu, 15 Oct 1998 07:02:58 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25091
          for ; Thu, 15 Oct 1998 07:02:14 -0700 (PDT)
          (envelope-from ady@warpnet.ro)
Received: from localhost (ady@localhost)
	by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id QAA12316;
	Thu, 15 Oct 1998 16:56:13 +0300 (EEST)
	(envelope-from ady@warpnet.ro)
Date: Thu, 15 Oct 1998 16:56:12 +0300 (EEST)
From: Adrian Penisoara 
To: Cory Kempf 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: What is a BSP, and why does SMP panic about it?
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

Hi,

On 11 Oct 1998, Cory Kempf wrote:

> 
> When I attempted to boot, I got a panic: no BSP found.
> 
> Uh, what is a BSP, and where can they be found?


 AFAIK it's BootS*** Processor (??) -- meaning the processor that will run
the boot code.
 I believe you'll need to change the CPU to the other socket (it should
read CPU0 or something like that on the motherboard diagram).

 This is just a supposition, theoretically the machine shouldn't even boot
up if the CPU was placed in the wrong socket ??

> 
> Thanks,
> 
> +C
> -- 
> Thinking of purchasing RAM from the Chip Merchant?  
> Please read this first: 
> 
> Cory Kempf                Macintosh / Unix Consulting & Software Development
> ckempf@enigami.com        
> 

 Just my $0.02
 Ady (@freebsd.ady.ro)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 07:10:03 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA27224
          for freebsd-current-outgoing; Thu, 15 Oct 1998 07:10:03 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from plethora.techv.net ([205.210.170.77])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27170
          for ; Thu, 15 Oct 1998 07:09:58 -0700 (PDT)
          (envelope-from darin@slovitt.net)
Received: from localhost (darin@localhost)
	by plethora.techv.net (8.8.8/8.8.8) with ESMTP id KAA05390
	for ; Thu, 15 Oct 1998 10:09:31 -0400 (EDT)
Date: Thu, 15 Oct 1998 10:09:31 -0400 (EDT)
From: Darin Slovitt 
X-Sender: darin@plethora.techv.net
To: freebsd-current@FreeBSD.ORG
Subject: Limits Problems ...
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,

I been looking through the mailing archives, but I couldn't find a direct
answer to my problem. Perhaps someone here will be helpfull, and please
excuse this post if I missed some obvious answer ...

I have installed a fresh copy of 3.0-19981006-BETA, and seem to have no
end of problems with limits. When I run 'limits', I get the following
results:

Resource limits (current):
  cputime          infinity secs
  filesize         infinity kb
  datasize           524288 kb
  stacksize           65536 kb
  coredumpsize     infinity kb
  memoryuse        infinity kb
  memorylocked     infinity kb
  maxprocesses          531
  openfiles            1064

I have checked login.conf, and it does indeed confirm that the cputime
limits should be set to 'infinity'.

        :cputime=unlimited:\
        :datasize=unlimited:\
        :stacksize=unlimited:\
        :memorylocked=unlimited:\
        :memoryuse=unlimited:\
        :filesize=unlimited:\
        :coredumpsize=unlimited:\
        :openfiles=unlimited:\
        :maxproc=unlimited:\

When I attempt to untar a file, I get the ever-so-annoying: 
 Cputime limit exceeded
 0.000u 0.000s 5:33.14 0.0%      0+0k 3594+7617io 0pf+0w

The point at which this occurs seems random at best, sometimes I almost
make it to the end, other times only two or so files are extracted
before it gives the above message.

What am I missing? When you 'su' to root, does it keep the limits of the
current user, or take on the limits set for root? This machine is in a
remote location, and I cannot compile or even untar things! Why would the
installation default to this!?

Any help would be greatly appreciated!!

--
TTYS :-)
Darin Slovitt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 07:26:57 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA29432
          for freebsd-current-outgoing; Thu, 15 Oct 1998 07:26:57 -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 HAA29415
          for ; Thu, 15 Oct 1998 07:26:44 -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 VAA11428;
	Thu, 15 Oct 1998 21:58:15 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810151358.VAA11428@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mike Smith 
cc: Karl Denninger , current@FreeBSD.ORG
Subject: Re: Uh, guys, BETA 3.0 right now panics on boot 
In-reply-to: Your message of "Wed, 14 Oct 1998 18:57:11 MST."
             <199810150157.SAA00818@dingo.cdrom.com> 
Date: Thu, 15 Oct 1998 21:58:14 +0800
From: Peter Wemm 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Smith wrote:
> > Immediate panic, no dump, "supervisor page not present".  Never even starts
> > probing devices.
> 
> If you're using the new bootloader, go slap Peter Wemm; it's breakage 
> in his changes to the preload code (specifically, relocations).

Err, what?

I could imagine this happening if the kernel and the loader got out of 
sync.  The alignment of the MODINFO_* tags was changed from int32_t 
alignment to int64_t alignment for the benefit of the alpha.  vm_offset_t 
is 64 bit there and can't be accessed on non-natural boundaries.

There are a couple of other problems that i've found.  Some long-standing
bugs in the kern_linker.c code and the link_*.c modules turned up.

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 15 07:30:03 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA29976
          for freebsd-current-outgoing; Thu, 15 Oct 1998 07:30:03 -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 HAA29909
          for ; Thu, 15 Oct 1998 07:29:59 -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 JAA02779;
	Thu, 15 Oct 1998 09:29:21 -0500 (EST)
Date: Thu, 15 Oct 1998 09:29:21 -0500 (EST)
From: John Fieber 
To: "Jeffrey J. Mountin" 
cc: Mike Smith , "Jordan K. Hubbard" ,
        Karl Pielorz , current@FreeBSD.ORG
Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) 
In-Reply-To: <3.0.3.32.19981014233959.010725dc@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, 14 Oct 1998, Jeffrey J. Mountin wrote:

> OK, I'm still a bit unclear.  There have been dozens of messages concerning
> the loader et all w/wo an ELF kernel.

[...]

> Thus making the transition smoother to full ELF (ie kernel) for the next
> release.

Or, think if it like removing a band-aid--a quick yank and get it
over with fast.  Slowly pulling those hairs out one by
one...yech!  It is a foregone conclusion that 3.0 is not going to
be a stunning release, what with half the ports collection broken
and the like....what is another wee little bump?  :-)

-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 15 08:01:19 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA04669
          for freebsd-current-outgoing; Thu, 15 Oct 1998 08:01: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 IAA04664
          for ; Thu, 15 Oct 1998 08:01:17 -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 IAA03637;
	Thu, 15 Oct 1998 08:00:56 -0700 (PDT)
	(envelope-from jdp)
Message-Id: <199810151500.IAA03637@austin.polstra.com>
To: winter@jurai.net
Subject: Re: kernel dependancies broken?
In-Reply-To: 
References: 
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Date: Thu, 15 Oct 1998 08:00:56 -0700
From: John Polstra 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article ,
Matthew N. Dodd  wrote:
> 
> Anyone seen this?
> 
> 1. edit src/sys/cam/cam_xpt.c
> 2. add a quirk entry
> 3. cd src/sys/compile/KERNEL/
> 4. 'make'
> 5. wait while most of the kernel source is rebuilt.

It doesn't happen here on an ELF system from October 11.  Maybe you
can debug it by using "make -d m".  Also, look at your .depend file
and see what depends on cam_xpt.[co].

It might be worthwhile to remove the compilation directory entirely,
reconfig your kernel, and try it again.  Maybe you've gotten some
screwy circular arrangement of symlinks or something.  (OK, I'm
reaching.)  An fsck run might not be a bad idea, either. :-)

John
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 08:13:11 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA05853
          for freebsd-current-outgoing; Thu, 15 Oct 1998 08:13:11 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA05826
          for ; Thu, 15 Oct 1998 08:12:54 -0700 (PDT)
          (envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id OAA28254; Thu, 15 Oct 1998 14:14:14 +0100
From: Luigi Rizzo 
Message-Id: <199810151314.OAA28254@labinfo.iet.unipi.it>
Subject: dummynet for 3.0 (fixed)
To: current@FreeBSD.ORG
Date: Thu, 15 Oct 1998 14:14:14 +0100 (MET)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thanks to Philippe Regnauld i have removed the hopefully last bugs from
the 3.0 port of dummynet+bridge. Patches for a very -current system are
at http://www.iet.unipi.it/~luigi/ip_dummynet/

This stuff will be (hopefully) on the 3.0 CD in the xperimnt/ area
whatever it is called there. Will commit patches after the release,
at which point it would be interesting (for me) if someone can try
these things on Alpha machines.

	cheers
	luigi
-----------------------------+--------------------------------------
Luigi Rizzo                  |  Dip. di Ingegneria dell'Informazione
email: luigi@iet.unipi.it    |  Universita' di Pisa
tel: +39-50-568533           |  via Diotisalvi 2, 56126 PISA (Italy)
fax: +39-50-568522           |  http://www.iet.unipi.it/~luigi/
_____________________________|______________________________________

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 08:34:47 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA08653
          for freebsd-current-outgoing; Thu, 15 Oct 1998 08:34:47 -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 IAA08632
          for ; Thu, 15 Oct 1998 08:34:38 -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 LAA16665;
	Thu, 15 Oct 1998 11:34:04 -0400 (EDT)
	(envelope-from wollman)
Date: Thu, 15 Oct 1998 11:34:04 -0400 (EDT)
From: Garrett Wollman 
Message-Id: <199810151534.LAA16665@khavrinen.lcs.mit.edu>
To: Andrzej Bialecki 
Cc: bryan collins , freebsd-current@FreeBSD.ORG
Subject: Re: /usr/sbin/arp: actual retrieval of routing table
In-Reply-To: 
References: <199810150116.SAA03564@hub.freebsd.org>
	
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

< said:

> Perhaps the programs which use this double sysctl(3) calls should allocate
> somewhat bigger buffer than that calculated on basis of previous call,
> anticipating for unexpected change in data size...

Actually, the size-estimate routines often intentionally overestimate
for precisely this reason.

-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 15 08:40:45 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA09735
          for freebsd-current-outgoing; Thu, 15 Oct 1998 08:40:45 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09724
          for ; Thu, 15 Oct 1998 08:40:39 -0700 (PDT)
          (envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA17467;
	Thu, 15 Oct 1998 11:40:06 -0400 (EDT)
Date: Thu, 15 Oct 1998 11:40:06 -0400 (EDT)
From: "Matthew N. Dodd" 
To: John Polstra 
cc: current@FreeBSD.ORG
Subject: Re: kernel dependancies broken?
In-Reply-To: <199810151500.IAA03637@austin.polstra.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 Thu, 15 Oct 1998, John Polstra wrote:
> It doesn't happen here on an ELF system from October 11.  Maybe you
> can debug it by using "make -d m".  Also, look at your .depend file
> and see what depends on cam_xpt.[co].

Nothing unusual as far as I can tell.

> It might be worthwhile to remove the compilation directory entirely,
> reconfig your kernel, and try it again.  Maybe you've gotten some
> screwy circular arrangement of symlinks or something.  (OK, I'm
> reaching.)  An fsck run might not be a bad idea, either. :-)

No joy.

Examining scsi_sa.o...modified 11:34:02 Oct 15, 1998...modified before
source...out-of-date.    

It does this for -every- file it recompiles. (under make -d m)  No I don't
have a time problem, no the file isn't modified before the source file.

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 08:49:02 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA10951
          for freebsd-current-outgoing; Thu, 15 Oct 1998 08:49:02 -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 IAA10946
          for ; Thu, 15 Oct 1998 08:49:00 -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 IAA03958;
	Thu, 15 Oct 1998 08:48:38 -0700 (PDT)
	(envelope-from jdp)
Message-Id: <199810151548.IAA03958@austin.polstra.com>
To: "Matthew N. Dodd" 
cc: current@FreeBSD.ORG
Subject: Re: kernel dependancies broken? 
In-reply-to: Your message of "Thu, 15 Oct 1998 11:40:06 EDT."
     
Date: Thu, 15 Oct 1998 08:48:38 -0700
From: John Polstra 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> It does this for -every- file it recompiles. (under make -d m) No
> I don't have a time problem, no the file isn't modified before the
> source file.

I'm doing a fresh make world now, so I'll be able to try it on an
up-to-date system in a couple of hours.  If it can't be duplicated,
then I would seriously suspect a damaged filesystem.

John
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 08:59:32 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA12203
          for freebsd-current-outgoing; Thu, 15 Oct 1998 08:59:32 -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 IAA12198
          for ; Thu, 15 Oct 1998 08:59:30 -0700 (PDT)
          (envelope-from info@highwind.com)
Received: (from info@localhost)
	by highwind.com (8.8.6/8.8.6) id LAA25044;
	Thu, 15 Oct 1998 11:58:36 -0400 (EDT)
Date: Thu, 15 Oct 1998 11:58:36 -0400 (EDT)
Message-Id: <199810151558.LAA25044@highwind.com>
From: HighWind Software Information 
To: lists@tar.com
CC: current@FreeBSD.ORG
In-reply-to: <199810151331.IAA25456@ns.tar.com> (lists@tar.com)
Subject: Re: Recent 3.0's are Depressing
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>   FreeBSD ns.tar.com 3.0-BETA FreeBSD 3.0-BETA #15: Sat Sep 26 11:33:35 CDT 1998

There is no question that the program does NOT work on our machine.

August 31st kernel:

% uname -a
FreeBSD zonda.highwind.com 3.0-19980831-SNAP FreeBSD 3.0-19980831-SNAP #0: Mon Aug 31 14:03:19 GMT 1998     root@make.ican.net:/usr/src/sys/compile/GENERIC  i386

However, the LATEST libc_r:

zonda.highwind.com:/usr/lib/aout % ls -l libc_r*
-r--r--r--  1 bin  bin  702952 Oct 14 12:35 libc_r.a
-r--r--r--  1 bin  bin  547350 Oct 14 12:35 libc_r.so.3.0
-r--r--r--  1 bin  bin  812290 Oct 14 12:35 libc_r_p.a

zonda.highwind.com:/usr/lib/aout % md5 libc_r.so.3.0 
MD5 (libc_r.so.3.0) = b5fcfaf056d5ddeaa7f6b0ace5e17216

zonda.highwind.com:/usr/lib/aout % md5 libc_r.a
MD5 (libc_r.a) = be936ec713f97e927151d70cd2e53481


See:

% ./condBug 
assertion "err" failed: file "condBug.C", line 49
Abort

This is a pretty *SERIOUS* problem for us.

John: Do you see the same problem as we do?

-Rob

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 09:03:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA12928
          for freebsd-current-outgoing; Thu, 15 Oct 1998 09:03:58 -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 JAA12923
          for ; Thu, 15 Oct 1998 09:03:56 -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 JAA07569;
	Thu, 15 Oct 1998 09:03:38 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: John Fieber 
cc: "Jeffrey J. Mountin" , Mike Smith ,
        Karl Pielorz , current@FreeBSD.ORG
Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) 
In-reply-to: Your message of "Thu, 15 Oct 1998 09:29:21 CDT."
              
Date: Thu, 15 Oct 1998 09:03:38 -0700
Message-ID: <7565.908467418@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> one...yech!  It is a foregone conclusion that 3.0 is not going to
> be a stunning release, what with half the ports collection broken
> and the like....what is another wee little bump?  :-)

I think it's important to distinguish between normal bumps in the road
and the migrating turtles you're running over.  A "broken" ports
collection is by no means equivalent to the ELF kernel issue and
should not be erroneously confused for such. :)

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 09:15:47 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA14606
          for freebsd-current-outgoing; Thu, 15 Oct 1998 09:15:47 -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 JAA14600
          for ; Thu, 15 Oct 1998 09:15:44 -0700 (PDT)
          (envelope-from info@highwind.com)
Received: (from info@localhost)
	by highwind.com (8.8.6/8.8.6) id MAA25672;
	Thu, 15 Oct 1998 12:14:53 -0400 (EDT)
Date: Thu, 15 Oct 1998 12:14:53 -0400 (EDT)
Message-Id: <199810151614.MAA25672@highwind.com>
From: HighWind Software Information 
To: lists@tar.com
CC: current@FreeBSD.ORG
In-reply-to: <199810151331.IAA25456@ns.tar.com> (lists@tar.com)
Subject: Re: Recent 3.0's are Depressing
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


   Hmm..  I ran your test program and it works ok here.  It blocks for
   15 seconds, and pthread_cond_timewait returns ETIMEDOUT.  I'm not 
   running the most current kernel and system, but I did update libc_r
   to -current as of yesterday.

   dick@ns$ uname -a                                                                                                                
   FreeBSD ns.tar.com 3.0-BETA FreeBSD 3.0-BETA #15: Sat Sep 26 11:33:35 CDT 1998


This makes me worry:

Both of us are on the "latest" libc_r and we see different results.
Statically linking an old libc_r into the application didn't fix the problem.

This makes me think it isn't "libc_r".

Any of the kernel folks or more knowledgable folks get a chance to try that
program on the latest/greatest kernel + latest/greatest libc_r?

-Rob

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 09:28:33 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA16544
          for freebsd-current-outgoing; Thu, 15 Oct 1998 09:28:33 -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 JAA16537
          for ; Thu, 15 Oct 1998 09:28:29 -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 JAA22910;
          Thu, 15 Oct 1998 09:28:10 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Date: Thu, 15 Oct 1998 09:28:09 -0700 (PDT)
From: Doug White 
To: Darin Slovitt 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ...
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, 15 Oct 1998, Darin Slovitt wrote:

> Resource limits (current):
>   cputime          infinity secs

> I have checked login.conf, and it does indeed confirm that the cputime
> limits should be set to 'infinity'.
> 
>         :cputime=unlimited:\

> When I attempt to untar a file, I get the ever-so-annoying: 
>  Cputime limit exceeded
>  0.000u 0.000s 5:33.14 0.0%      0+0k 3594+7617io 0pf+0w

This sounds like the timewarping clock bug that's been popping up on
systems running APM.  If you're using the APM driver try knocking it out
of your kernel.

Don't forget, when you modfiy /etc/login.conf, run cap_mkdb afterwards.

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 15 09:34:47 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA17638
          for freebsd-current-outgoing; Thu, 15 Oct 1998 09:34:47 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17633
          for ; Thu, 15 Oct 1998 09:34:44 -0700 (PDT)
          (envelope-from skynyrd@opus.cts.cwu.edu)
Received: from localhost (skynyrd@localhost)
	by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id JAA10732;
	Thu, 15 Oct 1998 09:34:04 -0700 (PDT)
Date: Thu, 15 Oct 1998 09:34:04 -0700 (PDT)
From: Chris Timmons 
To: HighWind Software Information 
cc: lists@tar.com, current@FreeBSD.ORG
Subject: Re: Recent 3.0's are Depressing
In-Reply-To: <199810151614.MAA25672@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



Well, you'll have to take what you can get - I'm not a kernel folk nor a
more knowledgable folk, but I happen to have a fairly recent -current from
yesterday afternoon :)

tcsh> time ./condBug
0.008u 0.016s 0:14.48 0.0%      24+496k 0+0io 0pf+0w

FreeBSD midtest3.gw.cwu.edu 3.0-BETA FreeBSD 3.0-BETA #0: Wed Oct 14
17:41:50 PDT 1998 

(my sources were up-to-date about two hours before the kernel was built.
this is also an SMP kernel running on a dual-PII machine.)

was it supposed to blow up or something?

-Chris


On Thu, 15 Oct 1998, HighWind Software Information wrote:

> Any of the kernel folks or more knowledgable folks get a chance to try that
> program on the latest/greatest kernel + latest/greatest libc_r?
> 
> -Rob


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 09:35:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA17720
          for freebsd-current-outgoing; Thu, 15 Oct 1998 09:35:58 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17708
          for ; Thu, 15 Oct 1998 09:35:56 -0700 (PDT)
          (envelope-from skynyrd@opus.cts.cwu.edu)
Received: from localhost (skynyrd@localhost)
	by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id JAA10846;
	Thu, 15 Oct 1998 09:35:36 -0700 (PDT)
Date: Thu, 15 Oct 1998 09:35:36 -0700 (PDT)
From: Chris Timmons 
To: Doug White 
cc: Darin Slovitt , freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ...
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


3.0-current (if you update your /etc files) enforces no resource limits
(once you've done a cap_mkdb I suppose.)

-Chris


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 09:58:38 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA21090
          for freebsd-current-outgoing; Thu, 15 Oct 1998 09:58:38 -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 JAA21081
          for ; Thu, 15 Oct 1998 09:58: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 MAA01901
	for ; Thu, 15 Oct 1998 12:58:10 -0400 (EDT)
	(envelope-from scrappy@hub.org)
Date: Thu, 15 Oct 1998 12:58:10 -0400 (EDT)
From: "Marc G. Fournier" 
To: freebsd-current@FreeBSD.ORG
Subject: Upping process limits...
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 running a 3.0-current build of around the end of July this year, so
pre-ELF stuff and have hit a snag...

I need to increase the news processes datasize and stack limits, and can't
seem to get them above 256Meg, even with modifying /etc/login.conf (and
running cap_mkdb)...

I had, at one point, added MAXDSIZ and DLTDSIZ values of 256Meg to my
kernel, and suspect that this has created a *hard limit* to th emax,which
login.conf can't override.  Is this correct?

If so, is there any way around this, without my having to rebuild?  I've
been putting off upgradeing to the current 3.0-ELF stuff for two
reasons...fear and beign 2500kilometers away from the server :(

Is there any sysctl value I can set or something like that?

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  Thu Oct 15 10:04:32 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA22490
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:04:32 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from plethora.techv.net ([205.210.170.77])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22485
          for ; Thu, 15 Oct 1998 10:04:28 -0700 (PDT)
          (envelope-from darin@slovitt.net)
Received: from localhost (darin@localhost)
	by plethora.techv.net (8.8.8/8.8.8) with ESMTP id NAA05938;
	Thu, 15 Oct 1998 13:04:10 -0400 (EDT)
Date: Thu, 15 Oct 1998 13:04:09 -0400 (EDT)
From: Darin Slovitt 
X-Sender: darin@plethora.techv.net
To: Doug White 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ...
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, 15 Oct 1998, Doug White wrote:

> This sounds like the timewarping clock bug that's been popping up on
> systems running APM.  If you're using the APM driver try knocking it out
> of your kernel.

Unfortunatly I don't have APM in my kernel. It was one of the first things
that I took out.

> Don't forget, when you modfiy /etc/login.conf, run cap_mkdb afterwards.

Always.

Thanks for the suggestion, anything else that you can think of?

--
TTYS :-)
Darin Slovitt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 10:07:32 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA22838
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:07:32 -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 KAA22833
          for ; Thu, 15 Oct 1998 10:07:30 -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 NAA06490;
	Thu, 15 Oct 1998 13:08:52 -0400 (EDT)
	(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Thu, 15 Oct 1998 13:08:51 -0400 (EDT)
From: Alfred Perlstein 
X-Sender: bright@porkfriedrice.ny.genx.net
To: "Marc G. Fournier" 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Upping process limits...
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


you don't have a snap of that source code available to rebuild a kernel
from back then with?

have you looked into using an earlier version of the sources? you're able
to ask for an older source tree by setting some flag in a cvsup file,
check the man page or the older lists.  (i don't know how far back you can
go though)

yes, you have a hard limit, yes you need a new kernel.

-Alfred

On Thu, 15 Oct 1998, Marc G. Fournier wrote:

> 
> I'm running a 3.0-current build of around the end of July this year, so
> pre-ELF stuff and have hit a snag...
> 
> I need to increase the news processes datasize and stack limits, and can't
> seem to get them above 256Meg, even with modifying /etc/login.conf (and
> running cap_mkdb)...
> 
> I had, at one point, added MAXDSIZ and DLTDSIZ values of 256Meg to my
> kernel, and suspect that this has created a *hard limit* to th emax,which
> login.conf can't override.  Is this correct?
> 
> If so, is there any way around this, without my having to rebuild?  I've
> been putting off upgradeing to the current 3.0-ELF stuff for two
> reasons...fear and beign 2500kilometers away from the server :(
> 
> Is there any sysctl value I can set or something like that?
> 
> 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
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 10:16:17 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA23796
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:16:17 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from plethora.techv.net ([205.210.170.77])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23764
          for ; Thu, 15 Oct 1998 10:16:12 -0700 (PDT)
          (envelope-from darin@slovitt.net)
Received: from localhost (darin@localhost)
	by plethora.techv.net (8.8.8/8.8.8) with ESMTP id NAA05988;
	Thu, 15 Oct 1998 13:15:01 -0400 (EDT)
Date: Thu, 15 Oct 1998 13:15:01 -0400 (EDT)
From: Darin Slovitt 
X-Sender: darin@plethora.techv.net
To: Chris Timmons 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ...
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, 15 Oct 1998, Chris Timmons wrote:

> 3.0-current (if you update your /etc files) enforces no resource limits
> (once you've done a cap_mkdb I suppose.)

I'm using the most recent one I could find:
 $Id: login.conf,v 1.22 1998/09/17 17:02:39 dt Exp $

Is there a newer one I should be using? As near as I can tell, ALL the
limits in this file *are* set to infinity. Unfortunatly something isn't
obeying this ...

--
TTYS :-)
Darin Slovitt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 10:21:57 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA24942
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:21:57 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24931
          for ; Thu, 15 Oct 1998 10:21:55 -0700 (PDT)
          (envelope-from skynyrd@opus.cts.cwu.edu)
Received: from localhost (skynyrd@localhost)
	by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id KAA13030;
	Thu, 15 Oct 1998 10:21:36 -0700 (PDT)
Date: Thu, 15 Oct 1998 10:21:36 -0700 (PDT)
From: Chris Timmons 
To: Darin Slovitt 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ...
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


No, you've got the right file.  Is you login.conf.db as hopelessly out of
date as mine?  

daemon:/etc#> ls -l login*
-rw-r--r--  1 root  wheel   1837 Sep  6 12:11 login.access
-rw-r--r--  1 root  wheel   6794 Sep 18 13:38 login.conf
-rw-r--r--  1 root  wheel  32768 Dec 28  1997 login.conf.db


On Thu, 15 Oct 1998, Darin Slovitt wrote:

> Is there a newer one I should be using? As near as I can tell, ALL the
> limits in this file *are* set to infinity. Unfortunatly something isn't
> obeying this ...


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 10:25:46 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA25575
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:25:46 -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 KAA25544
          for ; Thu, 15 Oct 1998 10:25:37 -0700 (PDT)
          (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by hub.org (8.8.8/8.8.8) with ESMTP id NAA05676;
	Thu, 15 Oct 1998 13:25:11 -0400 (EDT)
	(envelope-from scrappy@hub.org)
Date: Thu, 15 Oct 1998 13:24:57 -0400 (EDT)
From: "Marc G. Fournier" 
To: Alfred Perlstein 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Upping process limits...
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 wish...I'd also have to play with getting the right versions of CAM put
into it and all that...I'll end up having to upgrade eventually, just was
hoping to avoid for a couple of months :(

Should I get rid of the *SIZ values altogether, in favor of login.conf, or
is there a 'default ceiling' in place?

On Thu, 15 Oct 1998, Alfred Perlstein wrote:

> 
> you don't have a snap of that source code available to rebuild a kernel
> from back then with?
> 
> have you looked into using an earlier version of the sources? you're able
> to ask for an older source tree by setting some flag in a cvsup file,
> check the man page or the older lists.  (i don't know how far back you can
> go though)
> 
> yes, you have a hard limit, yes you need a new kernel.
> 
> -Alfred
> 
> On Thu, 15 Oct 1998, Marc G. Fournier wrote:
> 
> > 
> > I'm running a 3.0-current build of around the end of July this year, so
> > pre-ELF stuff and have hit a snag...
> > 
> > I need to increase the news processes datasize and stack limits, and can't
> > seem to get them above 256Meg, even with modifying /etc/login.conf (and
> > running cap_mkdb)...
> > 
> > I had, at one point, added MAXDSIZ and DLTDSIZ values of 256Meg to my
> > kernel, and suspect that this has created a *hard limit* to th emax,which
> > login.conf can't override.  Is this correct?
> > 
> > If so, is there any way around this, without my having to rebuild?  I've
> > been putting off upgradeing to the current 3.0-ELF stuff for two
> > reasons...fear and beign 2500kilometers away from the server :(
> > 
> > Is there any sysctl value I can set or something like that?
> > 
> > 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
> > 
> 

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  Thu Oct 15 10:29:29 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA25945
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:29:29 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from plethora.techv.net ([205.210.170.77])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25937
          for ; Thu, 15 Oct 1998 10:29:26 -0700 (PDT)
          (envelope-from darin@slovitt.net)
Received: from localhost (darin@localhost)
	by plethora.techv.net (8.8.8/8.8.8) with ESMTP id NAA06036;
	Thu, 15 Oct 1998 13:28:18 -0400 (EDT)
Date: Thu, 15 Oct 1998 13:28:18 -0400 (EDT)
From: Darin Slovitt 
X-Sender: darin@plethora.techv.net
To: Chris Timmons 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ...
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, 15 Oct 1998, Chris Timmons wrote:

> No, you've got the right file.  Is you login.conf.db as hopelessly out of
> date as mine?  
> daemon:/etc#> ls -l login*
> -rw-r--r--  1 root  wheel   1837 Sep  6 12:11 login.access
> -rw-r--r--  1 root  wheel   6794 Sep 18 13:38 login.conf
> -rw-r--r--  1 root  wheel  32768 Dec 28  1997 login.conf.db

-rw-r--r--  1 root   wheel  32768 Oct 15 21:08 login.conf.db

Appears up-to-date. I've ran 'cap_mkdb /etc/login.conf' a few times in
hopes that it was simply the db out of date. Not so =(

--
TTYS :-)
Darin Slovitt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 10:31:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA26224
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:31:35 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26217
          for ; Thu, 15 Oct 1998 10:31:33 -0700 (PDT)
          (envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.8.8/8.8.7) with SMTP id NAA19065;
	Thu, 15 Oct 1998 13:31:13 -0400 (EDT)
Date: Thu, 15 Oct 1998 13:31:12 -0400 (EDT)
From: "Matthew N. Dodd" 
To: John Polstra 
cc: current@FreeBSD.ORG
Subject: Re: kernel dependancies broken? 
In-Reply-To: <199810151548.IAA03958@austin.polstra.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 Thu, 15 Oct 1998, John Polstra wrote:
> I'm doing a fresh make world now, so I'll be able to try it on an
> up-to-date system in a couple of hours.  If it can't be duplicated,
> then I would seriously suspect a damaged filesystem.

I'm pretty sure I found the problem; files with modification dates in the
future.  For some reason a great many files on that machine were
created/modified in 2007.  Very strange.

I'm doing a `find . | xargs touch` right now to fix it.

I'm really glad the build process isn't broken. :)

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 10:32:56 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA26377
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:32:56 -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 KAA26372
          for ; Thu, 15 Oct 1998 10:32: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 NAA06517;
	Thu, 15 Oct 1998 13:34:19 -0400 (EDT)
	(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Thu, 15 Oct 1998 13:34:19 -0400 (EDT)
From: Alfred Perlstein 
X-Sender: bright@porkfriedrice.ny.genx.net
To: "Marc G. Fournier" 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Upping process limits...
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


afaik the defualt is smaller than what you have in place in place now.

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 Thu, 15 Oct 1998, Marc G. Fournier wrote:

> 
> I wish...I'd also have to play with getting the right versions of CAM put
> into it and all that...I'll end up having to upgrade eventually, just was
> hoping to avoid for a couple of months :(
> 
> Should I get rid of the *SIZ values altogether, in favor of login.conf, or
> is there a 'default ceiling' in place?
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 10:33:45 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA26431
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:33:45 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fhut.fingerhut.com (fhut.fingerhut.com [204.221.45.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26418
          for ; Thu, 15 Oct 1998 10:33:41 -0700 (PDT)
          (envelope-from Bruce.Albrecht@seag.fingerhut.com)
Received: from gw002e0.seag.fingerhut.com (intmail [151.210.152.6])
	by fhut.fingerhut.com (8.9.1/8.9.1) with ESMTP id MAA22122;
	Thu, 15 Oct 1998 12:33:21 -0500 (CDT)
Received: from seag.fingerhut.com (GF007E0.SEAG.fingerhut.com [151.210.140.7])
	by gw002e0.seag.fingerhut.com (8.8.8/8.8.8) with SMTP id MAA18697;
	Thu, 15 Oct 1998 12:33:20 -0500 (CDT)
Received: from gf006e0.seag.fingerhut.com by seag.fingerhut.com (SMI-8.6/SMI-SVR4)
	id MAA00327; Thu, 15 Oct 1998 12:33:17 -0500
Received: by gf006e0.seag.fingerhut.com (SMI-8.6/SMI-SVR4)
	id MAA01407; Thu, 15 Oct 1998 12:33:15 -0500
From: Bruce Albrecht 
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <13862.12762.329486.287365@fingerhut.com>
Date: Thu, 15 Oct 1998 12:33:14 -0500 (CDT)
To: Bruce Evans 
Cc: bruce@zuhause.mn.org, freebsd-current@FreeBSD.ORG
Subject: Re: New build problem?
In-Reply-To: <199810150534.PAA05419@godzilla.zeta.org.au>
References: <199810150534.PAA05419@godzilla.zeta.org.au>
X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bruce Evans writes:
 > >I was looking at this further, and it looks to me like the problem is
 > >that the make depend for /usr/src/lib/csu/i386 is looking for
 > >the includes in /usr/obj/usr/src/tmp/usr/include instead of
 > >/usr/obj/aout/usr/src/tmp/usr/include.  The reason why it got further
 > >in the previous build is because I hadn't started out with a totally
 > >empty /usr/obj, and I think it was finding an old param.h.
 > >
 > >Is this something that needs to be fixed before the release?  I
 > >suspect that it may not be an issue for elf builds on an elf machine,
 > >but I haven't gotten far enough to check.  I was hoping to upgrade my
 > >system from source, but maybe I'll have to resort to installing the
 > >3.0 release.
 > 
 > You apparently have a stale .depend file in the source directory.
 > The `make clean' step won't remove this if an obj directory exists.
 > `make clean' can be run twice to first rm -rf any obj directories
 > and then to clean the source tree, but `make world' only runs it
 > once since this is sufficient for files created by `make world',
 > modulo bugs in (possibly previous versions of) `make world'.

That was the problem.  Thanks.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 10:51:17 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA29150
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:51:17 -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 KAA29136
          for ; Thu, 15 Oct 1998 10:51:09 -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 BAA12300;
	Fri, 16 Oct 1998 01:21:04 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810151721.BAA12300@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Somers 
cc: Bruce Evans , current@FreeBSD.ORG, kjc@csl.sony.co.jp
Subject: Re: Improper sharing of modem bandwidth 
In-reply-to: Your message of "Thu, 15 Oct 1998 08:12:18 +0100."
             <199810150712.IAA00515@woof.lan.awfulhak.org> 
Date: Fri, 16 Oct 1998 01:21:03 +0800
From: Peter Wemm 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Brian Somers wrote:
> > >If there was an ioctl to change the usable tty buffer size to less than 
> > >4k, ppp could set it to ``whatever the MTU is'' and get quite a 
> > >reasonable interactive performance gain.
> > 
> > Maybe not.  Kernel ppp doesn't have the 4KB buffer between it and the
> > driver, but its interactive performance is not reasonable when just
> > one scp is using the link.
> 
> But kernel ppp doesn't do any interactive queue jumping does it ?

Yes it does, and has done so from near day one.  However, it's IP_TOS 
based rather than the traditional magic port numbers.

> > Bruce

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 15 11:08:31 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA02055
          for freebsd-current-outgoing; Thu, 15 Oct 1998 11:08:31 -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 LAA02031
          for ; Thu, 15 Oct 1998 11:08:21 -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 TAA03736;
	Thu, 15 Oct 1998 19:08:00 +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 PAA01110;
	Thu, 15 Oct 1998 15:11:34 +0100 (BST)
	(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199810151411.PAA01110@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: bryan collins 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: /usr/sbin/arp: actual retrieval of routing table 
In-reply-to: Your message of "Thu, 15 Oct 1998 11:16:21 +1000."
             <199810150116.SAA03564@hub.freebsd.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 15:11:34 +0100
From: Brian Somers 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Hi,
> 
> I'm running FreeBSD 3.0-19980925-BETA on a P133.
> Its not doing much but monitoring the network for IP usage.
> (a few scripts to force arp requests for each IP iin a subnet)
> 
> I run a script from cron to compare the machines arp table with
> my arp database.

Sounds like you should be using the arpwatch port.

[.....]
> Thanks
> 
> Bry

-- 
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  Thu Oct 15 11:08:41 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA02106
          for freebsd-current-outgoing; Thu, 15 Oct 1998 11:08:41 -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 LAA02059
          for ; Thu, 15 Oct 1998 11:08:32 -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 TAA03739;
	Thu, 15 Oct 1998 19:08:00 +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 LAA00689;
	Thu, 15 Oct 1998 11:30:32 +0100 (BST)
	(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199810151030.LAA00689@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Terry Lambert 
cc: brian@Awfulhak.org (Brian Somers), mike@smith.net.au, rkw@Dataplex.NET,
        fjaccard@urbanet.ch, current@FreeBSD.ORG
Subject: Re: [GIMPS] /proc/net/route needed 
In-reply-to: Your message of "Thu, 15 Oct 1998 01:33:18 -0000."
             <199810150133.SAA14949@usr04.primenet.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 11:30:32 +0100
From: Brian Somers 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > And doesn't work as dial-on-demand apps will have created the 
> > necessary routing entries and UPd the interface already.
> 
> This is absolutely the wrong level at which this should be implemented.

You're assuming a one-to-one mapping from interface to transport.  

As things currently stand, ppp decides when which transports are used 
based on the contents of ppp.conf.  There's no way any other program 
can ask it ``what would happen if I gave you this packet'', as the 
decision is partially based on the current packet load.

To implement things as a firewall management daemon, the daemon would 
need to be smart enough to not only start ppp, but to instruct it on 
which link[s] to use as a transport.  The daemon would also need to 
have the facility to be told when a transport is no longer available, 
and it would have to interrogate ppp as to how much traffic has been 
sent down a given link.

Any program can configure a tun interface and multiplex the data in 
whatever way it chooses.  The best that could be done to control this 
would be to have a central ``transport policy'' file and some API for 
reading/writing how many packets have been sent over which transports.

So, for the moment, I suspect things will remain the same; the public 
interface layer will be brought up despite the lower layers not yet 
being available.  When something arrives at the higher layer, the 
dialup is performed.

[.....]
> 					Terry Lambert
> 					terry@lambert.org
> ---
> Any opinions in this posting are my own and not those of my present
> or previous employers.
> 

-- 
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  Thu Oct 15 11:23:57 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA04895
          for freebsd-current-outgoing; Thu, 15 Oct 1998 11:23:57 -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 LAA04868
          for ; Thu, 15 Oct 1998 11:23:45 -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 UAA04450;
	Thu, 15 Oct 1998 20:28:21 +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 UAA23461;
	Thu, 15 Oct 1998 20:43:11 +0200 (CEST)
Received: (from regnauld@localhost)
	by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id UAA20046;
	Thu, 15 Oct 1998 20:36:04 +0200 (CEST)
Message-ID: <19981015203604.15745@deepo.prosa.dk>
Date: Thu, 15 Oct 1998 20:36:04 +0200
From: Philippe Regnauld 
To: Luigi Rizzo 
Cc: current@FreeBSD.ORG
Subject: Re: dummynet for 3.0 (fixed)
References: <199810151314.OAA28254@labinfo.iet.unipi.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88e
In-Reply-To: <199810151314.OAA28254@labinfo.iet.unipi.it>; from Luigi Rizzo on Thu, Oct 15, 1998 at 02:14:14PM +0100
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

Luigi Rizzo writes:
> Thanks to Philippe Regnauld i have removed the hopefully last bugs from
> the 3.0 port of dummynet+bridge. Patches for a very -current system are
> at http://www.iet.unipi.it/~luigi/ip_dummynet/

	Yes, works like a charm!  Doesn't break anything!(*)  Heals your
	dog!  Tames your users!  Should be in LINT! :-P

	(didn't break anything on my sysyem with IPFIREWALL, IPDIVERT, natd,
	SOFTUPDATES, VESA, VM86).  

> This stuff will be (hopefully) on the 3.0 CD in the xperimnt/ area

	I really hope so.  It's really worth trying out!

	With a nice shell script in xperimnt for patching ? :-P

-- 
 -[ 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  Thu Oct 15 11:28:49 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA05688
          for freebsd-current-outgoing; Thu, 15 Oct 1998 11:28:49 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA05679
          for ; Thu, 15 Oct 1998 11:28:43 -0700 (PDT)
          (envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA28639; Thu, 15 Oct 1998 17:30:14 +0100
From: Luigi Rizzo 
Message-Id: <199810151630.RAA28639@labinfo.iet.unipi.it>
Subject: Re: dummynet for 3.0 (fixed)
To: regnauld@deepo.prosa.dk (Philippe Regnauld)
Date: Thu, 15 Oct 1998 17:30:14 +0100 (MET)
Cc: current@FreeBSD.ORG
In-Reply-To: <19981015203604.15745@deepo.prosa.dk> from "Philippe Regnauld" at Oct 15, 98 08:35:45 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > This stuff will be (hopefully) on the 3.0 CD in the xperimnt/ area
> 
> 	I really hope so.  It's really worth trying out!
> 
> 	With a nice shell script in xperimnt for patching ? :-P

this is your job. you are the shell script expert...

	cheers
	luigi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 11:29:14 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA05758
          for freebsd-current-outgoing; Thu, 15 Oct 1998 11:29:14 -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 LAA05735
          for ; Thu, 15 Oct 1998 11:29:10 -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 UAA27786;
	Thu, 15 Oct 1998 20:33:40 +0200 (CEST)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Thu, 15 Oct 1998 20:33:39 +0200 (CEST)
From: Andrzej Bialecki 
X-Sender: abial@korin.warman.org.pl
To: Garrett Wollman 
cc: bryan collins , freebsd-current@FreeBSD.ORG
Subject: Re: /usr/sbin/arp: actual retrieval of routing table
In-Reply-To: <199810151534.LAA16665@khavrinen.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 Thu, 15 Oct 1998, Garrett Wollman wrote:

> < said:
> 
> > Perhaps the programs which use this double sysctl(3) calls should allocate
> > somewhat bigger buffer than that calculated on basis of previous call,
> > anticipating for unexpected change in data size...
> 
> Actually, the size-estimate routines often intentionally overestimate
> for precisely this reason.

Ok, good to know this - but this didn't work in this case...

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 15 11:42:30 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA08254
          for freebsd-current-outgoing; Thu, 15 Oct 1998 11:42:30 -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 LAA08248
          for ; Thu, 15 Oct 1998 11:42:24 -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 NAA23660;
	Thu, 15 Oct 1998 13:41:51 -0500 (CDT)
	(envelope-from eculp@webwizard.org.mx)
Message-ID: <362641EE.D064078B@webwizard.org.mx>
Date: Thu, 15 Oct 1998 13:41:51 -0500
From: Edwin Culp 
X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Philippe Regnauld 
CC: Luigi Rizzo , current@FreeBSD.ORG
Subject: Re: dummynet for 3.0 (fixed)
References: <199810151314.OAA28254@labinfo.iet.unipi.it> <19981015203604.15745@deepo.prosa.dk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Philippe Regnauld wrote:

> Luigi Rizzo writes:
> > Thanks to Philippe Regnauld i have removed the hopefully last bugs from
> > the 3.0 port of dummynet+bridge. Patches for a very -current system are
> > at http://www.iet.unipi.it/~luigi/ip_dummynet/
>
>         Yes, works like a charm!  Doesn't break anything!(*)  Heals your
>         dog!  Tames your users!  Should be in LINT! :-P
>
>         (didn't break anything on my sysyem with IPFIREWALL, IPDIVERT, natd,
>         SOFTUPDATES, VESA, VM86).
>
> > This stuff will be (hopefully) on the 3.0 CD in the xperimnt/ area
>
>         I really hope so.  It's really worth trying out!
>
>         With a nice shell script in xperimnt for patching ? :-P
>
> --

I am downloading it now.  I plan to apply it tomorrow morning early, after some
of the release smoke clears:-)  I assume that it must be reapplied after each
cvsup or am I hopefully wrong?

Thanks

ed


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 11:51:23 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA09260
          for freebsd-current-outgoing; Thu, 15 Oct 1998 11:51:23 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA09251
          for ; Thu, 15 Oct 1998 11:51:20 -0700 (PDT)
          (envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA28708; Thu, 15 Oct 1998 17:52:43 +0100
From: Luigi Rizzo 
Message-Id: <199810151652.RAA28708@labinfo.iet.unipi.it>
Subject: Re: dummynet for 3.0 (fixed)
To: eculp@webwizard.org.mx (Edwin Culp)
Date: Thu, 15 Oct 1998 17:52:43 +0100 (MET)
Cc: regnauld@deepo.prosa.dk, current@FreeBSD.ORG
In-Reply-To: <362641EE.D064078B@webwizard.org.mx> from "Edwin Culp" at Oct 15, 98 01:41:32 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I am downloading it now.  I plan to apply it tomorrow morning early, after some
> of the release smoke clears:-)  I assume that it must be reapplied after each
> cvsup or am I hopefully wrong?

it will go into the std. sources after the release is done. couple of
weeks perhaps ?

	luigi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 11:54:11 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA09641
          for freebsd-current-outgoing; Thu, 15 Oct 1998 11:54:11 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from unix.tfs.net (as1-p22.tfs.net [139.146.210.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09568
          for ; Thu, 15 Oct 1998 11:53:59 -0700 (PDT)
          (envelope-from jbryant@unix.tfs.net)
Received: (from jbryant@localhost)
	by unix.tfs.net (8.9.1/8.8.5) id NAA16334;
	Thu, 15 Oct 1998 13:53:03 -0500 (CDT)
From: Jim Bryant 
Message-Id: <199810151853.NAA16334@unix.tfs.net>
Subject: Re: Limits Problems ...
In-Reply-To:  from Darin Slovitt at "Oct 15, 98 10:09:31 am"
To: darin@slovitt.net (Darin Slovitt)
Date: Thu, 15 Oct 1998 13:52:59 -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:
> I been looking through the mailing archives, but I couldn't find a direct
> answer to my problem. Perhaps someone here will be helpfull, and please
> excuse this post if I missed some obvious answer ...
> 
> I have installed a fresh copy of 3.0-19981006-BETA, and seem to have no
> end of problems with limits. When I run 'limits', I get the following
> results:
> 
> Resource limits (current):
>   cputime          infinity secs
>   filesize         infinity kb
>   datasize           524288 kb
>   stacksize           65536 kb
>   coredumpsize     infinity kb
>   memoryuse        infinity kb
>   memorylocked     infinity kb
>   maxprocesses          531
>   openfiles            1064
> 
> I have checked login.conf, and it does indeed confirm that the cputime
> limits should be set to 'infinity'.
> 
>         :cputime=unlimited:\
>         :datasize=unlimited:\
>         :stacksize=unlimited:\
>         :memorylocked=unlimited:\
>         :memoryuse=unlimited:\
>         :filesize=unlimited:\
>         :coredumpsize=unlimited:\
>         :openfiles=unlimited:\
>         :maxproc=unlimited:\
> 
> When I attempt to untar a file, I get the ever-so-annoying: 
>  Cputime limit exceeded
>  0.000u 0.000s 5:33.14 0.0%      0+0k 3594+7617io 0pf+0w
> 
> The point at which this occurs seems random at best, sometimes I almost
> make it to the end, other times only two or so files are extracted
> before it gives the above message.
> 
> What am I missing? When you 'su' to root, does it keep the limits of the
> current user, or take on the limits set for root? This machine is in a
> remote location, and I cannot compile or even untar things! Why would the
> installation default to this!?
> 
> Any help would be greatly appreciated!!

hmmmmm....

i recall writing to this list, as well as talking to principals on
#FreeBSD about the exact same thing...

I've had this ever since the beginning of summer or thereabouts when i
put -current on this toshiba 660cdt laptop.  when i reported this, all
i got were a lot of "that's what you get when you run -current"
messages, and a couple of potentially useful messages stating that it
might be caused by the apm counters.

i have heard nothing more about this, the problem has never been
fixed, and is now going into -RELEASE.

and to the jerks who gave the "that's what you get when you run
-current" answers originally, -current is also for reporting problems
such as these so they don't get into -release...

i know people have a lot to discuss, such as x and y chromosomes, and
very little time for stuff like this.

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  Thu Oct 15 12:00:05 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA10846
          for freebsd-current-outgoing; Thu, 15 Oct 1998 12:00:05 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from unix.tfs.net (as1-p22.tfs.net [139.146.210.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10756
          for ; Thu, 15 Oct 1998 11:59:54 -0700 (PDT)
          (envelope-from jbryant@unix.tfs.net)
Received: (from jbryant@localhost)
	by unix.tfs.net (8.9.1/8.8.5) id NAA16361;
	Thu, 15 Oct 1998 13:59:21 -0500 (CDT)
From: Jim Bryant 
Message-Id: <199810151859.NAA16361@unix.tfs.net>
Subject: Re: Limits Problems ...
In-Reply-To:  from Darin Slovitt at "Oct 15, 98 01:04:09 pm"
To: darin@slovitt.net (Darin Slovitt)
Date: Thu, 15 Oct 1998 13:59:20 -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:
> On Thu, 15 Oct 1998, Doug White wrote:
> 
> > This sounds like the timewarping clock bug that's been popping up on
> > systems running APM.  If you're using the APM driver try knocking it out
> > of your kernel.

been there, done that, it don't help.

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  Thu Oct 15 12:18:46 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA13122
          for freebsd-current-outgoing; Thu, 15 Oct 1998 12:18:46 -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 MAA13103
          for ; Thu, 15 Oct 1998 12:18:30 -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 OAA24005;
	Thu, 15 Oct 1998 14:17:45 -0500 (CDT)
	(envelope-from eculp@webwizard.org.mx)
Message-ID: <36264A59.C352D4C1@webwizard.org.mx>
Date: Thu, 15 Oct 1998 14:17:45 -0500
From: Edwin Culp 
X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Luigi Rizzo 
CC: regnauld@deepo.prosa.dk, current@FreeBSD.ORG
Subject: Re: dummynet for 3.0 (fixed)
References: <199810151652.RAA28708@labinfo.iet.unipi.it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Luigi Rizzo wrote:

> > I am downloading it now.  I plan to apply it tomorrow morning early, after some
> > of the release smoke clears:-)  I assume that it must be reapplied after each
> > cvsup or am I hopefully wrong?
>
> it will go into the std. sources after the release is done. couple of
> weeks perhaps ?
>
>         luigi

Hopefully, sooner:-) It's a kernel option, shouldn't be a problem.  I understand the
ipfw changes have been tested and retested.

Thanks a lot,

ed



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 12:26:09 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA14243
          for freebsd-current-outgoing; Thu, 15 Oct 1998 12:26:09 -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 MAA14236
          for ; Thu, 15 Oct 1998 12:26:07 -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 MAA00809;
	Thu, 15 Oct 1998 12:27:37 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810151927.MAA00809@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman 
cc: Greg Lehey , Julian Elischer ,
        Mike Smith ,
        "Alex G. Bulushev" ,
        Daniel Rock , current@FreeBSD.ORG
Subject: Re: -current NFS problem 
In-reply-to: Your message of "Wed, 14 Oct 1998 22:27:35 EDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 12:27:37 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I've done some NFS experimentation on my box, and basically, I try to test
> a lot of the new technologies (and older) in FreeBSD. Some of the less
> successful combos I've tried were:
> 	mount_union anything
> 	NFS mounting and beating on the FS
> 	floppies with softupdates
> 	2 vnode pan60's on 2 SoftUpdates partitions, CCD'd, and made ino a
> new fs, beat on
> 	etc.
> And beating on as defined something like:
> #!/bin/sh
> i=0
> while [ $i -le 100 ]; do
>         mkdir $i
>         cd $i
>         i=`expr $i + 1`
>         p=0
>         while [ $p -le 100 ]; do
>                 date > a$p
>                 p=`expr $p + 1`
>         done
> done
> But I fear these are just the wild experiments of a 15-year-old :-)

The "wild experiment" part is stopping here.  Now you have a big list 
of things that need to be fixed, and firsthand experience at working 
out how to identify what needs to be fixed.

In order to mature, you have to learn to fix them.  Right now you're 
blessed with being able to sleep only 3-4 hours a night, so you've got 
plenty of time to get on with it.  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  Thu Oct 15 12:42:33 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA16529
          for freebsd-current-outgoing; Thu, 15 Oct 1998 12:42:33 -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 MAA16517
          for ; Thu, 15 Oct 1998 12:42: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 MAA00931;
	Thu, 15 Oct 1998 12:46:36 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810151946.MAA00931@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Matthew N. Dodd" 
cc: current@FreeBSD.ORG
Subject: Re: kernel dependancies broken? 
In-reply-to: Your message of "Thu, 15 Oct 1998 01:03:27 EDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 12:46:36 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> Anyone seen this?
> 
> 1. edit src/sys/cam/cam_xpt.c
> 2. add a quirk entry
> 3. cd src/sys/compile/KERNEL/
> 4. 'make'
> 5. wait while most of the kernel source is rebuilt.
> 
> Note that I'm typing 'make' in a kernel compile directory that had just
> finished building a kernel.  No other files where changed.
> 
> This is really annoying as it takes 30+ minutes for a 486 to chug through
> a kernel compile that should only take about a minute for a simple 1 file
> change.

It's likely that the date on either your system or some parts of your 
kernel source tree is wrong.
-- 
\\  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 15 12:45:07 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA17399
          for freebsd-current-outgoing; Thu, 15 Oct 1998 12:45:07 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17358
          for ; Thu, 15 Oct 1998 12:45:04 -0700 (PDT)
          (envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.8.8/8.8.7) with SMTP id PAA20702;
	Thu, 15 Oct 1998 15:44:35 -0400 (EDT)
Date: Thu, 15 Oct 1998 15:44:34 -0400 (EDT)
From: "Matthew N. Dodd" 
To: Mike Smith 
cc: current@FreeBSD.ORG
Subject: Re: kernel dependancies broken? 
In-Reply-To: <199810151946.MAA00931@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 Thu, 15 Oct 1998, Mike Smith wrote:
> It's likely that the date on either your system or some parts of your 
> kernel source tree is wrong.

That was it.  Damn computer was timetraveling again.

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 12:48:48 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA18575
          for freebsd-current-outgoing; Thu, 15 Oct 1998 12:48:48 -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 MAA18567
          for ; Thu, 15 Oct 1998 12:48:44 -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 TAA00947;
	Wed, 14 Oct 1998 19:08:29 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810150208.TAA00947@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jeffrey J. Mountin" 
cc: "Jordan K. Hubbard" ,
        Karl Pielorz , current@FreeBSD.ORG
Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) 
In-reply-to: Your message of "Wed, 14 Oct 1998 20:47:17 CDT."
             <3.0.3.32.19981014204717.0107000c@207.227.119.2> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 14 Oct 1998 19:08:29 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> One wonders if Jordan has been busy on working on the bootloader issue...
> Have yet to hear more than "we should" or "we shouldn't" and kernel ELF vs
> aout (ad naseum - which certainly isn't going to happen) are getting rather
> stale.

Actually, Jordan's load is currently split between testing (where most 
of my effort right now is) and trying to have something ready for the 
Alpha at about the same time.

> Was anything definitive decided?  Or is it going to wait for the next release?

To the very best of my knowledge, it will not be sprung on the
unsuspecting 3.0 release.  Instead, it will probably be turned on as the
default a couple of weeks after the release, so that people tracking 3.0
will transition, but those using 3.0 flat will 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 15 13:05:33 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA21055
          for freebsd-current-outgoing; Thu, 15 Oct 1998 13:05:33 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m2-52-dbn.dial-up.net [196.34.155.116])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21034
          for ; Thu, 15 Oct 1998 13:05:26 -0700 (PDT)
          (envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA00555; Thu, 15 Oct 1998 21:49:10 +0200 (SAT)
From: Robert Nordier 
Message-Id: <199810151949.VAA00555@ceia.nordier.com>
Subject: Re: sysinstall build error
In-Reply-To: <199810150911.MAA25239@bsd.mbp.ee> from Lauri Laupmaa at "Oct 15, 98 12:11:41 pm"
To: mauri@mbp.ee (Lauri Laupmaa)
Date: Thu, 15 Oct 1998 21:49:09 +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

Lauri Laupmaa wrote:
> hi
> 
> it dies with:
> 
> file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp
> cannot open /boot/boot0: no such file
> *** Error code 2
> 
> where does one get this boot0 ?

(mkdir -p /boot; cd /sys/boot/i386/boot0; make all install clean)

-- 
Robert Nordier

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 13:06:09 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA21233
          for freebsd-current-outgoing; Thu, 15 Oct 1998 13:06:09 -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 NAA21227
          for ; Thu, 15 Oct 1998 13:06:07 -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 NAA01067;
	Thu, 15 Oct 1998 13:10:14 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810152010.NAA01067@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Darin Slovitt 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ... 
In-reply-to: Your message of "Thu, 15 Oct 1998 10:09:31 EDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 13:10:14 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


This is a known bug in 3.0, most commonly affecting laptop users.   We 
haven't been able to track down the exact cause of it.

> I been looking through the mailing archives, but I couldn't find a direct
> answer to my problem. Perhaps someone here will be helpfull, and please
> excuse this post if I missed some obvious answer ...
> 
> I have installed a fresh copy of 3.0-19981006-BETA, and seem to have no
> end of problems with limits. When I run 'limits', I get the following
> results:
> 
> Resource limits (current):
>   cputime          infinity secs
>   filesize         infinity kb
>   datasize           524288 kb
>   stacksize           65536 kb
>   coredumpsize     infinity kb
>   memoryuse        infinity kb
>   memorylocked     infinity kb
>   maxprocesses          531
>   openfiles            1064
> 
> I have checked login.conf, and it does indeed confirm that the cputime
> limits should be set to 'infinity'.
> 
>         :cputime=unlimited:\
>         :datasize=unlimited:\
>         :stacksize=unlimited:\
>         :memorylocked=unlimited:\
>         :memoryuse=unlimited:\
>         :filesize=unlimited:\
>         :coredumpsize=unlimited:\
>         :openfiles=unlimited:\
>         :maxproc=unlimited:\
> 
> When I attempt to untar a file, I get the ever-so-annoying: 
>  Cputime limit exceeded
>  0.000u 0.000s 5:33.14 0.0%      0+0k 3594+7617io 0pf+0w
> 
> The point at which this occurs seems random at best, sometimes I almost
> make it to the end, other times only two or so files are extracted
> before it gives the above message.
> 
> What am I missing? When you 'su' to root, does it keep the limits of the
> current user, or take on the limits set for root? This machine is in a
> remote location, and I cannot compile or even untar things! Why would the
> installation default to this!?
> 
> Any help would be greatly appreciated!!
> 
> --
> TTYS :-)
> Darin Slovitt
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
\\  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 15 13:11:31 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA21958
          for freebsd-current-outgoing; Thu, 15 Oct 1998 13:11:31 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from plethora.techv.net ([205.210.170.77])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21950
          for ; Thu, 15 Oct 1998 13:11:28 -0700 (PDT)
          (envelope-from darin@slovitt.net)
Received: from localhost (darin@localhost)
	by plethora.techv.net (8.8.8/8.8.8) with ESMTP id QAA06515;
	Thu, 15 Oct 1998 16:10:59 -0400 (EDT)
Date: Thu, 15 Oct 1998 16:10:59 -0400 (EDT)
From: Darin Slovitt 
X-Sender: darin@plethora.techv.net
To: Mike Smith 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ... 
In-Reply-To: <199810152010.NAA01067@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 Thu, 15 Oct 1998, Mike Smith wrote:

> This is a known bug in 3.0, most commonly affecting laptop users.   We 
> haven't been able to track down the exact cause of it.

It's quite interesting that something like this isn't considered a little
more important.

In my case, it's on a PII 333MHz machine. The only reason why I decided to
install current was because I had a 3COM 905B NIC, currently unsupported
via RELEASE.

Update: the problem seems to be gone ... all I did was recompile the
KERNEL using GENERIC and change absolutly nothing. Seems a little
disconserning that customizing the KERNEL actually introduces nasty 
side effects, much like this one.

Ohwell, I'll just keep using GENERIC =)

--
TTYS :-)
Darin Slovitt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 13:37:36 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA26383
          for freebsd-current-outgoing; Thu, 15 Oct 1998 13:37:36 -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 NAA26377
          for ; Thu, 15 Oct 1998 13:37:35 -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 NAA01266;
	Thu, 15 Oct 1998 13:41:10 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810152041.NAA01266@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Darin Slovitt 
cc: Mike Smith , freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ... 
In-reply-to: Your message of "Thu, 15 Oct 1998 16:10:59 EDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 13:41:10 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Thu, 15 Oct 1998, Mike Smith wrote:
> 
> > This is a known bug in 3.0, most commonly affecting laptop users.   We 
> > haven't been able to track down the exact cause of it.
> 
> It's quite interesting that something like this isn't considered a little
> more important.

It's considered *extremely* important.  If you want to complain about 
it not being fixed, please write to phk@freebsd.org, and be prepared to 
work quickly with him to see it resolved.

I've managed to narrow it down somewhat, but I haven't had the time 
(and haven't been able to regularly repeat it) to do more than that.

-- 
\\  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 15 13:44:43 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA27604
          for freebsd-current-outgoing; Thu, 15 Oct 1998 13:44:43 -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 NAA27563
          for ; Thu, 15 Oct 1998 13:44:29 -0700 (PDT)
          (envelope-from tlambert@usr02.primenet.com)
Received: (from daemon@localhost)
	by smtp01.primenet.com (8.8.8/8.8.8) id NAA22041;
	Thu, 15 Oct 1998 13:44:04 -0700 (MST)
Received: from usr02.primenet.com(206.165.6.202)
 via SMTP by smtp01.primenet.com, id smtpd021975; Thu Oct 15 13:43:57 1998
Received: (from tlambert@localhost)
	by usr02.primenet.com (8.8.5/8.8.5) id NAA23406;
	Thu, 15 Oct 1998 13:43:51 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810152043.NAA23406@usr02.primenet.com>
Subject: Re: [GIMPS] /proc/net/route needed
To: brian@Awfulhak.org (Brian Somers)
Date: Thu, 15 Oct 1998 20:43:51 +0000 (GMT)
Cc: tlambert@primenet.com, brian@Awfulhak.org, mike@smith.net.au,
        rkw@Dataplex.NET, fjaccard@urbanet.ch, current@FreeBSD.ORG
In-Reply-To: <199810151030.LAA00689@woof.lan.awfulhak.org> from "Brian Somers" at Oct 15, 98 11:30:32 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

> Any program can configure a tun interface and multiplex the data in 
> whatever way it chooses.  The best that could be done to control this 
> would be to have a central ``transport policy'' file and some API for 
> reading/writing how many packets have been sent over which transports.
> 
> So, for the moment, I suspect things will remain the same; the public 
> interface layer will be brought up despite the lower layers not yet 
> being available.  When something arrives at the higher layer, the 
> dialup is performed.

The point is to allow some programs use of the network to cause
the link to automatically come up, while other programs use of the
network will fail instead of causing the link to come up.

Basically, blocking packets from some programs, but not others,
based on administrative policy decisions.

For example, you might want to cause outbound mail to bring up a
link any time, but since you are intermittently connected to the
net, and your ISP can't bring the link up, you only want to
bring the link up to check for inbound mail when there are likely
to be people around to receive it.

As an instance of a specific policy, consider that it doesn't
matter if you dial up and ETRN the ISP every half hour all night
long, or if you ETRN them just before the normal working day
begins; either way, the mail will arrive before the humans to whom
it's addressed are available to read it, so between 6 PM and 8 AM,
all you are doing is burning money by allowing the half-hourly
cron job to actually successfully bring the link up.

In other words, a differential administrative policy based on some
definition of "work hours".

I thought of the firewall because:

o	Packets are what bring the link up
o	The firewall's job is to block packets
o	The firewall can keep the link from coming up
o	It's a nice centralized chokepoint that could be managed
	by a daemon, in the same way that bandwidth management
	works by differentially preferring protocols that have
	a high likelihood of having humans connected to the
	other end, using a single daemon to administer policy.
o	The code's already there, and can be abused to do the
	job.  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  Thu Oct 15 13:53:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA29710
          for freebsd-current-outgoing; Thu, 15 Oct 1998 13:53:59 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peotl.tuebingen.netsurf.de (host-345.tuebingen.netsurf.de [195.180.140.145])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29697
          for ; Thu, 15 Oct 1998 13:53:53 -0700 (PDT)
          (envelope-from thz@tuebingen.netsurf.de)
Received: (from thz@localhost)
	by peotl.tuebingen.netsurf.de (8.8.8/8.8.8) id WAA00248;
	Thu, 15 Oct 1998 22:40:29 +0200 (MET DST)
	(envelope-from thz)
Message-ID: <19981015224029.44241@tuebingen.netsurf.de>
Date: Thu, 15 Oct 1998 22:40:29 +0200
From: Thomas Zenker 
To: HighWind Software Information 
Cc: current@FreeBSD.ORG
Subject: Re: Recent 3.0's are Depressing
References:  <199810150215.WAA22134@highwind.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <199810150215.WAA22134@highwind.com>; from HighWind Software Information on Wed, Oct 14, 1998 at 10:15:13PM -0400
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Oct 14, 1998 at 10:15:13PM -0400, HighWind Software Information wrote:
> 
> Well... I think we have a test program that illustrates a (perhaps
> "the") bug in the new libc_r.a's. It appears that
> pthread_cond_timedwait() is now broken.
> 
> We updated our machine to the latest libc_r. Check out the following
> program.
> 
> Haven't looked at the libc_r code yet.
> 
> -Rob
> 
> ---
> 
> /*
>    Illustration of FreeBSD pthread_cond_wait() bug
>    

your test program terminates normally with an exit value of 0 after 15 secs
on a current system with kernel and world from 11. Oct cvsupped and compiled.

cheers,
Thomas

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 13:57:01 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA00328
          for freebsd-current-outgoing; Thu, 15 Oct 1998 13:57:01 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00306;
          Thu, 15 Oct 1998 13:56:53 -0700 (PDT)
          (envelope-from jabley@buddha.clear.net.nz)
Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id JAA02526; Fri, 16 Oct 1998 09:56:33 +1300 (NZDT)
Received: (from jabley@localhost)
	by buddha.clear.net.nz (8.9.1/8.9.1) id JAA25211;
	Fri, 16 Oct 1998 09:56:32 +1300 (NZDT)
Message-ID: <19981016095632.A25175@clear.co.nz>
Date: Fri, 16 Oct 1998 09:56:32 +1300
From: Joe Abley 
To: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: Luigi's Sound Drivers on Digital PC5000
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
X-Files: the Truth is Out There
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I am running FreeBSD 3.0-BETA, CVSUPped a few days ago, on a P2 Digital
PC5000 with some kind of (supposedly sb16- and wss-compatible) on-board
audio.

I have the following in my kernel config:

controller      pnp0
device          pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 vector pcmintr

I get the following on boot:

...
Probing for PnP devices:
CSN 1 Vendor ID: CSC0735 [0x3507630e] Serial 0xffffffff Comp ID: @@@0000 [0x0000
0000]
This is a CS4236, but LDN 0 is disabled
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
pcm0 not found
...

What is LDN 0? Why is it disabled?

Other than temporarily ditching fbsd and re-installing Windows 95 so that I
can find out what IRQ/DRQ is appropriate for the sound card (no!!) what could
I do to find out how the sound card in this PC should be configured?


Joe

-- 
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  Thu Oct 15 14:02:13 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA01441
          for freebsd-current-outgoing; Thu, 15 Oct 1998 14:02:13 -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 OAA01351
          for ; Thu, 15 Oct 1998 14:02:05 -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 OAA09271
	for ; Thu, 15 Oct 1998 14:02:08 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: current@FreeBSD.ORG
Subject: heads up!
Date: Thu, 15 Oct 1998 14:02:08 -0700
Message-ID: <9268.908485328@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Just a reminder:

The release tag will be going down at 20:00 PDT tonite.  I'm also
*only* going to tag the src tree; I'll leave tagging ports to the
ports team since I have no idea where they are on their own timeline
and it's not necessary for me to have ports tagged in order to start
the release process.  When Satoshi and crew are ready, I expect
they'll (well, Satoshi will) put down the ports tag.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 14:41:01 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA11857
          for freebsd-current-outgoing; Thu, 15 Oct 1998 14:41:01 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from qix (hibou.obs-besancon.fr [193.52.184.7])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11841;
          Thu, 15 Oct 1998 14:40:53 -0700 (PDT)
          (envelope-from jmz@FreeBSD.ORG)
Received: (from jmz@localhost)
	by qix (8.9.1/8.8.7) id XAA18428;
	Thu, 15 Oct 1998 23:41:31 +0200 (MET DST)
Date: Thu, 15 Oct 1998 23:41:31 +0200 (MET DST)
Message-Id: <199810152141.XAA18428@qix>
From: Jean-Marc Zucconi 
To: sos@FreeBSD.ORG
CC: current@FreeBSD.ORG
In-reply-to: <199810132117.XAA14689@sos.freebsd.dk>
Subject: Re: MFS broken on SMP ??
X-Mailer: Emacs
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> SЬren  writes:

 > I just tried using an MFS /tmp filesystem, and that breaks under a 
 > new (~2 hours ago) current with SMP. It makes various things like
 > make the compiler etc segfault pretty quickly on a make -j8 world.

 > I think I've run with a MFS /tmp before under SMP, so it might be
 > a recent breakage.....

 > Ideas? observations?

Now I notice the MFS problem even on a UP machine. I get a panic when
X starts. This is with a kernel from this morning.

Jean-Marc

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 15:03:48 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA14861
          for freebsd-current-outgoing; Thu, 15 Oct 1998 15:03:48 -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 PAA14824
          for ; Thu, 15 Oct 1998 15:03:37 -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 SAA24086;
	Thu, 15 Oct 1998 18:03:31 -0400
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: drosih@pop1.rpi.edu
Message-Id: 
In-Reply-To: 
References: <199810152010.NAA01067@dingo.cdrom.com>
Date: Thu, 15 Oct 1998 18:07:36 -0400
To: Darin Slovitt , Mike Smith 
From: Garance A Drosihn 
Subject: Re: Limits Problems ...
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 4:10 PM -0400 10/15/98, Darin Slovitt wrote:
>On Thu, 15 Oct 1998, Mike Smith wrote:
>
>> This is a known bug in 3.0, most commonly affecting laptop users.
>> We haven't been able to track down the exact cause of it.
>
> It's quite interesting that something like this isn't considered a
> little more important.

This problem is not hitting me, but even as a casual observer on this
mailing list it seems clear that several people consider this problem
very important.  The fact that it is not fixed only means that no one
has been able to pin down the problem, it does not mean that people
think the problem is unimportant.  People have been quite interested
in any information which would help pin down the problem, and have
been actively working on collecting more information.  Note that
Mike said "we haven't been ABLE to track down the exact cause", he
did *not* say "we haven't felt it was important".

Still, the parts of 3.0 which are working are also very important,
and I can understand the need to cut an official 3.0 release even
though this particular issue has not been resolved.

> Update: the problem seems to be gone ... all I did was recompile
> the KERNEL using GENERIC and change absolutly nothing. Seems a
> little disconserning that customizing the KERNEL actually
> introduces nasty side effects, much like this one.

Okay, so we now know that "something" in your custom configuration
seems to tickle the problem.  How about doing a simple diff
between the generic kernel and your customized kernel and telling
people differences you have?  That might suggest some possible
testing that you or someone else could do to narrow the problem
down further.  A simple step like this could be a very useful
contribution.

---
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  Thu Oct 15 15:17:04 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA17321
          for freebsd-current-outgoing; Thu, 15 Oct 1998 15:17:04 -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 PAA17316
          for ; Thu, 15 Oct 1998 15:17:02 -0700 (PDT)
          (envelope-from info@highwind.com)
Received: (from info@localhost)
	by highwind.com (8.8.6/8.8.6) id SAA28718;
	Thu, 15 Oct 1998 18:16:10 -0400 (EDT)
Date: Thu, 15 Oct 1998 18:16:10 -0400 (EDT)
Message-Id: <199810152216.SAA28718@highwind.com>
From: HighWind Software Information 
To: thz@tuebingen.netsurf.de
CC: current@FreeBSD.ORG
In-reply-to: <19981015224029.44241@tuebingen.netsurf.de> (message from Thomas
	Zenker on Thu, 15 Oct 1998 22:40:29 +0200)
Subject: Re: Recent 3.0's are Depressing
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>your test program terminates normally with an exit value of 0 after 15 secs
>on a current system with kernel and world from 11. Oct cvsupped and compiled.

It appears that the current libc_r has the problem I mentioned fixed.

Thanks for all the help.

-Rob

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 15:45:06 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA21479
          for freebsd-current-outgoing; Thu, 15 Oct 1998 15:45:06 -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 PAA21474
          for ; Thu, 15 Oct 1998 15:45:01 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp03.primenet.com (8.8.8/8.8.8) id PAA08202;
	Thu, 15 Oct 1998 15:44:42 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp03.primenet.com, id smtpd008088; Thu Oct 15 15:44:31 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id PAA22563;
	Thu, 15 Oct 1998 15:44:17 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810152244.PAA22563@usr04.primenet.com>
Subject: Re: -current NFS problem
To: dg@root.com
Date: Thu, 15 Oct 1998 22:44:17 +0000 (GMT)
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
In-Reply-To: <199810150258.TAA07046@implode.root.com> from "David Greenman" at Oct 14, 98 07:58:41 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

> >Well, according to Jordan's "non-verification" to my alluding that since
> >Dr. McKusick was committing NFS deltas, he was the mysterious contracted
> >NFS fixer-upper. Last time I checked, he didn't really do his entire job
> >if that was to totally fix NFS.... but hey, I don't use NFS much if ever,
> >so I won't Complain...
> 
>    Kirk was contracted to fix the problems that he could fix in a short amount
> of time. He did that and confirmed my own analysis of the remaining problems,
> which basically all stem from lack of FS node locking in the NFS code. Adding
> such locking opens a very large can of worms and everyone who has tried to
> do this has failed.

Not everyone.  Network Appliance, Sun Microsystems, USL, and SCO
have all got working NFS.  I think BSDI has working NFS as well,
including locking based one some of the stub code produced for
FreeBSD by Andrew (and by me), and I'm pretty sure the NFS code,
sans locking, worked before it left the University of Guelph.

The problems with NFS in FreeBSD are architectural problems with
FreeBSD.  Until someone starts committing fixes for the architectural
problems, you're going to continue to see their effects percolate
up to the surface in various places (like the recent complaints
by someone trying to do advisory locking on sockets; an fd is an
fd, right?  Wrong).

To put it another way, if the foundation is out of square, then
any house you build on the foundation will also be out of square.

I would like to recommend contacting John Heidemann about the
differences between his stacking vnode VFS architecture and the
implementation of that architecture in FreeBSD.  At least it
would be a starting point for addressing some of these things,
with an appeal to an authority everyone can respect instead of
a disagreement between peers.


					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  Thu Oct 15 15:58:27 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA23185
          for freebsd-current-outgoing; Thu, 15 Oct 1998 15:58:27 -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 PAA23174
          for ; Thu, 15 Oct 1998 15:58:25 -0700 (PDT)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.8/8.8.5) id RAA20521;
	Thu, 15 Oct 1998 17:56:58 -0500 (CDT)
From: Kevin Day 
Message-Id: <199810152256.RAA20521@home.dragondata.com>
Subject: Re: -current NFS problem
In-Reply-To: <199810152244.PAA22563@usr04.primenet.com> from Terry Lambert at "Oct 15, 98 10:44:17 pm"
To: tlambert@primenet.com (Terry Lambert)
Date: Thu, 15 Oct 1998 17:56:57 -0500 (CDT)
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
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

> > >Well, according to Jordan's "non-verification" to my alluding that since
> > >Dr. McKusick was committing NFS deltas, he was the mysterious contracted
> > >NFS fixer-upper. Last time I checked, he didn't really do his entire job
> > >if that was to totally fix NFS.... but hey, I don't use NFS much if ever,
> > >so I won't Complain...
> > 
> >    Kirk was contracted to fix the problems that he could fix in a short amount
> > of time. He did that and confirmed my own analysis of the remaining problems,
> > which basically all stem from lack of FS node locking in the NFS code. Adding
> > such locking opens a very large can of worms and everyone who has tried to
> > do this has failed.
> 
> Not everyone.  Network Appliance, Sun Microsystems, USL, and SCO
> have all got working NFS.  I think BSDI has working NFS as well,
> including locking based one some of the stub code produced for
> FreeBSD by Andrew (and by me), and I'm pretty sure the NFS code,
> sans locking, worked before it left the University of Guelph.
> 
> The problems with NFS in FreeBSD are architectural problems with
> FreeBSD.  Until someone starts committing fixes for the architectural
> problems, you're going to continue to see their effects percolate
> up to the surface in various places (like the recent complaints
> by someone trying to do advisory locking on sockets; an fd is an
> fd, right?  Wrong).
> 
> To put it another way, if the foundation is out of square, then
> any house you build on the foundation will also be out of square.
> 
> I would like to recommend contacting John Heidemann about the
> differences between his stacking vnode VFS architecture and the
> implementation of that architecture in FreeBSD.  At least it
> would be a starting point for addressing some of these things,
> with an appeal to an authority everyone can respect instead of
> a disagreement between peers.
> 

I don't think it's just architectural problems that people are complaining
over though.

I'd be perfectly happy to go back to 3.0 if nfs didn't cause kernel panic's.
I can deal with the limitations that freebsd's implementation has, as long
as one of those limitations isn't "Don't expect a >24 hour uptime, if
you're making heavy use of NFS."

2.2 is stablish when it comes to NFS. I get randomly corrupted files, but
it's so rare, i don't worry much about it. 3.0 causes kernel panics up the
wazoo. (nfsbioread, Bad nfs svc reply, nfs rcvunlock, bwrite: buffer is not
busy???, etc..... page fault while in kernel mode comes up often, too)


That's my only present beef when it comes to NFS.


Kevin



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 16:03:06 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA23701
          for freebsd-current-outgoing; Thu, 15 Oct 1998 16:03:06 -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 QAA23694
          for ; Thu, 15 Oct 1998 16:03:03 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp02.primenet.com (8.8.8/8.8.8) id QAA01809;
	Thu, 15 Oct 1998 16:02:44 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp02.primenet.com, id smtpd001752; Thu Oct 15 16:02:35 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id QAA23687;
	Thu, 15 Oct 1998 16:02:32 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810152302.QAA23687@usr04.primenet.com>
Subject: Re: New build problem?
To: bde@zeta.org.au (Bruce Evans)
Date: Thu, 15 Oct 1998 23:02:31 +0000 (GMT)
Cc: bruce@zuhause.mn.org, freebsd-current@FreeBSD.ORG
In-Reply-To: <199810150534.PAA05419@godzilla.zeta.org.au> from "Bruce Evans" at Oct 15, 98 03:34:03 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

> >I was looking at this further, and it looks to me like the problem is
> >that the make depend for /usr/src/lib/csu/i386 is looking for
> >the includes in /usr/obj/usr/src/tmp/usr/include instead of
> >/usr/obj/aout/usr/src/tmp/usr/include.  The reason why it got further
> >in the previous build is because I hadn't started out with a totally
> >empty /usr/obj, and I think it was finding an old param.h.
> >
> >Is this something that needs to be fixed before the release?  I
> >suspect that it may not be an issue for elf builds on an elf machine,
> >but I haven't gotten far enough to check.  I was hoping to upgrade my
> >system from source, but maybe I'll have to resort to installing the
> >3.0 release.
> 
> You apparently have a stale .depend file in the source directory.
> The `make clean' step won't remove this if an obj directory exists.
> `make clean' can be run twice to first rm -rf any obj directories
> and then to clean the source tree, but `make world' only runs it
> once since this is sufficient for files created by `make world',
> modulo bugs in (possibly previous versions of) `make world'.

How does a stale .depend file exist?

Specifically, shouldn't the .depend file depend on the Makefile?

I think anything that permits a dependent file to become desynchronized
is itself a dependent file, isn't 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  Thu Oct 15 16:22:32 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA25829
          for freebsd-current-outgoing; Thu, 15 Oct 1998 16:22:32 -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 QAA25814
          for ; Thu, 15 Oct 1998 16:22:27 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp04.primenet.com (8.8.8/8.8.8) id QAA26861;
	Thu, 15 Oct 1998 16:22:08 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp04.primenet.com, id smtpd026814; Thu Oct 15 16:22:04 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id QAA25846;
	Thu, 15 Oct 1998 16:21:51 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810152321.QAA25846@usr04.primenet.com>
Subject: Re: Recent 3.0's are Depressing
To: info@highwind.com (HighWind Software Information)
Date: Thu, 15 Oct 1998 23:21:51 +0000 (GMT)
Cc: lists@tar.com, current@FreeBSD.ORG
In-Reply-To: <199810151614.MAA25672@highwind.com> from "HighWind Software Information" at Oct 15, 98 12:14:53 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

> This makes me worry:
> 
> Both of us are on the "latest" libc_r and we see different results.
> Statically linking an old libc_r into the application didn't fix the problem.
> 
> This makes me think it isn't "libc_r".
> 
> Any of the kernel folks or more knowledgable folks get a chance to try that
> program on the latest/greatest kernel + latest/greatest libc_r?

This thread is going retrograde too fast.

We *knew* several days ago, when you told us it's a statically linked
binary that's having problems, that it wasn't libc_r changes that
were biting you because there *were no libc_r changes* (software
does not mutate, and a statically linked libc_r is invariant).

Clearly, it's a problem caused by a kernel change.

It's going to take grunt work to fix this problem; you will either
have to attack it from user space by instrumenting to identify
the broken call, or you will have to attack it from kernel space
by finding "the day the universe changed" by checking out various
dates of kernel tree, and binary searching the date space.  If it
happened in the last month, the kernel attack will take you a
maximum of 5 reboots to find the exact day, and then you can tell
us what code did the deed by:

	cd /sys
	cvs diff -D date1 -D date2 > here_it_is


Here are some guesses as to the probable identity:

Did you revert the recent vfs_bio.c change (October 15th) and see
if this fixed the problem for you?

How about if you revert the recent cleanup David Greenman did to
some of the VM code?

But they are only guesses.

Unfortunately, there too much code between your example and the
kernel for us to be able to easily tell what code path in the
kernel your code is exercising just by seeing the code, and what
system call is returning something bogus when used in exactly the
way you are using it.

It's possible to track this down, but it's going to require someone
instrumenting a local copy of libc_r for your test program or doing
a number of kernel builds and reboots, and since your system can
switch the problem on and off by selecting which kernel will be booted,
you're elected.

Once you identify the problem, I'm positive that you can blackmail
the culprit into fixing 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  Thu Oct 15 16:35:41 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA27314
          for freebsd-current-outgoing; Thu, 15 Oct 1998 16:35:41 -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 QAA27304
          for ; Thu, 15 Oct 1998 16:35:35 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp03.primenet.com (8.8.8/8.8.8) id QAA29315;
	Thu, 15 Oct 1998 16:35:13 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp03.primenet.com, id smtpd029289; Thu Oct 15 16:35:09 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id QAA26332;
	Thu, 15 Oct 1998 16:35:06 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810152335.QAA26332@usr04.primenet.com>
Subject: Re: Limits Problems ...
To: dwhite@resnet.uoregon.edu (Doug White)
Date: Thu, 15 Oct 1998 23:35:06 +0000 (GMT)
Cc: darin@slovitt.net, freebsd-current@FreeBSD.ORG
In-Reply-To:  from "Doug White" at Oct 15, 98 09:28:09 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

> > Resource limits (current):
> >   cputime          infinity secs
> 
> > I have checked login.conf, and it does indeed confirm that the cputime
> > limits should be set to 'infinity'.
> > 
> >         :cputime=unlimited:\
> 
> > When I attempt to untar a file, I get the ever-so-annoying: 
> >  Cputime limit exceeded
> >  0.000u 0.000s 5:33.14 0.0%      0+0k 3594+7617io 0pf+0w
> 
> This sounds like the timewarping clock bug that's been popping up on
> systems running APM.  If you're using the APM driver try knocking it out
> of your kernel.

Works on my box, which doesn't have APM, so it's still not APM
that's causing this problem.  APM was a guess, and the verdict is
in: the guess was wrong.


> Don't forget, when you modfiy /etc/login.conf, run cap_mkdb afterwards.

See the output of his "limit" command: he remembered.


I think he's probably upset that, no matter what the root cause of
the bug is (besides APM, I mean, since it's probably not that),
FreeBSD is claiming that some time_t minus another time_t somewhere
in the kernel has exceeded infinity.


Since that's logically impossible, the code that's enforcing the
limit by killing the process is *broken*, since it's apparently
grasping neither logic nor one of the basic tenets of number theory.


					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  Thu Oct 15 16:49:03 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA28432
          for freebsd-current-outgoing; Thu, 15 Oct 1998 16:49:03 -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 QAA28424
          for ; Thu, 15 Oct 1998 16:49:00 -0700 (PDT)
          (envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
	by cheddar.netmonger.net (8.8.8/8.8.8) id TAA17806;
	Thu, 15 Oct 1998 19:48:40 -0400 (EDT)
Message-ID: <19981015194840.A16439@netmonger.net>
Date: Thu, 15 Oct 1998 19:48:40 -0400
From: Christopher Masto 
To: freebsd-current@FreeBSD.ORG
Subject: cvsup and file permissions
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

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.

chris@cheddar:~$ ls -l /usr/cvs/freebsd/
total 4
drwxr-xr-x   5 root  cvs  1536 Oct 15 19:20 CVSROOT/
drwxr-xr-x  45 root  cvs  1024 Oct 10 22:21 ports/
drwxr-xr-x  22 root  cvs   512 Oct 15 19:20 src/

I want those to be 775, not 755.  I can change them all, but next time
I cvsup, I get a SetAttrs line for every directory, and it puts them
back.  Is there some way to avoid this?
-- 
Christopher Masto        Director of Operations  S   NetMonger Communications
chris@netmonger.net        info@netmonger.net   SSS  http://www.netmonger.net
                                                \_/
   [...] Microsoft has taken a perfectly good standard, broken it, and
   then told us that we have to buy expensive programs that support the
   broken interface rather than use the free ones that come with all
   operating systems in the world except Microsoft operating systems.
   - ALLEN HOLUB, Programmer and Columnist

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 16:50:26 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA28736
          for freebsd-current-outgoing; Thu, 15 Oct 1998 16:50:26 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28642;
          Thu, 15 Oct 1998 16:50:02 -0700 (PDT)
          (envelope-from shocking@ariadne.prth.tensor.pgs.com)
Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36])
	by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id HAA13166;
	Fri, 16 Oct 1998 07:49:38 +0800 (WST)
Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4)
	id HAA12023; Fri, 16 Oct 1998 07:49:38 +0800
Message-Id: <199810152349.HAA12023@ariadne.tensor.pgs.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: hackers@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Need working kernel threads - here why
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Oct 1998 07:49:38 +0800
From: Stephen Hocking-Senior Programmer PGS Tensor Perth 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The X inside Group have just released beta X servers that accelerate 3D 
features on some cards. This allows OpenGL stuff to run rather well. They 
state that they need a working threads implementation, and from some hints, I 
gather that user space threads aren't enough. They've  released them for SCO 
Unixware & Linux. FreeBSD is prominent by its absence.


	Stephen

PS - I intend having the /dev/3dfx driver mostly finished this weekend. I've 
had to cope with my source drive dying, and a number of emergencies at work.
-- 
  The views expressed above are not those of PGS Tensor.

    "We've heard that a million monkeys at a million keyboards could produce
     the Complete Works of Shakespeare; now, thanks to the Internet, we know
     this is not true."            Robert Wilensky, University of California



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 16:56:21 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA29499
          for freebsd-current-outgoing; Thu, 15 Oct 1998 16:56:21 -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 QAA29494
          for ; Thu, 15 Oct 1998 16:56:19 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp02.primenet.com (8.8.8/8.8.8) id QAA23117;
	Thu, 15 Oct 1998 16:56:01 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp02.primenet.com, id smtpd022983; Thu Oct 15 16:55:50 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id QAA28005;
	Thu, 15 Oct 1998 16:55:47 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810152355.QAA28005@usr04.primenet.com>
Subject: Re: Limits Problems ...
To: jbryant@unix.tfs.net
Date: Thu, 15 Oct 1998 23:55:47 +0000 (GMT)
Cc: darin@slovitt.net, freebsd-current@FreeBSD.ORG
In-Reply-To: <199810151853.NAA16334@unix.tfs.net> from "Jim Bryant" at Oct 15, 98 01:52:59 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

> I've had this ever since the beginning of summer or thereabouts when i
> put -current on this toshiba 660cdt laptop.  when i reported this, all
> i got were a lot of "that's what you get when you run -current"
> messages, and a couple of potentially useful messages stating that it
> might be caused by the apm counters.

----> IT'S NOT APM.

This happens on a box I have that wouldn't know an APM if it ran
up and bit it on the ass.  The box was designed prior to APM existing.

----> IT'S NOT A BUGGY 486 L2 CACHE.

This box doesn't *have* an L2 cache.

----> IT'S NOT A BUGGY 486 L1 CACHE.

This box's 486 stepping postdates the 486 L1 cache problems, but
to be on the safe side, I wrote the configuration register and
*turned the L1 cache off*.

THE PROBLEM DOES NOT EXIST IN 2.2.5.


> i have heard nothing more about this, the problem has never been
> fixed, and is now going into -RELEASE.
> 
> and to the jerks who gave the "that's what you get when you run
> -current" answers originally, -current is also for reporting problems
> such as these so they don't get into -release...
> 
> i know people have a lot to discuss, such as x and y chromosomes, and
> very little time for stuff like this.

The "monoclock" is going backwards.

There are quotes here, since real monoclocks, by definition, *can't*
go backwards (the "mono" stands for "monotonically increasing", and
going backwards involves *decreasing*).

I don't care if APM kicks in, and the laptop is in suspend mode
for 10 frigging *years*, the value from the monoclock at the time
the process is started can *NEVER* *NEVER* *EVER* exceed the
current monoclock time.  This is a DEFINITION.


					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  Thu Oct 15 16:58:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA29852
          for freebsd-current-outgoing; Thu, 15 Oct 1998 16:58:35 -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 QAA29843
          for ; Thu, 15 Oct 1998 16:58:31 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp01.primenet.com (8.8.8/8.8.8) id QAA12968;
	Thu, 15 Oct 1998 16:58:13 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp01.primenet.com, id smtpd012888; Thu Oct 15 16:58:04 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id QAA28284;
	Thu, 15 Oct 1998 16:58:00 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810152358.QAA28284@usr04.primenet.com>
Subject: Re: Limits Problems ...
To: mike@smith.net.au (Mike Smith)
Date: Thu, 15 Oct 1998 23:58:00 +0000 (GMT)
Cc: darin@slovitt.net, freebsd-current@FreeBSD.ORG
In-Reply-To: <199810152010.NAA01067@dingo.cdrom.com> from "Mike Smith" at Oct 15, 98 01:10:14 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

> This is a known bug in 3.0, most commonly affecting laptop users.   We 
> haven't been able to track down the exact cause of it.

I'll tell you what the cause is:

Code somewhere is either decrementing the monoclock, or is adding a
negative value to the monoclock.

Put in Bruce Evans' diagnostic code to see where.


					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  Thu Oct 15 17:05:40 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA00906
          for freebsd-current-outgoing; Thu, 15 Oct 1998 17:05:40 -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 RAA00893
          for ; Thu, 15 Oct 1998 17:05:37 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp03.primenet.com (8.8.8/8.8.8) id RAA12543;
	Thu, 15 Oct 1998 17:05:18 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp03.primenet.com, id smtpd012414; Thu Oct 15 17:05:09 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id RAA28932;
	Thu, 15 Oct 1998 17:04:51 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810160004.RAA28932@usr04.primenet.com>
Subject: Re: -current NFS problem
To: toasty@home.dragondata.com (Kevin Day)
Date: Fri, 16 Oct 1998 00:04:51 +0000 (GMT)
Cc: tlambert@primenet.com, 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
In-Reply-To: <199810152256.RAA20521@home.dragondata.com> from "Kevin Day" at Oct 15, 98 05:56: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

> I don't think it's just architectural problems that people are complaining
> over though.

Of course it's not.  People are complaining that the house is out
of square.  Very few people actually complain about architectural
problems, and the people who do tend to get yelled at.


> I'd be perfectly happy to go back to 3.0 if nfs didn't cause kernel panic's.
> I can deal with the limitations that freebsd's implementation has, as long
> as one of those limitations isn't "Don't expect a >24 hour uptime, if
> you're making heavy use of NFS."
> 
> 2.2 is stablish when it comes to NFS. I get randomly corrupted files, but
> it's so rare, i don't worry much about it.

David Greenman poseted a vnode locking patch to the -hackers list
some months ago that I believe would fix this particular problem
for you.


> 3.0 causes kernel panics up the
> wazoo. (nfsbioread, Bad nfs svc reply, nfs rcvunlock, bwrite: buffer is not
> busy???, etc..... page fault while in kernel mode comes up often, too)
> 
> That's my only present beef when it comes to NFS.

Ugh.


					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  Thu Oct 15 17:07:53 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA01255
          for freebsd-current-outgoing; Thu, 15 Oct 1998 17:07:53 -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 RAA01248
          for ; Thu, 15 Oct 1998 17:07:52 -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 RAA03004;
	Thu, 15 Oct 1998 17:07:31 -0700 (PDT)
	(envelope-from Studded@gorean.org)
Message-ID: <36268E43.1FD48575@gorean.org>
Date: Thu, 15 Oct 1998 17:07:31 -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: Christopher Masto 
CC: freebsd-current@FreeBSD.ORG
Subject: Re: cvsup and file permissions
References: <19981015194840.A16439@netmonger.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Christopher Masto wrote:

> 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.
> 
> chris@cheddar:~$ ls -l /usr/cvs/freebsd/

Guess 1 (most likely): You need to change the permissions on
/usr/cvs/freebsd to 775, and make sure it's owned by the right user and
group. 

Guess 2 (might be both): Change your umask before using cvsup to update
the tree. I had a similar problem in a different environment and just
wrote a little wrapper script to set the umask the way I wanted it and
called cvsup with arguments. If you need help with this just let me
know.

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  Thu Oct 15 17:13:56 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA01945
          for freebsd-current-outgoing; Thu, 15 Oct 1998 17:13:56 -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 RAA01938
          for ; Thu, 15 Oct 1998 17:13:52 -0700 (PDT)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id RAA03945;
	Thu, 15 Oct 1998 17:11:54 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpdZp3940; Fri Oct 16 00:11:48 1998
Date: Thu, 15 Oct 1998 17:11:44 -0700 (PDT)
From: Julian Elischer 
To: Terry Lambert 
cc: HighWind Software Information , lists@tar.com,
        current@FreeBSD.ORG
Subject: Re: Recent 3.0's are Depressing
In-Reply-To: <199810152321.QAA25846@usr04.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

Apparently the newest libc's have been fixed to cope with whatever was
changed. (or it was changed back). Latest reports have it working again.



On Thu, 15 Oct 1998, Terry Lambert wrote:

> > This makes me worry:
> > 
> > Both of us are on the "latest" libc_r and we see different results.
> > Statically linking an old libc_r into the application didn't fix the problem.
> > 
> > This makes me think it isn't "libc_r".
> > 
> > Any of the kernel folks or more knowledgable folks get a chance to try that
> > program on the latest/greatest kernel + latest/greatest libc_r?
> 
> This thread is going retrograde too fast.
> 
> We *knew* several days ago, when you told us it's a statically linked
> binary that's having problems, that it wasn't libc_r changes that
> were biting you because there *were no libc_r changes* (software
> does not mutate, and a statically linked libc_r is invariant).
> 
> Clearly, it's a problem caused by a kernel change.
> 
> It's going to take grunt work to fix this problem; you will either
> have to attack it from user space by instrumenting to identify
> the broken call, or you will have to attack it from kernel space
> by finding "the day the universe changed" by checking out various
> dates of kernel tree, and binary searching the date space.  If it
> happened in the last month, the kernel attack will take you a
> maximum of 5 reboots to find the exact day, and then you can tell
> us what code did the deed by:
> 
> 	cd /sys
> 	cvs diff -D date1 -D date2 > here_it_is
> 
> 
> Here are some guesses as to the probable identity:
> 
> Did you revert the recent vfs_bio.c change (October 15th) and see
> if this fixed the problem for you?
> 
> How about if you revert the recent cleanup David Greenman did to
> some of the VM code?
> 
> But they are only guesses.
> 
> Unfortunately, there too much code between your example and the
> kernel for us to be able to easily tell what code path in the
> kernel your code is exercising just by seeing the code, and what
> system call is returning something bogus when used in exactly the
> way you are using it.
> 
> It's possible to track this down, but it's going to require someone
> instrumenting a local copy of libc_r for your test program or doing
> a number of kernel builds and reboots, and since your system can
> switch the problem on and off by selecting which kernel will be booted,
> you're elected.
> 
> Once you identify the problem, I'm positive that you can blackmail
> the culprit into fixing 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
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 17:23:15 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA03263
          for freebsd-current-outgoing; Thu, 15 Oct 1998 17:23:15 -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 RAA03236
          for ; Thu, 15 Oct 1998 17:23:12 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp04.primenet.com (8.8.8/8.8.8) id RAA19094;
	Thu, 15 Oct 1998 17:22:54 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp04.primenet.com, id smtpd018960; Thu Oct 15 17:22:45 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id RAA29939;
	Thu, 15 Oct 1998 17:22:39 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810160022.RAA29939@usr04.primenet.com>
Subject: Re: Recent 3.0's are Depressing
To: julian@whistle.com (Julian Elischer)
Date: Fri, 16 Oct 1998 00:22:39 +0000 (GMT)
Cc: tlambert@primenet.com, info@highwind.com, lists@tar.com,
        current@FreeBSD.ORG
In-Reply-To:  from "Julian Elischer" at Oct 15, 98 05:11:44 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

> Apparently the newest libc's have been fixed to cope with whatever was
> changed. (or it was changed back). Latest reports have it working again.
>
>
> > > Both of us are on the "latest" libc_r and we see different results.
> > > Statically linking an old libc_r into the application didn't fix
> > > the problem.

This is possible.  But I am unconvinced, since the "it's working"
report was on a kernel and libc_r combination from 11 Oct 1998.

We need to get a hard date for the problem start, with kernel source
dates, before we can say the problem no longer exists.


I'm also concerned that, even if it's a libc_r/kernel mismatch,
this bodes poorly for statically linked libc_r applications, such
as the one Highwind is distributing.

It would be a bad precedent to set to not attempt to ensure binary
backward compatability because "it's just libc_r".

On the other hand, I would probably welcome such a precedent, since
it would mean that making FreeBSD's default ABI IABI compliant
would be possible, and then we could take advantage of all of the
existing Solaris x86 and UnixWare applications without having to
...uh, borrow... shared libraries off a Solaris or SCO box.


					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  Thu Oct 15 17:24:48 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA03451
          for freebsd-current-outgoing; Thu, 15 Oct 1998 17:24:48 -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 RAA03446
          for ; Thu, 15 Oct 1998 17:24:46 -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 RAA02305;
	Thu, 15 Oct 1998 17:28:51 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810160028.RAA02305@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 "Thu, 15 Oct 1998 19:48:40 EDT."
             <19981015194840.A16439@netmonger.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 17:28:51 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 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.

-- 
\\  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 15 17:36:05 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA04996
          for freebsd-current-outgoing; Thu, 15 Oct 1998 17:36:05 -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 RAA04944
          for ; Thu, 15 Oct 1998 17:35:59 -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 TAA20946; Thu, 15 Oct 1998 19:35:38 -0500 (CDT)
Received: (from bruce@localhost)
	by zuhause.mn.org (8.8.8/8.8.7) id TAA18777;
	Thu, 15 Oct 1998 19:31:16 -0500 (CDT)
From: Bruce Albrecht 
Date: Thu, 15 Oct 1998 19:31:16 -0500 (CDT)
To: Terry Lambert 
Cc: bde@zeta.org.au (Bruce Evans), bruce@zuhause.mn.org,
        freebsd-current@FreeBSD.ORG
Subject: Re: New build problem?
In-Reply-To: <199810152302.QAA23687@usr04.primenet.com>
References: <199810150534.PAA05419@godzilla.zeta.org.au>
	<199810152302.QAA23687@usr04.primenet.com>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <13862.37752.281526.741779@zuhause.zuhause.mn.org>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Terry Lambert writes:
 > How does a stale .depend file exist?
 > 
 > Specifically, shouldn't the .depend file depend on the Makefile?
 > 
 > I think anything that permits a dependent file to become desynchronized
 > is itself a dependent file, isn't it?

The odd thing was that this was the only .depend in my source tree.
After I removed it, I was able to complete the build.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 17:54:25 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA07857
          for freebsd-current-outgoing; Thu, 15 Oct 1998 17:54:25 -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 RAA07842;
          Thu, 15 Oct 1998 17:54:20 -0700 (PDT)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id RAA05104;
	Thu, 15 Oct 1998 17:49:25 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpdec5100; Fri Oct 16 00:49:20 1998
Date: Thu, 15 Oct 1998 17:49:17 -0700 (PDT)
From: Julian Elischer 
To: Stephen Hocking-Senior Programmer PGS Tensor Perth 
cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: Need working kernel threads - here why
In-Reply-To: <199810152349.HAA12023@ariadne.tensor.pgs.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

who is PGS Tensor?

are you in Perth? (my old home town?)

bumped into peter yet?

julian

(just looked at the website, where is 9320?)


On Fri, 16 Oct 1998, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:

> The X inside Group have just released beta X servers that accelerate 3D 
> features on some cards. This allows OpenGL stuff to run rather well. They 
> state that they need a working threads implementation, and from some hints, I 
> gather that user space threads aren't enough. They've  released them for SCO 
> Unixware & Linux. FreeBSD is prominent by its absence.
> 
> 
> 	Stephen
> 
> PS - I intend having the /dev/3dfx driver mostly finished this weekend. I've 
> had to cope with my source drive dying, and a number of emergencies at work.
> -- 
>   The views expressed above are not those of PGS Tensor.
> 
>     "We've heard that a million monkeys at a million keyboards could produce
>      the Complete Works of Shakespeare; now, thanks to the Internet, we know
>      this is not true."            Robert Wilensky, University of California
> 
> 
> 
> 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 15 18:42:37 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA13894
          for freebsd-current-outgoing; Thu, 15 Oct 1998 18:42:37 -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 SAA13888
          for ; Thu, 15 Oct 1998 18:42:34 -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 SAA22337;
	Thu, 15 Oct 1998 18:39:35 -0700 (PDT)
Message-Id: <199810160139.SAA22337@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 "Thu, 15 Oct 1998 22:44:17 -0000."
             <199810152244.PAA22563@usr04.primenet.com> 
From: David Greenman 
Reply-To: dg@root.com
Date: Thu, 15 Oct 1998 18:39:34 -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>    Kirk was contracted to fix the problems that he could fix in a short amount
>> of time. He did that and confirmed my own analysis of the remaining problems,
>> which basically all stem from lack of FS node locking in the NFS code. Adding
>> such locking opens a very large can of worms and everyone who has tried to
>> do this has failed.
>
>Not everyone.  Network Appliance, Sun Microsystems, USL, and SCO
>have all got working NFS.  I think BSDI has working NFS as well,
>including locking based one some of the stub code produced for
>FreeBSD by Andrew (and by me), and I'm pretty sure the NFS code,
>sans locking, worked before it left the University of Guelph.
>
>The problems with NFS in FreeBSD are architectural problems with
>FreeBSD.

   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. 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.

-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 15 18:48:55 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA14382
          for freebsd-current-outgoing; Thu, 15 Oct 1998 18:48:55 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from unix.tfs.net (as1-p93.tfs.net [139.146.210.93])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14375
          for ; Thu, 15 Oct 1998 18:48:50 -0700 (PDT)
          (envelope-from jbryant@unix.tfs.net)
Received: (from jbryant@localhost)
	by unix.tfs.net (8.9.1/8.8.5) id UAA00667;
	Thu, 15 Oct 1998 20:48:23 -0500 (CDT)
From: Jim Bryant 
Message-Id: <199810160148.UAA00667@unix.tfs.net>
Subject: Re: Limits Problems ...
In-Reply-To: <199810152335.QAA26332@usr04.primenet.com> from Terry Lambert at "Oct 15, 98 11:35:06 pm"
To: tlambert@primenet.com (Terry Lambert)
Date: Thu, 15 Oct 1998 20:48:22 -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:
> I think he's probably upset that, no matter what the root cause of
> the bug is (besides APM, I mean, since it's probably not that),
> FreeBSD is claiming that some time_t minus another time_t somewhere
> in the kernel has exceeded infinity.

actually, over here it is usually -[very large number]....  negative
number.

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  Thu Oct 15 18:56:56 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA15426
          for freebsd-current-outgoing; Thu, 15 Oct 1998 18:56:56 -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 SAA15407
          for ; Thu, 15 Oct 1998 18:56:49 -0700 (PDT)
          (envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
	by cheddar.netmonger.net (8.8.8/8.8.8) id VAA24209;
	Thu, 15 Oct 1998 21:56:30 -0400 (EDT)
Message-ID: <19981015215629.C16439@netmonger.net>
Date: Thu, 15 Oct 1998 21:56:29 -0400
From: Christopher Masto 
To: current@FreeBSD.ORG
Subject: Re: -current NFS problem
References: <19981015115155.O586@freebie.lemis.com> <6710.908424028@dstc.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <6710.908424028@dstc.edu.au>; from George Michaelson on Thu, Oct 15, 1998 at 02:00:28PM +1000
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Oct 15, 1998 at 02:00:28PM +1000, George Michaelson wrote:
> > I use NFS.  I'd really like to see it fixed.
> 
> Gee. I see history about to repeat itself. Exit stateless filesystems left
> and enter 'the Newcastle connection' stage right. Then we can argue about
> who invented the acronym DFS and why RFS failed.
[and why NFS is impossible]

I don't think the issue here is really whether fixing all of NFS is an
intractable problem.  The fact is that you can take certain other
unixes and use their NFS implementations happily, whereas adding
FreeBSD to the mix results in unhappiness.  Whether this is because of
actual bugs in the FreeBSD code, or whether it is fairy dust and
workarounds by the other guys, it implies that it should be possible
to make FreeBSD at least as reliable as, say, Solaris in the area of
NFS(v3).

I personally only use NFS occasionally, and almost exclusively
FreeBSD-FreeBSD, and then almost always just to do a "make reinstall"
somewhere, so I can't say I was even aware that we had NFS problems.
But if there are people who are working on it, I don't think they
should be encouraged to drop it because there are better network
filesystem solutions... NFS is still the thing you're most likely to
find supported elsewhere, and it can be the very lack of legacy
compatability that hinders a system's widespread adoption.

That said, I happen to have Coda on my workstation and laptop, and I
certainly hope to reap the benefits of its continued development.
-- 
Christopher Masto        Director of Operations  S   NetMonger Communications
chris@netmonger.net        info@netmonger.net   SSS  http://www.netmonger.net
                                                \_/
   It's possible, you can never know, that the universe exists only for
   me.
   - BILL GATES

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 19:17:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA18347
          for freebsd-current-outgoing; Thu, 15 Oct 1998 19:17:59 -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 TAA18342
          for ; Thu, 15 Oct 1998 19:17:57 -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 WAA11755
	for ; Thu, 15 Oct 1998 22:17:34 -0400 (EDT)
Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
	id AA03976; Thu, 15 Oct 1998 22:17:34 -0400
Received: (from jwd@localhost)
	by bb01f39.unx.sas.com (8.9.1/8.9.1) id WAA22278
	for freebsd-current@freebsd.org; Thu, 15 Oct 1998 22:17:34 -0400 (EDT)
	(envelope-from jwd)
From: "John W. DeBoskey" 
Message-Id: <199810160217.WAA22278@bb01f39.unx.sas.com>
Subject: 3.0-current 'make world' error (10pm EDT)
To: freebsd-current@FreeBSD.ORG
Date: Thu, 15 Oct 1998 22:17:34 -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,

   I have a 3.0-current system sup'd as of 10pm EDT...  Oct 15...

--------------------------------------------------------------
>>> Cleaning up the elf obj tree
--------------------------------------------------------------
.
.
.
.
===> lib/libmd
rm -f a.out md2c.o md4c.o md5c.o md2hl.o md4hl.o md5hl.o md2c.o.tmp md4c.o.tmp md5c.o.tmp md2hl.o.tmp md4hl.o.tmp md5hl.o.tmp md[245]hl.c md[245].ref md[245].3 mddriver md2.3.gz md4.3.gz md5.3.gz md2.3.cat.gz md4.3.cat.gz md5.3.cat.gz
rm -f libmd.a # llib-lmd.ln
rm -f md2c.po md4c.po md5c.po md2hl.po md4hl.po md5hl.po md2c.po.tmp md4c.po.tmp md5c.po.tmp md2hl.po.tmp md4hl.po.tmp md5hl.po.tmp libmd_p.a
rm -f md2c.so md4c.so md5c.so md2hl.so md4hl.so md5hl.so md2c.so.tmp md4c.so.tmp md5c.so.tmp md2hl.so.tmp md4hl.so.tmp md5hl.so.tmp libmd.so.* libmd_pic.a
rm -f .depend /usr/src/lib/libmd/GRTAGS /usr/src/lib/libmd/GSYMS /usr/src/lib/libmd/GTAGS
===> lib/libmytinfo
rm: /usr/obj/elf/usr/src/lib/libmytinfo: Directory not empty
*** Error code 1

Stop.



   I'll clean this by hand, but thought I'd say something just in 
case I'm not the only one seeing this....

thanks,
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 15 20:04:09 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA24600
          for freebsd-current-outgoing; Thu, 15 Oct 1998 20:04:09 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from plethora.techv.net ([205.210.170.77])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24514
          for ; Thu, 15 Oct 1998 20:04:05 -0700 (PDT)
          (envelope-from darin@slovitt.net)
Received: from localhost (darin@localhost)
	by plethora.techv.net (8.8.8/8.8.8) with ESMTP id XAA07482
	for ; Thu, 15 Oct 1998 23:03:44 -0400 (EDT)
Date: Thu, 15 Oct 1998 23:03:44 -0400 (EDT)
From: Darin Slovitt 
X-Sender: darin@plethora.techv.net
To: freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ...
Message-ID: 
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-1329008565-908507024=:7435"
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-1329008565-908507024=:7435
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

I have attached to this message two kernel config files. The GENERIC one
which I am running now (which appears to function properly), and the
kernel config that I was using which caused "cputime exceeded" messages
randomly (I noticed them when running 'tar -xvf' and when attemping to
compile perl). If it makes any difference, the tar file was close to
1.0GB.

Please note that both kernels used the EXACT same login.conf, which is
unmodified from the 3.0-19981006-BETA sources.

I am building these kernels using 3.0-19981006-BETA sources.

I'd be more then willing to aid someone who knows the FreeBSD 3.0 inners
in attempting to track this problem down. I haven't tried recently, but I
think I can faithfully reproduce the bug(s).

Thanks in advance,

--
TTYS :-)
Darin Slovitt

--0-1329008565-908507024=:7435
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=GENERIC
Content-Transfer-Encoding: BASE64
Content-ID: 
Content-Description: Generic Kernel Config
Content-Disposition: attachment; filename=GENERIC

Iw0KIyBHRU5FUklDIC0tIEdlbmVyaWMgbWFjaGluZSB3aXRoIFdEL0FIeC9O
Q1IvQlR4IGZhbWlseSBkaXNrcw0KIw0KIyBGb3IgbW9yZSBpbmZvcm1hdGlv
biByZWFkIHRoZSBoYW5kYm9vayBwYXJ0IFN5c3RlbSBBZG1pbmlzdHJhdGlv
biAtPiANCiMgQ29uZmlndXJpbmcgdGhlIEZyZWVCU0QgS2VybmVsIC0+IFRo
ZSBDb25maWd1cmF0aW9uIEZpbGUuIA0KIyBUaGUgaGFuZGJvb2sgaXMgYXZh
aWxhYmxlIGluIC91c3Ivc2hhcmUvZG9jL2hhbmRib29rIG9yIG9ubGluZSBh
cw0KIyBsYXRlc3QgdmVyc2lvbiBmcm9tIHRoZSBGcmVlQlNEIFdvcmxkIFdp
ZGUgV2ViIHNlcnZlciANCiMgPFVSTDpodHRwOi8vd3d3LkZyZWVCU0QuT1JH
Lz4NCiMNCiMgQW4gZXhoYXVzdGl2ZSBsaXN0IG9mIG9wdGlvbnMgYW5kIG1v
cmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZSANCiMgZGV2aWNlIGxp
bmVzIGlzIHByZXNlbnQgaW4gdGhlIC4vTElOVCBjb25maWd1cmF0aW9uIGZp
bGUuIElmIHlvdSBhcmUgDQojIGluIGRvdWJ0IGFzIHRvIHRoZSBwdXJwb3Nl
IG9yIG5lY2Vzc2l0eSBvZiBhIGxpbmUsIGNoZWNrIGZpcnN0IGluIExJTlQu
DQojDQojCSRJZDogR0VORVJJQyx2IDEuMTIxIDE5OTgvMTAvMDUgMDc6NDU6
NTQgb2JyaWVuIEV4cCAkDQoNCm1hY2hpbmUJCSJpMzg2Ig0KY3B1CQkiSTM4
Nl9DUFUiDQpjcHUJCSJJNDg2X0NQVSINCmNwdQkJIkk1ODZfQ1BVIg0KY3B1
CQkiSTY4Nl9DUFUiDQppZGVudAkJR0VORVJJQw0KbWF4dXNlcnMJMzINCg0K
b3B0aW9ucwkJTUFUSF9FTVVMQVRFCQkjU3VwcG9ydCBmb3IgeDg3IGVtdWxh
dGlvbg0Kb3B0aW9ucwkJSU5FVAkJCSNJbnRlck5FVHdvcmtpbmcNCm9wdGlv
bnMJCUZGUwkJCSNCZXJrZWxleSBGYXN0IEZpbGVzeXN0ZW0NCm9wdGlvbnMJ
CUZGU19ST09UCQkjRkZTIHVzYWJsZSBhcyByb290IGRldmljZSBba2VlcCB0
aGlzIV0NCm9wdGlvbnMJCU5GUwkJCSNOZXR3b3JrIEZpbGVzeXN0ZW0NCm9w
dGlvbnMJCU5GU19ST09UCQkjTkZTIHVzYWJsZSBhcyByb290IGRldmljZSwg
Ik5GUyIgcmVxJ2VkDQpvcHRpb25zCQlNU0RPU0ZTCQkJI01TRE9TIEZpbGVz
eXN0ZW0NCm9wdGlvbnMJCUNEOTY2MAkJCSNJU08gOTY2MCBGaWxlc3lzdGVt
DQpvcHRpb25zCQlDRDk2NjBfUk9PVAkJI0NELVJPTSB1c2FibGUgYXMgcm9v
dCBkZXZpY2UsICJDRDk2NjAiIHJlcSdlZA0Kb3B0aW9ucwkJUFJPQ0ZTCQkJ
I1Byb2Nlc3MgZmlsZXN5c3RlbQ0Kb3B0aW9ucwkJIkNPTVBBVF80MyIJCSND
b21wYXRpYmxlIHdpdGggQlNEIDQuMyBbS0VFUCBUSElTIV0NCm9wdGlvbnMJ
CVNDU0lfREVMQVk9MTUwMDAJI0JlIHBlc3NpbWlzdGljIGFib3V0IEpvZSBT
Q1NJIGRldmljZQ0Kb3B0aW9ucwkJVUNPTlNPTEUJCSNBbGxvdyB1c2VycyB0
byBncmFiIHRoZSBjb25zb2xlDQpvcHRpb25zCQlGQUlMU0FGRQkJI0JlIGNv
bnNlcnZhdGl2ZQ0Kb3B0aW9ucwkJVVNFUkNPTkZJRwkJI2Jvb3QgLWMgZWRp
dG9yDQpvcHRpb25zCQlWSVNVQUxfVVNFUkNPTkZJRwkjdmlzdWFsIGJvb3Qg
LWMgZWRpdG9yDQoNCmNvbmZpZwkJa2VybmVsCXJvb3Qgb24gd2QwDQoNCmNv
bnRyb2xsZXIJaXNhMA0KY29udHJvbGxlcgllaXNhMA0KY29udHJvbGxlcglw
Y2kwDQoNCmNvbnRyb2xsZXIJZmRjMAlhdCBpc2E/IHBvcnQgIklPX0ZEMSIg
YmlvIGlycSA2IGRycSAyIHZlY3RvciBmZGludHINCmRpc2sJCWZkMAlhdCBm
ZGMwIGRyaXZlIDANCmRpc2sJCWZkMQlhdCBmZGMwIGRyaXZlIDENCiMgVW5s
ZXNzIHlvdSBrbm93IHZlcnkgd2VsbCB3aGF0IHlvdSdyZSBkb2luZywgbGVh
dmUgZnQwIGF0IGRyaXZlIDIsIG9yDQojIHJlbW92ZSB0aGUgbGluZSBlbnRp
cmVseSBpZiB5b3UgZG9uJ3QgbmVlZCBpdC4gIFRyeWluZyB0byBjb25maWd1
cmUNCiMgaXQgb24gYW5vdGhlciB1bml0IG1pZ2h0IGNhdXNlIHN1cnByaXNl
cywgc2VlIFBSIGtlcm4vNzE3Ni4NCnRhcGUJCWZ0MAlhdCBmZGMwIGRyaXZl
IDINCg0Kb3B0aW9ucwkJIkNNRDY0MCIJIyB3b3JrIGFyb3VuZCBDTUQ2NDAg
Y2hpcCBkZWZpY2llbmN5DQpjb250cm9sbGVyCXdkYzAJYXQgaXNhPyBwb3J0
ICJJT19XRDEiIGJpbyBpcnEgMTQgdmVjdG9yIHdkaW50cg0KZGlzawkJd2Qw
CWF0IHdkYzAgZHJpdmUgMA0KZGlzawkJd2QxCWF0IHdkYzAgZHJpdmUgMQ0K
DQpjb250cm9sbGVyCXdkYzEJYXQgaXNhPyBwb3J0ICJJT19XRDIiIGJpbyBp
cnEgMTUgdmVjdG9yIHdkaW50cg0KZGlzawkJd2QyCWF0IHdkYzEgZHJpdmUg
MA0KZGlzawkJd2QzCWF0IHdkYzEgZHJpdmUgMQ0KDQpvcHRpb25zCQlBVEFQ
SQkJI0VuYWJsZSBBVEFQSSBzdXBwb3J0IGZvciBJREUgYnVzDQpvcHRpb25z
CQlBVEFQSV9TVEFUSUMJI0Rvbid0IGRvIGl0IGFzIGFuIExLTQ0KZGV2aWNl
CQl3Y2QwCQkjSURFIENELVJPTQ0KZGV2aWNlCQl3ZmQwCQkjSURFIEZsb3Bw
eSAoZS5nLiBMUy0xMjApDQoNCiMgQSBzaW5nbGUgZW50cnkgZm9yIGFueSBv
ZiB0aGVzZSBjb250cm9sbGVycyAobmNyLCBhaGIsIGFoYywgYW1kKSBpcw0K
IyBzdWZmaWNpZW50IGZvciBhbnkgbnVtYmVyIG9mIGluc3RhbGxlZCBkZXZp
Y2VzLg0KY29udHJvbGxlcgluY3IwDQojY29udHJvbGxlcglhbWQwDQpjb250
cm9sbGVyCWFoYjANCmNvbnRyb2xsZXIJYWhjMA0KY29udHJvbGxlcglpc3Aw
DQoNCiMgVGhpcyBjb250cm9sbGVyIG9mZmVycyBhIG51bWJlciBvZiBjb25m
aWd1cmF0aW9uIG9wdGlvbnMsIHRvbyBtYW55IHRvDQojIGRvY3VtZW50IGhl
cmUgIC0gc2VlIHRoZSBMSU5UIGZpbGUgaW4gdGhpcyBkaXJlY3RvcnkgYW5k
IGxvb2sgdXAgdGhlDQojIGRwdDAgZW50cnkgdGhlcmUgZm9yIG11Y2ggZnVs
bGVyIGRvY3VtZW50YXRpb24gb24gdGhpcy4NCmNvbnRyb2xsZXIgICAgICBk
cHQwDQoNCmNvbnRyb2xsZXIJYWR2MAlhdCBpc2E/IHBvcnQgPyBjYW0gaXJx
ID8NCmNvbnRyb2xsZXIJYnQwCWF0IGlzYT8gcG9ydCA/IGNhbSBpcnEgPw0K
Y29udHJvbGxlcglhaGEwCWF0IGlzYT8gcG9ydCA/IGNhbSBpcnEgPw0KI2Nv
bnRyb2xsZXIJdWhhMAlhdCBpc2E/IHBvcnQgIklPX1VIQTAiIGJpbyBpcnEg
PyBkcnEgNSB2ZWN0b3IgdWhhaW50cg0KI2NvbnRyb2xsZXIJYWljMAlhdCBp
c2E/IHBvcnQgMHgzNDAgYmlvIGlycSAxMSB2ZWN0b3IgYWljaW50cg0KI2Nv
bnRyb2xsZXIJbmNhMAlhdCBpc2E/IHBvcnQgMHgxZjg4IGJpbyBpcnEgMTAg
dmVjdG9yIG5jYWludHINCiNjb250cm9sbGVyCW5jYTEJYXQgaXNhPyBwb3J0
IDB4MzUwIGJpbyBpcnEgNSB2ZWN0b3IgbmNhaW50cg0KI2NvbnRyb2xsZXIJ
c2VhMAlhdCBpc2E/IGJpbyBpcnEgNSBpb21lbSAweGM4MDAwIGlvc2l6IDB4
MjAwMCB2ZWN0b3Igc2VhaW50cg0KDQpjb250cm9sbGVyCXNjYnVzMA0KDQpk
ZXZpY2UJCWRhMA0KDQpkZXZpY2UJCXNhMA0KDQpkZXZpY2UJCXBhc3MwDQoN
CmRldmljZQkJY2QwCSNPbmx5IG5lZWQgb25lIG9mIHRoZXNlLCB0aGUgY29k
ZSBkeW5hbWljYWxseSBncm93cw0KDQpkZXZpY2UJCXd0MAlhdCBpc2E/IHBv
cnQgMHgzMDAgYmlvIGlycSA1IGRycSAxIHZlY3RvciB3dGludHINCmRldmlj
ZQkJbWNkMAlhdCBpc2E/IHBvcnQgMHgzMDAgYmlvIGlycSAxMCB2ZWN0b3Ig
bWNkaW50cg0KDQpjb250cm9sbGVyCW1hdGNkMAlhdCBpc2E/IHBvcnQgMHgy
MzAgYmlvDQoNCmRldmljZQkJc2NkMAlhdCBpc2E/IHBvcnQgMHgyMzAgYmlv
DQoNCiMgc3lzY29ucyBpcyB0aGUgZGVmYXVsdCBjb25zb2xlIGRyaXZlciwg
cmVzZW1ibGluZyBhbiBTQ08gY29uc29sZQ0KZGV2aWNlCQlzYzAJYXQgaXNh
PyBwb3J0ICJJT19LQkQiIGNvbmZsaWN0cyB0dHkgaXJxIDEgdmVjdG9yIHNj
aW50cg0KIyBFbmFibGUgdGhpcyBhbmQgUENWVF9GUkVFQlNEIGZvciBwY3Z0
IHZ0MjIwIGNvbXBhdGlibGUgY29uc29sZSBkcml2ZXINCiNkZXZpY2UJCXZ0
MAlhdCBpc2E/IHBvcnQgIklPX0tCRCIgY29uZmxpY3RzIHR0eSBpcnEgMSB2
ZWN0b3IgcGNyaW50DQojb3B0aW9ucwkJWFNFUlZFUgkJCSMgc3VwcG9ydCBm
b3IgWCBzZXJ2ZXINCiNvcHRpb25zCQlGQVRfQ1VSU09SCQkjIHN0YXJ0IHdp
dGggYmxvY2sgY3Vyc29yDQojIElmIHlvdSBoYXZlIGEgVGhpbmtQQUQsIHVu
Y29tbWVudCB0aGlzIGFsb25nIHdpdGggdGhlIHJlc3Qgb2YgdGhlIFBDVlQg
bGluZXMNCiNvcHRpb25zCQlQQ1ZUX1NDQU5TRVQ9MgkJIyBJQk0ga2V5Ym9h
cmRzIGFyZSBub24tc3RkDQoNCmRldmljZQkJbnB4MAlhdCBpc2E/IHBvcnQg
IklPX05QWCIgaXJxIDEzIHZlY3RvciBucHhpbnRyDQoNCiMNCiMgTGFwdG9w
IHN1cHBvcnQgKHNlZSBMSU5UIGZvciBtb3JlIG9wdGlvbnMpDQojDQpkZXZp
Y2UJCWFwbTAgICAgYXQgaXNhPwlkaXNhYmxlCWZsYWdzIDB4MzEgIyBBZHZh
bmNlZCBQb3dlciBNYW5hZ2VtZW50DQoNCiMgUENDQVJEIChQQ01DSUEpIHN1
cHBvcnQNCiNjb250cm9sbGVyCWNhcmQwDQojZGV2aWNlCQlwY2ljMAlhdCBj
YXJkPw0KI2RldmljZQkJcGNpYzEJYXQgY2FyZD8NCg0KZGV2aWNlCQlzaW8w
CWF0IGlzYT8gcG9ydCAiSU9fQ09NMSIgZmxhZ3MgMHgxMCB0dHkgaXJxIDQg
dmVjdG9yIHNpb2ludHINCmRldmljZQkJc2lvMQlhdCBpc2E/IHBvcnQgIklP
X0NPTTIiIHR0eSBpcnEgMyB2ZWN0b3Igc2lvaW50cg0KZGV2aWNlCQlzaW8y
CWF0IGlzYT8gZGlzYWJsZSBwb3J0ICJJT19DT00zIiB0dHkgaXJxIDUgdmVj
dG9yIHNpb2ludHINCmRldmljZQkJc2lvMwlhdCBpc2E/IGRpc2FibGUgcG9y
dCAiSU9fQ09NNCIgdHR5IGlycSA5IHZlY3RvciBzaW9pbnRyDQoNCmRldmlj
ZQkJbHB0MAlhdCBpc2E/IHBvcnQ/IHR0eSBpcnEgNyB2ZWN0b3IgbHB0aW50
cg0KDQpkZXZpY2UJCXBzbTAJYXQgaXNhPyBwb3J0ICJJT19LQkQiIGNvbmZs
aWN0cyB0dHkgaXJxIDEyIHZlY3RvciBwc21pbnRyDQoNCiMgT3JkZXIgaXMg
aW1wb3J0YW50IGhlcmUgZHVlIHRvIGludHJ1c2l2ZSBwcm9iZXMsIGRvICpu
b3QqIGFscGhhYmV0aXplDQojIHRoaXMgbGlzdCBvZiBuZXR3b3JrIGludGVy
ZmFjZXMgdW50aWwgdGhlIHByb2JlcyBoYXZlIGJlZW4gZml4ZWQuDQojIFJp
Z2h0IG5vdyBpdCBhcHBlYXJzIHRoYXQgdGhlIGllMCBtdXN0IGJlIHByb2Jl
ZCBiZWZvcmUgZXAwLiBTZWUNCiMgcmV2aXNpb24gMS4yMCBvZiB0aGlzIGZp
bGUuDQpkZXZpY2UgZGUwDQpkZXZpY2UgZnhwMA0KZGV2aWNlIHRsMA0KZGV2
aWNlIHR4MA0KZGV2aWNlIHZ4MA0KZGV2aWNlIHhsMA0KDQpkZXZpY2UgZWQw
IGF0IGlzYT8gcG9ydCAweDI4MCBuZXQgaXJxIDEwIGlvbWVtIDB4ZDgwMDAg
dmVjdG9yIGVkaW50cg0KZGV2aWNlIGllMCBhdCBpc2E/IHBvcnQgMHgzMDAg
bmV0IGlycSAxMCBpb21lbSAweGQwMDAwIHZlY3RvciBpZWludHINCmRldmlj
ZSBlcDAgYXQgaXNhPyBwb3J0IDB4MzAwIG5ldCBpcnEgMTAgdmVjdG9yIGVw
aW50cg0KZGV2aWNlIGV4MCBhdCBpc2E/IHBvcnQ/IG5ldCBpcnE/IHZlY3Rv
ciBleGludHINCmRldmljZSBmZTAgYXQgaXNhPyBwb3J0IDB4MzAwIG5ldCBp
cnEgPyB2ZWN0b3IgZmVpbnRyDQpkZXZpY2UgbGUwIGF0IGlzYT8gcG9ydCAw
eDMwMCBuZXQgaXJxIDUgaW9tZW0gMHhkMDAwMCB2ZWN0b3IgbGVfaW50cg0K
ZGV2aWNlIGxuYzAgYXQgaXNhPyBwb3J0IDB4MjgwIG5ldCBpcnEgMTAgZHJx
IDAgdmVjdG9yIGxuY2ludHINCmRldmljZSB6ZTAgYXQgaXNhPyBwb3J0IDB4
MzAwIG5ldCBpcnEgMTAgaW9tZW0gMHhkODAwMCB2ZWN0b3IgemVpbnRyDQpk
ZXZpY2UgenAwIGF0IGlzYT8gcG9ydCAweDMwMCBuZXQgaXJxIDEwIGlvbWVt
IDB4ZDgwMDAgdmVjdG9yIHpwaW50cg0KZGV2aWNlIGNzMCBhdCBpc2E/IHBv
cnQgMHgzMDAgbmV0IGlycSA/IHZlY3RvciBjc2ludHINCg0KcHNldWRvLWRl
dmljZQlsb29wDQpwc2V1ZG8tZGV2aWNlCWV0aGVyDQpwc2V1ZG8tZGV2aWNl
CXNsCTENCnBzZXVkby1kZXZpY2UJcHBwCTENCnBzZXVkby1kZXZpY2UJdHVu
CTENCnBzZXVkby1kZXZpY2UJcHR5CTE2DQpwc2V1ZG8tZGV2aWNlCWd6aXAJ
CSMgRXhlYyBnemlwcGVkIGEub3V0J3MNCg0KIyBLVFJBQ0UgZW5hYmxlcyB0
aGUgc3lzdGVtLWNhbGwgdHJhY2luZyBmYWNpbGl0eSBrdHJhY2UoMikuDQoj
IFRoaXMgYWRkcyA0IEtCIGJsb2F0IHRvIHlvdXIga2VybmVsLCBhbmQgc2xp
Z2h0bHkgaW5jcmVhc2VzDQojIHRoZSBjb3N0cyBvZiBlYWNoIHN5c2NhbGwu
DQpvcHRpb25zCQlLVFJBQ0UJCSNrZXJuZWwgdHJhY2luZw0KDQojIFRoaXMg
cHJvdmlkZXMgc3VwcG9ydCBmb3IgU3lzdGVtIFYgc2hhcmVkIG1lbW9yeS4N
CiMNCm9wdGlvbnMJCVNZU1ZTSE0NCg==
--0-1329008565-908507024=:7435
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=BUSTED
Content-Transfer-Encoding: BASE64
Content-ID: 
Content-Description: Broken Kernel Config
Content-Disposition: attachment; filename=BUSTED

Iw0KIyBHRU5FUklDIC0tIEdlbmVyaWMgbWFjaGluZSB3aXRoIFdEL0FIeC9O
Q1IvQlR4IGZhbWlseSBkaXNrcw0KIw0KIyBGb3IgbW9yZSBpbmZvcm1hdGlv
biByZWFkIHRoZSBoYW5kYm9vayBwYXJ0IFN5c3RlbSBBZG1pbmlzdHJhdGlv
biAtPiANCiMgQ29uZmlndXJpbmcgdGhlIEZyZWVCU0QgS2VybmVsIC0+IFRo
ZSBDb25maWd1cmF0aW9uIEZpbGUuIA0KIyBUaGUgaGFuZGJvb2sgaXMgYXZh
aWxhYmxlIGluIC91c3Ivc2hhcmUvZG9jL2hhbmRib29rIG9yIG9ubGluZSBh
cw0KIyBsYXRlc3QgdmVyc2lvbiBmcm9tIHRoZSBGcmVlQlNEIFdvcmxkIFdp
ZGUgV2ViIHNlcnZlciANCiMgPFVSTDpodHRwOi8vd3d3LkZyZWVCU0QuT1JH
Lz4NCiMNCiMgQW4gZXhoYXVzdGl2ZSBsaXN0IG9mIG9wdGlvbnMgYW5kIG1v
cmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZSANCiMgZGV2aWNlIGxp
bmVzIGlzIHByZXNlbnQgaW4gdGhlIC4vTElOVCBjb25maWd1cmF0aW9uIGZp
bGUuIElmIHlvdSBhcmUgDQojIGluIGRvdWJ0IGFzIHRvIHRoZSBwdXJwb3Nl
IG9yIG5lY2Vzc2l0eSBvZiBhIGxpbmUsIGNoZWNrIGZpcnN0IGluIExJTlQu
DQojDQojCSRJZDogR0VORVJJQyx2IDEuMTIxIDE5OTgvMTAvMDUgMDc6NDU6
NTQgb2JyaWVuIEV4cCAkDQoNCm1hY2hpbmUJCSJpMzg2Ig0KY3B1CQkiSTM4
Nl9DUFUiDQpjcHUJCSJJNDg2X0NQVSINCmNwdQkJIkk1ODZfQ1BVIg0KY3B1
CQkiSTY4Nl9DUFUiDQppZGVudAkJR0VORVJJQw0KbWF4dXNlcnMJMzINCg0K
b3B0aW9ucwkJTUFUSF9FTVVMQVRFCQkjU3VwcG9ydCBmb3IgeDg3IGVtdWxh
dGlvbg0Kb3B0aW9ucwkJSU5FVAkJCSNJbnRlck5FVHdvcmtpbmcNCm9wdGlv
bnMJCUZGUwkJCSNCZXJrZWxleSBGYXN0IEZpbGVzeXN0ZW0NCm9wdGlvbnMJ
CUZGU19ST09UCQkjRkZTIHVzYWJsZSBhcyByb290IGRldmljZSBba2VlcCB0
aGlzIV0NCm9wdGlvbnMJCU5GUwkJCSNOZXR3b3JrIEZpbGVzeXN0ZW0NCm9w
dGlvbnMJCU5GU19ST09UDQpvcHRpb25zCQlNU0RPU0ZTDQojb3B0aW9ucwkJ
Q0Q5NjYwDQojb3B0aW9ucwkJQ0Q5NjYwX1JPT1QNCm9wdGlvbnMJCVBST0NG
UwkJCSNQcm9jZXNzIGZpbGVzeXN0ZW0NCm9wdGlvbnMJCSJDT01QQVRfNDMi
CQkjQ29tcGF0aWJsZSB3aXRoIEJTRCA0LjMgW0tFRVAgVEhJUyFdDQpvcHRp
b25zCQlTQ1NJX0RFTEFZPTE1MDAwCSNCZSBwZXNzaW1pc3RpYyBhYm91dCBK
b2UgU0NTSSBkZXZpY2UNCm9wdGlvbnMJCVVDT05TT0xFCQkjQWxsb3cgdXNl
cnMgdG8gZ3JhYiB0aGUgY29uc29sZQ0Kb3B0aW9ucwkJRkFJTFNBRkUJCSNC
ZSBjb25zZXJ2YXRpdmUNCm9wdGlvbnMJCVVTRVJDT05GSUcJCSNib290IC1j
IGVkaXRvcg0Kb3B0aW9ucwkJVklTVUFMX1VTRVJDT05GSUcJI3Zpc3VhbCBi
b290IC1jIGVkaXRvcg0KDQpjb25maWcJCWtlcm5lbAlyb290IG9uIHdkMA0K
DQpjb250cm9sbGVyCWlzYTANCmNvbnRyb2xsZXIJZWlzYTANCmNvbnRyb2xs
ZXIJcGNpMA0KDQpjb250cm9sbGVyCWZkYzAJYXQgaXNhPyBwb3J0ICJJT19G
RDEiIGJpbyBpcnEgNiBkcnEgMiB2ZWN0b3IgZmRpbnRyDQpkaXNrCQlmZDAJ
YXQgZmRjMCBkcml2ZSAwDQpkaXNrCQlmZDEJYXQgZmRjMCBkcml2ZSAxDQoj
IFVubGVzcyB5b3Uga25vdyB2ZXJ5IHdlbGwgd2hhdCB5b3UncmUgZG9pbmcs
IGxlYXZlIGZ0MCBhdCBkcml2ZSAyLCBvcg0KIyByZW1vdmUgdGhlIGxpbmUg
ZW50aXJlbHkgaWYgeW91IGRvbid0IG5lZWQgaXQuICBUcnlpbmcgdG8gY29u
ZmlndXJlDQojIGl0IG9uIGFub3RoZXIgdW5pdCBtaWdodCBjYXVzZSBzdXJw
cmlzZXMsIHNlZSBQUiBrZXJuLzcxNzYuDQp0YXBlCQlmdDAJYXQgZmRjMCBk
cml2ZSAyDQoNCm9wdGlvbnMJCSJDTUQ2NDAiCSMgd29yayBhcm91bmQgQ01E
NjQwIGNoaXAgZGVmaWNpZW5jeQ0KY29udHJvbGxlcgl3ZGMwCWF0IGlzYT8g
cG9ydCAiSU9fV0QxIiBiaW8gaXJxIDE0IHZlY3RvciB3ZGludHINCmRpc2sJ
CXdkMAlhdCB3ZGMwIGRyaXZlIDANCmRpc2sJCXdkMQlhdCB3ZGMwIGRyaXZl
IDENCg0KY29udHJvbGxlcgl3ZGMxCWF0IGlzYT8gcG9ydCAiSU9fV0QyIiBi
aW8gaXJxIDE1IHZlY3RvciB3ZGludHINCmRpc2sJCXdkMglhdCB3ZGMxIGRy
aXZlIDANCmRpc2sJCXdkMwlhdCB3ZGMxIGRyaXZlIDENCg0Kb3B0aW9ucwkJ
QVRBUEkJCSNFbmFibGUgQVRBUEkgc3VwcG9ydCBmb3IgSURFIGJ1cw0Kb3B0
aW9ucwkJQVRBUElfU1RBVElDCSNEb24ndCBkbyBpdCBhcyBhbiBMS00NCmRl
dmljZQkJd2NkMAkJI0lERSBDRC1ST00NCmRldmljZQkJd2ZkMAkJI0lERSBG
bG9wcHkgKGUuZy4gTFMtMTIwKQ0KDQojIEEgc2luZ2xlIGVudHJ5IGZvciBh
bnkgb2YgdGhlc2UgY29udHJvbGxlcnMgKG5jciwgYWhiLCBhaGMsIGFtZCkg
aXMNCiMgc3VmZmljaWVudCBmb3IgYW55IG51bWJlciBvZiBpbnN0YWxsZWQg
ZGV2aWNlcy4NCmNvbnRyb2xsZXIJbmNyMA0KI2NvbnRyb2xsZXIJYW1kMA0K
Y29udHJvbGxlcglhaGIwDQpjb250cm9sbGVyCWFoYzANCmNvbnRyb2xsZXIJ
aXNwMA0KDQojIFRoaXMgY29udHJvbGxlciBvZmZlcnMgYSBudW1iZXIgb2Yg
Y29uZmlndXJhdGlvbiBvcHRpb25zLCB0b28gbWFueSB0bw0KIyBkb2N1bWVu
dCBoZXJlICAtIHNlZSB0aGUgTElOVCBmaWxlIGluIHRoaXMgZGlyZWN0b3J5
IGFuZCBsb29rIHVwIHRoZQ0KIyBkcHQwIGVudHJ5IHRoZXJlIGZvciBtdWNo
IGZ1bGxlciBkb2N1bWVudGF0aW9uIG9uIHRoaXMuDQpjb250cm9sbGVyICAg
ICAgZHB0MA0KDQpjb250cm9sbGVyCWFkdjAJYXQgaXNhPyBwb3J0ID8gY2Ft
IGlycSA/DQpjb250cm9sbGVyCWJ0MAlhdCBpc2E/IHBvcnQgPyBjYW0gaXJx
ID8NCmNvbnRyb2xsZXIJYWhhMAlhdCBpc2E/IHBvcnQgPyBjYW0gaXJxID8N
CiNjb250cm9sbGVyCXVoYTAJYXQgaXNhPyBwb3J0ICJJT19VSEEwIiBiaW8g
aXJxID8gZHJxIDUgdmVjdG9yIHVoYWludHINCiNjb250cm9sbGVyCWFpYzAJ
YXQgaXNhPyBwb3J0IDB4MzQwIGJpbyBpcnEgMTEgdmVjdG9yIGFpY2ludHIN
CiNjb250cm9sbGVyCW5jYTAJYXQgaXNhPyBwb3J0IDB4MWY4OCBiaW8gaXJx
IDEwIHZlY3RvciBuY2FpbnRyDQojY29udHJvbGxlcgluY2ExCWF0IGlzYT8g
cG9ydCAweDM1MCBiaW8gaXJxIDUgdmVjdG9yIG5jYWludHINCiNjb250cm9s
bGVyCXNlYTAJYXQgaXNhPyBiaW8gaXJxIDUgaW9tZW0gMHhjODAwMCBpb3Np
eiAweDIwMDAgdmVjdG9yIHNlYWludHINCg0KY29udHJvbGxlcglzY2J1czAN
Cg0KZGV2aWNlCQlkYTANCg0KZGV2aWNlCQlzYTANCg0KZGV2aWNlCQlwYXNz
MA0KDQpkZXZpY2UJCWNkMAkjT25seSBuZWVkIG9uZSBvZiB0aGVzZSwgdGhl
IGNvZGUgZHluYW1pY2FsbHkgZ3Jvd3MNCg0KZGV2aWNlCQl3dDAJYXQgaXNh
PyBwb3J0IDB4MzAwIGJpbyBpcnEgNSBkcnEgMSB2ZWN0b3Igd3RpbnRyDQpk
ZXZpY2UJCW1jZDAJYXQgaXNhPyBwb3J0IDB4MzAwIGJpbyBpcnEgMTAgdmVj
dG9yIG1jZGludHINCg0KY29udHJvbGxlcgltYXRjZDAJYXQgaXNhPyBwb3J0
IDB4MjMwIGJpbw0KDQpkZXZpY2UJCXNjZDAJYXQgaXNhPyBwb3J0IDB4MjMw
IGJpbw0KDQojIHN5c2NvbnMgaXMgdGhlIGRlZmF1bHQgY29uc29sZSBkcml2
ZXIsIHJlc2VtYmxpbmcgYW4gU0NPIGNvbnNvbGUNCmRldmljZQkJc2MwCWF0
IGlzYT8gcG9ydCAiSU9fS0JEIiBjb25mbGljdHMgdHR5IGlycSAxIHZlY3Rv
ciBzY2ludHINCiMgRW5hYmxlIHRoaXMgYW5kIFBDVlRfRlJFRUJTRCBmb3Ig
cGN2dCB2dDIyMCBjb21wYXRpYmxlIGNvbnNvbGUgZHJpdmVyDQojZGV2aWNl
CQl2dDAJYXQgaXNhPyBwb3J0ICJJT19LQkQiIGNvbmZsaWN0cyB0dHkgaXJx
IDEgdmVjdG9yIHBjcmludA0KI29wdGlvbnMJCVhTRVJWRVIJCQkjIHN1cHBv
cnQgZm9yIFggc2VydmVyDQojb3B0aW9ucwkJRkFUX0NVUlNPUgkJIyBzdGFy
dCB3aXRoIGJsb2NrIGN1cnNvcg0KIyBJZiB5b3UgaGF2ZSBhIFRoaW5rUEFE
LCB1bmNvbW1lbnQgdGhpcyBhbG9uZyB3aXRoIHRoZSByZXN0IG9mIHRoZSBQ
Q1ZUIGxpbmVzDQojb3B0aW9ucwkJUENWVF9TQ0FOU0VUPTIJCSMgSUJNIGtl
eWJvYXJkcyBhcmUgbm9uLXN0ZA0KDQpkZXZpY2UJCW5weDAJYXQgaXNhPyBw
b3J0ICJJT19OUFgiIGlycSAxMyB2ZWN0b3IgbnB4aW50cg0KDQojDQojIExh
cHRvcCBzdXBwb3J0IChzZWUgTElOVCBmb3IgbW9yZSBvcHRpb25zKQ0KIw0K
ZGV2aWNlCQlhcG0wICAgIGF0IGlzYT8JZGlzYWJsZQlmbGFncyAweDMxICMg
QWR2YW5jZWQgUG93ZXIgTWFuYWdlbWVudA0KDQojIFBDQ0FSRCAoUENNQ0lB
KSBzdXBwb3J0DQojY29udHJvbGxlcgljYXJkMA0KI2RldmljZQkJcGNpYzAJ
YXQgY2FyZD8NCiNkZXZpY2UJCXBjaWMxCWF0IGNhcmQ/DQoNCmRldmljZQkJ
c2lvMAlhdCBpc2E/IHBvcnQgIklPX0NPTTEiIGZsYWdzIDB4MTAgdHR5IGly
cSA0IHZlY3RvciBzaW9pbnRyDQpkZXZpY2UJCXNpbzEJYXQgaXNhPyBwb3J0
ICJJT19DT00yIiB0dHkgaXJxIDMgdmVjdG9yIHNpb2ludHINCmRldmljZQkJ
c2lvMglhdCBpc2E/IGRpc2FibGUgcG9ydCAiSU9fQ09NMyIgdHR5IGlycSA1
IHZlY3RvciBzaW9pbnRyDQpkZXZpY2UJCXNpbzMJYXQgaXNhPyBkaXNhYmxl
IHBvcnQgIklPX0NPTTQiIHR0eSBpcnEgOSB2ZWN0b3Igc2lvaW50cg0KDQpk
ZXZpY2UJCWxwdDAJYXQgaXNhPyBwb3J0PyB0dHkgaXJxIDcgdmVjdG9yIGxw
dGludHINCg0KZGV2aWNlCQlwc20wCWF0IGlzYT8gcG9ydCAiSU9fS0JEIiBj
b25mbGljdHMgdHR5IGlycSAxMiB2ZWN0b3IgcHNtaW50cg0KDQojIE9yZGVy
IGlzIGltcG9ydGFudCBoZXJlIGR1ZSB0byBpbnRydXNpdmUgcHJvYmVzLCBk
byAqbm90KiBhbHBoYWJldGl6ZQ0KIyB0aGlzIGxpc3Qgb2YgbmV0d29yayBp
bnRlcmZhY2VzIHVudGlsIHRoZSBwcm9iZXMgaGF2ZSBiZWVuIGZpeGVkLg0K
IyBSaWdodCBub3cgaXQgYXBwZWFycyB0aGF0IHRoZSBpZTAgbXVzdCBiZSBw
cm9iZWQgYmVmb3JlIGVwMC4gU2VlDQojIHJldmlzaW9uIDEuMjAgb2YgdGhp
cyBmaWxlLg0KZGV2aWNlIGRlMA0KZGV2aWNlIGZ4cDANCmRldmljZSB0bDAN
CmRldmljZSB0eDANCmRldmljZSB2eDANCmRldmljZSB4bDANCg0KZGV2aWNl
IGVkMCBhdCBpc2E/IHBvcnQgMHgyODAgbmV0IGlycSAxMCBpb21lbSAweGQ4
MDAwIHZlY3RvciBlZGludHINCmRldmljZSBpZTAgYXQgaXNhPyBwb3J0IDB4
MzAwIG5ldCBpcnEgMTAgaW9tZW0gMHhkMDAwMCB2ZWN0b3IgaWVpbnRyDQpk
ZXZpY2UgZXAwIGF0IGlzYT8gcG9ydCAweDMwMCBuZXQgaXJxIDEwIHZlY3Rv
ciBlcGludHINCmRldmljZSBleDAgYXQgaXNhPyBwb3J0PyBuZXQgaXJxPyB2
ZWN0b3IgZXhpbnRyDQpkZXZpY2UgZmUwIGF0IGlzYT8gcG9ydCAweDMwMCBu
ZXQgaXJxID8gdmVjdG9yIGZlaW50cg0KZGV2aWNlIGxlMCBhdCBpc2E/IHBv
cnQgMHgzMDAgbmV0IGlycSA1IGlvbWVtIDB4ZDAwMDAgdmVjdG9yIGxlX2lu
dHINCmRldmljZSBsbmMwIGF0IGlzYT8gcG9ydCAweDI4MCBuZXQgaXJxIDEw
IGRycSAwIHZlY3RvciBsbmNpbnRyDQpkZXZpY2UgemUwIGF0IGlzYT8gcG9y
dCAweDMwMCBuZXQgaXJxIDEwIGlvbWVtIDB4ZDgwMDAgdmVjdG9yIHplaW50
cg0KZGV2aWNlIHpwMCBhdCBpc2E/IHBvcnQgMHgzMDAgbmV0IGlycSAxMCBp
b21lbSAweGQ4MDAwIHZlY3RvciB6cGludHINCmRldmljZSBjczAgYXQgaXNh
PyBwb3J0IDB4MzAwIG5ldCBpcnEgPyB2ZWN0b3IgY3NpbnRyDQoNCnBzZXVk
by1kZXZpY2UJbG9vcA0KcHNldWRvLWRldmljZQlldGhlcg0KcHNldWRvLWRl
dmljZQlzbAkxDQpwc2V1ZG8tZGV2aWNlCXBwcAkxDQpwc2V1ZG8tZGV2aWNl
CXR1bgkxDQpwc2V1ZG8tZGV2aWNlCXB0eQkxNg0KcHNldWRvLWRldmljZQln
emlwCQkjIEV4ZWMgZ3ppcHBlZCBhLm91dCdzDQoNCiMgS1RSQUNFIGVuYWJs
ZXMgdGhlIHN5c3RlbS1jYWxsIHRyYWNpbmcgZmFjaWxpdHkga3RyYWNlKDIp
Lg0KIyBUaGlzIGFkZHMgNCBLQiBibG9hdCB0byB5b3VyIGtlcm5lbCwgYW5k
IHNsaWdodGx5IGluY3JlYXNlcw0KIyB0aGUgY29zdHMgb2YgZWFjaCBzeXNj
YWxsLg0Kb3B0aW9ucwkJS1RSQUNFCQkja2VybmVsIHRyYWNpbmcNCg0KIyBU
aGlzIHByb3ZpZGVzIHN1cHBvcnQgZm9yIFN5c3RlbSBWIHNoYXJlZCBtZW1v
cnkuDQojDQpvcHRpb25zCQlTWVNWU0hNDQo=
--0-1329008565-908507024=:7435--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 21:12:52 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA03587
          for freebsd-current-outgoing; Thu, 15 Oct 1998 21:12:52 -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 VAA03582
          for ; Thu, 15 Oct 1998 21:12:49 -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 VAA08948;
	Thu, 15 Oct 1998 21:12:27 -0700 (PDT)
	(envelope-from jdp)
Message-Id: <199810160412.VAA08948@austin.polstra.com>
To: chris@netmonger.net
Subject: Re: cvsup and file permissions
In-Reply-To: <19981015194840.A16439@netmonger.net>
References: <19981015194840.A16439@netmonger.net>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Date: Thu, 15 Oct 1998 21:12:27 -0700
From: John Polstra 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <19981015194840.A16439@netmonger.net>,
Christopher Masto   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.
> 
> chris@cheddar:~$ ls -l /usr/cvs/freebsd/
> total 4
> drwxr-xr-x   5 root  cvs  1536 Oct 15 19:20 CVSROOT/
> drwxr-xr-x  45 root  cvs  1024 Oct 10 22:21 ports/
> drwxr-xr-x  22 root  cvs   512 Oct 15 19:20 src/
> 
> I want those to be 775, not 755.  I can change them all, but next time
> I cvsup, I get a SetAttrs line for every directory, and it puts them
> back.  Is there some way to avoid this?

I think the problem may be that you're running cvsup with a umask of
22.  Make sure the umask allows the file modes that you want.  I.e.,
try a umask of 2.  To be sure of that, it might pay off to write a
little shell script for running cvsup.  (Yes, I know, it should be an
option in the CVSupfile.  Some day ...)

John
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 21:21:17 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA04960
          for freebsd-current-outgoing; Thu, 15 Oct 1998 21:21:17 -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 VAA04954
          for ; Thu, 15 Oct 1998 21:21:16 -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 VAA08999
	for ; Thu, 15 Oct 1998 21:20:58 -0700 (PDT)
	(envelope-from jdp)
Message-Id: <199810160420.VAA08999@austin.polstra.com>
To: current@FreeBSD.ORG
Subject: Re: Limits Problems ... 
In-Reply-To: 
References: 
Organization: Polstra & Co., Seattle, WA
Date: Thu, 15 Oct 1998 21:20:58 -0700
From: John Polstra 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article ,
Darin Slovitt   wrote:
> On Thu, 15 Oct 1998, Mike Smith wrote:
> 
> > This is a known bug in 3.0, most commonly affecting laptop users.   We 
> > haven't been able to track down the exact cause of it.
> 
> It's quite interesting that something like this isn't considered a little
> more important.

The most accurate indicator of how important a problem is to a person
is the number of hours he has spent working on diagnosing it and
fixing it.  Under that metric, how important is it to YOU?
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 21:21:45 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA05017
          for freebsd-current-outgoing; Thu, 15 Oct 1998 21:21:45 -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 VAA05012
          for ; Thu, 15 Oct 1998 21:21:40 -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 AAA10972
	for ; Fri, 16 Oct 1998 00:21:24 -0400 (EDT)
Date: Fri, 16 Oct 1998 00:21:23 -0400 (EDT)
From: Brian Feldman 
To: current@FreeBSD.ORG
Subject: MFS LKM for 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

Perhaps this is a little too late to get it changed (hope not) but... if
you touch opt_mfs.h, the MFS LKM builds fine, links into the kernel fine,
and works. I just used an MFS with the MFS LKM a few minutes ago. I'm sure
someone could move mfs from the broken -> fixed section in lkm/Makefile
and easily add a touch opt_mfs.h in lkm/mfs/Makefile... (not me, I don't
really know the Makefiles that well, only bsd.port.mk).

Cheers,
Brian Feldman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 21:34:31 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA06829
          for freebsd-current-outgoing; Thu, 15 Oct 1998 21:34:31 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from unix.tfs.net (as1-p5.tfs.net [139.146.210.5])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06767
          for ; Thu, 15 Oct 1998 21:34:15 -0700 (PDT)
          (envelope-from jbryant@unix.tfs.net)
Received: (from jbryant@localhost)
	by unix.tfs.net (8.9.1/8.8.5) id XAA05552
	for freebsd-current@freebsd.org; Thu, 15 Oct 1998 23:33:51 -0500 (CDT)
From: Jim Bryant 
Message-Id: <199810160433.XAA05552@unix.tfs.net>
Subject: netscape in -current is broked
To: freebsd-current@FreeBSD.ORG
Date: Thu, 15 Oct 1998 23:33:50 -0500 (CDT)
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

okay, i just tried installing the ports version of netscape, since my
4.5-beta is expiring.  since netscape seems to not be distributing 4.5
for freebsd anymore, i went to /usr/ports...

i also noticed that the ports version seems to be just a package, not
a true source-code dist.

i am elfen.

[...]
===>   Registering installation for netscape-communicator-4.07
 11:26:43pm  argus(26): rehash
 11:28:08pm  argus(27): netscape >&/dev/null&
[1] 5539
[1]    Exit 1                 netscape >& /dev/null
 11:28:15pm  argus(28):
 11:28:17pm  argus(28): netscape
ld.so failed: Can't find shared library "libXt.so.6.0"
 11:28:19pm  argus(29): communicator-4
ld.so failed: Can't find shared library "libXt.so.6.0"
 11:29:11pm  argus(30): pwd
/usr/ports/www/netscape4-communicator

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  Thu Oct 15 21:37:48 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA07195
          for freebsd-current-outgoing; Thu, 15 Oct 1998 21:37:48 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from seera.nttlabs.com (seera.nttlabs.com [204.162.36.81])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07175;
          Thu, 15 Oct 1998 21:37:30 -0700 (PDT)
          (envelope-from gene@nttlabs.com)
Received: from localhost (gene@localhost)
	by seera.nttlabs.com (8.9.1/8.9.1) with ESMTP id VAA28486;
	Thu, 15 Oct 1998 21:36:56 -0700 (PDT)
	(envelope-from gene@nttlabs.com)
X-Authentication-Warning: seera.nttlabs.com: gene owned process doing -bs
Date: Thu, 15 Oct 1998 21:36:56 -0700 (PDT)
From: "Eugene M. Kim" 
To: "Jordan K. Hubbard" 
cc: FreeBSD-current Mailing List 
Subject: Incompatibility report
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 hope this isn't too late; I just got back from a business trip to
Dusseldorf.)

Could you please add CD-220E (rev 1.0D) IDE CD-ROM drive into the
hardware incompatibility list?  The drive is so braindamaged to report a
capability (accelerated DMA mode) that it does not have indeed, and it
causes any process that accesses the drive to lock up.

Actually I happened to make a patch for this problem, but since it is a
little bit late to expect it to get committed...

Thank you,
Eugene

PS.
Unfortunately I could not figure the manufacturer of the drive; the
model name and revision number was obtained from the bootup diagnostic
message.  It is installed in my Fujitsu Lifebook 675Tx notebook.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 21:47:00 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA08287
          for freebsd-current-outgoing; Thu, 15 Oct 1998 21:47:00 -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 VAA08280
          for ; Thu, 15 Oct 1998 21:46:57 -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 AAA28703;
	Fri, 16 Oct 1998 00:46:30 -0400 (EDT)
Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
	id AA15385; Fri, 16 Oct 1998 00:46:30 -0400
Received: (from jwd@localhost)
	by bb01f39.unx.sas.com (8.9.1/8.9.1) id AAA23559;
	Fri, 16 Oct 1998 00:46:29 -0400 (EDT)
	(envelope-from jwd)
From: "John W. DeBoskey" 
Message-Id: <199810160446.AAA23559@bb01f39.unx.sas.com>
Subject: Re: -current NFS problem
In-Reply-To: From Mike Smith at "Oct 14, 98 09:04:20 am"
To: mike@smith.net.au (Mike Smith)
Date: Fri, 16 Oct 1998 00:46:29 -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

> > Perhaps this could be the problem with NFS "hanging" certain people all
> > the time? (not the pine thing) The system spending way too much time
> > inside the kernel transmitting NFS packets....
> 
> No.  Lack of ACCESS caching makes us slow and eats the network (because 
> we are very good at generating/sending/receiving them).
> 
> If there's someone out there that wants to work with the very best NFS 
> people in the business to sort out our problems, please let me know.  
> NetApp are keen to see our issues resolved (it will mean less angst 
> for them in the long run, as they have many FreeBSD-using customers).
> 
> Right now, we are accumulating a bad NFS reputation. 8(
> 
... deleted for brevity...

Hi,

   I have 50 266 Mhz pc's clustered around 3 netapp F630 Filers used
as compile servers for an in-house distributed make facility.

   85% of the traffic to the netapp(s) 'was' due to access calls. I
do not recommend it for public consumption, but the following patch
reduces the access overhead to less than 20%. 

diff nfs_vnops.c /nfs/locutus/usr/src/sys/nfs
273c273
<       int v3 = NFS_ISV3(vp);
---
>       int v3 = 0; /* NFS_ISV3(vp); */

   ie: tell the nfs_access() function we're always version 2, even
though we're actually connected via 3.  The side effect of this patch
is to delay file access errors, but this is not a real problem in
our environment.

FWIW: currently, 28 pc's connected to 1 F630 netapp delivered the
      following performance (not a controlled test, just an overnight
      job):

>>>STAT: 3149 .o     : avg time 00:02 : avg speed    520/minute :   0 failed.

      ie: 6 minutes to compile 3149 files.

      Our usage of the filers is sequential read of c/h files, and then
sequential write of the .o file.  We do not do mmap'd or random access
i/o and thus have seen no problems such as those reported on -current.

Just my 0.02
John

ps: BTW, I cannot amd mount the filers due to a problem with GARBAGE_ARGS
    being returned from clnt_call() in amfs_host.c\fetch_fhandle() regardless
    of whether I force a V2 or V3 mount protocol.  This is a 'random' error
    which I can get to occurr approximately 1 out of 10 mounts.

    We wrote a small shell script to mount/umount the filers and interfaced
    this with amd via the type=program statement (being tested). So far,
    this has yet to fail...

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 22:43:41 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA14421
          for freebsd-current-outgoing; Thu, 15 Oct 1998 22:43:41 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14412
          for ; Thu, 15 Oct 1998 22:43: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 WAA00764;
	Thu, 15 Oct 1998 22:47:27 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810160547.WAA00764@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jeffrey J. Mountin" 
cc: Mike Smith , "Jordan K. Hubbard" ,
        Karl Pielorz , current@FreeBSD.ORG
Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) 
In-reply-to: Your message of "Wed, 14 Oct 1998 23:39:59 CDT."
             <3.0.3.32.19981014233959.010725dc@207.227.119.2> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 22:47:26 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> At 07:08 PM 10/14/98 -0700, Mike Smith wrote:
> >Actually, Jordan's load is currently split between testing (where most 
> >of my effort right now is) and trying to have something ready for the 
> >Alpha at about the same time.
> 
> Alpha?

It looks like there will be a snapshot of FreeBSD/Alpha at about the 
3.0-RELEASE level, out at about the same time.  I don't think it will 
be described as RELEASE quality (we're not a Linux vendor after all).

> >To the very best of my knowledge, it will not be sprung on the
> >unsuspecting 3.0 release.  Instead, it will probably be turned on as the
> >default a couple of weeks after the release, so that people tracking 3.0
> >will transition, but those using 3.0 flat will not. 
> 
> OK, I'm still a bit unclear.  There have been dozens of messages concerning
> the loader et all w/wo an ELF kernel.
> 
> So, for 3.0 will sysinstall install the new loader and boot blocks _or_
> will this have to be done manually.

The new loader will be installed.  The new boot blocks will be 
available, but will not be installed.  The new loader will not be 
*used* by default.

> Further will 'make world'/'make buildworld' automagically install the new
> load on 3.0 if the sysinstall does not?

Yes.

> And then all hell breaks loose after the freeze. 8-O

The principal goals for the next few months will be to complete the 
current development push and stabilise the existing feature set.  We'll 
branch before 3.0.5 or whatever it's called in February or so, at which 
point aggressive development will move to the 3.1 branch and the 
-stable tag will transition to the 3.0.x branch.

As Jordan has already expounded, the 3.0-RELEASE is meant to put the 
mostly-complete current feature set out to a wider audience; to get it 
used in real-world conditions and on the radar screens of commercial 
vendors, etc.  It holds much of the shape of things to come in many 
ways, even though it is in and of itself not a complete thing.

-- 
\\  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 15 22:45:40 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA14651
          for freebsd-current-outgoing; Thu, 15 Oct 1998 22:45:40 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14645
          for ; Thu, 15 Oct 1998 22:45: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 WAA00789;
	Thu, 15 Oct 1998 22:49:58 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810160549.WAA00789@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Darren Whittaker 
cc: Mike Smith , freebsd-current@FreeBSD.ORG,
        john.young@openmarket.com
Subject: Re: problem in 3.0 
In-reply-to: Your message of "Thu, 15 Oct 1998 07:59:51 MDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 22:49:57 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> > > The code appeared to work until I set buf[0] = '\0'; at the start of the
> > > loop, then only one message was displayed. Since err displays to std error
> > > and I have to run this program from a browers I did not see any error
> > > messages.
> > 
> > I specifically asked what the exact code below does when built as a 
> > program and run on your system.
> > 
> > If setting buf[0] to 0 kills all but the first output, you should be 
> > checking the return from fgets, as it's likely that it's not returning 
> > anything.
> You are right, when I check the return value of fgets, it's NULL, and
> feof() returns a non-zero value meaning at end of file. So is this more of
> an I/O problem than a popen error?

It would tend to indicate that there's something wrong, yes.  8)  You 
need to go back to the test source I posted, and see whether that works 
(it does), and then look at the environment your cgi binary is running 
in and work out why it's *not* working.

You may have encountered a bug either in our C library or Apache.  Does 
the code work on another platform?  Can you add more debugging?  Does 
the child 'date' process always get created?  What happens to 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  Thu Oct 15 22:58:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA15844
          for freebsd-current-outgoing; Thu, 15 Oct 1998 22:58:58 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.easystreet.com (easystreet.com [206.26.36.40])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15835
          for ; Thu, 15 Oct 1998 22:58:57 -0700 (PDT)
          (envelope-from ctapang@easystreet.com)
Received: from apex (dial-56-088.easystreet.com [206.103.56.88])
	by mail.easystreet.com (8.8.7/8.8.7) with SMTP id WAA20904
	for ; Thu, 15 Oct 1998 22:58:38 -0700 (PDT)
Message-ID: <001801bdf8d2$1d525ec0$0d787880@apex>
From: "Carlos C. Tapang" 
To: 
Subject: Intel Pro/10 ethernet card driver
Date: Thu, 15 Oct 1998 23:56:34 -0700
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

I am using the 2.2.7 release, but I believe this problem exists in -current
also.

The mechanism by which if_ex.c distinguishes between the older Pro/10 and
the Pro/10+ does not work for all Pro/10+ (plus) cards. I have a plus card,
but the driver thinks it's the older card. I will go through the handbook
and learn how to submit a fix. It may take me a while to do it because I
still need to find out what the right mechanism is. All I know right now is
that the ethernet address is not the differentiating element.

The driver right now does not work for a (probably) small subset of Pro/10+
cards. It gets all the eeprom info correct except the IRQ, and without the
IRQ no packets go through: ping does not get anything back from another
machine on the same ethernet hub. I kludged the driver to force it to use
the plus configuration data, and now at least I got this FreeBSD machine to
work.

--Carlos


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Thu Oct 15 23:08:41 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA17328
          for freebsd-current-outgoing; Thu, 15 Oct 1998 23:08:41 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17322
          for ; Thu, 15 Oct 1998 23:08:37 -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 XAA00987;
	Thu, 15 Oct 1998 23:13:11 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810160613.XAA00987@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Carlos C. Tapang" 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Intel Pro/10 ethernet card driver 
In-reply-to: Your message of "Thu, 15 Oct 1998 23:56:34 PDT."
             <001801bdf8d2$1d525ec0$0d787880@apex> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 23:13:10 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> The mechanism by which if_ex.c distinguishes between the older Pro/10 and
> the Pro/10+ does not work for all Pro/10+ (plus) cards. I have a plus card,
> but the driver thinks it's the older card. I will go through the handbook
> and learn how to submit a fix. It may take me a while to do it because I
> still need to find out what the right mechanism is. All I know right now is
> that the ethernet address is not the differentiating element.

Thanks for the warning; please do let us know what you manage to work 
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  Thu Oct 15 23:36:19 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA19740
          for freebsd-current-outgoing; Thu, 15 Oct 1998 23:36:19 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19734
          for ; Thu, 15 Oct 1998 23:36:16 -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 XAA01139;
	Thu, 15 Oct 1998 23:40:44 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810160640.XAA01139@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Mike Grommet" 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Installation bugs 3.0BETA 10-09??? We need a can of RAID :) 
In-reply-to: Your message of "Tue, 13 Oct 1998 17:15:51 CDT."
             <00ca01bdf6f7$0a09a080$0cf896d0@work2.insolwwb.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Oct 1998 23:40:43 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Please note that at the moment FTL doesn't have a DPT card of any
description, so we can't do any inhouse debugging of release problems
with them.

We haven't seen any of the problems you're seeing on any other disk 
controller, which makes me suspect that it's related to something 
unique that the DPT is doing. 

> Hi.  running into some interesting problems trying to install
> 3.0 Beta, 10-09 release.
> 
> A bit about the hardware in this machine...
> Pent II 350, Intel BX Chipset
> DPT Raid Controller (DPT PM3334UW)
> 128 Megs of ram, etc etc.
> 
> I go in and dedicate a partition to freebsd...
> I then break the partition up into these chunks:
> 
> 256 Megs      /
> 512 Megs      SWAP
> 1000 Megs    /var
> 3200 Megs    /usr/local
> 2400 Megs    /usr
> 
> basically all goes as normal until it tries to newfs the partitions...
> 
> when it tries to newfs the first slice ( / filesystem)
> 
> Debug reports "DEBUG: unknown major/minor for devtype -"

The message is actually "MakeDev: Unknown major/minor for devtype ..."
and comes from libdisk.  It's surprising that it's being called, but 
it *shouldn't* actually be fatal.

Do all the filesystems get created correctly at this stage?

> it dies with a message on the debug console where it gives "Cross device
> link" error in newfs  and then a rewrite label error.

This sounds a little odd.  It would help to know what the actual text 
from newfs was.

> I just wanted to make sure you guys knew of this situation before the
> release date.

Thanks for the notice; unfortunately it's difficult to know where to
point the finger.  A similar partitioning scheme on a single IDE disk
seems to work just fine, so the suspicion about it maybe being
DPT-related has to take some weight.  I can't see how, though.


-- 
\\  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 16 00:43:23 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA25719
          for freebsd-current-outgoing; Fri, 16 Oct 1998 00:43:23 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25686
          for ; Fri, 16 Oct 1998 00:43: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 AAA01489;
	Fri, 16 Oct 1998 00:47:51 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810160747.AAA01489@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "John W. DeBoskey" 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: -current NFS problem 
In-reply-to: Your message of "Fri, 16 Oct 1998 00:46:29 EDT."
             <199810160446.AAA23559@bb01f39.unx.sas.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Oct 1998 00:47:50 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > No.  Lack of ACCESS caching makes us slow and eats the network (because 
> > we are very good at generating/sending/receiving them).
...
>    I have 50 266 Mhz pc's clustered around 3 netapp F630 Filers used
> as compile servers for an in-house distributed make facility.

Yeep.  Looks like a pretty monster build farm.  I take it you're not 
targetting FreeBSD with the build itself?

>    85% of the traffic to the netapp(s) 'was' due to access calls. I
> do not recommend it for public consumption, but the following patch
> reduces the access overhead to less than 20%. 

Hmm.  I would (naively) have expected this to reduce it to 0.  Where 
else do we make access RPCs from?

> ps: BTW, I cannot amd mount the filers due to a problem with GARBAGE_ARGS
>     being returned from clnt_call() in amfs_host.c\fetch_fhandle() regardless
>     of whether I force a V2 or V3 mount protocol.  This is a 'random' error
>     which I can get to occurr approximately 1 out of 10 mounts.

Is this the "old" amd, or the "new" am-utils amd?  It sounds like one 
or more uninitialised fields in the request structure...

-- 
\\  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 16 04:16:25 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA15191
          for freebsd-current-outgoing; Fri, 16 Oct 1998 04:16:25 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA15182
          for ; Fri, 16 Oct 1998 04:16:22 -0700 (PDT)
          (envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
	by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id HAA29657
	for ; Fri, 16 Oct 1998 07:20:07 -0400 (EDT)
	(envelope-from matt@zigg.com)
Date: Fri, 16 Oct 1998 07:20:07 -0400 (EDT)
From: Matt Behrens 
To: current@FreeBSD.ORG
Subject: sysinstall "probing devices" hangs only on 3.0-199810??-BETA, not
 on 2.2.7-RELEASE boot disk
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

Sorry this is after-the-fact... I really wanted to get this in
before -RELEASE but had no working computer until last night. :(

I can't start the 3.0-19981009-BETA or 3.0-19981015-BETA install
process because sysinstall is hanging at the "probing devices, this
may take a while" screen.  Upon switching to the second VT, the
final DEBUG message is either (forgive my paraphrasing please)

DEBUG: found a disk wd0

or

DEBUG: found a DOS partition wd0s1 on wd0

depending on whether or not there really is a DOS partition.  Prior
to that, it will find ed0, lp0, and create all the slip/ppp
associations appropriately.

The same machine will go through the same screen in < 10s with the
2.2.7-RELEASE boot floppy.  Here's the config:

486 SX 25
AMI BIOS from 1992
8 MB RAM
1.44 FDD
1.2 GB IDE HDD (BIOS does not support any sort of LBA)
VLB IDE/IO controller (also tried w/ ISA IDE/IO controller)
VLB WD Video (also tried w/ generic ISA video)
NE2000-compat ISA NIC

I've tried all manner of switching kernel configs around down to
leaving just fdc0, wd0, and ed0 (the install files are on the
network, so I can't leave ed0 out unless I resorted to lp0 or
something) and done just about everything to the HDD from fake
geometries (which didn't even let the system POST properly) to many
different sized DOS partitions.

Any ideas?  If this is determined to not be my fault, I'll submit
a PR.  But I'm not sure. (:

Matt Behrens    | If only I could learn Japanese and get my
Servant of Karen Behrens       | hands on all 200 Sailor Moon episodes and
Engineer, Nameless IRC Network | all the movies, I think my life would
I eat penguins for breakfast.  | finally be complete . . . . . . . . . . .


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 04:24:07 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA15651
          for freebsd-current-outgoing; Fri, 16 Oct 1998 04:24:07 -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 EAA15646
          for ; Fri, 16 Oct 1998 04:24:04 -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 EAA13178;
	Fri, 16 Oct 1998 04:24:04 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Matt Behrens 
cc: current@FreeBSD.ORG
Subject: Re: sysinstall "probing devices" hangs only on 3.0-199810??-BETA, not on 2.2.7-RELEASE boot disk 
In-reply-to: Your message of "Fri, 16 Oct 1998 07:20:07 EDT."
              
Date: Fri, 16 Oct 1998 04:24:04 -0700
Message-ID: <13174.908537044@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I can't start the 3.0-19981009-BETA or 3.0-19981015-BETA install
> process because sysinstall is hanging at the "probing devices, this
> may take a while" screen.  Upon switching to the second VT, the
> final DEBUG message is either (forgive my paraphrasing please)

I saw that once myself, but only when I went and trimmed out
everything and its brother with the visual userconfig.  When I just
whacked return the next time through, editing nothing in the kernel
configuration, it went fine.  Could you perhaps try this so we could
narrow things down a bit?

- 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 16 05:12:44 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA18027
          for freebsd-current-outgoing; Fri, 16 Oct 1998 05:12:44 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from world.virtual-earth.de (world.virtual-earth.de [194.231.209.38])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18016;
          Fri, 16 Oct 1998 05:12:35 -0700 (PDT)
          (envelope-from mathiasp@mp.virtual-earth.de)
Received: from mp.virtual-earth.de (mp.virtual-earth.de [194.231.209.35])
	by world.virtual-earth.de (8.9.1/8.8.5) with ESMTP id OAA08792;
	Fri, 16 Oct 1998 14:12:08 +0200 (MET DST)
Received: from mp.virtual-earth.de (localhost.virtual-earth.de [127.0.0.1])
	by mp.virtual-earth.de (8.9.1/8.8.5) with ESMTP id OAA02251;
	Fri, 16 Oct 1998 14:11:59 +0200 (MET DST)
Message-Id: <199810161211.OAA02251@mp.virtual-earth.de>
Date: Fri, 16 Oct 1998 14:11:57 +0200 (MET DST)
From: Mathias Picker 
Subject: wine on current: bad system call (semsys)
To: current@FreeBSD.ORG, ports@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
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.

Thanks,

Mathias


-- 

  Mathias Picker

Consultant Information Architecture 

  Mathias.Picker@virtual-earth.de 
              +49 172 / 89 19 381


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 06:25:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA26567
          for freebsd-current-outgoing; Fri, 16 Oct 1998 06:25:59 -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 GAA26562
          for ; Fri, 16 Oct 1998 06:25:55 -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 IAA26239; Fri, 16 Oct 1998 08:25:35 -0500 (CDT)
Received: (from bruce@localhost)
	by zuhause.mn.org (8.8.8/8.8.7) id IAA02005;
	Fri, 16 Oct 1998 08:19:11 -0500 (CDT)
From: Bruce Albrecht 
Date: Fri, 16 Oct 1998 08:18:58 -0500 (CDT)
To: Darin Slovitt 
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ...
In-Reply-To: 
References: 
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <13863.18029.431406.791313@zuhause.zuhause.mn.org>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Darin Slovitt writes:
 > Hello,
 > 
 > I have attached to this message two kernel config files. The GENERIC one
 > which I am running now (which appears to function properly), and the
 > kernel config that I was using which caused "cputime exceeded" messages
 > randomly (I noticed them when running 'tar -xvf' and when attemping to
 > compile perl). If it makes any difference, the tar file was close to
 > 1.0GB.

I hate to bring up the MIME complaint again, because I don't really
care if I get MIME messages, but I wish people would use common sense
when attaching files.  The two attached files were encoded using
base64 when they were just text files.  Text files should use 7bit,
8bit or quoted-printable encoding, as they are readable (more or less) 
on non-MIME readers, and the message is shorter because it doesn't
need to encode 3 characters into 4.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 06:29:07 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA26848
          for freebsd-current-outgoing; Fri, 16 Oct 1998 06:29:07 -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 GAA26843
          for ; Fri, 16 Oct 1998 06:29:05 -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 IAA07749;
	Fri, 16 Oct 1998 08:28:44 -0500 (CDT)
	(envelope-from eculp@webwizard.org.mx)
Message-ID: <36274A0B.8E639D73@webwizard.org.mx>
Date: Fri, 16 Oct 1998 08:28:43 -0500
From: Edwin Culp 
X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386)
X-Accept-Language: en
MIME-Version: 1.0
To: jbryant@unix.tfs.net
CC: freebsd-current@FreeBSD.ORG
Subject: Re: netscape in -current is broked
References: <199810160433.XAA05552@unix.tfs.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jim Bryant wrote:

> okay, i just tried installing the ports version of netscape, since my
> 4.5-beta is expiring.  since netscape seems to not be distributing 4.5
> for freebsd anymore, i went to /usr/ports...
>
> i also noticed that the ports version seems to be just a package, not
> a true source-code dist.
>
> i am elfen.
>
> [...]
> ===>   Registering installation for netscape-communicator-4.07
>  11:26:43pm  argus(26): rehash
>  11:28:08pm  argus(27): netscape >&/dev/null&
> [1] 5539
> [1]    Exit 1                 netscape >& /dev/null
>  11:28:15pm  argus(28):
>  11:28:17pm  argus(28): netscape
> ld.so failed: Can't find shared library "libXt.so.6.0"
>  11:28:19pm  argus(29): communicator-4
> ld.so failed: Can't find shared library "libXt.so.6.0"
>  11:29:11pm  argus(30): pwd
> /usr/ports/www/netscape4-communicator
>

I'm using 4.5b2 aout with an all elf system.  It works more or less ok, although
it seems to crash more often under elf, but then maybe it's the user:-)  I like
it much better than 4.0?.

The downloadable for FreeBSD is under a directory unsupported, if my memory
serves me correctly.

provecho y saludos

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 16 06:40:26 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA27999
          for freebsd-current-outgoing; Fri, 16 Oct 1998 06:40:26 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from unix.tfs.net (as1-p104.tfs.net [139.146.210.104])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27989
          for ; Fri, 16 Oct 1998 06:40:22 -0700 (PDT)
          (envelope-from jbryant@unix.tfs.net)
Received: (from jbryant@localhost)
	by unix.tfs.net (8.9.1/8.8.5) id IAA09676;
	Fri, 16 Oct 1998 08:39:47 -0500 (CDT)
From: Jim Bryant 
Message-Id: <199810161339.IAA09676@unix.tfs.net>
Subject: Re: netscape in -current is broked
In-Reply-To: <36274A0B.8E639D73@webwizard.org.mx> from Edwin Culp at "Oct 16, 98 08:28:43 am"
To: eculp@webwizard.org.mx (Edwin Culp)
Date: Fri, 16 Oct 1998 08:39:46 -0500 (CDT)
Cc: jkh@time.cdrom.com, 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:
> Jim Bryant wrote:
> >  11:28:19pm  argus(29): communicator-4
> > ld.so failed: Can't find shared library "libXt.so.6.0"
> >  11:29:11pm  argus(30): pwd
> > /usr/ports/www/netscape4-communicator
> >
> 
> I'm using 4.5b2 aout with an all elf system.  It works more or less ok, although
> it seems to crash more often under elf, but then maybe it's the user:-)  I like
> it much better than 4.0?.
> 
> The downloadable for FreeBSD is under a directory unsupported, if my memory
> serves me correctly.
> 
> provecho y saludos
> 
> ed

apparently they took it down, or didn't match all of their systems...

anyhow, i think i've found the problem...

when i elfed, i rebuilt X from scratch.  i just double checked on the
Xt lib reference...

-rwxr-xr-x  1 root  wheel  291589 Oct 11 23:38 libXt.so.6

take note that EVERYTHING seems to be looking for:

ld.so failed: Can't find shared library "libXt.so.6.0"

the rebuild of X seems to have built an incorrect version number.
This build was off of last Sat's cvsup.

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  Fri Oct 16 06:52:48 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA29334
          for freebsd-current-outgoing; Fri, 16 Oct 1998 06:52:48 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gate.netbenefit.co.uk (gate.netbenefit.co.uk [195.153.24.12])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA29312
          for ; Fri, 16 Oct 1998 06:52:43 -0700 (PDT)
          (envelope-from pierre.dampure@k2c.co.uk)
Received: from k2c.co.uk [193.149.74.199] 
	by gate.netbenefit.co.uk with esmtp (9.1.3/8.7.3)
	id 0zUAIQ-0002nQ-00; Fri, 16 Oct 1998 14:51:58 +0100
Message-ID: <36274EB8.9DF3380F@k2c.co.uk>
Date: Fri, 16 Oct 1998 14:48:40 +0100
From: "Pierre Y. Dampure" 
Organization: K2C Ltd
X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386)
MIME-Version: 1.0
To: jbryant@unix.tfs.net
CC: Edwin Culp , jkh@time.cdrom.com,
        freebsd-current@FreeBSD.ORG
Subject: Re: netscape in -current is broked
References: <199810161339.IAA09676@unix.tfs.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> anyhow, i think i've found the problem...
>
> when i elfed, i rebuilt X from scratch.  i just double checked on the
> Xt lib reference...
>
> -rwxr-xr-x  1 root  wheel  291589 Oct 11 23:38 libXt.so.6
>
> take note that EVERYTHING seems to be looking for:
>
> ld.so failed: Can't find shared library "libXt.so.6.0"
>
> the rebuild of X seems to have built an incorrect version number.
> This build was off of last Sat's cvsup.
>
> 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



--

Pierre Y. Dampure, Systems Consultant, K2C Ltd
mailto: pierre.dampure@k2c.co.uk       http://www.k2c.co.uk




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 06:54:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA29624
          for freebsd-current-outgoing; Fri, 16 Oct 1998 06:54:35 -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 GAA29605
          for ; Fri, 16 Oct 1998 06:54:28 -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 JAA01316;
	Fri, 16 Oct 1998 09:55:45 -0400 (EDT)
	(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Fri, 16 Oct 1998 09:55:45 -0400 (EDT)
From: Alfred Perlstein 
X-Sender: bright@porkfriedrice.ny.genx.net
To: Edwin Culp 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: netscape in -current is broked
In-Reply-To: <36274A0B.8E639D73@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


well, i've just been running the linux version, yesterday i used a very
spiffy java chat client through netscape-linux and it worked really well.

the emulation in 3.0 is just amazing.

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 Fri, 16 Oct 1998, Edwin Culp wrote:

> Jim Bryant wrote:
> 
> > okay, i just tried installing the ports version of netscape, since my
> > 4.5-beta is expiring.  since netscape seems to not be distributing 4.5
> > for freebsd anymore, i went to /usr/ports...
> >
> > i also noticed that the ports version seems to be just a package, not
> > a true source-code dist.
> >
> > i am elfen.
> >
> > [...]
> > ===>   Registering installation for netscape-communicator-4.07
> >  11:26:43pm  argus(26): rehash
> >  11:28:08pm  argus(27): netscape >&/dev/null&
> > [1] 5539
> > [1]    Exit 1                 netscape >& /dev/null
> >  11:28:15pm  argus(28):
> >  11:28:17pm  argus(28): netscape
> > ld.so failed: Can't find shared library "libXt.so.6.0"
> >  11:28:19pm  argus(29): communicator-4
> > ld.so failed: Can't find shared library "libXt.so.6.0"
> >  11:29:11pm  argus(30): pwd
> > /usr/ports/www/netscape4-communicator
> >
> 
> I'm using 4.5b2 aout with an all elf system.  It works more or less ok, although
> it seems to crash more often under elf, but then maybe it's the user:-)  I like
> it much better than 4.0?.
> 
> The downloadable for FreeBSD is under a directory unsupported, if my memory
> serves me correctly.
> 
> provecho y saludos
> 
> ed
> 
> 
> 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  Fri Oct 16 06:58:39 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA00514
          for freebsd-current-outgoing; Fri, 16 Oct 1998 06:58:39 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gate.netbenefit.co.uk (gate.netbenefit.co.uk [195.153.24.12])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA00508
          for ; Fri, 16 Oct 1998 06:58:37 -0700 (PDT)
          (envelope-from pierre.dampure@k2c.co.uk)
Received: from k2c.co.uk [193.149.74.199] 
	by gate.netbenefit.co.uk with esmtp (9.1.3/8.7.3)
	id 0zUAOQ-0002uN-00; Fri, 16 Oct 1998 14:58:11 +0100
Message-ID: <36275020.A5ADA60B@k2c.co.uk>
Date: Fri, 16 Oct 1998 14:54:40 +0100
From: "Pierre Y. Dampure" 
Organization: K2C Ltd
X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386)
MIME-Version: 1.0
To: jbryant@unix.tfs.net
CC: freebsd-current@FreeBSD.ORG
Subject: Re: netscape in -current is broked
References: <199810161339.IAA09676@unix.tfs.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jim Bryant wrote:

> anyhow, i think i've found the problem...
>
> when i elfed, i rebuilt X from scratch.  i just double checked on the
> Xt lib reference...
>
> -rwxr-xr-x  1 root  wheel  291589 Oct 11 23:38 libXt.so.6
>
> take note that EVERYTHING seems to be looking for:
>
> ld.so failed: Can't find shared library "libXt.so.6.0"
>
> the rebuild of X seems to have built an incorrect version number.
> This build was off of last Sat's cvsup.
>

(previous email to be ignored, mistyping)

As mentioned on numerous occasions in this list, you should have backed up your a.out
X libraries before moving to ELF, since Netscape (and others) are still assuming
FreeBSD is an a.out system. The error you're getting is fairly clear in this regard
(netscape looks for an a.out format libXt.so -- the ELF format libraries do not use
so.X.Y naming convention).

Pick up the a.out libraries from ftp.xfree86.org, move them to /usr/X11R6/lib/aout,
add that to your a.out ld path, you're in.

Best Regards,

--

Pierre Y. Dampure, Systems Consultant, K2C Ltd
mailto: pierre.dampure@k2c.co.uk       http://www.k2c.co.uk




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 07:08:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA01601
          for freebsd-current-outgoing; Fri, 16 Oct 1998 07:08:35 -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 HAA01589
          for ; Fri, 16 Oct 1998 07:08:17 -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 JAA08401;
	Fri, 16 Oct 1998 09:05:58 -0500 (CDT)
	(envelope-from eculp@webwizard.org.mx)
Message-ID: <362752C6.2380A867@webwizard.org.mx>
Date: Fri, 16 Oct 1998 09:05:58 -0500
From: Edwin Culp 
X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386)
X-Accept-Language: en
MIME-Version: 1.0
To: jbryant@unix.tfs.net
CC: jkh@time.cdrom.com, freebsd-current@FreeBSD.ORG
Subject: Re: netscape in -current is broked
References: <199810161339.IAA09676@unix.tfs.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jim Bryant wrote:

> In reply:
> > Jim Bryant wrote:
> > >  11:28:19pm  argus(29): communicator-4
> > > ld.so failed: Can't find shared library "libXt.so.6.0"
> > >  11:29:11pm  argus(30): pwd
> > > /usr/ports/www/netscape4-communicator
> > >
> >
> > I'm using 4.5b2 aout with an all elf system.  It works more or less ok, although
> > it seems to crash more often under elf, but then maybe it's the user:-)  I like
> > it much better than 4.0?.
> >
> > The downloadable for FreeBSD is under a directory unsupported, if my memory
> > serves me correctly.
> >
> > provecho y saludos
> >
> > ed
>
> apparently they took it down, or didn't match all of their systems...
>
> anyhow, i think i've found the problem...
>
> when i elfed, i rebuilt X from scratch.  i just double checked on the
> Xt lib reference...
>
> -rwxr-xr-x  1 root  wheel  291589 Oct 11 23:38 libXt.so.6
>
> take note that EVERYTHING seems to be looking for:
>
> ld.so failed: Can't find shared library "libXt.so.6.0"
>
> the rebuild of X seems to have built an incorrect version number.
> This build was off of last Sat's cvsup.

You should have the aout version also.  I put mine in /usr/X11R6/lib/aout.  Maybe you
aren't running ldconfig on the aout directory that netscape needs.  If you don't have
the file, I could attach it or put it up for ftp.

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 16 07:09:26 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA01770
          for freebsd-current-outgoing; Fri, 16 Oct 1998 07:09:26 -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 HAA01683
          for ; Fri, 16 Oct 1998 07:09:09 -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 QAA17426; Fri, 16 Oct 1998 16:08:16 +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: <199810161339.IAA09676@unix.tfs.net>
Date: Fri, 16 Oct 1998 16:08:16 +0200 (MEST)
Organization: university of bayreuth
From: Werner Griessl 
To: Jim Bryant 
Subject: Re: netscape in -current is broked
Cc: freebsd-current@FreeBSD.ORG, jkh@time.cdrom.com,
        (Edwin Culp) 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


You need the old aout-Xlibs for netscape:

ldd /usr/local/lib/netscape/navigator-4.07.bin
/usr/local/lib/netscape/navigator-4.07.bin:
        -lXt.6 => /usr/X11R6/lib/aout/libXt.so.6.0 (0x2063c000)
        -lXmu.6 => /usr/X11R6/lib/aout/libXmu.so.6.0 (0x20678000)
        -lX11.6 => /usr/X11R6/lib/aout/libX11.so.6.1 (0x20687000)
        -lXext.6 => /usr/X11R6/lib/aout/libXext.so.6.3 (0x20718000)
        -lSM.6 => /usr/X11R6/lib/aout/libSM.so.6.0 (0x20721000)
        -lICE.6 => /usr/X11R6/lib/aout/libICE.so.6.3 (0x20729000)
        -lg++.4 => /usr/lib/aout/libg++.so.4.0 (0x2073a000)
        -lm.2 => /usr/lib/aout/libm.so.2.0 (0x20776000)
        -lstdc++.2 => /usr/lib/aout/libstdc++.so.2.0 (0x20790000)
        -lc.3 => /usr/lib/aout/libc.so.3.1 (0x207c6000)
Werner

On 16-Oct-98 Jim Bryant wrote:
> In reply:
>> Jim Bryant wrote:
>> >  11:28:19pm  argus(29): communicator-4
>> > ld.so failed: Can't find shared library "libXt.so.6.0"
>> >  11:29:11pm  argus(30): pwd
>> > /usr/ports/www/netscape4-communicator
>> >
>> 
>> I'm using 4.5b2 aout with an all elf system.  It works more or less ok,
>> although
>> it seems to crash more often under elf, but then maybe it's the user:-)  I
>> like
>> it much better than 4.0?.
>> 
>> The downloadable for FreeBSD is under a directory unsupported, if my memory
>> serves me correctly.
>> 
>> provecho y saludos
>> 
>> ed
> 
> apparently they took it down, or didn't match all of their systems...
> 
> anyhow, i think i've found the problem...
> 
> when i elfed, i rebuilt X from scratch.  i just double checked on the
> Xt lib reference...
> 
> -rwxr-xr-x  1 root  wheel  291589 Oct 11 23:38 libXt.so.6
> 
> take note that EVERYTHING seems to be looking for:
> 
> ld.so failed: Can't find shared library "libXt.so.6.0"
> 
> the rebuild of X seems to have built an incorrect version number.
> This build was off of last Sat's cvsup.
> 
> 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

----------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 07:29:08 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA03844
          for freebsd-current-outgoing; Fri, 16 Oct 1998 07:29:08 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sage1.sagecorp.com ([204.250.198.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03839
          for ; Fri, 16 Oct 1998 07:29:02 -0700 (PDT)
          (envelope-from djw@sage1.sagecorp.com)
Received: from localhost (djw@localhost) by sage1.sagecorp.com (8.7.5/8.7.3) with SMTP id IAA22131; Fri, 16 Oct 1998 08:35:19 -0600 (MDT)
Date: Fri, 16 Oct 1998 08:35:19 -0600 (MDT)
From: Darren Whittaker 
To: Mike Smith 
cc: freebsd-current@FreeBSD.ORG, john.young@openmarket.com
Subject: Re: problem in 3.0 
In-Reply-To: <199810160549.WAA00789@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

First off let me express my thanks for all the help I'ver received.

We seem to have found out what the problem is. We have been compiling our
code on a BSD system. Up to this point this code would run on both BSD and
freeBSD systems. With freeBSD's version 3.0 this no longer seems to be the
case. I took the test program and compiled it on a freeBSD system and it
correctly executed on the customer's 3.0 beta system.

-Darren



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 07:30:13 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA04155
          for freebsd-current-outgoing; Fri, 16 Oct 1998 07:30:13 -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 HAA04111
          for ; Fri, 16 Oct 1998 07:30:05 -0700 (PDT)
          (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by hub.org (8.8.8/8.8.8) with ESMTP id KAA19990
	for ; Fri, 16 Oct 1998 10:29:35 -0400 (EDT)
	(envelope-from scrappy@hub.org)
Date: Fri, 16 Oct 1998 10:29:28 -0400 (EDT)
From: "Marc G. Fournier" 
To: freebsd-current@FreeBSD.ORG
Subject: can't checkout kernel source code for 3.0-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


I got into the habit awhile back of cvsup'ng down the CVS reposity, and
then doing checkouts on my own here, and after cvsup'ng the newest code as
of this morning, and trying to check it out, I get:

hub# pwd
/usr/src/sys/i386/isa
hub# cvs update .
cvs update: Updating .
Abort (core dumped)
hub#

I rm -rf'd the sys directory from the cvs repository and re-cvsup'd that.
No change.  I removed /usr/src/sys and re-checked it out.  No change.  

Using truss, the error appears to be:

syscall
open("/usr/local/freebsd-cvsroot/src/sys/i386/isa/if_ed.c,v",0,0666)
        returns 4 (0x4)
syscall fstat(4,0xefbfd7b8)
        returns 0 (0x0)
syscall read(0x4,0x8c000,0x2000)
        returns 8192 (0x2000)
syscall lstat(0x85340,0xefbfd7d8)
        errno 2 'No such file or directory'

Doing an ls -l of the file shows it fine, so I'm not sure which file it
isn't finding :(

Help?

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  Fri Oct 16 07:42:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA06064
          for freebsd-current-outgoing; Fri, 16 Oct 1998 07:42:59 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bytor.rush.net (bytor.rush.net [209.45.245.145])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06046
          for ; Fri, 16 Oct 1998 07:42:55 -0700 (PDT)
          (envelope-from lynch@rush.net)
Received: from localhost (lynch@localhost)
	by bytor.rush.net (8.9.1/8.8.8) with SMTP id KAA14132;
	Fri, 16 Oct 1998 10:41:45 -0400 (EDT)
	(envelope-from lynch@rush.net)
Date: Fri, 16 Oct 1998 10:41:44 -0400 (EDT)
From: Pat Lynch 
To: Werner Griessl 
cc: Jim Bryant , freebsd-current@FreeBSD.ORG,
        jkh@time.cdrom.com, eculp@webwizard.org.mx
Subject: Re: netscape in -current is broked
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 wonder if now that 3.0 is being released they will release an ELF
FreeBSD Netscape? 

___________________________________________________________________________

Pat Lynch						lynch@rush.net
Systems Administrator					Rush Networking

___________________________________________________________________________

On Fri, 16 Oct 1998, Werner Griessl wrote:

> 
> You need the old aout-Xlibs for netscape:
> 
> ldd /usr/local/lib/netscape/navigator-4.07.bin
> /usr/local/lib/netscape/navigator-4.07.bin:
>         -lXt.6 => /usr/X11R6/lib/aout/libXt.so.6.0 (0x2063c000)
>         -lXmu.6 => /usr/X11R6/lib/aout/libXmu.so.6.0 (0x20678000)
>         -lX11.6 => /usr/X11R6/lib/aout/libX11.so.6.1 (0x20687000)
>         -lXext.6 => /usr/X11R6/lib/aout/libXext.so.6.3 (0x20718000)
>         -lSM.6 => /usr/X11R6/lib/aout/libSM.so.6.0 (0x20721000)
>         -lICE.6 => /usr/X11R6/lib/aout/libICE.so.6.3 (0x20729000)
>         -lg++.4 => /usr/lib/aout/libg++.so.4.0 (0x2073a000)
>         -lm.2 => /usr/lib/aout/libm.so.2.0 (0x20776000)
>         -lstdc++.2 => /usr/lib/aout/libstdc++.so.2.0 (0x20790000)
>         -lc.3 => /usr/lib/aout/libc.so.3.1 (0x207c6000)
> Werner
> 
> On 16-Oct-98 Jim Bryant wrote:
> > In reply:
> >> Jim Bryant wrote:
> >> >  11:28:19pm  argus(29): communicator-4
> >> > ld.so failed: Can't find shared library "libXt.so.6.0"
> >> >  11:29:11pm  argus(30): pwd
> >> > /usr/ports/www/netscape4-communicator
> >> >
> >> 
> >> I'm using 4.5b2 aout with an all elf system.  It works more or less ok,
> >> although
> >> it seems to crash more often under elf, but then maybe it's the user:-)  I
> >> like
> >> it much better than 4.0?.
> >> 
> >> The downloadable for FreeBSD is under a directory unsupported, if my memory
> >> serves me correctly.
> >> 
> >> provecho y saludos
> >> 
> >> ed
> > 
> > apparently they took it down, or didn't match all of their systems...
> > 
> > anyhow, i think i've found the problem...
> > 
> > when i elfed, i rebuilt X from scratch.  i just double checked on the
> > Xt lib reference...
> > 
> > -rwxr-xr-x  1 root  wheel  291589 Oct 11 23:38 libXt.so.6
> > 
> > take note that EVERYTHING seems to be looking for:
> > 
> > ld.so failed: Can't find shared library "libXt.so.6.0"
> > 
> > the rebuild of X seems to have built an incorrect version number.
> > This build was off of last Sat's cvsup.
> > 
> > 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
> 
> ----------------------------------
> 
> 
> 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  Fri Oct 16 08:37:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA12943
          for freebsd-current-outgoing; Fri, 16 Oct 1998 08:37:59 -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 IAA12826
          for ; Fri, 16 Oct 1998 08:37:26 -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 LAA18009;
	Fri, 16 Oct 1998 11:36:30 -0400 (EDT)
Date: Fri, 16 Oct 1998 11:36:30 -0400 (EDT)
From: Brian Feldman 
To: "Marc G. Fournier" 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: can't checkout kernel source code for 3.0-CURRENT...
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

But you haven't used ktrace/kdump instead of truss? By default, I'm not
sure if truss is the best thing to use, really. Ktrace and kdump always
does a much nicer job.

Cheers,
Brian Feldman

On Fri, 16 Oct 1998, Marc G. Fournier wrote:

> 
> I got into the habit awhile back of cvsup'ng down the CVS reposity, and
> then doing checkouts on my own here, and after cvsup'ng the newest code as
> of this morning, and trying to check it out, I get:
> 
> hub# pwd
> /usr/src/sys/i386/isa
> hub# cvs update .
> cvs update: Updating .
> Abort (core dumped)
> hub#
> 
> I rm -rf'd the sys directory from the cvs repository and re-cvsup'd that.
> No change.  I removed /usr/src/sys and re-checked it out.  No change.  
> 
> Using truss, the error appears to be:
> 
> syscall
> open("/usr/local/freebsd-cvsroot/src/sys/i386/isa/if_ed.c,v",0,0666)
>         returns 4 (0x4)
> syscall fstat(4,0xefbfd7b8)
>         returns 0 (0x0)
> syscall read(0x4,0x8c000,0x2000)
>         returns 8192 (0x2000)
> syscall lstat(0x85340,0xefbfd7d8)
>         errno 2 'No such file or directory'
> 
> Doing an ls -l of the file shows it fine, so I'm not sure which file it
> isn't finding :(
> 
> Help?
> 
> 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
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 08:38:07 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA12993
          for freebsd-current-outgoing; Fri, 16 Oct 1998 08:38: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 IAA12925
          for ; Fri, 16 Oct 1998 08:37: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 IAA00383;
	Fri, 16 Oct 1998 08:41:25 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810161541.IAA00383@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Darren Whittaker 
cc: Mike Smith , freebsd-current@FreeBSD.ORG,
        john.young@openmarket.com
Subject: Re: problem in 3.0 
In-reply-to: Your message of "Fri, 16 Oct 1998 08:35:19 MDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Oct 1998 08:41:25 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> First off let me express my thanks for all the help I'ver received.
> 
> We seem to have found out what the problem is. We have been compiling our
> code on a BSD system. Up to this point this code would run on both BSD and
> freeBSD systems. With freeBSD's version 3.0 this no longer seems to be the
> case. I took the test program and compiled it on a freeBSD system and it
> correctly executed on the customer's 3.0 beta system.

When you say "on a BSD system", which BSD?  FreeBSD?  NetBSD?  OpenBSD? 
BSD/OS?

It sounds like what you're saying is that we've broken BSD/OS 
compatibility.  That's bad.  Were you linking the application 
statically or shared?

-- 
\\  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 16 08:43:04 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA13928
          for freebsd-current-outgoing; Fri, 16 Oct 1998 08:43:04 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA13920
          for ; Fri, 16 Oct 1998 08:42:58 -0700 (PDT)
          (envelope-from shimon@simon-shapiro.org)
Received: (qmail 3685 invoked by uid 1000); 16 Oct 1998 16:46:20 -0000
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, 16 Oct 1998 12:46:20 -0400 (EDT)
X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z#
 Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+
 O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc?
Reply-To: shimon@simon-shapiro.org
Organization: The Simon Shapiro Foundation
From: Simon Shapiro 
To: freebsd-current@FreeBSD.ORG
Subject: Show Stopper?  Failure to Install 19981014
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi Yall,

I am installing, from scratch, on a known-to-be-good system, FreeBSD
3.0-CURRENT, the snapshot from 14-Oct (compiled here) and getting the
following error messages during filesystem creation:

[ After newfs lists superblocks ]

newfs: ioctl (WDINFO): cros-device link
newfs: /mnt/dev/rda0s4a cant rewrite disk label.

The disk is partitioned to have a 64MB DOS slice a 1GB FreeBSD
slice another 1GB freeBSD slice and a slightly over 2GB FreeBSD
slice.

There are numerous FreeBSD partitions in each slice.  The systme has a DPT
controller driving a RAID-1 array.  The very same system (and numerous
others) are running IDENTICAL hardware with the very same date code without
any sign of this problem. This problem has been confirmed by others and is
very real.

As a reference, 2.2.7 installs and boots.  Pre-CAM 3.0 installs and boots.

The (excessive) confirmations are an attempt to stem ``Oh, it soes not
happen here, must be the DPT driver'' comments.  I belive it does not
happen elsewhere but is serious enough for us to post it here in search for
help.  We are standing by to do what is needed to make it work.

If you feel like chatting, I am at 770.794.1513




Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
                                             770.265.7340
Simon Shapiro

Unwritten code has no bugs and executes at twice the speed of mouth


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 08:51:02 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA14418
          for freebsd-current-outgoing; Fri, 16 Oct 1998 08:51:02 -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 IAA14400;
          Fri, 16 Oct 1998 08:51:00 -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 IAA06761;
	Fri, 16 Oct 1998 08:50:25 -0700 (PDT)
	(envelope-from Studded@gorean.org)
Message-ID: <36276B40.EB20EA55@gorean.org>
Date: Fri, 16 Oct 1998 08:50:24 -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: Mathias Picker 
CC: current@FreeBSD.ORG, ports@FreeBSD.ORG
Subject: Re: wine on current: bad system call (semsys)
References: <199810161211.OAA02251@mp.virtual-earth.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mathias Picker wrote:
> 
> 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.

	If quickbooks is not a networked app, try bochs instead. Depending on
wine for any real work is not a good thing. The wine people are
notoriously linux-centric, and don't really care to change.

Good luck,

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  Fri Oct 16 08:59:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA15209
          for freebsd-current-outgoing; Fri, 16 Oct 1998 08:59:58 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sage1.sagecorp.com ([204.250.198.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15203
          for ; Fri, 16 Oct 1998 08:59:57 -0700 (PDT)
          (envelope-from djw@sage1.sagecorp.com)
Received: from localhost (djw@localhost) by sage1.sagecorp.com (8.7.5/8.7.3) with SMTP id KAA22793; Fri, 16 Oct 1998 10:06:23 -0600 (MDT)
Date: Fri, 16 Oct 1998 10:06:22 -0600 (MDT)
From: Darren Whittaker 
To: Mike Smith 
cc: freebsd-current@FreeBSD.ORG, john.young@openmarket.com
Subject: Re: problem in 3.0 
In-Reply-To: <199810161541.IAA00383@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

We compile on:
 BSDI BSD/OS 2.0

We link shared.

-Darren              



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 09:04:28 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA15834
          for freebsd-current-outgoing; Fri, 16 Oct 1998 09:04:28 -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 JAA15823
          for ; Fri, 16 Oct 1998 09:04:26 -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 JAA06836;
	Fri, 16 Oct 1998 09:03:44 -0700 (PDT)
	(envelope-from Studded@gorean.org)
Message-ID: <36276E5F.CAF7B06F@gorean.org>
Date: Fri, 16 Oct 1998 09:03:43 -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: Werner Griessl 
CC: freebsd-current@FreeBSD.ORG
Subject: Re: netscape in -current is broked
References: 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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? 

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  Fri Oct 16 09:10:29 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA16904
          for freebsd-current-outgoing; Fri, 16 Oct 1998 09:10:29 -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 JAA16875
          for ; Fri, 16 Oct 1998 09:10:24 -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 JAA00588;
	Fri, 16 Oct 1998 09:13:53 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810161613.JAA00588@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Darren Whittaker 
cc: Mike Smith , freebsd-current@FreeBSD.ORG,
        john.young@openmarket.com
Subject: Re: problem in 3.0 
In-reply-to: Your message of "Fri, 16 Oct 1998 10:06:22 MDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Oct 1998 09:13:52 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> We compile on:
>  BSDI BSD/OS 2.0
> 
> We link shared.

Ok, sounds like you're being bitten by incompatibilities between our C 
library and theirs.  The best way to work around this will be to link 
static - your program will start and run faster, and as a bonus you'll 
have a much better chance of running on both BSD/OS and FreeBSD systems.

We do our best to maintain binary compatibility with BSD/OS at the 
kernel level, but at the library level it's just a bit too hard.

-- 
\\  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 16 09:39:12 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA21490
          for freebsd-current-outgoing; Fri, 16 Oct 1998 09:39:12 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sage1.sagecorp.com ([204.250.198.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21485
          for ; Fri, 16 Oct 1998 09:39:09 -0700 (PDT)
          (envelope-from djw@sage1.sagecorp.com)
Received: from localhost (djw@localhost) by sage1.sagecorp.com (8.7.5/8.7.3) with SMTP id KAA23166; Fri, 16 Oct 1998 10:45:28 -0600 (MDT)
Date: Fri, 16 Oct 1998 10:45:28 -0600 (MDT)
From: Darren Whittaker 
To: Mike Smith 
cc: freebsd-current@FreeBSD.ORG, john.young@openmarket.com
Subject: Re: problem in 3.0 
In-Reply-To: <199810161613.JAA00588@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 Fri, 16 Oct 1998, Mike Smith wrote:

> > We compile on:
> >  BSDI BSD/OS 2.0
> > 
> > We link shared.
> 
> Ok, sounds like you're being bitten by incompatibilities between our C 
> library and theirs.  The best way to work around this will be to link 
> static - your program will start and run faster, and as a bonus you'll 
> have a much better chance of running on both BSD/OS and FreeBSD systems.
> 
> We do our best to maintain binary compatibility with BSD/OS at the 
> kernel level, but at the library level it's just a bit too hard.
> 
> -- 
> \\  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
> 
> 
> 
We just linked our code using static but they still won't work on the 3.0
system. We are concerned that our freeBSD customers are going to have
problems with our working software when they upgrade from 2.x to 3.x.

-Darren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 09:39:33 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA21582
          for freebsd-current-outgoing; Fri, 16 Oct 1998 09:39:33 -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 JAA21576
          for ; Fri, 16 Oct 1998 09:39:27 -0700 (PDT)
          (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by hub.org (8.8.8/8.8.8) with ESMTP id MAA00409;
	Fri, 16 Oct 1998 12:39:01 -0400 (EDT)
	(envelope-from scrappy@hub.org)
Date: Fri, 16 Oct 1998 12:39:01 -0400 (EDT)
From: "Marc G. Fournier" 
To: Brian Feldman 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: can't checkout kernel source code for 3.0-CURRENT...
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 Fri, 16 Oct 1998, Brian Feldman wrote:

> But you haven't used ktrace/kdump instead of truss? By default, I'm not
> sure if truss is the best thing to use, really. Ktrace and kdump always
> does a much nicer job.

 28149 cvs      RET   read 8192/0x2000
 28149 cvs      CALL  lstat(0x85340,0xefbfd7d8)
 28149 cvs      NAMI  "if_ed.c"
 28149 cvs      RET   lstat -1 errno 2 No such file or directory
 28149 cvs      CALL  lseek(0x4,0,0,0,0x1)
 28149 cvs      RET   lseek 8192/0x2000
 28149 cvs      CALL  break(0x8f000)
 28149 cvs      RET   break 0
 28149 cvs      CALL  break(0x90000)
 28149 cvs      RET   break 0
 28149 cvs      CALL  break(0x91000)
 28149 cvs      RET   break 0
 28149 cvs      CALL  break(0x92000)
 28149 cvs      RET   break 0
 28149 cvs      CALL  break(0x93000)
 28149 cvs      RET   break 0
 28149 cvs      CALL  break(0x94000)
 28149 cvs      RET   break 0
 28149 cvs      CALL  break(0x95000)
 28149 cvs      RET   break 0
 28149 cvs      CALL  sigprocmask(0x3,0xffffffdf)
 28149 cvs      RET   sigprocmask 0
 28149 cvs      CALL  getpid
 28149 cvs      RET   getpid 28149/0x6df5
 28149 cvs      CALL  kill(0x6df5,0x6)
 28149 cvs      PSIG  SIGIOT SIG_DFL
 28149 cvs      NAMI  "cvs.core"

	Okay, so its gettinga 'No such file or directory' on if_ed.c, but
of course it doesn't exist, since I'm just trying to check it out :(

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  Fri Oct 16 09:54:44 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA22781
          for freebsd-current-outgoing; Fri, 16 Oct 1998 09:54:44 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA22774
          for ; Fri, 16 Oct 1998 09:54:40 -0700 (PDT)
          (envelope-from shimon@simon-shapiro.org)
Received: (qmail 4026 invoked by uid 1000); 16 Oct 1998 17:58:02 -0000
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: Fri, 16 Oct 1998 13:58:02 -0400 (EDT)
X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z#
 Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+
 O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc?
Reply-To: shimon@simon-shapiro.org
Organization: The Simon Shapiro Foundation
From: Simon Shapiro 
To: Simon Shapiro 
Subject: RE: Show Stopper?  Failure to Install 19981014
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

NewsFlash:

While the release from the 4-oct-1998 has the same error messages, it
installs correctly.  Now, will some wise person who knowns what happened in
between help me solve this problem?

Simon

Simon Shapiro, On 16-Oct-98 you wrote:
>  Hi Yall,
>  
>  I am installing, from scratch, on a known-to-be-good system, FreeBSD
>  3.0-CURRENT, the snapshot from 14-Oct (compiled here) and getting the
>  following error messages during filesystem creation:
>  
>  [ After newfs lists superblocks ]
>  
>  newfs: ioctl (WDINFO): cros-device link
>  newfs: /mnt/dev/rda0s4a cant rewrite disk label.
>  
>  The disk is partitioned to have a 64MB DOS slice a 1GB FreeBSD
>  slice another 1GB freeBSD slice and a slightly over 2GB FreeBSD
>  slice.
>  
>  There are numerous FreeBSD partitions in each slice.  The systme has a
>  DPT
>  controller driving a RAID-1 array.  The very same system (and numerous
>  others) are running IDENTICAL hardware with the very same date code
>  without
>  any sign of this problem. This problem has been confirmed by others and
>  is
>  very real.
>  
>  As a reference, 2.2.7 installs and boots.  Pre-CAM 3.0 installs and
>  boots.
>  
>  The (excessive) confirmations are an attempt to stem ``Oh, it soes not
>  happen here, must be the DPT driver'' comments.  I belive it does not
>  happen elsewhere but is serious enough for us to post it here in search
>  for
>  help.  We are standing by to do what is needed to make it work.
>  
>  If you feel like chatting, I am at 770.794.1513
>  
>  
>  
>  
>  Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
>                                               770.265.7340
>  Simon Shapiro
>  
>  Unwritten code has no bugs and executes at twice the speed of mouth
>  
>  
>  To Unsubscribe: send mail to majordomo@FreeBSD.org
>  with "unsubscribe freebsd-current" in the body of the message



Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
                                             770.265.7340
Simon Shapiro

Unwritten code has no bugs and executes at twice the speed of mouth


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 09:58:38 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA23206
          for freebsd-current-outgoing; Fri, 16 Oct 1998 09:58:38 -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 JAA23201
          for ; Fri, 16 Oct 1998 09:58:37 -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 KAA00831;
	Fri, 16 Oct 1998 10:02:05 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810161702.KAA00831@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Darren Whittaker 
cc: Mike Smith , freebsd-current@FreeBSD.ORG,
        john.young@openmarket.com
Subject: Re: problem in 3.0 
In-reply-to: Your message of "Fri, 16 Oct 1998 10:45:28 MDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Oct 1998 10:02:05 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Fri, 16 Oct 1998, Mike Smith wrote:
> 
> > > We compile on:
> > >  BSDI BSD/OS 2.0
> > > 
> > > We link shared.
> > 
> > Ok, sounds like you're being bitten by incompatibilities between our C 
> > library and theirs.  The best way to work around this will be to link 
> > static - your program will start and run faster, and as a bonus you'll 
> > have a much better chance of running on both BSD/OS and FreeBSD systems.
> > 
> > We do our best to maintain binary compatibility with BSD/OS at the 
> > kernel level, but at the library level it's just a bit too hard.
...
> We just linked our code using static but they still won't work on the 3.0
> system.

That's interesting.  Building the code on a 3.0 system results in a
working binary, but a fully-static binary built on BSD/OS 2.x doesn't
work correctly?  Can you please file a PR describing this, and if
possible include a uuencoded standalone BSD/OS binary that demonstrates
the problem, as well as source for it?

It would also be interesting to know if the code built on a FreeBSD 
2.2.x system and ran properly on a FreeBSD 3.0 system.  It may be that 
this would be a workable migration path for you?

> We are concerned that our freeBSD customers are going to have
> problems with our working software when they upgrade from 2.x to 3.x.

At this point, you should recommend your 2.x customers to move to 2.2.8 in
November if they go anywhere, and then to the next 3.0.x release in
1Q99.  We would expect to be able to resolve this issue well before the 
next 3.0-based release.

Alternatively, consider offering a FreeBSD native binary to your 
customers; if the build on 2.2.7 works correctly on 3.0, this will give 
you a stable platform to work from for some 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

From owner-freebsd-current  Fri Oct 16 09:59:51 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA23320
          for freebsd-current-outgoing; Fri, 16 Oct 1998 09:59:51 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from unix.tfs.net (as1-p82.tfs.net [139.146.210.82])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23304
          for ; Fri, 16 Oct 1998 09:59:47 -0700 (PDT)
          (envelope-from jbryant@unix.tfs.net)
Received: (from jbryant@localhost)
	by unix.tfs.net (8.9.1/8.8.5) id LAA00587;
	Fri, 16 Oct 1998 11:59:09 -0500 (CDT)
From: Jim Bryant 
Message-Id: <199810161659.LAA00587@unix.tfs.net>
Subject: Re: netscape in -current is broked
In-Reply-To:  from Alexander Sanda at "Oct 16, 98 08:12:12 am"
To: as@psa.at (Alexander Sanda)
Date: Fri, 16 Oct 1998 11:59:08 -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:
> On Thu, 15 Oct 1998, Jim Bryant wrote:
> 
> > okay, i just tried installing the ports version of netscape, since my
> > 4.5-beta is expiring.  since netscape seems to not be distributing 4.5
> > for freebsd anymore, i went to /usr/ports...
> 
> Hm, where did you get this rumour ?
> 
> I have a native aout version of 4.5b2 (which expires not-so-soon as far
> as I can remember).

actually my 4.5b1 expired today.

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  Fri Oct 16 10:29:57 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA29026
          for freebsd-current-outgoing; Fri, 16 Oct 1998 10:29:57 -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 KAA29018
          for ; Fri, 16 Oct 1998 10:29:53 -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 TAA09522
	for freebsd-current@FreeBSD.ORG; Fri, 16 Oct 1998 19:29:32 +0200 (CEST)
	(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (VMailer, from userid 101)
	id 069F21462; Fri, 16 Oct 1998 19:23:39 +0200 (CEST)
Date: Fri, 16 Oct 1998 19:23:39 +0200
From: Ollivier Robert 
To: "FreeBSD Current Users' list" 
Subject: Perl5 compiled in both a.out and ELF builds
Message-ID: <19981016192339.A5726@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#4724 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"make world" in an ELF 3.0-BETA^H^H^H^HRELEASE still build Perl (and
probably a few others) in both ELF and a.out. The a.out version is not
installed of course but it seems wasteful to compile it.
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-BETA #2: Sat Oct  3 11:34:55 CEST 1998


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 10:31:17 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA29425
          for freebsd-current-outgoing; Fri, 16 Oct 1998 10:31:17 -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 KAA29400
          for ; Fri, 16 Oct 1998 10:31:05 -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 KAA10302;
          Fri, 16 Oct 1998 10:30:33 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Date: Fri, 16 Oct 1998 10:30:32 -0700 (PDT)
From: Doug White 
To: Simon Shapiro 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper?  Failure to Install 19981014
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 Fri, 16 Oct 1998, Simon Shapiro wrote:

> newfs: ioctl (WDINFO): cros-device link
> newfs: /mnt/dev/rda0s4a cant rewrite disk label.
> 
> The disk is partitioned to have a 64MB DOS slice a 1GB FreeBSD
> slice another 1GB freeBSD slice and a slightly over 2GB FreeBSD
> slice.
[..]
> The (excessive) confirmations are an attempt to stem ``Oh, it soes not
> happen here, must be the DPT driver'' comments.  I belive it does not
> happen elsewhere but is serious enough for us to post it here in search for
> help.  We are standing by to do what is needed to make it work.

I can get IDE and SCSI disks to do the same thing; I'll go to work in an
hour and repeat it on a 400MB IDE disk, I bet.

Re-running 'commit' will work OK.

I think newfs has issues.  If you can get it to run outside of the install
environment we can backtrace it.

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 16 10:37:13 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA00407
          for freebsd-current-outgoing; Fri, 16 Oct 1998 10:37:13 -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 KAA00398
          for ; Fri, 16 Oct 1998 10:37:11 -0700 (PDT)
          (envelope-from ulf@Gatekeeper.Alameda.net)
Received:  by Gatekeeper.Alameda.net (8.8.8/8.8.6) id KAA06839;
	Fri, 16 Oct 1998 10:36:43 -0700 (PDT)
Message-ID: <19981016103643.A5694@Alameda.net>
Date: Fri, 16 Oct 1998 10:36:43 -0700
From: Ulf Zimmermann 
To: shimon@simon-shapiro.org
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper?  Failure to Install 19981014
Reply-To: ulf@Alameda.net
References:  
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: ; from Simon Shapiro on Fri, Oct 16, 1998 at 01:58:02PM -0400
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 Fri, Oct 16, 1998 at 01:58:02PM -0400, Simon Shapiro wrote:
> NewsFlash:
> 
> While the release from the 4-oct-1998 has the same error messages, it
> installs correctly.  Now, will some wise person who knowns what happened in
> between help me solve this problem?

It has been reported here already several times. Try to commit again, 
and it probably will work.

> 
> Simon
> 
> Simon Shapiro, On 16-Oct-98 you wrote:
> >  Hi Yall,
> >  
> >  I am installing, from scratch, on a known-to-be-good system, FreeBSD
> >  3.0-CURRENT, the snapshot from 14-Oct (compiled here) and getting the
> >  following error messages during filesystem creation:
> >  
> >  [ After newfs lists superblocks ]
> >  
> >  newfs: ioctl (WDINFO): cros-device link
> >  newfs: /mnt/dev/rda0s4a cant rewrite disk label.
> >  
> >  The disk is partitioned to have a 64MB DOS slice a 1GB FreeBSD
> >  slice another 1GB freeBSD slice and a slightly over 2GB FreeBSD
> >  slice.
> >  
> >  There are numerous FreeBSD partitions in each slice.  The systme has a
> >  DPT
> >  controller driving a RAID-1 array.  The very same system (and numerous
> >  others) are running IDENTICAL hardware with the very same date code
> >  without
> >  any sign of this problem. This problem has been confirmed by others and
> >  is
> >  very real.
> >  
> >  As a reference, 2.2.7 installs and boots.  Pre-CAM 3.0 installs and
> >  boots.
> >  
> >  The (excessive) confirmations are an attempt to stem ``Oh, it soes not
> >  happen here, must be the DPT driver'' comments.  I belive it does not
> >  happen elsewhere but is serious enough for us to post it here in search
> >  for
> >  help.  We are standing by to do what is needed to make it work.
> >  
> >  If you feel like chatting, I am at 770.794.1513
> >  
> >  
> >  
> >  
> >  Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
> >                                               770.265.7340
> >  Simon Shapiro
> >  
> >  Unwritten code has no bugs and executes at twice the speed of mouth
> >  
> >  
> >  To Unsubscribe: send mail to majordomo@FreeBSD.org
> >  with "unsubscribe freebsd-current" in the body of the message
> 
> 
> 
> Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
>                                              770.265.7340
> Simon Shapiro
> 
> Unwritten code has no bugs and executes at twice the speed of mouth
> 
> 
> 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  Fri Oct 16 10:37:43 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA00466
          for freebsd-current-outgoing; Fri, 16 Oct 1998 10:37:43 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00457
          for ; Fri, 16 Oct 1998 10:37:38 -0700 (PDT)
          (envelope-from root@psa.at)
Received: from uvo-108.univie.ac.at ([131.130.230.108] helo=entropy.quake.at)
	by darkstar.psa.at with esmtp (Exim 2.05 #1)
	id 0zUDoi-0003yv-00
	for freebsd-current@freebsd.org; Fri, 16 Oct 1998 19:37:33 +0200
Received: from localhost ([127.0.0.1])
	by entropy.quake.at with esmtp (Exim 2.05 #1)
	id 0zU37U-0000Kp-00; Fri, 16 Oct 1998 08:12:12 +0200
Date: Fri, 16 Oct 1998 08:12:12 +0200 (CEST)
From: Alexander Sanda 
X-Sender: root@darkstar.vmx
To: Jim Bryant 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: netscape in -current is broked
In-Reply-To: <199810160433.XAA05552@unix.tfs.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, 15 Oct 1998, Jim Bryant wrote:

> okay, i just tried installing the ports version of netscape, since my
> 4.5-beta is expiring.  since netscape seems to not be distributing 4.5
> for freebsd anymore, i went to /usr/ports...

Hm, where did you get this rumour ?

I have a native aout version of 4.5b2 (which expires not-so-soon as far
as I can remember).

However, I have made the experience, that Netscapes ftp servers are not
always in sync. Not all versions are available on every server.

> i also noticed that the ports version seems to be just a package, not
> a true source-code dist.

Sure, the complete source for communicator-4.5 isn't publically
available. Only Mozilla, but that's another story...

> i am elfen.

You'll probable have to keep the necessary aout libraries (libc, libX11,
libXt, ...) on your system. Communicator is still aout, and I'am afraid
it will stay aout for some time. I wouldn't excpect a ELF version of the
final 4.5.

-- 
# /AS/                               http://privat.schlund.de/entropy/ #
# GNU is not Unix, BSD is.                                             #


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 10:38:51 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA00577
          for freebsd-current-outgoing; Fri, 16 Oct 1998 10:38:51 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00558
          for ; Fri, 16 Oct 1998 10:38:39 -0700 (PDT)
          (envelope-from root@psa.at)
Received: from uvo-108.univie.ac.at ([131.130.230.108] helo=entropy.quake.at)
	by darkstar.psa.at with esmtp (Exim 2.05 #1)
	id 0zUDom-0003yx-00
	for current@freebsd.org; Fri, 16 Oct 1998 19:37:38 +0200
Received: from localhost ([127.0.0.1])
	by entropy.quake.at with esmtp (Exim 2.05 #1)
	id 0zUBps-0000Wu-00
	for current@freebsd.org; Fri, 16 Oct 1998 17:30:36 +0200
Date: Fri, 16 Oct 1998 17:30:36 +0200 (CEST)
From: Alexander Sanda 
X-Sender: root@darkstar.vmx
To: current@FreeBSD.ORG
Subject: How to get rid of a CLOSE_WAIT connection ?
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


Well, here is the story:

On one of my boxes, running 3.0-BETA, I mistakenly killed xinetd while I
was remotely logged in via ssh. Bad thing(tm), but I could manage to get
some guy of the office staff to log in and restart xinetd. Now, I note,
that netstat -na still shows a connection from this machine:port22 to my
former ip adress:some_port (the ip adress, I have been assigned, when
the accident happened). The connection is reported to be in CLOSE_WAIT
state.

Obviously, xinetd cannot bind to port 22, because this port is still
used, and waiting for something to happen :) In fact, the Revc-Q field
also shows a non-zero value.

Will this ever go away (it's now about 17 hrs since this happened) ?

BTW: some other thing: Now after 3.0-RELEASE has seen the world, what's
the correct cvsup tag to stay with 3.0 ? Is it RELENG_3_0 ?

-- 
# /AS/                               http://privat.schlund.de/entropy/ #
# GNU is not Unix, BSD is.                                             # 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 10:57:34 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA03599
          for freebsd-current-outgoing; Fri, 16 Oct 1998 10:57:34 -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 KAA03568
          for ; Fri, 16 Oct 1998 10:57:25 -0700 (PDT)
          (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by hub.org (8.8.8/8.8.8) with ESMTP id NAA06413
	for ; Fri, 16 Oct 1998 13:56:59 -0400 (EDT)
	(envelope-from scrappy@hub.org)
Date: Fri, 16 Oct 1998 13:56:58 -0400 (EDT)
From: "Marc G. Fournier" 
To: freebsd-current@FreeBSD.ORG
Subject: paranoid question: aout vs ELF...
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 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'...

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

From owner-freebsd-current  Fri Oct 16 11:06:04 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA05553
          for freebsd-current-outgoing; Fri, 16 Oct 1998 11:06: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 LAA05498
          for ; Fri, 16 Oct 1998 11:05:58 -0700 (PDT)
          (envelope-from ulf@Gatekeeper.Alameda.net)
Received:  by Gatekeeper.Alameda.net (8.8.8/8.8.6) id LAA08412;
	Fri, 16 Oct 1998 11:05:36 -0700 (PDT)
Message-ID: <19981016110536.A7140@Alameda.net>
Date: Fri, 16 Oct 1998 11:05:36 -0700
From: Ulf Zimmermann 
To: Doug White ,
        Simon Shapiro 
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper?  Failure to Install 19981014
Reply-To: ulf@Alameda.net
References:  
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: ; from Doug White on Fri, Oct 16, 1998 at 10:30:32AM -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 Fri, Oct 16, 1998 at 10:30:32AM -0700, Doug White wrote:
> On Fri, 16 Oct 1998, Simon Shapiro wrote:
> 
> > newfs: ioctl (WDINFO): cros-device link
> > newfs: /mnt/dev/rda0s4a cant rewrite disk label.
> > 
> > The disk is partitioned to have a 64MB DOS slice a 1GB FreeBSD
> > slice another 1GB freeBSD slice and a slightly over 2GB FreeBSD
> > slice.
> [..]
> > The (excessive) confirmations are an attempt to stem ``Oh, it soes not
> > happen here, must be the DPT driver'' comments.  I belive it does not
> > happen elsewhere but is serious enough for us to post it here in search for
> > help.  We are standing by to do what is needed to make it work.
> 
> I can get IDE and SCSI disks to do the same thing; I'll go to work in an
> hour and repeat it on a 400MB IDE disk, I bet.
> 
> Re-running 'commit' will work OK.
> 
> I think newfs has issues.  If you can get it to run outside of the install
> environment we can backtrace it.

I had the same issues with newfs outside of sysinstall, which I reported
already earlier.

> 
> 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

-- 
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  Fri Oct 16 11:14:16 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA07955
          for freebsd-current-outgoing; Fri, 16 Oct 1998 11:14:16 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA07878
          for ; Fri, 16 Oct 1998 11:14:08 -0700 (PDT)
          (envelope-from shimon@simon-shapiro.org)
Received: (qmail 29459 invoked by uid 1000); 16 Oct 1998 19:17:10 -0000
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: <19981016103643.A5694@Alameda.net>
Date: Fri, 16 Oct 1998 15:17:09 -0400 (EDT)
X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z#
 Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+
 O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc?
Reply-To: shimon@simon-shapiro.org
Organization: The Simon Shapiro Foundation
From: Simon Shapiro 
To: Ulf Zimmermann 
Subject: Re: Show Stopper?  Failure to Install 19981014
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Ulf Zimmermann, On 16-Oct-98 you wrote:
>  On Fri, Oct 16, 1998 at 01:58:02PM -0400, Simon Shapiro wrote:
> > NewsFlash:
> > 
> > While the release from the 4-oct-1998 has the same error messages, it
> > installs correctly.  Now, will some wise person who knowns what
> > happened in
> > between help me solve this problem?
>  
>  It has been reported here already several times. Try to commit again, 
>  and it probably will work.

Nope.  That did not help :-(

I did confirm that a kernel made form the same sources boots, newfs's and
runs reliably, with no error messages.

>  
> > 
> > Simon
> > 
> > Simon Shapiro, On 16-Oct-98 you wrote:
> > >  Hi Yall,
> > >  
> > >  I am installing, from scratch, on a known-to-be-good system, FreeBSD
> > >  3.0-CURRENT, the snapshot from 14-Oct (compiled here) and getting
> > >  the
> > >  following error messages during filesystem creation:
> > >  
> > >  [ After newfs lists superblocks ]
> > >  
> > >  newfs: ioctl (WDINFO): cros-device link
> > >  newfs: /mnt/dev/rda0s4a cant rewrite disk label.
> > >  
> > >  The disk is partitioned to have a 64MB DOS slice a 1GB FreeBSD
> > >  slice another 1GB freeBSD slice and a slightly over 2GB FreeBSD
> > >  slice.
> > >  
> > >  There are numerous FreeBSD partitions in each slice.  The systme has
> > >  a
> > >  DPT
> > >  controller driving a RAID-1 array.  The very same system (and
> > >  numerous
> > >  others) are running IDENTICAL hardware with the very same date code
> > >  without
> > >  any sign of this problem. This problem has been confirmed by others
> > >  and
> > >  is
> > >  very real.
> > >  
> > >  As a reference, 2.2.7 installs and boots.  Pre-CAM 3.0 installs and
> > >  boots.
> > >  
> > >  The (excessive) confirmations are an attempt to stem ``Oh, it soes
> > >  not
> > >  happen here, must be the DPT driver'' comments.  I belive it does
> > >  not
> > >  happen elsewhere but is serious enough for us to post it here in
> > >  search
> > >  for
> > >  help.  We are standing by to do what is needed to make it work.
> > >  
> > >  If you feel like chatting, I am at 770.794.1513
> > >  
> > >  
> > >  
> > >  
> > >  Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
> > >                                               770.265.7340
> > >  Simon Shapiro
> > >  
> > >  Unwritten code has no bugs and executes at twice the speed of mouth
> > >  
> > >  
> > >  To Unsubscribe: send mail to majordomo@FreeBSD.org
> > >  with "unsubscribe freebsd-current" in the body of the message
> > 
> > 
> > 
> > Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
> >                                              770.265.7340
> > Simon Shapiro
> > 
> > Unwritten code has no bugs and executes at twice the speed of mouth
> > 
> > 
> > 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



Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
                                             770.265.7340
Simon Shapiro

Unwritten code has no bugs and executes at twice the speed of mouth


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 11:15:51 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA08494
          for freebsd-current-outgoing; Fri, 16 Oct 1998 11:15:51 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA08404
          for ; Fri, 16 Oct 1998 11:15:31 -0700 (PDT)
          (envelope-from shimon@simon-shapiro.org)
Received: (qmail 29467 invoked by uid 1000); 16 Oct 1998 19:18:33 -0000
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: Fri, 16 Oct 1998 15:18:33 -0400 (EDT)
X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z#
 Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+
 O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc?
Reply-To: shimon@simon-shapiro.org
Organization: The Simon Shapiro Foundation
From: Simon Shapiro 
To: Doug White 
Subject: Re: Show Stopper?  Failure to Install 19981014
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Doug White, On 16-Oct-98 you wrote:
>  On Fri, 16 Oct 1998, Simon Shapiro wrote:
>  
> > newfs: ioctl (WDINFO): cros-device link
> > newfs: /mnt/dev/rda0s4a cant rewrite disk label.
> > 
> > The disk is partitioned to have a 64MB DOS slice a 1GB FreeBSD
> > slice another 1GB freeBSD slice and a slightly over 2GB FreeBSD
> > slice.
>  [..]
> > The (excessive) confirmations are an attempt to stem ``Oh, it soes not
> > happen here, must be the DPT driver'' comments.  I belive it does not
> > happen elsewhere but is serious enough for us to post it here in search
> > for
> > help.  We are standing by to do what is needed to make it work.
>  
>  I can get IDE and SCSI disks to do the same thing; I'll go to work in an
>  hour and repeat it on a 400MB IDE disk, I bet.
>  
>  Re-running 'commit' will work OK.
>  
>  I think newfs has issues.  If you can get it to run outside of the
>  install
>  environment we can backtrace it.

The normal newfs works without a hitch.  Do you want me to try the /stand
one on a running system?


>  
>  Doug White                               
>  Internet:  dwhite@resnet.uoregon.edu    | FreeBSD: The Power to Serve
>  http://gladstone.uoregon.edu/~dwhite    | www.freebsd.org
>  



Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
                                             770.265.7340
Simon Shapiro

Unwritten code has no bugs and executes at twice the speed of mouth


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 11:45:36 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA14846
          for freebsd-current-outgoing; Fri, 16 Oct 1998 11:45:36 -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 LAA14841
          for ; Fri, 16 Oct 1998 11:45:33 -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 OAA22577;
	Fri, 16 Oct 1998 14:44:53 -0400 (EDT)
	(envelope-from wollman)
Date: Fri, 16 Oct 1998 14:44:53 -0400 (EDT)
From: Garrett Wollman 
Message-Id: <199810161844.OAA22577@khavrinen.lcs.mit.edu>
To: "Marc G. Fournier" 
Cc: freebsd-current@FreeBSD.ORG
Subject: paranoid question: aout vs ELF...
In-Reply-To: 
References: 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

< said:

> My paranoia...all my aout stuff in /usr/local/bin won't all of a sudden
> break...will it?

Not all-of-a-sudden, but there are some dependencies which may be
tricky to resolve.  (For example, you need to break the package
dependencies in some of the Perl packages so that you can recompile
new ELF versions of Perl DynaLoaded modules without breaking the whole
universe.)  In my case it was made somewhat easier because I had not yet
updated my system to the new Perl, so all of the things I needed to
keep running during the upgrade were using the old Perl port.

-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  Fri Oct 16 11:50:21 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA15476
          for freebsd-current-outgoing; Fri, 16 Oct 1998 11:50:21 -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 LAA15468
          for ; Fri, 16 Oct 1998 11:50:19 -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 NAA10871;
	Fri, 16 Oct 1998 13:49:54 -0500 (CDT)
	(envelope-from eculp@webwizard.org.mx)
Message-ID: <36279552.F92C02DE@webwizard.org.mx>
Date: Fri, 16 Oct 1998 13:49:54 -0500
From: Edwin Culp 
X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Marc G. 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 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
    # 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


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 12:37:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA24091
          for freebsd-current-outgoing; Fri, 16 Oct 1998 12:37:58 -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 MAA24063
          for ; Fri, 16 Oct 1998 12:37:43 -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 MAA14740
	for ; Fri, 16 Oct 1998 12:37:49 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: current@FreeBSD.ORG
Subject: The src tree is unfrozen.
Date: Fri, 16 Oct 1998 12:37:49 -0700
Message-ID: <14736.908566669@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Now that 3.0 is out, commits can begin again.

- 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 16 12:47:51 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA26224
          for freebsd-current-outgoing; Fri, 16 Oct 1998 12:47: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 MAA26193
          for ; Fri, 16 Oct 1998 12:47:42 -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 MAA14874;
	Fri, 16 Oct 1998 12:47:45 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: shimon@simon-shapiro.org
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper? Failure to Install 19981014 
In-reply-to: Your message of "Fri, 16 Oct 1998 12:46:20 EDT."
              
Date: Fri, 16 Oct 1998 12:47:45 -0700
Message-ID: <14871.908567265@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I am installing, from scratch, on a known-to-be-good system, FreeBSD
> 3.0-CURRENT, the snapshot from 14-Oct (compiled here) and getting the
> following error messages during filesystem creation:
> 
> [ After newfs lists superblocks ]
> 
> newfs: ioctl (WDINFO): cros-device link
> newfs: /mnt/dev/rda0s4a cant rewrite disk label.

FWIW, I've seen this reported by 2-3 other people as well (and not
with DPT controllers) but I'm buggered if I can reproduce it here on
any of my test boxes.  Can you tell me a bit more about what installation
type you're using, whether the disks are being installed "dangerously
dedicated", are shared with other OSes, etc?

Thanks!

- 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 16 13:06:20 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA29871
          for freebsd-current-outgoing; Fri, 16 Oct 1998 13:06:20 -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 NAA29846
          for ; Fri, 16 Oct 1998 13:06:12 -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 NAA15013;
	Fri, 16 Oct 1998 13:05:42 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Alexander Sanda 
cc: current@FreeBSD.ORG
Subject: Re: How to get rid of a CLOSE_WAIT connection ? 
In-reply-to: Your message of "Fri, 16 Oct 1998 17:30:36 +0200."
              
Date: Fri, 16 Oct 1998 13:05:42 -0700
Message-ID: <15009.908568342@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> BTW: some other thing: Now after 3.0-RELEASE has seen the world, what's
> the correct cvsup tag to stay with 3.0 ? Is it RELENG_3_0 ?

Still the same as always.  "."

- 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 16 13:10:26 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA00837
          for freebsd-current-outgoing; Fri, 16 Oct 1998 13:10:26 -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 NAA00764;
          Fri, 16 Oct 1998 13:10:07 -0700 (PDT)
          (envelope-from dag-erli@ifi.uio.no)
Received: from jarnsaxa.ifi.uio.no (2602@jarnsaxa.ifi.uio.no [129.240.65.44])
	by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id WAA03720;
	Fri, 16 Oct 1998 22:08:45 +0200 (MET DST)
Received: (from dag-erli@localhost) by jarnsaxa.ifi.uio.no ; Fri, 16 Oct 1998 22:08:45 +0200 (MET DST)
Mime-Version: 1.0
To: Joe Abley 
Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: Re: Luigi's Sound Drivers on Digital PC5000
References: <19981016095632.A25175@clear.co.nz>
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: 16 Oct 1998 22:08:44 +0200
In-Reply-To: Joe Abley's message of "Fri, 16 Oct 1998 09:56:32 +1300"
Message-ID: 
Lines: 40
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 NAA00812
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Joe Abley  writes:
> Probing for PnP devices:
> CSN 1 Vendor ID: CSC0735 [0x3507630e] Serial 0xffffffff Comp ID: @@@0000 [0x0000
> 0000]
> This is a CS4236, but LDN 0 is disabled

The "LDN 0 is disabled" message seems to indicate the device has been
disabled in software. Try to add the following line to your
/kernel.config:

 pnp 1 0 os enable port0 0x534 port2 0x220 irq0 5 drq0 1 drq1 3

If you don't have a /kernel.config, create one that looks like this:

 USERCONFIG
 pnp 1 0 os enable port0 0x534 port2 0x220 irq0 5 drq0 1 drq1 3
 quit

You'll need to add the USERCONFIG and USERCONFIG_BOOT kernel options
for this to work.


This is actually a CS4236B, which should be identified as such and
properly attached by a recent kernel (built from sources newer than
October 4th):

Probing for PnP devices:
CSN 1 Vendor ID: CSC6835 [0x3568630e] Serial 0xffffffff Comp ID: @@@0000 [0x0000
0000]
mss_attach 1 at 0x530 irq 5 dma 1:3 flags 0x13
pcm1 (CS423x/Yamaha  sn 0xffffffff) at 0x530-0x537 irq 5 drq 1 flags 0x1
3 on isa

(CSC play games with their vendor ID so we ignore the second-most
significant byte of the PnP ID)


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  Fri Oct 16 13:15:25 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA01866
          for freebsd-current-outgoing; Fri, 16 Oct 1998 13:15:25 -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 NAA01844
          for ; Fri, 16 Oct 1998 13:15:14 -0700 (PDT)
          (envelope-from dag-erli@ifi.uio.no)
Received: from jarnsaxa.ifi.uio.no (2602@jarnsaxa.ifi.uio.no [129.240.65.44])
	by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id WAA04285;
	Fri, 16 Oct 1998 22:14:43 +0200 (MET DST)
Received: (from dag-erli@localhost) by jarnsaxa.ifi.uio.no ; Fri, 16 Oct 1998 22:14:42 +0200 (MET DST)
Mime-Version: 1.0
To: Andrzej Bialecki 
Cc: bryan collins , freebsd-current@FreeBSD.ORG
Subject: Re: /usr/sbin/arp: actual retrieval of routing table
References: 
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: 16 Oct 1998 22:14:42 +0200
In-Reply-To: Andrzej Bialecki's message of "Thu, 15 Oct 1998 09:37:33 +0200 (CEST)"
Message-ID: 
Lines: 15
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 NAA01855
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Andrzej Bialecki  writes:
> If your machine is quite busy adding/deleteing routes, I can understand
> this. When you retrieve a bigger chunk of data from the kernel, you first
> do the "sizing" of the memory needed, then you actually retrieve the data
> - 'arp' does exactly this. If the actual routing table grows between these
> two sysctl(3) calls, the data wouldn't fit and sysctl(3) refuses to
> transfer them to your buffer.

Write up a PR and set me (des) as responsible, and I'll fix it ASAP.
I've already fixed a similar bug in libkvm so I know precisely how to
lick it. Not right now though...

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  Fri Oct 16 13:34:21 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA07197
          for freebsd-current-outgoing; Fri, 16 Oct 1998 13:34:21 -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 NAA07107
          for ; Fri, 16 Oct 1998 13:34:00 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from daemon@localhost)
	by smtp02.primenet.com (8.8.8/8.8.8) id NAA19613;
	Fri, 16 Oct 1998 13:33:36 -0700 (MST)
Received: from usr04.primenet.com(206.165.6.204)
 via SMTP by smtp02.primenet.com, id smtpd019579; Fri Oct 16 13:33:32 1998
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id NAA26303;
	Fri, 16 Oct 1998 13:33:31 -0700 (MST)
From: Terry Lambert 
Message-Id: <199810162033.NAA26303@usr04.primenet.com>
Subject: Re: Limits Problems ...
To: jdp@polstra.com (John Polstra)
Date: Fri, 16 Oct 1998 20:33:31 +0000 (GMT)
Cc: current@FreeBSD.ORG
In-Reply-To: <199810160420.VAA08999@austin.polstra.com> from "John Polstra" at Oct 15, 98 09:20: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

> > > This is a known bug in 3.0, most commonly affecting laptop users.   We 
> > > haven't been able to track down the exact cause of it.
> > 
> > It's quite interesting that something like this isn't considered a little
> > more important.
> 
> The most accurate indicator of how important a problem is to a person
> is the number of hours he has spent working on diagnosing it and
> fixing it.  Under that metric, how important is it to YOU?

Very.

I can easily get rid of it by reverting the clock code.


					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 16 13:36:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA07776
          for freebsd-current-outgoing; Fri, 16 Oct 1998 13:36:59 -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 NAA07717
          for ; Fri, 16 Oct 1998 13:36:46 -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 NAA14745;
	Fri, 16 Oct 1998 13:36:23 -0700 (PDT)
	(envelope-from jdp)
Message-Id: <199810162036.NAA14745@austin.polstra.com>
To: Terry Lambert 
cc: current@FreeBSD.ORG
Subject: Re: Limits Problems ... 
In-reply-to: Your message of "Fri, 16 Oct 1998 20:33:31 -0000."
    <199810162033.NAA26303@usr04.primenet.com> 
Date: Fri, 16 Oct 1998 13:36:23 -0700
From: John Polstra 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > The most accurate indicator of how important a problem is to a
> > person is the number of hours he has spent working on diagnosing
> > it and fixing it.  Under that metric, how important is it to YOU?
>
> Very.
>
> I can easily get rid of it by reverting the clock code.

Reverting != diagnosing and fixing.
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 13:52:46 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA11972
          for freebsd-current-outgoing; Fri, 16 Oct 1998 13:52:46 -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 NAA11907
          for ; Fri, 16 Oct 1998 13:52:29 -0700 (PDT)
          (envelope-from ulf@Gatekeeper.Alameda.net)
Received:  by Gatekeeper.Alameda.net (8.8.8/8.8.6) id NAA16380;
	Fri, 16 Oct 1998 13:52:01 -0700 (PDT)
Message-ID: <19981016135201.A10465@Alameda.net>
Date: Fri, 16 Oct 1998 13:52:01 -0700
From: Ulf Zimmermann 
To: "Jordan K. Hubbard" , shimon@simon-shapiro.org
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper? Failure to Install 19981014
Reply-To: ulf@Alameda.net
References:  <14871.908567265@time.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <14871.908567265@time.cdrom.com>; from Jordan K. Hubbard on Fri, Oct 16, 1998 at 12:47:45PM -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 Fri, Oct 16, 1998 at 12:47:45PM -0700, Jordan K. Hubbard wrote:
> > I am installing, from scratch, on a known-to-be-good system, FreeBSD
> > 3.0-CURRENT, the snapshot from 14-Oct (compiled here) and getting the
> > following error messages during filesystem creation:
> > 
> > [ After newfs lists superblocks ]
> > 
> > newfs: ioctl (WDINFO): cros-device link
> > newfs: /mnt/dev/rda0s4a cant rewrite disk label.
> 
> FWIW, I've seen this reported by 2-3 other people as well (and not
> with DPT controllers) but I'm buggered if I can reproduce it here on
> any of my test boxes.  Can you tell me a bit more about what installation
> type you're using, whether the disks are being installed "dangerously
> dedicated", are shared with other OSes, etc?

I had the following configs:

Celeron with IDE drive: made one partition, then disklabeled for
	/, /var, /usr and /usr/local. Failed on /, worked commiting
	again. Tried sysinstall only.

K6-233 with Adaptec 2940UW:
	4GB SCSI drive for /, /usr, /usr/local and /var. Failed
	with sysinstall, recommitted and worked.
	2x9GB SCSI disks, configured as ccd0, newfs first time
	fails, tried newfs again fails, but the file system
	is mountable.
K6-200 with IDE drive 4GB: two partition, 2GB for Win95, 2GB for
	FreeBSD. Made disklabel with sysinstall, 1. commit fails
	on /, second worked.


> 
> Thanks!
> 
> - Jordan
> 
> 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  Fri Oct 16 13:55:09 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA12491
          for freebsd-current-outgoing; Fri, 16 Oct 1998 13:55:09 -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 NAA12462;
          Fri, 16 Oct 1998 13:54:55 -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 NAA22095;
          Fri, 16 Oct 1998 13:54:25 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Date: Fri, 16 Oct 1998 13:54:25 -0700 (PDT)
From: Doug White 
To: Joe Abley 
cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: Re: Luigi's Sound Drivers on Digital PC5000
In-Reply-To: <19981016095632.A25175@clear.co.nz>
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, Joe Abley wrote:

> I am running FreeBSD 3.0-BETA, CVSUPped a few days ago, on a P2
> Digital PC5000 with some kind of (supposedly sb16- and wss-compatible)
> on-board audio.

ok.

> I have the following in my kernel config:
> 
> controller      pnp0
> device          pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 vector pcmintr

ok.

> I get the following on boot:
> 
> ...
> Probing for PnP devices:
> CSN 1 Vendor ID: CSC0735 [0x3507630e] Serial 0xffffffff Comp ID: @@@0000 [0x0000
> 0000]
> This is a CS4236, but LDN 0 is disabled
> Probing for devices on the ISA bus:
> sc0 at 0x60-0x6f irq 1 on motherboard
> sc0: VGA color <16 virtual consoles, flags=0x0>
> pcm0 not found
> ...
> 
> What is LDN 0? Why is it disabled?

LDN is Logical Device Number, it's a PNP thing.

You can do one of these two:

1.  Go into the BIOS Setup and Set PnP OS to No.

.OR.


2. Boot -c and type at the config> prompt:

pnp 1 0 os enable port0 0x530 irq0 5 drq0 1 drq1 3

quit and your card should come up.  Change the resources if necessary.

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 16 13:56:10 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA12634
          for freebsd-current-outgoing; Fri, 16 Oct 1998 13:56:10 -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 NAA12590
          for ; Fri, 16 Oct 1998 13:55:56 -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 NAA15468;
	Fri, 16 Oct 1998 13:55:50 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: ulf@Alameda.net
cc: shimon@simon-shapiro.org, freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper? Failure to Install 19981014 
In-reply-to: Your message of "Fri, 16 Oct 1998 13:52:01 PDT."
             <19981016135201.A10465@Alameda.net> 
Date: Fri, 16 Oct 1998 13:55:49 -0700
Message-ID: <15464.908571349@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I had the following configs:

I still need to know:  Dedicated?  Non-dedicated?  Shared?

- 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 16 14:15:36 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA17506
          for freebsd-current-outgoing; Fri, 16 Oct 1998 14:15:36 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA17373
          for ; Fri, 16 Oct 1998 14:15:12 -0700 (PDT)
          (envelope-from shimon@simon-shapiro.org)
Received: (qmail 7240 invoked by uid 1000); 16 Oct 1998 22:18:07 -0000
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: <14871.908567265@time.cdrom.com>
Date: Fri, 16 Oct 1998 18:18:07 -0400 (EDT)
X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z#
 Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+
 O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc?
Reply-To: shimon@simon-shapiro.org
Organization: The Simon Shapiro Foundation
From: Simon Shapiro 
To: "Jordan K. Hubbard" 
Subject: Re: Show Stopper? Failure to Install 19981014
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Jordan K. Hubbard, On 16-Oct-98 you wrote:
> > I am installing, from scratch, on a known-to-be-good system, FreeBSD
> > 3.0-CURRENT, the snapshot from 14-Oct (compiled here) and getting the
> > following error messages during filesystem creation:
> > 
> > [ After newfs lists superblocks ]
> > 
> > newfs: ioctl (WDINFO): cros-device link
> > newfs: /mnt/dev/rda0s4a cant rewrite disk label.
>  
>  FWIW, I've seen this reported by 2-3 other people as well (and not
>  with DPT controllers) but I'm buggered if I can reproduce it here on
>  any of my test boxes.  Can you tell me a bit more about what
>  installation
>  type you're using, whether the disks are being installed "dangerously
>  dedicated", are shared with other OSes, etc?

I can reliablyreproduce it at will.

Novice installation, creating an fdisk partition with 1 DOS partition in
da0s1a, a 1024MB type 165 in da0s2 and da0s3, and a 2GB+ (or whatever is
left over) in da0s4.

Freebsd labls chop these into root, tmp, var, var/tmp, var/spool, var/log,
var/qmail, var/account, usr, usr/X11R6, usr/local, usr/local/pgsql,
usr/local/pgsql/data, home, SourceControl, Archives, and so on.

If you want, drop me a line and I'll let you in to the machine in question.


Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
                                             770.265.7340
Simon Shapiro

Unwritten code has no bugs and executes at twice the speed of mouth


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 14:45:22 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA24045
          for freebsd-current-outgoing; Fri, 16 Oct 1998 14:45:22 -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 OAA24000
          for ; Fri, 16 Oct 1998 14:44:57 -0700 (PDT)
          (envelope-from ulf@Gatekeeper.Alameda.net)
Received:  by Gatekeeper.Alameda.net (8.8.8/8.8.6) id OAA18746;
	Fri, 16 Oct 1998 14:44:33 -0700 (PDT)
Message-ID: <19981016144432.A18717@Alameda.net>
Date: Fri, 16 Oct 1998 14:44:32 -0700
From: Ulf Zimmermann 
To: "Jordan K. Hubbard" 
Cc: shimon@simon-shapiro.org, freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper? Failure to Install 19981014
Reply-To: ulf@Alameda.net
References: <19981016135201.A10465@Alameda.net> <15464.908571349@time.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <15464.908571349@time.cdrom.com>; from Jordan K. Hubbard on Fri, Oct 16, 1998 at 01:55:49PM -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 Fri, Oct 16, 1998 at 01:55:49PM -0700, Jordan K. Hubbard wrote:
> > I had the following configs:
> 
> I still need to know:  Dedicated?  Non-dedicated?  Shared?

Two machines were FreeBSD only, but in a normal partition.
One machine was paritioned into two 2GB partitions, one being
primary FAT, one being FreeBSD. Inside of the partitions always
slices for swap, /, /usr and /var at least.
> 
> - Jordan

-- 
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  Fri Oct 16 14:59:12 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA26111
          for freebsd-current-outgoing; Fri, 16 Oct 1998 14:59:12 -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 OAA25983
          for ; Fri, 16 Oct 1998 14:58:32 -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 PAA02313;
	Fri, 16 Oct 1998 15:01:48 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810162201.PAA02313@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: ulf@Alameda.net
cc: "Jordan K. Hubbard" , shimon@simon-shapiro.org,
        freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper? Failure to Install 19981014 
In-reply-to: Your message of "Fri, 16 Oct 1998 14:44:32 PDT."
             <19981016144432.A18717@Alameda.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Oct 1998 15:01:48 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Fri, Oct 16, 1998 at 01:55:49PM -0700, Jordan K. Hubbard wrote:
> > > I had the following configs:
> > 
> > I still need to know:  Dedicated?  Non-dedicated?  Shared?
> 
> Two machines were FreeBSD only, but in a normal partition.
> One machine was paritioned into two 2GB partitions, one being
> primary FAT, one being FreeBSD. Inside of the partitions always
> slices for swap, /, /usr and /var at least.

Uh, Ulf, your terminology is screwy; you can't put slices inside 
partitions, and you're still being too vague.

With the "FreeBSD only" machines, you have a single slice with all your 
partitions inside it, right?

-- 
\\  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 16 15:13:44 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA29187
          for freebsd-current-outgoing; Fri, 16 Oct 1998 15:13:44 -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 PAA29161
          for ; Fri, 16 Oct 1998 15:13: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 PAA02391;
	Fri, 16 Oct 1998 15:16:08 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810162216.PAA02391@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: ulf@Alameda.net
cc: Mike Smith , "Jordan K. Hubbard" ,
        shimon@simon-shapiro.org, freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper? Failure to Install 19981014 
In-reply-to: Your message of "Fri, 16 Oct 1998 15:01:27 PDT."
             <19981016150127.B18717@Alameda.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Oct 1998 15:16:08 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > With the "FreeBSD only" machines, you have a single slice with all your 
> > partitions inside it, right?
> 
> Sorry, let me name it different:
> 
> sysinstall->Partition->Create one partition, size it as full disk, but not
> 	               dedicated.
> sysinstall->Disklabel->Create swap (128 or 256MB)
> sysinstall->Disklabel->Create root (usual 100 or 200MB)
> sysinstall->Disklabel->Create /usr (usual ~500MB)
> sysinstall->Disklabel->Create /var (usual 100 or 200MB)
> sysinstall->Disklabel->Create /usr/local (using the rest of the space)
> 
> This is the usual order I enter the file systems in the sysinstall Disklabel.

I'm working on the details right now, but you *must* create root and 
swap in that order.  Doing it the other way around confuses something; 
I'm not yet sure what.

This was pointed out by another poster several days ago.

-- 
\\  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 16 15:29:50 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA01908
          for freebsd-current-outgoing; Fri, 16 Oct 1998 15:29:50 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.camalott.com (mail.camalott.com [208.203.140.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01889
          for ; Fri, 16 Oct 1998 15:29:43 -0700 (PDT)
          (envelope-from joelh@gnu.org)
Received: from detlev.UUCP (tex-63.camalott.com [208.229.74.63])
	by mail.camalott.com (8.8.7/8.8.7) with ESMTP id RAA12406;
	Fri, 16 Oct 1998 17:31:21 -0500
Received: (from joelh@localhost)
	by detlev.UUCP (8.9.1/8.9.1) id HAA02690;
	Fri, 16 Oct 1998 07:14:12 -0500 (CDT)
	(envelope-from joelh)
To: Terry Lambert 
Cc: current@FreeBSD.ORG
Subject: Re: -current NFS problem
References: <199810160004.RAA28932@usr04.primenet.com>
From: Joel Ray Holveck 
Date: 16 Oct 1998 07:14:12 -0500
In-Reply-To: Terry Lambert's message of "Fri, 16 Oct 1998 00:04:51 +0000 (GMT)"
Message-ID: <86d87soga3.fsf@detlev.UUCP>
Lines: 14
X-Mailer: Gnus v5.5/Emacs 20.3
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?

Best,
joelh

-- 
Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan
   Fourth law of programming:
   Anything that can go wrong wi
sendmail: segmentation violation - core dumped

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 15:34:24 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA02655
          for freebsd-current-outgoing; Fri, 16 Oct 1998 15:34:24 -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 PAA02649
          for ; Fri, 16 Oct 1998 15:34:21 -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 PAA02507;
	Fri, 16 Oct 1998 15:37:50 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810162237.PAA02507@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: shimon@simon-shapiro.org
cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper? Failure to Install 19981014 
In-reply-to: Your message of "Fri, 16 Oct 1998 18:18:07 EDT."
              
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Oct 1998 15:37:49 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> Jordan K. Hubbard, On 16-Oct-98 you wrote:
> > > I am installing, from scratch, on a known-to-be-good system, FreeBSD
> > > 3.0-CURRENT, the snapshot from 14-Oct (compiled here) and getting the
> > > following error messages during filesystem creation:
> > > 
> > > [ After newfs lists superblocks ]
> > > 
> > > newfs: ioctl (WDINFO): cros-device link
> > > newfs: /mnt/dev/rda0s4a cant rewrite disk label.
> >  
> >  FWIW, I've seen this reported by 2-3 other people as well (and not
> >  with DPT controllers) but I'm buggered if I can reproduce it here on
> >  any of my test boxes.  Can you tell me a bit more about what
> >  installation
> >  type you're using, whether the disks are being installed "dangerously
> >  dedicated", are shared with other OSes, etc?
> 
> I can reliablyreproduce it at will.
> 
> Novice installation, creating an fdisk partition with 1 DOS partition in
> da0s1a, a 1024MB type 165 in da0s2 and da0s3, and a 2GB+ (or whatever is
> left over) in da0s4.
> 
> Freebsd labls chop these into root, tmp, var, var/tmp, var/spool, var/log,
> var/qmail, var/account, usr, usr/X11R6, usr/local, usr/local/pgsql,
> usr/local/pgsql/data, home, SourceControl, Archives, and so on.
> 
> If you want, drop me a line and I'll let you in to the machine in question.

It appears to be caused by not entering the root filesystem first.
There's a test in the disklabel code which checks to see if the
partition you have open to write the label starts at 0, and if not then
it defaults to the 'a' partition.

Partitions are laid on disk in the order that you enter them.  The 'a' 
partition is always reserved for the partition you mount on /.  If you 
don't enter this partition first, it won't be at the beginning of the 
disk, and any attempt to rewrite the disklabel will fail.

Due to the way that sysinstall interacts with libdisk, this is 
difficult to get "right".  We probably need a bandaid which insists 
that if you want to create an 'a' partition you must lay it down first.
-- 
\\  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 16 15:47:02 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA04768
          for freebsd-current-outgoing; Fri, 16 Oct 1998 15:47:02 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04749
          for ; Fri, 16 Oct 1998 15:46:56 -0700 (PDT)
          (envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
	by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id SAA01140;
	Fri, 16 Oct 1998 18:50:51 -0400 (EDT)
	(envelope-from matt@zigg.com)
Date: Fri, 16 Oct 1998 18:50:50 -0400 (EDT)
From: Matt Behrens 
To: "Jordan K. Hubbard" 
cc: current@FreeBSD.ORG
Subject: Re: sysinstall "probing devices" hangs only on 3.0-199810??-BETA,
 not on 2.2.7-RELEASE boot disk 
In-Reply-To: <13174.908537044@time.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

First time I tried it, it seemed to hang after the ep0 probe returned
"not found at 0x300".  It had probed all my hardware up until that
point correctly, however.

What comes after ep0 in the default lineup?  Maybe I can try
disabling that.

On Fri, 16 Oct 1998, Jordan K. Hubbard wrote:

> > I can't start the 3.0-19981009-BETA or 3.0-19981015-BETA install
> > process because sysinstall is hanging at the "probing devices, this
> > may take a while" screen.  Upon switching to the second VT, the
> > final DEBUG message is either (forgive my paraphrasing please)
> 
> I saw that once myself, but only when I went and trimmed out
> everything and its brother with the visual userconfig.  When I just
> whacked return the next time through, editing nothing in the kernel
> configuration, it went fine.  Could you perhaps try this so we could
> narrow things down a bit?
> 
> - Jordan
> 

Matt Behrens    | If only I could learn Japanese and get my
Servant of Karen Behrens       | hands on all 200 Sailor Moon episodes and
Engineer, Nameless IRC Network | all the movies, I think my life would
I eat Penguins for breakfast.  | finally be complete. . . . . . . . . . .


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 15:51:33 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA05689
          for freebsd-current-outgoing; Fri, 16 Oct 1998 15:51:33 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05666
          for ; Fri, 16 Oct 1998 15:51:17 -0700 (PDT)
          (envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
	by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id SAA01175;
	Fri, 16 Oct 1998 18:55:18 -0400 (EDT)
	(envelope-from matt@zigg.com)
Date: Fri, 16 Oct 1998 18:55:17 -0400 (EDT)
From: Matt Behrens 
To: "Jordan K. Hubbard" 
cc: current@FreeBSD.ORG
Subject: Re: sysinstall "probing devices" hangs only on 3.0-199810??-BETA,
 not on 2.2.7-RELEASE boot disk 
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

Wahoo!  I disabled the one following ep0 in the visual userconfig
(Intel EtherExpress, I forget which one exactly) and she booted
right in.  Thanks a lot, Jordan.  You're the greatest. :)

On Fri, 16 Oct 1998, Matt Behrens wrote:

> First time I tried it, it seemed to hang after the ep0 probe returned
> "not found at 0x300".  It had probed all my hardware up until that
> point correctly, however.
> 
> What comes after ep0 in the default lineup?  Maybe I can try
> disabling that.
> 
> On Fri, 16 Oct 1998, Jordan K. Hubbard wrote:
> 
> > > I can't start the 3.0-19981009-BETA or 3.0-19981015-BETA install
> > > process because sysinstall is hanging at the "probing devices, this
> > > may take a while" screen.  Upon switching to the second VT, the
> > > final DEBUG message is either (forgive my paraphrasing please)
> > 
> > I saw that once myself, but only when I went and trimmed out
> > everything and its brother with the visual userconfig.  When I just
> > whacked return the next time through, editing nothing in the kernel
> > configuration, it went fine.  Could you perhaps try this so we could
> > narrow things down a bit?
> > 
> > - Jordan
> > 
> 
> Matt Behrens    | If only I could learn Japanese and get my
> Servant of Karen Behrens       | hands on all 200 Sailor Moon episodes and
> Engineer, Nameless IRC Network | all the movies, I think my life would
> I eat Penguins for breakfast.  | finally be complete. . . . . . . . . . .
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

Matt Behrens    | If only I could learn Japanese and get my
Servant of Karen Behrens       | hands on all 200 Sailor Moon episodes and
Engineer, Nameless IRC Network | all the movies, I think my life would
I eat Penguins for breakfast.  | finally be complete. . . . . . . . . . .


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 16:00:50 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA07350
          for freebsd-current-outgoing; Fri, 16 Oct 1998 16:00:50 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07202
          for ; Fri, 16 Oct 1998 16:00:22 -0700 (PDT)
          (envelope-from dhw@whistle.com)
Received: (from dhw@localhost)
	by pau-amma.whistle.com (8.8.8/8.8.7) id PAA09598
	for freebsd-current@FreeBSD.ORG; Fri, 16 Oct 1998 15:59:28 -0700 (PDT)
	(envelope-from dhw)
Date: Fri, 16 Oct 1998 15:59:28 -0700 (PDT)
From: David Wolfskill 
Message-Id: <199810162259.PAA09598@pau-amma.whistle.com>
Subject: Re: Show Stopper? Failure to Install 19981014
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <199810162237.PAA02507@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Date: Fri, 16 Oct 1998 15:37:49 -0700
>From: Mike Smith 

>Partitions are laid on disk in the order that you enter them.  The 'a' 
>partition is always reserved for the partition you mount on /.

Which is fairly reasonable for an initial install.

But for subsequent customization (such as adding a new disk, or
partitioning a disk that is destined to become a new boot disk), it can
be a fair nuisance.  (Yes, I realize I'm veering rather off-subject...
but I've needed to deal with this a few too many times lately.)

>Due to the way that sysinstall interacts with libdisk, this is 
>difficult to get "right".  We probably need a bandaid which insists 
>that if you want to create an 'a' partition you must lay it down first.

Well, I've tried resorting to using sysinstall to do the partitioning,
then "disklabel -r -e" to change the partition names back to what I wanted
in the first place.  It worked out, but I'd have difficulty recommending
the approach.

david
-- 
David Wolfskill		UNIX System Administrator
dhw@whistle.com		voice: (650) 577-7158	pager: (650) 371-4621

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 16:07:08 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA08990
          for freebsd-current-outgoing; Fri, 16 Oct 1998 16:07:08 -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 QAA08949
          for ; Fri, 16 Oct 1998 16:06:52 -0700 (PDT)
          (envelope-from ulf@Gatekeeper.Alameda.net)
Received:  by Gatekeeper.Alameda.net (8.8.8/8.8.6) id QAA22574;
	Fri, 16 Oct 1998 16:06:18 -0700 (PDT)
Message-ID: <19981016160618.A22426@Alameda.net>
Date: Fri, 16 Oct 1998 16:06:18 -0700
From: Ulf Zimmermann 
To: Mike Smith 
Cc: "Jordan K. Hubbard" , shimon@simon-shapiro.org,
        freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper? Failure to Install 19981014
Reply-To: ulf@Alameda.net
References: <19981016150127.B18717@Alameda.net> <199810162216.PAA02391@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199810162216.PAA02391@dingo.cdrom.com>; from Mike Smith on Fri, Oct 16, 1998 at 03:16:08PM -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 Fri, Oct 16, 1998 at 03:16:08PM -0700, Mike Smith wrote:
> > > With the "FreeBSD only" machines, you have a single slice with all your 
> > > partitions inside it, right?
> > 
> > Sorry, let me name it different:
> > 
> > sysinstall->Partition->Create one partition, size it as full disk, but not
> > 	               dedicated.
> > sysinstall->Disklabel->Create swap (128 or 256MB)
> > sysinstall->Disklabel->Create root (usual 100 or 200MB)
> > sysinstall->Disklabel->Create /usr (usual ~500MB)
> > sysinstall->Disklabel->Create /var (usual 100 or 200MB)
> > sysinstall->Disklabel->Create /usr/local (using the rest of the space)
> > 
> > This is the usual order I enter the file systems in the sysinstall Disklabel.
> 
> I'm working on the details right now, but you *must* create root and 
> swap in that order.  Doing it the other way around confuses something; 
> I'm not yet sure what.
> 
> This was pointed out by another poster several days ago.
> 

I know that is was pointed out, but I also had problems with newfs on
a ccd, which was not done via sysinstall and has no swap at all (just
one large fs).

> -- 
> \\  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
> 

-- 
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  Fri Oct 16 16:20:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA11568
          for freebsd-current-outgoing; Fri, 16 Oct 1998 16:20:35 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11477
          for ; Fri, 16 Oct 1998 16:20:12 -0700 (PDT)
          (envelope-from dhw@whistle.com)
Received: (from dhw@localhost)
	by pau-amma.whistle.com (8.8.8/8.8.7) id QAA09684
	for freebsd-current@freebsd.org; Fri, 16 Oct 1998 16:19:25 -0700 (PDT)
	(envelope-from dhw)
Date: Fri, 16 Oct 1998 16:19:25 -0700 (PDT)
From: David Wolfskill 
Message-Id: <199810162319.QAA09684@pau-amma.whistle.com>
To: freebsd-current@FreeBSD.ORG
Subject: inetd, again, with a slightly different mode of failure
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is more of a "heads-up" than anything else, especially given the
lack of diagnostic detail....

One of my colleagues has a couple of machines running -current:

FreeBSD crab.whistle.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Tue Sep 22 13:39:07 PDT 1998     root@:/crab/home1/usr/current/freebsd/src/sys/compile/CRAB  i386

FreeBSD lax.whistle.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Wed Aug 19 16:00:50 PDT 1998     eoldford@lax.whistle.com:/usr/src/sys/compile/LAX  i386


He tells me that their level of -currency is the same.  (I don't run
-current myself, which is one reason this is short on detail).

The salient differences of which I am aware are:

* crab is utilized significantly more heavily than lax is.  Indeed,
  characterizing lax as "underutilized" would be reasonable.

* inetd behaves as might reasonably be expected on lax, while on crab,
  it occasionally (every 2 - 4 days) seems to forget how to exec certain
  programs:

Oct 16 15:03:01 crab inetd[28051]: cannot execute : No such file or directory
Oct 16 15:03:01 crab inetd[26067]: [28051]: exit status 0x4700
Oct 16 15:03:11 crab inetd[28188]: cannot execute : No such file or directory
Oct 16 15:03:11 crab inetd[26067]: [28188]: exit status 0x4700
Oct 16 15:03:21 crab inetd[28285]: cannot execute : No such file or directory
Oct 16 15:03:21 crab inetd[26067]: [28285]: exit status 0x4700
Oct 16 15:08:20 crab sudo:      dhw : TTY=ttyq9 ; PWD=/a/pau-amma/root/pau-amma/home/dhw ; COMMAND=/usr/bin/whoami 
Oct 16 15:08:46 crab sudo:      dhw : TTY=ttyq9 ; PWD=/a/pau-amma/root/pau-amma/home/dhw ; COMMAND=/bin/kill 26067 
Oct 16 15:08:46 crab sudo:      dhw : TTY=ttyq9 ; PWD=/a/pau-amma/root/pau-amma/home/dhw ; COMMAND=/usr/sbin/inetd


The "cannot execute" whines were referring to the following line from
/etc/inetd.conf:

amanda	dgram	udp	wait	operator	/usr/local/libexec/amanda/amandad	amandad


And, as the above excerpt from /var/log/messages shows, I killed &
re-started inetd; I then re-ran the "amcheck"... and everything was
fine:

> amcheck -c Engineering

Amanda Backup Client Hosts Check
--------------------------------
Client check: 19 hosts checked in 5.685 seconds, 0 problems found.

(brought to you by Amanda 2.4.2)


(The whines quoted above were from a cron-initiated "amcheck".)


Anyway, I mention this in order to let folks know that this kind of
symptom is being seen (here, at least), though so far, I've only seen it
on this one machine.

david
-- 
David Wolfskill		UNIX System Administrator
dhw@whistle.com		voice: (650) 577-7158	pager: (650) 371-4621

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 17:02:43 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA27000
          for freebsd-current-outgoing; Fri, 16 Oct 1998 15:03:38 -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 PAA26762
          for ; Fri, 16 Oct 1998 15:02:11 -0700 (PDT)
          (envelope-from ulf@Gatekeeper.Alameda.net)
Received:  by Gatekeeper.Alameda.net (8.8.8/8.8.6) id PAA19643;
	Fri, 16 Oct 1998 15:01:27 -0700 (PDT)
Message-ID: <19981016150127.B18717@Alameda.net>
Date: Fri, 16 Oct 1998 15:01:27 -0700
From: Ulf Zimmermann 
To: Mike Smith 
Cc: "Jordan K. Hubbard" , shimon@simon-shapiro.org,
        freebsd-current@FreeBSD.ORG
Subject: Re: Show Stopper? Failure to Install 19981014
Reply-To: ulf@Alameda.net
References: <19981016144432.A18717@Alameda.net> <199810162201.PAA02313@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199810162201.PAA02313@dingo.cdrom.com>; from Mike Smith on Fri, Oct 16, 1998 at 03:01:48PM -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 Fri, Oct 16, 1998 at 03:01:48PM -0700, Mike Smith wrote:
> > On Fri, Oct 16, 1998 at 01:55:49PM -0700, Jordan K. Hubbard wrote:
> > > > I had the following configs:
> > > 
> > > I still need to know:  Dedicated?  Non-dedicated?  Shared?
> > 
> > Two machines were FreeBSD only, but in a normal partition.
> > One machine was paritioned into two 2GB partitions, one being
> > primary FAT, one being FreeBSD. Inside of the partitions always
> > slices for swap, /, /usr and /var at least.
> 
> Uh, Ulf, your terminology is screwy; you can't put slices inside 
> partitions, and you're still being too vague.
> 
> With the "FreeBSD only" machines, you have a single slice with all your 
> partitions inside it, right?

Sorry, let me name it different:

sysinstall->Partition->Create one partition, size it as full disk, but not
	               dedicated.
sysinstall->Disklabel->Create swap (128 or 256MB)
sysinstall->Disklabel->Create root (usual 100 or 200MB)
sysinstall->Disklabel->Create /usr (usual ~500MB)
sysinstall->Disklabel->Create /var (usual 100 or 200MB)
sysinstall->Disklabel->Create /usr/local (using the rest of the space)

This is the usual order I enter the file systems in the sysinstall Disklabel.

> 
> -- 
> \\  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
> 

-- 
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  Fri Oct 16 17:23:06 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA23638
          for freebsd-current-outgoing; Fri, 16 Oct 1998 17:23:06 -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 RAA23556
          for ; Fri, 16 Oct 1998 17:22:33 -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 UAA01772
	for ; Fri, 16 Oct 1998 20:22:05 -0400 (EDT)
Date: Fri, 16 Oct 1998 20:22:05 -0400 (EDT)
To: freebsd-current@FreeBSD.ORG
Subject: 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

Hello,

I'm attempting to give 3.0-RELEASE a try on my Toshiba 4015CDT.  3.0
recognizes everything (flawlessley, I might add) at bootup.

Everything goes smoothly until I attempt to start the actual transfer
of information from the FTP site and sysinstall starts doing a newfs
to prepare my drive...  Sysinstall then gets rather upset and says,
"Unable to make new root filesystem on /dev/rwd0s2a!" and I have to
abort.

ALT-F2 yields:

newfs: ioctl (WDINFO): Cross-device link
newfs: /dev/rwd0s2a: can't rewrite disk label

Is my partition table just fubar?  2.2.7-RELEASE chugs happily along.

I got the same thing with the last 3.0-BETA release on a PPro SMP box
I was playing with the other day.  On the SMP box, it was calling my
SCSI drives daX instead of sdX - is this the new terminology?  Just
curious.  :)  I fell back to an older SNAP (5/20 I believe) I'd been
running on a similarly-configured box with no problems.

Thanks in advance for any help...

	-mike


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 17:59:23 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA29156
          for freebsd-current-outgoing; Fri, 16 Oct 1998 17:59:23 -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 RAA29147
          for ; Fri, 16 Oct 1998 17:59:18 -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 UAA23740
	for ; Fri, 16 Oct 1998 20:58:51 -0400 (EDT)
Date: Fri, 16 Oct 1998 20:58:51 -0400 (EDT)
From: Brian Feldman 
To: current@FreeBSD.ORG
Subject: modules/atapi change
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

@ is linked to /usr/src/sys/sys
Of course, it should be linked with /usr/src/sys. Peter, if I knew how to
fix the Makefile, I would.

Cheers,
Brian Feldman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 18:08:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA01112
          for freebsd-current-outgoing; Fri, 16 Oct 1998 18:08:58 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from top.worldcontrol.com (209-239-204-165.oak.jps.net [209.239.204.165])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA01084
          for ; Fri, 16 Oct 1998 18:08:53 -0700 (PDT)
          (envelope-from brian@worldcontrol.com)
From: brian@worldcontrol.com
Received: (qmail 20831 invoked by uid 100); 17 Oct 1998 01:08:51 -0000
Date: Fri, 16 Oct 1998 18:08:51 -0700
To: freebsd-current@FreeBSD.ORG
Subject: Re: wine on current: bad system call (semsys)
Message-ID: <19981016180850.A20813@top.worldcontrol.com>
Mail-Followup-To: freebsd-current@freebsd.org
References: <199810161211.OAA02251@mp.virtual-earth.de> <36276B40.EB20EA55@gorean.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.6i
In-Reply-To: <36276B40.EB20EA55@gorean.org>; from Studded on Fri, Oct 16, 1998 at 08:50:24AM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Oct 16, 1998 at 08:50:24AM -0700, Studded wrote:
> 	If quickbooks is not a networked app, try bochs instead. Depending on
> wine for any real work is not a good thing. The wine people are
> notoriously linux-centric, and don't really care to change.

I did not find the "wine people" to be notoriously linux-centric.  In
fact I found them more helpful than the "freebsd people" in my
efforts to get wine running under FreeBSD.

As for the bad system call, I found I had to include all of

options         SYSVSHM
options         SYSVSEM
options         SYSVMSG
options         USER_LDT

in my kernel conf file to get things working under -current/elf.




-- 
Brian Litzinger 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 18:28:49 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA05393
          for freebsd-current-outgoing; Fri, 16 Oct 1998 18:28:49 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05374
          for ; Fri, 16 Oct 1998 18:28:35 -0700 (PDT)
          (envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
	by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id VAA01522;
	Fri, 16 Oct 1998 21:32:36 -0400 (EDT)
	(envelope-from matt@zigg.com)
Date: Fri, 16 Oct 1998 21:32:36 -0400 (EDT)
From: Matt Behrens 
To: mike@seidata.com
cc: freebsd-current@FreeBSD.ORG
Subject: Re: 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

I got the same thing on my 2477/16/63 disk (same machine I was
messing with before).  Fudged with geometry for awhile before giving
up.  Also recreated a partition table, MBR, you name it from DOS.

Mike: what was the last beta you used successfully?

On Fri, 16 Oct 1998 mike@seidata.com wrote:

> Hello,
> 
> I'm attempting to give 3.0-RELEASE a try on my Toshiba 4015CDT.  3.0
> recognizes everything (flawlessley, I might add) at bootup.
> 
> Everything goes smoothly until I attempt to start the actual transfer
> of information from the FTP site and sysinstall starts doing a newfs
> to prepare my drive...  Sysinstall then gets rather upset and says,
> "Unable to make new root filesystem on /dev/rwd0s2a!" and I have to
> abort.
> 
> ALT-F2 yields:
> 
> newfs: ioctl (WDINFO): Cross-device link
> newfs: /dev/rwd0s2a: can't rewrite disk label
> 
> Is my partition table just fubar?  2.2.7-RELEASE chugs happily along.

Matt Behrens    | If only I could learn Japanese and get my
Servant of Karen Behrens       | hands on all 200 Sailor Moon episodes and
Engineer, Nameless IRC Network | all the movies, I think my life would
I eat Penguins for breakfast.  | finally be complete. . . . . . . . . . .


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 18:53:57 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA09484
          for freebsd-current-outgoing; Fri, 16 Oct 1998 18:53:57 -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 SAA09453
          for ; Fri, 16 Oct 1998 18:53:49 -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 JAA23793;
	Sat, 17 Oct 1998 09:25:32 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810170125.JAA23793@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 "Fri, 16 Oct 1998 20:58:51 -0400."
              
Date: Sat, 17 Oct 1998 09:25:30 +0800
From: Peter Wemm 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Brian Feldman wrote:
> @ is linked to /usr/src/sys/sys
> Of course, it should be linked with /usr/src/sys. Peter, if I knew how to
> fix the Makefile, I would.

A couple of things..  bsd.kmod.mk sets this link.  Are you sure
/usr/share/mk/bsd.kmod.mk has been updated correctly? 
(cd /usr/src/share/mk; make install if not)

Second, if this was created before bsd.kmod.mk was updated, the old link 
will not get changed.  You'll have to do a 'make clean' first to get rid 
of the old one.

Make sure that you got a sys/modules/Makefile.inc file that sets KLDMOD.  
Otherwise bsd.kmod.mk works in LKM mode.

I'd be very wary of the atapi/wcd modules at the moment, I have not tested
them (I don't have IDE active on any machines within testing reach).

> 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  Fri Oct 16 19:07:31 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA10674
          for freebsd-current-outgoing; Fri, 16 Oct 1998 19:07:31 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10653
          for ; Fri, 16 Oct 1998 19:07:14 -0700 (PDT)
          (envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
	by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id WAA01695;
	Fri, 16 Oct 1998 22:10:49 -0400 (EDT)
	(envelope-from matt@zigg.com)
Date: Fri, 16 Oct 1998 22:10:49 -0400 (EDT)
From: Matt Behrens 
To: mike@seidata.com
cc: freebsd-current@FreeBSD.ORG
Subject: Re: 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

I am installing 3.0-19981015-BETA now and it does not exhibit this
symptom.  3.0-RELEASE does.  I'll commit a PR.

On Fri, 16 Oct 1998, Matt Behrens wrote:

> I got the same thing on my 2477/16/63 disk (same machine I was
> messing with before).  Fudged with geometry for awhile before giving
> up.  Also recreated a partition table, MBR, you name it from DOS.
> 
> Mike: what was the last beta you used successfully?
> 
> On Fri, 16 Oct 1998 mike@seidata.com wrote:
> 
> > Hello,
> > 
> > I'm attempting to give 3.0-RELEASE a try on my Toshiba 4015CDT.  3.0
> > recognizes everything (flawlessley, I might add) at bootup.
> > 
> > Everything goes smoothly until I attempt to start the actual transfer
> > of information from the FTP site and sysinstall starts doing a newfs
> > to prepare my drive...  Sysinstall then gets rather upset and says,
> > "Unable to make new root filesystem on /dev/rwd0s2a!" and I have to
> > abort.
> > 
> > ALT-F2 yields:
> > 
> > newfs: ioctl (WDINFO): Cross-device link
> > newfs: /dev/rwd0s2a: can't rewrite disk label
> > 
> > Is my partition table just fubar?  2.2.7-RELEASE chugs happily along.
> 
> Matt Behrens    | If only I could learn Japanese and get my
> Servant of Karen Behrens       | hands on all 200 Sailor Moon episodes and
> Engineer, Nameless IRC Network | all the movies, I think my life would
> I eat Penguins for breakfast.  | finally be complete. . . . . . . . . . .
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

Matt Behrens    | If only I could learn Japanese and get my
Servant of Karen Behrens       | hands on all 200 Sailor Moon episodes and
Engineer, Nameless IRC Network | all the movies, I think my life would
I eat Penguins for breakfast.  | finally be complete. . . . . . . . . . .


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 19:11:19 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA11048
          for freebsd-current-outgoing; Fri, 16 Oct 1998 19:11: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 TAA11042
          for ; Fri, 16 Oct 1998 19:11: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 LAA13544
	for ; Sat, 17 Oct 1998 11:40:54 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.1/8.9.0) id LAA01687;
	Sat, 17 Oct 1998 11:40:52 +0930 (CST)
Message-ID: <19981017114052.Q469@freebie.lemis.com>
Date: Sat, 17 Oct 1998 11:40:52 +0930
From: Greg Lehey 
To: FreeBSD current users 
Subject: Why can't I check out RELENG_3_0_0_RELEASE?
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

I'm not sure if I'm doing something wrong here or not.  Certainly I've
seen a difference between 2.2.6 and 3.0 RELEASEs.  With 2.2.6, I can
write:

# cvs co -r RELENG_2_2_6_RELEASE world 
cvs checkout: Updating .
cvs checkout: Updating CVSROOT
cvs checkout: Updating CVSROOT/commitlogs
cvs checkout: Updating doc
(etc)

If I enter:

  # cvs co -r RELENG_3_0_0_RELEASE src

it creates the directories CVS and src/CVS, apparently with the
correct contents, but doesn't check any modules out.  I can then go to
src and say

  # cvs update -P -d

and it checks the things out.

What's wrong here?

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 16 19:21:06 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA12886
          for freebsd-current-outgoing; Fri, 16 Oct 1998 19:21:06 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.1.8])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA12880;
          Fri, 16 Oct 1998 19:21:04 -0700 (PDT)
          (envelope-from dholland@cs.toronto.edu)
Received: from qew.cs.toronto.edu ([128.100.2.15]) by yonge.cs.toronto.edu with SMTP id <86534-436>; Fri, 16 Oct 1998 22:20:12 -0400
Received: by qew.cs.toronto.edu id <37814-16861>; Fri, 16 Oct 1998 22:17:19 -0400
Subject: Re: Never ending 'make clean' in kde port?
From: David Holland 
To: rkw@Dataplex.NET (Richard Wackerbarth)
Date: 	Fri, 16 Oct 1998 22:17:17 -0400
Cc: asami@FreeBSD.ORG, kpielorz@tdx.co.uk, eivind@yes.no, current@FreeBSD.ORG
In-Reply-To:  from "Richard Wackerbarth" at Oct 12, 98 07:49:26 am
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <98Oct16.221719edt.37814-16861@qew.cs.toronto.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 > This is a clear case of the evils of "recursive make".
 > http://www.canb.auug.org.au/~millerp/rmch/recu-make-cons-harm.html

While this guy has some points, his assertion that it's always faster
to have one makefile is completely false - I broke netbsd's libc into
recursive makes at one point and it got a lot faster.

Why? Probably because some of the operations on the dependency graph
are slower than O(n).

-- 
   - David A. Holland             | (please continue to send non-list mail to
     dholland@cs.utoronto.ca      | dholland@hcs.harvard.edu. yes, I moved.)

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 19:27:01 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA13622
          for freebsd-current-outgoing; Fri, 16 Oct 1998 19:27: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 TAA13610
          for ; Fri, 16 Oct 1998 19:26:57 -0700 (PDT)
          (envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id VAA12979;
	Fri, 16 Oct 1998 21:26:17 -0500 (CDT)
Received: from harkol-60.isdn.mke.execpc.com(169.207.64.188) by peak.mountin.net via smap (V1.3)
	id sma012976; Fri Oct 16 21:25:46 1998
Message-Id: <3.0.3.32.19981016212053.00f51c60@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, 16 Oct 1998 21:20:53 -0500
To: Mike Smith 
From: "Jeffrey J. Mountin" 
Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) 
Cc: Mike Smith , "Jordan K. Hubbard" ,
        Karl Pielorz , current@FreeBSD.ORG
In-Reply-To: <199810160547.WAA00764@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 10:47 PM 10/15/98 -0700, Mike Smith wrote:
>It looks like there will be a snapshot of FreeBSD/Alpha at about the 
>3.0-RELEASE level, out at about the same time.  I don't think it will 
>be described as RELEASE quality (we're not a Linux vendor after all).

So 3.0-RELEASE is a release, but not of the normal variety.

>The new loader will be installed.  The new boot blocks will be 
>available, but will not be installed.  The new loader will not be 
>*used* by default.

Gotcha.

>> Further will 'make world'/'make buildworld' automagically install the new
>> load on 3.0 if the sysinstall does not?
>
>Yes.

Following what sysinstall does in the first place.

>The principal goals for the next few months will be to complete the 
>current development push and stabilise the existing feature set.  We'll 
>branch before 3.0.5 or whatever it's called in February or so, at which 
>point aggressive development will move to the 3.1 branch and the 
>-stable tag will transition to the 3.0.x branch.

Ah, so the 3.x -stable branch will not appear for while and RELENG_3(?)
won't appear for a while.  Been expecting to cvsup from -current anyways
should there be any issue.

>As Jordan has already expounded, the 3.0-RELEASE is meant to put the 
>mostly-complete current feature set out to a wider audience; to get it 
>used in real-world conditions and on the radar screens of commercial 
>vendors, etc.  It holds much of the shape of things to come in many 
>ways, even though it is in and of itself not a complete thing.

Fully understood and plan to run with it on a fairly loaded dual-PPro web
server.  They way things look now, any problems should be related to the
site's cgi, which is undergoing a rewrite by myself to fix some problems.

"FreeBSD, no warranty, no official tech support, but assures satisfaction."

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  Fri Oct 16 19:31:23 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA14375
          for freebsd-current-outgoing; Fri, 16 Oct 1998 19:31:23 -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 TAA14363
          for ; Fri, 16 Oct 1998 19:31:19 -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 TAA16504;
	Fri, 16 Oct 1998 19:30:50 -0700 (PDT)
	(envelope-from jdp)
Message-Id: <199810170230.TAA16504@austin.polstra.com>
To: grog@lemis.com
Subject: Re: Why can't I check out RELENG_3_0_0_RELEASE?
In-Reply-To: <19981017114052.Q469@freebie.lemis.com>
References: <19981017114052.Q469@freebie.lemis.com>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Date: Fri, 16 Oct 1998 19:30:50 -0700
From: John Polstra 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <19981017114052.Q469@freebie.lemis.com>,
Greg Lehey   wrote:
> I'm not sure if I'm doing something wrong here or not.  Certainly I've
> seen a difference between 2.2.6 and 3.0 RELEASEs.  With 2.2.6, I can
> write:
> 
> # cvs co -r RELENG_2_2_6_RELEASE world 
> cvs checkout: Updating .
> cvs checkout: Updating CVSROOT
> cvs checkout: Updating CVSROOT/commitlogs
> cvs checkout: Updating doc
> (etc)
> 
> If I enter:
> 
>   # cvs co -r RELENG_3_0_0_RELEASE src
> 
> it creates the directories CVS and src/CVS, apparently with the
> correct contents, but doesn't check any modules out.

Did you really wait until it finished, or did you get impatient and
kill it?  The first time you check out using a new tag, it goes
searching through every file looking for the tag to make sure it's
valid.  Then it adds the tag to ${CVSROOT}/CVSROOT/val-tags and works
quickly thereafter.

I don't know why it doesn't find the tag sooner than it does.  I have
a suspicion that it's searching the whole repository including the
ports tree, which does not contain that tag.

John
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 19:41:30 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA15584
          for freebsd-current-outgoing; Fri, 16 Oct 1998 19:41:30 -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 TAA15571
          for ; Fri, 16 Oct 1998 19:41:22 -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 TAA17318;
	Fri, 16 Oct 1998 19:40:59 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Matt Behrens 
cc: mike@seidata.com, freebsd-current@FreeBSD.ORG
Subject: Re: 3.0-RELEASE 
In-reply-to: Your message of "Fri, 16 Oct 1998 22:10:49 EDT."
              
Date: Fri, 16 Oct 1998 19:40:56 -0700
Message-ID: <17310.908592056@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I am installing 3.0-19981015-BETA now and it does not exhibit this
> symptom.  3.0-RELEASE does.  I'll commit a PR.

I may have a work-around here.  I'm not sure why this bug has suddenly
cropped up in just 3 days, and I'm looking hard for it, but if you
could please try the 3.0 installation floppy in:

      ftp://ftp.freebsd.org/pub/FreeBSD/incoming/boot.flp

And report back your results, I would much appreciate it!  Same goes
for anyone else who's experienced this problem.

Thanks..

- Jordan

> 
> On Fri, 16 Oct 1998, Matt Behrens wrote:
> 
> > I got the same thing on my 2477/16/63 disk (same machine I was
> > messing with before).  Fudged with geometry for awhile before giving
> > up.  Also recreated a partition table, MBR, you name it from DOS.
> > 
> > Mike: what was the last beta you used successfully?
> > 
> > On Fri, 16 Oct 1998 mike@seidata.com wrote:
> > 
> > > Hello,
> > > 
> > > I'm attempting to give 3.0-RELEASE a try on my Toshiba 4015CDT.  3.0
> > > recognizes everything (flawlessley, I might add) at bootup.
> > > 
> > > Everything goes smoothly until I attempt to start the actual transfer
> > > of information from the FTP site and sysinstall starts doing a newfs
> > > to prepare my drive...  Sysinstall then gets rather upset and says,
> > > "Unable to make new root filesystem on /dev/rwd0s2a!" and I have to
> > > abort.
> > > 
> > > ALT-F2 yields:
> > > 
> > > newfs: ioctl (WDINFO): Cross-device link
> > > newfs: /dev/rwd0s2a: can't rewrite disk label
> > > 
> > > Is my partition table just fubar?  2.2.7-RELEASE chugs happily along.
> > 
> > Matt Behrens    | If only I could learn Japanese and get my
> > Servant of Karen Behrens       | hands on all 200 Sailor Moon episodes and
> > Engineer, Nameless IRC Network | all the movies, I think my life would
> > I eat Penguins for breakfast.  | finally be complete. . . . . . . . . . .
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> > 
> 
> Matt Behrens    | If only I could learn Japanese and get my
> Servant of Karen Behrens       | hands on all 200 Sailor Moon episodes and
> Engineer, Nameless IRC Network | all the movies, I think my life would
> I eat Penguins for breakfast.  | finally be complete. . . . . . . . . . .
> 
> 
> 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  Fri Oct 16 19:45:57 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA16261
          for freebsd-current-outgoing; Fri, 16 Oct 1998 19:45:57 -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 TAA16243
          for ; Fri, 16 Oct 1998 19:45:45 -0700 (PDT)
          (envelope-from donegan@oldnews.quick.net)
Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id TAA00348; Fri, 16 Oct 1998 19:45:24 -0700 (PDT)
Date: Fri, 16 Oct 1998 19:45:24 -0700 (PDT)
From: "Steven P. Donegan" 
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 freebsd-current

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 19:57:24 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA17717
          for freebsd-current-outgoing; Fri, 16 Oct 1998 19:57:24 -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 TAA17708
          for ; Fri, 16 Oct 1998 19:57:20 -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 MAA13735;
	Sat, 17 Oct 1998 12:26:58 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.1/8.9.0) id MAA01827;
	Sat, 17 Oct 1998 12:26:58 +0930 (CST)
Message-ID: <19981017122657.X469@freebie.lemis.com>
Date: Sat, 17 Oct 1998 12:26:57 +0930
From: Greg Lehey 
To: John Polstra 
Cc: current@FreeBSD.ORG
Subject: Re: Why can't I check out RELENG_3_0_0_RELEASE?
References: <19981017114052.Q469@freebie.lemis.com> <199810170230.TAA16504@austin.polstra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199810170230.TAA16504@austin.polstra.com>; from John Polstra on Fri, Oct 16, 1998 at 07:30:50PM -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
X-Mutt-References: <199810170230.TAA16504@austin.polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Friday, 16 October 1998 at 19:30:50 -0700, John Polstra wrote:
> In article <19981017114052.Q469@freebie.lemis.com>,
> Greg Lehey   wrote:
>> I'm not sure if I'm doing something wrong here or not.  Certainly I've
>> seen a difference between 2.2.6 and 3.0 RELEASEs.  With 2.2.6, I can
>> write:
>>
>> # cvs co -r RELENG_2_2_6_RELEASE world
>> cvs checkout: Updating .
>> cvs checkout: Updating CVSROOT
>> cvs checkout: Updating CVSROOT/commitlogs
>> cvs checkout: Updating doc
>> (etc)
>>
>> If I enter:
>>
>>   # cvs co -r RELENG_3_0_0_RELEASE src
>>
>> it creates the directories CVS and src/CVS, apparently with the
>> correct contents, but doesn't check any modules out.
>
> Did you really wait until it finished, or did you get impatient and
> kill it?

I got impatient and killed it.  I had a similar problem with 2.2.7,
and in that case ISTR that I let it finish, and it didn't check
anything else out, so I assumed there was something wrong with what I
was doing.

> The first time you check out using a new tag, it goes searching
> through every file looking for the tag to make sure it's valid.
> Then it adds the tag to ${CVSROOT}/CVSROOT/val-tags and works
> quickly thereafter.

OK, it wasn't in val-tags, so I tried again, with

   cvs co -r RELENG_3_0_0_RELEASE src

It took nearly 10 minutes, during which it created only src/CVS and
(correct) contents.  Then it started checking out normally.  It still
hasn't finished, but it has updated val-tags, so I'll assume it's a
quirk rather than a bug.  I'll put something in the book about it.

> I don't know why it doesn't find the tag sooner than it does.  I have
> a suspicion that it's searching the whole repository including the
> ports tree, which does not contain that tag.

It can't be that simple, since this time I checked out only src.

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 16 20:07:26 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA18909
          for freebsd-current-outgoing; Fri, 16 Oct 1998 20:07:26 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18899;
          Fri, 16 Oct 1998 20:07:20 -0700 (PDT)
          (envelope-from rkw@Dataplex.NET)
Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5])
	by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id AAA25773;
	Sat, 17 Oct 1998 00:46:04 -0500 (CDT)
	(envelope-from rkw@dataplex.net)
X-Sender: rkw@mail.dataplex.net
Message-Id: 
In-Reply-To: <98Oct16.221719edt.37814-16861@qew.cs.toronto.edu>
References:  from "Richard
 Wackerbarth" at Oct 12, 98 07:49:26 am
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 16 Oct 1998 22:06:46 -0500
To: David Holland 
From: Richard Wackerbarth 
Subject: Re: Never ending 'make clean' in kde port?
Cc: asami@FreeBSD.ORG, kpielorz@tdx.co.uk, eivind@yes.no, current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 9:17 PM -0500 10/16/98, David Holland wrote:
> > This is a clear case of the evils of "recursive make".
> > http://www.canb.auug.org.au/~millerp/rmch/recu-make-cons-harm.html
>
>While this guy has some points, his assertion that it's always faster
>to have one makefile is completely false - I broke netbsd's libc into
>recursive makes at one point and it got a lot faster.
>
>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. The cleaning operation which started
this discussion is a prime example. OTOH, IF (and that is a big if)
the author knows (and maintains) isolated subgraphs, it can be
advantageous to perform the make in those subgraphs as a separate
ie., recursive, make.

However, at the macro level, the intermodule dependancy relations
are properly handled by avoiding the recursion.

Richard Wackerbarth



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 20:30:34 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA21929
          for freebsd-current-outgoing; Fri, 16 Oct 1998 20:30:34 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.1.8])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA21922;
          Fri, 16 Oct 1998 20:30:31 -0700 (PDT)
          (envelope-from dholland@cs.toronto.edu)
Received: from qew.cs.toronto.edu ([128.100.2.15]) by yonge.cs.toronto.edu with SMTP id <86542-436>; Fri, 16 Oct 1998 23:30:08 -0400
Received: by qew.cs.toronto.edu id <37814-16861>; Fri, 16 Oct 1998 23:29:38 -0400
Subject: Re: Never ending 'make clean' in kde port?
From: David Holland 
To: rkw@Dataplex.NET (Richard Wackerbarth)
Date: 	Fri, 16 Oct 1998 23:29:35 -0400
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 11:06:46 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <98Oct16.232938edt.37814-16861@qew.cs.toronto.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 > 
 > At 9:17 PM -0500 10/16/98, David Holland wrote:
 > > > This is a clear case of the evils of "recursive make".
 > > > http://www.canb.auug.org.au/~millerp/rmch/recu-make-cons-harm.html
 > >
 > >While this guy has some points, his assertion that it's always faster
 > >to have one makefile is completely false - I broke netbsd's libc into
 > >recursive makes at one point and it got a lot faster.
 > >
 > >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*

-- 
   - David A. Holland             | (please continue to send non-list mail to
     dholland@cs.utoronto.ca      | dholland@hcs.harvard.edu. yes, I moved.)

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 20:41:36 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA22632
          for freebsd-current-outgoing; Fri, 16 Oct 1998 20:41:36 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22626;
          Fri, 16 Oct 1998 20:41:31 -0700 (PDT)
          (envelope-from rkw@Dataplex.NET)
Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5])
	by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id BAA25854;
	Sat, 17 Oct 1998 01:21:01 -0500 (CDT)
	(envelope-from rkw@dataplex.net)
X-Sender: rkw@mail.dataplex.net
Message-Id: 
In-Reply-To: <98Oct16.232938edt.37814-16861@qew.cs.toronto.edu>
References:  from "Richard
 Wackerbarth" at Oct 16, 98 11:06:46 pm
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 16 Oct 1998 22:36:19 -0500
To: David Holland 
From: Richard Wackerbarth 
Subject: Re: Never ending 'make clean' in kde port?
Cc: dholland@cs.toronto.edu, asami@FreeBSD.ORG, kpielorz@tdx.co.uk,
        eivind@yes.no, current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 10:29 PM -0500 10/16/98, David Holland wrote:
> >
> > At 9:17 PM -0500 10/16/98, David Holland wrote:
> > > > This is a clear case of the evils of "recursive make".
> > > > http://www.canb.auug.org.au/~millerp/rmch/recu-make-cons-harm.html
> > >
> > >While this guy has some points, his assertion that it's always faster
> > >to have one makefile is completely false - I broke netbsd's libc into
> > >recursive makes at one point and it got a lot faster.
> > >
> > >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.     :-(

Richard Wackerbarth



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 20:54:03 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA23623
          for freebsd-current-outgoing; Fri, 16 Oct 1998 20:54:03 -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 UAA23618
          for ; Fri, 16 Oct 1998 20:54:01 -0700 (PDT)
          (envelope-from ckempf@singularity.enigami.com)
Received: (from ckempf@localhost)
	by singularity.enigami.com (8.9.1/8.9.1) id XAA15050;
	Fri, 16 Oct 1998 23:53:27 -0400 (EDT)
To: freebsd-current@FreeBSD.ORG
Subject: So, what does ELF give me?
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: 16 Oct 1998 23:53:27 -0400
Message-ID: 
Lines: 22
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
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?

Thanks,

+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  Fri Oct 16 21:11:38 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA24699
          for freebsd-current-outgoing; Fri, 16 Oct 1998 21:11:38 -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 VAA24694
          for ; Fri, 16 Oct 1998 21:11:35 -0700 (PDT)
          (envelope-from donegan@oldnews.quick.net)
Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id VAA00568; Fri, 16 Oct 1998 21:11:15 -0700 (PDT)
Date: Fri, 16 Oct 1998 21:11:15 -0700 (PDT)
From: "Steven P. Donegan" 
To: freebsd-current@FreeBSD.ORG
Subject: softupdates/smp
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

After a long biz trip and other adventures...

I finally got back to the list, and compiled today's kernel (SMP). Tried 
a boot - no problem. Turned on softupdates on the disk (tunefs -n 
enable). Boot proceeded and then tombstone. Is softupdates viable on 
anyone's hardware at present under SMP?

TIA

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Fri Oct 16 21:36:19 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA26626
          for freebsd-current-outgoing; Fri, 16 Oct 1998 21:36:19 -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 VAA26619
          for ; Fri, 16 Oct 1998 21:36:18 -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 VAA17784
	for ; Fri, 16 Oct 1998 21:36:26 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: current@FreeBSD.ORG
Subject: The "cross device link" bug people have been seeing on newfs
Date: Fri, 16 Oct 1998 21:36:26 -0700
Message-ID: <17780.908598986@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Neither David, Mike nor myself have any idea why this is currently
happening or why it apparently did not happen 3 days ago, but in the
meantime I've come up with a work-around that appears to do the trick
(according to Ulf, the first tester to respond, anyway).  I've
re-rolled the boot.flp on ftp.cdrom.com and, for consistency's sake,
will also reroll the src and bin distributions so that newfs is
updated in all locations.  The fixed bits will also go out on the
CDROM since I haven't built that yet.

Those who have already installed 3.0-RELEASE can either cvsup themselves
up to date to get the fix in or simply apply the following patch:

RCS file: /home/ncvs/src/sbin/newfs/newfs.c,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- newfs.c     1998/09/30 07:53:52     1.25
+++ newfs.c     1998/10/17 04:19:29     1.26
@@ -601,8 +601,10 @@
        if (realsectorsize != DEV_BSIZE)
                pp->p_size /= realsectorsize /DEV_BSIZE;
 #endif
+#if 0  /* XXX this shouldn't fail, but it returns ENXDEV right now - pure workaround, this */
        if (!Nflag && bcmp(pp, &oldpartition, sizeof(oldpartition)))
                rewritelabel(special, fso, lp);
+#endif
        if (!Nflag)
                close(fso);
        close(fsi);

Again, we've no idea why rewriting the label causes this bug in the
first place and this is a WORK-AROUND until we do.  Not rewriting the
lable doesn't (shouldn't) hurt in any case since we don't use the
fields it updates right now, at least not in any typical
disklabel/newfs scenario.

- 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 16 21:40:06 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA26990
          for freebsd-current-outgoing; Fri, 16 Oct 1998 21:40:06 -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 VAA26888
          for ; Fri, 16 Oct 1998 21:40:01 -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 AAA04868;
	Sat, 17 Oct 1998 00:37:55 -0400 (EDT)
Date: Sat, 17 Oct 1998 00:37:55 -0400 (EDT)
From: Chuck Robey 
To: "Steven P. Donegan" 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: softupdates/smp
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 Fri, 16 Oct 1998, Steven P. Donegan wrote:

> After a long biz trip and other adventures...
> 
> I finally got back to the list, and compiled today's kernel (SMP). Tried 
> a boot - no problem. Turned on softupdates on the disk (tunefs -n 
> enable). Boot proceeded and then tombstone. Is softupdates viable on 
> anyone's hardware at present under SMP?

Solid here.  With CAM and softupdates.  Buildworlds like crazy.  Wasn't
always that way, but is now.  Real good, this machine get's used heavily
for schoolwork (I shouldn't run current on it, but I've been too heavily
infected with FreeBSD).

It's a dual P6-166, Tyan Titan II.  Wouldn't part with it for the world.


----------------------------+-----------------------------------------------
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  Fri Oct 16 21:51:38 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA27884
          for freebsd-current-outgoing; Fri, 16 Oct 1998 21:51:38 -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 VAA27879
          for ; Fri, 16 Oct 1998 21:51:34 -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 OAA00376;
	Sat, 17 Oct 1998 14:51:01 +1000
Date: Sat, 17 Oct 1998 14:51:01 +1000
From: Bruce Evans 
Message-Id: <199810170451.OAA00376@godzilla.zeta.org.au>
To: mike@smith.net.au, shimon@simon-shapiro.org
Subject: Re: Show Stopper? Failure to Install 19981014
Cc: freebsd-current@FreeBSD.ORG, jkh@time.cdrom.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>It appears to be caused by not entering the root filesystem first.
>There's a test in the disklabel code which checks to see if the
>partition you have open to write the label starts at 0, and if not then
>it defaults to the 'a' partition.

Labels should always be written using the RAW_PART partition ('c' on
i386's).  If not, then they must be written using a partition that has
offset 0.  If not even that, then the 'a' partition must have offset 0.
Unfortunately, newfs(8) writes labels to the same partition that it
is newfs'ing.

>Partitions are laid on disk in the order that you enter them.  The 'a' 
>partition is always reserved for the partition you mount on /.  If you 

It's not reserved.  It's just the default.

>don't enter this partition first, it won't be at the beginning of the 
>disk, and any attempt to rewrite the disklabel will fail.
>
>Due to the way that sysinstall interacts with libdisk, this is 
>difficult to get "right".  We probably need a bandaid which insists 
>that if you want to create an 'a' partition you must lay it down first.

This is easy to fix by changing the (whole) test in writedisklabel() to
`lp->p_partitions[RAW_PART] == 0'.  Even that is probably only necessary
to give the right errno (this condition is enforced in several places).
This might wake bugs in other code where partition 0 is magic.

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 16 22:05:16 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA29087
          for freebsd-current-outgoing; Fri, 16 Oct 1998 22:05:16 -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 WAA29082
          for ; Fri, 16 Oct 1998 22:05:13 -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 PAA01112;
	Sat, 17 Oct 1998 15:04:49 +1000
Date: Sat, 17 Oct 1998 15:04:49 +1000
From: Bruce Evans 
Message-Id: <199810170504.PAA01112@godzilla.zeta.org.au>
To: jkh@time.cdrom.com, matt@zigg.com
Subject: Re: sysinstall "probing devices" hangs only on 3.0-199810??-BETA, not on 2.2.7-RELEASE boot disk
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>First time I tried it, it seemed to hang after the ep0 probe returned
>"not found at 0x300".  It had probed all my hardware up until that
>point correctly, however.
>
>What comes after ep0 in the default lineup?  Maybe I can try
>disabling that.

Some of the probes for ISA ethernet cards are invasive.  Most likely
it's something before ep0, or ep0 itself, or something NOT before ep0
(see below) that screws up the following probes (whether or not there
is any hardware for the following probes to succeed on).

>> I saw that once myself, but only when I went and trimmed out
>> everything and its brother with the visual userconfig.  When I just
>> whacked return the next time through, editing nothing in the kernel
>> configuration, it went fine.  Could you perhaps try this so we could
>> narrow things down a bit?

Leaving things alone can work by allowing the actual device to be found
early so that most of the invasive probes are skipped because they would
conflict.  E.g., I have an ed0 at 0x300.  ed is "sensitive hardware"",
so it is always probed early.  However, the default ed0 is at 0x280.
If I don't change that, then ed0 is not found (early or at all) and the
probe sequence hangs near ep0, apparently because some invasive probe
gets confused when it finds ed0 at 0x300.

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 16 22:13:07 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA29616
          for freebsd-current-outgoing; Fri, 16 Oct 1998 22:13:07 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles146.castles.com [208.214.165.146])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29610
          for ; Fri, 16 Oct 1998 22:13:05 -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 WAA00708;
	Fri, 16 Oct 1998 22:17:15 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810170517.WAA00708@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bruce Evans 
cc: mike@smith.net.au, shimon@simon-shapiro.org, freebsd-current@FreeBSD.ORG,
        jkh@time.cdrom.com
Subject: Re: Show Stopper? Failure to Install 19981014 
In-reply-to: Your message of "Sat, 17 Oct 1998 14:51:01 +1000."
             <199810170451.OAA00376@godzilla.zeta.org.au> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Oct 1998 22:17:14 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >It appears to be caused by not entering the root filesystem first.
> >There's a test in the disklabel code which checks to see if the
> >partition you have open to write the label starts at 0, and if not then
> >it defaults to the 'a' partition.
> 
> Labels should always be written using the RAW_PART partition ('c' on
> i386's).  If not, then they must be written using a partition that has
> offset 0.  If not even that, then the 'a' partition must have offset 0.
> Unfortunately, newfs(8) writes labels to the same partition that it
> is newfs'ing.

I checked the history for this; it appears to have done this for a long 
time.

There is also bogus code in sys/ufs/ufs/ufs_disksubr.c which checks the 
start of the partition to which the label is being written, and if that 
is not 0, uses partition 0 ('a') instead.  It is this code which is 
returning EXDEV.

> >Partitions are laid on disk in the order that you enter them.  The 'a' 
> >partition is always reserved for the partition you mount on /.  If you 
> 
> It's not reserved.  It's just the default.

It's reserved by sysinstall.

> >don't enter this partition first, it won't be at the beginning of the 
> >disk, and any attempt to rewrite the disklabel will fail.
> >
> >Due to the way that sysinstall interacts with libdisk, this is 
> >difficult to get "right".  We probably need a bandaid which insists 
> >that if you want to create an 'a' partition you must lay it down first.
> 
> This is easy to fix by changing the (whole) test in writedisklabel() to
> `lp->p_partitions[RAW_PART] == 0'.  Even that is probably only necessary
> to give the right errno (this condition is enforced in several places).
> This might wake bugs in other code where partition 0 is magic.

Exactly.  More to the point, why has this symptom only just recently 
manifested?

-- 
\\  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 16 23:02:13 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA02329
          for freebsd-current-outgoing; Fri, 16 Oct 1998 23:02:13 -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 XAA02324
          for ; Fri, 16 Oct 1998 23:02:10 -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 QAA03864;
	Sat, 17 Oct 1998 16:01:46 +1000
Date: Sat, 17 Oct 1998 16:01:46 +1000
From: Bruce Evans 
Message-Id: <199810170601.QAA03864@godzilla.zeta.org.au>
To: bde@zeta.org.au, mike@smith.net.au
Subject: Re: Show Stopper? Failure to Install 19981014
Cc: freebsd-current@FreeBSD.ORG, jkh@time.cdrom.com, shimon@simon-shapiro.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> Labels should always be written using the RAW_PART partition ('c' on
>> i386's).  If not, then they must be written using a partition that has
>> offset 0.  If not even that, then the 'a' partition must have offset 0.
>> Unfortunately, newfs(8) writes labels to the same partition that it
>> is newfs'ing.
>
>I checked the history for this; it appears to have done this for a long 
>time.

Yes, it's unreasonhable for it to frob the minor bits to convert from
the partition that it is newfs'ing to the raw partition.

>There is also bogus code in sys/ufs/ufs/ufs_disksubr.c which checks the 
>start of the partition to which the label is being written, and if that 
>is not 0, uses partition 0 ('a') instead.  It is this code which is 
>returning EXDEV.

This is the same bogus code.  This failure of newfs's label write shows
that the test lp->d_partitions[part] (where `part' is the partition being
used to write the label) in writedisklabel() is bogus.  It makes labels
written via the raw partition more equal than the same labels written
via another partition.  The EXDEV return code is correct.  It's clear
from the handling of this code in disklabel(8) that the special handling
of the 'a' partition is the intended behaviour.  It's just wrong on
systems where the raw partition isn't 'a'.


>> >Partitions are laid on disk in the order that you enter them.  The 'a' 
>> >partition is always reserved for the partition you mount on /.  If you 
>> 
>> It's not reserved.  It's just the default.
>
>It's reserved by sysinstall.

Some of us don't use sysinstall.

>> This is easy to fix by changing the (whole) test in writedisklabel() to
>> `lp->p_partitions[RAW_PART] == 0'.  Even that is probably only necessary
>> to give the right errno (this condition is enforced in several places).
>> This might wake bugs in other code where partition 0 is magic.
>
>Exactly.  More to the point, why has this symptom only just recently 
>manifested?

Because newfs was broken in rev.1.9 of newfs/newfs.c (before 2.0.5R).
Unfortunately, the breaker didn't seem to have investigated the failure
mode, so I didn't know how to fix it when I backed out the breakage
in rev.1.22.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 02:35:42 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA18425
          for freebsd-current-outgoing; Sat, 17 Oct 1998 02:35:42 -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 CAA18420
          for ; Sat, 17 Oct 1998 02:35:37 -0700 (PDT)
          (envelope-from sos@sos.freebsd.dk)
Received: (from sos@localhost)
	by sos.freebsd.dk (8.9.1/8.9.1) id LAA09826;
	Sat, 17 Oct 1998 11:34:47 +0200 (CEST)
	(envelope-from sos)
Message-Id: <199810170934.LAA09826@sos.freebsd.dk>
Subject: Re: softupdates/smp
In-Reply-To:  from Chuck Robey at "Oct 17, 98 00:37:55 am"
To: chuckr@mat.net (Chuck Robey)
Date: Sat, 17 Oct 1998 11:34:47 +0200 (CEST)
Cc: donegan@quick.net, 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 Chuck Robey who wrote:
> On Fri, 16 Oct 1998, Steven P. Donegan wrote:
> 
> > After a long biz trip and other adventures...
> > 
> > I finally got back to the list, and compiled today's kernel (SMP). Tried 
> > a boot - no problem. Turned on softupdates on the disk (tunefs -n 
> > enable). Boot proceeded and then tombstone. Is softupdates viable on 
> > anyone's hardware at present under SMP?
> 
> Solid here.  With CAM and softupdates.  Buildworlds like crazy.  Wasn't
> always that way, but is now.  Real good, this machine get's used heavily
> for schoolwork (I shouldn't run current on it, but I've been too heavily
> infected with FreeBSD).
> 
> It's a dual P6-166, Tyan Titan II.  Wouldn't part with it for the world.

You are lucky I guess, I still think we have race problems in there, at
least it breaks real fast on a make work -j8 or above on resonably
fast hardware here, and remember your filesystem is then beyond repair...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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  Sat Oct 17 04:02:38 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA29575
          for freebsd-current-outgoing; Sat, 17 Oct 1998 04:02:38 -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 EAA29559
          for ; Sat, 17 Oct 1998 04:02:25 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id MAA00258
	for ; Sat, 17 Oct 1998 12:01:59 +0100 (BST)
Message-ID: <362878E6.3EE89054@tdx.co.uk>
Date: Sat, 17 Oct 1998 12:00:54 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: current@FreeBSD.ORG
Subject: Serial Console - broken? (src as of 10/16 @ 16:43)
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'm running a serial console for ddb etc. - This used to work great, but with
recent builds every time the system panic's, I get the usual details about the
panic, but it ends with:

"
current process         = Idle
interrupt mask          = bio  <- SMP: XXX
$T0b08:079713f0;05:784b80ff;04:644b80ff;#b4
"

Any key presses on the serial console result in
"04:644b80ff;#b4$T0b08:079713f0;" being displayed...

'Ah, serial port speed I thought', erm, nope - double checking /etc/make.conf
etc. it's set to 57600... Trying different speeds while it's in this state
doesn't net anything better (I get a lot of 'xxx's at lower speeds, which are
normal symptomatic of wrong serial speed).

The boot blocks know about the serial console - the first thing the machine
does when it boots is display the usage message etc. (I've reinstalled the
boot blocks just incase, no change though).

This was all working a couple of days ago, and now it doesn't appear to be...
Can anyone else who has a similar set-up (i.e. serial console) check this?

I've tried typing blindly things like 'panic' {enter} but all to no avail...
:-(

The machines running -current as of 10/16, 16:43 - and it's running SMP...

As a final ditch attempt I tried setting everything to 9600, but again with
the same results (albeit slower :)

Any thoughts?

Regards,

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 04:10:24 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA01894
          for freebsd-current-outgoing; Sat, 17 Oct 1998 04:10:24 -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 EAA01884
          for ; Sat, 17 Oct 1998 04:10:15 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id MAA00275
	for ; Sat, 17 Oct 1998 12:09:54 +0100 (BST)
Message-ID: <36287AC1.3F0C0D9C@tdx.co.uk>
Date: Sat, 17 Oct 1998 12:08:49 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: current@FreeBSD.ORG
Subject: SCSI / CAM error or warning output?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi All (again?)

This might be considered slightly more -hardware oriented, but I thought
-current was probably more appropriate as current probably has the later
version of CAM...

My system's started spitting these out on the console, whilst I can get the
'jist' of what it's trying to say, can someone translate for me? (and tell me
whether it's good or bad?) - system is -current as of 10/16 @ 16:43...

ahc2 is a 2940UW, with 3 x Quantum drives on it. First 2 are un-terminated,
third is using onboard active termination, controller is set to terminate high
& low bits. Cable is a nice Adaptec cable (so _please_ don't tell me it's
termination )...

This happens when the drives are 'busy' (but not totally thrashed)...

"
ahc2:A:8: no active SCB for reconnecting target - issuing BUS DEVICE RESET
SAVED_TCL == 0x80, ARG_1 == 0x1b, SEQ_FLAGS == 0x40
ahc2: Bus Device Reset on A:8. 6 SCBs aborted
(da4:ahc2:0:8:0): tagged openings now 64
(da4:ahc2:0:8:0): tagged openings now 63
Timedout SCB handled by another timeout
(da5:ahc2:0:9:0): data overrun detected in Data-In phase.  Tag == 0x2.
(da5:ahc2:0:9:0): Have seen Data Phase.  Length = 8192.  NumSGs = 1.
Timedout SCB handled by another timeout
ahc2: WARNING no command for scb 65 (cmdcmplt)
QOUTPOS = 1
ahc2: WARNING no command for scb 65 (cmdcmplt)
QOUTPOS = 34
ahc2: WARNING no command for scb 65 (cmdcmplt)
QOUTPOS = 43
ahc2: WARNING no command for scb 1 (cmdcmplt)
QOUTPOS = 58
ahc2:A:10: ahc_intr - referenced scb not valid during seqint 0x71 scb(1)
ahc2: WARNING no command for scb 1 (cmdcmplt)
QOUTPOS = 67
"

DMesg for ah2 is:

"
ahc2:  rev 0x00 int a irq 19 on pci0.20.0
ahc2: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
"

Drives are:

"
da4 at ahc2 bus 0 target 8 lun 0
da4:  Fixed Direct Access SCSI2 device
da4: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da4: 4148MB (8496960 512 byte sectors: 255H 63S/T 528C)
da5 at ahc2 bus 0 target 9 lun 0
da5:  Fixed Direct Access SCSI2 device
da5: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da5: 4148MB (8496960 512 byte sectors: 255H 63S/T 528C)
da6 at ahc2 bus 0 target 10 lun 0
da6:  Fixed Direct Access SCSI2 device
da6: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da6: 4148MB (8496960 512 byte sectors: 255H 63S/T 528C)
"

Regards,

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 04:13:17 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA02137
          for freebsd-current-outgoing; Sat, 17 Oct 1998 04:13:17 -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 EAA02132
          for ; Sat, 17 Oct 1998 04:13:16 -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 EAA22290;
	Sat, 17 Oct 1998 04:12:16 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Bruce Evans 
cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG, shimon@simon-shapiro.org
Subject: Re: Show Stopper? Failure to Install 19981014 
In-reply-to: Your message of "Sat, 17 Oct 1998 16:01:46 +1000."
             <199810170601.QAA03864@godzilla.zeta.org.au> 
Date: Sat, 17 Oct 1998 04:12:16 -0700
Message-ID: <22286.908622736@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Because newfs was broken in rev.1.9 of newfs/newfs.c (before 2.0.5R).
> Unfortunately, the breaker didn't seem to have investigated the failure
> mode, so I didn't know how to fix it when I backed out the breakage
> in rev.1.22.

Unfortunately, you broke it even worse.  Please don't cause worse
breakage, where breakage is defined as systems which no longer
install, in the process of fixing other breakage.  This "feature" in
1.22 will stay disabled until the root issues are figured out, not
before.

- 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 17 04:51:17 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA05105
          for freebsd-current-outgoing; Sat, 17 Oct 1998 04:51:17 -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 EAA05097;
          Sat, 17 Oct 1998 04:51:11 -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 HAA09526;
	Sat, 17 Oct 1998 07:49:17 -0400 (EDT)
Date: Sat, 17 Oct 1998 07:49:17 -0400 (EDT)
From: Chuck Robey 
To: =?iso-8859-1?Q?S=F8ren_Schmidt?= 
cc: donegan@quick.net, freebsd-current@FreeBSD.ORG
Subject: Re: softupdates/smp
In-Reply-To: <199810170934.LAA09826@sos.freebsd.dk>
Message-ID: 
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

On Sat, 17 Oct 1998, SЬren Schmidt wrote:

> In reply to Chuck Robey who wrote:
> > On Fri, 16 Oct 1998, Steven P. Donegan wrote:
> > 
> > > After a long biz trip and other adventures...
> > > 
> > > I finally got back to the list, and compiled today's kernel (SMP). Tried 
> > > a boot - no problem. Turned on softupdates on the disk (tunefs -n 
> > > enable). Boot proceeded and then tombstone. Is softupdates viable on 
> > > anyone's hardware at present under SMP?
> > 
> > Solid here.  With CAM and softupdates.  Buildworlds like crazy.  Wasn't
> > always that way, but is now.  Real good, this machine get's used heavily
> > for schoolwork (I shouldn't run current on it, but I've been too heavily
> > infected with FreeBSD).
> > 
> > It's a dual P6-166, Tyan Titan II.  Wouldn't part with it for the world.
> 
> You are lucky I guess, I still think we have race problems in there, at
> least it breaks real fast on a make work -j8 or above on resonably
> fast hardware here, and remember your filesystem is then beyond repair...

I don't doubt that.  I know longer think it's just a smp only breakage,
tho, something is complicating it.  I've had those dumps, but luckily
the filesystems I do that with, I could regenerate.  Not my cvs.

----------------------------+-----------------------------------------------
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 17 04:58:56 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA05449
          for freebsd-current-outgoing; Sat, 17 Oct 1998 04:58:56 -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 EAA05441;
          Sat, 17 Oct 1998 04:58:53 -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 HAA09549;
	Sat, 17 Oct 1998 07:56:59 -0400 (EDT)
Date: Sat, 17 Oct 1998 07:56:58 -0400 (EDT)
From: Chuck Robey 
To: =?iso-8859-1?Q?S=F8ren_Schmidt?= 
cc: donegan@quick.net, freebsd-current@FreeBSD.ORG
Subject: Re: softupdates/smp
In-Reply-To: 
Message-ID: 
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

On Sat, 17 Oct 1998, Chuck Robey wrote:

> On Sat, 17 Oct 1998, SЬren Schmidt wrote:
> 
> > In reply to Chuck Robey who wrote:
> > > On Fri, 16 Oct 1998, Steven P. Donegan wrote:
> > > 
> > > > After a long biz trip and other adventures...
> > > > 
> > > > I finally got back to the list, and compiled today's kernel (SMP). Tried 
> > > > a boot - no problem. Turned on softupdates on the disk (tunefs -n 
> > > > enable). Boot proceeded and then tombstone. Is softupdates viable on 
> > > > anyone's hardware at present under SMP?
> > > 
> > > Solid here.  With CAM and softupdates.  Buildworlds like crazy.  Wasn't
> > > always that way, but is now.  Real good, this machine get's used heavily
> > > for schoolwork (I shouldn't run current on it, but I've been too heavily
> > > infected with FreeBSD).
> > > 
> > > It's a dual P6-166, Tyan Titan II.  Wouldn't part with it for the world.
> > 
> > You are lucky I guess, I still think we have race problems in there, at
> > least it breaks real fast on a make work -j8 or above on resonably
> > fast hardware here, and remember your filesystem is then beyond repair...
> 
> I don't doubt that.  I know longer think it's just a smp only breakage,
> tho, something is complicating it.  I've had those dumps, but luckily
> the filesystems I do that with, I could regenerate.  Not my cvs.

I better amend that.  I used to have the problems you have now, but they
went away at least a month ago.  Can't say why, exactly.  Went off
softupdates for a while, did a large number of extra fsck checks, went
back on softupdates (after CAM came live) and now, well, it just works.
Fine.

Keeping one rabbit's foot quite handy.

----------------------------+-----------------------------------------------
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 17 06:01:26 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA08700
          for freebsd-current-outgoing; Sat, 17 Oct 1998 06:01:26 -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 GAA08694;
          Sat, 17 Oct 1998 06:01:24 -0700 (PDT)
          (envelope-from donegan@oldnews.quick.net)
Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id GAA04524; Sat, 17 Oct 1998 06:00:59 -0700 (PDT)
Date: Sat, 17 Oct 1998 06:00:58 -0700 (PDT)
From: "Steven P. Donegan" 
To: Chuck Robey 
cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= ,
        freebsd-current@FreeBSD.ORG
Subject: Re: softupdates/smp
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 Sat, 17 Oct 1998, Chuck Robey wrote:

> 
> Keeping one rabbit's foot quite handy.
> 

I'd rather not take up too much of the lists time on this - so my 
question is who is actively working on softupdates? My system(s) are Tyan 
Tomcat's - one a dual 133 with 256 meg RAM and the other a dual 233 with 
256 meg, both have kernels stripped to the bone (ie no drivers in the 
kernel that are not needed) different drivers/boards on the two systems 
(ie nothing else really in common hardware-wise). Both panic, according 
to DDB, in softupdates code immediately after going SMP and tunefs -n enable.

A long time back softupdates worked OK (somewhat) unless I did the make 
-j anything thing :-) Now it's a nice hard failure :-)

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 06:05:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA09084
          for freebsd-current-outgoing; Sat, 17 Oct 1998 06:05:35 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA09060
          for ; Sat, 17 Oct 1998 06:05:19 -0700 (PDT)
          (envelope-from itfs!nnd%itfs.nsk.su@gw.itfs.nsk.su)
Received: from itfs.UUCP (root@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id TAA09833 for current@freebsd.org; Sat, 17 Oct 1998 19:04:46 +0600
Received: by itfs.nsk.su; Sat, 17 Oct 98 20:06:03 +0700 (NST)
To: current@FreeBSD.ORG
Message-ID: 
Organization: Scientific & Technical Enterprise INFOTEKA
From: nnd@itfs.nsk.su (Nickolay Dudorov)
Date: Sat, 17 Oct 98 20:06:03 +0700 (NST)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=koi8-r
Content-Transfer-Encoding: 8BIT
Subject: CVS corruption through cvs-cur.4733.gz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

       After receiving and applying CTM's 'cvs-cur.4733.gz'
to my CVS tree I try to "cvs update" my 3.0 tree and
discover that there are some directories deleted from
CVS tree (in 'ports'). Some of this deletions prevent
"cvs ... update -Pd ." to finish its work (f.e.
'ports/devel/glade/patches').

       What is the reason for this ?

       How can I correct/synchronize my CVS-tree ?

       N.Dudorov


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 06:35:46 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA12280
          for freebsd-current-outgoing; Sat, 17 Oct 1998 06:35:46 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gaia.euronet.nl (gaia.euronet.nl [194.134.0.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12275
          for ; Sat, 17 Oct 1998 06:35:39 -0700 (PDT)
          (envelope-from marcel@scc.nl)
Received: from scones.sup.scc.nl (i017.ztm.euronet.nl [194.134.112.18])
	by gaia.euronet.nl (8.8.8/8.8.8) with ESMTP id PAA07970
	from  for ; Sat, 17 Oct 1998 15:35:17 +0200 (MET DST)
Received: (from marcel@localhost)
	by scones.sup.scc.nl (8.9.1/8.9.1) id PAA23546
	for current@FreeBSD.ORG; Sat, 17 Oct 1998 15:10:37 +0200 (CEST)
	(envelope-from marcel)
Message-Id: <199810171310.PAA23546@scones.sup.scc.nl>
To: current@FreeBSD.ORG
From: Marcel Moolenaar 
Subject: Re: softupdates/smp
Date: Sat, 17 Oct 1998 14:54:47 +0200
Organization: S.C.C. vof
References:  <199810170934.LAA09826@sos.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386)
X-Accept-Language: en
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Sxren Schmidt wrote:

> > Solid here.  With CAM and softupdates.  Buildworlds like crazy.  Wasn't
> > always that way, but is now.  Real good, this machine get's used heavily
> > for schoolwork (I shouldn't run current on it, but I've been too heavily
> > infected with FreeBSD).
> >
> > It's a dual P6-166, Tyan Titan II.  Wouldn't part with it for the world.
>
> You are lucky I guess, I still think we have race problems in there, at
> least it breaks real fast on a make work -j8 or above on resonably
> fast hardware here, and remember your filesystem is then beyond repair...

This both confuses and worries me. I'm running softupdates on a SMP (dual
PII-266) machine with CAM with no problems. I don't have problems when
running make -jX buildworld, with X >= 8, either.

I'm running SMP for more than 4 months and softupdates for at least 6 weeks
(I don't remember exactly, but I enabled it to test the latest patches for
it). Now I'm being told I'm lucky?

I remember a discussion about exactly this a couple of months ago. I'm
surprised that there still is no consensus (albeit vague) on the current
state of SMP and softupdates.

I accept all consequences for running -current and even throw in some
alpha/beta-testing effort when resources permit it, but I'm not generally
happy when my filesystems FUBAR.

Can SMP and softupdates FUBAR my filesystems or can it still be repaired
(modulo bugs) by fsck?

marcel

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 06:47:22 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA13637
          for freebsd-current-outgoing; Sat, 17 Oct 1998 06:47:22 -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 GAA13622
          for ; Sat, 17 Oct 1998 06:47:17 -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 PAA00718;
	Sat, 17 Oct 1998 15:46:26 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <199810171346.PAA00718@gratis.grondar.za>
To: nnd@itfs.nsk.su (Nickolay Dudorov)
cc: current@FreeBSD.ORG
Subject: Re: CVS corruption through cvs-cur.4733.gz 
In-Reply-To: Your message of " Sat, 17 Oct 1998 20:06:03 +0700."  
References:  
Date: Sat, 17 Oct 1998 15:46:25 +0200
From: Mark Murray 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 wrote:
>        After receiving and applying CTM's 'cvs-cur.4733.gz'
> to my CVS tree I try to "cvs update" my 3.0 tree and
> discover that there are some directories deleted from
> CVS tree (in 'ports'). Some of this deletions prevent
> "cvs ... update -Pd ." to finish its work (f.e.
> 'ports/devel/glade/patches').
> 
>        What is the reason for this ?

Someone did something naughty in the repository?

>        How can I correct/synchronize my CVS-tree ?

Manually remove the conflict in your /usr/ports area.

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  Sat Oct 17 07:43:13 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA17982
          for freebsd-current-outgoing; Sat, 17 Oct 1998 07:43:13 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA17967
          for ; Sat, 17 Oct 1998 07:43:06 -0700 (PDT)
          (envelope-from shimon@simon-shapiro.org)
Received: (qmail 24582 invoked by uid 1000); 17 Oct 1998 15:46:17 -0000
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: <22286.908622736@time.cdrom.com>
Date: Sat, 17 Oct 1998 11:46:17 -0400 (EDT)
X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z#
 Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+
 O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc?
Reply-To: shimon@simon-shapiro.org
Organization: The Simon Shapiro Foundation
From: Simon Shapiro 
To: "Jordan K. Hubbard" 
Subject: Re: Show Stopper? Failure to Install 19981014
Cc: freebsd-current@FreeBSD.ORG, mike@smith.net.au,
        Bruce Evans 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Jordan K. Hubbard, On 17-Oct-98 you wrote:
> > Because newfs was broken in rev.1.9 of newfs/newfs.c (before 2.0.5R).
> > Unfortunately, the breaker didn't seem to have investigated the failure
> > mode, so I didn't know how to fix it when I backed out the breakage
> > in rev.1.22.
>  
>  Unfortunately, you broke it even worse.  Please don't cause worse
>  breakage, where breakage is defined as systems which no longer
>  install, in the process of fixing other breakage.  This "feature" in
>  1.22 will stay disabled until the root issues are figured out, not
>  before.

Please note that:

a.  At least here, newfs, in and by itself, in an installed system does not
    exhibit any of these messages, nor the faulty behavior.  Only the
    context of sysinstall, from the boot floppy does.

b.  We have not done a complete, destructive, install since the pre-CAM
    days.  The problem might have been there all along.

c.  The release we built on the 4th of October displays the messages but
    does not fail to install.  The release of the 13th displays the same
    messages but fails to install.

Maybe there is sme help in these notes...


Sincerely Yours,                 Shimon@Simon-Shapiro.ORG
                                             770.265.7340
Simon Shapiro

Unwritten code has no bugs and executes at twice the speed of mouth


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 08:48:45 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA25522
          for freebsd-current-outgoing; Sat, 17 Oct 1998 08:48:45 -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 IAA25517
          for ; Sat, 17 Oct 1998 08:48:43 -0700 (PDT)
          (envelope-from gibbs@narnia.plutotech.com)
Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id JAA11982; Sat, 17 Oct 1998 09:41:25 -0600 (MDT)
Date: Sat, 17 Oct 1998 09:41:25 -0600 (MDT)
From: "Justin T. Gibbs" 
Message-Id: <199810171541.JAA11982@narnia.plutotech.com>
To: Karl Pielorz 
cc: current@FreeBSD.ORG
Subject: Re: SCSI / CAM error or warning output?
Newsgroups: pluto.freebsd.current
In-Reply-To: <36287AC1.3F0C0D9C@tdx.co.uk>
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 <36287AC1.3F0C0D9C@tdx.co.uk> you wrote:
> ahc2 is a 2940UW, with 3 x Quantum drives on it.

Funny.  They look very much like Seagate drives to me.

> First 2 are un-terminated,
> third is using onboard active termination, controller is set to terminate high
> & low bits. Cable is a nice Adaptec cable (so _please_ don't tell me it's
> termination )...

This is a nice Adaptec cable *without* a built in terminator, right?

> This happens when the drives are 'busy' (but not totally thrashed)...

Does it only happen before the tag count is reduced, or does it happen
regardless of how man, "tagged openings now X" messages you see for the
offending target?

It looks like, at least for this particular rev of the firmware on these
drives, the drives continue to take in transactions above and beyond
their internal tag limit, hang up probably blocking on a resource shortage,
then do not properly clean up all pending transactions when we whap them
with a Bus Device Reset Message.  The Adaptec driver then starts seeing
transactions returned by the device that are no longer pending (they should
have been killed by the BDR) and complains.

You should look to see if there is later firmware available for this
drive.

--
Justin

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 09:29:33 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA28863
          for freebsd-current-outgoing; Sat, 17 Oct 1998 09:29:33 -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 JAA28858
          for ; Sat, 17 Oct 1998 09:29:28 -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 MAA02383
	for ; Sat, 17 Oct 1998 12:28:58 -0400 (EDT)
Date: Sat, 17 Oct 1998 12:28:58 -0400 (EDT)
From: Chuck Robey 
To: freebsd-current@FreeBSD.ORG
Subject: Latest kernel
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 am getting panics immediately after startup on the latest kernel now,
which I wasn't getting a few days ago.  I haven't used crash dumps
before, but I want to report something useful, so I want to start this,
and I have a question.

I've built the debugging kernel, about 10M in size, but I don't really
have room in /var to stick it, is there any problem with it being in
/usr2, where there's lots of room?  I have 2 swap partitions, and either
will easily handle the crash dump.

When the crash occurs, right after starting the smp stuff, and drops to
ddb, what's the command to get it to dump the crash dump?  Is it just
there automatically, and do I just type "panic" to get ddb to exit and
dump the core?

I understand I have to save the crash dump immediately after rebooting
-s with my good kernel, using savecore.  All the savecore examples give
/var/crash as the target, is that hardcoded in, or can I move it as I
showed above to /usr2 (/usr2/crash) after mounting /usr2 in single, so
it's writeable?

Thanks.  I'll report the results soon's I get them.

----------------------------+-----------------------------------------------
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 17 09:51:50 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA01529
          for freebsd-current-outgoing; Sat, 17 Oct 1998 09:51:50 -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 JAA01520
          for ; Sat, 17 Oct 1998 09:51:47 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id RAA00358;
	Sat, 17 Oct 1998 17:51:08 +0100 (BST)
Message-ID: <3628CABB.53B52FF1@tdx.co.uk>
Date: Sat, 17 Oct 1998 17:50:03 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Justin T. Gibbs" 
CC: current@FreeBSD.ORG
Subject: Re: SCSI / CAM error or warning output?
References: <199810171541.JAA11982@narnia.plutotech.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


"Justin T. Gibbs" wrote:
> 
> In article <36287AC1.3F0C0D9C@tdx.co.uk> you wrote:
> > ahc2 is a 2940UW, with 3 x Quantum drives on it.
> 
> Funny.  They look very much like Seagate drives to me.

Ugh... Sorry, Quantum on the brain... ;-)

> This is a nice Adaptec cable *without* a built in terminator, right?

Yes... ;-)
 
> > This happens when the drives are 'busy' (but not totally thrashed)...
> 
> Does it only happen before the tag count is reduced, or does it happen
> regardless of how man, "tagged openings now X" messages you see for the
> offending target?

Hmmm... Looking through the vast amounts of console output I've captured, it
appears to happen any time - sometimes theres "tagged openings now XX"
messages, other times theres not... (i.e. the first thing that appears on the
console is "ahc2:A:10: no active SCB for reconnecting target - issuing BUS
DEVICE RESET"
 
> It looks like, at least for this particular rev of the firmware on these
> drives, the drives continue to take in transactions above and beyond
> their internal tag limit, hang up probably blocking on a resource shortage,
> then do not properly clean up all pending transactions when we whap them
> with a Bus Device Reset Message.  The Adaptec driver then starts seeing
> transactions returned by the device that are no longer pending (they should
> have been killed by the BDR) and complains.
> 
> You should look to see if there is later firmware available for this
> drive.

Ok, I am doing now... Thanks for the info...

Regards,

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 10:10:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA03079
          for freebsd-current-outgoing; Sat, 17 Oct 1998 10:10:59 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03061;
          Sat, 17 Oct 1998 10:10:55 -0700 (PDT)
          (envelope-from roger@cs.strath.ac.uk)
Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3])
	by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id SAA02323
	Sat, 17 Oct 1998 18:10:28 +0100 (BST)
Message-ID: <3628CF7E.7BDB136A@cs.strath.ac.uk>
Date: Sat, 17 Oct 1998 18:10:22 +0100
From: Roger Hardiman 
Organization: Strathclyde Uni
X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-980520-SNAP i386)
MIME-Version: 1.0
To: current@FreeBSD.ORG, hackers@FreeBSD.ORG, roger@cs.strath.ac.uk
Subject: a.out format and MMX instructions on 3.0-release
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

On 3.0-RELEASE, when GAS is called to assemble a.out code, is it using
gas 2.9.1 or does it link
back to the old a.out toolchain assembler.

On my 3.0-current test machine 6 months ago, I upgraded gas with GAS
2.9.1. from GNU's binutils
by building a local copy of GAS for the i386-unknown-bsd-aout target.
I could happily build a.out binaries which included inline MMX assembler
code in my C files.

Unfer 3.0-RELEASE, if I rebuild my project with gcc -aout, it Rejects
the MMX instructions,
indicating it is not using gas 2.9.1 in aout mode but switching back to
old toolchain code.

Any comments on this.
I run a mix of 2.2.5 and 3.0 systems so I wanted to keep a.out for now.

Bye
Roger Hardiman
Strathclyde Uni Telepresence Group

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 10:15:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA03487
          for freebsd-current-outgoing; Sat, 17 Oct 1998 10:15:58 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03465;
          Sat, 17 Oct 1998 10:15:50 -0700 (PDT)
          (envelope-from roger@cs.strath.ac.uk)
Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3])
	by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id SAA02362
	Sat, 17 Oct 1998 18:15:07 +0100 (BST)
Message-ID: <3628D096.63BF824@cs.strath.ac.uk>
Date: Sat, 17 Oct 1998 18:15:02 +0100
From: Roger Hardiman 
Organization: Strathclyde Uni
X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-980520-SNAP i386)
MIME-Version: 1.0
To: hackers@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: a.out and MMX instructions 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ok, I solved my own problem

On 3.0-RELEASE

as -v       gives me GNU Assembler 2.9.1
as -aout -v gives me GNU Assembler 1.92.3
So aout mode does drop back to the old toolchain. That is a pitty.

So in order to make a.out binaries with MMX inline code, I need to make
a new
copy of gas 2.9.1 in a.out format. (which is not a problem. I have done
it before)

BTW, I use the MMX instructions in my image processing work. I got a 40%
speedup in my code.
For once, you can believe Intels hype.


Cheers
Roger Hardiman
Strathclyde Uni

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 10:35:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA05647
          for freebsd-current-outgoing; Sat, 17 Oct 1998 10:35:35 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from soccer.ksg.com (cm340421-b.ftwrth1.tx.home.com [24.4.2.116])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05641
          for ; Sat, 17 Oct 1998 10:35:31 -0700 (PDT)
          (envelope-from kgor@soccer.ksg.com)
Received: (from kgor@localhost)
	by soccer.ksg.com (8.8.8/8.8.8) id MAA10305;
	Sat, 17 Oct 1998 12:35:05 -0500 (CDT)
	(envelope-from kgor)
Date: Sat, 17 Oct 1998 12:35:05 -0500 (CDT)
Message-Id: <199810171735.MAA10305@soccer.ksg.com>
From: "Kent S. Gordon" 
To: current@FreeBSD.ORG
Subject: FreeBSD 3.0-RELEASE calcru: negative time 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I just installed FreeBSD 3.0-RELEASE.  I am getting a lot of messages
about calcru: negitive time for ftp processes.  This has happened both
with inbound and outbound ftp. I also had the problem with rcp.
Remote cvs is working find.  Any suggestions?

 Here is my /var/log/messages showing 
my configuration and the problem

Oct 17 00:43:13 ggzoo /kernel: Copyright (c) 1992-1998 FreeBSD Inc.
Oct 17 00:43:13 ggzoo /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993
Oct 17 00:43:13 ggzoo /kernel: The Regents of the University of California. All rights reserved.
Oct 17 00:43:13 ggzoo /kernel: FreeBSD 3.0-RELEASE #0: Fri Oct 16 16:52:08 GMT 1998
Oct 17 00:43:13 ggzoo /kernel: jkh@kickme.freebsd.org:/usr/src/sys/compile/GENERIC
Oct 17 00:43:13 ggzoo /kernel: Timecounter "i8254"  frequency 1193182 Hz  cost 3794 ns
Oct 17 00:43:13 ggzoo /kernel: Timecounter "TSC"  frequency 179629231 Hz  cost 271 ns
Oct 17 00:43:13 ggzoo /kernel: CPU: Pentium Pro (179.63-MHz 686-class CPU)
Oct 17 00:43:13 ggzoo /kernel: Origin = "GenuineIntel"  Id = 0x616  Stepping=6
Oct 17 00:43:13 ggzoo /kernel: Features=0xf9ff
Oct 17 00:43:13 ggzoo /kernel: real memory  = 67108864 (65536K bytes)
Oct 17 00:43:13 ggzoo /kernel: avail memory = 62488576 (61024K bytes)
Oct 17 00:43:13 ggzoo /kernel: Probing for devices on PCI bus 0:
Oct 17 00:43:13 ggzoo /kernel: chip0:  rev 0x02 on pci0.0.0
Oct 17 00:43:13 ggzoo /kernel: chip1:  rev 0x01 on pci0.1.0
Oct 17 00:43:13 ggzoo /kernel: ide_pci0:  rev 0x00 on pci0.1.1
Oct 17 00:43:13 ggzoo /kernel: ncr0:  rev 0x11 int a irq 9 on pci0.9.0
Oct 17 00:43:13 ggzoo /kernel: vga0:  rev 0x00 int a irq 12 on pci0.11.0
Oct 17 00:43:13 ggzoo /kernel: Probing for devices on the
Oct 17 00:43:13 ggzoo /kernel: ISA bus:
Oct 17 00:43:13 ggzoo /kernel: sc0 at 0x60-0x6f irq 1 on motherboard
Oct 17 00:43:13 ggzoo /kernel: sc0: VGA color <16 virtual consoles, flags=0x0>
Oct 17 00:43:13 ggzoo /kernel: ed0 not found at 0x280
Oct 17 00:43:13 ggzoo /kernel: fe0 not found at 0x300
Oct 17 00:43:13 ggzoo /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
Oct 17 00:43:13 ggzoo /kernel: sio0: type 16550A
Oct 17 00:43:13 ggzoo /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa
Oct 17 00:43:13 ggzoo /kernel: sio1: type 16550A
Oct 17 00:43:13 ggzoo /kernel: lpt0 at 0x378-0x37f irq 7 on isa
Oct 17 00:43:13 ggzoo /kernel: lpt0: Interrupt-driven port
Oct 17 00:43:13 ggzoo /kernel: lp0: TCP/IP capable interface
Oct 17 00:43:13 ggzoo /kernel: psm0 not found at 0x60
Oct 17 00:43:13 ggzoo /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
Oct 17 00:43:13 ggzoo /kernel: fdc0: FIFO enabled, 8 bytes threshold
Oct 17 00:43:14 ggzoo /kernel: fd0: 1.44MB 3.5in
Oct 17 00:43:14 ggzoo /kernel: fd1: 1.2MB 5.25in
Oct 17 00:43:14 ggzoo /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa
Oct 17 00:43:14 ggzoo /kernel: wdc0: unit 0 (wd0): 
Oct 17 00:43:14 ggzoo /kernel: wd0: 2452MB (5021856 sectors), 4982 cyls, 16 heads, 63 S/T, 512 B/S
Oct 17 00:43:14 ggzoo /kernel: wdc0: unit 1 (wd1): 
Oct 17 00:43:14 ggzoo /kernel: wd1: 2452MB (5021856 sectors), 4982 cyls, 16 heads, 63 S/T, 512 B/S
Oct 17 00:43:14 ggzoo /kernel: wdc1 at 0x170-0x177 irq 15 on isa
Oct 17 00:43:14 ggzoo /kernel: wdc1: unit 0 (atapi): , removable, accel, dma, iordis
Oct 17 00:43:14 ggzoo /kernel: wcd0: 1378Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray
Oct 17 00:43:14 ggzoo /kernel: wcd0: no disc inside, unlocked
Oct 17 00:43:14 ggzoo /kernel: wt0 not found at 0x300
Oct 17 00:43:14 ggzoo /kernel: mcd0 not found at 0x300
Oct 17 00:43:14 ggzoo /kernel: matcdc0 not found at 0x230
Oct 17 00:43:14 ggzoo /kernel: s
Oct 17 00:43:14 ggzoo /kernel: cd0 not found at 0x230
Oct 17 00:43:14 ggzoo /kernel: ie0: unknown board_id: 0
Oct 17 00:43:14 ggzoo /kernel: ie0 not found at 0x300
Oct 17 00:43:14 ggzoo /kernel: ep0 not found at 0x300
Oct 17 00:43:14 ggzoo /kernel: ex0 not found
Oct 17 00:43:14 ggzoo /kernel: le0 not found at 0x300
Oct 17 00:43:14 ggzoo /kernel: lnc0 not found at 0x280
Oct 17 00:43:14 ggzoo /kernel: ze0 not found at 0x300
Oct 17 00:43:14 ggzoo /kernel: zp0 not found at 0x300
Oct 17 00:43:14 ggzoo /kernel: cs0 not found at 0x300
Oct 17 00:43:14 ggzoo /kernel: adv0 not found at 0x330
Oct 17 00:43:14 ggzoo /kernel: bt0 not found at 0x134
Oct 17 00:43:14 ggzoo /kernel: aha0 not found at 0x134
Oct 17 00:43:14 ggzoo /kernel: npx0 on motherboard
Oct 17 00:43:14 ggzoo /kernel: npx0: INT 16 interface
Oct 17 00:43:14 ggzoo /kernel: Waiting 15 seconds for SCSI devices to settle
Oct 17 00:43:14 ggzoo /kernel: changing root device to wd0s1a
Oct 17 00:43:26 ggzoo login: ROOT LOGIN (root) ON ttyv0
Oct 17 00:43:48 ggzoo reboot: rebooted by root
Oct 17 00:43:48 ggzoo syslogd: exiting on signal 15
Oct 17 00:47:11 ggzoo /kernel: ory controller> rev 0x02 on pci0.0.0
Oct 17 00:47:11 ggzoo /kernel: found->	vendor=0x8086, dev=0x7000, revid=0x01
Oct 17 00:47:11 ggzoo /kernel: class=06-01-00, hdrtype=0x00, mfdev=1
Oct 17 00:47:11 ggzoo /kernel: subordinatebus=0 	secondarybus=0
Oct 17 00:47:11 ggzoo /kernel: chip1:  rev 0x01 on pci0.1.0
Oct 17 00:47:11 ggzoo /kernel: I/O Recovery Timing: 8-bit 3.5 clocks, 16-bit 3.5 clocks
Oct 17 00:47:11 ggzoo /kernel: Extended BIOS: disabled
Oct 17 00:47:11 ggzoo /kernel: Lower BIOS: enabled
Oct 17 00:47:11 ggzoo /kernel: Coprocessor IRQ13: enabled
Oct 17 00:47:11 ggzoo /kernel: Mouse IRQ12: disabled
Oct 17 00:47:11 ggzoo /kernel: Interrupt Routing: A: disabled, B: IRQ12, C: disabled, D: IRQ9
Oct 17 00:47:11 ggzoo /kernel: MB0: IRQ15, MB1: 
Oct 17 00:47:11 ggzoo /kernel: found->	vendor=0x8086, dev=0x7010, revid=0x00
Oct 17 00:47:11 ggzoo /kernel: class=01-01-80, hdrtype=0x00, mfdev=0
Oct 17 00:47:11 ggzoo /kernel: subordinatebus=0 	secondarybus=0
Oct 17 00:47:11 ggzoo /kernel: ide_pci0:  rev 0x00 on pci0.1.1
Oct 17 00:47:11 ggzoo /kernel: intel_piix_status: primary master sample = 3, master recovery = 1
Oct 17 00:47:11 ggzoo /kernel: intel_piix_status: primary master fastDMAonly disabled, pre/post enabled,
Oct 17 00:47:11 ggzoo /kernel: intel_piix_status:  IORDY sampling enabled,
Oct 17 00:47:11 ggzoo /kernel: intel_piix_status:  fast PIO enabled
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status: primary slave sample = 3, slave recovery = 1
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status: primary slave fastDMAonly disabled, pre/post enabled,
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status:
Oct 17 00:47:12 ggzoo /kernel: IORDY sampling enabled,
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status:  fast PIO enabled
Oct 17 00:47:12 ggzoo /kernel: ide_pci: busmaster 0 status: 04 from port: 0000e802
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status: secondary master sample = 4, master recovery = 2
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled,
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status:  IORDY sampling enabled,
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status:  fast PIO enabled
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status: secondary slave sample = 5, slave recovery = 4
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled,
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status:  IORDY sampling disabled,
Oct 17 00:47:12 ggzoo /kernel: intel_piix_status:  fast PIO disabled
Oct 17 00:47:12 ggzoo /kernel: ide_pci: busmaster 1 status: 04 from port: 0000e80a
Oct 17 00:47:12 ggzoo /kernel: found->	vendor=0x1000, dev=0x0001, revid=0x11
Oct 17 00:47:12 ggzoo /kernel: class=01-00-00, hdrtype=0x00, mfdev=0
Oct 17 00:47:12 ggzoo /kernel: subordinatebus=0 	secondarybus=0
Oct 17 00:47:12 ggzoo /kernel: intpin=a, irq=9
Oct 17 00:47:12 ggzoo /kernel: map[0]: type 4, range 32, base 0000e000, size  8
Oct 17 00:47:12 ggzoo /kernel: map[1]: type 1, range 32, base fb000000, size  8
Oct 17 00:47:12 ggzoo /kernel: ncr0:  rev 0x11 int a irq 9 on pci0.9.0
Oct 17 00:47:12 ggzoo /kernel: ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo
Oct 17 00:47:12 ggzoo /kernel: ncr0: single-ended, open drain
Oct 17 00:47:12 ggzoo /kernel: IRQ driver
Oct 17 00:47:12 ggzoo /kernel: found->	vendor=0x5333, dev=0x88f0, revid=0x00
Oct 17 00:47:12 ggzoo /kernel: class=03-00-00, hdrtype=0x00, mfdev=0
Oct 17 00:47:12 ggzoo /kernel: subordinatebus=0 	secondarybus=0
Oct 17 00:47:12 ggzoo /kernel: intpin=a, irq=12
Oct 17 00:47:12 ggzoo /kernel: map[0]: type 1, range 32, base f8000000, size 25
Oct 17 00:47:12 ggzoo /kernel: vga0:  rev 0x00 int a irq 12 on pci0.11.0
Oct 17 00:47:12 ggzoo /kernel: Probing for devices on the ISA bus:
Oct 17 00:47:12 ggzoo /kernel: video: RTC equip. code:0x4f, DCC code:0x09
Oct 17 00:47:12 ggzoo /kernel: video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16
Oct 17 00:47:12 ggzoo /kernel: video: param table EGA/VGA:0xf00c396c, CGA/MDA:0
Oct 17 00:47:12 ggzoo /kernel: video: rows_offset:1
Oct 17 00:47:12 ggzoo /kernel: video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4
Oct 17 00:47:12 ggzoo /kernel: video#0: init mode:24, bios mode:3, current mode:24
Oct 17 00:47:13 ggzoo /kernel: video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#
Oct 17 00:47:13 ggzoo /kernel: 0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:6, flags:0x3 G 640x200x1, 1 plan
Oct 17 00:47:13 ggzoo /kernel: e(s), font:8x8, win:0xb8000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000
Oct 17 00:47:13 ggzoo /kernel: video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000
Oct 17 00:47:13 ggzoo /kernel: VGA parameters upon power-up
Oct 17 00:47:14 ggzoo /kernel: 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
Oct 17 00:47:14 ggzoo /kernel: bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 
Oct 17 00:47:14 ggzoo /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
Oct 17 00:47:14 ggzoo /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
Oct 17 00:47:14 ggzoo /kernel: VGA parameters
Oct 17 00:47:14 ggzoo /kernel: in BIOS for mode 24
Oct 17 00:47:14 ggzoo /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
Oct 17 00:47:14 ggzoo /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
Oct 17 00:47:14 ggzoo /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
Oct 17 00:47:14 ggzoo /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
Oct 17 00:47:14 ggzoo /kernel: EGA/VGA parameters to be used for mode 24
Oct 17 00:47:14 ggzoo /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
Oct 17 00:47:14 ggzoo /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
Oct 17 00:47:14 ggzoo /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
Oct 17 00:47:14 ggzoo /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
Oct 17 00:47:14 ggzoo /kernel: sc0: the current keyboard controller command byte 0065
Oct 17 00:47:14 ggzoo /kernel: kbdio: DIAGNOSE status:0055
Oct 17 00:47:14 ggzoo /kernel: kbdio: TEST_KBD_PORT status:0000
Oct 17 00:47:14 ggzoo /kernel: kbdio: RESET_KBD return code:00fa
Oct 17 00:47:14 ggzoo /kernel: kbdio: RESET_KBD status:00aa
Oct 17 00:47:14 ggzoo /kernel: sc0: keyboard device ID: ab41
Oct 17 00:47:14 ggzoo /kernel: sc0 at 0x60-0x6f irq 1 on motherboard
Oct 17 00:47:14 ggzoo /kernel: sc0: VGA color <16 virtual consoles, flags=0x0>
Oct 17 00:47:14 ggzoo /kernel: ed0 at 0x300-0x31f irq 10 on isa
Oct 17 00:47:14 ggzoo /kernel: ed0: address 00:40:33:58:9b:b7, type NE2000 (16 bit) 
Oct 17 00:47:14 ggzoo /kernel: fe0: disabled, not probed.
Oct 17 00:47:14 ggzoo /kernel: sio0: irq maps: 0x1 0x11 0x1 0x1
Oct 17 00:47:14 ggzoo /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
Oct 17 00:47:14 ggzoo /kernel: sio0: type 16550A
Oct 17 00:47:14 ggzoo /kernel: sio1: irq maps: 0x1 0x9 0x1 0x1
Oct 17 00:47:14 ggzoo /kernel: sio1 at 0x2f8-0x2ff 
Oct 17 00:47:14 ggzoo /kernel: irq 3 on isa
Oct 17 00:47:14 ggzoo /kernel: sio1: type 16550A
Oct 17 00:47:14 ggzoo /kernel: sio2: disabled, not probed.
Oct 17 00:47:14 ggzoo /kernel: sio3: disabled, not probed.
Oct 17 00:47:14 ggzoo /kernel: lpt0 at 0x378-0x37f irq 7 on isa
Oct 17 00:47:15 ggzoo /kernel: lpt0: Interrupt-driven port
Oct 17 00:47:15 ggzoo /kernel: lp0: TCP/IP capable interface
Oct 17 00:47:15 ggzoo /kernel: psm0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
Oct 17 00:47:15 ggzoo /kernel: fdc0: FIFO enabled, 8 bytes threshold
Oct 17 00:47:15 ggzoo /kernel: fd0: 1.44MB 3.5in
Oct 17 00:47:15 ggzoo /kernel: fd1: 1.2MB 5.25in
Oct 17 00:47:15 ggzoo /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa
Oct 17 00:47:15 ggzoo /kernel: wdc0: unit 0 (wd0): 
Oct 17 00:47:15 ggzoo /kernel: wd0: 2452MB (5021856 sectors), 4982 cyls, 16 heads, 63 S/T, 512 B/S
Oct 17 00:47:15 ggzoo /kernel: wd0: ATA INQUIRE valid = 0003, dmamword = 0007, apio = 0003, udma = 0000
Oct 17 00:47:15 ggzoo /kernel: wdc0: unit 1 (wd1): 
Oct 17 00:47:15 ggzoo /kernel: wd1: 2452MB (5021856 sectors), 4982 cyls, 16 heads, 63 S/T, 512 B/S
Oct 17 00:47:15 ggzoo /kernel: wd1: ATA INQUIRE valid = 0003, dmamword = 0007, apio = 0003, udma = 0000
Oct 17 00:47:15 ggzoo /kernel: wdc1 at 0x170-0x177 irq 15 on isa
Oct 17 00:47:15 ggzoo /kernel: wdc1: unit 0 (atapi): , removable, accel, dma, iordis
Oct 17 00:47:15 ggzoo /kernel: wcd0: 1378Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray
Oct 17 00:47:15 ggzoo /kernel: wcd0: no disc inside, unlocked
Oct 17 00:47:15 ggzoo /kernel: wt0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: mcd0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: matcdc0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: scd0: 
Oct 17 00:47:15 ggzoo /kernel: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: ie0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: ep0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: ex0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: le0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: lnc0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: ze0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: zp0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: cs0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: adv0: disabled, not probed.
Oct 17 00:47:15 ggzoo /kernel: bt0: disabled, not probed.
Oct 17 00:47:16 ggzoo /kernel: aha0: disabled, not probed.
Oct 17 00:47:16 ggzoo /kernel: npx0 on motherboard
Oct 17 00:47:16 ggzoo /kernel: npx0: INT 16 interface
Oct 17 00:47:16 ggzoo /kernel: apm0: disabled, not probed.
Oct 17 00:47:16 ggzoo /kernel: imasks: bio c008c040, tty c007049a, net c007049a
Oct 17 00:47:16 ggzoo /kernel: BIOS Geometries:
Oct 17 00:47:16 ggzoo /kernel: 0:026c7f3f 0..620=621 cylinders, 0..127=128 heads, 1..63=63 sectors
Oct 17 00:47:16 ggzoo /kernel: 1:026c7f3f 0..620=621 cylinders, 0..127=128 heads, 1..63=63 sectors
Oct 17 00:47:16 ggzoo /kernel: 0 accounted for
Oct 17 00:47:16 ggzoo /kernel: Device configuration finished.
Oct 17 00:47:16 ggzoo /kernel: new masks: bio c008c040, tty c007049a, net c007049a
Oct 17 00:47:16 ggzoo /kernel: Waiting 15 seconds for SCSI devices to settle
Oct 17 00:47:16 ggzoo /kernel: ncr0: restart (scsi reset).
Oct 17 00:47:16 ggzoo /kernel: Considering MFS root f/s.
Oct 17 00:47:16 ggzoo /kernel: No MFS image available as root f/s.
Oct 17 00:47:16 ggzoo /kernel: Considering FFS root f/s.
Oct 17 00:47:16 ggzoo /kernel: changing root device to wd0s1a
Oct 17 00:47:16 ggzoo /kernel: wd0s1: type 0xa5, start 0, end = 5021855, size 5021856 : OK
Oct 17 00:47:16 ggzoo /kernel: wd1s1: type 0xa5, start 0, end = 5021855, size 5021856 : OK
Oct 17 00:47:25 ggzoo login: ROOT LOGIN (root) ON ttyv0
Oct 17 11:14:05 ggzoo login: ROOT LOGIN (root) ON ttyv0
Oct 17 11:29:43 ggzoo /kernel: wcd0: cannot read audio disc
Oct 17 11:53:13 ggzoo ftpd[3263]: ANONYMOUS FTP LOGIN REFUSED FROM soccer.ksg.com
Oct 17 11:53:17 ggzoo ftpd[3263]: FTP LOGIN REFUSED FROM soccer.ksg.com, root
Oct 17 11:53:31 ggzoo login: ROOT LOGIN (root) ON ttyv1
Oct 17 11:55:19 ggzoo /kernel: calcru: negative time of -18675438 usec for pid 3272 (ftp)
Oct 17 11:55:19 ggzoo /kernel: calcru: negative time of -18674285 usec for pid 3272 (ftp)
Oct 17 11:58:54 ggzoo /kernel: calcru: negative time of -21080244 usec for pid 3284 (ftp)
Oct 17 11:58:54 ggzoo /kernel: calcru: negative time of -21078710 usec for pid 3284 (ftp)
Oct 17 12:02:45 ggzoo /kernel: calcru: negative time of -21934061 usec for pid 3302 (rcp)
Oct 17 12:02:46 ggzoo /kernel: calcru: negative time of -21933678 usec for pid 3302 (rcp)
Oct 17 12:06:54 ggzoo /kernel: calcru: negative time of -10935186 usec for pid 3325 (ftpd)
Oct 17 12:06:54 ggzoo /kernel: calcru: negative time of -10932361 usec for pid 3325 (ftpd)
Oct 17 12:09:46 ggzoo /kernel: calcru: negative time of -23279483 usec for pid 3332 (ftp)
Oct 17 12:09:46 ggzoo /kernel: calcru: negative time of -23277065 usec for pid 3332 (ftp)
Oct 17 12:11:05 ggzoo /kernel: calcru: negative time of -21597967 usec for pid 3333 (ftp)
Oct 17 12:11:05 ggzoo /kernel: calcru: negative time of -21597442 usec for pid 3333 (ftp)

-- 
Kent S. Gordon 
KSG  --  Unix, Network, Database Consulting
Postal: 76 Corral Drive North, Keller, Texas 76248
e-mail: kgor@ksg.com Phone:(817)431-8775 Resume: http://www.ksg.com/resume.html

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 10:44:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA06024
          for freebsd-current-outgoing; Sat, 17 Oct 1998 10:44:35 -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 KAA06018
          for ; Sat, 17 Oct 1998 10:44:33 -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 KAA00384;
	Sat, 17 Oct 1998 10:44:05 -0700 (PDT)
	(envelope-from jdp)
Message-Id: <199810171744.KAA00384@austin.polstra.com>
To: Greg Lehey 
cc: current@FreeBSD.ORG
Subject: Re: Why can't I check out RELENG_3_0_0_RELEASE? 
In-reply-to: Your message of "Sat, 17 Oct 1998 12:26:57 +0930."
    <19981017122657.X469@freebie.lemis.com> 
Date: Sat, 17 Oct 1998 10:44:05 -0700
From: John Polstra 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> OK, it wasn't in val-tags, so I tried again, with
> 
>    cvs co -r RELENG_3_0_0_RELEASE src
> 
> It took nearly 10 minutes, during which it created only src/CVS and
> (correct) contents.  Then it started checking out normally.  It still
> hasn't finished, but it has updated val-tags, so I'll assume it's a
> quirk rather than a bug.  I'll put something in the book about it.
> 
> > I don't know why it doesn't find the tag sooner than it does.  I have
> > a suspicion that it's searching the whole repository including the
> > ports tree, which does not contain that tag.
> 
> It can't be that simple, since this time I checked out only src.

But that's what I'm saying -- I suspect it searches the whole
repository regardless of which module you're checking out.

Strictly speaking, it has to do that.  It needs to know whether the
tag is valid anywhere in the repository.  If it's valid even outside
of the module you're checking out, then has to know that so it won't
tell you that the tag is invalid.  But it could be a lot smarter
about it.  It should search first in the module you specified, and
only later in other places.

John

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 11:12:34 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA07972
          for freebsd-current-outgoing; Sat, 17 Oct 1998 11:12:34 -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 LAA07964
          for ; Sat, 17 Oct 1998 11:12:30 -0700 (PDT)
          (envelope-from obrien@NUXI.com)
Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id LAA19232; Sat, 17 Oct 1998 11:11:58 -0700 (PDT)
Message-ID: <19981017111157.A19217@nuxi.com>
Date: Sat, 17 Oct 1998 11:11:57 -0700
From: "David O'Brien" 
To: Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
Reply-To: obrien@NUXI.com
References: 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: ; from Chuck Robey on Sat, Oct 17, 1998 at 12:28:58PM -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

> have room in /var to stick it, is there any problem with it being in
> /usr2, where there's lots of room?  

    cd /var
    mv crash crash.orig
    mkdir /usr2/crash
    ln -s /usr2/crash .

And you are done.  The savecore runs in RC after all file systems are
mounted.

-- 
-- 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 17 11:25:34 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA08745
          for freebsd-current-outgoing; Sat, 17 Oct 1998 11:25:34 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08740
          for ; Sat, 17 Oct 1998 11:25: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 LAA06756;
	Sat, 17 Oct 1998 11:27:08 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810171827.LAA06756@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Karl Pielorz 
cc: current@FreeBSD.ORG
Subject: Re: Serial Console - broken? (src as of 10/16 @ 16:43) 
In-reply-to: Your message of "Sat, 17 Oct 1998 12:00:54 BST."
             <362878E6.3EE89054@tdx.co.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 17 Oct 1998 11:27:08 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Hi,
> 
> I'm running a serial console for ddb etc. - This used to work great, but with
> recent builds every time the system panic's, I get the usual details about the
> panic, but it ends with:
> 
> "
> current process         = Idle
> interrupt mask          = bio  <- SMP: XXX
> $T0b08:079713f0;05:784b80ff;04:644b80ff;#b4
> "
> 
> Any key presses on the serial console result in
> "04:644b80ff;#b4$T0b08:079713f0;" being displayed...
> 
> 'Ah, serial port speed I thought', erm, nope - double checking /etc/make.conf
> etc. it's set to 57600... Trying different speeds while it's in this state
> doesn't net anything better (I get a lot of 'xxx's at lower speeds, which are
> normal symptomatic of wrong serial speed).

You appear to be booting with the '-g' flag, as what you're seeing 
looks like the gdb-remote protocol.  The simple answer is "don't".

-- 
\\  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 17 11:34:51 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA09533
          for freebsd-current-outgoing; Sat, 17 Oct 1998 11:34:51 -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 LAA09527
          for ; Sat, 17 Oct 1998 11:34:47 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id TAA00279;
	Sat, 17 Oct 1998 19:34:12 +0100 (BST)
Message-ID: <3628E2E3.2EB04701@tdx.co.uk>
Date: Sat, 17 Oct 1998 19:33:07 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Mike Smith 
CC: current@FreeBSD.ORG
Subject: Re: Serial Console - broken? (src as of 10/16 @ 16:43)
References: <199810171827.LAA06756@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:

> You appear to be booting with the '-g' flag, as what you're seeing
> looks like the gdb-remote protocol.  The simple answer is "don't".

Hmmm... If that's what the output looks like, then valid point...

But I've just checked my /boot.config - which didn't mention '-g', and I've
just blown that away, checked my kernel config and /etc/make.config (which
certainly doesn't specify it - or GDB_REMOTE_CHAT or similar), and it still
does it...?

Weird?

What would you suggest next?  I haven't changed anything other than a build /
install world since everything was working fine (which I think was Wednesday?)

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 12:02:05 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA11247
          for freebsd-current-outgoing; Sat, 17 Oct 1998 12:02:05 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11232
          for ; Sat, 17 Oct 1998 12:02:02 -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 MAA06992;
	Sat, 17 Oct 1998 12:06:21 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810171906.MAA06992@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Karl Pielorz 
cc: Mike Smith , current@FreeBSD.ORG
Subject: Re: Serial Console - broken? (src as of 10/16 @ 16:43) 
In-reply-to: Your message of "Sat, 17 Oct 1998 19:33:07 BST."
             <3628E2E3.2EB04701@tdx.co.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 17 Oct 1998 12:06:20 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> Mike Smith wrote:
> 
> > You appear to be booting with the '-g' flag, as what you're seeing
> > looks like the gdb-remote protocol.  The simple answer is "don't".
> 
> Hmmm... If that's what the output looks like, then valid point...
> 
> But I've just checked my /boot.config - which didn't mention '-g', and I've
> just blown that away, checked my kernel config and /etc/make.config (which
> certainly doesn't specify it - or GDB_REMOTE_CHAT or similar), and it still
> does it...?
> 
> Weird?
> 
> What would you suggest next?  I haven't changed anything other than a build /
> install world since everything was working fine (which I think was Wednesday?)

Um, try checking the flags on your serial console.  You should have 0x10
or 0x30, but 0x50 or 0x70 would be bad.  (ie. you don't want 0x40 set).

Apart from that, there's the hideous fear that something leaked in and 
GDB is the default debugger.  Ick.

-- 
\\  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 17 12:03:28 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA11466
          for freebsd-current-outgoing; Sat, 17 Oct 1998 12:03:28 -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 MAA11454
          for ; Sat, 17 Oct 1998 12:03:25 -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 PAA00359;
	Sat, 17 Oct 1998 15:02:29 -0400 (EDT)
Date: Sat, 17 Oct 1998 15:02:29 -0400 (EDT)
From: Chuck Robey 
To: "David O'Brien" 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
In-Reply-To: <19981017111157.A19217@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, 17 Oct 1998, David O'Brien wrote:

> > have room in /var to stick it, is there any problem with it being in
> > /usr2, where there's lots of room?  
> 
>     cd /var
>     mv crash crash.orig
>     mkdir /usr2/crash
>     ln -s /usr2/crash .
> 
> And you are done.  The savecore runs in RC after all file systems are
> mounted.

OK, I set everything up.  Dumpon knows where to go, savecore knows also,
but when I actually did it, savecore told me there was no core there.
When the kernel panics, I'm in ddb... how do I force ddb to make the
kernel leave a core file around?

I have the data, handcopied, but I want to figure from the addresses I
have to real functions.

Thanks.


----------------------------+-----------------------------------------------
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 17 12:44:05 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA15835
          for freebsd-current-outgoing; Sat, 17 Oct 1998 12:44:05 -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 MAA15795
          for ; Sat, 17 Oct 1998 12:43:57 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id UAA00463;
	Sat, 17 Oct 1998 20:43:26 +0100 (BST)
Message-ID: <3628F31C.29EE2587@tdx.co.uk>
Date: Sat, 17 Oct 1998 20:42:20 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Mike Smith 
CC: current@FreeBSD.ORG
Subject: Re: Serial Console - broken? (src as of 10/16 @ 16:43)
References: <199810171906.MAA06992@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:

> Um, try checking the flags on your serial console.  You should have 0x10
> or 0x30, but 0x50 or 0x70 would be bad.  (ie. you don't want 0x40 set).
> 
> Apart from that, there's the hideous fear that something leaked in and
> GDB is the default debugger.  Ick.

Hmmm... Serial console is definitely set to:

device          sio0    at isa? port "IO_COM1" flags 0x30 tty irq 4 vector
siointr

I presume 'Ick' is bad, but how bad? - i.e. easily fixable?

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 12:50:34 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA16443
          for freebsd-current-outgoing; Sat, 17 Oct 1998 12:50:34 -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 MAA16438
          for ; Sat, 17 Oct 1998 12:50:31 -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 PAA00382
	for ; Sat, 17 Oct 1998 15:50:02 -0400 (EDT)
Date: Sat, 17 Oct 1998 15:50:02 -0400 (EDT)
From: Chuck Robey 
To: freebsd-current@FreeBSD.ORG
Subject: panic
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 now getting a panic on startup, SMP kernel, on a config file that
was working fine a few days ago.  The panic is coming in module_register
+ 14.  I'd give you the stack dump, but I can't seem to get a kernel
dump captured yet.

I checked, all my LKMs are brand new.  This is a fresh build for both
the world and the kernel from equal sources (no intervening cvsup or cvs
actions), with all new LKMs.  Normal ELF system you'd expect.

Panic is supervisor read, page not present.  Can't tell what module it
was trying to load without the kernel dump (I think).  Panic message
says it's in the swapper process, but I think that's not germane here
(is it?).  I have a fault virtual address of 8be58955, I'm not sure
that's useful, seeing as I can't translate that to a module address.

How do I force a kernel dump?

----------------------------+-----------------------------------------------
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 17 12:58:34 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA17395
          for freebsd-current-outgoing; Sat, 17 Oct 1998 12:58:34 -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 MAA17383
          for ; Sat, 17 Oct 1998 12:58:27 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id UAA00482;
	Sat, 17 Oct 1998 20:47:19 +0100 (BST)
Message-ID: <3628F405.E6F17E82@tdx.co.uk>
Date: Sat, 17 Oct 1998 20:46:13 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Chuck Robey 
CC: freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
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:

> OK, I set everything up.  Dumpon knows where to go, savecore knows also,
> but when I actually did it, savecore told me there was no core there.
> When the kernel panics, I'm in ddb... how do I force ddb to make the
> kernel leave a core file around?
> 
> I have the data, handcopied, but I want to figure from the addresses I
> have to real functions.

Issuing 'panic' from ddb should get the system to dump the core, you should
see something like:

"
db> panic
panic: from debugger
mp_lock = 01000002; cpuid = 1; lapic.id = 01000000
boot() called on cpu#1
syncing disks... 4 done

dumping to dev 20009, offset 262144
dump 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65
64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 4 5 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 succeeded
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
"

(ignore the 'mp_lock and boot() called bits - I run SMP :)

When the system reboots - you should see savecore kick in and write the dump
from the dumpdevice to /var/crash...

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 13:03:33 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA18339
          for freebsd-current-outgoing; Sat, 17 Oct 1998 13:03:33 -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 NAA18328
          for ; Sat, 17 Oct 1998 13:03:28 -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 QAA18733;
	Sat, 17 Oct 1998 16:02:48 -0400 (EDT)
Date: Sat, 17 Oct 1998 16:02:48 -0400 (EDT)
To: Matt Behrens 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: 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 Fri, 16 Oct 1998, Matt Behrens wrote:

> I got the same thing on my 2477/16/63 disk (same machine I was

Toshiba MK4006MAV driving a 7944/16/63 here.

> Mike: what was the last beta you used successfully?

I've been running the 5/20 SNAP with great success on multiple
(heavily loaded) production SMP servers for awhile.  I was going to
take a newer NS up to BETA to play with it, but after trying 1014 
and 1015 I fell back to the 5/20 SNAP again.

I should try the 1017 SNAP...

Later,

	-mike


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 13:05:05 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA18676
          for freebsd-current-outgoing; Sat, 17 Oct 1998 13:05:05 -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 NAA18638
          for ; Sat, 17 Oct 1998 13:04:53 -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 QAA00404;
	Sat, 17 Oct 1998 16:04:13 -0400 (EDT)
Date: Sat, 17 Oct 1998 16:04:13 -0400 (EDT)
From: Chuck Robey 
To: Karl Pielorz 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
In-Reply-To: <3628F405.E6F17E82@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:

> > OK, I set everything up.  Dumpon knows where to go, savecore knows also,
> > but when I actually did it, savecore told me there was no core there.
> > When the kernel panics, I'm in ddb... how do I force ddb to make the
> > kernel leave a core file around?
> > 
> > I have the data, handcopied, but I want to figure from the addresses I
> > have to real functions.
> 
> Issuing 'panic' from ddb should get the system to dump the core, you should
> see something like:
> 
> "
> db> panic
> panic: from debugger
> mp_lock = 01000002; cpuid = 1; lapic.id = 01000000
> boot() called on cpu#1
> syncing disks... 4 done

Get this part, but

> 
> dumping to dev 20009, offset 262144
> dump 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65
> 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 4 5 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 succeeded
> Automatic reboot in 15 seconds - press a key on the console to abort
> Rebooting...
> "

I don't get this part.  It's not doing the dump.

I separately posted a bunch of copied-down stuff on the ddb panic info I
got, but I'd sure like to see the dump, especially with the symbols from
my kernel.debug (compiled from config -g).

I want to know what's dying.

> 
> (ignore the 'mp_lock and boot() called bits - I run SMP :)
> 
> When the system reboots - you should see savecore kick in and write the dump
> from the dumpdevice to /var/crash...
> 
> Karl
> 
> 

----------------------------+-----------------------------------------------
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 17 13:32:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA22112
          for freebsd-current-outgoing; Sat, 17 Oct 1998 13:32:35 -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 NAA22093
          for ; Sat, 17 Oct 1998 13:32:28 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id VAA00616;
	Sat, 17 Oct 1998 21:32:00 +0100 (BST)
Message-ID: <3628FE7F.6C5F65D7@tdx.co.uk>
Date: Sat, 17 Oct 1998 21:30:55 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Chuck Robey 
CC: freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
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:

> > "
> > db> panic
> > panic: from debugger
> > mp_lock = 01000002; cpuid = 1; lapic.id = 01000000
> > boot() called on cpu#1
> > syncing disks... 4 done
> 
> Get this part, but
> 
> >
> > dumping to dev 20009, offset 262144
> > dump 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65
> > [snip]
> 
> I don't get this part.  It's not doing the dump.

What do you get then?

I'm sure you've checked - but you have got a line like:

"
dumpdev="/dev/wd1s1b"           # Device name to crashdump to (if enabled).
"

In your /etc/rc.conf right? - If so, which device is it trying to dump to? -
and how big is it (vs. your RAM size)...

Sorry if you've covered this all before - the regular fixit crewe seem to have
disappeared for the night ;-) - So I'll have to do 

Regards,

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 13:42:06 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA23035
          for freebsd-current-outgoing; Sat, 17 Oct 1998 13:42:06 -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 NAA22963
          for ; Sat, 17 Oct 1998 13:41:58 -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 QAA01512;
	Sat, 17 Oct 1998 16:41:20 -0400 (EDT)
Date: Sat, 17 Oct 1998 16:41:20 -0400 (EDT)
From: Chuck Robey 
To: Karl Pielorz 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
In-Reply-To: <3628FE7F.6C5F65D7@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:

> > > dumping to dev 20009, offset 262144
> > > dump 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65
> > > [snip]
> > 
> > I don't get this part.  It's not doing the dump.
> 
> What do you get then?
> 
> I'm sure you've checked - but you have got a line like:
> 
> "
> dumpdev="/dev/wd1s1b"           # Device name to crashdump to (if enabled).
> "
> 
> In your /etc/rc.conf right? - If so, which device is it trying to dump to? -
> and how big is it (vs. your RAM size)...

I dump to da0s1b, it's 96M big.  It's got a companion da1b (not sliced)
that's the same size on the second disk.

> 
> Sorry if you've covered this all before - the regular fixit crewe seem to have
> disappeared for the night ;-) - So I'll have to do 

Appreciate the help, I don't know what I might be doing wrong.  /etc/rc
keeps on telling me the same thing I get when I go into single user with
now (now preciously hoarded) good kernel single-user and try to save the
kernel dump --- no kernel dump.  When I'm in ddb, and call panic, then
continue, it says it can't get the smp lock, doesn't do the dump at all,
and goes directly to reset.  No dump.

> 
> Regards,
> 
> Karl
> 
> 

----------------------------+-----------------------------------------------
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 17 13:58:09 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA25348
          for freebsd-current-outgoing; Sat, 17 Oct 1998 13:58:09 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from k6n1.znh.org (dialup20.gaffaneys.com [208.155.161.70])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25296
          for ; Sat, 17 Oct 1998 13:58:01 -0700 (PDT)
          (envelope-from zach@gaffaneys.com)
Received: (from zach@localhost)
	by k6n1.znh.org (8.9.1/8.9.1) id UAA05270;
	Sat, 17 Oct 1998 20:58:03 GMT
	(envelope-from zach)
Message-ID: <19981017155803.A4753@znh.org>
Date: Sat, 17 Oct 1998 15:58:03 -0500
From: Zach Heilig 
To: Chuck Robey , Karl Pielorz 
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
References: <3628FE7F.6C5F65D7@tdx.co.uk> 
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 Sat, Oct 17, 1998 at 04:41:20PM -0400
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Oct 17, 1998 at 04:41:20PM -0400, Chuck Robey wrote:
> > Sorry if you've covered this all before - the regular fixit crewe seem to have
> > disappeared for the night ;-) - So I'll have to do 
> 
> Appreciate the help, I don't know what I might be doing wrong.  /etc/rc
> keeps on telling me the same thing I get when I go into single user with
> now (now preciously hoarded) good kernel single-user and try to save the
> kernel dump --- no kernel dump.  When I'm in ddb, and call panic, then
> continue, it says it can't get the smp lock, doesn't do the dump at all,
> and goes directly to reset.  No dump.

It does make the dump, right?  If it is getting that far, you should make
sure that 'dumpon /dev/da0s1b' happens before trying to run savecore.

-- 
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 17 14:06:32 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA26264
          for freebsd-current-outgoing; Sat, 17 Oct 1998 14:06:32 -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 OAA26256
          for ; Sat, 17 Oct 1998 14:06:25 -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 RAA02187;
	Sat, 17 Oct 1998 17:05:48 -0400 (EDT)
Date: Sat, 17 Oct 1998 17:05:48 -0400 (EDT)
From: Chuck Robey 
To: Zach Heilig 
cc: Karl Pielorz , freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
In-Reply-To: <19981017155803.A4753@znh.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 Sat, 17 Oct 1998, Zach Heilig wrote:

> On Sat, Oct 17, 1998 at 04:41:20PM -0400, Chuck Robey wrote:
> > > Sorry if you've covered this all before - the regular fixit crewe seem to have
> > > disappeared for the night ;-) - So I'll have to do 
> > 
> > Appreciate the help, I don't know what I might be doing wrong.  /etc/rc
> > keeps on telling me the same thing I get when I go into single user with
> > now (now preciously hoarded) good kernel single-user and try to save the
> > kernel dump --- no kernel dump.  When I'm in ddb, and call panic, then
> > continue, it says it can't get the smp lock, doesn't do the dump at all,
                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^

> > and goes directly to reset.  No dump.
> 
> It does make the dump, right?

No, it doesn't make the dump, that's the whole point.

> If it is getting that far,

It ISN'T getting that far.

> you should make
> sure that 'dumpon /dev/da0s1b' happens before trying to run savecore.

There's nothing in the swap partition for savecore to act on.  No dump
being made.  Why not?

----------------------------+-----------------------------------------------
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 17 14:19:39 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA27684
          for freebsd-current-outgoing; Sat, 17 Oct 1998 14:19:39 -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 OAA27679
          for ; Sat, 17 Oct 1998 14:19:36 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id WAA00706;
	Sat, 17 Oct 1998 22:19:09 +0100 (BST)
Message-ID: <3629098B.14313D94@tdx.co.uk>
Date: Sat, 17 Oct 1998 22:18:03 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Chuck Robey 
CC: freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
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:

> Appreciate the help, I don't know what I might be doing wrong.  /etc/rc
> keeps on telling me the same thing I get when I go into single user with
> now (now preciously hoarded) good kernel single-user and try to save the
> kernel dump --- no kernel dump.  When I'm in ddb, and call panic, then
> continue, it says it can't get the smp lock, doesn't do the dump at all,
> and goes directly to reset.  No dump.

"Can't get the SMP lock?" - Are you running an SMP system? You say da0s1b is
96Mb, how much RAM do you have in the machine?

If you can get the exact text it comes up with at panic time, in response to
you issuing 'panic' to DDB it might shed some light on things...

Regards,

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 14:26:07 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA28647
          for freebsd-current-outgoing; Sat, 17 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 OAA28542
          for ; Sat, 17 Oct 1998 14:26:00 -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 RAA02226;
	Sat, 17 Oct 1998 17:25:21 -0400 (EDT)
Date: Sat, 17 Oct 1998 17:25:21 -0400 (EDT)
From: Chuck Robey 
To: Karl Pielorz 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
In-Reply-To: <3629098B.14313D94@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:

> 
> 
> Chuck Robey wrote:
> 
> > Appreciate the help, I don't know what I might be doing wrong.  /etc/rc
> > keeps on telling me the same thing I get when I go into single user with
> > now (now preciously hoarded) good kernel single-user and try to save the
> > kernel dump --- no kernel dump.  When I'm in ddb, and call panic, then
> > continue, it says it can't get the smp lock, doesn't do the dump at all,
> > and goes directly to reset.  No dump.
> 
> "Can't get the SMP lock?" - Are you running an SMP system? You say da0s1b is
> 96Mb, how much RAM do you have in the machine?

I have 192M of swap, in two 96M partitions.  I have 64M of memory.  That
ought to be hoards and hoards more than I need.

> If you can get the exact text it comes up with at panic time, in response to
> you issuing 'panic' to DDB it might shed some light on things...

I posted separately about what I found with the panic problem, at least
as much as I could without being able to get the dump.  It's not all
that useful, without all the context from teh dump itself.  I wanted
this to concentrate on getting me the dump, not analysis of something I
can't get yet.  I'm greedily waiting on advice on how to force the dump.


----------------------------+-----------------------------------------------
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 17 14:39:45 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA29858
          for freebsd-current-outgoing; Sat, 17 Oct 1998 14:39:45 -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 OAA29849
          for ; Sat, 17 Oct 1998 14:39:41 -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 RAA09295
	for ; Sat, 17 Oct 1998 17:41:04 -0400 (EDT)
	(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Sat, 17 Oct 1998 17:41:04 -0400 (EDT)
From: Alfred Perlstein 
X-Sender: bright@porkfriedrice.ny.genx.net
To: current@FreeBSD.ORG
Subject: about those crash dumps
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 sure everyone kinda rembers my crashdump problem that i had, well i
was wondering what the turnout of that was.

Has anything happened to the way FreeBSD handles drives detected as LBA?

I modified my flags for my harddrive and was wondering if it'd smash a
parition or not if I tried to take a crashdump.

thank you,
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  Sat Oct 17 14:41:05 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA00208
          for freebsd-current-outgoing; Sat, 17 Oct 1998 14:41:05 -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 OAA00199
          for ; Sat, 17 Oct 1998 14:41:01 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id WAA00770;
	Sat, 17 Oct 1998 22:40:37 +0100 (BST)
Message-ID: <36290E93.139108FE@tdx.co.uk>
Date: Sat, 17 Oct 1998 22:39:31 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Chuck Robey 
CC: freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel
X-Priority: 2 (High)
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 192M of swap, in two 96M partitions.  I have 64M of memory.  That
> ought to be hoards and hoards more than I need.

Yes, that's fine - I thought you might have had 96Mb of RAM :-)
 
> > If you can get the exact text it comes up with at panic time, in response to
> > you issuing 'panic' to DDB it might shed some light on things...
> 
> I posted separately about what I found with the panic problem, at least
> as much as I could without being able to get the dump.  It's not all
> that useful, without all the context from teh dump itself.  I wanted
> this to concentrate on getting me the dump, not analysis of something I
> can't get yet.  I'm greedily waiting on advice on how to force the dump.

Yes, I can see that :-) ... What I'd be interested in is the text that appears
after you give DDB the 'panic' command, i.e. not the details of the panic that
bought you into DDB, but what happens between you telling DDB to dump (by
entering 'panic') and the system rebooting...

Ahh... I've just seen something I should have seen before...

"When the crash occurs, right after starting the smp stuff, and drops to
ddb, what's the command to get it to dump the crash dump?  Is it just
there automatically, and do I just type "panic" to get ddb to exit and
dump the core?"

OK - sounds like the system is panic'ing too early to get a crashdump...
Afterall, if the system hasn't read /etc/rc.conf - how's it know where to
dump? :)

All is becoming clearer...

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!

If your building a new kernel, remember to keep your 'working' kernel safe on
the system (by copying it to '/kernel.works' or something - so you can still
boot in the future).

Give the above ago - and let me know what happens...

Sorry for the 'long way round' - I didn't read all the background mails :-(

Regards,

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 16:03:45 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA06031
          for freebsd-current-outgoing; Sat, 17 Oct 1998 16:03:45 -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 QAA06026
          for ; Sat, 17 Oct 1998 16:03:43 -0700 (PDT)
          (envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.29] by silverback.gorilla.net with ESMTP
  (SMTPD32-4.07) id A12D5E0152; Sat, 17 Oct 1998 17:58:53 CDT
Received: (from tom@localhost)
	by peeper.TOJ.org (8.9.1/8.8.8) id SAA21943;
	Sat, 17 Oct 1998 18:03:27 -0500 (CDT)
	(envelope-from tom)
Message-ID: <19981017180257.A21925@TOJ.org>
Date: Sat, 17 Oct 1998 18:02:57 -0500
From: Tom Jackson 
To: Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: panic
References: 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: ; from Chuck Robey on Sat, Oct 17, 1998 at 03:50:02PM -0400
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Oct 17, 1998 at 03:50:02PM -0400, Chuck Robey wrote:
> I'm now getting a panic on startup, SMP kernel, on a config file that
> was working fine a few days ago.  The panic is coming in module_register
> + 14.  I'd give you the stack dump, but I can't seem to get a kernel
> dump captured yet.

I'm getting this crash, not on elf(kernel+exec)/smp/scsi but on a old
Thinkpad with a pccard ed0, a elf(kernel+exec)/up/ide. Thought since the
reference to modules that pcvt instead of sc0 might work - no such luck.
I get the panic right after the pcic is probed and before the pccard is
initialized.

>From the instruction pointer, nm /kernel | sort gives module_init.

> 
> I checked, all my LKMs are brand new.  This is a fresh build for both
> the world and the kernel from equal sources (no intervening cvsup or cvs
> actions), with all new LKMs.  Normal ELF system you'd expect.
> 
> Panic is supervisor read, page not present.  Can't tell what module it
> was trying to load without the kernel dump (I think).  Panic message
> says it's in the swapper process, but I think that's not germane here
> (is it?).  I have a fault virtual address of 8be58955, I'm not sure
> that's useful, seeing as I can't translate that to a module address.
> 
> How do I force a kernel dump?
I'm not getting any crash dumps on any of my elf systems.
> 
> ----------------------------+-----------------------------------------------
> 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
> 

-- 
Tom

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 16:17:45 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA06876
          for freebsd-current-outgoing; Sat, 17 Oct 1998 16:17:45 -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 QAA06844
          for ; Sat, 17 Oct 1998 16:17:04 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id AAA00947;
	Sun, 18 Oct 1998 00:16:28 +0100 (BST)
Message-ID: <3629250A.42D9A28D@tdx.co.uk>
Date: Sun, 18 Oct 1998 00:15:22 +0100
From: Karl Pielorz 
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom Jackson 
CC: Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: panic
References:  <19981017180257.A21925@TOJ.org>
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:

> [snip]
> 
> I'm getting this crash, not on elf(kernel+exec)/smp/scsi but on a old
> Thinkpad with a pccard ed0, a elf(kernel+exec)/up/ide. Thought since the
> reference to modules that pcvt instead of sc0 might work - no such luck.
> I get the panic right after the pcic is probed and before the pccard is
> initialized.
> 
> I'm not getting any crash dumps on any of my elf systems.

Hi,

I've been talking to Chuck about this - if the panic is similar / the same as
his, you won't get a crashdump - as it's happening too soon into the boot
process...

The only thing I could think of was to have a line similar to:

config          kernel  root on XXX dumps on YYYY

In the kernel config - Though LINT warns against this, it might be the only
way of telling the system where to dump to - as it's panics so soon during
boot...

I'm hoping someone who knows more what there talking about will step in with
"That's a good/bad idea" - and why...

I seem to remember using the kernel config to specify the dump device, but
that was from ages ago (2.2.2? :-)

Regards,

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 17:23:53 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA11268
          for freebsd-current-outgoing; Sat, 17 Oct 1998 17:23:53 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from redfish.go2net.com (redfish.go2net.com [207.178.55.5])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA11263
          for ; Sat, 17 Oct 1998 17:23:52 -0700 (PDT)
          (envelope-from marcs@go2net.com)
Received: from marcs by redfish.go2net.com with smtp (Exim 1.82 #2)
	id 0zUgc4-0000D3-00; Sat, 17 Oct 1998 17:22:24 -0700
Date: Sat, 17 Oct 1998 17:22:24 -0700 (PDT)
From: Marc Slemko 
X-Sender: marcs@redfish
To: current@FreeBSD.ORG, "Jordan K. Hubbard" 
Subject: sleep() and Apache in release notes
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

(don't know who wrote what part of the release notes, but...)

It is somewhat disappointing to see:

o sleep(3) and usleep(3) are now implemented in terms of signanosleep(2)
  and now have correct SIGALRM interaction semantics and sleep(3) correctly
  returns the time remaining.  Some programs (notably apache httpd) bogusly
  depend on a sleep() "absorbing" a SIGALRM from a timer that expires during
  the life of the sleep.

in RELNOTES.TXT considering I have no idea where the bug in Apache that is
claiming would be and there have been no bug report or attempt to get this
fixed in Apache other than sticking lines in the release notes saying
"Apache is broken".

If there is a problem in Apache, please point it out so it can be fixed.  

-- 
     Marc Slemko     | Apache Group member
     marcs@znep.com  | marc@apache.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 17 17:58:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA12820
          for freebsd-current-outgoing; Sat, 17 Oct 1998 17:58:35 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12815
          for ; Sat, 17 Oct 1998 17:58: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 SAA08498;
	Sat, 17 Oct 1998 18:02:37 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810180102.SAA08498@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Tom Jackson 
cc: Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-reply-to: Your message of "Sat, 17 Oct 1998 18:02:57 CDT."
             <19981017180257.A21925@TOJ.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 17 Oct 1998 18:02:36 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Sat, Oct 17, 1998 at 03:50:02PM -0400, Chuck Robey wrote:
> > I'm now getting a panic on startup, SMP kernel, on a config file that
> > was working fine a few days ago.  The panic is coming in module_register
> > + 14.  I'd give you the stack dump, but I can't seem to get a kernel
> > dump captured yet.
> 
> I'm getting this crash, not on elf(kernel+exec)/smp/scsi but on a old
> Thinkpad with a pccard ed0, a elf(kernel+exec)/up/ide. Thought since the
> reference to modules that pcvt instead of sc0 might work - no such luck.
> I get the panic right after the pcic is probed and before the pccard is
> initialized.

You probably need to update /boot/loader, as the module metadata layout 
changed.

-- 
\\  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 17 18:15:50 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA13877
          for freebsd-current-outgoing; Sat, 17 Oct 1998 18:15:50 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13861
          for ; Sat, 17 Oct 1998 18:15:46 -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 SAA08612;
	Sat, 17 Oct 1998 18:19:38 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810180119.SAA08612@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Karl Pielorz 
cc: Mike Smith , current@FreeBSD.ORG
Subject: Re: Serial Console - broken? (src as of 10/16 @ 16:43) 
In-reply-to: Your message of "Sat, 17 Oct 1998 20:42:20 BST."
             <3628F31C.29EE2587@tdx.co.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 17 Oct 1998 18:19:37 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> 
> Mike Smith wrote:
> 
> > Um, try checking the flags on your serial console.  You should have 0x10
> > or 0x30, but 0x50 or 0x70 would be bad.  (ie. you don't want 0x40 set).
> > 
> > Apart from that, there's the hideous fear that something leaked in and
> > GDB is the default debugger.  Ick.
> 
> Hmmm... Serial console is definitely set to:
> 
> device          sio0    at isa? port "IO_COM1" flags 0x30 tty irq 4 vector
> siointr
> 
> I presume 'Ick' is bad, but how bad? - i.e. easily fixable?

You're going to have to work out why it's dropping into gdb mode rather 
than ddb mode; check the value of 'boothowto' inside the kernel.  

What happens if you break to the debugger manually?

-- 
\\  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 17 18:23:50 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA14399
          for freebsd-current-outgoing; Sat, 17 Oct 1998 18:23:50 -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 SAA14394
          for ; Sat, 17 Oct 1998 18:23:47 -0700 (PDT)
          (envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.106] by silverback.gorilla.net with ESMTP
  (SMTPD32-4.07) id A202D600D8; Sat, 17 Oct 1998 20:18:58 CDT
Received: (from tom@localhost)
	by peeper.TOJ.org (8.9.1/8.8.8) id UAA12171;
	Sat, 17 Oct 1998 20:23:35 -0500 (CDT)
	(envelope-from tom)
Message-ID: <19981017202305.A12163@TOJ.org>
Date: Sat, 17 Oct 1998 20:23:05 -0500
From: Tom Jackson 
To: Karl Pielorz , Tom Jackson 
Cc: Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: panic
References:  <19981017180257.A21925@TOJ.org> <3629250A.42D9A28D@tdx.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <3629250A.42D9A28D@tdx.co.uk>; from Karl Pielorz on Sun, Oct 18, 1998 at 12:15:22AM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

nm tells me module_register (dugh) not module_init.

For me, no amount of dumps on anything will produce a crash dump. On my
laptop it just says bad dump device and on my server (which is not crashing
now) I get a count down but no crash modules are produced.

btw, these are 100% elf and I don't think the panic is a smp problem.

Maybe Peter will know what the problem is.

On Sun, Oct 18, 1998 at 12:15:22AM +0100, Karl Pielorz wrote:
> 
> Tom Jackson wrote:
> 
> > [snip]
> > 
> > I'm getting this crash, not on elf(kernel+exec)/smp/scsi but on a old
> > Thinkpad with a pccard ed0, a elf(kernel+exec)/up/ide. Thought since the
> > reference to modules that pcvt instead of sc0 might work - no such luck.
> > I get the panic right after the pcic is probed and before the pccard is
> > initialized.
> > 
> > I'm not getting any crash dumps on any of my elf systems.
> 
> Hi,
> 
> I've been talking to Chuck about this - if the panic is similar / the same as
> his, you won't get a crashdump - as it's happening too soon into the boot
> process...
> 
> The only thing I could think of was to have a line similar to:
> 
> config          kernel  root on XXX dumps on YYYY
> 
> In the kernel config - Though LINT warns against this, it might be the only
> way of telling the system where to dump to - as it's panics so soon during
> boot...
> 
> I'm hoping someone who knows more what there talking about will step in with
> "That's a good/bad idea" - and why...
> 
> I seem to remember using the kernel config to specify the dump device, but
> that was from ages ago (2.2.2? :-)
> 
> Regards,
> 
> Karl
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
Tom

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 18:26:38 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA14706
          for freebsd-current-outgoing; Sat, 17 Oct 1998 18:26:38 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.insolwwb.net (ns.insolwwb.net [206.31.149.200])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14527
          for ; Sat, 17 Oct 1998 18:24:40 -0700 (PDT)
          (envelope-from mgrommet@ns.insolwwb.net)
Received: (from mgrommet@localhost)
	by ns.insolwwb.net (8.8.8/8.8.5) id UAA17901;
	Sat, 17 Oct 1998 20:14:01 -0500 (CDT)
Date: Sat, 17 Oct 1998 20:14:00 -0500 (CDT)
From: mike grommet 
To: Simon Shapiro 
cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG,
        mike@smith.net.au, Bruce Evans 
Subject: Re: Show Stopper? Failure to Install 19981014
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

> 
> c.  The release we built on the 4th of October displays the messages but
>     does not fail to install.  The release of the 13th displays the same
>     messages but fails to install.
> 
> Maybe there is sme help in these notes...
> 

Well, it happened (the cross link error and failed install) to me on the Oct 
4th version... thats when I first attempted to install 3.0...

just to clarify that it (the bug) did exist and was fatal (if to no one 
else but me) on the 4th...

So, anyone know if that fix mentioned a few messages ago actually
did the trick?



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 18:27:20 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA14742
          for freebsd-current-outgoing; Sat, 17 Oct 1998 18:27:20 -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 SAA14737
          for ; Sat, 17 Oct 1998 18:27:17 -0700 (PDT)
          (envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.105] by silverback.gorilla.net with ESMTP
  (SMTPD32-4.07) id A2DAE200D8; Sat, 17 Oct 1998 20:22:34 CDT
Received: (from tom@localhost)
	by peeper.TOJ.org (8.9.1/8.8.8) id UAA12180;
	Sat, 17 Oct 1998 20:27:11 -0500 (CDT)
	(envelope-from tom)
Message-ID: <19981017202305.A12163@TOJ.org>
Date: Sat, 17 Oct 1998 20:26:40 -0500
From: Tom Jackson 
To: Karl Pielorz , Tom Jackson 
Cc: Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: panic
References:  <19981017180257.A21925@TOJ.org> <3629250A.42D9A28D@tdx.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <3629250A.42D9A28D@tdx.co.uk>; from Karl Pielorz on Sun, Oct 18, 1998 at 12:15:22AM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

nm tells me module_register (dugh) not module_init.

For me, no amount of dumps on anything will produce a crash dump. On my
laptop it just says bad dump device and on my server (which is not crashing
now) I get a count down but no crash modules are produced.

btw, these are 100% elf and I don't think the panic is a smp problem.

Maybe Peter will know what the problem is.

On Sun, Oct 18, 1998 at 12:15:22AM +0100, Karl Pielorz wrote:
> 
> Tom Jackson wrote:
> 
> > [snip]
> > 
> > I'm getting this crash, not on elf(kernel+exec)/smp/scsi but on a old
> > Thinkpad with a pccard ed0, a elf(kernel+exec)/up/ide. Thought since the
> > reference to modules that pcvt instead of sc0 might work - no such luck.
> > I get the panic right after the pcic is probed and before the pccard is
> > initialized.
> > 
> > I'm not getting any crash dumps on any of my elf systems.
> 
> Hi,
> 
> I've been talking to Chuck about this - if the panic is similar / the same as
> his, you won't get a crashdump - as it's happening too soon into the boot
> process...
> 
> The only thing I could think of was to have a line similar to:
> 
> config          kernel  root on XXX dumps on YYYY
> 
> In the kernel config - Though LINT warns against this, it might be the only
> way of telling the system where to dump to - as it's panics so soon during
> boot...
> 
> I'm hoping someone who knows more what there talking about will step in with
> "That's a good/bad idea" - and why...
> 
> I seem to remember using the kernel config to specify the dump device, but
> that was from ages ago (2.2.2? :-)
> 
> Regards,
> 
> Karl
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
Tom

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 18:27:37 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA14772
          for freebsd-current-outgoing; Sat, 17 Oct 1998 18:27:37 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14757
          for ; Sat, 17 Oct 1998 18:27: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 SAA08718;
	Sat, 17 Oct 1998 18:31:47 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810180131.SAA08718@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Tom Jackson 
cc: Karl Pielorz , Chuck Robey ,
        freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-reply-to: Your message of "Sat, 17 Oct 1998 20:23:05 CDT."
             <19981017202305.A12163@TOJ.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 17 Oct 1998 18:31:47 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> nm tells me module_register (dugh) not module_init.
> 
> For me, no amount of dumps on anything will produce a crash dump. On my
> laptop it just says bad dump device and on my server (which is not crashing
> now) I get a count down but no crash modules are produced.

You can't write a dump to disk until you've found a disk to write to.  
Module_register is way too early.  

> btw, these are 100% elf and I don't think the panic is a smp problem.

If you're running an ELF kernel, make sure your /boot/loader is up to 
date.

-- 
\\  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 17 18:29:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA15090
          for freebsd-current-outgoing; Sat, 17 Oct 1998 18:29:59 -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 SAA15084
          for ; Sat, 17 Oct 1998 18:29:56 -0700 (PDT)
          (envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.105] by silverback.gorilla.net with ESMTP
  (SMTPD32-4.07) id A377E900D8; Sat, 17 Oct 1998 20:25:11 CDT
Received: (from tom@localhost)
	by peeper.TOJ.org (8.9.1/8.8.8) id UAA12189;
	Sat, 17 Oct 1998 20:29:48 -0500 (CDT)
	(envelope-from tom)
Message-ID: <19981017202305.A12163@TOJ.org>
Date: Sat, 17 Oct 1998 20:29:48 -0500
From: Tom Jackson 
To: Karl Pielorz , Tom Jackson 
Cc: Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: panic
References:  <19981017180257.A21925@TOJ.org> <3629250A.42D9A28D@tdx.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <3629250A.42D9A28D@tdx.co.uk>; from Karl Pielorz on Sun, Oct 18, 1998 at 12:15:22AM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

nm tells me module_register (dugh) not module_init.

For me, no amount of dumps on anything will produce a crash dump. On my
laptop it just says bad dump device and on my server (which is not crashing
now) I get a count down but no crash modules are produced.

btw, these are 100% elf and I don't think the panic is a smp problem.

Maybe Peter will know what the problem is.

On Sun, Oct 18, 1998 at 12:15:22AM +0100, Karl Pielorz wrote:
> 
> Tom Jackson wrote:
> 
> > [snip]
> > 
> > I'm getting this crash, not on elf(kernel+exec)/smp/scsi but on a old
> > Thinkpad with a pccard ed0, a elf(kernel+exec)/up/ide. Thought since the
> > reference to modules that pcvt instead of sc0 might work - no such luck.
> > I get the panic right after the pcic is probed and before the pccard is
> > initialized.
> > 
> > I'm not getting any crash dumps on any of my elf systems.
> 
> Hi,
> 
> I've been talking to Chuck about this - if the panic is similar / the same as
> his, you won't get a crashdump - as it's happening too soon into the boot
> process...
> 
> The only thing I could think of was to have a line similar to:
> 
> config          kernel  root on XXX dumps on YYYY
> 
> In the kernel config - Though LINT warns against this, it might be the only
> way of telling the system where to dump to - as it's panics so soon during
> boot...
> 
> I'm hoping someone who knows more what there talking about will step in with
> "That's a good/bad idea" - and why...
> 
> I seem to remember using the kernel config to specify the dump device, but
> that was from ages ago (2.2.2? :-)
> 
> Regards,
> 
> Karl
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
Tom

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 18:30:50 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA15278
          for freebsd-current-outgoing; Sat, 17 Oct 1998 18:30:50 -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 SAA15257
          for ; Sat, 17 Oct 1998 18:30:47 -0700 (PDT)
          (envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.105] by silverback.gorilla.net with ESMTP
  (SMTPD32-4.07) id A3AC6D00C0; Sat, 17 Oct 1998 20:26:04 CDT
Received: (from tom@localhost)
	by peeper.TOJ.org (8.9.1/8.8.8) id UAA12198;
	Sat, 17 Oct 1998 20:30:41 -0500 (CDT)
	(envelope-from tom)
Message-ID: <19981017202305.A12163@TOJ.org>
Date: Sat, 17 Oct 1998 20:30:41 -0500
From: Tom Jackson 
To: Karl Pielorz 
Cc: Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: panic
References:  <19981017180257.A21925@TOJ.org> <3629250A.42D9A28D@tdx.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <3629250A.42D9A28D@tdx.co.uk>; from Karl Pielorz on Sun, Oct 18, 1998 at 12:15:22AM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

nm tells me module_register (dugh) not module_init.

For me, no amount of dumps on anything will produce a crash dump. On my
laptop it just says bad dump device and on my server (which is not crashing
now) I get a count down but no crash modules are produced.

btw, these are 100% elf and I don't think the panic is a smp problem.

Maybe Peter will know what the problem is.

On Sun, Oct 18, 1998 at 12:15:22AM +0100, Karl Pielorz wrote:
> 
> Tom Jackson wrote:
> 
> > [snip]
> > 
> > I'm getting this crash, not on elf(kernel+exec)/smp/scsi but on a old
> > Thinkpad with a pccard ed0, a elf(kernel+exec)/up/ide. Thought since the
> > reference to modules that pcvt instead of sc0 might work - no such luck.
> > I get the panic right after the pcic is probed and before the pccard is
> > initialized.
> > 
> > I'm not getting any crash dumps on any of my elf systems.
> 
> Hi,
> 
> I've been talking to Chuck about this - if the panic is similar / the same as
> his, you won't get a crashdump - as it's happening too soon into the boot
> process...
> 
> The only thing I could think of was to have a line similar to:
> 
> config          kernel  root on XXX dumps on YYYY
> 
> In the kernel config - Though LINT warns against this, it might be the only
> way of telling the system where to dump to - as it's panics so soon during
> boot...
> 
> I'm hoping someone who knows more what there talking about will step in with
> "That's a good/bad idea" - and why...
> 
> I seem to remember using the kernel config to specify the dump device, but
> that was from ages ago (2.2.2? :-)
> 
> Regards,
> 
> Karl
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
Tom

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 18:43:01 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA16470
          for freebsd-current-outgoing; Sat, 17 Oct 1998 18:43:01 -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 SAA16462
          for ; Sat, 17 Oct 1998 18:42:59 -0700 (PDT)
          (envelope-from ulf@Gatekeeper.Alameda.net)
Received:  by Gatekeeper.Alameda.net (8.8.8/8.8.6) id SAA28227;
	Sat, 17 Oct 1998 18:42:39 -0700 (PDT)
Message-ID: <19981017184238.A26929@Alameda.net>
Date: Sat, 17 Oct 1998 18:42:38 -0700
From: Ulf Zimmermann 
To: current@FreeBSD.ORG
Subject: newfs problems, more information:
Reply-To: ulf@Alameda.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
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 have a machine with BETA from 0930 installed:

FreeBSD PacHell.TelcoSucks.org 3.0-19980930-BETA FreeBSD 3.0-19980930-BETA #2: Sun Oct  4 05:12:58 PDT 1998     root@PacHell.TelcoSucks.org:/usr/src/sys/compile/PACHELL  i386

The system has several disks, two of them are configured like this:

PacHell root / # fdisk da2
******* Working on device /dev/rda2 *******
parameters extracted from in-core disklabel are:
cylinders=1109 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1109 heads=255 sectors/track=63 (16065 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:
sysid 165,(FreeBSD/NetBSD/386BSD)
    start 1, size 17816084 (8699 Meg), flag 80 (active)
        beg: cyl 0/ sector 2/ head 0;
        end: cyl 1023/ sector 63/ head 254

PacHell root / # fdisk da3
******* Working on device /dev/rda3 *******
parameters extracted from in-core disklabel are:
cylinders=1109 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1109 heads=255 sectors/track=63 (16065 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:
sysid 165,(FreeBSD/NetBSD/386BSD)
    start 1, size 17816084 (8699 Meg), flag 80 (active)
        beg: cyl 0/ sector 2/ head 0;
        end: cyl 1023/ sector 63/ head 254

PacHell root / # disklabel da2
# /dev/rda2c:
type: SCSI
disk: da2s4
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 1108
sectors/unit: 17816084
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  c: 17816084        0    unused        0     0         # (Cyl.    0 - 1108*)
  e: 17816084        0    4.2BSD     1024  8192    16   # (Cyl.    0 - 1108*)


PacHell root / # disklabel da3
# /dev/rda3c:
type: SCSI
disk: da3s4
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 1108
sectors/unit: 17816084
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  c: 17816084        0    unused        0     0         # (Cyl.    0 - 1108*)
  e: 17816084        0    4.2BSD     1024  8192    16   # (Cyl.    0 - 1108*)

Then these two disks are configured as ccd0:

PacHell root / # cat /etc/ccd.conf 
ccd0    16      none    /dev/da2s4e /dev/da3s4e

Doing a newfs on it:

PacHell root / # newfs /dev/ccd0c
newfs: /dev/ccd0c: not a character-special device
Warning: 3072 sector(s) in last cylinder unallocated
/dev/ccd0c:     35632128 sectors in 8700 cylinders of 1 tracks, 4096 sectors
        17398.5MB in 544 cyl groups (16 c/g, 32.00MB/g, 7936 i/g)
super-block backups (for fsck -b #) at:
 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856,
....
 35389472, 35455008, 35520544, 35586080,
newfs: ioctl (WDINFO): No such process
newfs: /dev/ccd0c: can't rewrite disk label

PacHell root / # strings /sbin/newfs | grep newfs.c
$Id: newfs.c,v 1.25 1998/09/30 07:53:52 grog Exp $

-- 
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 17 18:58:06 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA17939
          for freebsd-current-outgoing; Sat, 17 Oct 1998 18:58:06 -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 SAA17893
          for ; Sat, 17 Oct 1998 18:58:00 -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 SAA24754;
	Sat, 17 Oct 1998 18:58:01 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Marc Slemko 
cc: current@FreeBSD.ORG
Subject: Re: sleep() and Apache in release notes 
In-reply-to: Your message of "Sat, 17 Oct 1998 17:22:24 PDT."
              
Date: Sat, 17 Oct 1998 18:58:01 -0700
Message-ID: <24750.908675881@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> (don't know who wrote what part of the release notes, but...)

I'm not really sure who wrote that (possibly Garrett, but I wouldn't
swear on it) but I'm sorry for the unfortunate choice of words.  I
should have proof-read the release notes more carefully - mea culpa!

I don't think that any intentional slight was meant by it, just an
off-the-cuff comment in engineer-speak that problably shouldn't have
gone into the public docs.  Once we figure out who added it (I'm on a
slow link at the moment or I'd inspect the CVS logs), we can determine
just what was meant by it.

- Jordan

> 
> It is somewhat disappointing to see:
> 
> o sleep(3) and usleep(3) are now implemented in terms of signanosleep(2)
>   and now have correct SIGALRM interaction semantics and sleep(3) correctly
>   returns the time remaining.  Some programs (notably apache httpd) bogusly
>   depend on a sleep() "absorbing" a SIGALRM from a timer that expires during
>   the life of the sleep.
> 
> in RELNOTES.TXT considering I have no idea where the bug in Apache that is
> claiming would be and there have been no bug report or attempt to get this
> fixed in Apache other than sticking lines in the release notes saying
> "Apache is broken".
> 
> If there is a problem in Apache, please point it out so it can be fixed.  
> 
> -- 
>      Marc Slemko     | Apache Group member
>      marcs@znep.com  | marc@apache.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  Sat Oct 17 18:58:43 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA18025
          for freebsd-current-outgoing; Sat, 17 Oct 1998 18:58:43 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18017
          for ; Sat, 17 Oct 1998 18:58:41 -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 TAA08917;
	Sat, 17 Oct 1998 19:03:04 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810180203.TAA08917@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: ulf@Alameda.net
cc: current@FreeBSD.ORG
Subject: Re: newfs problems, more information: 
In-reply-to: Your message of "Sat, 17 Oct 1998 18:42:38 PDT."
             <19981017184238.A26929@Alameda.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 17 Oct 1998 19:03:04 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> 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.

> Warning: 3072 sector(s) in last cylinder unallocated
> /dev/ccd0c:     35632128 sectors in 8700 cylinders of 1 tracks, 4096 sectors
>         17398.5MB in 544 cyl groups (16 c/g, 32.00MB/g, 7936 i/g)
> super-block backups (for fsck -b #) at:
>  32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856,
> ....
>  35389472, 35455008, 35520544, 35586080,
> newfs: ioctl (WDINFO): No such process
> newfs: /dev/ccd0c: can't rewrite disk label

Update.  You might get a better error message, but I think you'll find 
the problem 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 17 19:08:03 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA19645
          for freebsd-current-outgoing; Sat, 17 Oct 1998 19:08:03 -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 TAA19599
          for ; Sat, 17 Oct 1998 19:07:58 -0700 (PDT)
          (envelope-from ulf@Gatekeeper.Alameda.net)
Received:  by Gatekeeper.Alameda.net (8.8.8/8.8.6) id TAA29253;
	Sat, 17 Oct 1998 19:07:01 -0700 (PDT)
Message-ID: <19981017190701.B26929@Alameda.net>
Date: Sat, 17 Oct 1998 19:07:01 -0700
From: Ulf Zimmermann 
To: Mike Smith 
Cc: current@FreeBSD.ORG
Subject: Re: newfs problems, more information:
Reply-To: ulf@Alameda.net
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.91.1i
In-Reply-To: <199810180203.TAA08917@dingo.cdrom.com>; from Mike Smith on Sat, Oct 17, 1998 at 07:03:04PM -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

Forgot to say, that I was going to upgrade after this email.
As soon I have 3.0-R mirrored.

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.
> 
> > Warning: 3072 sector(s) in last cylinder unallocated
> > /dev/ccd0c:     35632128 sectors in 8700 cylinders of 1 tracks, 4096 sectors
> >         17398.5MB in 544 cyl groups (16 c/g, 32.00MB/g, 7936 i/g)
> > super-block backups (for fsck -b #) at:
> >  32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856,
> > ....
> >  35389472, 35455008, 35520544, 35586080,
> > newfs: ioctl (WDINFO): No such process
> > newfs: /dev/ccd0c: can't rewrite disk label
> 
> Update.  You might get a better error message, but I think you'll find 
> the problem 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
> 

-- 
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 17 19:12:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA20008
          for freebsd-current-outgoing; Sat, 17 Oct 1998 19:12:59 -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 TAA20002
          for ; Sat, 17 Oct 1998 19:12:54 -0700 (PDT)
          (envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.9] by silverback.gorilla.net with ESMTP
  (SMTPD32-4.07) id AD89BE007A; Sat, 17 Oct 1998 21:08:09 CDT
Received: (from tom@localhost)
	by peeper.TOJ.org (8.9.1/8.8.8) id VAA12680;
	Sat, 17 Oct 1998 21:12:47 -0500 (CDT)
	(envelope-from tom)
Message-ID: <19981017211217.A12670@TOJ.org>
Date: Sat, 17 Oct 1998 21:12:17 -0500
From: Tom Jackson 
To: Mike Smith 
Cc: Karl Pielorz , Chuck Robey ,
        freebsd-current@FreeBSD.ORG
Subject: Re: panic
References: <19981017202305.A12163@TOJ.org> <199810180131.SAA08718@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199810180131.SAA08718@dingo.cdrom.com>; from Mike Smith on Sat, Oct 17, 1998 at 06:31:47PM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Oct 17, 1998 at 06:31:47PM -0700, Mike Smith wrote:
> > nm tells me module_register (dugh) not module_init.
> > 
> > For me, no amount of dumps on anything will produce a crash dump. On my
> > laptop it just says bad dump device and on my server (which is not crashing
> > now) I get a count down but no crash modules are produced.
> 
> You can't write a dump to disk until you've found a disk to write to.  
> Module_register is way too early.  
> 
> > btw, these are 100% elf and I don't think the panic is a smp problem.
> 
> If you're running an ELF kernel, make sure your /boot/loader is up to 
> date.
> 

There are up to date, in fact my observation is that they are routinely
updated in 'make world', at least mine are. This seems to be involved 
with massive changes made by Peter Wemm on 10/15 involving kern_module.c
and friends.
-- 
Tom

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 19:13:56 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA20121
          for freebsd-current-outgoing; Sat, 17 Oct 1998 19:13:56 -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 TAA20115
          for ; Sat, 17 Oct 1998 19:13:54 -0700 (PDT)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id TAA08914;
	Sat, 17 Oct 1998 19:04:09 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpdhx8899; Sun Oct 18 02:04:00 1998
Date: Sat, 17 Oct 1998 19:03:57 -0700 (PDT)
From: Julian Elischer 
To: "Kent S. Gordon" 
cc: current@FreeBSD.ORG
Subject: Re: FreeBSD 3.0-RELEASE calcru: negative time 
In-Reply-To: <199810171735.MAA10305@soccer.ksg.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

This is a long standing problem
I see it on quite a few machines.
There may be a relationship with power management, but not always.


On Sat, 17 Oct 1998, Kent S. Gordon wrote:

> I just installed FreeBSD 3.0-RELEASE.  I am getting a lot of messages
> about calcru: negitive time for ftp processes.  This has happened both
> with inbound and outbound ftp. I also had the problem with rcp.
> Remote cvs is working find.  Any suggestions?
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 19:21:26 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA21190
          for freebsd-current-outgoing; Sat, 17 Oct 1998 19:21:26 -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 TAA21167
          for ; Sat, 17 Oct 1998 19:21: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 KAA12204;
	Sun, 18 Oct 1998 10:20:16 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810180220.KAA12204@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" 
cc: Marc Slemko , current@FreeBSD.ORG
Subject: Re: sleep() and Apache in release notes 
In-reply-to: Your message of "Sat, 17 Oct 1998 18:58:01 MST."
             <24750.908675881@time.cdrom.com> 
Date: Sun, 18 Oct 1998 10:20:14 +0800
From: Peter Wemm 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Jordan K. Hubbard" wrote:
> > (don't know who wrote what part of the release notes, but...)
> 
> I'm not really sure who wrote that (possibly Garrett, but I wouldn't
> swear on it) but I'm sorry for the unfortunate choice of words.  I
> should have proof-read the release notes more carefully - mea culpa!
> 
> I don't think that any intentional slight was meant by it, just an
> off-the-cuff comment in engineer-speak that problably shouldn't have
> gone into the public docs.  Once we figure out who added it (I'm on a
> slow link at the moment or I'd inspect the CVS logs), we can determine
> just what was meant by it.

Earlier on, it was a real problem because httpd was depending on alarm() to
wake up a sleep and depending on the SIGALRM handler not being called. This
was quite some time ago, my memory isn't all that good from back then. I
have a feeling that it was from the 1.1 or 1.2 beta releases.  I am sure it
is no longer the case because the syscall that was originally added to
implement these semantics has since been removed.  signanosleep(2) is gone 
and sleep/usleep use normal nanosleep(2), so this note is out of date even.

> - Jordan
> 
> > 
> > It is somewhat disappointing to see:
> > 
> > o sleep(3) and usleep(3) are now implemented in terms of signanosleep(2)
> >   and now have correct SIGALRM interaction semantics and sleep(3) correctly
> >   returns the time remaining.  Some programs (notably apache httpd) bogusly
> >   depend on a sleep() "absorbing" a SIGALRM from a timer that expires durin
    g
> >   the life of the sleep.
> > 
> > in RELNOTES.TXT considering I have no idea where the bug in Apache that is
> > claiming would be and there have been no bug report or attempt to get this
> > fixed in Apache other than sticking lines in the release notes saying
> > "Apache is broken".
> > 
> > If there is a problem in Apache, please point it out so it can be fixed.  
> > 
> > -- 
> >      Marc Slemko     | Apache Group member
> >      marcs@znep.com  | marc@apache.org

Cheers,
-Peter



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 19:24:21 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA21514
          for freebsd-current-outgoing; Sat, 17 Oct 1998 19:24:21 -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 TAA21500;
          Sat, 17 Oct 1998 19:24:16 -0700 (PDT)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id TAA09182;
	Sat, 17 Oct 1998 19:21:41 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpdwS9174; Sun Oct 18 02:21:32 1998
Date: Sat, 17 Oct 1998 19:21:28 -0700 (PDT)
From: Julian Elischer 
To: "Steven P. Donegan" 
cc: Chuck Robey ,
        =?iso-8859-1?Q?S=F8ren_Schmidt?= ,
        freebsd-current@FreeBSD.ORG
Subject: Re: softupdates/smp
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

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.

julian


On Sat, 17 Oct 1998, Steven P. Donegan wrote:

> On Sat, 17 Oct 1998, Chuck Robey wrote:
> 
> > 
> > Keeping one rabbit's foot quite handy.
> > 
> 
> I'd rather not take up too much of the lists time on this - so my 
> question is who is actively working on softupdates? My system(s) are Tyan 
> Tomcat's - one a dual 133 with 256 meg RAM and the other a dual 233 with 
> 256 meg, both have kernels stripped to the bone (ie no drivers in the 
> kernel that are not needed) different drivers/boards on the two systems 
> (ie nothing else really in common hardware-wise). Both panic, according 
> to DDB, in softupdates code immediately after going SMP and tunefs -n enable.
> 
> A long time back softupdates worked OK (somewhat) unless I did the make 
> -j anything thing :-) Now it's a nice hard failure :-)
> 
> 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  Sat Oct 17 19:28:57 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA21890
          for freebsd-current-outgoing; Sat, 17 Oct 1998 19:28:57 -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 TAA21885
          for ; Sat, 17 Oct 1998 19:28:53 -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 LAA02679;
	Sun, 18 Oct 1998 11:58:25 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.1/8.9.0) id LAA03699;
	Sun, 18 Oct 1998 11:58:24 +0930 (CST)
Message-ID: <19981018115824.Q435@freebie.lemis.com>
Date: Sun, 18 Oct 1998 11:58:24 +0930
From: Greg Lehey 
To: Karl Pielorz , Mike Smith 
Cc: current@FreeBSD.ORG
Subject: Re: Serial Console - broken? (src as of 10/16 @ 16:43)
References: <199810171906.MAA06992@dingo.cdrom.com> <3628F31C.29EE2587@tdx.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <3628F31C.29EE2587@tdx.co.uk>; from Karl Pielorz on Sat, Oct 17, 1998 at 08:42:20PM +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
X-Mutt-References: <3628F31C.29EE2587@tdx.co.uk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Saturday, 17 October 1998 at 20:42:20 +0100, Karl Pielorz wrote:
>
>
> Mike Smith wrote:
>
>> Um, try checking the flags on your serial console.  You should have 0x10
>> or 0x30, but 0x50 or 0x70 would be bad.  (ie. you don't want 0x40 set).
>>
>> Apart from that, there's the hideous fear that something leaked in and
>> GDB is the default debugger.  Ick.
>
> Hmmm... Serial console is definitely set to:
>
> device          sio0    at isa? port "IO_COM1" flags 0x30 tty irq 4 vector
> siointr
>
> I presume 'Ick' is bad, but how bad? - i.e. easily fixable?

Fixed.  It's a "bug" in Vinum: previously, if you called debug, even
to set the debug flags, it also set remote gdb debugging:

 vinum debug 8

sets request trace debugging.

 vinum debug

takes you into the remote debugger.

Now there's a separate flag (256) to set remote debugging.  To get
remote debugging, you must do

  vinum debug 256    (once)
  vinum debug	     (every time you want to enter the debugger)

I'm just packaging up a new version of the distributions.  Watch the
commit messages or the times on the ftp site.

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  Sat Oct 17 19:35:04 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA22719
          for freebsd-current-outgoing; Sat, 17 Oct 1998 19:35:04 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from tor-dev1.nbc.netcom.ca (tor-dev1.nbc.netcom.ca [207.181.89.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22464
          for ; Sat, 17 Oct 1998 19:33:20 -0700 (PDT)
          (envelope-from taob@tor-dev1.nbc.netcom.ca)
Received: (from taob@localhost)
	by tor-dev1.nbc.netcom.ca (8.8.8/8.8.8) id WAA21286;
	Sat, 17 Oct 1998 22:30:37 -0400 (EDT)
Date: Sat, 17 Oct 1998 22:30:37 -0400 (EDT)
From: Brian Tao 
X-Sender: taob@tor-dev1.nbc.netcom.ca
To: Simon Shapiro 
cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG,
        mike@smith.net.au, Bruce Evans 
Subject: Re: Show Stopper? Failure to Install 19981014
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 Sat, 17 Oct 1998, Simon Shapiro wrote:
> 
> Please note that:
> 
> a.  At least here, newfs, in and by itself, in an installed system
> does not exhibit any of these messages, nor the faulty behavior.
> Only the context of sysinstall, from the boot floppy does.

    Not here.  I picked up an old 1GB drive and by habit, I
disklablled the first filesystem as swap, and then root.  Newfs'ing
from the command line always prints the error (contrary to prior
observations saying the error does not appear on second and subsequent
tries, while in /stand/sysinstall):

# disklabel -r da1s1 | fgrep -A 2 fstype
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:   204800   262144    4.2BSD        0     0     0   # (Cyl.   16*- 29*)
  b:   262144        0      swap                        # (Cyl.    0 - 16*)

# newfs da1s1a
/dev/rda1s1a:   204800 sectors in 50 cylinders of 1 tracks, 4096 sectors
        100.0MB in 4 cyl groups (16 c/g, 32.00MB/g, 6272 i/g)
super-block backups (for fsck -b #) at:
 32, 65568, 131104, 196640,
newfs: ioctl (WDINFO): Cross-device link
newfs: /dev/rda1s1a: can't rewrite disk label

# newfs da1s1a
/dev/rda1s1a:   204800 sectors in 50 cylinders of 1 tracks, 4096 sectors
        100.0MB in 4 cyl groups (16 c/g, 32.00MB/g, 6272 i/g)
super-block backups (for fsck -b #) at:
 32, 65568, 131104, 196640,
newfs: ioctl (WDINFO): Cross-device link
newfs: /dev/rda1s1a: can't rewrite disk label


    If I reverse the / and swap filesystems so that / starts at
cylinder 0, the error is not printed:

# disklabel -r da1s1 | fgrep -A 2 fstype
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:   262144        0    4.2BSD        0     0     0   # (Cyl.    0 - 16*)
  b:   204800   262144      swap                        # (Cyl.   16*- 29*)

# newfs da1s1a 
/dev/rda1s1a:   262144 sectors in 64 cylinders of 1 tracks, 4096 sectors
        128.0MB in 4 cyl groups (16 c/g, 32.00MB/g, 7936 i/g)
super-block backups (for fsck -b #) at:
 32, 65568, 131104, 196640,

#

    In both cases, the filesystem appears to be created correctly.
This happens with both 3.0-19981004 and 3.0-19981016 newfs.
-- 
Brian Tao (BT300, taob@risc.org)
"Though this be madness, yet there is method in't"


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 19:41:04 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA23634
          for freebsd-current-outgoing; Sat, 17 Oct 1998 19:41:04 -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 TAA23596
          for ; Sat, 17 Oct 1998 19:40:37 -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 KAA16030;
	Sun, 18 Oct 1998 10:39:14 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810180239.KAA16030@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Tom Jackson 
cc: Karl Pielorz , Chuck Robey ,
        freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-reply-to: Your message of "Sat, 17 Oct 1998 20:23:05 EST."
             <19981017202305.A12163@TOJ.org> 
Date: Sun, 18 Oct 1998 10:39:13 +0800
From: Peter Wemm 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Tom Jackson wrote:
> nm tells me module_register (dugh) not module_init.
> 
> For me, no amount of dumps on anything will produce a crash dump. On my
> laptop it just says bad dump device and on my server (which is not crashing
> now) I get a count down but no crash modules are produced.
> 
> btw, these are 100% elf and I don't think the panic is a smp problem.
> 
> Maybe Peter will know what the problem is.

I can guess, but I need more information.  Can you mail me your kernel 
config file[s] that are breaking?

My gut reaction is that the sysinit table is getting corrupted, or that 
something is calling module_register too soon.  module_init() initializes 
a couple of tailq's, and all sorts of things go wrong if something tries 
to add to these lists before then.

As a long shot, can you add #define DIAGNOSTIC to the start of
kern/kern_malloc.c and see if the fault address changes to something
along the lines of 0xdeadc0de.

How far does it get into the boot sequence before crashing?  What are the
last few messages?  It is possible that some filesystem initialization that
you are using that I didn't test with is causing this.

> On Sun, Oct 18, 1998 at 12:15:22AM +0100, Karl Pielorz wrote:
> > 
> > Tom Jackson wrote:
> > 
> > > [snip]
> > > 
> > > I'm getting this crash, not on elf(kernel+exec)/smp/scsi but on a old
> > > Thinkpad with a pccard ed0, a elf(kernel+exec)/up/ide. Thought since the
> > > reference to modules that pcvt instead of sc0 might work - no such luck.
> > > I get the panic right after the pcic is probed and before the pccard is
> > > initialized.
> > > 
> > > I'm not getting any crash dumps on any of my elf systems.
> > 
> > Hi,
> > 
> > I've been talking to Chuck about this - if the panic is similar / the same 
    as
> > his, you won't get a crashdump - as it's happening too soon into the boot
> > process...
> > 
> > The only thing I could think of was to have a line similar to:
> > 
> > config          kernel  root on XXX dumps on YYYY
> > 
> > In the kernel config - Though LINT warns against this, it might be the only
> > way of telling the system where to dump to - as it's panics so soon during
> > boot...
> > 
> > I'm hoping someone who knows more what there talking about will step in wit
    h
> > "That's a good/bad idea" - and why...
> > 
> > I seem to remember using the kernel config to specify the dump device, but
> > that was from ages ago (2.2.2? :-)
> > 
> > Regards,
> > 
> > Karl
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> > 
> 
> -- 
> Tom
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

Cheers,
-Peter
--
Peter Wemm    Netplex Consulting
"No coffee, No workee!" :-)



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 20:00:31 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA26821
          for freebsd-current-outgoing; Sat, 17 Oct 1998 20:00:31 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA26809
          for ; Sat, 17 Oct 1998 20:00:28 -0700 (PDT)
          (envelope-from itfs!nnd%itfs.nsk.su@gw.itfs.nsk.su)
Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id JAA12158 for current@FreeBSD.ORG; Sun, 18 Oct 1998 09:00:06 +0600
Received: by itfs.nsk.su; Sun, 18 Oct 98 10:02:30 +0700 (NST)
To: nnd@itfs.nsk.su
Cc: current@FreeBSD.ORG
References: <199810171346.PAA00718@gratis.grondar.za>
Message-ID: 
Organization: Scientific & Technical Enterprise INFOTEKA
From: nnd@itfs.nsk.su (Nickolay Dudorov)
Date: Sun, 18 Oct 98 10:02:30 +0700 (NST)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=koi8-r
Content-Transfer-Encoding: 8BIT
Subject: Re: CVS corruption through cvs-cur.4733.gz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mark Murray  wrote:

>>        After receiving and applying CTM's 'cvs-cur.4733.gz'
>> to my CVS tree I try to "cvs update" my 3.0 tree and
>> discover that there are some directories deleted from
>> CVS tree (in 'ports'). Some of this deletions prevent
>> "cvs ... update -Pd ." to finish its work (f.e.
>> 'ports/devel/glade/patches').
>> 
>>        What is the reason for this ?
>
>Someone did something naughty in the repository?

       And there may be somthing with CTM delta generation -
there is no new delta after 'cvs-cur.4733.gz'.

>
>>        How can I correct/synchronize my CVS-tree ?
>
>Manually remove the conflict in your /usr/ports area.

       I can finish "cvs update" after moving 'ports'
to 'ports-old'. It means that only this part of the
repository (ports) corrupted (?)


       N.Dudorov

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 20:05:42 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA27505
          for freebsd-current-outgoing; Sat, 17 Oct 1998 20:05:42 -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 UAA27500
          for ; Sat, 17 Oct 1998 20:05:37 -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 LAA23805;
	Sun, 18 Oct 1998 11:05:02 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810180305.LAA23805@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Chuck Robey 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-reply-to: Your message of "Sat, 17 Oct 1998 15:50:02 -0400."
              
Date: Sun, 18 Oct 1998 11:05:01 +0800
From: Peter Wemm 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Chuck Robey wrote:
> I'm now getting a panic on startup, SMP kernel, on a config file that
> was working fine a few days ago.  The panic is coming in module_register
> + 14.  I'd give you the stack dump, but I can't seem to get a kernel
> dump captured yet.
> 
> I checked, all my LKMs are brand new.  This is a fresh build for both
> the world and the kernel from equal sources (no intervening cvsup or cvs
> actions), with all new LKMs.  Normal ELF system you'd expect.
> 
> Panic is supervisor read, page not present.  Can't tell what module it
> was trying to load without the kernel dump (I think).  Panic message
> says it's in the swapper process, but I think that's not germane here
> (is it?).  I have a fault virtual address of 8be58955, I'm not sure
> that's useful, seeing as I can't translate that to a module address.

It is useful, but bad news. :-(

It means that the SYSINIT() process got scrambled somehow.

There are a bunch of sysinit's like this:

static moduledata_t root_bus_mod = {
        "rootbus",
        root_bus_module_handler,
        0 
};
DECLARE_MODULE(rootbus, root_bus_mod, SI_SUB_DRIVERS, SI_ORDER_FIRST);
.. which turns into
SYSINIT(rootbusmodule, SI_SUB_DRIVERS, SI_ORDER_FIRST, 
	module_register_init, &root_bus_mod)

Effectively, this causes init_main.c to call
  module_register_init((void *)&root_bus_mod);

module_register_init(void *arg)
{
    moduledata_t* data = (moduledata_t*) arg;
    error = module_register(data->name, data->evhand, data->priv, data->_file);
}
module_register(const char* name, modeventhand_t handler, void* arg, void *file)
{
    size_t namelen;
    namelen = strlen(name) + 1;
              ^^^^^^^^^^^^ Here is where it's crashing.

And there's the dilemma.  Either the name in the moduledata_t struct got 
smashed somehow, or the sysinit process is passing the wrong pointer to 
module_register_init().

I picked this one out for the example for no particular reason, this has 
been in the kernel for a while.  There are a number of these activated by 
new definitions of things like VFS_SET(), VNODEOP_SET(), EXEC_SET() macros 
in src/sys/*.h.

Hmm, you don't have MATH_EMULATE or GPL_MATH_EMULATE options turned on by 
any chance, do you?  Take them out if so.

Another thought..  Please try a 'make clean' and do a rebuild of the kernel.

Also, it would be helpful to know if the same problem happens with a plain 
a.out kernel booted from the standard bootblocks, not /boot/loader.  I'd 
be suprised if it was different though.

Cheers,
-Peter



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 20:13:40 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA28593
          for freebsd-current-outgoing; Sat, 17 Oct 1998 20:13:40 -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 UAA28571
          for ; Sat, 17 Oct 1998 20:13: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 LAA26224;
	Sun, 18 Oct 1998 11:12:18 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810180312.LAA26224@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mark Murray 
cc: nnd@itfs.nsk.su (Nickolay Dudorov), current@FreeBSD.ORG
Subject: Re: CVS corruption through cvs-cur.4733.gz 
In-reply-to: Your message of "Sat, 17 Oct 1998 15:46:25 +0200."
             <199810171346.PAA00718@gratis.grondar.za> 
Date: Sun, 18 Oct 1998 11:12:17 +0800
From: Peter Wemm 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mark Murray wrote:
>  wrote:
> >        After receiving and applying CTM's 'cvs-cur.4733.gz'
> > to my CVS tree I try to "cvs update" my 3.0 tree and
> > discover that there are some directories deleted from
> > CVS tree (in 'ports'). Some of this deletions prevent
> > "cvs ... update -Pd ." to finish its work (f.e.
> > 'ports/devel/glade/patches').
> > 
> >        What is the reason for this ?
> 
> Someone did something naughty in the repository?

Sort-of.  I cleaned out a pile of empty directories and Attics to help
'cvs update -d -P' along, but got some that were a bit too recent.  We've
recreated some of them so that people with reasonably recent ports trees
shouldn't be too inconvenienced.

> >        How can I correct/synchronize my CVS-tree ?
> 
> Manually remove the conflict in your /usr/ports area.

In this case, if you get a problem with ports/devel/glade/patches, then rm 
-rf the checked out version, it got 'cvs rm'ed from the repository a while 
ago, but cvs is being paranoid.  Give it a help along by removing the 
defunct checked out copies of the files.  And then rerun the
cvs update -dP (sorry).

> M

Cheers,
-Peter




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 20:40:58 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA01088
          for freebsd-current-outgoing; Sat, 17 Oct 1998 20:40:58 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from redfish.go2net.com (redfish.go2net.com [207.178.55.5])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA01076
          for ; Sat, 17 Oct 1998 20:40:44 -0700 (PDT)
          (envelope-from marcs@go2net.com)
Received: from marcs by redfish.go2net.com with smtp (Exim 1.82 #2)
	id 0zUjew-000155-00; Sat, 17 Oct 1998 20:37:34 -0700
Date: Sat, 17 Oct 1998 20:37:34 -0700 (PDT)
From: Marc Slemko 
X-Sender: marcs@redfish
To: Peter Wemm 
cc: "Jordan K. Hubbard" , current@FreeBSD.ORG
Subject: Re: sleep() and Apache in release notes 
In-Reply-To: <199810180220.KAA12204@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 Sun, 18 Oct 1998, Peter Wemm wrote:

> "Jordan K. Hubbard" wrote:
> > > (don't know who wrote what part of the release notes, but...)
> > 
> > I'm not really sure who wrote that (possibly Garrett, but I wouldn't
> > swear on it) but I'm sorry for the unfortunate choice of words.  I
> > should have proof-read the release notes more carefully - mea culpa!
> > 
> > I don't think that any intentional slight was meant by it, just an
> > off-the-cuff comment in engineer-speak that problably shouldn't have
> > gone into the public docs.  Once we figure out who added it (I'm on a
> > slow link at the moment or I'd inspect the CVS logs), we can determine
> > just what was meant by it.

Thanks.

I understand how such things can happen and that no slight was intended.
If FreeBSD was broken in some way then we certainly would include that in
the Apache documentation in the appropriate place, after being sure that
whoever is responsible is aware of it.

I do think I prefer the other error in the release notes that you fixed,
which was:

   An in-kernel linker is implemented and intended to replace the lkm
   system with the bogosity that goes with it



> 
> Earlier on, it was a real problem because httpd was depending on alarm() to
> wake up a sleep and depending on the SIGALRM handler not being called. This
> was quite some time ago, my memory isn't all that good from back then. I
> have a feeling that it was from the 1.1 or 1.2 beta releases.  I am sure it
> is no longer the case because the syscall that was originally added to
> implement these semantics has since been removed.  signanosleep(2) is gone 
> and sleep/usleep use normal nanosleep(2), so this note is out of date even.

Mmm.  I am having some trouble figuring out where this would be since
Apache, as a general rule with a couple of exceptions, normally doesn't
call sleep().

1.2 did use sleep() in the parent process but I don't see where any
SIGALRMs would be involved there.

bccing to the Apache development list (since it doesn't accept posts from
non-subscribers).


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 21:03:53 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA03265
          for freebsd-current-outgoing; Sat, 17 Oct 1998 21:03: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 VAA03260
          for ; Sat, 17 Oct 1998 21:03: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 AAA00892;
	Sun, 18 Oct 1998 00:00:45 -0400 (EDT)
Date: Sun, 18 Oct 1998 00:00:45 -0400 (EDT)
From: Chuck Robey 
To: Peter Wemm 
cc: freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-Reply-To: <199810180305.LAA23805@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 Sun, 18 Oct 1998, Peter Wemm wrote:

> 
> It is useful, but bad news. :-(
> 
> It means that the SYSINIT() process got scrambled somehow.
> 
> There are a bunch of sysinit's like this:
> 
> static moduledata_t root_bus_mod = {
>         "rootbus",
>         root_bus_module_handler,
>         0 
> };
> DECLARE_MODULE(rootbus, root_bus_mod, SI_SUB_DRIVERS, SI_ORDER_FIRST);
> .. which turns into
> SYSINIT(rootbusmodule, SI_SUB_DRIVERS, SI_ORDER_FIRST, 
> 	module_register_init, &root_bus_mod)
> 
> Effectively, this causes init_main.c to call
>   module_register_init((void *)&root_bus_mod);
> 
> module_register_init(void *arg)
> {
>     moduledata_t* data = (moduledata_t*) arg;
>     error = module_register(data->name, data->evhand, data->priv, data->_file);
> }
> module_register(const char* name, modeventhand_t handler, void* arg, void *file)
> {
>     size_t namelen;
>     namelen = strlen(name) + 1;
>               ^^^^^^^^^^^^ Here is where it's crashing.
> 
> And there's the dilemma.  Either the name in the moduledata_t struct got 
> smashed somehow, or the sysinit process is passing the wrong pointer to 
> module_register_init().
> 
> I picked this one out for the example for no particular reason, this has 
> been in the kernel for a while.  There are a number of these activated by 
> new definitions of things like VFS_SET(), VNODEOP_SET(), EXEC_SET() macros 
> in src/sys/*.h.
> 
> Hmm, you don't have MATH_EMULATE or GPL_MATH_EMULATE options turned on by 
> any chance, do you?  Take them out if so.

Peter, I just got home (I'd warned previously I would be out for several
hours, but I didn't expect it to get this hot this soon).  Let me hit
some points first.

Earlier there was a question from Mike about boot blocks.  I have never
done anything to my kernel builds.  They were aout.  Has that changed in
some way?  I'm pretty certain it's still aout, right, for the kernel?  I
haven't updated my boot blocks, because I thought that for aout, it
wasn't called for.  Correct me if I'm wrong.

The hit is happening about like you say, and if that's a string, I can
use ddb to hunt for it, I just can't seem to coax ddb to dump a kernel
core file.

options GPL_MATH_EMULATE has always been in my kernel config.  I'll take
it out now.  I'm surprised, I'd seen nothing about taking it out
anywhere.

I just got home, I am going to ingest some protein before you get any
data out of me ...

> 
> Another thought..  Please try a 'make clean' and do a rebuild of the kernel.
> 
> Also, it would be helpful to know if the same problem happens with a plain 
> a.out kernel booted from the standard bootblocks, not /boot/loader.  I'd 
> be suprised if it was different though.
> 
> Cheers,
> -Peter
> 
> 
> 
> 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  Sat Oct 17 21:21:15 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA04669
          for freebsd-current-outgoing; Sat, 17 Oct 1998 21:21:15 -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 VAA04662
          for ; Sat, 17 Oct 1998 21:21:07 -0700 (PDT)
          (envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.27] by silverback.gorilla.net with ESMTP
  (SMTPD32-4.07) id AB8216B0146; Sat, 17 Oct 1998 23:16:02 CDT
Received: (from tom@localhost)
	by peeper.TOJ.org (8.9.1/8.8.8) id XAA01279;
	Sat, 17 Oct 1998 23:20:24 -0500 (CDT)
	(envelope-from tom)
Message-ID: <19981017231953.A1263@TOJ.org>
Date: Sat, 17 Oct 1998 23:19:53 -0500
From: Tom Jackson 
To: Peter Wemm 
Cc: Karl Pielorz , Chuck Robey ,
        freebsd-current@FreeBSD.ORG
Subject: Re: panic
References: <19981017202305.A12163@TOJ.org> <199810180239.KAA16030@spinner.netplex.com.au>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="J2SCkAp4GZ/dPZZf"
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199810180239.KAA16030@spinner.netplex.com.au>; from Peter Wemm on Sun, Oct 18, 1998 at 10:39:13AM +0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii

On Sun, Oct 18, 1998 at 10:39:13AM +0800, Peter Wemm wrote:
> Tom Jackson wrote:
> > nm tells me module_register (dugh) not module_init.
> > 
> > For me, no amount of dumps on anything will produce a crash dump. On my
> > laptop it just says bad dump device and on my server (which is not crashing
> > now) I get a count down but no crash modules are produced.
> > 
> > btw, these are 100% elf and I don't think the panic is a smp problem.
> > 
> > Maybe Peter will know what the problem is.
> 
> I can guess, but I need more information.  Can you mail me your kernel 
> config file[s] that are breaking?
> 
> My gut reaction is that the sysinit table is getting corrupted, or that 
> something is calling module_register too soon.  module_init() initializes 
> a couple of tailq's, and all sorts of things go wrong if something tries 
> to add to these lists before then.
> 
> As a long shot, can you add #define DIAGNOSTIC to the start of
> kern/kern_malloc.c and see if the fault address changes to something
> along the lines of 0xdeadc0de.

ip is still 0xf01205ac, that is, no change

> 
> How far does it get into the boot sequence before crashing?  What are the
> last few messages?  It is possible that some filesystem initialization that
> you are using that I didn't test with is causing this.

various probes
...
pcic: controller irq 3
Initializing pc-card drivers: ed sio
Fatal Trap 12
...

when I hit any key at the db>, Card inserted, slot 1, appears at the prompt.
In a normal boot sequence, changing root device to wd0s1a, normally appears
between the Initializing... and the Card inserted...

To reiterate, this problem only shows up on my old Thinkpad. No problem on
the smp server. Let me know if there's anything else I can do.
> 
> > On Sun, Oct 18, 1998 at 12:15:22AM +0100, Karl Pielorz wrote:
> > > 
> > > Tom Jackson wrote:
> > > 
> > > > [snip]
> > > > 
> > > > I'm getting this crash, not on elf(kernel+exec)/smp/scsi but on a old
> > > > Thinkpad with a pccard ed0, a elf(kernel+exec)/up/ide. Thought since the
> > > > reference to modules that pcvt instead of sc0 might work - no such luck.
> > > > I get the panic right after the pcic is probed and before the pccard is
> > > > initialized.
> > > > 
> > > > I'm not getting any crash dumps on any of my elf systems.
> > > 
> > > Hi,
> > > 
> > > I've been talking to Chuck about this - if the panic is similar / the same 
>     as
> > > his, you won't get a crashdump - as it's happening too soon into the boot
> > > process...
> > > 
> > > The only thing I could think of was to have a line similar to:
> > > 
> > > config          kernel  root on XXX dumps on YYYY
> > > 
> > > In the kernel config - Though LINT warns against this, it might be the only
> > > way of telling the system where to dump to - as it's panics so soon during
> > > boot...
> > > 
> > > I'm hoping someone who knows more what there talking about will step in wit
>     h
> > > "That's a good/bad idea" - and why...
> > > 
> > > I seem to remember using the kernel config to specify the dump device, but
> > > that was from ages ago (2.2.2? :-)
> > > 
> > > Regards,
> > > 
> > > Karl
> > > 
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-current" in the body of the message
> > > 
> > 
> > -- 
> > Tom
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> > 
> 
> Cheers,
> -Peter
> --
> Peter Wemm    Netplex Consulting
> "No coffee, No workee!" :-)
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
Tom

--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Description: kernel config
Content-Disposition: attachment; filename=SLIM

#
# PCCARD -- GENERIC laptop support
#
# For more information read the handbook part System Administration -> 
# Configuring the FreeBSD Kernel -> The Configuration File. 
# The handbook is available in /usr/share/doc/handbook or online as
# latest version from the FreeBSD World Wide Web server 
# 
#
# An exhaustive list of options and more detailed explanations of the 
# device lines is present in the ./LINT configuration file. If you are 
# in doubt as to the purpose or necessity of a line, check first in LINT.
#
#	$Id: PCCARD,v 1.2 1997/11/11 00:47:01 nate Exp $

machine		"i386"
cpu		"I386_CPU"
cpu		"I486_CPU"
#cpu		"I586_CPU"
#cpu		"I686_CPU"
ident		SLIM
maxusers	10

options		GPL_MATH_EMULATE	#Support for x87 GPL emulation
#options		MATH_EMULATE		# x87 emulation
options		INET			#InterNETworking
options		FFS			#Berkeley Fast Filesystem
options		NFS			#Network Filesystem
options		MSDOSFS			#MSDOS Filesystem
#options		"CD9660"		#ISO 9660 Filesystem
options		PROCFS			#Process filesystem
#options		DEVFS
#options		SLICE
options		"COMPAT_43"		#Compatible with BSD 4.3 [KEEP THIS!]
#options		SCSI_DELAY=15		#Be pessimistic about Joe SCSI device
options		UCONSOLE		#Allow users to grab the console
options		FAILSAFE		#Be conservative
options		USERCONFIG		#boot -c editor
options		VISUAL_USERCONFIG	#visual boot -c editor
options		"NO_F00F_HACK"
# strings -aout /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL
options		INCLUDE_CONFIG_FILE	# include this file in kernel
#options		"VM86"
#options		VESA
options		DDB

config		kernel	root on wd0

controller	isa0
#controller	pci0

controller	fdc0	at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk		fd0	at fdc0 drive 0

#options		"CMD640"	# work around CMD640 chip deficiency
controller	wdc0	at isa? port "IO_WD1" bio irq 14 vector wdintr
disk		wd0	at wdc0 drive 0

#controller	wdc1	at isa? port "IO_WD2" bio irq 15 vector wdintr

#options		ATAPI		#Enable ATAPI support for IDE bus
#options		ATAPI_STATIC	#Don't do it as an LKM
#device		wcd0	#IDE CD-ROM

#controller	aic0	at isa? port 0x340 bio irq 11 vector aicintr

#controller	scbus0

#device		sd0

#device		od0	#See LINT for possible `od' options.

#device		st0

#device		cd0	#Only need one of these, the code dynamically grows

# syscons is the default console driver, resembling an SCO console
#device		sc0	at isa? port "IO_KBD" tty irq 1 flags 0x10 vector scintr
# Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver
device		vt0	at isa? port "IO_KBD" conflicts tty irq 1 vector pcrint
options		XSERVER			# support for X server
#options		FAT_CURSOR		# start with block cursor
# If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines
options		PCVT_SCANSET=2		# IBM keyboards are non-std

device		npx0	at isa? port "IO_NPX" irq 13 vector npxintr

#
# Laptop support (see LINT for more options)
#
device		apm0    at isa? flags 0x31	# Advanced Power Management

# PCCARD (PCMCIA) support
controller	card0
device		pcic0	at card?
device		pcic1	at card?

device		sio0	at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr
#device		sio1	at isa? port "IO_COM2" tty irq 3 vector siointr
#device		sio2	at isa? disable port "IO_COM3" tty irq 5 vector siointr
#device		sio3	at isa? disable port "IO_COM4" tty irq 9 vector siointr

device		lpt0	at isa? port? tty irq 7 vector lptintr

device		psm0	at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr
options		PSM_HOOKAPM		#hook the APM resume event
options		PSM_RESETAFTERSUSPEND	#reset the device at the resume event

device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr
#device ep0 at isa? port 0x300 net irq 10 vector epintr
#device fe0 at isa? port 0x300 net irq ? vector feintr

pseudo-device	loop
pseudo-device	ether
#pseudo-device	sl	1
# iijppp uses tun instead of ppp device
#pseudo-device	ppp	1
pseudo-device	tun	1
pseudo-device	pty	16
pseudo-device	gzip		# Exec gzipped a.out's

# KTRACE enables the system-call tracing facility ktrace(2).
# This adds 4 KB bloat to your kernel, and slightly increases
# the costs of each syscall.
options		KTRACE		#kernel tracing

# This provides support for System V shared memory.
#
options         SYSVSHM
#options		SYSVSEM
#options		SYSVMSG

--J2SCkAp4GZ/dPZZf--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 21:29:22 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA05204
          for freebsd-current-outgoing; Sat, 17 Oct 1998 21:29:22 -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 VAA05197;
          Sat, 17 Oct 1998 21:29:19 -0700 (PDT)
          (envelope-from donegan@oldnews.quick.net)
Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id VAA05720; Sat, 17 Oct 1998 21:28:57 -0700 (PDT)
Date: Sat, 17 Oct 1998 21:28:56 -0700 (PDT)
From: "Steven P. Donegan" 
To: Julian Elischer 
cc: Chuck Robey ,
        =?iso-8859-1?Q?S=F8ren_Schmidt?= ,
        freebsd-current@FreeBSD.ORG
Subject: Re: softupdates/smp
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 Sat, 17 Oct 1998, Julian Elischer 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.
> 
> julian
> 

Thanks for the feedback Julian - from the other panic's being talked 
about it may just be collateral damage - I'll await those items being 
fixed before re-attempting SMP/softupdates again.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 21:30:59 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA05381
          for freebsd-current-outgoing; Sat, 17 Oct 1998 21:30: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 VAA05364
          for ; Sat, 17 Oct 1998 21:30:51 -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 MAA16935;
	Sun, 18 Oct 1998 12:28:29 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810180428.MAA16935@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Tom Jackson 
cc: Karl Pielorz , Chuck Robey ,
        freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-reply-to: Your message of "Sat, 17 Oct 1998 23:19:53 EST."
             <19981017231953.A1263@TOJ.org> 
Date: Sun, 18 Oct 1998 12:28:28 +0800
From: Peter Wemm 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Tom Jackson wrote:
[..]
> options		GPL_MATH_EMULATE	#Support for x87 GPL emulation
> #options		MATH_EMULATE		# x87 emulation


Ahh shit!
sys/gnu/i386/fpuemul/fpu_entry.c:

moduledata_t gnufpumod = {
        "gnufpu",
        gnufpu_modevent,
        0
};
DECLARE_MODULE(gnufpu, gnufpu_modevent, SI_SUB_PSEUDO, SI_ORDER_ANY);

The declaration should be:
DECLARE_MODULE(gnufpu, gnufpumod, SI_SUB_PSEUDO, SI_ORDER_ANY);

This would explain a few things...  The function address is being passed in 
instead of the parameter block.

If you need it, try using plain MATH_EMULATE, or try the fix above.

Cheers,
-Peter




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 22:07:31 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA08339
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:07:31 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08331
          for ; Sat, 17 Oct 1998 22:07:27 -0700 (PDT)
          (envelope-from ache@nagual.pp.ru)
Received: (from ache@localhost)
	by nagual.pp.ru (8.9.1/8.9.1) id JAA29669;
	Sun, 18 Oct 1998 09:06:57 +0400 (MSD)
	(envelope-from ache)
Message-ID: <19981018090656.A26533@nagual.pp.ru>
Date: Sun, 18 Oct 1998 09:06:56 +0400
From: "Andrey A. Chernov" 
To: Marc Slemko , current@FreeBSD.ORG,
        "Jordan K. Hubbard" 
Subject: Re: sleep() and Apache in release notes
Mail-Followup-To: Marc Slemko , current@FreeBSD.ORG,
	"Jordan K. Hubbard" 
References: 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: ; from marcs@znep.com on Sat, Oct 17, 1998 at 05:22:24PM -0700
Organization: Biomechanoid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> o sleep(3) and usleep(3) are now implemented in terms of signanosleep(2)

It is not true, they are implemented using nanosleep(2), signanosleep(2) 
removed some time ago as non-standard. 

>   and now have correct SIGALRM interaction semantics and sleep(3) correctly
>   returns the time remaining.  Some programs (notably apache httpd) bogusly

It was happen with some old Apache version, so obsoleted at this moment.

-- 
Andrey A. Chernov
http://www.nagual.pp.ru/~ache/
MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 22:18:26 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA09286
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:18:26 -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 WAA09275
          for ; Sat, 17 Oct 1998 22:18:22 -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 BAA00353;
	Sun, 18 Oct 1998 01:16:52 -0400 (EDT)
Date: Sun, 18 Oct 1998 01:16:52 -0400 (EDT)
From: Chuck Robey 
To: Peter Wemm 
cc: Tom Jackson , Karl Pielorz ,
        freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-Reply-To: <199810180428.MAA16935@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 Sun, 18 Oct 1998, Peter Wemm wrote:

> Tom Jackson wrote:
> [..]
> > options		GPL_MATH_EMULATE	#Support for x87 GPL emulation
> > #options		MATH_EMULATE		# x87 emulation
> 
> 
> Ahh shit!
> sys/gnu/i386/fpuemul/fpu_entry.c:
> 
> moduledata_t gnufpumod = {
>         "gnufpu",
>         gnufpu_modevent,
>         0
> };
> DECLARE_MODULE(gnufpu, gnufpu_modevent, SI_SUB_PSEUDO, SI_ORDER_ANY);
> 
> The declaration should be:
> DECLARE_MODULE(gnufpu, gnufpumod, SI_SUB_PSEUDO, SI_ORDER_ANY);
> 
> This would explain a few things...  The function address is being passed in 
> instead of the parameter block.
> 
> If you need it, try using plain MATH_EMULATE, or try the fix above.

Tried, verified, works!  Got the patch offa freefall (couldn't wait for
cvsup, wouldn't anyhow).

Ummmm ... Peter ... who tells Jordan?

> 
> Cheers,
> -Peter
> 
> 
> 
> 
> 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  Sat Oct 17 22:20:48 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA09562
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:20:48 -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 WAA09554
          for ; Sat, 17 Oct 1998 22:20:40 -0700 (PDT)
          (envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.47] by silverback.gorilla.net with ESMTP
  (SMTPD32-4.07) id A98BB60084; Sun, 18 Oct 1998 00:15:55 CDT
Received: (from tom@localhost)
	by peeper.TOJ.org (8.9.1/8.8.8) id AAA02130;
	Sun, 18 Oct 1998 00:20:19 -0500 (CDT)
	(envelope-from tom)
Message-ID: <19981018001948.B1263@TOJ.org>
Date: Sun, 18 Oct 1998 00:19:48 -0500
From: Tom Jackson 
To: Peter Wemm , Tom Jackson 
Cc: Karl Pielorz , Chuck Robey ,
        freebsd-current@FreeBSD.ORG
Subject: Re: panic
References: <19981017231953.A1263@TOJ.org> <199810180428.MAA16935@spinner.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199810180428.MAA16935@spinner.netplex.com.au>; from Peter Wemm on Sun, Oct 18, 1998 at 12:28:28PM +0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

*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
Unknown error in reboot
Enter root password...

This one's really a gem. Don't even go into ddb. Let me know if you want to 
tackle that one.

Thanks for the help on the other. Imagine Chuck's problem isn't this.

On Sun, Oct 18, 1998 at 12:28:28PM +0800, Peter Wemm wrote:
> Tom Jackson wrote:
> [..]
> > options		GPL_MATH_EMULATE	#Support for x87 GPL emulation
> > #options		MATH_EMULATE		# x87 emulation
> 
> 
> Ahh shit!
> sys/gnu/i386/fpuemul/fpu_entry.c:
> 
> moduledata_t gnufpumod = {
>         "gnufpu",
>         gnufpu_modevent,
>         0
> };
> DECLARE_MODULE(gnufpu, gnufpu_modevent, SI_SUB_PSEUDO, SI_ORDER_ANY);
> 
> The declaration should be:
> DECLARE_MODULE(gnufpu, gnufpumod, SI_SUB_PSEUDO, SI_ORDER_ANY);
> 
> This would explain a few things...  The function address is being passed in 
> instead of the parameter block.
> 
> If you need it, try using plain MATH_EMULATE, or try the fix above.
> 
> Cheers,
> -Peter
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
Tom

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 22:28:06 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA10107
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:28:06 -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 WAA10102
          for ; Sat, 17 Oct 1998 22:28:05 -0700 (PDT)
          (envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.29] by silverback.gorilla.net with ESMTP
  (SMTPD32-4.07) id AB45DA00E8; Sun, 18 Oct 1998 00:23:17 CDT
Received: (from tom@localhost)
	by peeper.TOJ.org (8.9.1/8.8.8) id AAA02580;
	Sun, 18 Oct 1998 00:27:40 -0500 (CDT)
	(envelope-from tom)
Message-ID: <19981018001948.B1263@TOJ.org>
Date: Sun, 18 Oct 1998 00:27:09 -0500
From: Tom Jackson 
To: Peter Wemm 
Cc: Karl Pielorz , Chuck Robey ,
        freebsd-current@FreeBSD.ORG
Subject: Re: panic
References: <19981017231953.A1263@TOJ.org> <199810180428.MAA16935@spinner.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199810180428.MAA16935@spinner.netplex.com.au>; from Peter Wemm on Sun, Oct 18, 1998 at 12:28:28PM +0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

*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
Unknown error in reboot
Enter root password...

This one's really a gem. Don't even go into ddb. Let me know if you want to 
tackle that one.

Thanks for the help on the other. Imagine Chuck's problem isn't this.

On Sun, Oct 18, 1998 at 12:28:28PM +0800, Peter Wemm wrote:
> Tom Jackson wrote:
> [..]
> > options		GPL_MATH_EMULATE	#Support for x87 GPL emulation
> > #options		MATH_EMULATE		# x87 emulation
> 
> 
> Ahh shit!
> sys/gnu/i386/fpuemul/fpu_entry.c:
> 
> moduledata_t gnufpumod = {
>         "gnufpu",
>         gnufpu_modevent,
>         0
> };
> DECLARE_MODULE(gnufpu, gnufpu_modevent, SI_SUB_PSEUDO, SI_ORDER_ANY);
> 
> The declaration should be:
> DECLARE_MODULE(gnufpu, gnufpumod, SI_SUB_PSEUDO, SI_ORDER_ANY);
> 
> This would explain a few things...  The function address is being passed in 
> instead of the parameter block.
> 
> If you need it, try using plain MATH_EMULATE, or try the fix above.
> 
> Cheers,
> -Peter
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
Tom

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 22:28:46 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA10199
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:28:46 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10194
          for ; Sat, 17 Oct 1998 22:28:44 -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 WAA09936;
	Sat, 17 Oct 1998 22:32:02 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810180532.WAA09936@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Tom Jackson 
cc: Peter Wemm , Karl Pielorz ,
        Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-reply-to: Your message of "Sun, 18 Oct 1998 00:19:48 CDT."
             <19981018001948.B1263@TOJ.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 17 Oct 1998 22:32:01 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> *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
> Unknown error in reboot
> Enter root password...
> 
> This one's really a gem. Don't even go into ddb. Let me know if you want to 
> tackle that one.

This isn't something that would take you to ddb; it's fsck exploding 
for some reason.  What happens if you exit single-user mode at this 
point?  Does the system come up OK?

The "normal" math emulator ought to work as well as it ever has(n't).

-- 
\\  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 17 22:34:34 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA10544
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:34:34 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10533
          for ; Sat, 17 Oct 1998 22:34: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 WAA09998;
	Sat, 17 Oct 1998 22:38:38 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810180538.WAA09998@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Tom Jackson 
cc: Peter Wemm , Karl Pielorz ,
        Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-reply-to: Your message of "Sun, 18 Oct 1998 00:27:09 CDT."
             <19981018001948.B1263@TOJ.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 17 Oct 1998 22:38:37 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> *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.

-- 
\\  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 17 22:34:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA10545
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:34:35 -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 WAA10535
          for ; Sat, 17 Oct 1998 22:34:32 -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 WAA25548;
	Sat, 17 Oct 1998 22:33:58 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Chuck Robey 
cc: Peter Wemm , Tom Jackson ,
        Karl Pielorz , freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-reply-to: Your message of "Sun, 18 Oct 1998 01:16:52 EDT."
              
Date: Sat, 17 Oct 1998 22:33:57 -0700
Message-ID: <25544.908688837@time.cdrom.com>
From: "Jordan K. Hubbard" 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It'll make it into the ERRATA.  Given that the modules are optional, I don't consider
it a tag-sliding offense.

- Jordan

> On Sun, 18 Oct 1998, Peter Wemm wrote:
> 
> > Tom Jackson wrote:
> > [..]
> > > options		GPL_MATH_EMULATE	#Support for x87 GPL emulation
> > > #options		MATH_EMULATE		# x87 emulation
> > 
> > 
> > Ahh shit!
> > sys/gnu/i386/fpuemul/fpu_entry.c:
> > 
> > moduledata_t gnufpumod = {
> >         "gnufpu",
> >         gnufpu_modevent,
> >         0
> > };
> > DECLARE_MODULE(gnufpu, gnufpu_modevent, SI_SUB_PSEUDO, SI_ORDER_ANY);
> > 
> > The declaration should be:
> > DECLARE_MODULE(gnufpu, gnufpumod, SI_SUB_PSEUDO, SI_ORDER_ANY);
> > 
> > This would explain a few things...  The function address is being passed in
 
> > instead of the parameter block.
> > 
> > If you need it, try using plain MATH_EMULATE, or try the fix above.
> 
> Tried, verified, works!  Got the patch offa freefall (couldn't wait for
> cvsup, wouldn't anyhow).
> 
> Ummmm ... Peter ... who tells Jordan?
> 
> > 
> > Cheers,
> > -Peter
> > 
> > 
> > 
> > 
> > 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


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 22:43:07 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA11210
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:43:07 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11199
          for ; Sat, 17 Oct 1998 22:42:57 -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 WAA10065;
	Sat, 17 Oct 1998 22:46:52 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810180546.WAA10065@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" 
cc: Chuck Robey , Peter Wemm ,
        Tom Jackson , Karl Pielorz ,
        freebsd-current@FreeBSD.ORG
Subject: Re: panic 
In-reply-to: Your message of "Sat, 17 Oct 1998 22:33:57 PDT."
             <25544.908688837@time.cdrom.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 17 Oct 1998 22:46:50 -0700
From: Mike Smith 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> It'll make it into the ERRATA.  Given that the modules are optional, I
> don't consider it a tag-sliding offense.

It completely breaks the GPL_MATH_EMULATE option; it's not just a 
module-related issue.



-- 
\\  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 17 22:49:18 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA11604
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:49:18 -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 WAA11598
          for ; Sat, 17 Oct 1998 22:49:15 -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 HAA07086;
	Sun, 18 Oct 1998 07:48:44 +0200 (SAT)
From: John Hay 
Message-Id: <199810180548.HAA07086@zibbi.mikom.csir.co.za>
Subject: Re: panic
In-Reply-To: <19981018001948.B1263@TOJ.org> from Tom Jackson at "Oct 18, 98 00:27:09 am"
To: toj@gorilla.net (Tom Jackson)
Date: Sun, 18 Oct 1998 07:48:44 +0200 (SAT)
Cc: freebsd-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

> 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
> Unknown error in reboot
> Enter root password...
> 

Hmmm. This is interesting. I saw the same signal 10 on a 386EX system
last night when I was trying to help a friend with an embedded system
that he want to use FreeBSD on. I still don't know what the solution
is though. The strange thing is that it seems like fsck is almost
finished when this happens. It would go through al the steps and will
ask if it should mark the filesystem clean and only after that it
would give the bus error. The kernel is still the GENERIC kernel and
it is a 3.0 SNAP of a few days ago. Maybe the is something wrong
with our math emulation on processors without a math processor?

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  Sat Oct 17 22:49:56 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA11687
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:49:56 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp.hkstar.com (cassiopeia.hkstar.com [202.82.3.11])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11681
          for ; Sat, 17 Oct 1998 22:49:40 -0700 (PDT)
          (envelope-from c5666305@b1.hkstar.com)
Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by smtp.hkstar.com (8.8.8/8.8.4) with ESMTP id NAA10076 for ; Sun, 18 Oct 1998 13:49:08 +0800 (HKT)
Received: (from c5666305@localhost)
	by b1.hkstar.com (8.8.8/8.8.8) id NAA11083
	for current@freebsd.org; Sun, 18 Oct 1998 13:51:06 +0800 (HKT)
From: Chan Yiu Wah 
Message-Id: <199810180551.NAA11083@b1.hkstar.com>
Subject: does 3.0-RELEASE support pcmcia as PAO
To: current@FreeBSD.ORG
Date: Sun, 18 Oct 1998 13:51:06 +0800 (HKT)
X-Mailer: ELM [version 2.5 PL0b1]
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,

I would like to know if 3.0-RELEASE does support pcmcia for laptop as the
PAO ?  Thanks.

Clarence

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 22:52:12 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA11850
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:52:12 -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 WAA11842
          for ; Sat, 17 Oct 1998 22:52:08 -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 BAA12554;
	Sun, 18 Oct 1998 01:51:29 -0400 (EDT)
Date: Sun, 18 Oct 1998 01:51:28 -0400 (EDT)
From: Brian Feldman 
To: Peter Wemm 
cc: current@FreeBSD.ORG
Subject: Re: modules/atapi change 
In-Reply-To: <199810170125.JAA23793@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

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.

Cheers,
Brian Feldman

On Sat, 17 Oct 1998, Peter Wemm wrote:

> Brian Feldman wrote:
> > @ is linked to /usr/src/sys/sys
> > Of course, it should be linked with /usr/src/sys. Peter, if I knew how to
> > fix the Makefile, I would.
> 
> A couple of things..  bsd.kmod.mk sets this link.  Are you sure
> /usr/share/mk/bsd.kmod.mk has been updated correctly? 
> (cd /usr/src/share/mk; make install if not)
> 
> Second, if this was created before bsd.kmod.mk was updated, the old link 
> will not get changed.  You'll have to do a 'make clean' first to get rid 
> of the old one.
> 
> Make sure that you got a sys/modules/Makefile.inc file that sets KLDMOD.  
> Otherwise bsd.kmod.mk works in LKM mode.
> 
> I'd be very wary of the atapi/wcd modules at the moment, I have not tested
> them (I don't have IDE active on any machines within testing reach).
> 
> > Cheers,
> > Brian Feldman
> 
> Cheers,
> -Peter
> 
> 
> 
> 
> 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  Sat Oct 17 22:52:27 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA11885
          for freebsd-current-outgoing; Sat, 17 Oct 1998 22:52:27 -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 WAA11857
          for ; Sat, 17 Oct 1998 22:52:16 -0700 (PDT)
          (envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.13] by silverback.gorilla.net with ESMTP
  (SMTPD32-4.07) id A0EF1A400D8; Sun, 18 Oct 1998 00:47:27 CDT
Received: (from tom@localhost)
	by peeper.TOJ.org (8.9.1/8.8.8) id AAA02693;
	Sun, 18 Oct 1998 00:51:51 -0500 (CDT)
	(envelope-from tom)
Message-ID: <19981018005120.C1263@TOJ.org>
Date: Sun, 18 Oct 1998 00:51:20 -0500
From: Tom Jackson 
To: Mike Smith 
Cc: Peter Wemm , Karl Pielorz ,
        Chuck Robey , freebsd-current@FreeBSD.ORG
Subject: Re: panic
References: <19981018001948.B1263@TOJ.org> <199810180532.WAA09936@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199810180532.WAA09936@dingo.cdrom.com>; from Mike Smith on Sat, Oct 17, 1998 at 10:32:01PM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Oct 17, 1998 at 10:32:01PM -0700, 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
> > Unknown error in reboot
> > Enter root password...
> > 
> > This one's really a gem. Don't even go into ddb. Let me know if you want to 
> > tackle that one.
> 
> This isn't something that would take you to ddb; it's fsck exploding 
> for some reason.  What happens if you exit single-user mode at this 
> point?  Does the system come up OK?
> 
> The "normal" math emulator ought to work as well as it ever has(n't).
> 

it goes ahaead and comes up with:

Setting up DEVFS: .
awk: fatal error: internal error
Oct 18 ... slim /kernel.old: pid 219 (awk),uid 0:exited on signal 6 (core
dumped)
Abort trap - core dumped
Starting local daemons...

normal from here

Struck me as strange because I know the default is and I had started with the
less restricted MATH_EMULATE way back when.

-- 
Tom

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

From owner-freebsd-current  Sat Oct 17 23:15:35 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA13205
          for freebsd-current-outgoing; Sat, 17 Oct 1998 23:15:35 -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 XAA13199
          for ; Sat, 17 Oct 1998 23:15:29 -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 IAA07410;
	Sun, 18 Oct 1998 08:14:20 +0200 (SAT)
From: John Hay 
Message-Id: <199810180614.IAA07410@zibbi.mikom.csir.co.za>
Subject: Re: does 3.0-RELEASE support pcmcia as PAO
In-Reply-To: <199810180551.NAA11083@b1.hkstar.com> from Chan Yiu Wah at "Oct 18, 98 01:51:06 pm"
To: c5666305@b1.hkstar.com (Chan Yiu Wah)
Date: Sun, 18 Oct 1998 08:14:20 +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

> 
> I would like to know if 3.0-RELEASE does support pcmcia for laptop as the
> PAO ?  Thanks.

Well the install floppy don't really cater for it and there is certain
cards that work with the PAO 2.2.7 boot floppy, but don't work with 3.0.
I cheated by using the PAO boot floppy and then in the options set it
to install 3.0 for me. It won't be able to do everything properly though.
For example it doesn't know about the new X, but it did give me a basic
install and I can now try to figure out why 3.0 don't work with my
ACCTON 2212 ethernet card. It is supposed to be a NE2000 compatable, but
it looks like our pccardd gets confused by something and I get the dreaded
"Resource allocation failure for ...".

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  Sat Oct 17 23:39:32 1998
Return-Path: 
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA15791
          for freebsd-current-outgoing; Sat, 17 Oct 1998 23:39:32 -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 XAA15778
          for ; Sat, 17 Oct 1998 23:39:16 -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 IAA03066;
	Sun, 18 Oct 1998 08:38:16 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <199810180638.IAA03066@gratis.grondar.za>
To: nnd@itfs.nsk.su (Nickolay Dudorov)
cc: current@FreeBSD.ORG
Subject: Re: CVS corruption through cvs-cur.4733.gz 
In-Reply-To: Your message of " Sun, 18 Oct 1998 10:02:30 +0700."  
References: <199810171346.PAA00718@gratis.grondar.za>    
Date: Sun, 18 Oct 1998 08:38:15 +0200
From: Mark Murray 
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 :-)

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