From owner-freebsd-qa Sun Dec 5 4:50:43 1999 Delivered-To: freebsd-qa@freebsd.org Received: from lk.tempest.sk (lk.tempest.sk [195.28.100.47]) by hub.freebsd.org (Postfix) with ESMTP id 1F72715382 for ; Sun, 5 Dec 1999 04:50:31 -0800 (PST) (envelope-from lk@tempest.sk) Received: (from koren@localhost) by lk.tempest.sk (8.9.3/8.9.3) id NAA06686; Sun, 5 Dec 1999 13:50:28 +0100 (CET) (envelope-from koren) Date: Sun, 5 Dec 1999 13:50:28 +0100 (CET) Message-Id: <199912051250.NAA06686@lk.tempest.sk> From: Ludo Koren To: freebsd-qa@freebsd.org Subject: 3.3-19991204-STABLE Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have installed 3.3-19991204-STABLE from releng3.freebsd.org successfully. The following benchmarks completed without problems: bonnie bytebench lmbench nbench netperf netpipe ludo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Thu Dec 9 5:27:57 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id A6FF115359; Thu, 9 Dec 1999 05:27:55 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id IAA52407; Thu, 9 Dec 1999 08:27:49 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912091327.IAA52407@spoon.beta.com> To: freebsd-qa@freebsd.org Cc: jkh@freebsd.org Subject: 12/8 and 12/9 images... Date: Thu, 09 Dec 1999 08:27:49 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Due to the fact that it appears the 12/8 image did not build, you should now be testing with the 12/9 image (which is now available on releng3.freebsd.org). Due to now being a day off, this will be a _3_ day cycle. Extra care should be taken on this one, as obviously something happened that broke the 12/8 snapshot from building. Perhaps Jordan can provide more information to the list ;) -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Sat Dec 11 13: 3:11 1999 Delivered-To: freebsd-qa@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 9ED3815133; Sat, 11 Dec 1999 13:03:09 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id NAA00375; Sat, 11 Dec 1999 13:03:06 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 11 Dec 1999 13:03:06 -0800 (PST) From: Doug White To: "Brian J. McGovern" Cc: freebsd-qa@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: 12/8 and 12/9 images... In-Reply-To: <199912091327.IAA52407@spoon.beta.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Dec 1999, Brian J. McGovern wrote: > Due to the fact that it appears the 12/8 image did not build, you should now > be testing with the 12/9 image (which is now available on releng3.freebsd.org). There are no images on releng3 now. Where did they go? Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Sat Dec 11 13: 6: 2 1999 Delivered-To: freebsd-qa@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id 9348915270 for ; Sat, 11 Dec 1999 13:06:00 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id QAA03742; Sat, 11 Dec 1999 16:08:36 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19991211160450.04c32580@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 11 Dec 1999 16:05:54 -0500 To: Doug White From: Mike Tancsa Subject: Re: 12/8 and 12/9 images... Cc: freebsd-qa@FreeBSD.ORG In-Reply-To: References: <199912091327.IAA52407@spoon.beta.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:03 PM 12/11/99 , Doug White wrote: >On Thu, 9 Dec 1999, Brian J. McGovern wrote: > >> Due to the fact that it appears the 12/8 image did not build, you should now >> be testing with the 12/9 image (which is now available on >releng3.freebsd.org). > >There are no images on releng3 now. Where did they go? Try on ftp://current.freebsd.org:/pub/FreeBSD/snapshots/i386/ISO-IMAGES -rw-r--r-- 1 root 0 212924416 Dec 3 11:41 3.3-19991203-STABLE.iso -rw-r--r-- 1 root 0 183793664 Dec 4 11:45 3.3-19991204-STABLE.iso -rw-r--r-- 1 root 0 212967424 Dec 5 11:43 3.3-19991205-STABLE.iso -rw-r--r-- 1 root 0 212987904 Dec 6 11:40 3.3-19991206-STABLE.iso -rw-r--r-- 1 root 0 213008384 Dec 7 12:03 3.3-19991207-STABLE.iso -rw-r--r-- 1 root 0 216530944 Dec 9 12:05 3.3-19991209-STABLE.iso -rw-r--r-- 1 root 0 216569856 Dec 10 12:07 3.3-19991210-STABLE.iso -rw-r--r-- 1 root 0 216619008 Dec 11 12:15 3.3-19991211-STABLE.iso -rw-r--r-- 1 root 0 904 Dec 11 12:15 CHECKSUM.MD5 ---Mike ********************************************************************** Mike Tancsa * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 519 651 3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Sat Dec 11 13:41:13 1999 Delivered-To: freebsd-qa@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0D07414E3C; Sat, 11 Dec 1999 13:41:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA91898; Sat, 11 Dec 1999 13:41:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Doug White Cc: "Brian J. McGovern" , freebsd-qa@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: 12/8 and 12/9 images... In-reply-to: Your message of "Sat, 11 Dec 1999 13:03:06 PST." Date: Sat, 11 Dec 1999 13:41:23 -0800 Message-ID: <91894.944948483@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There are no images on releng3 now. Where did they go? Hurm? Same place they've always been! ftp://releng3.freebsd.org/pub/FreeBSD/snapshots/i386/ISO-IMAGES/ [current.freebsd.org and releng3.freebsd.org actually share a common ftp area via NFS, so either host is good for the same bits] - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Sun Dec 12 11: 3:54 1999 Delivered-To: freebsd-qa@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 5FE7014D4E; Sun, 12 Dec 1999 11:03:53 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id LAA90414; Sun, 12 Dec 1999 11:03:49 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sun, 12 Dec 1999 11:03:49 -0800 (PST) From: Doug White To: "Jordan K. Hubbard" Cc: "Brian J. McGovern" , freebsd-qa@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: 12/8 and 12/9 images... In-Reply-To: <91894.944948483@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Dec 1999, Jordan K. Hubbard wrote: > > There are no images on releng3 now. Where did they go? > > Hurm? Same place they've always been! > > ftp://releng3.freebsd.org/pub/FreeBSD/snapshots/i386/ISO-IMAGES/ > > [current.freebsd.org and releng3.freebsd.org actually share a common > ftp area via NFS, so either host is good for the same bits] Sorry, looking in the wrong place. The /pub/FreeBSD/ISO/ directory should go away. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 13 10: 5:58 1999 Delivered-To: freebsd-qa@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id B9BF015458; Mon, 13 Dec 1999 10:05:56 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id KAA08635; Mon, 13 Dec 1999 10:05:56 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 13 Dec 1999 10:05:56 -0800 (PST) From: Doug White To: "David E. O'Brien" Cc: freebsd-qa@FreeBSD.org Subject: Re: cvs commit: src/contrib/isc-dhcp/client/scripts freebsd In-Reply-To: <199912120117.RAA01926@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Dec 1999, David E. O'Brien wrote: > obrien 1999/12/11 17:17:31 PST > > Modified files: (Branch: RELENG_3) > contrib/isc-dhcp/client/scripts freebsd > Log: > MFC: rev 1.8 (don't add localhost routes). Everyone, bang on this change real hard. It's a last-minute and was broken logic that was pulled from 3.3 at the last second. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 13 10:28:19 1999 Delivered-To: freebsd-qa@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 76B4715170 for ; Mon, 13 Dec 1999 10:28:10 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA06829; Mon, 13 Dec 1999 10:28:09 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA32573; Mon, 13 Dec 1999 10:28:10 -0800 (PST) (envelope-from obrien) Date: Mon, 13 Dec 1999 10:28:09 -0800 From: "David O'Brien" To: Doug White Cc: freebsd-qa@FreeBSD.org Subject: Re: cvs commit: src/contrib/isc-dhcp/client/scripts freebsd Message-ID: <19991213102809.G5414@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <199912120117.RAA01926@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dwhite@resnet.uoregon.edu on Mon, Dec 13, 1999 at 10:05:56AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Modified files: (Branch: RELENG_3) > > contrib/isc-dhcp/client/scripts freebsd > > Log: > > MFC: rev 1.8 (don't add localhost routes). > > Everyone, bang on this change real hard. It's a last-minute and was > broken logic that was pulled from 3.3 at the last second. I would agree. I would have prefered to not do it, but there were 4 PRs on it. The things to test: network_interfaces="auto" ifconfig_fxp0="DHCP" then network_interfaces="lo0 fxp0" ifconfig_fxp0="DHCP" then network_interfaces="fxp0 lo0" ifconfig_fxp0="DHCP" then network_interfaces="fxp0" ifconfig_fxp0="DHCP" -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 13 10:55: 0 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 825AD14D86; Mon, 13 Dec 1999 10:54:57 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id NAA68275; Mon, 13 Dec 1999 13:54:47 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912131854.NAA68275@spoon.beta.com> To: Doug White Cc: "David E. O'Brien" , freebsd-qa@FreeBSD.ORG Subject: Re: cvs commit: src/contrib/isc-dhcp/client/scripts freebsd In-reply-to: Your message of "Mon, 13 Dec 1999 10:05:56 PST." Date: Mon, 13 Dec 1999 13:54:47 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would this have made it in tot he 12/12 image? This is the last "formal test" image. If we need to grab something later, it'd be nice to know before we're out of time (the 15th)... -Brian > On Sat, 11 Dec 1999, David E. O'Brien wrote: > > > obrien 1999/12/11 17:17:31 PST > > > > Modified files: (Branch: RELENG_3) > > contrib/isc-dhcp/client/scripts freebsd > > Log: > > MFC: rev 1.8 (don't add localhost routes). > > Everyone, bang on this change real hard. It's a last-minute and was > broken logic that was pulled from 3.3 at the last second. > > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-qa" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 13 13:50:36 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 7CDFB151E4 for ; Mon, 13 Dec 1999 13:50:33 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id QAA68793; Mon, 13 Dec 1999 16:50:30 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912132150.QAA68793@spoon.beta.com> To: obrien@NUXI.com Cc: freebsd-qa@freebsd.org Subject: Re: cvs commit: src/contrib/isc-dhcp/client/scripts freebsd Date: Mon, 13 Dec 1999 16:50:30 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Based on 3.3-19991212-STABLE, I got.... > > > Modified files: (Branch: RELENG_3) > > > contrib/isc-dhcp/client/scripts freebsd > > > Log: > > > MFC: rev 1.8 (don't add localhost routes). > > > > Everyone, bang on this change real hard. It's a last-minute and was > > broken logic that was pulled from 3.3 at the last second. > > I would agree. I would have prefered to not do it, but there were 4 PRs > on it. The things to test: > > network_interfaces="auto" > ifconfig_fxp0="DHCP" This is as sysinstall set it up when I installed w/DHCP to configure the interface. lo0 and fxp0 configured fine. > then > > network_interfaces="lo0 fxp0" > ifconfig_fxp0="DHCP" This also configured lo0 and fxp0 correctly. > then > > network_interfaces="fxp0 lo0" > ifconfig_fxp0="DHCP" > This worked. > then > > network_interfaces="fxp0" > ifconfig_fxp0="DHCP" > lo0 did not configure here. > > -- > -- David (obrien@NUXI.com) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-qa" in the body of the message -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 13 17:56:24 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id B7CB915260 for ; Mon, 13 Dec 1999 17:56:18 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id UAA69328; Mon, 13 Dec 1999 20:56:03 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912140156.UAA69328@spoon.beta.com> To: "Jordan K. Hubbard" Cc: freebsd-qa@freebsd.org Subject: Re: Linux emulation causes sysinstall weirdness... 19991212-STABLE In-reply-to: Your message of "Mon, 13 Dec 1999 13:47:49 PST." <13133.945121669@zippy.cdrom.com> Date: Mon, 13 Dec 1999 20:56:03 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have some more info. It looks like its a screen redraw issue. When selected, it gives the message that its installing, and it checks the check box (which you can see on the message screen). At that point, the underlying menu is active, but you can't see it unless you start moving the cursor around with the arrow keys. My "success" at hitting a couple of keys making it come back was due to hitting the "Enter" key, and having a parent screen redraw. -Brian > That sounds very weird - I'll see if I can reproduce it! > > - Jordan > > > Just a heads up . Different than prior versions, with 3.3-19991212-STABLE, > > enabling Linux emulation _after_ installing the package no longer causes i t > > to generate errors because the package has already been installed. Instead , > > it seems to now hang out in limbo until you hit a few keys on the > > keyboard (the machine didn't seem to be doing anything, and the debug scre en > > didn't show anything interesting). > > > > I'll validate this behavior when I get home tonight (1-2 hours), and let y ou > > know if its consistent. > > -Brian > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 13 19:19:56 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 0CF2315304 for ; Mon, 13 Dec 1999 19:19:53 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id WAA69561 for ; Mon, 13 Dec 1999 22:19:52 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912140319.WAA69561@spoon.beta.com> To: freebsd-qa@freebsd.org Subject: 4.0-RELEASE in January? Date: Mon, 13 Dec 1999 22:19:52 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There has been talk of 4.0-RELEASE dates on -current. I currently have an email in to Jordan to try to determine an exact date, so that we can schedule testing appropriately. Since 4.0 will be a "new product", I'd like to start testing (albiet probably lightly with the holidays) as soon as 3.4 ships. We should make use of the extra time to really shake the OS down, and see if we can turn 4.0 in to a fairly stable release. Anyhow, I will let everyone know what the target dates are as soon as I hear. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 13 22:29:51 1999 Delivered-To: freebsd-qa@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 78715151BB for ; Mon, 13 Dec 1999 22:29:48 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA01979; Mon, 13 Dec 1999 22:30:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Brian J. McGovern" Cc: freebsd-qa@freebsd.org Subject: Re: Linux emulation causes sysinstall weirdness... 19991212-STABLE In-reply-to: Your message of "Mon, 13 Dec 1999 20:56:03 EST." <199912140156.UAA69328@spoon.beta.com> Date: Mon, 13 Dec 1999 22:30:10 -0800 Message-ID: <1975.945153010@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm. Well, I've just changed this utterly in -current, but I wasn't going to back-port it to -stable until I had a snapshot build done. Hmmm. I know, I'll insert the changes just into tonite's snapshot without actually committing them yet. We may have to push the release date forward 24-48 hours, I'm thinking at this point. But don't tell anyone yet, let them continue to work as if the deadline was 2 days from now. :-) - Jordan > I have some more info. It looks like its a screen redraw issue. When selected , > it gives the message that its installing, and it checks the check box (which > you can see on the message screen). At that point, the underlying menu is > active, but you can't see it unless you start moving the cursor around with > the arrow keys. My "success" at hitting a couple of keys making it come back > was due to hitting the "Enter" key, and having a parent screen redraw. > -Brian > > > > That sounds very weird - I'll see if I can reproduce it! > > > > - Jordan > > > > > Just a heads up . Different than prior versions, with 3.3-19991212-STABL E, > > > enabling Linux emulation _after_ installing the package no longer causes i > t > > > to generate errors because the package has already been installed. Inste ad > , > > > it seems to now hang out in limbo until you hit a few keys on the > > > keyboard (the machine didn't seem to be doing anything, and the debug sc re > en > > > didn't show anything interesting). > > > > > > I'll validate this behavior when I get home tonight (1-2 hours), and let y > ou > > > know if its consistent. > > > -Brian > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Tue Dec 14 7: 9:15 1999 Delivered-To: freebsd-qa@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id A94C7151F6 for ; Tue, 14 Dec 1999 07:09:07 -0800 (PST) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id KAA01561 for ; Tue, 14 Dec 1999 10:09:00 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19991214100734.00a78440@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 14 Dec 1999 10:07:34 -0500 To: freebsd-qa@FreeBSD.ORG From: Mike Tancsa Subject: Re: Linux emulation causes sysinstall weirdness... 19991212-STABLE In-Reply-To: <1975.945153010@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:30 PM 12/13/99 -0800, Jordan K. Hubbard wrote: >Hmmm. Well, I've just changed this utterly in -current, but I wasn't >going to back-port it to -stable until I had a snapshot build done. >Hmmm. I know, I'll insert the changes just into tonite's snapshot >without actually committing them yet. We may have to push the release >date forward 24-48 hours, I'm thinking at this point. But don't >tell anyone yet, let them continue to work as if the deadline was 2 >days from now. :-) I have been tracking STABLE via cvsup most every day now, but have only cut 2 CDs. When will be the "OK, make sure this ISO image works as planned" image ? I will allocate more time to try and test that a little more closely. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Tue Dec 14 9:29:47 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 523D31508D for ; Tue, 14 Dec 1999 09:29:45 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id MAA71662; Tue, 14 Dec 1999 12:29:33 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912141729.MAA71662@spoon.beta.com> To: Mike Tancsa Cc: freebsd-qa@FreeBSD.ORG, mcgovern@spoon.beta.com Subject: Re: Linux emulation causes sysinstall weirdness... 19991212-STABLE In-reply-to: Your message of "Tue, 14 Dec 1999 10:07:34 EST." <3.0.5.32.19991214100734.00a78440@staff.sentex.ca> Date: Tue, 14 Dec 1999 12:29:32 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A large number of us (including myself) _have_ already been running off of the ISO images. I suggested to Jordan that he start including the full package set at RELEASE + 4 (which should have been the 12/12 snapshot), so we could test what would be the actual release CD. So far, this hasn't happened, but I suspect that its more that Jordan is under a lot of pressure to fix things, rather than the release cycle is going to get stretched. Therefore, if you really want to bang on the ISO images, the time to do so is "now". -Brian > At 10:30 PM 12/13/99 -0800, Jordan K. Hubbard wrote: > >Hmmm. Well, I've just changed this utterly in -current, but I wasn't > >going to back-port it to -stable until I had a snapshot build done. > >Hmmm. I know, I'll insert the changes just into tonite's snapshot > >without actually committing them yet. We may have to push the release > >date forward 24-48 hours, I'm thinking at this point. But don't > >tell anyone yet, let them continue to work as if the deadline was 2 > >days from now. :-) > > I have been tracking STABLE via cvsup most every day now, but have only cut > 2 CDs. When will be the "OK, make sure this ISO image works as planned" > image ? I will allocate more time to try and test that a little more closely . > > > ---Mike > ------------------------------------------------------------------------ > Mike Tancsa, tel +1 519 651 3400 > Network Administrator, mike@sentex.net > Sentex Communications www.sentex.net > Cambridge, Ontario Canada > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-qa" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Tue Dec 14 9:32:28 1999 Delivered-To: freebsd-qa@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 4358D14D2A for ; Tue, 14 Dec 1999 09:32:25 -0800 (PST) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id MAA22577 for ; Tue, 14 Dec 1999 12:32:23 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19991214123051.01741830@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 14 Dec 1999 12:30:51 -0500 To: freebsd-qa@FreeBSD.ORG From: Mike Tancsa Subject: Re: Linux emulation causes sysinstall weirdness... 19991212-STABLE In-Reply-To: <199912141729.MAA71662@spoon.beta.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:29 PM 12/14/99 -0500, Brian J. McGovern wrote: >Therefore, if you really want to bang on the ISO images, the time to do so is >"now". Super, I will burn and test the snapshot. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Wed Dec 15 12: 9:39 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 73123155A3; Wed, 15 Dec 1999 12:07:27 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id PAA75368; Wed, 15 Dec 1999 15:07:23 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912152007.PAA75368@spoon.beta.com> To: jkh@freebsd.org Cc: freebsd-qa@freebsd.org Subject: sysinstall in 3.2-19991215-STABLE... Date: Wed, 15 Dec 1999 15:07:23 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking for a nice way to word this, but the sysinstall included in today's image (which I believe is from 4.0), is kaka. After one pass, I have the following complaints: - Sig 11 was generated while selecting Linux emulation after already having installed it as a package. I don't know if its one affecting the other, or whether picking the Linux emulator off the Startup menu will always cause a sig 11 (I'll do more testing tonight). - Use of Return and Space bar appears inconsistent and counter-intuituive.In the "old" version, space would select, or move you down a level, ENTER would exit and move up a level. The new method is a nightmare mix. - Linux_glide (the package) still generates an error message. This screws up the underlying (Post Configuration) menu screen. This causes problems after the packages are installed, as the menu is now difficult to use. - As an aside to the above, the package-install screen goes back to the post-install screen when you select "INSTALL". Messages about package installs are now tiled OVER the post configuration window (used to be a blank screen). - Menus do not consistently have an "EXIT" option to move upwards. This helps the confusion about whether to use the space bar, or the ENTER key. It also brings up user concern as to what will happen if they hit either (select it? Or exit?) - Highlighting of first character in menus is inconsistent. This makes a number of menus look ugly (this is cosmetic). Thats it for now. I'll shoot up comments as I get some more time on it. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Thu Dec 16 12:56: 6 1999 Delivered-To: freebsd-qa@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 46D47156AE; Thu, 16 Dec 1999 12:56:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA63287; Thu, 16 Dec 1999 12:55:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Brian J. McGovern" Cc: jkh@freebsd.org, freebsd-qa@freebsd.org Subject: Re: sysinstall in 3.2-19991215-STABLE... In-reply-to: Your message of "Wed, 15 Dec 1999 15:07:23 EST." <199912152007.PAA75368@spoon.beta.com> Date: Thu, 16 Dec 1999 12:55:43 -0800 Message-ID: <63283.945377743@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - Sig 11 was generated while selecting Linux emulation after already > having installed it as a package. I don't know if its one affecting > the other, or whether picking the Linux emulator off the Startup menu > will always cause a sig 11 (I'll do more testing tonight). Very odd, but I'll certainly look into this. Odd because nothing has been changed in this area of code. > - Use of Return and Space bar appears inconsistent and > counter-intuituive.In the "old" version, space would select, or move > you down a level, ENTER would exit and move up a level. The new method > is a nightmare mix. Hmmm, really? Much of what I did was an attempt to *homogenize* the menu behavior. It was quite inconsistent before and I even fixed a bug in libdialog which prevented spaces from working in certain circumstances. Can you be more specific about when and where it transitions from being reasonable to being yuck? > - Linux_glide (the package) still generates an error message. This > screws up the underlying (Post Configuration) menu screen. This > causes problems after the packages are installed, as the menu is now > difficult to use. Urk, really? How odd - it's not supposed to have any access at all to VTY0! Again, can you give me a reproduction sequence? Just a simple matter of installing it off the package menu? > - As an aside to the above, the package-install screen goes back to > the post-install screen when you select "INSTALL". Messages about > package installs are now tiled OVER the post configuration window (used > to be a blank screen). I can add a screen clear here, no problem. > - Menus do not consistently have an "EXIT" option to move upwards. This Actually, they're more consistent now in that respect. Many items with SELECTION_RETURNS set (which means that any selection leaves the menu) had Exit items and those were essentially redundant. Likewise Exit items in checklist or radiolist menus - not very useful. If you have specific examples of stuff that's hosed, please let me know though. > - Highlighting of first character in menus is inconsistent. This makes > a number of menus look ugly (this is cosmetic). Actually, it's much more consistent now. We had duplicate accelerators for just about everything before and accelerators weren't even useful as a consequence. Now the long menus use accelerators to get to the first entry of each alphabet-sorted grouping. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Thu Dec 16 19:36:43 1999 Delivered-To: freebsd-qa@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id B8E251522B for ; Thu, 16 Dec 1999 19:36:40 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991217033434.URRG15480.mail.rdc3.on.home.com@tristan.net> for ; Thu, 16 Dec 1999 19:34:34 -0800 Content-Length: 3076 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 16 Dec 1999 22:33:55 -0500 (EST) From: Colin To: freebsd-qa@FreeBSD.ORG Subject: Kernel Panic when VESA support compiled in Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I compiled in VESA support to use a better splash.bmp, and imagine my surprise when I saw a kernel panic. The applicable information is as follows: changing root device to wd0s1a Fatal trap 18: integer divide fault while in kernel mode * * * code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=8 current process = 5(init) interupt mask = net tty bio cam trap number = 18 panic: integer divide fault uname -a ************************************************************************** FreeBSD tristan.net 3.4-RC FreeBSD 3.4-RC #3: Thu Dec 16 21:47:26 EST 1999 root@tristan.net:/usr/src/sys/compile/MARVIN i386 dmesg ****************************************************************************** FreeBSD 3.4-RC #3: Thu Dec 16 21:47:26 EST 1999 root@tristan.net:/usr/src/sys/compile/MARVIN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 116611094 Hz CPU: AMD-K5(tm) Processor (116.61-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x524 Stepping = 4 Features=0x21bf AMD Features=0x0 real memory = 67108864 (65536K bytes) avail memory = 62480384 (61016K bytes) Preloaded elf kernel "kernel" at 0xc02a7000. Preloaded elf module "splash_bmp.ko" at 0xc02a709c. Preloaded splash_image_data "/boot/splash.bmp" at 0xc02a7140. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ed1: rev 0x00 int a irq 11 on pci0.10.0 ed1: address 00:00:b4:59:37:bd, type NE2000 (16 bit) vga0: rev 0x48 on pci0.11.0 Probing for PnP devices: CSN 1 Vendor ID: CTL0070 [0x70008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] Probing for devices on the ISA bus: ...etc... (only my 2 IDE disk drives found from here) The most important bit is that the video card is a Mach 64-VT, 2 Meg RAM, and this happens with 320X200 and 640X480 bitmaps for the splash. To confirm, I rebuilt my kernel without the 2 lines: #options "VM86" #options "VESA" (no other changes) and the panic stopped, but the splash works great. Tried rebooting from the previos kernel (as kernel.old...sometimes it's good to keep a known problem kernel ;)), it didn't load the splash but it still panicked. I don't see this as a release stopper, but it's a problem. Are there any known problems with Mach 64's? Or VESA support in general? Let me know if any further information would help. I plan to root through the source for VESA support over the next day or so, maybe I can see something. Cheers, Colin ---------------------------------- E-Mail: Colin Date: 16-Dec-1999 Time: 22:09:18 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Fri Dec 17 6:34:30 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id B14871573A for ; Fri, 17 Dec 1999 06:34:27 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id JAA89085; Fri, 17 Dec 1999 09:33:58 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912171433.JAA89085@spoon.beta.com> To: Colin Cc: freebsd-qa@FreeBSD.ORG Subject: Re: Kernel Panic when VESA support compiled in In-reply-to: Your message of "Thu, 16 Dec 1999 22:33:55 EST." Date: Fri, 17 Dec 1999 09:33:58 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Next day or so" might be too long. Jordan is chomping at the bit to get 3.4 out :) Try toggling just the VESA part in and out, and see if its the VESA code, or the VM86 code that is causing the panic. -Brian > I compiled in VESA support to use a better splash.bmp, and imagine my > surprise when I saw a kernel panic. The applicable information is as follow s: > > changing root device to wd0s1a > > > Fatal trap 18: integer divide fault while in kernel mode > * > * > * > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL=8 > current process = 5(init) > interupt mask = net tty bio cam > trap number = 18 > panic: integer divide fault > > uname -a > ************************************************************************** > FreeBSD tristan.net 3.4-RC FreeBSD 3.4-RC #3: Thu Dec 16 21:47:26 EST 1999 > root@tristan.net:/usr/src/sys/compile/MARVIN i386 > > dmesg > **************************************************************************** ** > FreeBSD 3.4-RC #3: Thu Dec 16 21:47:26 EST 1999 > root@tristan.net:/usr/src/sys/compile/MARVIN > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 116611094 Hz > CPU: AMD-K5(tm) Processor (116.61-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x524 Stepping = 4 > Features=0x21bf > AMD Features=0x0 > real memory = 67108864 (65536K bytes) > avail memory = 62480384 (61016K bytes) > Preloaded elf kernel "kernel" at 0xc02a7000. > Preloaded elf module "splash_bmp.ko" at 0xc02a709c. > Preloaded splash_image_data "/boot/splash.bmp" at 0xc02a7140. > Probing for devices on PCI bus 0: > chip0: rev 0x02 on pci0.0.0 > chip1: rev 0x01 on pci0.7.0 > ide_pci0: rev 0x00 on pci0.7.1 > ed1: rev 0x00 int a irq 11 on pci0.10.0 > ed1: address 00:00:b4:59:37:bd, type NE2000 (16 bit) > vga0: rev 0x48 on pci0.11.0 > Probing for PnP devices: > CSN 1 Vendor ID: CTL0070 [0x70008c0e] Serial 0xffffffff Comp ID: PNPb02f > [0x2fb0d041] > Probing for devices on the ISA bus: > ...etc... > (only my 2 IDE disk drives found from here) > > The most important bit is that the video card is a Mach 64-VT, 2 Meg RA M, > and this happens with 320X200 and 640X480 bitmaps for the splash. To > confirm, I rebuilt my kernel without the 2 lines: > > #options "VM86" > #options "VESA" > > (no other changes) and the panic stopped, but the splash works great. Tried > rebooting from the previos kernel (as kernel.old...sometimes it's good to ke ep > a known problem kernel ;)), it didn't load the splash but it still panicked. > I don't see this as a release stopper, but it's a problem. Are there a ny > known problems with Mach 64's? Or VESA support in general? > Let me know if any further information would help. I plan to root thro ugh > the source for VESA support over the next day or so, maybe I can see somethi ng. > > Cheers, > Colin > > ---------------------------------- > E-Mail: Colin > Date: 16-Dec-1999 > Time: 22:09:18 > > This message was sent by XFMail > ---------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-qa" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Fri Dec 17 15: 1:57 1999 Delivered-To: freebsd-qa@freebsd.org Received: from pinenut.nosc.mil (pinenut.nosc.mil [198.253.4.217]) by hub.freebsd.org (Postfix) with ESMTP id 3E90D14A24; Fri, 17 Dec 1999 15:01:54 -0800 (PST) (envelope-from syed@pinenut.nosc.mil) Received: by pinenut.nosc.mil (Postfix, from userid 1001) id 2216618F; Fri, 17 Dec 1999 15:01:07 -0800 (PST) Subject: TEST of 3.3-19991215-STABLE To: freebsd-qa@freebsd.org Date: Fri, 17 Dec 1999 15:01:07 -0800 (PST) Cc: jkh@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <19991217230107.2216618F@pinenut.nosc.mil> From: syed@pinenut.nosc.mil (basit Syed) Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Report on 3.3-19991215-STABLE 0. Install via ftp and using DHCP. if an error is made in the URL specification the system shuts down the interface and won't resume. i had to abort the install and restart from kern.flp. 1. Installing via ftp: system installs properly and then one package is added ( various packages, tcsh, mpack ) which is successful. Now you are back at the FreeBSD Configuration Menu. if you select Packages again to add another package, the system generates an immediate SIG 11. I then rebooted the newly installed system off of the hard disk and re-entered Configuration Menu. Again i added a package (mpack) which installed properly. Now i'm back at the Config menu. i select Packages again, i get an immediate SIG 11 (sysinstall core dumped). The system stays up, i have to logout and then log back in because typed characters were not being echoed. 2. Progress screen for extracting bin, compat22, dict, doc, man displayed properly but for the other operations (making newfs, Remaking all devices, etc.) the screen would go blank (all blue) until the function being performed completed. 3. /stand/sysinstall Main Menu: 991212 had offset single alphanumeric selectors but the 991515 has done away with them. CUSTOM entry is offset one character and the first letter is not highlighted. This causes the SPACE BAR to select this entry. same effect. 4. Options Editor: I modified all entries and then tried to RESET using the USE DEFAULTS option. NFS SLOW, DEBUGGING, NO WARNINGS, YES TO ALL, were not reset. ESCAPE key as well as Q take you out of the menu. 5. FDISK Partition Editor: PType not defined. 6. Choose Installation Media Menu: last entry Options needs to be fixed. 7. Choose Distributions Menu: If X-Developer is selected then entries 1-6 are displayed as selected, ie. an X. SPACE BAR does not function as a toggle. 8. FreeBSD FTP distribution site Menu: All entries are not consistent. 9. XFree86 3.3.5 Distribution : The Reset entry should be [] Reset. XFree86 3.3.5 Distribution basic, server, fonts menus: The All and Reset entries should be [] All and [] Reset A. FreeBSD Configuration Menu: The display is messed up a bit - the normal menu is superimposed on a left over blue border. SPACE BAR returns you to Distributions entry from any other entry. Only the last option Exit has an highlighted offset alphanumeric (X) associated with it. B. System Console Keymap menu: Belgian, Danish, Estonian, etc. have the first letter highlighted and are offset one position while others are not. C. User and Group Management Menu: SPACE BAR functions the same as ENTER. D. Configure Your Mouse Menu: SPACE BAR and ENTER are equal. E. Network Services Menu: INTERFACES MENU is high lighted, ENTER takes you back one menu screen, SPACE BAR takes you to the proper place. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Fri Dec 17 15:10:23 1999 Delivered-To: freebsd-qa@freebsd.org Received: from pinenut.nosc.mil (pinenut.nosc.mil [198.253.4.217]) by hub.freebsd.org (Postfix) with ESMTP id 5000B157E8 for ; Fri, 17 Dec 1999 15:10:18 -0800 (PST) (envelope-from syed@pinenut.nosc.mil) Received: by pinenut.nosc.mil (Postfix, from userid 1001) id 7A09218F; Fri, 17 Dec 1999 15:09:31 -0800 (PST) Subject: Report on 3.3-19991212-STABLE To: freebsd-qa@freebsd.org Date: Fri, 17 Dec 1999 15:09:31 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <19991217230931.7A09218F@pinenut.nosc.mil> From: syed@pinenut.nosc.mil (basit Syed) Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1. i did a buildworld over NFSv2 without any problems. i also had 6 different sessions of xemacs and netscape and bytebench running at the same time to try to load down the machine. i was also using the machine to read stuff on an NT machine via VNCviewer. 2. if anyone wants to suggest some test to run let me know. --b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Fri Dec 17 16:20:48 1999 Delivered-To: freebsd-qa@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 6D33E15328 for ; Fri, 17 Dec 1999 16:20:46 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991218001839.BYXC15480.mail.rdc3.on.home.com@tristan.net>; Fri, 17 Dec 1999 16:18:39 -0800 Content-Length: 980 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912171433.JAA89085@spoon.beta.com> Date: Fri, 17 Dec 1999 19:18:00 -0500 (EST) From: Colin To: "Brian J. McGovern" Subject: Re: Kernel Panic when VESA support compiled in Cc: freebsd-qa@FreeBSD.ORG Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm doing this as fast as I can, unfortunately work keeps interfering with the important things in my life ;) I turned on VM86, recompiled and it works. By elimination, the problem is in VESA. From LINT, I surmise that VM86 is required for VESA so I can't really test that...or can I? I also need a few hours to make sure it's not something I'm doing and is in fact a bug. That's why I haven't cross posted to -HACKERS or -STABLE yet. That will happen later tonight, probably. At this late stage, a note in errata would probably be appropriate, since from the web resources I've seen, this obviously works on at least some controllers ;) Just for information, there are already announcements about 3.4-RELEASE on daily.daemonnews.org. I guess some people are getting anxious ;) ---------------------------------- E-Mail: Colin Date: 17-Dec-1999 Time: 19:05:21 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Fri Dec 17 19: 7:14 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 7864A14CA6 for ; Fri, 17 Dec 1999 19:07:12 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id WAA01916; Fri, 17 Dec 1999 22:07:08 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912180307.WAA01916@spoon.beta.com> To: Colin Cc: "Brian J. McGovern" , freebsd-qa@FreeBSD.ORG, mcgovern@spoon.beta.com Subject: Re: Kernel Panic when VESA support compiled in In-reply-to: Your message of "Fri, 17 Dec 1999 19:18:00 EST." Date: Fri, 17 Dec 1999 22:07:08 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.4 was supposed to be "ready" on the 15th ;) Thats probably why you're hearing about it. However, we still have some big problems to get through with... As to VESA, I compiled it in here with no problems. The only thing I did with it, however, was to switch some text modes on the console. Perhaps a couple of others in the group and try it, and see if its just your hardware, or whether we can duplicate it. -Brian > I'm doing this as fast as I can, unfortunately work keeps interfering w ith > the important things in my life ;) > I turned on VM86, recompiled and it works. By elimination, the problem is > in VESA. From LINT, I surmise that VM86 is required for VESA so I can't rea lly > test that...or can I? I also need a few hours to make sure it's not somethi ng > I'm doing and is in fact a bug. That's why I haven't cross posted to -HACKE RS > or -STABLE yet. That will happen later tonight, probably. > At this late stage, a note in errata would probably be appropriate, sin ce > from the web resources I've seen, this obviously works on at least some > controllers ;) > > Just for information, there are already announcements about 3.4-RELEASE on > daily.daemonnews.org. I guess some people are getting anxious ;) > > ---------------------------------- > E-Mail: Colin > Date: 17-Dec-1999 > Time: 19:05:21 > > This message was sent by XFMail > ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Fri Dec 17 19:12:53 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id CC8F214D0C; Fri, 17 Dec 1999 19:12:51 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id WAA01951; Fri, 17 Dec 1999 22:12:49 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912180312.WAA01951@spoon.beta.com> To: syed@pinenut.nosc.mil (basit Syed) Cc: freebsd-qa@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: TEST of 3.3-19991215-STABLE In-reply-to: Your message of "Fri, 17 Dec 1999 15:01:07 PST." <19991217230107.2216618F@pinenut.nosc.mil> Date: Fri, 17 Dec 1999 22:12:49 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Report on 3.3-19991215-STABLE > > 0. Install via ftp and using DHCP. if an error is made in the URL > specification the system shuts down the interface and won't > resume. i had to abort the install and restart from kern.flp. > 1. Installing via ftp: system installs properly and then one package ... [snip] You caught more than I did. Shame on me :) Here are some of the things I found that i don't think you listed (from 3.2-19991217-STABLE)... 1.) The screen doesn't clear around package installs. You see the Post-install configuration menu behind it. Its only distracting, but... 2.) linux_glide still generates an error. This throws the display off by two lines. 3.) When the package install is complete, the configuration menu is not redrawn. Depending on the mess you create with the package install (see #1 and #2), the underlying menu is normally useless. You need to scroll all the way down and back up to get all of the menu items viewable again. The borders and headers can not be redrawn. 4.) The system catches a sig 11, apparently any time the user tries to install a package a second time - this is particularly noticable if you install the Linux emulator from the packages menu, then select it from the Startup menu. 5.) Menus do not redraw after manually configuring the ethernet interface. This is similar to #3. 6.) The X window (top-level) menu doesn't behave similar to the others. If following the "custom Install", Enter gets used a lot. In this menu, exit does not leave the menu. You must scroll to the bottom and select Exit. Although this is cosmetic, its a PITA. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Sat Dec 18 8: 5: 7 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 3397214E21; Sat, 18 Dec 1999 08:05:05 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id LAA06442; Sat, 18 Dec 1999 11:05:02 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912181605.LAA06442@spoon.beta.com> To: syed@pinenut.nosc.mil (basit Syed) Cc: freebsd-qa@freebsd.org, jkh@freebsd.org Subject: Re: which version to test (was: Re: TEST of 3.3-19991215-STABLE) In-reply-to: Your message of "Sat, 18 Dec 1999 06:57:54 PST." <19991218145754.68028C8@pinenut.nosc.mil> Date: Sat, 18 Dec 1999 11:05:02 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At this point, I think Jordan is in a mad rush to get 3.4 stabilized for shipping. Since we're 3 days behind right now, I'm trying to track the daily snaps as much as possible to keep up with the most recent code so we know if we still have a problem or not. On certain days when the build doesn't seem to make it (like today), I'll spend more time with the OS itself (rather than just sysinstall), and try to make sure nothing [major] broke since the last time I could play with it. Given that the OS itself has done fairly well, and sysinstall seems to have a slew of new bugs that occured during the release cycle, I'm really trying to concentrate there.... So, to answer your question, test what you can. Some of us should probably concentrate on sysinstall issues, and others should continue 'deep testing', where they actually make it through the install, and look at the OS. I'm hoping to finally get my second test machine running today, so I can do both. -Brian > > > > > Report on 3.3-19991215-STABLE > > > > > > 0. Install via ftp and using DHCP. if an error is made in the URL > > > specification the system shuts down the interface and won't > > > resume. i had to abort the install and restart from kern.flp. > > > 1. Installing via ftp: system installs properly and then one package > > > > ... > > [snip] > > > > You caught more than I did. Shame on me :) > > > > Here are some of the things I found that i don't think you listed (from > > 3.2-19991217-STABLE)... > > ^^^^^^^^^^^^^^^ > [snip] > > what should we be currently testing, 3.3-19991217-STABLE? > > --b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Sun Dec 19 20:53:48 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 1CCCA14CC3; Sun, 19 Dec 1999 20:53:47 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id XAA11477; Sun, 19 Dec 1999 23:53:46 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912200453.XAA11477@spoon.beta.com> To: jkh@freebsd.org Cc: freebsd-qa@freebsd.org Subject: 3.4-19991219-STABLE Date: Sun, 19 Dec 1999 23:53:46 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG New problems: - Option screen, when selected, does not appear. Typical keyboard functions, such as "q" and arrows appear to work, and some help text is displayed as [apparently] the fields change. However, the screen itself is never fully/correctly drawn. - I received an immediate sig 11 when selecting "Custom" for distributions I'd like to install. It appears that selecting one of the "pre canned" distributions works better (I selected 'User'). I'm now working on packages, but due to the relatively slow link I have here, I probably won't have results until morning. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 20 1:11: 6 1999 Delivered-To: freebsd-qa@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2F3391528C; Mon, 20 Dec 1999 01:11:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA45825; Mon, 20 Dec 1999 01:10:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Brian J. McGovern" Cc: jkh@freebsd.org, freebsd-qa@freebsd.org Subject: Re: 3.4-19991219-STABLE In-reply-to: Your message of "Sun, 19 Dec 1999 23:53:46 EST." <199912200453.XAA11477@spoon.beta.com> Date: Mon, 20 Dec 1999 01:10:29 -0800 Message-ID: <45821.945681029@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - Option screen, when selected, does not appear. Typical keyboard > functions, such as "q" and arrows appear to work, and some help text is > displayed as [apparently] the fields change. However, the screen itself is > never fully/correctly drawn. Fixed today, thanks. See commit messages from this morning. > - I received an immediate sig 11 when selecting "Custom" for > distributions I'd like to install. Also already fixed. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 20 8:44:31 1999 Delivered-To: freebsd-qa@freebsd.org Received: from pinenut.nosc.mil (pinenut.nosc.mil [198.253.4.217]) by hub.freebsd.org (Postfix) with ESMTP id 704A7152F1 for ; Mon, 20 Dec 1999 08:44:30 -0800 (PST) (envelope-from syed@pinenut.nosc.mil) Received: by pinenut.nosc.mil (Postfix, from userid 1001) id A5557103; Mon, 20 Dec 1999 08:43:30 -0800 (PST) Subject: quick look at 3.4-19991220-STABLE sysinstall To: freebsd-qa@freebsd.org Date: Mon, 20 Dec 1999 08:43:30 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <19991220164330.A5557103@pinenut.nosc.mil> From: syed@pinenut.nosc.mil (basit Syed) Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1. incorrect URL is followed by an interface shutdown. must abort and restart. 2. after completion of NOVICE install, then going to Configuration menu and selecting Distributions causes SIG 11. This was the same behavior with 3.4-19991219-STABLE. 3. Disklabel Menu: select A for Auto then delete swap and usr. then i attempted to create a partition. i get a system message: Unable to create the Partions, too big". also cannot create 1M partition even though system says smallest is 1M: "Can't create 1MB size". 4. more later --b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 20 17:15: 5 1999 Delivered-To: freebsd-qa@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id A90741545C; Mon, 20 Dec 1999 17:14:54 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991221011246.IWGJ7552.mail.rdc3.on.home.com@tristan.net>; Mon, 20 Dec 1999 17:12:46 -0800 Content-Length: 900 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <385D8697.D237F7B7@wcnet.net> Date: Mon, 20 Dec 1999 20:12:05 -0500 (EST) From: Colin To: John Estess , freebsd-qa@FreeBSD.ORG Subject: RE: freebsd-stable wannabe tester Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The other thing you might try is subscribing to freebsd-qa. Assuming our friend the moderator doesn't mind ;) This is where we've been tracking the tests on 3.4-RC most recently. On 20-Dec-1999 John Estess wrote: > I'm been shamed into becoming a -stable tester (read > comp.unix.bsd.freebsd.misc if you care how) and wonder what kind of help > you need. Just download and compile latest kernel? Anything else? > > -- > _/ _/_/_/ || John Estess > _/ _/ _/_/ || jestess@wcnet.net > _/_/_/ _/_/_/ || C- FAQ: http://www.eskimo.com/~scs/C-faq/top.html > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---------------------------------- E-Mail: Colin Date: 20-Dec-1999 Time: 20:09:51 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 20 17:20:23 1999 Delivered-To: freebsd-qa@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id C37AC153DD for ; Mon, 20 Dec 1999 17:20:20 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991221011812.IXKJ7552.mail.rdc3.on.home.com@tristan.net> for ; Mon, 20 Dec 1999 17:18:12 -0800 Content-Length: 452 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 20 Dec 1999 20:17:32 -0500 (EST) From: Colin To: freebsd-qa@FreeBSD.ORG Subject: After 3.4 finally goes out the door Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I realize we got off to a rather slow start, but all things considered better than many expected. My question is, is there any intent for this list to survive the release of 3.4, as basically a home for people with the time/energy/hardware to talk about testing? I think it would be a marvelous idea, assuming sufficient interest of course, to continue this with 4.0-RC when that starts the long arduous path from -CURRENT ;) Cheers, Colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 20 17:50:21 1999 Delivered-To: freebsd-qa@freebsd.org Received: from staff.accessus.net (staff.accessus.net [209.145.151.3]) by hub.freebsd.org (Postfix) with ESMTP id 7D950153FE; Mon, 20 Dec 1999 17:50:14 -0800 (PST) (envelope-from doogie@staff.accessus.net) Received: by staff.accessus.net with Internet Mail Service (5.5.2650.21) id ; Mon, 20 Dec 1999 19:50:13 -0600 Message-ID: From: Jason Young To: 'Colin' , freebsd-qa@FreeBSD.ORG Cc: "'jkh@freebsd.org'" Subject: RE: After 3.4 finally goes out the door Date: Mon, 20 Dec 1999 19:50:12 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF4B55.B8B7227A" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF4B55.B8B7227A Content-Type: text/plain; charset="iso-8859-1" I think it's a good idea to keep the list around, but I don't think that the QA volunteers were really used to their full potential. I tested when I could (early in the testing cycle), and I feel that most of my efforts were for naught, because as usual, a large percentage of the commits in the testing period were very last minute (after most or all of the QA builds). Yeah, it's a free software project and nobody's paid, and what gets out the door is still a fine piece of work (and major kudos to jkh and the rest of the guys on that). But, I don't think much meaningful testing of the real release was accomplished due to all the really really late changes. The last minute "oh I really need such and such MFC'd" trips are killers (sysinstall, moused, you won't have to rack your brain too hard for examples). I assume that the schedule for 3.5-RELEASE is pretty much set already. Would it be possible to back most of that schedule up about a week, and in the week before the CD is cut, put the "pretty-much-final, we-really-mean-it, won't touch it unless the release is definitely fscked" up for general FTP? If the schedules are set well in advance, nobody will be hurting or complaining of the loss of one week's time in a three or four month -STABLE release cycle. The QA volunteers need a set release to assure its quality, ya know? This is no extra work or major change for anyone. I think that if we could get the "frozen" release candidate out there in front of people for at least a week or so, we could muchly reduce the size of our ERRATA files. > -----Original Message----- > From: Colin [mailto:cwass99@home.com] > Sent: Monday, December 20, 1999 7:18 PM > To: freebsd-qa@FreeBSD.ORG > Subject: After 3.4 finally goes out the door > > > I realize we got off to a rather slow start, but all > things considered > better than many expected. My question is, is there any > intent for this list > to survive the release of 3.4, as basically a home for people with the > time/energy/hardware to talk about testing? > I think it would be a marvelous idea, assuming > sufficient interest of > course, to continue this with 4.0-RC when that starts the > long arduous path > from -CURRENT ;) > > Cheers, > Colin > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-qa" in the body of the message > ------_=_NextPart_001_01BF4B55.B8B7227A Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: After 3.4 finally goes out the door

