Executor 2.0/executorv2.0.iso/pc/linux/extra/docs/maillist/text/archive.96/text2951.txt

Text File | 1996-07-25 | 1.8 KB | 43 lines

In article <[e-mail]>, Rob Browning <[e-mail]> writes:
>>>>>> "V" == Vincent S Cojot <[e-mail]> writes:
>
>
>V> I'd like to ask a small question about executor under Linux: I love
>V> executor and I have installed on an ext2fs partition.  However, the
>V> usual backup programs one would use under Linux complain about that
>V> partition (Mac programs tend to put spaces and other strange
>V> characters in file names). GNU tar complains about Long links and
>V> skips files and cpio simply doesn't like some file names and skips
>V> some files too.
>
>Look at the --null option to GNU tar (find has a complementary
>-print0).  Basically what you want is to pass tar a list of null
>terminated (not whitespace terminated) files.  That way the files can
>have spaces, weird characters, etc.

Unfortunately, adding --null to my tar command line did not seem to make
any kind of difference (current command line: tar --null -cvpzf ...):
tar still complains about Long Links.. could it be that GNU tar has a
limitation on the number of characters in the names of the files handed
to it? I know this is not really the right newsgroup for that but tar
only has problems with my executor partition and the some of the files
and directories on it. At this point, I am a little lost about what to
do to be able to put all files on my executor partition on my backups.

--
,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,
Vincent S. Cojot, Computer Engineering.
Ecole Polytechnique de Montreal, Comite Micro-Informatique.
[e-mail], [e-mail]

They cannot scare me with their empty spaces
Between stars - on stars where no human race is
I have it in me so much nearer home
To scare myself with my own desert places.       - Robert Frost