On Mar 3, 7:26 am, Gadrin <[EMAIL PROTECTED]> wrote:
> On Mar 2, 9:59 pm, [EMAIL PROTECTED] (Bob Proulx) wrote:
>
>
>
> > Gadrin wrote:
> > > do you get only folders and the structure (no files) on a test on your
> > > system ?
>
> > Correct.  I only get directories not files.
>
> > Here is a test hierarchy of directories and files.
>
> >   mkdir dir1 dir2 dir3
> >   mkdir dir1/foo
> >   mkdir dir1/foo/bar
> >   mkdir dir2/foo
> >   touch dir1/foo/bar/FILE
> >   touch dir1/foo/FILE
>
> >   find . -exec ls -ldog {} +
> >   drwxrwxr-x 5 4096 2008-03-02 22:54 .
> >   drwxrwxr-x 3 4096 2008-03-02 22:54 ./dir1
> >   drwxrwxr-x 3 4096 2008-03-02 22:54 ./dir1/foo
> >   -rw-rw-r-- 1    0 2008-03-02 22:54 ./dir1/foo/FILE
> >   drwxrwxr-x 2 4096 2008-03-02 22:54 ./dir1/foo/bar
> >   -rw-rw-r-- 1    0 2008-03-02 22:54 ./dir1/foo/bar/FILE
> >   drwxrwxr-x 3 4096 2008-03-02 22:54 ./dir2
> >   drwxrwxr-x 2 4096 2008-03-02 22:54 ./dir2/foo
> >   drwxrwxr-x 2 4096 2008-03-02 22:54 ./dir3
>
> > Here is a test case:
>
> >   find . -type d | tar cf - -T- --no-recursion | tar tvf -
> >   drwxrwxr-x bob/bob           0 2008-03-02 22:54 ./
> >   drwxrwxr-x bob/bob           0 2008-03-02 22:54 ./dir1/
> >   drwxrwxr-x bob/bob           0 2008-03-02 22:54 ./dir1/foo/
> >   drwxrwxr-x bob/bob           0 2008-03-02 22:54 ./dir1/foo/bar/
> >   drwxrwxr-x bob/bob           0 2008-03-02 22:54 ./dir3/
> >   drwxrwxr-x bob/bob           0 2008-03-02 22:54 ./dir2/
> >   drwxrwxr-x bob/bob           0 2008-03-02 22:54 ./dir2/foo/
>
> > Only directories are processed.  Works for me.
>
> > Bob
>
> Okay, it must be windows that's having the problem.
>
> Mine finds only folders but when that path is passed to tar, it thinks
> I'm
> specifying the entire folder with no restrictions.
>
> Looks like xcopy is it for now.
>
> Can you recommend a decent GNU shell ? When I downloaded the
> GNU core utils it came with SH.EXE and I recently downloaded WIN-
> BASH.EXE
> but I can't find documentation. Apparently it uses different paths and
> doesn't see
> the .EXEs that I have in the same folder.
>
> I guess I have more digging, but for now it's workable.

Thanks for your help.

Reply via email to