<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/16/2014 11:10 PM, Eric Bradshaw
wrote:<br>
</div>
<blockquote
cite="mid:6xqy4foi2cyor6sfu5n3vl3p.1416100954957@email.android.com"
type="cite">
<div>
<div>[snip]</div>
<div>>>> added a line to blacklabimager to get all the
files from the bios</div>
<div>>>> directory including the <a
moz-do-not-send="true" href="http://boot.cat">boot.cat</a>
one I had added into it;</div>
<div>>>></div>
<div>>>> cp /usr/lib/syslinux/modules/bios/*
$WORKDIR/ISOTMP/isolinux</div>
<div>>>></div>
<div>>>> It booted this time! However, I still didn't
see my own vesamenu. I</div>
<div>>>> instead was greeted with my splash screen
graphic and a "Guest" login</div>
<div>>>> invitation and that led nowhere of course.</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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:</div>
<div><br>
</div>
<div>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.</div>
<div>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).</div>
<div>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.</div>
<div>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.</div>
<div><br>
</div>
<div>Eric Bradshaw</div>
<div><br>
</div>
<div>--</div>
<div><br>
</div>
<div>Thank You,</div>
<div>God Bless,</div>
<div>Computers4Christians</div>
<div><a moz-do-not-send="true"
href="http://www.Computers4Christians.org/">http://www.Computers4Christians.org/</a><br>
</div>
</div>
<br>
</blockquote>
<br>
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?)<br>
<br>
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?<br>
<br>
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?)<br>
<br>
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.<br>
<br>
</body>
</html>