problems packaging kernel

[Hajo Locke]

Hello,

Am 08.07.2019 um 14:03 schrieb Ralf Mardorf via ubuntu-users:
> On Mon, 8 Jul 2019 13:37:43 +0200, Liam Proven wrote:
>> OK, so, next question. If you need to run something on 14.04 and it's
>> out of support: why?
> The OP mentioned that it's a temporary solution:
>
> On Mon, 8 Jul 2019 09:38:50 +0200, Hajo Locke wrote:
>> We still have ~3000 Servers with ubuntu14, this is just a try to bridge
>> a short time until we upgrade them.
yes, thanks Ralf for explaining.

I do some tests with the stuff and write back if i know something better.
I followed the steps here: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
I received xenial sources that way and compiled like described, but ends
up with same errormessage:

# Some initramfs-tools specific modules
install -d
/usr/src/ubuntu-xenial/debian/linux-modules-4.4.0-154-generic/lib/modules/4.4.0-154-generic/initrd
if [ -f
/usr/src/ubuntu-xenial/debian/linux-modules-4.4.0-154-generic/lib/modules/4.4.0-154-generic/kernel/drivers/video/vesafb.ko
]; then\
           ln -sf
/usr/src/ubuntu-xenial/debian/linux-modules-4.4.0-154-generic/lib/modules/4.4.0-154-generic/kernel/drivers/video/vesafb.ko
\
/usr/src/ubuntu-xenial/debian/linux-modules-4.4.0-154-generic/lib/modules/4.4.0-154-generic/initrd/;
\
         fi
echo "interest linux-update-4.4.0-154-generic"
 >"debian/linux-image-unsigned-4.4.0-154-generic.triggers"
# Install the postinit/postrm scripts in the extras package.
if [ -f debian.master/control.d/generic.inclusion-list ] ; then \
                 ; \
         fi
/bin/bash: -c: line 1: syntax error near unexpected token `;'
make: *** [install-generic] Fehler 2

same tripwires... may be ubuntu needs some reasons for selling
esm-service ;)

Last week i tried another appoach. i kept original-kernel (3.13) and
created patches  with quilt from debian jessie (3.16 - still maintained)
package. basically i did the same way and this was working but compared
to just recompiling a xenial-package much more effort. and effort will
increase with growing differences between a maintained and outdated kernel.
Its just a try to be prepared for next kernel bug which can not be
resolved with a workaround.

Hmm, i try some other ideas...
>
Thanks,
Hajo