Le 12/02/2016 15:19, Corey Velan a écrit :
Worked for me! Thanks David.
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.....)
David
Corey
On Thu, Feb 11, 2016 at 6:23 PM, Michael . <[email protected]
<mailto:[email protected]>> wrote:
Can you be a little more specific with what folder you placed them in?
On 11 February 2016 at 18:52, David Ansart <[email protected]
<mailto:[email protected]>> wrote:
Hi
I download (not install) sid version of live-boot
and live-boot-initramfs-tools.
Then, before the build. i put them into the folder of .deb
file of my live project
David
2016-02-11 3:05 GMT+00:00 Michael . <[email protected]
<mailto:[email protected]>>:
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.
Cheers.
Michael.
On 11 February 2016 at 13:00, Corey Velan
<[email protected]
<mailto:[email protected]>> wrote:
Hi David,
Did you end up finding a way to get live-boot to work
with the 4.3 kernel in jessie-backports? I'm hitting
the same issue as you.
Thanks,
Corey
On Sat, Nov 21, 2015 at 5:36 AM, David Ansart
<[email protected] <mailto:[email protected]>>
wrote:
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 ?
Must i install other things ?
#
>----------------------------------------------------------------------------
lb config noauto --distribution jessie
--binary-images iso-hybrid --architectures amd64
--linux-flavours amd64 \
--archive-areas "main contrib" --apt-indices false
--backports true --updates true \
--memtest memtest86+ \
--mirror-bootstrap
http://ftp.fr.debian.org/debian/ --mirror-binary
http://ftp.fr.debian.org/debian/ \
--bootappend-live "boot=live union=overlay
components locales=en_US.UTF-8 hostname=minimal \
username=user noautologin"
cat /dev/null > config/package-lists/my.list.chroot
echo task-english >>
config/package-lists/my.list.chroot
echo task-ssh-server >>
config/package-lists/my.list.chroot
echo '! Packages Priority standard' >
config/package-lists/standard.list.chroot
#@source:
http://live.debian.net/manual/4.x/html/live-manual.en.html
#echo "live-tools user-setup sudo eject" >
config/package-lists/necessaire.list.chroot
cat > config/archives/backport.pref.chroot <<EOF
Package: *
Pin: release n=jessie
Pin-Priority: 500
Package: *
Pin: release n=jessie-backports
Pin-Priority: 500
EOF
#
----------------------------------------------------------------------------
--
Corey Velan
Co-founder
514.220.8207
[email protected] <mailto:[email protected]>
www.FixMeStick.com <http://www.FixMeStick.com>