I think it's a good idea to keep the list around, but = I don't think that the QA volunteers were really used to their full = potential.

I tested when I could (early in the testing cycle), = and I feel that most of my efforts were for naught, because as usual, a = large percentage of the commits in the testing period were very last = minute (after most or all of the QA builds).

Yeah, it's a free software project and nobody's paid, = and what gets out the door is still a fine piece of work (and major = kudos to jkh and the rest of the guys on that). But, I don't think much = meaningful testing of the real release was accomplished due to all the = really really late changes. The last minute "oh I really need such = and such MFC'd" trips are killers (sysinstall, moused, you won't = have to rack your brain too hard for examples).

I assume that the schedule for 3.5-RELEASE is pretty = much set already. Would it be possible to back most of that schedule up = about a week, and in the week before the CD is cut, put the = "pretty-much-final, we-really-mean-it, won't touch it unless the = release is definitely fscked" up for general FTP? If the schedules = are set well in advance, nobody will be hurting or complaining of the = loss of one week's time in a three or four month -STABLE release cycle. = The QA volunteers need a set release to assure its quality, ya know? = This is no extra work or major change for anyone.

I think that if we could get the "frozen" = release candidate out there in front of people for at least a week or = so, we could muchly reduce the size of our ERRATA files.

> -----Original Message-----
> From: Colin [mailto:cwass99@home.com]
> Sent: Monday, December 20, 1999 7:18 PM
> To: freebsd-qa@FreeBSD.ORG
> Subject: After 3.4 finally goes out the = door
>
>
>      I realize we got = off to a rather slow start, but all
> things considered
> better than many expected.  My question = is, is there any
> intent for this list
> to survive the release of 3.4, as basically a = home for people with the
> time/energy/hardware to talk about = testing?
>      I think it would = be a marvelous idea, assuming
> sufficient interest of
> course, to continue this with 4.0-RC when that = starts the
> long arduous path
> from -CURRENT ;)
>
> Cheers,
> Colin
>
>
> To Unsubscribe: send mail to = majordomo@FreeBSD.org
> with "unsubscribe freebsd-qa" in the = body of the message
>

