Use chain.c32 rather than LOCALBOOT -1

Bug #898838 reported by Dave Walker
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cobbler (Ubuntu)
Fix Released
Undecided
Andres Rodriguez

Bug Description

...
LABEL local
        MENU LABEL (local)
        MENU DEFAULT
        LOCALBOOT -1

...

localboot $value, has varying degrees of success depending on the hardware. It is also seems to be incompatible with using ipxe.

Switching to:
...
LABEL local
        KERNEL chain.c32
...

Seems to provide a more reliable boot experience, and is also compatible with ipxe.

..

chain.c32 needs to be installed to /var/lib/tftpboot/ (where menu.c32 currently is, provided by the same syslinux depends.)

Thanks.

Related branches

Dave Walker (davewalker)
Changed in cobbler (Ubuntu):
milestone: none → precise-alpha-2
Revision history for this message
Dave Walker (davewalker) wrote :

(ARM will require special-casing)

Changed in cobbler (Ubuntu):
assignee: nobody → Andres Rodriguez (andreserl)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cobbler (Ubuntu):
status: New → Confirmed
Changed in cobbler (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cobbler - 2.2.2-0ubuntu7

---------------
cobbler (2.2.2-0ubuntu7) precise; urgency=low

  * debian/patches:
    - 45_add_gpxe_support.patch: Updated to only use menu.gpxe when gpxe
      is enabled and not always. (LP: #8417268)
    - 61_ubuntu_pxe_chainc32_default.patch: Use chain.c32 for localboot,
      rather than 'LOCALBOOT -1' by default. (LP: #898838)
 -- Andres Rodriguez <email address hidden> Tue, 06 Dec 2011 17:15:41 -0500

Changed in cobbler (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Nish Aravamudan (nacc) wrote :

Just would like to point out this patch, which was picked up by Debian, breaks `cobbler sync` by default. I'm planning on dropping it, because it's clearly not being maintained and is an unnecessary (afaict) divergence from upstream (and if it's not, then the patch shoudl have been sent upstream).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.