On Sunday 12 August 2012 18:48, Harald Becker wrote:
> They way I have setup busybox.conf (root.root -rw---), and the way
> it worked for a long time. I have not stepped into this bug before, but
> possibly due to the fact that most of my Busybox based control scripts
> run as root or did not r
Hi Tito !
>"Format of /etc/busybox.conf:
>
>The file has to be owned by user root, group root and has to be
>writeable only by root (chown 0.0; chmod 600;). "
They way I have setup busybox.conf (root.root -rw---), and the way
it worked for a long time. I have not stepped into this bug before
On Sunday 12 August 2012 16:09:52 Harald Becker wrote:
> Hi Tito !
>
> >can you run it again after disabling ENABLE_FEATURE_SUID_CONFIG
> >just to be sure, as in this case there should be no error.
>
> Ok, fresh compile with CONFIG_FEATURE_SUID_CONFIG disabled: No error as
> you expected.
>
> >
Hi Tito !
>can you run it again after disabling ENABLE_FEATURE_SUID_CONFIG
>just to be sure, as in this case there should be no error.
Ok, fresh compile with CONFIG_FEATURE_SUID_CONFIG disabled: No error as
you expected.
>This would narrow down our search.
Sure. Ask for any information which w
On Sunday 12 August 2012 05:37:03 Harald Becker wrote:
> Hi All !
>
> >I think some strace or gdb or valgrind is needed
> >to see what this memory refers to.
>
> As this machine is not installed for development those debugging aids
> are not available ... but I fiddled a bit and got strace runnin
Hi All !
>I think some strace or gdb or valgrind is needed
>to see what this memory refers to.
As this machine is not installed for development those debugging aids
are not available ... but I fiddled a bit and got strace running ...
... first result: Running the script via strace did not trigge
Hi Walter !
>I have no idea about your environment, but i had a similar problem
>some time ago and found mount --bind handy.
My current system was the first approach to this vserver like
installation. Over the time it summed up of over 100 active "mount
--bind" ... and I'm planing to reorganize a
On Saturday 11 August 2012 18:20:29 Harald Becker wrote:
> Hi Tito !
>
> >GNU C Library (Debian EGLIBC 2.11.3-3) stable release version 2.11.3,
> >Compiled by GNU CC version 4.4.5.
> >Compiled on a Linux 2.6.32 system on 2012-02-13.
> >
> >./busybox
> >BusyBox v1.21.0.git (2012-08-10 21:15:09 CEST
Hi Tito !
>GNU C Library (Debian EGLIBC 2.11.3-3) stable release version 2.11.3,
>Compiled by GNU CC version 4.4.5.
>Compiled on a Linux 2.6.32 system on 2012-02-13.
>
>./busybox
>BusyBox v1.21.0.git (2012-08-10 21:15:09 CEST) multi-call binary.
>BusyBox is copyrighted by many authors between 1998
On Saturday 11 August 2012 11:23:43 Harald Becker wrote:
> Hi Tito !
>
> >Had to modify the script a little
>
> Doesn't matter. The gawk check was just for comparison.
>
>
> ># use prefered applet feature awk
> >awk -f "w.awk" "w.txt"
>
> This is the one still failing on my side :-(
>
>
> D
Am 11.08.2012 12:36, schrieb Harald Becker:
> Hi Michael !
>
>
>> PATH=/busybox:$PATH ./busybox.shell.script
>>
>> where /busybox contains (sym)links for all busybox applets.
>
> Sure, it is possible to create a directory with all the symlinks to
> Busybox ... but that's definitely not what I
Hi Michael !
>PATH=/busybox:$PATH ./busybox.shell.script
>
>where /busybox contains (sym)links for all busybox applets.
Sure, it is possible to create a directory with all the symlinks to
Busybox ... but that's definitely not what I want. I used this prefer
applet feature for a long time within
On 11.08.2012 14:03, Harald Becker wrote:
> Hi Walter !
>
>> perhaps you can create a busybox with awk only ?
>
> That wont't help. If Busybox awk is called direct or via symlink it
> works correct. The problem arrise with the standalone/preferred applet
> feature. Which I really want to work, as
Hi Walter !
>perhaps you can create a busybox with awk only ?
That wont't help. If Busybox awk is called direct or via symlink it
works correct. The problem arrise with the standalone/preferred applet
feature. Which I really want to work, as Busybox sit on a System with
most GNU utilities install
Am 11.08.2012 11:23, schrieb Harald Becker:
> Hi Tito !
>
>> Had to modify the script a little
>
> Doesn't matter. The gawk check was just for comparison.
>
>
>> # use prefered applet feature awk
>> awk -f "w.awk" "w.txt"
>
> This is the one still failing on my side :-(
>
>
> Did you use
Hi Tito !
>Had to modify the script a little
Doesn't matter. The gawk check was just for comparison.
># use prefered applet feature awk
>awk -f "w.awk" "w.txt"
This is the one still failing on my side :-(
Did you use my configuration to compile your Busybox binary? Which gcc
and glibc versi
On Friday 10 August 2012 17:21:28 Harald Becker wrote:
> Second repost as this has not got through to list yet ...
> I really have trouble to get that standalone/prefer applet working
> again within Busybox ash scripts. Other applets of Busybox seam to
> fail in same way, not only awk. Need help!
On Friday 10 August 2012 17:21:28 Harald Becker wrote:
> Second repost as this has not got through to list yet ...
> I really have trouble to get that standalone/prefer applet working
> again within Busybox ash scripts. Other applets of Busybox seam to
> fail in same way, not only awk. Need help!
Second repost as this has not got through to list yet ...
I really have trouble to get that standalone/prefer applet working
again within Busybox ash scripts. Other applets of Busybox seam to
fail in same way, not only awk. Need help!
Hi !
I stumbled on some trouble. After modifying a few script
19 matches
Mail list logo
