From: "Geo" 

This is a multi-part message in MIME format.

------=_NextPart_000_00BA_01C652BA.9F8D4C70
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm not sure I like TxF, the thing they call  Consistant Concurrent =
Update sounds like it would cause all sorts of problems for some handy =
functions like=20

tail -f filename

this sounds like it's a service that's constantly running on top of the =
file system, that would make it the sort of thing I usually turn off. =
(like windows file protection)

Geo.
  "Rich"  wrote in message news:4428ab74{at}w3....
     Transaction support is not the same as the rollback in case of a =
system crash.  Transactions provide quite a bit more.  See =
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/fileio=
/fs/what_is_transactional_ntfs_.asp for more info.

  Rich

    "Geo"  wrote in message news:4428a3e8{at}w3....
    "Rich Gauszka"  wrote in message =
news:442771db$1{at}w3....

    > I think the keywords in the link below are "allows all file =
operations on
    an
    > NTFS file system volume to be performed transactionally" . An =
application
    > through a standard API would be able to group file operations into =
a
    > transaction and commit or abort.  It appears to be yet another =
step in
    > database - file system convergence.

    It sounds the same to me with the difference being that they exposed =
the
    functionality to programs now so it can be monitored by something =
other than
    the OS. W2K NTFS allows the OS to roll back a transaction that =
failed, it
    just did it automatically.

    Geo.


------=_NextPart_000_00BA_01C652BA.9F8D4C70
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








I'm not sure I like TxF, the
thing they =
call =20
Consistant Concurrent Update sounds like it would cause all sorts of = problems=20
for some handy functions like 
 
tail -f
filename
 
this sounds like it's a service that's =
constantly=20
running on top of the file system, that would make it the sort of thing = I=20
usually turn off. (like windows file protection)
 
Geo.

  "Rich" <{at}> wrote in message news:4428ab74{at}w3....
    
Transaction support is =
not the same=20
  as the rollback in case of a system crash.  Transactions provide =
quite a=20
  bit more.  See http://msdn.microsoft.com/library/default.asp?url=3D/library/en-u=
s/fileio/fs/what_is_transactional_ntfs_.asp">http://msdn.microsoft.com/li=
brary/default.asp?url=3D/library/en-us/fileio/fs/what_is_transactional_nt=
fs_.asp for=20
  more info.
   
  Rich
   
  
    "Geo" <georger{at}nls.net>=20">mailto:georger{at}nls.net">georger{at}nls.net>=20
    wrote in message news:4428a3e8{at}w3...."Rich
=
Gauszka" <gauszka{at}hotmail.com>">mailto:gauszka{at}hotmail.com">gauszka{at}hotmail.com>
=
wrote in=20
    message news:442771db$1{at}w3....>=20
    I think the keywords in the link below are "allows all file =
operations=20
    onan> NTFS file system volume to be performed =
transactionally" .=20
    An application> through a standard API would be able to group =
file=20
    operations into a> transaction and commit or
abort.  It =
appears=20
    to be yet another step in> database - file system=20
    convergence.It sounds the same to me with the difference =
being that=20
    they exposed thefunctionality to programs now so it can be =
monitored by=20
    something other thanthe OS. W2K NTFS allows the OS to roll back =
a=20
    transaction that failed, itjust did it=20
  =
automatically.Geo.

------=_NextPart_000_00BA_01C652BA.9F8D4C70--

--- BBBS/NT v4.01 Flag-5