Thanks Lonnie; I may have to just use the images on the website, as I really am not understanding what toolchain/build has done - where is the image to install?
The only downside will be I will be back on using asterisk 1.4 instead of asterisk 1.6, which was the whole point of doing the custom build. -Darryl -----Original Message----- From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com] Sent: August 16, 2010 12:35 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Asterisk 1.6 install On Aug 16, 2010, at 10:35 AM, Darryl Chandler wrote: > OK, I just don't know where the image is once toolchain/build is done? > Should I find a .img file somewhere? > > -Darryl There is a way to directly create a .img file, but I'll defer to others for that. What I would suggest is to first download the latest (currently 0.7.2) Install image (.img.gz) for your target, write to a CF card and follow the instructions to create a working setup with asterisk 1.4 (currently). == Then option 1 == In your build system, after a successful build for the 0.7 branch, you will see two files: astlinux-0.7-4300.tar.gz astlinux-0.7-4300.tar.gz.sha1 The "4300" corresponds to the current SVN rev. Then copy these two files to the "/oldroot/cdrom/os/" directory of your system and update the 'ver' file... $ echo "astlinux-0.7-4300" > /oldroot/cdrom/os/ver to match your new build. You will be good to go. OR... == Then option 2 == (my personal choice) There is an ever better way, IMHO if you build your own custom images. Create your own private HTTP repository for your custom images. On any web server ("server.local" for example) create a directory ("firmware" for example). Then in the firmware directory create a directory corresponding to your target, ie alix, net5501, geni586, geni586-serial, etc. Place your two files plus the 'ver' ("astlinux-0.7-4300") file... --- astlinux-0.7-4300.tar.gz astlinux-0.7-4300.tar.gz.sha1 ver --- into the server.local's /firmware/net5501/ directory (for the net5501 target) Then from the astlinux command line type: $ upgrade-run-image check http://server.local/firmware if all looks good, then upgrade with $ upgrade-run-image upgrade http://server.local/firmware The web interface (System tab) can be used instead of the command line if desired, I do. Lonnie ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
