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.
My server name and share name do not match the CD, for one thing, and I
have multiple client packages available. Therefore, I have to have
customized CD's if I want it to be fully automatic. This will actually be
the first year I will achieve that! :)
> > 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.
The driver for Broadcom NIC's request that updated firmware be loaded into
them. The ISO does not support loading firmware (it requires
hot-plug/udev), so it fails, but not until after waiting for a long
timeout (60 seconds, IIRC). Fortunately, they have on-board firmware, so
they still work, but the pause is very annoying, especially if I have to
type something in.
To avoid this, I manually set the kernel firmware loading timeout to 3
seconds. Seeing as firmware loading doesn't work anyway, I'm not sure why
the default isn't shorter.
I don't have easy access to the server right now, but here's what I have
in my notes: in misc/master, immediately after the line:
echo "*** Next, we'll look for PCI Ethernet hardware...:
Add the following:
echo "First, let's try to reduce the firmware delay..."
echo 3 > /sys/class/firmware/timeout
> > 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
This is the first I've heard of it. I assume I'm supposed to remove the
"ntinstall_cmd," part? I'll try it on Thursday.
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
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
unattended-devel mailing list
unattended-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-devel
