load jars from NTFS under linux

[Thomas]

Hi folks,

is there any obvious reason why the java compiler
cannot load jars from an NTFS filesystem under Linux (Debian) ?
I know for sure that the path I specify is correct and
I have read permit on that FS (not write though). I can
actually list the content of the jar with any standard
linux utility (cat, less...).
If I copy the same jar on my ext2 fs with the same
permissions (that is 444) the compilation runs just fine.
Any ideas/hints ?

Thomas

[Aragorn]

Re: load jars from NTFS under linux

On Saturday 15 July 2006 21:22, Thomas stood up and spoke the following
words to the masses in /comp.os.linux.m isc...:/

Hi folks,
>
is there any obvious reason why the java compiler
cannot load jars from an NTFS filesystem under Linux (Debian) ?
I know for sure that the path I specify is correct and
I have read permit on that FS (not write though). I can
actually list the content of the jar with any standard
linux utility (cat, less...).
If I copy the same jar on my ext2 fs with the same
permissions (that is 444) the compilation runs just fine.
Any ideas/hints ?

Just an educated guess: the double end_of_line character used by
DOS/Windows maybe?

UNIX only has a newline character at the end of each line, but DOS,
Windows and OS/2 have both a carriage return and a newline character at
the end of a line.

Like I said, just a guess. Your mileage may vary... ;-)

--
With kind regards,

*Aragorn*
(Registered GNU/Linux user #223157)

[Sigmund Hansen]

Re: load jars from NTFS under linux

Aragorn wrote:

On Saturday 15 July 2006 21:22, Thomas stood up and spoke the following
words to the masses in /comp.os.linux.m isc...:/
>

>Hi folks,
>>
>is there any obvious reason why the java compiler
>cannot load jars from an NTFS filesystem under Linux (Debian) ?
>I know for sure that the path I specify is correct and
>I have read permit on that FS (not write though). I can
>actually list the content of the jar with any standard
>linux utility (cat, less...).
>If I copy the same jar on my ext2 fs with the same
>permissions (that is 444) the compilation runs just fine.
>Any ideas/hints ?

>
Just an educated guess: the double end_of_line character used by
DOS/Windows maybe?
>
UNIX only has a newline character at the end of each line, but DOS,
Windows and OS/2 have both a carriage return and a newline character at
the end of a line.
>
Like I said, just a guess. Your mileage may vary... ;-)
>

I think zip(jars are zips) files are supposed to have CR LF combos.
Bzip and gzip are probably LF only, for any newlines though, but jar
uses the zip format.

[bowman]

Re: load jars from NTFS under linux

Aragorn wrote:

UNIX only has a newline character at the end of each line, but DOS,
Windows and OS/2 have both a carriage return and a newline character at
the end of a line.

Where do the extra characters get added/removed? The OP said that the jar
works if it is copied to an ext2 partition. afaik, the only utility that
messes with terminators is ftp in the text mode. Unfortunately, many
Windows ftp implementations default to text and will add carriage returns
to binary files.






----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[John W. Kennedy]

Re: load jars from NTFS under linux

Sigmund Hansen wrote:

Aragorn wrote:

>On Saturday 15 July 2006 21:22, Thomas stood up and spoke the following
>words to the masses in /comp.os.linux.m isc...:/
>>

>>Hi folks,
>>>
>>is there any obvious reason why the java compiler
>>cannot load jars from an NTFS filesystem under Linux (Debian) ?
>>I know for sure that the path I specify is correct and
>>I have read permit on that FS (not write though). I can
>>actually list the content of the jar with any standard
>>linux utility (cat, less...).
>>If I copy the same jar on my ext2 fs with the same
>>permissions (that is 444) the compilation runs just fine.
>>Any ideas/hints ?

>>
>Just an educated guess: the double end_of_line character used by
>DOS/Windows maybe?
>UNIX only has a newline character at the end of each line, but DOS,
>Windows and OS/2 have both a carriage return and a newline character at
>the end of a line.
>>
>Like I said, just a guess. Your mileage may vary... ;-)
>>

>
I think zip(jars are zips) files are supposed to have CR LF combos.
Bzip and gzip are probably LF only, for any newlines though, but jar
uses the zip format.

No, the ZIP programs normally treat all files as binary, although some
unzip programs can optionally be told to try to convert text files from
whatever they are to whatever is the native. Furthermore, copying a JAR
(or ZIP) file from one filesystem to another would not alter it in the
slightest.

The original poster has not mentioned how he is accessing this NTFS. By
mount, with NTFS code in Linux? By SAMBA? Some other way?

--
John W. Kennedy
"The blind rulers of Logres
Nourished the land on a fallacy of rational virtue."
-- Charles Williams. "Taliessin through Logres: Prelude"

[Ricardo Palomares Martínez]

Re: load jars from NTFS under linux

bowman escribió:

Aragorn wrote:
>

>UNIX only has a newline character at the end of each line, but DOS,
>Windows and OS/2 have both a carriage return and a newline character at
>the end of a line.

>
Where do the extra characters get added/removed? The OP said that the jar
works if it is copied to an ext2 partition. afaik, the only utility that
messes with terminators is ftp in the text mode. Unfortunately, many
Windows ftp implementations default to text and will add carriage returns
to binary files.
>

Maybe the JAR looks for its own pathname and tries to write some files
in the same directory? As NTFS partitions are usually mounted as
read-only in Linux, the writing would fail and the program would end
with an exception. :-?


--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?