From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: aia21@cam.ac.uk, Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
Cc: lkml@andyjeffries.co.uk, linux-kernel@vger.kernel.org
Subject: Re: Difficulties in interoperating with Windows
Date: Wed, 9 Jan 2002 10:48:47 -0600 (CST) [thread overview]
Message-ID: <200201091648.KAA19440@tomcat.admin.navo.hpc.mil> (raw)
In-Reply-To: <5.1.0.14.2.20020109152921.026ad0a0@pop.cus.cam.ac.uk>
...
> Er, you have to have the same algorithms or at least you need to achieve
> the same input and output which often requires the exact same algorithm
> otherwise you cannot achieve the same input/output...
>
Yup - and then you hit the "trade secrets" problem.
> To give a concrete example from ntfs, when collating attribute names (and
> file names for the matter) in order to determine where to place them in an
> inode, if you do not apply all collation criteria found in the windows
> driver, you will inevitably do the collation wrong at least in some corner
> cases and you have a broken filesystem on your hands when you are writing.
I believe the collating sequence/filenames is documentd. What isn't documented
is how the journal file is handled. How recovery is handled.
I think trying to make that compatable hits the trade secrets. Compatability
is needed if you expect to take a partition from one OS to another and still
have the possible crash conditions handled. NTFS write was (briefly) available
until the lawyers came to the door. Along with an external tool to recover
NTFS file systems.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next prev parent reply other threads:[~2002-01-09 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 9:37 Difficulties in interoperating with Windows Andy Jeffries
2002-01-09 15:06 ` Jesse Pollard
2002-01-09 15:28 ` Andy Jeffries
2002-01-09 16:04 ` Jesse Pollard
2002-01-09 16:29 ` Andy Jeffries
2002-01-09 19:06 ` Jesse Pollard
2002-01-09 16:22 ` Alan Cox
2002-01-09 16:34 ` Andy Jeffries
2002-01-09 17:09 ` Alan Cox
2002-01-10 8:34 ` Helge Hafting
2002-01-10 3:32 ` David Schwartz
2002-01-09 16:14 ` Anton Altaparmakov
2002-01-09 16:48 ` Jesse Pollard [this message]
2002-01-09 17:17 ` Alan Cox
2002-01-09 17:29 ` Anton Altaparmakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200201091648.KAA19440@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@andyjeffries.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox