If everything went in one checksum file, how would one (or shasum) tell
each of the checksums apart?
I'll submit a patch to mkrelease for the extra files.
On 21 December 2013 22:57, Matthew Jordan mjor...@digium.com wrote:
On Sat, Dec 21, 2013 at 4:26 PM, Paul Belanger
Patch submitted for review: https://reviewboard.asterisk.org/r/3091/
On 22 December 2013 11:31, Ben Langfeld b...@langfeld.me wrote:
If everything went in one checksum file, how would one (or shasum) tell
each of the checksums apart?
I'll submit a patch to mkrelease for the extra files.
On Sun, Dec 22, 2013 at 7:31 AM, Ben Langfeld b...@langfeld.me wrote:
If everything went in one checksum file, how would one (or shasum) tell
each of the checksums apart?
I'll submit a patch to mkrelease for the extra files.
I was thinking a JSON blob, but I'm perfectly happy with multiple
The *sum tools will test all lines in a checksum file and will return 0 if
any match or 1 if none match.
md5sum --quiet -c xxx.asc xxx.tar.gz
sha1sum --quiet -c xxx.asc xxx.tar.gz
sha256sum --quiet -c xxx.asc xxx.tar.gz
where xxx.asc is
But how do I know which one of those is which hash, since they're not
labelled?
On 22 December 2013 16:11, George Joseph george.jos...@fairview5.comwrote:
The *sum tools will test all lines in a checksum file and will return 0 if
any match or 1 if none match.
md5sum --quiet -c xxx.asc
On Sun, Dec 22, 2013 at 1:25 PM, Ben Langfeld b...@langfeld.me wrote:
But how do I know which one of those is which hash, since they're not
labelled?
The *sum programs can tell by the length. md5 is 32, sha1 is 40, sha256 is
64, etc. They ignore with warnings lines that don't match length.
Hi
Thanks for reply.
Actually, what I have tried to do is, I don't configure any menu in
confbridge.conf file, and here is application syntax like...
ConfBridge(conference[,bridge_profile[,user_profile[,menu]]]).
But from asterisk's dialplan, I just passed ConfBridge(CONFERENCE_NUMBER),
nothing
