On Tue, Oct 04, 2011 at 01:32:39PM -0400, RiverWind wrote:
> When attempting to extract "rar" files in either Linux or Unix, the
> file naming protocol seems to be a very crucial issue. To wit,
> should a file be fraught with open spaces, many Unix and Linux
> utilities will not work, because it seems that MS-Windows allows
> for blank spaces within file names, whereas Dos, Linux and Unix do
> not. This would seem to be the case from my personal point of view
> based upon recent experience.
Why not?
$ touch "file with spaces.txt"
$ ls
file with spaces.txt
> I am attempting to extract a large number of rar files using
> "unrar-free" with no success. I understand that it might be
> necessary to rename each and every file and put some sort of filler
> in each blank space, such as a question mark or some other type of
> punctuation. I am not sure if this is the case or not.
What command are you executing? You're probably just missing the necessary
syntax to handle the spaces correctly, such as escaping or quoting.
> Ultimately this whole matter is nothing more than a product of the
> ever-present conflict/ difference between MS_Windows and other
> systems that lead to all manner of compatibility issues. Linux, DOS
> and Unix users are for ever trying to find work-around solutions to
> these compatibility problems. So, how would you Linux users go
> about processing "rar" files that were produced in Windows using
> Linux software? Would you try to do some sort of "unrar" or would
> you try to convert them over to some version of zip format? If so,
> would you try some variant of gzip?
Generally, you won't find .rar archives on *n*x machines, but rather,
you're more likely to find .tar.gz, .tar.xz, .cpio, etc. But, should you
need to work with RAR archives, the tools are available.
--
. o . o . o . . o o . . . o .
. . o . o o o . o . o o . . o
o o o . o . . o o o o . o o o
Attachment:
signature.asc
Description: Digital signature