<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 11/13/2014 06:54 PM, Israel wrote: </div> <blockquote cite="mid:546560C5.904@gmail.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 11/13/2014 06:55 PM, Eric Bradshaw wrote: </div> <blockquote cite="mid:5465531B.7000209@computers4christians.org" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 11/13/2014 05:07 PM, John Hupp wrote: </div> <blockquote cite="mid:546547AA.8020502@prpcompany.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 11/13/2014 4:53 PM, Eric Bradshaw wrote: </div> <blockquote cite="mid:5465286A.5010902@computers4christians.org" type="cite"> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> To whomever may be able to provide some insight; Black Lab Image Creator (BLIC) 1.5 has NOT been tested with Lubuntu 14.10, but I'd like to continue using it to make Lubuntu respins if I can. Starting with BLIC's predesessor Remastersys; I have successfully made the C4C Lubuntu ReSpins based on 12.10, 13.04, 13.10, and 14.04. But, while trying to use Black Lab Image Creator 1.5 with Lubuntu 14.10 I get the following error early in the distribution build process: cp: missing destination file operand after ‘/home/blacklabimage/remasteredsys/ISOTMP/isolinux/’ Try 'cp --help' for more information The distribution build process continues and the iso seems to be produced as normal. However, after burning the iso to DVD and attempting to start another (32-bit) machine from it, I never even get to my custom splash screen. I get the error; failed to load ldlinux.c32 I believe the ldlinux.c32 file is created from contents I've always edited; isolinux.cfg is where I change the text of the splash screen (splash.png) to our own and remove options to start the install in low graphics mode or live. It seems that the error I get while first starting to boot a 32-bit machine from CD (DVD in this case) means a file called vesamenu.c32 failed to be created in /home/blacklabimage/remasteredsys/ISOTMP/isolinux/ and therefore failed to make it onto the iso. I went back and used Black Lab Image Creator 1.1 to respin Lubuntu 14.04. The vesamenu.c32 file is created and contains exactly one line: žþLÍ!üè There are other options for a non-programmer like me to respin Lubuntu. However, I have grown quite fond of this particular method. If anyone can help me figure out what changed/why this no longer works I'd be very grateful. Eric Bradshaw <div class="moz-signature">-- Thank You, God Bless, Computers4Christians <a moz-do-not-send="true" href="http://computers4christians.org/">http://www.Computers4Christians.org/</a> </div> </blockquote> I haven't got the first thing to offer by way of a solution or insight, but this is a topic I have been interested in. So maybe you can help ME instead! When you say, "There are other options for a non-programmer like me to respin Lubuntu," what options were you thinking about? I have seen references to Distroshare Ubuntu Imager (<a moz-do-not-send="true" href="https://github.com/Distroshare/distroshare-ubuntu-imager">https://github.com/Distroshare/distroshare-ubuntu-imager</a>) and Systemback (<a moz-do-not-send="true" href="http://sourceforge.net/projects/systemback/">http://sourceforge.net/projects/systemback/</a>) as Remastersys alternatives, but I have not tested either of them. I'd be interested in anyone else's experience with them or other alternatives. </blockquote> By George, I think I've got it! The new isolinux has a couple of extra directories now, so isolinux.bin, linux.c32, vesainfo.c32 and the file I think the one Black Dog Image Creator is looking for; vesamenu.c32 is now buried two more directories deep than it used to be; /usr/lib/syslinux/modules/efi32 - So I changed the path in blacklabimager in line 399 from VESAMENU=`find /usr -print0 | grep -FzZ "syslinux/vesamenu.c32"` to VESAMENU=`find /usr -print0 | grep -FzZ "syslinux/modules/efi32/vesamenu.c32"` and I'm not getting that error! And yes, there are those alternatives you mentioned, as well as just plain command-line instructions <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://help.ubuntu.com/community/MakeALiveCD/DVD/BootableFlashFromHarddiskInstall">https://help.ubuntu.com/community/MakeALiveCD/DVD/BootableFlashFromHarddiskInstall</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://help.ubuntu.com/community/LiveCDCustomizationFromScratch">https://help.ubuntu.com/community/LiveCDCustomizationFromScratch</a> but I've used this Remastersys fork for so long now because it uses my modified Ubiquity installer, my splash screen(s), allows me to delete options I don't want for the end-user like running in low graphics mode and running Live and I guess I just got used to the way it works. Even though it's now $50 - it's worth it it (if I can get it to work for 14.10 and beyond). Distroshare Ubuntu Imager says it's based on Remastersys and it looks like it took a bit from Black Lab Image Creator too, so that's definately my next script to try if the above doesn't work like I think. Eric Bradshaw <div class="moz-signature">-- Thank You, God Bless, Computers4Christians <a moz-do-not-send="true" href="http://computers4christians.org/">http://www.Computers4Christians.org/</a> </div> <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> Hi, There are a multitude of ways to do this. The way I do it is with a homemade script. This way I can control every single aspect of what is installed and how things are configured. This is extremely useful for OBI (one button installer) instead of Ubiquity as the installer. I am also optimizing things for the lowest-end hardware.... i.e. installing on a machine with 128MB ram rather than 384+ If you are interested in it, I'd be glad to share! I based it off of: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://help.ubuntu.com/community/LiveCDCustomizationFromScratch">https://help.ubuntu.com/community/LiveCDCustomizationFromScratch</a> the main change I made was making the chroot part into a separate script. I copy that into the chroot, and then run sudo chroot "$CHROOTDIR" ./mychrootscript.sh where "$CHROOTDIR" is the path to my chroot and ./mychrootscript.sh is the name of the script to do all the chroot stuff, like install packages, and configure things. I am currently trying to build for PPC also using qemu... but I am still in the very early stages. Jörn also has a script to custom make ISOs which use the Ubiquity installer. So his work might be more beneficial... it came from Ubuntu-GNOME (if I remember right). There is no graphic interface to making a script, but with a little optimization (caching the deboostrap into a tar file, and copying the debian archives outside the chroot) you can build it multiple times and test it without having to re-download tons of things. And there is the debian scripts that you can install... live-build <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://live.debian.net/manual/current/html/live-manual/installation.en.html">http://live.debian.net/manual/current/html/live-manual/installation.en.html</a> but that has quite the learning curve :) Though that is probably the most official route to take I suppose. P.S. I just recently got the other iBook setup to build packages :) And tested it out! Getting closer!!!! <pre class="moz-signature" cols="72">-- Regards</pre> </blockquote> Oh, silly me. I forgot about OBI until after I'd already send my last post. I was going to add it this morning, but Israel beat me to it. Since the creator of OBI frequents this mail list, that may be the best route for you John. He's gotten a lot of input from others here. (I think) I am closer with Black Dog Image Creator. I was pretty excited that I'd found "the" issue, and I think I am on the right track, but still no working iso. I changed line 399 again to take the vesamenu.c32 from syslinux/modules/bios/ instead because I saw there was actually a file called ldlinux.c32 in that bios directory. After making a DVD from that iso, I got no error about ldlinux.c32, but did get two more; Failed to load libcom32.c32 and Failed to load COM32 file vesamenu.c32 - and it again halted there. I also noticed a file called boot.cat that was present in my previous respins, but wasn't anywhere on my 14.10 system I could find, so I actually copied it into the syslinux/modules/bios/ directory. Then I added a line to blacklabimager to get all the files from the bios directory including the boot.cat one I had added into it; cp /usr/lib/syslinux/modules/bios/* $WORKDIR/ISOTMP/isolinux It booted this time! However, I still didn't see my own vesamenu. I instead was greeted with my splash screen graphic and a "Guest" login invitation and that led nowhere of course. I will work on it more later. Gotta' go to work now. Eric Bradshaw <div class="moz-signature">-- Thank You, God Bless, Computers4Christians <a href="http://computers4christians.org/">http://www.Computers4Christians.org/</a> </div> </body> </html>