A later version of asterisk is available for ACID installs.
These upgrade instructions must be followed to the letter.
1. Change directories to /root
2. If you don't have an astupd.sh file STOP. Your ACID install is too
old and you will need to do a fresh install which will install the
latest version automatically. If you have to re-install, make a backup
of your config files in /etc/asterisk so that you can restore them to
the new install.
3. If you have an astupd.sh file, you will need to update it by
downloading a new version. Use the following wget command from the /root
directory to do this:
with the instructions given wget does not overwrite astupd.sh directly. The old file remains. and the new file is saved as astupd.sh.1. It also needs to be made executable with chmod 770 before you can run it.
Thanks for catching this! I forgot about how cautious wget can be. My
two versions are identical and iI didn't key off of the date.
Steve
WA6ZFT
Eric Fort wrote:
···
with the instructions given wget does not overwrite astupd.sh directly. The
old file remains. and the new file is saved as astupd.sh.1. It also needs to
be made executable with chmod 770 before you can run it.
Eric
On Sat, Oct 11, 2008 at 8:56 PM, Stephen Rodgers < > hwstar@rodgers.sdcoxmail.com> wrote:
A later version of asterisk is available for ACID installs.
These upgrade instructions must be followed to the letter.
1. Change directories to /root
2. If you don't have an astupd.sh file STOP. Your ACID install is too
old and you will need to do a fresh install which will install the
latest version automatically. If you have to re-install, make a backup
of your config files in /etc/asterisk so that you can restore them to
the new install.
3. If you have an astupd.sh file, you will need to update it by
downloading a new version. Use the following wget command from the /root
directory to do this:
As Eric Fort as pointed out (thanks Eric!), these was a problem in the
previous instructions. Here are the revised update instructions:
1. Change directories to /root
2. Do an ls to list the files. If you don't have an astupd.sh file STOP.
Your ACID install is too old and you will need to do a fresh install
which will install the latest version automatically. If you have to
re-install, make a backup of your config files in /etc/asterisk so that
you can restore them to the new install.
3. If you have an astupd.sh file delete it by typing:
rm astupd.sh
4. You will need to update it by downloading a new version. Use the
following wget command from the /root directory to do this:
7. Your system will now be updated if it is not running the latest
Asterisk version. Wait for the download and compile to
complete.
8. Reboot your system and check to see that your node is functioning
properly.
Steve
WA6ZFT
Stephen Rodgers wrote:
···
A later version of asterisk is available for ACID installs.
These upgrade instructions must be followed to the letter.
1. Change directories to /root
2. If you don't have an astupd.sh file STOP. Your ACID install is too
old and you will need to do a fresh install which will install the
latest version automatically. If you have to re-install, make a backup
of your config files in /etc/asterisk so that you can restore them to
the new install.
3. If you have an astupd.sh file, you will need to update it by
downloading a new version. Use the following wget command from the /root
directory to do this:
Times they are a changing. Got a box lying around needing something to do. Thought I'd start another Limey Linux install for it. Wouldn't you know, the smallest CF card at Fry's was 4GB. I did find a 1GB CF at Sam's Club ($15 US). Turns out I had a 512MB card stuck in one of my laptops, so I'll swap that with the 1GB card. Still a lot of overkill but what do you do?
The big question is can you DD a 128mb image to a 512MB CF device and
still have it work? I've never tried this, but conceivably it should
work. I have initialized 512MB CF devices with make cf and it does work
for the 512MB Sandisk CF device I have.
Steve
WA6ZFT
Randy Hammock wrote:
···
Times they are a changing. Got a box lying around needing something to
do. Thought I'd start another Limey Linux install for it. Wouldn't you
know, the smallest CF card at Fry's was 4GB. I did find a 1GB CF at
Sam's Club ($15 US). Turns out I had a 512MB card stuck in one of my
laptops, so I'll swap that with the 1GB card. Still a lot of overkill
but what do you do?
I haven't tried this with limey linux, but, I put a fixed-size flash image
on larger CF cards all the time....I currently use 1GB kingston CF cards.
They're about the smallest/cheapest I can get new. The linux image I'm
using is a custom configured OpenWRT image that is roughly 64MB in size.
I primarily use pcengines ALIX boards....I'm just now starting to try them
with app_rpt....So far, so good!
73, David KB4FXC
···
On Fri, 17 Oct 2008, Stephen Rodgers wrote:
Randy,
The big question is can you DD a 128mb image to a 512MB CF device and
still have it work? I've never tried this, but conceivably it should
work. I have initialized 512MB CF devices with make cf and it does work
for the 512MB Sandisk CF device I have.
Steve
WA6ZFT
Randy Hammock wrote:
> Times they are a changing. Got a box lying around needing something to
> do. Thought I'd start another Limey Linux install for it. Wouldn't you
> know, the smallest CF card at Fry's was 4GB. I did find a 1GB CF at
> Sam's Club ($15 US). Turns out I had a 512MB card stuck in one of my
> laptops, so I'll swap that with the 1GB card. Still a lot of overkill
> but what do you do?
>
> --
> Randy Hammock KC6HUR
> http://kc6hur.net/~rhammock/
> http://irlp.kc6hur.net/
> If there are no horses in heaven, then when I die, I want to go where
> they went.
>
> _______________________________________________
> App_rpt mailing list
> App_rpt@lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
>
