Re: custom Kernel

To: debian-live@lists.debian.org
Subject: Re: custom Kernel
From: Machu Chukov <m.chukov@gmx.de>
Date: Sun, 25 Sep 2016 18:57:42 +0200
Message-id: <[🔎] de37cf05-89fd-5a3f-a028-10e59c3c06bd@gmx.de>
In-reply-to: <[🔎] DUB128-W75FDFE4DDA502B36072BBCABCA0@phx.gbl>
References: <[🔎] 168fe7b6-cc1f-47d0-25c3-2cec9478d84b@gmx.de> <[🔎] DUB128-W75FDFE4DDA502B36072BBCABCA0@phx.gbl>



Am 25.09.2016 um 14:24 schrieb Kristian Klausen:

Hello Marchu

Just use live-boot from jessie-backports, which support overlayfs.
aufs was removed from the Debian kernel when overlayfs was mainlined.

- Kristian

Hello Kristian,

That works, thanks for the hint.

Now I have two Kernels and two Initrds in my /live directory (in the ISObinary), my patched custom one (4.6.4.xx) and the default jessie-kernel.How can I prevent, that the default Kernel vmlinuz-3.16.0-4-amd64 andits Initrd are copied to the /live-directory in binary stage?

The default Kernel is not listed in any of the files inconfig/package-lists/*


kind regards
Machu

Reply to:

Follow-Ups:
- RE: custom Kernel
  - From: Kristian Klausen <klausenbusk@hotmail.com>

References:
- custom Kernel
  - From: Machu Chukov <m.chukov@gmx.de>
- RE: custom Kernel
  - From: Kristian Klausen <klausenbusk@hotmail.com>

Prev by Date: RE: custom Kernel
Next by Date: Re: custom Kernel
Previous by thread: RE: custom Kernel
Next by thread: RE: custom Kernel
Index(es):
- Date
- Thread