------_=_NextPart_001_01BF4B55.B8B7227A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 20 18: 1:23 1999 Delivered-To: freebsd-qa@freebsd.org Received: from diarmadhi.mushhaven.net (diarmadhi.mushhaven.net [63.75.111.197]) by hub.freebsd.org (Postfix) with ESMTP id 662B015271; Mon, 20 Dec 1999 18:01:20 -0800 (PST) (envelope-from mistwolf@diarmadhi.mushhaven.net) Received: (from mistwolf@localhost) by diarmadhi.mushhaven.net (8.9.3/8.9.3) id RAA59102; Mon, 20 Dec 1999 17:59:51 -0800 (PST) (envelope-from mistwolf) Date: Mon, 20 Dec 1999 17:59:51 -0800 From: Jamie Norwood To: Jason Young Cc: "'Colin'" , freebsd-qa@FreeBSD.ORG, "'jkh@freebsd.org'" Subject: Re: After 3.4 finally goes out the door Message-ID: <19991220175951.A59081@mushhaven.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I agree with this totally. I also feel someone should step forward and coordinate; I didn't do more than install and see if it worked as I am not familier with how things should be tested. Also, I feel that some things should be made available such as CVSUP scripts and such to make sure the people involved really are testing the right things. Could we maybe get a 'branch' named 'qa' that would show rc or qa in the uname output? That would also make things easier as we could then test that tree for the cd, and bug fixes that are essential could then be made to that tree only, and normal developement could continue on the -STABLE/-RELEASE tree. Jamie On Mon, Dec 20, 1999 at 07:50:12PM -0600, Jason Young wrote: > > I think it's a good idea to keep the list around, but I don't think that the > QA volunteers were really used to their full potential. > > I tested when I could (early in the testing cycle), and I feel that most of > my efforts were for naught, because as usual, a large percentage of the > commits in the testing period were very last minute (after most or all of > the QA builds). > > Yeah, it's a free software project and nobody's paid, and what gets out the > door is still a fine piece of work (and major kudos to jkh and the rest of > the guys on that). But, I don't think much meaningful testing of the real > release was accomplished due to all the really really late changes. The last > minute "oh I really need such and such MFC'd" trips are killers (sysinstall, > moused, you won't have to rack your brain too hard for examples). > > I assume that the schedule for 3.5-RELEASE is pretty much set already. Would > it be possible to back most of that schedule up about a week, and in the > week before the CD is cut, put the "pretty-much-final, we-really-mean-it, > won't touch it unless the release is definitely fscked" up for general FTP? > If the schedules are set well in advance, nobody will be hurting or > complaining of the loss of one week's time in a three or four month -STABLE > release cycle. The QA volunteers need a set release to assure its quality, > ya know? This is no extra work or major change for anyone. > > I think that if we could get the "frozen" release candidate out there in > front of people for at least a week or so, we could muchly reduce the size > of our ERRATA files. > > > -----Original Message----- > > From: Colin [mailto:cwass99@home.com] > > Sent: Monday, December 20, 1999 7:18 PM > > To: freebsd-qa@FreeBSD.ORG > > Subject: After 3.4 finally goes out the door > > > > > > I realize we got off to a rather slow start, but all > > things considered > > better than many expected. My question is, is there any > > intent for this list > > to survive the release of 3.4, as basically a home for people with the > > time/energy/hardware to talk about testing? > > I think it would be a marvelous idea, assuming > > sufficient interest of > > course, to continue this with 4.0-RC when that starts the > > long arduous path > > from -CURRENT ;) > > > > Cheers, > > Colin > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-qa" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 20 18:26:52 1999 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 5D9F214D6F for ; Mon, 20 Dec 1999 18:26:49 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id VAA14961 for ; Mon, 20 Dec 1999 21:26:47 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912210226.VAA14961@spoon.beta.com> To: freebsd-qa@freebsd.org Subject: Re: After 3.4 finally goes out the door In-reply-to: Your message of "Mon, 20 Dec 1999 17:59:51 PST." <19991220175951.A59081@mushhaven.net> Date: Mon, 20 Dec 1999 21:26:47 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A quick thanks to everyone who helped out on testing 3.4. The sentiments below seem to be fairly consistent with everyone's take on the process (myself included), so I'll take a minute and talk to them... > I agree with this totally. I also feel someone should step forward > and coordinate; Well, thats me :) Help me or yell at me as you like. I can take it ;) Overall, we tried. Unfortunately, we got started about 48 hours before the 3.4 release process started. During this 48 hours, we had to get volunteers, figure out a rough test schedule for the 16 days we had, and get as many people "ready" to hit it as possible. We didn't do too badly. I think we got some good exposure of the release. Contrary to belief, we did find and fix some things that would have made for a good, lengthy ERRATA file. > I didn't do more than install and see if it worked > as I am not familier with how things should be tested. You have to start somewhere. I think we got good coverage for a number of the critical pieces. In the real world, you'd have test tools to play with APIs for things (disks, mmap(), threads, etc.), which we didn't have this spin, but a lot of testing is still "taking it for a drive", which we all did in one way or another. > Also, I feel > that some things should be made available such as CVSUP scripts > and such to make sure the people involved really are testing the > right things. Could we maybe get a 'branch' named 'qa' that would show > rc or qa in the uname output? We asked for the tag. Its "too expensive" for the CVS repository. Normally, at the beginning of the project (for those late comers), the target stable snapshots are documented ahead of time... usually one every four days. Towards the end of this cycle (which I expect will happen in all cycles), it broke down in to daily or every-other-day snapshots so that we could be on top of the latest code, and really ride the day to day fixes. > That would also make things easier as we > could then test that tree for the cd, and bug fixes that are essential > could then be made to that tree only, and normal developement could > continue on the -STABLE/-RELEASE tree. The powers that be also don't like this (it, too, was brought up). It ends up being another merge issue (after all, you'll want fixes in your -RC branch to go back in to -stable sooner or later). I do agree that some of the last-minute changes caused some problems (*cough sysinstall *cough). I particularly don't like the fact that they slipped it in so late in the game. _But_, we are testers, not developers. Its not our place to make policy, only to point out the errors created by that policy ;) As to 4.0, here was the last conversation I had with Jordan on the topic... >> Hi, Jordan. I was just scanning -current, and have noticed alot about the >> "impending" 4.0-RELEASE. The only semi-solid number I've heard is 5 weeks, >> which will put it around 1/18/2000. > >It's somewhere in-between 1/15/2000 and 2/15/2000, the former being >the published date. > >- Jordan This means we all get a "Happy Holidays" break, and then we'll be looking at 4.0. Starting around 12/31, 1/1 (Hope its Y2K compliant! ;) ).... (Hint: If you want to start working on it now, the 12/27, 12/23, 12/31, 1/4, 1/8, and 1/12 dates will be the -CURRENT snapshots you want initially). This probably also means that we won't be test/feature rich for this release either. If there are a couple of good coders on the list who like writing tools to test things, then we'll abstain your need to test if you can provide said tools/scripts. After 4.0, I plan on starting some work in this area, but, as always with everyone, my time is somewhat limited. Anyhow, keep your spirits up. We're just starting, and it'll take some time to get a good working pattern down. The _best_ thing each of us can do is play with the upcoming releases and features, keep talking to each other about testing, and help out with tools as best as one can. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 20 18:57:28 1999 Delivered-To: freebsd-qa@freebsd.org Received: from staff.accessus.net (staff.accessus.net [209.145.151.3]) by hub.freebsd.org (Postfix) with ESMTP id D020514DEC; Mon, 20 Dec 1999 18:57:21 -0800 (PST) (envelope-from doogie@staff.accessus.net) Received: by staff.accessus.net with Internet Mail Service (5.5.2650.21) id ; Mon, 20 Dec 1999 20:57:21 -0600 Message-ID: From: Jason Young To: "'mistwolf@mushhaven.net'" , freebsd-qa@FreeBSD.ORG Cc: "'jkh@freebsd.org'" Subject: RE: After 3.4 finally goes out the door Date: Mon, 20 Dec 1999 20:57:14 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF4B5F.18AB1FAC" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF4B5F.18AB1FAC Content-Type: text/plain; charset="iso-8859-1" Well, I was trying to avoid the 'someone oughta' and 'you really should' type of rambling. :) I simply propose that if we could just gain some more time to QA the "real" release, then we'd get some truly useful work done. As for a standardized testing methodology or procedure? IMHO, that would be counterproductive. Everybody's got a different usage pattern, and different hardware, and trying to force people into the same mold will be hard and ultimately bad and wrong. For instance, if you had some script to follow in sysinstall - "test this, and then this, and then this, and test this" - would the sysinstall bugs have been found? If end-users with different hardware and configurations and usage patterns hadn't tested moused, would we have shipped with roller wheel support? No, it's people doing what they normally do, which is quite likely to be outside of what the developer tested. This is a Good Thing, and we need people doing their own unexpected, possibly weird, sometimes nonobvious stuff. The developers aren't total morons and the obvious stuff obviously works fine. The developers already have and already run the various regression tests that are available. A technically savvy QA volunteer might want to run those, and certainly that's fine, but I don't think we're short of dedicated and technical savvy developers familiar with the OS and its internals. What we need, IMHO, is a bunch of people putting it in real world situations, testing it under their various application and user loads, and seeing how it does. We had this in the form of the 3.4-RELEASE QA volunteer team, and everybody did a great job with the time and resources available. I hope that jkh and friends can see this, and see that just a little bit of foresight we can make sure that the next CD that ships holds a truly solid and kickass release. > -----Original Message----- > From: Jamie Norwood [mailto:mistwolf@mushhaven.net] > Sent: Monday, December 20, 1999 8:00 PM > To: Jason Young > Cc: 'Colin'; freebsd-qa@FreeBSD.ORG; 'jkh@freebsd.org' > Subject: Re: After 3.4 finally goes out the door > > > I agree with this totally. I also feel someone should step forward > and coordinate; I didn't do more than install and see if it worked > as I am not familier with how things should be tested. Also, I feel > that some things should be made available such as CVSUP scripts > and such to make sure the people involved really are testing the > right things. Could we maybe get a 'branch' named 'qa' that would show > rc or qa in the uname output? That would also make things > easier as we > could then test that tree for the cd, and bug fixes that are essential > could then be made to that tree only, and normal developement could > continue on the -STABLE/-RELEASE tree. > > Jamie > > > On Mon, Dec 20, 1999 at 07:50:12PM -0600, Jason Young wrote: > > > > I think it's a good idea to keep the list around, but I > don't think that the > > QA volunteers were really used to their full potential. > > > > I tested when I could (early in the testing cycle), and I > feel that most of > > my efforts were for naught, because as usual, a large > percentage of the > > commits in the testing period were very last minute (after > most or all of > > the QA builds). > > > > Yeah, it's a free software project and nobody's paid, and > what gets out the > > door is still a fine piece of work (and major kudos to jkh > and the rest of > > the guys on that). But, I don't think much meaningful > testing of the real > > release was accomplished due to all the really really late > changes. The last > > minute "oh I really need such and such MFC'd" trips are > killers (sysinstall, > > moused, you won't have to rack your brain too hard for examples). > > > > I assume that the schedule for 3.5-RELEASE is pretty much > set already. Would > > it be possible to back most of that schedule up about a > week, and in the > > week before the CD is cut, put the "pretty-much-final, > we-really-mean-it, > > won't touch it unless the release is definitely fscked" up > for general FTP? > > If the schedules are set well in advance, nobody will be hurting or > > complaining of the loss of one week's time in a three or > four month -STABLE > > release cycle. The QA volunteers need a set release to > assure its quality, > > ya know? This is no extra work or major change for anyone. > > > > I think that if we could get the "frozen" release candidate > out there in > > front of people for at least a week or so, we could muchly > reduce the size > > of our ERRATA files. > > > > > -----Original Message----- > > > From: Colin [mailto:cwass99@home.com] > > > Sent: Monday, December 20, 1999 7:18 PM > > > To: freebsd-qa@FreeBSD.ORG > > > Subject: After 3.4 finally goes out the door > > > > > > > > > I realize we got off to a rather slow start, but all > > > things considered > > > better than many expected. My question is, is there any > > > intent for this list > > > to survive the release of 3.4, as basically a home for > people with the > > > time/energy/hardware to talk about testing? > > > I think it would be a marvelous idea, assuming > > > sufficient interest of > > > course, to continue this with 4.0-RC when that starts the > > > long arduous path > > > from -CURRENT ;) > > > > > > Cheers, > > > Colin > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-qa" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-qa" in the body of the message > ------_=_NextPart_001_01BF4B5F.18AB1FAC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: After 3.4 finally goes out the door

