Bug 14043

Summary: lo0 not configured by default
Product: Base System Reporter: hvb <hvb>
Component: miscAssignee: jkh
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description hvb 1999-09-30 05:40:00 UTC
lo0 was not added to network_interface in rc.conf. This breaks lot-o-stuff

How-To-Repeat: I loaded from CD so i did the netconfig sometime after install.
network_interface was set to "fxp0 auto".  I would think sysconfig would 
setup lo0 in all cases.
Comment 1 Sheldon Hearn freebsd_committer freebsd_triage 1999-10-01 11:02:15 UTC
State Changed
From-To: open->closed

The release errata for 3.3-RELEASE explain the problem and a work-around. 
http://www.freebsd.org/releases/3.3R/errata.html 
Comment 2 Sheldon Hearn freebsd_committer freebsd_triage 1999-10-01 11:51:13 UTC
State Changed
From-To: closed->open

As reported by Ruslan Ermilov the problem is still not fixed. 


Comment 3 Sheldon Hearn freebsd_committer freebsd_triage 1999-10-01 11:51:13 UTC
Responsible Changed
From-To: freebsd-bugs->ru

Ruslan requested that this PR be re-opened. 
Comment 4 ru freebsd_committer freebsd_triage 1999-10-05 13:36:26 UTC
State Changed
From-To: open->feedback

Fixed in src/release/sysinstall/tcpip.c,v 1.96 (in -CURRENT). 


Comment 5 ru freebsd_committer freebsd_triage 1999-10-05 13:36:26 UTC
Responsible Changed
From-To: ru->jkh

So Jordan remembers to MFC. 
Comment 6 ru freebsd_committer freebsd_triage 1999-10-06 08:34:55 UTC
State Changed
From-To: feedback->closed

Fixed in 3.3-STABLE (src/release/sysinstall/tcpip.c,v 1.74.2.10).