Juanjo Pablos <jua...@apertus.es> wrote on 06/06/2011 01:19:15 PM:
> El 06/06/11 18:12, Timothy J Massey escribió:
> > The idea of reengineering the entire boot CD creation process is not
> > appealing to me, especially considering my *very* modest needs. I just
> > want a boot CD that doesn't require user input. Now that we've fixed
> > my booting problems, I don't even need to build my own CD to do that.
> > I can modify the stock ISO to achieve that.
> >
> I have just upload a 4.9 release here:
> https://sourceforge.net/projects/unattended/files/unattended/4.9/
> as far as I know there is no need for user input.
While it is possible to use the CD without requiring user input, there are
certain things that the CD configuration requires (such as the name of the
server) that are not easy to do with our environment. Therefore, the
default CD has always required user input for us, for reasons that are
hard-coded into the CD.
> > But now that I've got a build process working, I will probably stick
> > with my custom CD for this year. It has a big advantage in reducing
> > the timeout for missing Broadcom firmware from 60 seconds to 1 second.
> > Incidentally, seeing as firmware loading is broken on the CD, I'm not
> > sure why the default isn't reduced anyway...
> I have no idea what are you talking about.. sorry.
Some NIC drivers expect to be able to load firmware into the device.
Broadcom devices are such ones. The systems we are loading have Broadcom
NIC's. They therefore pause for a long time (60 seconds? more?) waiting
for firmware to materialize. Unfortunately, firmware loading requires
hotplug and udev, which the boot CD does not seem to use. In other words,
AFAICT, firmware loading is impossible with the boot CD. So why are we
waiting?
So, we set the firmware timeout to 1 second.
> > All I want out of the build process is a way to easily remove DOSEMU
> > seeing as most of my by-hand hassles are caused by it not building
> > with the same version of GCC as everything else--and seeing as I don't
> > use DOSEMU, you would think that would be easy. But it's not. So, I
> > deal with my convoluted build process.
> I thought that this line could fix your problem:
> "Default", ntinstall_cmd,nt5x-install
Not how to *use* the nt5x install. How do we modify the Makefile to
*avoid* compiling DOSEMU? DOSEMU breaks the compile, so we would like to
avoid compiling it. I haven't been able to figure out how to remove it
from the compile process.
Timothy J. Massey
Out of the Box Solutions, Inc.
Creative IT Solutions Made Simple!
http://www.OutOfTheBoxSolutions.com
tmas...@obscorp.com
22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
unattended-devel mailing list
unattended-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-devel
