[EMAIL PROTECTED] wrote:
> 
> However, you need to have a chance to find out what is 
> going wrong. I mean, the above mentioned ambiguity is 
> just a lack of documentation. 

Brief documentation is provided for all busybox commands.
-------------------
command_name --help
-------------------

> Without Steven's help I  would never have found out that 
> the tar command built into Busybox has a different syntax 
> than the tar binary present on other Linux distributions 

I don't think syntax is the problem.  The busybox tar uses the 
same syntax.  Your problem, I believe, is that the busybox tar 
lacks some parameters.  To see which parameters the busybox
tar understands, do this:
----------
tar --help
----------

> and described in the man pages coming with BasicLinux's HD 
> version.

Perhaps I should remove the tar manpage?

> For those who want to climb the ladder (or at least keep the
> results of their experiments) Steven prepared the HD version. 
> From that moment on it would be possible to replace some commands 
> from Busybox with full featured binary versions. 

That has been done.  The HD version replaces the busybox versions
of head and sed with the full binaries.  Users are free to replace
any busybox command with the full binary from Slackware 3.5 
(although in most cases this is a complete waste of time, since
the busybox versions are quite adequate).

> Just one sentence explaining that Busybox does not support all
> command line options listed on the man pages, 

Which particular command line option is bothering you?

> and where the Slackware versions of those utilities can be obtained.

The busybox commands cover a wide variety of functions.  They will
not be found in a single Slackware package.  For example, uudecode
is in the bin package, df is in the fileutls package, grep is in 
the grep package, gzip is in the gzip package, ps is in the procps
package, sleep is in the sh_utils package, tar is in the tar package,
ping is in the tcpip1 package, tr is in the txtutils package, and 
more is in the util package.  

The simplest way to find the location of a binary is to ask me.

Cheers,
Steven

Reply via email to