I think the idea here is that you download one of the prebuilt images and install that on a CF card...
Your system would then boot up into the image you downloaded... then you run your toolchain/build on your own development system.. this makes you a new build with your custopm options.. which it sounds like worked for you.. that you got no errors... if you followed the instructions.. you would have been in the 0.7 directory when you typed toolchain/build.. when the build is finished you will have a directory astlinux-0.7-4079 (or similar... the last 4 digits will be different based on your version). If you cd into that dir and list it.. you will see your new astlinux files.... [cadillac...@localhost astlinux-0.7-4079]$ ls -al total 18420 drwxrwxr-x 2 cadillackid cadillackid 4096 2010-07-21 07:00 . drwxr-xr-x 13 cadillackid cadillackid 4096 2010-08-16 04:44 .. -rw-rw-r-- 1 cadillackid cadillackid 0 2010-07-21 07:00 astflag -rwx------ 1 cadillackid cadillackid 18407424 2010-07-21 07:00 astlinux-0.7-4079.run -rw-rw-r-- 1 cadillackid cadillackid 421 2010-07-21 07:00 astlinux-0.7-4079.run.conf -rw-rw-r-- 1 cadillackid cadillackid 64 2010-07-21 07:00 astlinux-0.7-4079.run.sha1 -rw-rw-r-- 1 cadillackid cadillackid 437034 2010-07-21 07:00 initrd.img [cadillac...@localhost astlinux-0.7-4079]$ Those are the files that your toolchain/ build created.... copy those files into the /oldroot/cdrom/os directory of the compact flash card you had created with the pre-built image... Then make a new ver file in that /oldroot/cdrom/os directory on your astlinux box echo "astlinux-0.7-4079"> /oldroot/cdrom/os/ver remember to change the last 4 digits of the above command to the last 4 digits of the files you just copied over... this will allow you to use you new built versions rather than having to use the stock images.... if the files I listed above don't exist.. it means yourt build crashed or invalid options were selected when you did menuconfig -Christopher -----Original Message----- From: Darryl Chandler [mailto:dar...@sourcecable.ca] Sent: Monday, August 16, 2010 12:50 PM To: 'AstLinux Users Mailing List' Subject: Re: [Astlinux-users] Asterisk 1.6 install Ah, perhaps my problem is that I was hoping for a img file to put onto a CF for another system, and not to install on the system I was working on. I look forward to a future release having the asterisk 1.6 option.. Thanks Darrick. -Darryl -----Original Message----- From: Darrick Hartman [mailto:dhart...@djhsolutions.com] Sent: August 16, 2010 12:47 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Asterisk 1.6 install Darryl, The build environment isn't for everyone. It's expected that the end-user has some slightly more than basic linux knowledge. That being said, the documentation is pretty clear. If you follow those instructions, you should get a working system. There are some slightly older published images with Asterisk 1.6.2.x (don't recall the exact version). When I build the next set of 0.7 images, I'll build images with Asterisk 1.6 and make them available too. Darrick On 08/16/2010 11:41 AM, Darryl Chandler wrote: > 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. -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com ---------------------------------------------------------------------------- -- 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. ------------------------------------------------------------------------------ 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.
