Michael- if you put them in config/packages.chroot/, then
live-build will use them instead of the older ones.
Yes, it is that. Thanks Corey
(Sorry for the delay : I can't see my own code now, and i couldn't
see the manual page because the new site of Live Build is
empty.....)
This has only just happened
to me in the last few days.
Yesterday I built a live image
with MATE and backported kernel.
Today I built a minimal iso with
TinyWM and a backported kernel.
Neither will boot into a live
session but both will install and
then boot into the fresh
installation.
On Thursday 19
November 2015
18:59:42 David
Ansart wrote:
> > Does
it work without
backports
enabled?
> > I
build an image
(with live-build
5.0~a11-1) from
a config I had
laying
> > around
with jessie, but
without
backports and
that seems to
work.
>
> Yes. If i
disable
backport, the
iso boots
correctly.
Without
backports you'd
get
linux-image-3.16.0-4-amd64
and with
backports I
think you'd get
linux-image-4.2.0-0.bpo.1-amd64
so I'm guessing
the problem is
indeed with
overlayfs and I
don't know how
to fix that. It
could be that it
is
supported but
you forget some
config setting
or it just
doesn't work
properly.
What you could
try is create a
preference file
so that the
kernel is taken
from jessie and
not
jessie-backports
(ie pin to
version 3.16.*
or sth like
that) and see
whether it works
then. If it does
work, you could
stick with
that and/or dive
deeper into
getting it to
work with
overlayfs.
I know but I prefer a
more generic solution.
I do not like adding
exceptions.
If I could know the
package to be watched.
I have installed Live
boot 5.0~a11-2 0
I have added
"union=overlay" into
bootappend-live :
--bootappend-live
"boot=live
union=overlay
components
locales=en_US.UTF-8
hostname=minimal
username=user
noautologin"
But it isn't work.
Live boot must be
compatible with
overlayfs, must not I
?