On Thu, 18 Mar 2010 17:45:36 -0600, Mark Post <mp...@novell.com> wrote:
>>>> On 3/18/2010 at 06:53 PM, Paul Gilmartin <paulgboul...@aim.com> wrote:
>> And Samba doesn't convert line separators:
>
>It doesn't do it by design. It's a file server, not a data manglement server.
>
The z/OS NFS server, by contrast, converts line separators
in Classic data sets.
>> o Possibly because it might not be revertible?
>
>Indeed. Revertible to what? No way to know just what kind of client is
>connecting.
>
The client knows; if the conversion were done, it could
be done by the client (not that I'm recommending this.)
>> o Possibly because file size isn't readily available?
>
>The file system keeps track of this, not Samba. It has access to that
>information.
>
But if Samba (client or server) were to convert, e.g. LF<-->CRLF,
the size would appear wrong to the end user.
>> For major cluelessness, you should see the mess Samba
>> makes of case-sensitive filesystems. Charles Mills
>> would rightfully be aghast.
>
>Don't blame Samba for this. It simply preserves the case of the file names
>that are given to it by the client. Windows is case insensitive, but case
>preserving. Depending on how people type in the names, that's how they get
>passed to Samba.
>
Someone is to blame. If I have a UNIX directory containing
FRED.txt
Fred.txt
fred.txt
they all appear correctly in the Windows Explorer display. But
when I click on one, it's unpredictable which one opens. I
deem this irresponsible behavior. And, if Windows were to
pass the name as clicked (or typed) the correct file would open.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
