Hi Jack, >Hi, > >Great job Juergen, thank you for putting this up. >I am going to play around with it ;-) See where it goes. >If I run the ./astbuild after changing it a bit what part do I transfer >back to my original Astlinux build, that is not quite clear to me yet.
Good question ;-) .. == Fast answer == a. Make always a new IMAGE when you were touching the kernel, e.g. ijncludig a new NIC drivers or updating e.g. mISDN b. If you just compiled an ASTERISK chan_driver or a new application, you can just copy the results into your image. --more detailed-- Everything, which needs to build a new kernel e.g. updating mISDN, some active ISDN-card driver etc. to my understanding needs a new image. And into this new image you can probably transfer some scripts or so, which you had changed in the previous version. I made some tests in just partially re-compiling e.g. NIC drivers and then to included these into an existing image, but failed with that. Now, I always make a new complete image when driver changes (on the kernel level) were necessary. By the way, much easier is to cope with a new image when you use the "keydisk". On the keydisk there are most (if not all) of your user configurable scipts and files. After some 3 months playing around with the devel package my suggestion is to use this option with a seperate USB-stick. You can "just" make a new image and with the keydisk option it runs immediately with your "old" settings. Another matter is, when you compile modules on the application level e.g. an ASTERISK chan_driver or a text based browser ... Such an application you can just compile under the crosscompiler on your LINUX development box and instead of installing the results on this machine you can copy the resulting binaries etc. directly on your ASTLINUX box or at least into the image. Another hint: I use the "opt" path on my ASTLINUX testing box to mount that via NFS to my LINUX development machine, to ~/astlinux-devel/crosstool/i586-unknown-linux-gnu/gcc-3.3.4-glibc-2.3.3/opt and under this path I have the "normal structure" of bin, lib ... I arranged my makefiles for applications on my development box that "make install" copies the newly compiled applications into this structure. As it is mounted on my ASTLINUX box as well and is being included in the PATH I can test rightaway these applications w/o prior copying and probably copy them directly on the ASTLINUX box into my "main" CF-based image ... But, I suppose here everybody has his/her own style of arranging the testing environment and not much different from any other crosscompiling anvironment ... --Juergen >Thx > >Jack > > >2006/3/5, Juergen K. Zick ><<mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED]>: >Hi all, > >despite the bright sun outside I've setup a WiKi page for updating AstLinux >by use of the present development environment: > ><http://www.voip-info.org/wiki/view/AstLinux%252BUpdates>http://www.voip-info.org/wiki/view/AstLinux%252BUpdates > > > >Please feel free for extensions and error corrections, especially because >I'm not a native speaker of English ... > >* corrections are welcome * > > >--Jürgen > > >_______________________________________________ >Astlinux-users mailing list ><mailto:Astlinux-users@lists.kriscompanies.com>Astlinux-users@lists.kriscompanies.com >http://lists.kriscompanies.com/mailman/listinfo/astlinux-users > >Donations to support AstLinux are graciously accepted via PayPal to ><mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED] > > >_______________________________________________ >Astlinux-users mailing list >Astlinux-users@lists.kriscompanies.com >http://lists.kriscompanies.com/mailman/listinfo/astlinux-users > >Donations to support AstLinux are graciously accepted via PayPal to >[EMAIL PROTECTED] _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.kriscompanies.com http://lists.kriscompanies.com/mailman/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
