6.1 jumpstart issues

Erik Nørgaard norgaard at locolomo.org
Fri Jun 2 13:04:25 PDT 2006

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 an installCommit after the regular sysinstall
> stuff (but before my package adds)  The issue is not that my
> jumpstart fails to run, or run unattended.  The problem is that once
> made, my jumpstarted machines have no kernel.  And adding an explicit
> kernels dist to my list of dists to install did nothing that I could
> tell.  There is probably something useful in the debug, but it
> scrolls past so fast that I can't even see it.

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.

If you find an empty kernel check box, write down the name of the menu
option and grep it in the source.

This new kernel dist is unknown to me, I looked at the source and it
seems that the idea is to let you choose to install an smp kernel or
standard generic kernel.

I just tried to use the sysinstall interactively and indeed, when you
choose the kernels dist under distributions a new menu appears where you
are supposed to select the kernel(s) you want. By default, none is selected.

> 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 everyone would benefit from the
correct solution, if this new dist breaks the jumpstart installation
then a pr should be filed.

So, in short, it appears that the correct solution will be one of:

a) figure out the option that selects the kernel, or
b) hack sysinstall to set a reasonable default kernel to install,
   write a pr with a patch

I think that in any case a pr should be filed, even if there is an
option available for the install.cfg. A good default for the kernels
dist is to install the generic kernel which will work on both smp and
non-smp systems. Having none selected doesn't make sense.

Cheers, Erik

Ph: +34.666334818                      web: http://www.locolomo.org
X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt
Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4128 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20060602/ad474217/smime.bin

More information about the freebsd-questions mailing list