Request help respinning 14.10 w/Black Lab Image Creator

[Israel]

Hi all,

On 11/17/2014 09:39 AM, John Hupp wrote:
> On 11/16/2014 11:10 PM, Eric Bradshaw wrote:
>> [snip]
>> >>> added a line to blacklabimager to get all the files from the bios
>> >>> directory including the boot.cat <http://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.
>>
>> ---
>>
>> So, after working with Systemback and making distributable isos from
>> it, I'm pretty sure I can copy the files Systemback puts into the
>> syslinux folder of a live iso and believe this would work because the
>> DVDs made from Systemback isos boot without error.
>>
>> However, the Systemback software has got me rethinking using Black
>> Dog Image Creator at all. I've still got some "personalizing" to do
>> for the C4C Lubuntu ReSpin, but here's what I'm liking about
>> Systemback so far:
>>
>> 1. The creation of a distributable "live" iso with Systemback is
>> incredibly easy, and they each boot in every 32-bit machine I've
>> tried them (burned on DVD) in.
>> 2. Systemback has the ability to use Ubiquity, but claims to be able
>> to work with whatever bootloader I choose (would this then work with
>> Yaboot for PowerPC I wonder? I've yet to see if Systemback installs
>> on PPC).
>> 3. The polished GUI of Systemback makes it a real visual treat to
>> work with (for a non-programmer like me) and because it's a great,
>> easy-to-use backup system too, I've got no problem including it for
>> the end-user.
>> 4. They've overcome the 4GB iso limit! I've created several isos
>> larger than 4GB that are both live and successfully install a working
>> system too.
>>
>> Eric Bradshaw
>>
>> --
>>
>> Thank You,
>> God Bless,
>> Computers4Christians
>> http://www.Computers4Christians.org/
>>
>
> I'm glad to see you are both pushing ahead with the exploration and
> reporting on results.  I'm very interested in the topic but have had
> no time to invest so far.  In fact, I'm farther back in the process,
> and don't even know for sure what all the viable candidates are (and
> does the list include OBI or gnome-disks aka Disks?)
>
> But I hear you saying that it's looking more and more like Systemback
> could be a good replacement for Remastersys and B.D.I.C.  You did say
> earlier that "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 definitely my next script to try if the above doesn't work like
> I think."  Did you try that but then find Systemback to be superior?
>
> Can you say anything explicit about how Systemback treats user-level
> or global settings.  For instance, does it strip out all user accounts
> and settings?  Or certain ones?  Or have an option to do so or not? 
> (Or does the documentation cover this question?)
>
> On a related sort of question, for the more narrow purpose of
> per-system full-installation backup, I'm also interested in how
> Systemback or other candidates might serve for that.
>
>
>

I found the main issue (or at least my main issue)
syslinux in 14.10 does not install isolinux, and has some other caveats.
The way I overcame this way by making a chroot of 12.04 (though 14.04
should work)
and copied isolinux.bin over from it into my /live directory on my CD...
of course I am using something other than Ubiquity/Casper  so it will be
very different.  You may simply install isolinux and everything will
work as it used to.
Something has majorly changed with syslinux, the directory structure is
very different now ( /usr/lib/syslinux is where the files are installed )
it now contains multiple directories like modules and mbr
Those contain things specific to types of booting, i.e. EFI and BIOS.

Not sure entirely how this all plays out... but if you find any
information on how to use the new syslinux, let me know!  until then,
you can always chroot a version lower and copy over files from it.  If
you need help with making a chroot let me know, as I have made many and
tried various configurations, and made mistakes that you can avoid :)

-- 
Regards

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-users/attachments/20141117/c6246d08/attachment.html>