Snapcraft

kernel plugin: hard link vmlinuz to kernel.img

Bug #1611435 reported by Paolo Pisati
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
New
Undecided
Unassigned

Bug Description

One of the changes in the latest kernel snap model was the rename of the kernel file from vmlinuz to kernel.img, thus we need to obey to changes else the bootlader won't find our kernel file.

Attached is patch that does just that, and makes the kernel created using the snapcraft pluging usable again - sideloading a kernel is broken ATM, but you can create bootable images nonetheless.

Revision history for this message
Paolo Pisati (p-pisati) wrote :
Revision history for this message
Oliver Grawert (ogra) wrote :

please do not tie this faeture to teh kernel plugin but rather to "type: kernel" ... there are kernel snap builds that just use the make plugin for example (i.e. our default kernel snaps use this)

Revision history for this message
Paolo Pisati (p-pisati) wrote :

The only place where "type: kernel' seems to make a difference is in internal/meta.py::_compose_snap_yaml() where it collect the kernel keys, other than that i don't see it used anywhere.

Revision history for this message
Paolo Pisati (p-pisati) wrote :

https://github.com/snapcore/snapcraft/pull/747

Revision history for this message
Oliver Grawert (ogra) wrote :

well, it is perfectly fine to write your own plugin to roll a kernel, to use a binary tarball with the dump (formerly copy) plugin or to use a make plugin to populate the build, "type: kernel" is the one thing they all have in common, so the handling of the required resulting binary name should be bound to the type, not to some plugin.

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

Other bug subscribers

Remote bug watches

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