Otto Moerbeek wrote:
> On Wed, 8 Mar 2006, Chris 'Xenon' Hanson wrote:
>
>> Otto Moerbeek wrote:
>>> On Wed, 8 Mar 2006, Chris 'Xenon' Hanson wrote:
Thanks everyone!
>>> Leaves me wondering why you cannot use ksh to run the script. Are you
>>> running into a ksh bug or a bash specific featur
On Wed, 8 Mar 2006, Chris 'Xenon' Hanson wrote:
> Otto Moerbeek wrote:
> > On Wed, 8 Mar 2006, Chris 'Xenon' Hanson wrote:
> > > Thanks everyone!
> > Leaves me wondering why you cannot use ksh to run the script. Are you
> > running into a ksh bug or a bash specific feature?
>
> I honestly don
Otto Moerbeek wrote:
On Wed, 8 Mar 2006, Chris 'Xenon' Hanson wrote:
Thanks everyone!
Leaves me wondering why you cannot use ksh to run the script. Are you
running into a ksh bug or a bash specific feature?
I honestly don't know, I didn't write the script, Sangoma did. It calls for bash,
On Wed, 8 Mar 2006, Chris 'Xenon' Hanson wrote:
> Thanks everyone!
Leaves me wondering why you cannot use ksh to run the script. Are you
running into a ksh bug or a bash specific feature?
-Otto
yary wrote:
On 3/7/06, Chris 'Xenon' Hanson <[EMAIL PROTECTED]> wrote:
yary wrote:
Pardon me for giving what may be a naive answer, but how about putting
/usr/local/lib into the LD_LIBRARY_PATH env variable before starting
the wanrouter script?
It's an obvious answer, but I figured there mu
On 3/7/06, Chris 'Xenon' Hanson <[EMAIL PROTECTED]> wrote:
> yary wrote:
> > Pardon me for giving what may be a naive answer, but how about putting
> > /usr/local/lib into the LD_LIBRARY_PATH env variable before starting
> > the wanrouter script?
>
>It's an obvious answer, but I figured there m
yary wrote:
Pardon me for giving what may be a naive answer, but how about putting
/usr/local/lib into the LD_LIBRARY_PATH env variable before starting
the wanrouter script?
It's an obvious answer, but I figured there must be a good reason (security?) that
/usr/local/lib _isn't_ in the LD_LI
On 3/7/06, Chris 'Xenon' Hanson <[EMAIL PROTECTED]> wrote:
>I'm working on getting the Sangoma WANPIPE driver working under OpenBSD
> 3.8 (mostly
> working) and ran into a couple of little problems that I'm trying to find the
> "right" way
> to solve.
>
>The preferred setup is to run thei
Chris 'Xenon' Hanson wrote:
> While poking around, I see that there is a package for a static
>version of bash:
>
>ftp://ftp.openbsd.org//pub/OpenBSD/3.8/packages/i386/bash-3.0.16p1-static.tgz
> 2. For an automated installer, how would the installer know where to
>get the proper package? The
Chris 'Xenon' Hanson wrote:
While poking around, I see that there is a package for a static
version of bash:
ftp://ftp.openbsd.org//pub/OpenBSD/3.8/packages/i386/bash-3.0.16p1-static.tgz
2. For an automated installer, how would the installer know where to
get the proper package? The UR
From: [EMAIL PROTECTED]
>2. For an automated installer, how would the installer
> know where to get the proper
> package?
`machine -a` will pull the application architecture.
`uname -r` will get your release.
Don't know about magic for a package version. Perhaps pkg_add(1) can handle
some
Chris 'Xenon' Hanson wrote:
My hack solution was to symlink both libiconv and libintl into
/usr/lib, which does seem to be in the lib search path at that point,
but that seems like a poor solution.
While poking around, I see that there is a package for a static version of
bash:
ftp://ftp
I'm working on getting the Sangoma WANPIPE driver working under OpenBSD 3.8 (mostly
working) and ran into a couple of little problems that I'm trying to find the "right" way
to solve.
The preferred setup is to run their "wanrouter" bash script in the rc.securelevel
script, to load the driv
13 matches
Mail list logo
