From owner-freebsd-bugs Tue Oct 22 22:24:26 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA11767 for bugs-outgoing; Tue, 22 Oct 1996 22:24:26 -0700 (PDT) Received: from freenet.hamilton.on.ca (main.freenet.hamilton.on.ca [199.212.94.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA11752; Tue, 22 Oct 1996 22:24:19 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (james.freenet.hamilton.on.ca [199.212.94.66]) by freenet.hamilton.on.ca (8.7.5/8.7.3) with ESMTP id BAA27640; Wed, 23 Oct 1996 01:24:16 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.7.5/8.7.3) with SMTP id BAA15713; Wed, 23 Oct 1996 01:26:03 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Wed, 23 Oct 1996 01:25:10 -0400 (EDT) From: Tim Vanderhoek Reply-To: Tim Vanderhoek To: "Jordan K. Hubbard" cc: Tim Vanderhoek , phk@freefall.freebsd.org, freebsd-bugs@freefall.freebsd.org, jkh@freebsd.org Subject: Re: misc/1757 In-Reply-To: <7381.846045389@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 22 Oct 1996, Jordan K. Hubbard wrote: > > I don't follow -commit, but comparing -current sysinstall to the one I > > found this bug with revealed no differences likely to fix the problem. > > Moreover, the only changes after the 14th of October were to the help/ > > directory. Using the 2.2-961014-SNAP release, I verified that the bug > > still exists, as reported. (I will admit that one of the steps-to-repeat > > has changed marginally, but it's very intuitive to figure out what to do). > > If it's the bug about a missing NS value we're talking about, then > that was indeed fixed - I've tested it. If we're talking about a > *different* bug then you should re-open the PR. No. The instructions on repeating the bug tell you not to enter a nameserver value, but that is only for your sake so you don't have to dream one up. The bug can be reproduced on the FreeBSD-2.2-961014-SNAP boot disk even if you enter a nameserver value. I just verified this now. My advice is to re-open the PR, leave the how-to-repeat the instructions the same, and keep in mind that this truly is a low-priority bug that most people will never see. I say `keep the how-to-repeat instructions the same' because I don't have instructions written out at the moment that expect you to enter an NS value. It's the same bug that kills you regardless of wether there's an NS value or not. Besides that, shouldn't the NS bug be fixed in both 961001-SNAP and 961014-SNAP? Those are the releases I found and re-verified the bug under, respectively. PostScript: Okay, I wasn't going to include new "how-to-repeat" instructions, but I realized I would've been feeling guilty for the next couple weeks if I didn't, so here they are. Please excuse me if they're a brief, but I really was intending to be asleep by now.... Insert 2.2-961014-SNAP boot disk and boot it. Choose "Options" "Media type" "FTP" "URL" ftp://077.066.077.066/priv/FreeBSD "ppp0" /-- | netconfig | | Host: X | NS: 101.202.033.044 | All others: default tab-over | "Ok" \-- Baud rate? "Ok" your IP? "Ok" message("Please make PPP connection") "Ok" (don't bother making the connection) message("Cannot resolve `'") "Ok" Back at install media menu "FTP" "ppp0" tab over all for netconfig, leaving at same values... (ie. same host, ns, etc.) "Ok" "Ok" "Ok" Back at options menu "Media Type" Reuse old values? "Yes" Skip network configuration? "No" "ppp0" whatch sysinstall go boom. Say "Hey! This Tim guy's pretty good! I wish I was him!" ....or not... :-) -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk