<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Gustin,<br></div><div><br></div><div>That's pretty much the process I follow, with two exceptions --</div><div><br></div><div>1). I've divided my images into two parts, system and data. The "system" filesystem is the only image that is copied.</div><div><br></div><div>2). For the "system" filesystem, I maintain the image as small as possible, then expand it =after= copying over with "dd".</div><div><br></div><div>The advantage of keeping the system image as small as possible is that it reduces the copy time =and= helps me keep track of how large my system image is getting to be -- right now about 620MB.</div><div><br></div><div>I'm not convinced that using ISOs is the way to go, and not because the process is a pain in the neck. Having an image that can be copied bit-for-bit with dd means you =know= the bits are right, period.<br></div><div>--<br>Julie Haugh<br>Senior Design Engineer<br>greenHouse Computers, LLC // jfh at <a href="http://greenhousepc.com">greenhousepc.com</a> // greenHousePC on Skype</div><div><br><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [Voyage-linux] issues with usb installs.<br>
From: Gustin Johnson <<a href="mailto:gustin@meganerd.ca">gustin@meganerd.ca</a>><br>
Date: Tue, January 24, 2012 12:33 am<br>
To: Rich E Neese <<a href="mailto:r.neese@gmail.com">r.neese@gmail.com</a>><br>
Cc: "<a href="mailto:voyage-linux@voyage.hk">voyage-linux@voyage.hk</a>" <<a href="mailto:voyage-linux@voyage.hk">voyage-linux@voyage.hk</a>><br>
<br>
What I do is install the system to a CF card (I only use ALIX and<br>
Soekris SBCs). I boot the system, install packages I need/want, make<br>
sure that sync dirs is configured properly and any required users<br>
added. I then shutdown the system, pull the CF card and mount on my<br>
development machine (Ubuntu based). Then I wipe out all the NIC info<br>
in /etc/udev/rules.d (to assist with deploying the subsequent image on<br>
more than one machine.<br>
<br>
At this point if I need to deploy more than one of these machines,<br>
then I image the CF card with ddrescue. I can blast this out to any<br>
number of other CF cards.<br>
<br>
For commonly installed packages I use dpkg --get-selections and dpkg<br>
--set-selections<br>
<br>
I realize that this is not exactly the solution you were looking for,<br>
but it might help you with your prototyping.<br>
<br>
On Sun, Jan 22, 2012 at 8:25 PM, Rich E Neese <<a href="mailto:r.neese@gmail.com">r.neese@gmail.com</a>> wrote:<br>
> I have a script that I run on voyage called <a href="http://install-fusionpbx.sh">install-fusionpbx.sh</a>. it<br>
> apt-get installs all the deps. Then it pulls down the freeswitch src<br>
> into /usr/src/freeswitch and builds freeswitch and installs it in<br>
> /usr/local/freeswitch/ and it installs nginx and all the php5 deps and<br>
> then installs fusionpbx gui into /usr/shar/nginx/www/fusionpbx by default.<br>
><br>
> the issue I had with this was on reboot the system woudl not remount ro<br>
><br>
> so I figure out about the /etc/defaults/voyage-util file and added the<br>
> needed dir that needed to run in a mem/ramfs and sync back to their<br>
> perspective dir on system sync times and on reboots.<br>
><br>
> this fixed the issue. and the system then would reboot and remount ro<br>
> like it should.<br>
><br>
> I have done a few other changes to make it perform better.<br>
><br>
> as to the sync script I am not sure about where it is. that it syncs daily.<br>
><br>
> but this has also led to the current issue of the specific files not<br>
> being cp when using the voyage.update. so I guess i have to figure a fix<br>
> for this so then I can move forward to a install iso . and a bz2 file<br>
><br>
> thanks for your time . and hope we can figure this out.<br>
><br>
> by defalt there are files in /usr/local/freeswitch/conf dir that are<br>
> required by freeswitch to run else it will just not function as it should.<br>
><br>
> but I will figure this out. My iso requires it.<br>
><br>
> _______________________________________________<br>
> Voyage-linux mailing list<br>
> <a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>
> <a href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
<br>
_______________________________________________<br>
Voyage-linux mailing list<br>
<a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>
<a href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
</div>
</blockquote></span></body></html>