And that's simpler?
Ok, if you say so. :-)
It wouldn't work for me because my build host is on a remote network, and the
only way it can install images back to my local network is via SSH... it
doesn't have a publicly visible web server. Indeed, I'm not even sure I've
ever bothered to install a web server on it. Setting up port-forwarding for
Ssh on the other hand took less than a minute.
The easy way to get your "build label" is this:
make show_version
You can also pipe that into your "ver" file, as in:
make show_version > ver
and you don't have to grovel it out of "svn info" (also easier to script).
On 8/22/10 2:27 PM, Lonnie Abelbeck wrote:
> Or, for us mortals... :-)
>
> 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, your number will vary.
>
> 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' (echo "astlinux-0.7-4300"> ver) 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
>
> then reboot...
>
> The web interface (System tab) can be used instead of the command line if
> desired, I do.
>
> Lonnie
>
>
> On Aug 22, 2010, at 4:06 PM, Philip Prindeville wrote:
>
>> Mark,
>>
>> First, assuming you're not working with 'trunk', do the following:
>>
>> mkdir scripts
>> wget -P scripts -O shipit.sh
>> 'http://astlinux.svn.sourceforge.net/viewvc/astlinux/trunk/scripts/shipit.sh?revision=4337'
>> chmod a+x scripts/shipit.sh
>>
>> and then if you need to use a particular port to ssh into your router, do:
>>
>> export SHIPITPORT=22001 (or whatever #)
>>
>>
>> I usually upload to local routers where I'm inside the firewall, so port 22
>> works fine (the default).
>>
>> For the shipit.sh script to work best, you'll need to have root-ssh keys on
>> your pbx.
>>
>> You do this as:
>>
>> ssh-copy-id -i ~/.ssh/id_rsa.pub r...@pbx
>>
>>
>> once to install your ssh public key on that machine.
>>
>> Then after a successful instance of building an image, do:
>>
>> scripts/shipit.sh N.N.N.N [reboot]
>>
>>
>> to upload a new image and restart the router. I don't recommend this for
>> routers that aren't local... just in case you put the router into an
>> unrebootable state.
>>
>> And make sure that your VFAT partition has at least 60MB of space on it,
>> because you will have two images... the newest one and the previous one (in
>> /oldroot/cdrom/os.old) just in case you ever have to back out.
>>
>> When you do need to back out, do the following...
>>
>> mount -o remount,rw /oldroot/cdrom
>> cd /oldroot/cdrom
>> mv os os.broken
>> mv os.old os
>> sync
>> mount -o remount,ro /oldroot/cdrom
>> cd /
>> reboot
>>
>>
>> and that will put you back into the previous version of the build.
>>
>> From there, you can optionally do:
>>
>> mount -o remount,rw /oldroot/cdrom
>> rm -rf /oldroot/cdrom/os.broken
>> mount -o remount,ro /oldroot/cdrom
>>
>>
>> to get the broken image off your system.
>>
>> Can someone with editorial capabilities put whatever parts of this are
>> appropriate into the wiki?
>>
>> Mark: let me know if you have questions.
>>
>> Thanks,
>>
>> -Philip
>>
>>
>> On 8/22/10 6:10 AM, Mark Phillips wrote:
>>> This is what I followed to do my build. However, the docs just kinda
>>> stop right when it gets to the useful part.
>>>
>>>
>>>
>>> On 08/22/2010 01:12 AM, Darrick Hartman wrote:
>>>> Mark,
>>>>
>>>> Please follow this step by step:
>>>>
>>>> http://doc.astlinux.org/devdoc:documentation
>>>>
>>>> Some of those scripts are out-dated and should be removed. The above
>>>> documentation is the current method used to build AstLinux. After
>>>> you've followed, that ask away with any other questions.
>>>>
>>>> Darrick
>>>>
>>>> On 08/21/2010 09:48 PM, Mark Phillips wrote:
>>>>> Hi Folks,
>>>>>
>>>>> Are there any instructions on how to compile AstLinux?
>>>>>
>>>>> I've been able to download the sources and do an initial toolset build
>>>>> and AstLinux compile thanks to the devdoc notes but I'm unsure as to how
>>>>> to proceed.
>>>>>
>>>>> I'm left with 2 new files after the "make"; makeimage.sh and
>>>>> makerunnix.sh. Both of these scripts fail with various file not found
>>>>> errors etc. However I am left with a "disk.img" file and a mounted
>>>>> runnix environment in /mnt/runnix.
>>>>>
>>>>> Am I on the right track here?
>>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
