Lamont Lucas wrote:
I recently upgraded my jumpstart server from 5.5 to 6.1 and have had
some issues getting the new jumpstart process working.
Specifically, while using my old install.cfg, my new machines were not
being built with a kernel.
I figured out that the sysinstall manpage is
On Fri, Jun 02, 2006 at 04:06:21PM +0200, Erik Nørgaard wrote:
Lamont Lucas wrote:
Specifically, while using my old install.cfg, my new machines were not
being built with a kernel.
*snip*
If you do not have a installCommit at the end of your install.cfg the
sysinstall should fall back on
Lamont Lucas wrote:
On Fri, Jun 02, 2006 at 04:06:21PM +0200, Erik Nørgaard wrote:
If you do not have a installCommit at the end of your install.cfg the
sysinstall should fall back on the normal interactive interface and you
can verify that your settings have been applied.
I do indeed have
Erik Nørgaard wrote:
For clarity, I'm attaching my install.cfg to see if anybody can figure
out why it's not installing a kernel. To work around this, I think
I'm going to make a pkg of my kernel and install it along with the
rest of the packages.
Workarounds are ok, but I think that
On Fri, Jun 02, 2006 at 10:03:55PM +0200, Erik Nørgaard wrote:
Maybe I did not make myself clear, my idea is that if you disable the
installCommit you will get back to the interactive sysinstall and you
can run over the menus to see if things are actually set as you want.
Ah, I did not
I recently upgraded my jumpstart server from 5.5 to 6.1 and have had
some issues getting the new jumpstart process working.
Specifically, while using my old install.cfg, my new machines were not
being built with a kernel.
I figured out that the sysinstall manpage is out of date and as of 6.x