Well, I was trying to avoid the 'someone oughta' and = 'you really should' type of rambling. :) I simply propose that if we = could just gain some more time to QA the "real" release, then = we'd get some truly useful work done.

As for a standardized testing methodology or = procedure? IMHO, that would be counterproductive. Everybody's got a = different usage pattern, and different hardware, and trying to force = people into the same mold will be hard and ultimately bad and = wrong.

For instance, if you had some script to follow in = sysinstall - "test this, and then this, and then this, and test = this" - would the sysinstall bugs have been found? If end-users = with different hardware and configurations and usage patterns hadn't = tested moused, would we have shipped with roller wheel support? No, = it's people doing what they normally do, which is quite likely to be = outside of what the developer tested. This is a Good Thing, and we need = people doing their own unexpected, possibly weird, sometimes nonobvious = stuff. The developers aren't total morons and the obvious stuff = obviously works fine.

The developers already have and already run the = various regression tests that are available. A technically savvy QA = volunteer might want to run those, and certainly that's fine, but I = don't think we're short of dedicated and technical savvy developers = familiar with the OS and its internals. What we need, IMHO, is a bunch = of people putting it in real world situations, testing it under their = various application and user loads, and seeing how it does.

We had this in the form of the 3.4-RELEASE QA = volunteer team, and everybody did a great job with the time and = resources available. I hope that jkh and friends can see this, and see = that just a little bit of foresight we can make sure that the next CD = that ships holds a truly solid and kickass release.

