From owner-freebsd-bugs Fri Oct 27 22:10:03 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA13399 for bugs-outgoing; Fri, 27 Oct 1995 22:10:03 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA13379 ; Fri, 27 Oct 1995 22:10:01 -0700 Resent-Date: Fri, 27 Oct 1995 22:10:01 -0700 Resent-Message-Id: <199510280510.WAA13379@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, uhclem@fw.ast.com Received: from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id WAA13248 for ; Fri, 27 Oct 1995 22:07:39 -0700 Received: from fw.ast.com by ast.com with SMTP id AA03095 (5.67b/IDA-1.5 for ); Fri, 27 Oct 1995 22:08:48 -0700 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0t93PX-000086C; Sat, 28 Oct 95 00:02 CDT Received: by nemesis.lonestar.org (Smail3.1.27.1 #19) id m0t93D5-000IvJC; Fri, 27 Oct 95 23:49 WET DST Message-Id: Date: Fri, 27 Oct 95 23:49 WET DST From: uhclem%nemesis@fw.ast.com Reply-To: uhclem@fw.ast.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: misc/796: Network install incomplete in 1026-SNAP FDIV036 Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 796 >Category: misc >Synopsis: Network install doesn't update /etc/hosts FDIV036 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Oct 27 22:10:00 PDT 1995 >Last-Modified: >Originator: Frank Durda IV >Organization: none >Release: FreeBSD 2.1.0-951026-SNAP >Environment: Fresh install of 2.1.0-951026-SNAP on local ethernet network. Install was via FTP. >Description: After performing a successfull installation of a 1026 SNAP system using FTP from "another site", (which means I had to describe the network interface, IP number and other IP-ish details), all appears OK. In my case, the IP was 165.164.6.19 and the download was from 165.164.6.15. The mask was 255.255.0.0, the 1026 system was named skaro.lonestar.org. The remote system was nemesis.lonestar.org (165.164.6.15). However, on the first reboot, several error messages are displayed during the start-up process: ... skaro.lonestar.org: bad value [1] skaro.lonestar.org: bad value ... standard daemons: cron printer sendmailMy host name (skaro.lonestar.org) does not seem to exist! Connection refused [2] . <--- [3] Period on its own line. Oct 27 23:24:52 skaro sendmail[90]: NOQUEUE: SYSERR(root): My host name (skaro.lonestar.org) does not seem to exist!: (Connection refused) [2] . <--- [3] Period on its own line. On logging-in, none of the networking services work correctly. The problem appears to be that the installation process enabled networking, but did not use the information gathered during the installation to create an entry for /etc/hosts. By adding: 165.164.6.19 skaro.lonestar.org skaro to /etc/hosts, and rebooting, all errors went away. These are the same parameters entered during the installation process. Note that I only had a single network interface, and I did not run "Network Configuration" after the install was complete because it implies that you only needed to do this if you had multiple interfaces or were going to change things previously set, or turn on something like NFS. (I don't know if running Network Configuration a second time would have made any difference.) >How-To-Repeat: You can repeat it by doing a network installation. You probably can recreate similar errors by deleting the contents of /etc/hosts and rebooting. >Fix: Have the installation program stick an entry for the machine being installed in /etc/hosts. If a FTP installation was done, the installation system has all the information needed to make the entry. It also appears sendmail needs its error message fixed so that the trailing "." doesn't end up on its own line. The extra "." does not appear in /var/log/messages, but the rest of the error message does. The source of the "bad value" error also needs to be investigated. This message is displayed but does not appear in /var/log/messages. >Audit-Trail: >Unformatted: