Date: Tue, 10 Jun 2008 17:05:12 GMT From: Garrett Cooper <gcooper@FreeBSD.org> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/124452: 7.0-RELEASE amd64 bootonly media fails to use DHCP because of missing passwd entries Message-ID: <200806101705.m5AH5Ck2031725@www.freebsd.org> Resent-Message-ID: <200806101710.m5AHA4Kq077871@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 124452 >Category: misc >Synopsis: 7.0-RELEASE amd64 bootonly media fails to use DHCP because of missing passwd entries >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jun 10 17:10:04 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Garrett Cooper >Release: 7.0-RELEASE amd64 bootonly >Organization: n/a >Environment: Can't do this yet.. >Description: Going through the typical procedures to do a "Custom install" of FreeBSD and when I ask sysinstall to use DHCP to scan for an IP for me it comes back with blank fields and switching over to the output console I see the output: no such user: _dhcp, falling back to "nobody" no such user: nobody So it looks like the amd64 bootonly release media is missing /etc/passwd or some entries contained within /etc/passwd. My system is a Macbook running the latest VMware Fusion. >How-To-Repeat: 1. Fetch 7.0-RELEASE amd64 bootonly release media from ftp.freebsd.org. 2. Run installer. 3. Run through all steps in Custom install. 4. Attempt to fetch IP via DHCP when setting up the media. >Fix: Entries need to be fixed by release team. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806101705.m5AH5Ck2031725>