> -----Original Message-----
> From: Jamie Norwood [mailto:mistwolf@mushhaven.net= ]
> Sent: Monday, December 20, 1999 8:00 PM
> To: Jason Young
> Cc: 'Colin'; freebsd-qa@FreeBSD.ORG; = 'jkh@freebsd.org'
> Subject: Re: After 3.4 finally goes out the = door
>
>
> I agree with this totally. I also feel someone = should step forward
> and coordinate; I didn't do more than install = and see if it worked
> as I am not familier with how things should be = tested. Also, I feel
> that some things should be made available such = as CVSUP scripts
> and such to make sure the people involved = really are testing the
> right things. Could we maybe get a 'branch' = named 'qa' that would show
> rc or qa in the uname output? That would also = make things
> easier as we
> could then test that tree for the cd, and bug = fixes that are essential
> could then be made to that tree only, and = normal developement could
> continue on the -STABLE/-RELEASE tree.
>
> Jamie
>
>
> On Mon, Dec 20, 1999 at 07:50:12PM -0600, Jason = Young wrote:
> >
> > I think it's a good idea to keep the list = around, but I
> don't think that the
> > QA volunteers were really used to their = full potential.
> >
> > I tested when I could (early in the = testing cycle), and I
> feel that most of
> > my efforts were for naught, because as = usual, a large
> percentage of the
> > commits in the testing period were very = last minute (after
> most or all of
> > the QA builds).
> >
> > Yeah, it's a free software project and = nobody's paid, and
> what gets out the
> > door is still a fine piece of work (and = major kudos to jkh
> and the rest of
> > the guys on that). But, I don't think much = meaningful
> testing of the real
> > release was accomplished due to all the = really really late
> changes. The last
> > minute "oh I really need such and = such MFC'd" trips are
> killers (sysinstall,
> > moused, you won't have to rack your brain = too hard for examples).
> >
> > I assume that the schedule for 3.5-RELEASE = is pretty much
> set already. Would
> > it be possible to back most of that = schedule up about a
> week, and in the
> > week before the CD is cut, put the = "pretty-much-final,
> we-really-mean-it,
> > won't touch it unless the release is = definitely fscked" up
> for general FTP?
> > If the schedules are set well in advance, = nobody will be hurting or
> > complaining of the loss of one week's time = in a three or
> four month -STABLE
> > release cycle. The QA volunteers need a = set release to
> assure its quality,
> > ya know? This is no extra work or major = change for anyone.
> >
> > I think that if we could get the = "frozen" release candidate
> out there in
> > front of people for at least a week or so, = we could muchly
> reduce the size
> > of our ERRATA files.
> >
> > > -----Original Message-----
> > > From: Colin [mailto:cwass99@home.com]
> > > Sent: Monday, December 20, 1999 7:18 = PM
> > > To: freebsd-qa@FreeBSD.ORG
> > > Subject: After 3.4 finally goes out = the door
> > >
> > >
> > >      I = realize we got off to a rather slow start, but all
> > > things considered
> > > better than many expected.  My = question is, is there any
> > > intent for this list
> > > to survive the release of 3.4, as = basically a home for
> people with the
> > > time/energy/hardware to talk about = testing?
> > >      I think = it would be a marvelous idea, assuming
> > > sufficient interest of
> > > course, to continue this with 4.0-RC = when that starts the
> > > long arduous path
> > > from -CURRENT ;)
> > >
> > > Cheers,
> > > Colin
> > >
> > >
> > > To Unsubscribe: send mail to = majordomo@FreeBSD.org
> > > with "unsubscribe = freebsd-qa" in the body of the message
> > >
>
>
> To Unsubscribe: send mail to = majordomo@FreeBSD.org
> with "unsubscribe freebsd-qa" in the = body of the message
>

------_=_NextPart_001_01BF4B5F.18AB1FAC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Mon Dec 20 19:10:11 1999 Delivered-To: freebsd-qa@freebsd.org Received: from diarmadhi.mushhaven.net (diarmadhi.mushhaven.net [63.75.111.197]) by hub.freebsd.org (Postfix) with ESMTP id DAD2914A25; Mon, 20 Dec 1999 19:10:06 -0800 (PST) (envelope-from mistwolf@diarmadhi.mushhaven.net) Received: (from mistwolf@localhost) by diarmadhi.mushhaven.net (8.9.3/8.9.3) id TAA59458; Mon, 20 Dec 1999 19:08:47 -0800 (PST) (envelope-from mistwolf) Date: Mon, 20 Dec 1999 19:08:47 -0800 From: Jamie Norwood To: Jason Young Cc: freebsd-qa@FreeBSD.ORG, "'jkh@freebsd.org'" Subject: Re: After 3.4 finally goes out the door Message-ID: <19991220190847.A59425@mushhaven.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 08:57:14PM -0600, Jason Young wrote: > > Well, I was trying to avoid the 'someone oughta' and 'you really should' > type of rambling. :) I simply propose that if we could just gain some more > time to QA the "real" release, then we'd get some truly useful work done. > > As for a standardized testing methodology or procedure? IMHO, that would be > counterproductive. Everybody's got a different usage pattern, and different > hardware, and trying to force people into the same mold will be hard and > ultimately bad and wrong. > > For instance, if you had some script to follow in sysinstall - "test this, > and then this, and then this, and test this" - would the sysinstall bugs > have been found? Not if a full-featured script was written. Beyond, not having a script does not mean a bug .will. be found. I simply mean for people who don't have the knowledge or time to play with trying hard to break it, having a set set of things everyone should look at will get the broader range of hardware out there. > If end-users with different hardware and configurations and > usage patterns hadn't tested moused, would we have shipped with roller wheel > support? No, it's people doing what they normally do, which is quite likely > to be outside of what the developer tested. This is a Good Thing, and we > need people doing their own unexpected, possibly weird, sometimes nonobvious > stuff. The developers aren't total morons and the obvious stuff obviously > works fine. Are the two, though, mutually exclusive? I don't think a script precludes people doing their own thing so much as helps get people who don't HAVE their own thing involved and useful. > The developers already have and already run the various regression tests > that are available. A technically savvy QA volunteer might want to run > those, and certainly that's fine, but I don't think we're short of dedicated > and technical savvy developers familiar with the OS and its internals. What > we need, IMHO, is a bunch of people putting it in real world situations, > testing it under their various application and user loads, and seeing how it > does. But we couldn't/shouldn't be putting this on production machines, and the only machine I really run FreeBSD on is one I cannot reboot once or twice a day for a week every three months. Which means I don't have much I can really test in a real-world situation. > We had this in the form of the 3.4-RELEASE QA volunteer team, and everybody > did a great job with the time and resources available. I hope that jkh and > friends can see this, and see that just a little bit of foresight we can > make sure that the next CD that ships holds a truly solid and kickass > release. I agree we did great, but I definately feel we could do better. Certain things, like sysinstall, do need to be tested by as many people as possible. Moused, when they were putting wheel support in, would have been great to send out a list that said 'OK, if you have a wheel mouse, do X, Y, and Z and tell us if it works/fails and what hardware you run on'. Jamie > > > -----Original Message----- > > From: Jamie Norwood [mailto:mistwolf@mushhaven.net] > > Sent: Monday, December 20, 1999 8:00 PM > > To: Jason Young > > Cc: 'Colin'; freebsd-qa@FreeBSD.ORG; 'jkh@freebsd.org' > > Subject: Re: After 3.4 finally goes out the door > > > > > > I agree with this totally. I also feel someone should step forward > > and coordinate; I didn't do more than install and see if it worked > > as I am not familier with how things should be tested. Also, I feel > > that some things should be made available such as CVSUP scripts > > and such to make sure the people involved really are testing the > > right things. Could we maybe get a 'branch' named 'qa' that would show > > rc or qa in the uname output? That would also make things > > easier as we > > could then test that tree for the cd, and bug fixes that are essential > > could then be made to that tree only, and normal developement could > > continue on the -STABLE/-RELEASE tree. > > > > Jamie > > > > > > On Mon, Dec 20, 1999 at 07:50:12PM -0600, Jason Young wrote: > > > > > > I think it's a good idea to keep the list around, but I > > don't think that the > > > QA volunteers were really used to their full potential. > > > > > > I tested when I could (early in the testing cycle), and I > > feel that most of > > > my efforts were for naught, because as usual, a large > > percentage of the > > > commits in the testing period were very last minute (after > > most or all of > > > the QA builds). > > > > > > Yeah, it's a free software project and nobody's paid, and > > what gets out the > > > door is still a fine piece of work (and major kudos to jkh > > and the rest of > > > the guys on that). But, I don't think much meaningful > > testing of the real > > > release was accomplished due to all the really really late > > changes. The last > > > minute "oh I really need such and such MFC'd" trips are > > killers (sysinstall, > > > moused, you won't have to rack your brain too hard for examples). > > > > > > I assume that the schedule for 3.5-RELEASE is pretty much > > set already. Would > > > it be possible to back most of that schedule up about a > > week, and in the > > > week before the CD is cut, put the "pretty-much-final, > > we-really-mean-it, > > > won't touch it unless the release is definitely fscked" up > > for general FTP? > > > If the schedules are set well in advance, nobody will be hurting or > > > complaining of the loss of one week's time in a three or > > four month -STABLE > > > release cycle. The QA volunteers need a set release to > > assure its quality, > > > ya know? This is no extra work or major change for anyone. > > > > > > I think that if we could get the "frozen" release candidate > > out there in > > > front of people for at least a week or so, we could muchly > > reduce the size > > > of our ERRATA files. > > > > > > > -----Original Message----- > > > > From: Colin [mailto:cwass99@home.com] > > > > Sent: Monday, December 20, 1999 7:18 PM > > > > To: freebsd-qa@FreeBSD.ORG > > > > Subject: After 3.4 finally goes out the door > > > > > > > > > > > > I realize we got off to a rather slow start, but all > > > > things considered > > > > better than many expected. My question is, is there any > > > > intent for this list > > > > to survive the release of 3.4, as basically a home for > > people with the > > > > time/energy/hardware to talk about testing? > > > > I think it would be a marvelous idea, assuming > > > > sufficient interest of > > > > course, to continue this with 4.0-RC when that starts the > > > > long arduous path > > > > from -CURRENT ;) > > > > > > > > Cheers, > > > > Colin > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-qa" in the body of the message > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-qa" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Wed Dec 22 22: 6:17 1999 Delivered-To: freebsd-qa@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BC98314FDD; Wed, 22 Dec 1999 22:06:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA11238; Wed, 22 Dec 1999 22:06:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Jason Young Cc: "'Colin'" , freebsd-qa@FreeBSD.ORG, "'jkh@freebsd.org'" Subject: Re: After 3.4 finally goes out the door In-reply-to: Your message of "Mon, 20 Dec 1999 19:50:12 CST." Date: Wed, 22 Dec 1999 22:06:04 -0800 Message-ID: <11234.945929164@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think it's a good idea to keep the list around, but I don't think that the > QA volunteers were really used to their full potential. I agree, nor can I fault any of your reasoning as to why. > Yeah, it's a free software project and nobody's paid, and what gets out the > door is still a fine piece of work (and major kudos to jkh and the rest of > the guys on that). But, I don't think much meaningful testing of the real > release was accomplished due to all the really really late changes. The last > minute "oh I really need such and such MFC'd" trips are killers (sysinstall, > moused, you won't have to rack your brain too hard for examples). All I can say is that mistakes were made and learned from, in some cases for the 2nd or 3rd time (*urk*), and 3.5 will come out with a very very different and somewhat elongated release schedule as a result. Shall we say 30 days? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Thu Dec 23 18:59: 0 1999 Delivered-To: freebsd-qa@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id EE80815122; Thu, 23 Dec 1999 18:58:57 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991224025649.ODYH7552.mail.rdc3.on.home.com@tristan.net>; Thu, 23 Dec 1999 18:56:49 -0800 Content-Length: 1400 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <11234.945929164@zippy.cdrom.com> Date: Thu, 23 Dec 1999 21:56:03 -0500 (EST) From: Colin To: "Jordan K. Hubbard" Subject: Re: After 3.4 finally goes out the door Cc: "jkh@freebsd.org" , freebsd-qa@FreeBSD.ORG, Jason Young Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm in for a longer adventure, but I'm not sure 30 days is workable. Ideally we'd have a freeze at the start of the test phase, and I can't see a 30 day freeze working in this environment ;) I think we saw what happened when we tried testing against a moving target. I honestly don't know what the answer is, maybe tighter control over changes and additions after we enter the test phase without a real freeze? Maybe there is a way to do a freeze? The other point we should be aware of is that starting in Jan, most of us (I assume most of the people on this list are in the IT industry somewhere ;)) can expect to get really busy as the Y2K panic ends and businesses get back to upgrading and buying new stuff. Time for volunteering might get a bit tight ;) Assuming my day job doesn't kill me, I'lll even attempt some code for testing specific functionality. I'm open to ideas for this, I've already started mapping out some code to test threads and the file system, and I should have something to play with before end month. I really had no (and am still a bit vague on) ideas for what needs testing. cheers, Colin Jordan wrote... > All I can say is that mistakes were made and learned from, in some > cases for the 2nd or 3rd time (*urk*), and 3.5 will come out with a > very very different and somewhat elongated release schedule as a > result. Shall we say 30 days? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message From owner-freebsd-qa Sat Dec 25 12: 0:31 1999 Delivered-To: freebsd-qa@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1DC0A14EDB; Sat, 25 Dec 1999 12:00:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA57643; Sat, 25 Dec 1999 12:00:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Colin Cc: "jkh@freebsd.org" , freebsd-qa@FreeBSD.ORG, Jason Young Subject: Re: After 3.4 finally goes out the door In-reply-to: Your message of "Thu, 23 Dec 1999 21:56:03 EST." Date: Sat, 25 Dec 1999 12:00:38 -0800 Message-ID: <57639.946152038@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm in for a longer adventure, but I'm not sure 30 days is workable. Well, 30 days is workable if it's a real freeze, and that was something I also forgot to mention in my previous missive - we'd be going to a *real* freeze structure, not the half tongue-in-cheek "code slushes" I've been calling lately. A code slush might be appropriate for -current pending a dot-zero release, that much I can see, but anything less than a hard freeze for -stable pending a release just isn't going to fly in the future. In my eagerness to get rid of a really annoying and long-standing problem, I also broke too many of my own rules for last-minute tweaking with sysinstall in 3.4 and I don't intend to make that mistake again. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message