lb build TypeError
When I try to run lb build¹ it chugs through all the processes until it
tries to perform the shutil.copy. Then it spits out the below message and
stops running:
[2014-08-07 22:22:30] lb chroot_install-packages live
P: Begin installing packages (live pass)...
[2014-08-07 22:22:30] lb chroot-includes
[2014-08-07 22:22:30] lb chroot-hooks
Traceback (most recent call last):
File "/usr/lib/live/build/chroot-hooks", line 108, in
main()
File "/usr/lib/live/build/chroot-hooks", line 87, in main
shutil.copy(hook, os.path.join('chroot/live-build/' +
os.path.basename(hook)), follow_symlinks=True)
TypeError: copy() got an unexpected keyword argument 'follow_symlinks'
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...
Reading state information...
dando@demon:~/live-default$
I have tried a few things including install the latest live-build from git
and updating python to 3.2 as live-build 4 requires python >= 3.2 and
verified chroot-hooks is executing with 3.2, but to no avail. Internet
searches have not revealed much other than it was mentioned on this list
prior but without a resolution that I could find.
Cheers!
Zed
Re: ISO failure
I have run into the same issue using the same version of lb.
# lb --version
4.0~alpha39-1
I¹ve enabled verbose and debugging and see the following:
[2014-08-12 22:49:31] lb binary_iso
D: Reading configuration file config/bootstrap
D: Reading configuration file config/chroot
D: Reading configuration file config/binary
D: Reading configuration file config/source
P: Begin building binary iso image...
mv: cannot stat binary¹: No such file or directory
// sets all the LB variables from the config/ files
P: Begin unmounting filesystems...
P: Saving caches...
D: Executing: apt-get autoclean
Reading package lists...
Building dependency tree...
Reading state information
#
Checking the /usr/lib/live/build/binar_iso file I see the following on lines
200-217, which is where the mv is taking place:
case "${LB_BUILD_WITH_CHROOT}" in
true)
# Moving image
mv binary.sh chroot
mv binary chroot
Chroot chroot "sh binary.sh"
# Move image
mv chroot/binary chroot/${IMAGE} ./
rm -f chroot/binary.sh
;;
false)
sh binary.sh
rm -f binary.sh
;;
esac
I didn¹t have time to look into it further, but I will, and if I find
anything will answer back. Maybe this will point someone else in the right
direction though Still learning the lb tool set.
Zed
From: Anthony F McInerney
Date: Sat, 9 Aug 2014 14:06:12 +0100
To: Debian-live mailing list
Subject: ISO failure
Resent-From:
Resent-Date: Sat, 9 Aug 2014 13:06:31 + (UTC)
lb --version
4.0~alpha39-1
P: Begin building binary iso image...
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
libisoburn1
Suggested packages:
jigit cdck
The following NEW packages will be installed:
isolinux libisoburn1 xorriso
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 463 kB/553 kB of archives.
After this operation, 1231 kB of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian/ jessie/main libisoburn1 amd64 1.3.2-1
[329 kB]
Get:2 http://ftp.us.debian.org/debian/ jessie/main xorriso amd64 1.3.2-1
[134 kB]
Fetched 463 kB in 1s (289 kB/s)
Selecting previously unselected package isolinux.
(Reading database ... 107831 files and directories currently installed.)
Preparing to unpack .../isolinux_3%3a6.03~pre18+dfsg-1_amd64.deb ...
Unpacking isolinux (3:6.03~pre18+dfsg-1) ...
Selecting previously unselected package libisoburn1.
Preparing to unpack .../libisoburn1_1.3.2-1_amd64.deb ...
Unpacking libisoburn1 (1.3.2-1) ...
Selecting previously unselected package xorriso.
Preparing to unpack .../xorriso_1.3.2-1_amd64.deb ...
Unpacking xorriso (1.3.2-1) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up isolinux (3:6.03~pre18+dfsg-1) ...
Setting up libisoburn1 (1.3.2-1) ...
Setting up xorriso (1.3.2-1) ...
Processing triggers for libc-bin (2.19-7) ...
xorriso 1.3.2 : RockRidge filesystem manipulator, libburnia project.
Drive current: -outdev 'stdio:live-image-amd64.hybrid.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 231g free
xorriso : NOTE : -as mkisofs: Ignored option '-cache-inodes'
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules
Added to ISO image: directory '/'='/binary'
xorriso : UPDATE : 581 files added in 1 seconds
xorriso : UPDATE : 581 files added in 1 seconds
xorriso : NOTE : Copying to System Area: 432 bytes from file
'/usr/lib/ISOLINUX/isohdpfx.bin'
xorriso : FAILURE : Cannot find in ISO image: -boot_image ...
bin_path='/isolinux/isolinux.bin'
xorriso : NOTE : -return_with SORRY 32 triggered by problem severity FAILURE
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...
Reading state information...
Del parted 3.2-1 [194 kB]
Del busybox 1:1.22.0-6 [388 kB]
Del openssl 1.0.1h-3 [668 kB]
Del libtwolame0 0.3.13-1 [60.2 kB]
Del libparted-fs-resize0 3.2-1 [199 kB]
Del libparted2 3.2-1 [268 kB]
Del libbsd0 0.6.0-2 [63.5 kB]
Re: ISO failure
On 8/12/2014 11:05 PM, Zed wrote:
I have run into the same issue using the same version of lb.
# lb --version
4.0~alpha39-1
I’ve enabled verbose and debugging and see the following:
[2014-08-12 22:49:31] lb binary_iso
D: Reading configuration file config/bootstrap
D: Reading configuration file config/chroot
D: Reading configuration file config/binary
D: Reading configuration file config/source
*P*: Begin building binary iso image...
mv: cannot stat ‘binary’: No such file or directory
// sets all the LB variables from the config/ files
*P*: Begin unmounting filesystems...
*P*: Saving caches...
D: Executing: apt-get autoclean
Reading package lists...
Building dependency tree...
Reading state information…
#
Checking the /usr/lib/live/build/binar_iso file I see the following on
lines 200-217, which is where the mv is taking place:
case*"${LB_BUILD_WITH_CHROOT}"*in
true)
# Moving image
*mv* binary.sh chroot
*mv* binary chroot
Chroot chroot *"sh binary.sh"*
# Move image
*mv* chroot/binary chroot/*${IMAGE}* ./
*rm* -f chroot/binary.sh
;;
false)
sh binary.sh
*rm* -f binary.sh
;;
esac
I didn’t have time to look into it further, but I will, and if I find
anything will answer back. Maybe this will point someone else in the
right direction though… Still learning the lb tool set.
Zed
From: Anthony F McInerney mailto:afm...@gmail.com>>
Date: Sat, 9 Aug 2014 14:06:12 +0100
To: Debian-live mailing list <mailto:debian-live@lists.debian.org>>
Subject: ISO failure
Resent-From: <mailto:debian-live@lists.debian.org>>
Resent-Date: Sat, 9 Aug 2014 13:06:31 + (UTC)
lb --version
4.0~alpha39-1
P: Begin building binary iso image...
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
libisoburn1
Suggested packages:
jigit cdck
The following NEW packages will be installed:
isolinux libisoburn1 xorriso
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 463 kB/553 kB of archives.
After this operation, 1231 kB of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian/ jessie/main libisoburn1 amd64
1.3.2-1 [329 kB]
Get:2 http://ftp.us.debian.org/debian/ jessie/main xorriso amd64
1.3.2-1 [134 kB]
Fetched 463 kB in 1s (289 kB/s)
Selecting previously unselected package isolinux.
(Reading database ... 107831 files and directories currently installed.)
Preparing to unpack .../isolinux_3%3a6.03~pre18+dfsg-1_amd64.deb ...
Unpacking isolinux (3:6.03~pre18+dfsg-1) ...
Selecting previously unselected package libisoburn1.
Preparing to unpack .../libisoburn1_1.3.2-1_amd64.deb ...
Unpacking libisoburn1 (1.3.2-1) ...
Selecting previously unselected package xorriso.
Preparing to unpack .../xorriso_1.3.2-1_amd64.deb ...
Unpacking xorriso (1.3.2-1) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up isolinux (3:6.03~pre18+dfsg-1) ...
Setting up libisoburn1 (1.3.2-1) ...
Setting up xorriso (1.3.2-1) ...
Processing triggers for libc-bin (2.19-7) ...
xorriso 1.3.2 : RockRidge filesystem manipulator, libburnia project.
Drive current: -outdev 'stdio:live-image-amd64.hybrid.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 231g free
xorriso : NOTE : -as mkisofs: Ignored option '-cache-inodes'
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119
rules
Added to ISO image: directory '/'='/binary'
xorriso : UPDATE : 581 files added in 1 seconds
xorriso : UPDATE : 581 files added in 1 seconds
xorriso : NOTE : Copying to System Area: 432 bytes from file
'/usr/lib/ISOLINUX/isohdpfx.bin'
xorriso : FAILURE : Cannot find in ISO image: -boot_image ...
bin_path='/isolinux/isolinux.bin'
xorriso : NOTE : -return_with SORRY 32 triggered by problem severity
FAILURE
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...
Reading state information...
Del parted 3.2-1 [194 kB]
Del busybox 1:1.22.0-6 [388 kB]
Del openssl 1.0.1h-3 [668 kB]
Del libtwolame0 0.3.13-1 [60.2 kB]
Del libparted-fs-resize0 3.2-1 [199 kB]
Del libparted2 3.2-1 [268 kB]
Del libbsd0 0.6.0-2 [63.5 kB]
After some more digging this morning, I see that the binary_iso script
is not creating the iso that is required. Still digging in.
Re: ISO failure
The end error was the same, but he did not have the 'mv' error. The strange part is, after the failure when I check, 'binary' is in fact there. I will keep digging, but it seems strange to receive that error when the location does exist. I have run into other issues with the isolinux config i am using in /cofing/bootstrap as well, so I definately have a few things to iron out. Cherers! On 8/17/2014 4:53 PM, Ben Armstrong wrote: Zed, I don't think yours is the same issue: On 13/08/14 02:05 AM, Zed wrote: I have run into the same issue using the same version of lb. # lb --version 4.0~alpha39-1 I’ve enabled verbose and debugging and see the following: [2014-08-12 22:49:31] lb binary_iso D: Reading configuration file config/bootstrap D: Reading configuration file config/chroot D: Reading configuration file config/binary D: Reading configuration file config/source *P*: Begin building binary iso image... mv: cannot stat ‘binary’: No such file or directory If you look at Anthony's output, he did not have this error. If 'binary' is not there, something went seriously wrong earlier. If you had an earlier failure in the binary stage and wanted to rebuild just the binary stage, you may not be able to clean it with just 'lb clean --binary' (I found I needed to manually rm -rf chroot/binary). Try from a completely clean workspace, and if you get this error again, please include more context, as there may have been earlier errors you overlooked. Ben
Just a thank you
I wanted to thank the Debian-Live community for the assistance in building my first installable live-cd. I have learned a lot and am now building ISOs with the customized Debian-based distro I have wanted to build for a long time. Now that I am starting to understand the ins and outs, I am looking forward to paying it back and helping the cause. I plan on updating my github to reflect my changes in case anyone is interested today\tonight. https://github.com/mrzed/ I will have two new repos: lily-live-mate_64 lily-live-xfce4_64 These will be getting updated as I progress, but will work as-is once posted. I found looking at others work to see how it was working assisted in deciphering many of my questions. Special thanks to Anthony McInerney for sharing his git with me and getting me started. Thank you again, Zed (Devin) -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53f3c5eb.9020...@lilypadmudlib.com
Re: Status 'maybe-failed' with no ISO file
If you want to build a simple one, here are the basics: Ensure you have the live-build prerequisites met\installed. mkdir cd lb init lb config Next, modify the following files and replace your current system build with jessie: ./config/bootstrap:LB_DISTRIBUTION="jessie" ./config/bootstrap:LB_PARENT_DISTRIBUTION="jessie" ./config/bootstrap:LB_PARENT_DEBIAN_INSTALLER_DISTRIBUTION="jessie" ./config/build:Distribution: jessie ./config/binary:LB_DEBIAN_INSTALLER_DISTRIBUTION="jessie" ./config/binary:LB_ISO_VOLUME="Debian jessie $(date +%Y%m%d-%H:%M)" lb build 2>&1 |tee build.log I am not able to test this right now as I am working, but give it a shot and see if it works for you. If it fails, details will be in the build.log in the dir. Cheers! Zed On 8/22/2014 4:06 PM, pietro@tiscali.it wrote: It's true, I tried to build sid, I did not know that it was impossible. But now I tried to build jessie and I got the same error: http://cgi.build.live-systems.org/build/20140822.214850.387890629/ I want to test Debian Live on my Dell XPS 12, I already tried latest wheezy 7.6.0 Live CD with some problems (wireless adapter not found, Gnome failed to full install...), so I wanted to try jessie or sid before installing. I cannot upgrade wheezy to sid or jessie using a Live CD without rebooting, so how can I build a Live CD with jessie or sid? Thank you Pietro Il 22.08.2014 22:36 chals ha scritto: On Fri, Aug 22, 2014 at 10:07 PM, Richard Nelson mailto:unix...@gmail.com>> wrote: Greetings, On Thu, Aug 21, 2014 at 9:46 AM, <mailto:pietro@tiscali.it>> wrote: I started two builds but both ended with status 'maybe-failed' and ISO file is not produced: http://cgi.build.live-systems.org/build/20140821.130938.270493711/ http://cgi.build.live-systems.org/build/20140821.144237.312095495/ Can you explain why and how to get success? Thank you Pietro The builds were removed before I could examine. Could you build another or forward your build request and I will attempt to examine. I took a quick look at the build configuration (not the actual logs). I noticed that he chose "sid" as distribution. I do not know which live-build version is currently installed on the images autobuilder (for it does not appear at the bottom of the page as it used to) but I took for granted that the images didn't build correctly just because of that, trying to build sid, that is :) Have a nice weekend! -- chalswww.chalsattack.com <http://www.chalsattack.com> ch...@chalsattack.com <mailto:ch...@chalsattack.com> Scopri istella, il nuovo motore per il web italiano. Istella garantisce risultati di qualità e la possibilità di condividere, in modo semplice e veloce, documenti, immagini, audio e video. Usa istella, vai su http://www.istella.it?wtk=amc138614816829636
debian-installer-launcher
I have added the debian-installer-launcher to my live-build and added a desktop icon to launch the installer. Everything works fine, but when the install is finished, I have to manually disconnect the ISO and manually reboot. Where\what can I modify to automate the last steps of the install? I want it to function and complete more like the default Debian install does. I assume I need to modify the preseed.cfg, but I am not sure what exactly to look at to get it to behave the desired way. The manual didn't have specifics I was looking for (unless I completely overlooked them). Thanks! Zed -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54009bea.6080...@lilypadmudlib.com
Re: debian-installer-launcher
I believe I have figured this out... *fingers crossed* Cheers! Z On 8/29/2014 9:27 AM, Zed wrote: I have added the debian-installer-launcher to my live-build and added a desktop icon to launch the installer. Everything works fine, but when the install is finished, I have to manually disconnect the ISO and manually reboot. Where\what can I modify to automate the last steps of the install? I want it to function and complete more like the default Debian install does. I assume I need to modify the preseed.cfg, but I am not sure what exactly to look at to get it to behave the desired way. The manual didn't have specifics I was looking for (unless I completely overlooked them). Thanks! Zed -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5400a774.5050...@lilypadmudlib.com
Re: debian-installer-launcher
Ok, I have the preseed.cfg done and in the /includes.installer/ directory, but when I run lb build, it is ignoring the preseed config. Here are two lines that I have in my preseed.cfg: d-i partman-auto/choose_recipe select atomic d-i apt-setup/use_mirror boolean false But, when I run the installer from the desktop when booted to the liveCD, I am still prompted for both. The entries for the automatic cdrom unmount and system reboot are also ignored. What do I need to change to ensure the preseed is picked up and used from the bootloader and from the desktop icon I have created? Thanks! On 8/29/2014 10:16 AM, Zed wrote: I believe I have figured this out... *fingers crossed* Cheers! Z On 8/29/2014 9:27 AM, Zed wrote: I have added the debian-installer-launcher to my live-build and added a desktop icon to launch the installer. Everything works fine, but when the install is finished, I have to manually disconnect the ISO and manually reboot. Where\what can I modify to automate the last steps of the install? I want it to function and complete more like the default Debian install does. I assume I need to modify the preseed.cfg, but I am not sure what exactly to look at to get it to behave the desired way. The manual didn't have specifics I was looking for (unless I completely overlooked them). Thanks! Zed
Re: debian-installer-launcher
Thanks to Daniel on IRC with a little direction I learned why it was skipping the preseed. Basically, I had not appended the parameters to the boot options in isolinux. It is copying the preseed to the ISO now, but it can't be located when the install is loading. I have my preseed here: /config/includes.binary/install/preseed.cfg When I browse the built ISO I find my file here: /media/cdrom0/install/preseed.cfg But, when I launch the debian-installer from the liveCD desktop, or from the boot menu I receive the error: "The file needed for preconfiguration could not be retrieved from file:///install/preseed.cfg. The installation will proceed in non-automated mode. I have tried various boot options to resolve, but receive the same error (with the file:/// as entered of course): append preseed/file=/install/preseed.cfg append preseed/file=/media/cdrom/install/preseed.cfg append preseed/file=/media/cdrom0/install/preseed.cfg Getting close, but no cigar as of yet... Zed On 8/29/2014 10:49 AM, Zed wrote: Ok, I have the preseed.cfg done and in the /includes.installer/ directory, but when I run lb build, it is ignoring the preseed config. Here are two lines that I have in my preseed.cfg: d-i partman-auto/choose_recipe select atomic d-i apt-setup/use_mirror boolean false But, when I run the installer from the desktop when booted to the liveCD, I am still prompted for both. The entries for the automatic cdrom unmount and system reboot are also ignored. What do I need to change to ensure the preseed is picked up and used from the bootloader and from the desktop icon I have created? Thanks! On 8/29/2014 10:16 AM, Zed wrote: I believe I have figured this out... *fingers crossed* Cheers! Z On 8/29/2014 9:27 AM, Zed wrote: I have added the debian-installer-launcher to my live-build and added a desktop icon to launch the installer. Everything works fine, but when the install is finished, I have to manually disconnect the ISO and manually reboot. Where\what can I modify to automate the last steps of the install? I want it to function and complete more like the default Debian install does. I assume I need to modify the preseed.cfg, but I am not sure what exactly to look at to get it to behave the desired way. The manual didn't have specifics I was looking for (unless I completely overlooked them). Thanks! Zed
Re: debian-installer-launcher
Here are all the configs in my isolinux dir. * isolinux.cfg:* include menu.cfg default vesamenu.c32 prompt 0 timeout 0 *menu.cfg* menu hshift 0 menu width 82 menu title Boot menu include stdmenu.cfg include live.cfg include install.cfg menu begin advanced menu title Advanced options include stdmenu.cfg label mainmenu menu label ^Back.. menu exit include advanced.cfg menu end menu clear *stdmenu.cfg* menu background splash.png menu color title* # * menu color border* # # none menu color sel* # #76a1d0ff * menu color hotsel1;7;37;40 # #76a1d0ff * menu color tabmsg* # # * menu color help37;40 #ff00 # none menu vshift 12 menu rows 10 menu helpmsgrow 15 # The command line must be at least one line from the bottom. menu cmdlinerow 16 menu timeoutrow 16 menu tabmsgrow 18 menu tabmsg Press ENTER to boot or TAB to edit a menu entry *live.cfg.in* label live-@FLAVOUR@ menu label ^Live (@FLAVOUR@) menu default linux @LINUX@ initrd @INITRD@ append preseed/file=/install/preseed.cfg @APPEND_LIVE@ label live-@FLAVOUR@-failsafe menu label ^Live (@FLAVOUR@ failsafe) linux @LINUX@ initrd @INITRD@ append @APPEND_LIVE_FAILSAFE@ *install.cfg* label install menu label ^Install linux /install/vmlinuz initrd /install/initrd.gz append preseed/file=/install/preseed.cfg vga=788 @APPEND_INSTALL@ -- quiet label installgui menu label ^Graphical install linux /install/gtk/vmlinuz initrd /install/gtk/initrd.gz append preseed/file=/install/preseed.cfg video=vesa:ywrap,mtrr vga=788 @APPEND_INSTALL@ -- quiet *advanced.cfg* label hdt menu label ^Hardware Detection Tool (HDT) com32 hdt.c32 label memtest menu label ^Memory Diagnostic Tool (memtest86+) linux /live/memtest I am still learning these scripts, so I appreciate any assistance. Cheers! Zed On 8/29/2014 1:57 PM, Stefan Baur wrote: Am 29.08.2014 um 21:51 schrieb Zed: I have tried various boot options to resolve, but receive the same error (with the file:/// as entered of course): append preseed/file=/install/preseed.cfg append preseed/file=/media/cdrom/install/preseed.cfg append preseed/file=/media/cdrom0/install/preseed.cfg Could you please post your complete isolinux.cfg (and any *.cfg files it may pull in additionally)? -Stefan
Re: debian-installer-launcher
I accidentally took the list of a few responses, and Stefan was kind enough to let me know, so here is the last communication I sent him (intending to go to the whole list) with the solution, or at least what appears to be so far: root@debian:/# find /lib/live -name "preseed.cfg" /lib/live/mount/medium/install/preseed.cfg I also verified that the preseed in that location is in fact mine. I changed the boot from: .linux /install/vmlinuz file=/install/preseed.cfg TO .linux /install/vmlinuz /install/preseed.cfg This worked!! Thank you, Stefan. I have been beating my head against the wall and you got me looking down the right path. Thanks to DBA on IRC and Fernando as well! I think I can update my configs now so they will work. I need to make sure I document some of these finer points so I don't forget. Haha! Cheers! Zed (Devin) On 8/29/2014 2:07 PM, Zed wrote: Here are all the configs in my isolinux dir. * isolinux.cfg:* include menu.cfg default vesamenu.c32 prompt 0 timeout 0 *menu.cfg* menu hshift 0 menu width 82 menu title Boot menu include stdmenu.cfg include live.cfg include install.cfg menu begin advanced menu title Advanced options include stdmenu.cfg label mainmenu menu label ^Back.. menu exit include advanced.cfg menu end menu clear *stdmenu.cfg* menu background splash.png menu color title* # * menu color border* # # none menu color sel* # #76a1d0ff * menu color hotsel1;7;37;40 # #76a1d0ff * menu color tabmsg* # # * menu color help37;40 #ff00 # none menu vshift 12 menu rows 10 menu helpmsgrow 15 # The command line must be at least one line from the bottom. menu cmdlinerow 16 menu timeoutrow 16 menu tabmsgrow 18 menu tabmsg Press ENTER to boot or TAB to edit a menu entry *live.cfg.in* label live-@FLAVOUR@ menu label ^Live (@FLAVOUR@) menu default linux @LINUX@ initrd @INITRD@ append preseed/file=/install/preseed.cfg @APPEND_LIVE@ label live-@FLAVOUR@-failsafe menu label ^Live (@FLAVOUR@ failsafe) linux @LINUX@ initrd @INITRD@ append @APPEND_LIVE_FAILSAFE@ *install.cfg* label install menu label ^Install linux /install/vmlinuz initrd /install/initrd.gz append preseed/file=/install/preseed.cfg vga=788 @APPEND_INSTALL@ -- quiet label installgui menu label ^Graphical install linux /install/gtk/vmlinuz initrd /install/gtk/initrd.gz append preseed/file=/install/preseed.cfg video=vesa:ywrap,mtrr vga=788 @APPEND_INSTALL@ -- quiet *advanced.cfg* label hdt menu label ^Hardware Detection Tool (HDT) com32 hdt.c32 label memtest menu label ^Memory Diagnostic Tool (memtest86+) linux /live/memtest I am still learning these scripts, so I appreciate any assistance. Cheers! Zed On 8/29/2014 1:57 PM, Stefan Baur wrote: Am 29.08.2014 um 21:51 schrieb Zed: I have tried various boot options to resolve, but receive the same error (with thefile:/// as entered of course): append preseed/file=/install/preseed.cfg append preseed/file=/media/cdrom/install/preseed.cfg append preseed/file=/media/cdrom0/install/preseed.cfg Could you please post your complete isolinux.cfg (and any *.cfg files it may pull in additionally)? -Stefan
Re: debian-installer-launcher
Thank you, Fernando - If I hit a wall again after my rebuild and modifying my isolinux *.cfg files, I will give your setup a try. Have a good one! Zed (Devin) On 8/29/2014 3:06 PM, Fernando Toledo wrote: On Fri, 29 Aug 2014 13:51:35 -0600, Zed wrote: Thanks to Daniel on IRC with a little direction I learned why it was skipping the preseed. Basically, I had not appended the parameters to the boot options in isolinux. It is copying the preseed to the ISO now, but it can't be located when the install is loading. I have my preseed here: /config/includes.binary/install/preseed.cfg When I browse the built ISO I find my file here: /media/cdrom0/install/preseed.cfg But, when I launch the debian-installer from the liveCD desktop, or from the boot menu I receive the error: "The file needed for preconfiguration could not be retrieved from file:///install/preseed.cfg [1]. The installation will proceed in non-automated mode. I have tried various boot options to resolve, but receive the same error (with the file:/// [2] as entered of course): append preseed/file=/install/preseed.cfg append preseed/file=/media/cdrom/install/preseed.cfg append preseed/file=/media/cdrom0/install/preseed.cfg Getting close, but no cigar as of yet... Zed i put my pressed on config/include.debian-installer https://github.com/HuayraLinux/live-cd/tree/master/config/includes.debian-installer then i modified the syslinux menu to include them appending the paremeter to the kernel (file=/pressed.cfg) : https://github.com/HuayraLinux/live-cd/blob/master/config/includes.binary/isolinux/live.cfg -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5400f0ed.1080...@lilypadmudlib.com
Re: debian-installer-launcher
The below fixed the preseed issue from the boot menu, but not the liceCD installer. I am pretty sure the details from Fernando will be what I need to do, but once again, I will update as soon as I make more progress. Thanks, all. Z On 8/29/2014 3:27 PM, Zed wrote: I accidentally took the list of a few responses, and Stefan was kind enough to let me know, so here is the last communication I sent him (intending to go to the whole list) with the solution, or at least what appears to be so far: root@debian:/# find /lib/live -name "preseed.cfg" /lib/live/mount/medium/install/preseed.cfg I also verified that the preseed in that location is in fact mine. I changed the boot from: .linux /install/vmlinuz file=/install/preseed.cfg TO .linux /install/vmlinuz /install/preseed.cfg This worked!! Thank you, Stefan. I have been beating my head against the wall and you got me looking down the right path. Thanks to DBA on IRC and Fernando as well! I think I can update my configs now so they will work. I need to make sure I document some of these finer points so I don't forget. Haha! Cheers! Zed (Devin) On 8/29/2014 2:07 PM, Zed wrote: Here are all the configs in my isolinux dir. * isolinux.cfg:* include menu.cfg default vesamenu.c32 prompt 0 timeout 0 *menu.cfg* menu hshift 0 menu width 82 menu title Boot menu include stdmenu.cfg include live.cfg include install.cfg menu begin advanced menu title Advanced options include stdmenu.cfg label mainmenu menu label ^Back.. menu exit include advanced.cfg menu end menu clear *stdmenu.cfg* menu background splash.png menu color title* # * menu color border* # # none menu color sel* # #76a1d0ff * menu color hotsel1;7;37;40 # #76a1d0ff * menu color tabmsg* # # * menu color help37;40 #ff00 # none menu vshift 12 menu rows 10 menu helpmsgrow 15 # The command line must be at least one line from the bottom. menu cmdlinerow 16 menu timeoutrow 16 menu tabmsgrow 18 menu tabmsg Press ENTER to boot or TAB to edit a menu entry *live.cfg.in* label live-@FLAVOUR@ menu label ^Live (@FLAVOUR@) menu default linux @LINUX@ initrd @INITRD@ append preseed/file=/install/preseed.cfg @APPEND_LIVE@ label live-@FLAVOUR@-failsafe menu label ^Live (@FLAVOUR@ failsafe) linux @LINUX@ initrd @INITRD@ append @APPEND_LIVE_FAILSAFE@ *install.cfg* label install menu label ^Install linux /install/vmlinuz initrd /install/initrd.gz append preseed/file=/install/preseed.cfg vga=788 @APPEND_INSTALL@ -- quiet label installgui menu label ^Graphical install linux /install/gtk/vmlinuz initrd /install/gtk/initrd.gz append preseed/file=/install/preseed.cfg video=vesa:ywrap,mtrr vga=788 @APPEND_INSTALL@ -- quiet *advanced.cfg* label hdt menu label ^Hardware Detection Tool (HDT) com32 hdt.c32 label memtest menu label ^Memory Diagnostic Tool (memtest86+) linux /live/memtest I am still learning these scripts, so I appreciate any assistance. Cheers! Zed On 8/29/2014 1:57 PM, Stefan Baur wrote: Am 29.08.2014 um 21:51 schrieb Zed: I have tried various boot options to resolve, but receive the same error (with thefile:/// as entered of course): append preseed/file=/install/preseed.cfg append preseed/file=/media/cdrom/install/preseed.cfg append preseed/file=/media/cdrom0/install/preseed.cfg Could you please post your complete isolinux.cfg (and any *.cfg files it may pull in additionally)? -Stefan
Re: debian-installer-launcher
Thank you, Fernando - This was the ultimate solution. I placed my preseed.cfg in the same location and made references as you did, and it is now reading SOME of my preseed.cfg. Is there a specific order items need to be in the preseed.cfg? What I am seeing now, when I launch the installer from the desktop (debian-installer-launcher) and when I run it form the boot menu, it preseeds the locale and language, but then ignores setting the hostname, does not use an apt-mirror (which is correct), then ignores the cd eject and reboot. Here is what I last tested (with comments): ### Lilypad Linux Preseed file ## Locale\Location\KB ## THESE WORK d-i debian-installer/locale string en_US d-i debian-installer/country string US d-i debian-installer/language string en #d-i localechooser/supported-locales multiselect en_US.UTF-8 d-i console-keymaps-at/keymap select us d-i keyboard-configuration/xkb-keymap select us ## Network Time and timezone info d-i clock-setup/ntp boolean true d-i clock-setup/utc boolean true d-i time/zone string US/Mountain ##IGNORED ## Network Config (interface) d-i netcfg/choose_interface select auto ## Hostname and info d-i netcfg/hostname string LilypadLinux ##IGNORED ## Disk Partitioning ## All IGNORED # The presently available methods are: # - regular: use the usual partition types for your architecture # - lvm: use LVM to partition the disk # - crypto: use LVM within an encrypted partition d-i partman-auto/method string regular # You can choose one of the three predefined partitioning recipes: # - atomic: all files in one partition # - home: separate /home partition # - multi: separate /home, /usr, /var, and /tmp partitions d-i partman-auto/choose_recipe select atomic d-i partman-partitioning/confirm_write_new_label boolean true d-i partman/choose_partition select finish d-i partman/confirm boolean true d-i partman/confirm_nooverwrite boolean true d-i apt-setup/use_mirror boolean false ## This one works ## Install Completion # Hide the pesky install complete junk d-i finish-install/reboot_in_progress note ##IGNORED # Eject install cd media d-i cdrom-detect/eject boolean true ##IGNORED # reboot the system # shutdown and halt #d-i debian-installer/exit/halt boolean true # shutdown and poweroff #d-i debian-installer/exit/poweroff boolean true # reboot d-i debian-installer/exit/reboot boolean true ##IGNORED I have tried many things, and it is quite possible I have removed\commented out items needed for these all to work Thanks! Zed On 8/29/2014 3:06 PM, Fernando Toledo wrote: On Fri, 29 Aug 2014 13:51:35 -0600, Zed wrote: Thanks to Daniel on IRC with a little direction I learned why it was skipping the preseed. Basically, I had not appended the parameters to the boot options in isolinux. It is copying the preseed to the ISO now, but it can't be located when the install is loading. I have my preseed here: /config/includes.binary/install/preseed.cfg When I browse the built ISO I find my file here: /media/cdrom0/install/preseed.cfg But, when I launch the debian-installer from the liveCD desktop, or from the boot menu I receive the error: "The file needed for preconfiguration could not be retrieved from file:///install/preseed.cfg [1]. The installation will proceed in non-automated mode. I have tried various boot options to resolve, but receive the same error (with the file:/// [2] as entered of course): append preseed/file=/install/preseed.cfg append preseed/file=/media/cdrom/install/preseed.cfg append preseed/file=/media/cdrom0/install/preseed.cfg Getting close, but no cigar as of yet... Zed i put my pressed on config/include.debian-installer https://github.com/HuayraLinux/live-cd/tree/master/config/includes.debian-installer then i modified the syslinux menu to include them appending the paremeter to the kernel (file=/pressed.cfg) : https://github.com/HuayraLinux/live-cd/blob/master/config/includes.binary/isolinux/live.cfg -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54075bcc.2020...@lilypadmudlib.com
Re: method for getting speak and espeakup into a debian live image
Where are you setting the packages to be installed? Do you have your config on github at all so we can check out your configuration? Without knowing how your live-build is configured it is hard to tell where the issue may be (for me anyway - I am a visual dude). If you don¹t have your config on github or something similar, can you post your auto/config contents and config/packate-lists/* Cheers, Zed On 9/5/14, 3:40 PM, "Nick Gawronski" wrote: >Hi, I am totally blind and am trying to build my own debian live disc that >includes the espeakup and speak packages for use with the speak up screen >reader like is done in the debian-installer. I have added those packages >to the package list and when running lb build those packages are >downloaded and put into the image but when I boot the system no speech >starts and I am not able to start espeakup using /etc/init.d/espeakup >start either as the live user or using sudo. I have even tried using the >web builder and have not been emailed any links to the live rescue images >I built. What would I need to do to make sure speak and espeakup as well >as alas are properly setup in the live build process or better yet why not >put speech into the automatically built rescue images on the live systems >project and either speak a treating when the system starts up on how to >start speech or have a boot option for starting software speech? Nick >Gawronski > > >-- >To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org >with a subject of "unsubscribe". Trouble? Contact >listmas...@lists.debian.org >Archive: >https://lists.debian.org/bfec12f58309e434db05becc728d861f.squir...@hwa3.ul >trahost.us > -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/d02fa7a7.1f9%...@lilypadmudlib.com
Re: method for getting speak and espeakup into a debian live image
It may be some dependencies. I would suggest trying to use a custom hook that uses gdebi to install the debs - it will ensure that you have the needed dependencies. Zed On 9/6/14, 2:18 PM, "Don Raikes" wrote: >I am working on a similar issue with a copy of kali linus (a derivative >of Debian). > >My configuration is at http://github.com/dr1861/drkali.git. > >I think I pulled the speakup stuff out of my configuration because it >caused the system to be unbootable, but I will put it back in within the >hour. > >Any pointers on how to get it working would be appreciated. > >-Original Message- >From: Nick Gawronski [mailto:n...@nickgawronski.com] >Sent: Friday, September 05, 2014 5:30 PM >To: Zed >Cc: debian-live@lists.debian.org >Subject: Re: method for getting speak and espeakup into a debian live >image > >Hi, I have in my live directory the config directory and in that directory >there is another directory called package-lists. In that directory there >is a file called live.list.chroot where it contains packages like the >live-boot and live-config. I just went to the end of the file and entered >in espeakup and speak on different lines. To do the initial configuration >as I am using the current build of debian live in testing I did lb init >then lb config then edited the file and finally did lb build. I got the >iso image and burned it to a disc in the usually way using wodim and no >speech. One suggestion is could there not be a meta package for live >building where if say speakup_soft was put in a package list all needed >components would be put into the image? Also, is there a way to stop the >build once the chroot is made to allow me to go into it and manually >configure things then restart it to finish the build process? Nick >Gawronski >On Fri, September 5, 2014 6:49 pm, Zed wrote: >> Where are you setting the packages to be installed? Do you have your >> config on github at all so we can check out your configuration? >> >> Without knowing how your live-build is configured it is hard to tell >> where the issue may be (for me anyway - I am a visual dude). >> >> If you don¹t have your config on github or something similar, can you >> post your auto/config contents and config/packate-lists/* >> >> Cheers, >> Zed >> >> >> On 9/5/14, 3:40 PM, "Nick Gawronski" wrote: >> >> >>> Hi, I am totally blind and am trying to build my own debian live disc >>> that includes the espeakup and speak packages for use with the speak up >>> screen reader like is done in the debian-installer. I have added those >>> packages to the package list and when running lb build those packages >>> are downloaded and put into the image but when I boot the system no >>> speech starts and I am not able to start espeakup using >>> /etc/init.d/espeakup >>> start either as the live user or using sudo. I have even tried using >>> the web builder and have not been emailed any links to the live rescue >>> images I built. What would I need to do to make sure speak and >>>espeakup >>> as well as alas are properly setup in the live build process or better >>> yet why not put speech into the automatically built rescue images on >>>the >>> live systems project and either speak a treating when the system starts >>> up on how to start speech or have a boot option for starting software >>> speech? Nick Gawronski >>> >>> >>> >>> -- >>> To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org >>> with a subject of "unsubscribe". Trouble? Contact >>> listmas...@lists.debian.org >>> Archive: >>> >>>https://lists.debian.org/bfec12f58309e434db05becc728d861f.squirrel@hwa3. >>> ul trahost.us >>> >> >> >> >> -- >> To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org >> with a subject of "unsubscribe". Trouble? Contact >> listmas...@lists.debian.org Archive: >> https://lists.debian.org/d02fa7a7.1f9%...@lilypadmudlib.com >> >> >> > > > >-- >To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org >with a subject of "unsubscribe". Trouble? Contact >listmas...@lists.debian.org >Archive: >https://lists.debian.org/1c4a98a3013b7db3415fd04c31cc9532.squir...@hwa3.ul >trahost.us > > >-- >To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org >with a subject of "unsubscribe". Trouble? Contact >listmas...@lists.debian.org >Archive: >https://lists.debian.org/9d73fa89-639a-44a2-bf4d-5fb7b3c6c8b4@default > -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/d031391c.21c%...@lilypadmudlib.com
Re: method for getting speak and espeakup into a debian live image
To elaborate, what I have done (and seen other do) is: - In the root of your build directory, create a directory named: hooks - Create a file in the hooks folder. Mine is called stripped.hook.chroot - mkdir hooks ; cd hooks - touch stripped.hook.chroot - Edit the new file, and add the following: ## stripped.hook.chroot #!/bin/sh set -e # Download deb files to tmp dir echo download espeakup wget -nv -O /tmp/espeakup_deb_filename.deb http://download.location.for.espeakup.deb echo download speak wget -nv -O /tmp/speak_deb_filename.deb http://download.location.for.speak.deb # Install debs echo install espeakup gdebi -n -q /tmp/espeakup_deb_filename.deb echo install speak gdebi -n -q /tmp/speak_deb_filename.deb # Remove deb files rm /tmp/espeakup_deb_filename.deb rm /tmp/speak_deb_filename.deb # End of stripped.hook.chroot - Now create a symlink in build_dir/config/hooks: - cd ../config/hooks ; ln -s ../../hooks/stripped.hook.chroot 0500-stripped.hook.chroot What will this do? It will download the required files you want (espeakup and speak) then us gdebi to install them in your chroot during the build process, and then remove the deb files from your live chroot /tmp location. I have used the same script to install chrome and some other apps that I can’t use the traditional package-lists method. Good luck! Stick with it - this is a very powerful and useful set of scripts. I have only been using it for a bit now but have had a good time,solved some issues, and learned a TON - and more learning is coming… :) Again, good luck, and cheers! -Zed On 9/6/14, 10:20 PM, "Zed" wrote: >It may be some dependencies. I would suggest trying to use a custom hook >that uses gdebi to install the debs - it will ensure that you have the >needed dependencies. > >Zed > >On 9/6/14, 2:18 PM, "Don Raikes" wrote: > >>I am working on a similar issue with a copy of kali linus (a derivative >>of Debian). >> >>My configuration is at http://github.com/dr1861/drkali.git. >> >>I think I pulled the speakup stuff out of my configuration because it >>caused the system to be unbootable, but I will put it back in within the >>hour. >> >>Any pointers on how to get it working would be appreciated. >> >>-Original Message- >>From: Nick Gawronski [mailto:n...@nickgawronski.com] >>Sent: Friday, September 05, 2014 5:30 PM >>To: Zed >>Cc: debian-live@lists.debian.org >>Subject: Re: method for getting speak and espeakup into a debian live >>image >> >>Hi, I have in my live directory the config directory and in that >>directory >>there is another directory called package-lists. In that directory there >>is a file called live.list.chroot where it contains packages like the >>live-boot and live-config. I just went to the end of the file and >>entered >>in espeakup and speak on different lines. To do the initial >>configuration >>as I am using the current build of debian live in testing I did lb init >>then lb config then edited the file and finally did lb build. I got the >>iso image and burned it to a disc in the usually way using wodim and no >>speech. One suggestion is could there not be a meta package for live >>building where if say speakup_soft was put in a package list all needed >>components would be put into the image? Also, is there a way to stop the >>build once the chroot is made to allow me to go into it and manually >>configure things then restart it to finish the build process? Nick >>Gawronski >>On Fri, September 5, 2014 6:49 pm, Zed wrote: >>> Where are you setting the packages to be installed? Do you have your >>> config on github at all so we can check out your configuration? >>> >>> Without knowing how your live-build is configured it is hard to tell >>> where the issue may be (for me anyway - I am a visual dude). >>> >>> If you don¹t have your config on github or something similar, can you >>> post your auto/config contents and config/packate-lists/* >>> >>> Cheers, >>> Zed >>> >>> >>> On 9/5/14, 3:40 PM, "Nick Gawronski" wrote: >>> >>> >>>> Hi, I am totally blind and am trying to build my own debian live disc >>>> that includes the espeakup and speak packages for use with the speak >>>>up >>>> screen reader like is done in the debian-installer. I have added >>>>those >>>> packages to the package list and when running lb build those packages >>>> are downloaded and put into the image but when I boot the system no >>>> speech starts and I am not able to start espeakup using >>>> /et
Preseed\Livecd issue
I¹ve run into a few small snags that has me perplexed currently, and I hope someone can lend a hand. My live-build completes, and the ISO boots. Once the Live session has started, this is where I see two strange behaviors. 1. The desktop icon for the debian-installer-launcher that I have used for many past build no longer appears on the livecd desktop. 2. When I DO launch the debian-live-installer from the livecd (as the icon is in the System menu), it launches but does not read ANYTHING from my pressed, but if I boot to the installer or graphical installer, the pressed works exactly as expected. Details: debian-installer-shorcut.desktop file is located: config/includes.chroot/usr/share/applications/debian-installer-launcher.desk top debian-installer-launcher.desktop contents: [Desktop Entry] Version=1.0 Name=Install Lilypad Linux Comment=Install this system permanently to your hard disk Exec=su-to-root -X -c /usr/sbin/debian-installer-launcher Icon=debian-installer-launcher Type=Application Categories=Application;System; StartupNotify=true Terminal=false Preseed.cfg location: config/includes.installer/preseed.cfg Other location tried: config/debian-installer/preseed.cfg config/includes.debian-installer/preseed.cfg config/includes.binary/preseed.cfg (then adding file=/preseed.cfg to boot menu config) When I boot to the livecd and search for the pressed, it is on the livecd, but the desktop link ignores it completely. config/includes.binary/install/preseed.cfg (then adding file=/install/preseed.cfg to boot menu config) When I boot to the livecd and search for the pressed, it is on the livecd, but the desktop link ignores it completely. I do hope someone has some ideas on what I can try next. I have even removed all packages with the exception of desktop-base, and a dm\wm (tried various combinations with no luck). Even with just the basics, I can not get the pressed to be read when booted into the live session, and the desktop icon has just stopped working. Thanks all, and let me know if you need additional details. Thanks. Cheers! Zed (Devin)
Re: Failure to build Jessie with MATE
Maybe copying and pasting has included some characters that are causing issues (that are not exactly visible). I have comments all over the place and they have not caused any issues (begging. Middle, and end of configs) and I am running 4.0.1-1 and 4.0.2 without issues. I¹d try to recreate the config files maybe. Also, if your configs are so long, you could always put your project on GitHub so we can see the configs and then you don¹t have to worry about length of messages. Just a thought. Z From: "Michael ." Date: Sun, 5 Oct 2014 08:58:01 +1100 To: "debian-live@lists.debian.org" Subject: Re: Failure to build Jessie with MATE Resent-From: Resent-Date: Sat, 4 Oct 2014 21:58:17 + (UTC) That was the problem. I built an iso and am now about to test it to see if it will install. Why does Live Build no longer see comments at the beginning of a file? On 4 October 2014 21:35, Michael . wrote: > I think I have just figured it out, only because of having to copy and paste > configs over. > My package lists are derived from my 3.x configs and at the top of the file is > a line that > starts with "# /usr/share/live/build/package-lists/". This must have been from > when 3.x > in development (when I first started using Live Build) and I have not removed > it. > > It seems Live Build 4.x doesn't recognise # as a comment, even though Live > Build 3.x did, > so it reads the file as is and expects a file path to actually lead to a file > even though the line > is commented out. > > In the morning I will remove that line, start a totally new build and see what > happens. > > You may wonder why I haven't sent this with the configs etc inline as you > suggested. This > email was huge with all the configs and the build log. Well in excess of 5000 > lines, I have > been able to attach files before but have never had to attach anything so big. > It may help > if the list software allowed larger attachments. > > On 4 October 2014 20:41, Ben Armstrong wrote: >> On 04/10/14 12:26 AM, Michael . wrote: >>> > There should be 8 files in the previous message. >>> > Please let me know if they are there, if they aren't I'll link to them >>> > in my dropbox. >> >> There is no previous message. As I said, include them inline and you >> won't have this problem. >> >> Ben >> >
Re: Preseed\Livecd issue
Well, I have my preseed in the config/includes.installer directory. It is picked up and read perfectly when I boot the iso into Install or Graphic install just not when I boot into live. Also, if you want the debian-installer available from your livecd, you need to install the debian-instller-launcher. Even though the launcher isn¹t reading the pressed, the installer works well. Z From: "Michael ." Date: Sun, 5 Oct 2014 12:32:02 +1100 To: Jack Handy Cc: Debian-live mailing list Subject: Re: Preseed\Livecd issue Thanks so much for asking this. Now I have Live Build working in Jessie I am about to start on preseeding so I am interested in any helpful replies you get. I want to preseed language/country and keyboard (nothing much) when the image is installed to the computer so the user doesn't have to wade through a list of English speaking countries (di defaults to the USA for English and Australia is at the other end of the list). Sorting out the preseed contents is done I just need to know where to put it for it to work On 5 October 2014 10:23, Zed wrote: > I¹ve run into a few small snags that has me perplexed currently, and I hope > someone can lend a hand. > > My live-build completes, and the ISO boots. Once the Live session has started, > this is where I see two strange behaviors. > > 1. The desktop icon for the debian-installer-launcher that I have used for > many past build no longer appears on the livecd desktop. > 2. When I DO launch the debian-live-installer from the livecd (as the icon is > in the System menu), it launches but does not read ANYTHING from my pressed, > but if I boot to the installer or graphical installer, the pressed works > exactly as expected. > > Details: > debian-installer-shorcut.desktop file is located: > config/includes.chroot/usr/share/applications/debian-installer-launcher.deskto> p > > debian-installer-launcher.desktop contents: > > [Desktop Entry] > > Version=1.0 > > Name=Install Lilypad Linux > > Comment=Install this system permanently to your hard disk > > Exec=su-to-root -X -c /usr/sbin/debian-installer-launcher > > Icon=debian-installer-launcher > > Type=Application > > Categories=Application;System; > > StartupNotify=true > > Terminal=false > > > > Preseed.cfg location: config/includes.installer/preseed.cfg > > > > Other location tried: > > config/debian-installer/preseed.cfg > > config/includes.debian-installer/preseed.cfg > > config/includes.binary/preseed.cfg (then adding file=/preseed.cfg to boot menu > config) > > When I boot to the livecd and search for the pressed, it is on the livecd, but > the desktop link ignores it completely. > > config/includes.binary/install/preseed.cfg (then adding > file=/install/preseed.cfg to boot menu config) > > When I boot to the livecd and search for the pressed, it is on the livecd, but > the desktop link ignores it completely. > > > > > > I do hope someone has some ideas on what I can try next. I have even removed > all packages with the exception of desktop-base, and a dm\wm (tried various > combinations with no luck). Even with just the basics, I can not get the > pressed to be read when booted into the live session, and the desktop icon has > just stopped working. > > > > Thanks all, and let me know if you need additional details. > > > > Thanks. > > > > Cheers! > > Zed (Devin)
Re: Preseed\Livecd issue
Debian-installer-launcher reads the pressed I¹ve included on the ISO if I append the path to the exec path in my shortcut as such (pressed.cfg located in config/includes.binary): Exec=su-to-root -X -c /usr/sbin/debian-installer-launcher file=/preseed.cfg Still working on the desktop shortcut issue. From: Jack Handy Date: Sat, 04 Oct 2014 17:23:08 -0600 To: Debian-live mailing list Subject: Preseed\Livecd issue Resent-From: Resent-Date: Sat, 4 Oct 2014 23:22:50 + (UTC) I¹ve run into a few small snags that has me perplexed currently, and I hope someone can lend a hand. My live-build completes, and the ISO boots. Once the Live session has started, this is where I see two strange behaviors. 1. The desktop icon for the debian-installer-launcher that I have used for many past build no longer appears on the livecd desktop. 2. When I DO launch the debian-live-installer from the livecd (as the icon is in the System menu), it launches but does not read ANYTHING from my pressed, but if I boot to the installer or graphical installer, the pressed works exactly as expected. Details: debian-installer-shorcut.desktop file is located: config/includes.chroot/usr/share/applications/debian-installer-launcher.desk top debian-installer-launcher.desktop contents: [Desktop Entry] Version=1.0 Name=Install Lilypad Linux Comment=Install this system permanently to your hard disk Exec=su-to-root -X -c /usr/sbin/debian-installer-launcher Icon=debian-installer-launcher Type=Application Categories=Application;System; StartupNotify=true Terminal=false Preseed.cfg location: config/includes.installer/preseed.cfg Other location tried: config/debian-installer/preseed.cfg config/includes.debian-installer/preseed.cfg config/includes.binary/preseed.cfg (then adding file=/preseed.cfg to boot menu config) When I boot to the livecd and search for the pressed, it is on the livecd, but the desktop link ignores it completely. config/includes.binary/install/preseed.cfg (then adding file=/install/preseed.cfg to boot menu config) When I boot to the livecd and search for the pressed, it is on the livecd, but the desktop link ignores it completely. I do hope someone has some ideas on what I can try next. I have even removed all packages with the exception of desktop-base, and a dm\wm (tried various combinations with no luck). Even with just the basics, I can not get the pressed to be read when booted into the live session, and the desktop icon has just stopped working. Thanks all, and let me know if you need additional details. Thanks. Cheers! Zed (Devin)
