NC command lacks functionality (?)

2009-01-10 Thread Peter Renzland
with size-optimization and limited resources in mind. It is also extremely modular so you can easily include or exclude commands (or features) at compile time. I.e. that Tomato's nc command has been configured to lack -l functionality? Or is there another explanation. Thanks! -- Peter Renzland

Re: NC command lacks functionality (?)

2009-01-10 Thread Peter Renzland
Thanks Denys! I see that ... config_g:CONFIG_NC=y config_g:# CONFIG_NC_SERVER is not set config_g:CONFIG_NC_EXTRA=y That would explain it. Peter On 09 Jan 10, at 14:22 , Denys Vlasenko wrote: On Saturday 10 January 2009 19:46, Peter Renzland wrote: I am using Tomato 1.23 on a WRT54GL

Interrupt spawns Zombies and Vampires

2009-01-12 Thread Peter Renzland
feature configuration? (No job control) Thanks, -- Peter Renzland BusyBox v1.12.2 BusyBox v1.12.3 Linux 2.4.20 on mips (WRT54GL router) running Tomato ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox

Re: Interrupt spawns Zombies and Vampires

2009-01-12 Thread Peter Renzland
January 2009 22:38, Peter Renzland wrote: When I interrupt (^C) a looping process (ping, tail -f, or a script with a while or for loop in it), busybox version? .config? which shell do you use? (busybox has three) very strange things happen, including ... * a phantom sh process is created

Transcript -- Re: Interrupt spawns Zombies and Vampires

2009-01-12 Thread Peter Renzland
...\ # ### and of course the vamp ate it\ # \ # exit\ # ### that hungry vamp ...\ # exit\ Connection to spadina closed.\ 498 02:52:05 peter \ } Peter On 09 Jan 12, at 20:45 , Denys Vlasenko wrote: On Monday 12 January 2009 22:38, Peter Renzland wrote: When I interrupt (^C) a looping process (ping, tail -f

Re: Interrupt spawns Zombies and Vampires

2009-01-14 Thread Peter Renzland
be a known problem (it isn't). I will happily forward the config information, etc., to the Tomato developer(s). ... more in line ... On 09 Jan 13, at 21:31 , Denys Vlasenko wrote: On Tuesday 13 January 2009 03:37, Peter Renzland wrote: OK. Attaching the config_g I see

tar: corrupted octal value in tar header

2009-09-19 Thread Peter Renzland
Attempts to extract tar files produced by Mac OS X 10.6 (Snow Leopard) files fail with the error: tar: corrupted octal value in tar header from BusyBox v1.14.2 (2009-07-02 18:01:37 CEST) built-in shell (ash) On GNU/Linux 2.4.20, on a Linksys WRT54GL Router (MIPS) running Tomato 1.25. Is

Re: tar: corrupted octal value in tar header

2009-09-20 Thread Peter Renzland
On 09 Sep 19, at 20:32 , Denys Vlasenko wrote: On Sunday 20 September 2009 01:04, Peter Renzland wrote: I am attaching a file: snow.tar snow.tar Description: Unix tar archive Thanks. Works for me. Please post your .config file (mine is attached). Also test with newest busybox

Re: tar: corrupted octal value in tar header

2009-09-20 Thread Peter Renzland
On 09 Sep 20, at 08:05 , Denys Vlasenko wrote: On Sunday 20 September 2009 11:02, Peter Renzland wrote: On 09 Sep 19, at 20:32 , Denys Vlasenko wrote: On Sunday 20 September 2009 01:04, Peter Renzland wrote: I am attaching a file: snow.tar The closest thing appears to be scripts

Re: tar: corrupted octal value in tar header (Apple Snow Leopard)

2009-09-22 Thread Peter Renzland
On 09 Sep 20, at 19:31 , Denys Vlasenko wrote: On Sunday 20 September 2009 23:51, Peter Renzland wrote: It appears ironic that Snow Leopard, The World's most advanced OS, has switched to the POSIX tar format, which according to BusyBox terminology requires OLDGNU_COMPATIBILITY. I do not think

Re: tar: corrupted octal value in tar header (Apple Snow Leopard)

2009-09-23 Thread Peter Renzland
On 09 Sep 23, at 07:11 , Denys Vlasenko wrote: On Wed, Sep 23, 2009 at 5:55 AM, Peter Renzland pe...@dancing.org wrote: On 09 Sep 20, at 19:31 , Denys Vlasenko wrote: On Sunday 20 September 2009 23:51, Peter Renzland wrote: It appears ironic that Snow Leopard, The World's most advanced

Re: tar: corrupted octal value in tar header (Apple Snow Leopard)

2009-09-23 Thread Peter Renzland
On 09 Sep 23, at 11:20 , Denys Vlasenko wrote: Since there is no longer a current POSIX tar standard, perhaps it might make sense to create a Busybox term: NEW APPLE COMPATIBILITY which is equivalent to OLDGNU COMPATIBILITY. I think the question is: do we need to have

Re: tar: corrupted octal value in tar header (Apple Snow Leopard)

2009-09-23 Thread Peter Renzland
On 09 Sep 23, at 11:20 , Denys Vlasenko wrote: Since there is no longer a current POSIX tar standard, perhaps it might make sense to create a Busybox term: NEW APPLE COMPATIBILITY which is equivalent to OLDGNU COMPATIBILITY. I think the question is: do we need to have