>Number: 135317
>Category: conf
>Synopsis: install.cfg feature request
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Jun 06 22:30:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Adam Wien
>Release: 7.1-RELEASE
>Organization:
cPanel of Texas, Inc.
>Environment:
FreeBSD dotproject.cptxoffice.net 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>Description:
You have to supply a network interface when doing automated network installs using install.cfg
netDev=em0 for example
This causes a problem when trying to use the same install.cfg across multiple hardware platforms. I can understand this kind of granularity when supplying hard disks but, for network, it makes more sense not to.
>How-To-Repeat:
Generate an install.cfg for automated network installation.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"