From owner-freebsd-hackers Wed Aug 7 19:23:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA26359 for hackers-outgoing; Wed, 7 Aug 1996 19:23:45 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA26352; Wed, 7 Aug 1996 19:23:42 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id TAA14249; Wed, 7 Aug 1996 19:23:11 -0700 (PDT) To: mikebo@tellabs.com cc: mikebo@freefall.freebsd.org (Mike Borowiec), mrm@mole.mole.org, bugs@freebsd.org, hackers@freebsd.org Subject: Re: 2.1.5R PANIC on AHA2742AT In-reply-to: Your message of "Wed, 07 Aug 1996 12:13:45 CDT." <199608071713.MAA21702@sunc210.tellabs.com> Date: Wed, 07 Aug 1996 19:23:11 -0700 Message-ID: <14247.839470991@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is a nameserver mandatory? If so, the field editing probably shouldn't > have let me proceed without entering a value (or offering a default > value like "NO"). It is for now. :-( It never used to be, but some bug crept in which has now made it a mandatory field. I've looked through the code in question several times and can't reproduce any nameserver variable related crashes in multiuser mode (and its value is checked for NULL everywhere it's used). It's very strange. Anyway, I'm certainly going to try and fix it but, up to now, have been too busy with other things to set up the kind of testing environment I could both reproduce and debug the problem with - if I can't reproduce this running multiuser, I have to add debugging code for the purpose. :-( > Anyway, I'm trying to do a load via NFS, and spec'ed the server like so: > 198.102.156.5:/usr/FreeBSD. It shouldn't need a nameserver. What to do? Enter a nameserver value then nuke your /etc/resolv.conf when you come up. Jordan