This must be a really obvious thing, yet I couldn't find a solution for
this for years... so I have to ask here.
Debian-live (Jessie) uses aufs for its root filesystem, and by default
the amount of space available is half the total size of RAM. Sometimes I
need more space, and I have plenty of
Hello Marchu
Take a look at:
https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html#435
Should explain it, I think.
- Kristian
> Subject: Re: custom Kernel
> To: debian-live@lists.debian.org
> From: m.chu...@gmx.de
> Dat
d.luv e Www sweeter
Sent from my Samsung Galaxy smartphone. Original message
From: Machu Chukov
Date: 09/25/2016 11:57 AM (GMT-06:00)
To: debian-live@lists.debian.org
Subject: Re: custom Kernel
Am 25.09.2016 um 14:24 schrieb Kristian Klausen:
> Hello Marchu
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
Hello Marchu
Just use live-boot from jessie-backports, which support overlayfs.
aufs was removed from the Debian kernel when overlayfs was mainlined.
- Kristian
> To: debian-live@lists.debian.org
> From: m.chu...@gmx.de
> Subject: custom Kernel
> Date: Su
Hi guys,
I've built a custom Backport-Kernel for a jessie-live-system. It's based
on the source-package of the recent Kernel in jessie-backports. I added
some patches, made my config, created a deb.-Package. The same process
worked well with the jessie-Kernel, but the backport-kernel doesn't
Since I have found little documentation on this issue, I wanted to
briefly summarize my results creating an UEFI-bootable Isohybrid-Image.
Just in case that perhaps they could be useful for someone.
Both packages work for me with the following differences:
*live-build package provided by Kali-
