|
From: Anton A. <ai...@ca...> - 2004-05-08 17:20:54
|
On Sat, 8 May 2004, Szakacsits Szabolcs wrote: > On Sat, 8 May 2004, Anton Altaparmakov wrote: > > On Fri, 7 May 2004, Szakacsits Szabolcs wrote: > > > On Fri, 7 May 2004, Anton Altaparmakov wrote: > > > > At this point I would also like to say that I am no longer going to work > > > > on NTFS on 2.4 kernels as many of the write support changes to come > > > > > > What's the plan, priorities, schedule? > > > > plan: Slowly and extremely carefully move the code from ntfs-2.5-devel > > repository to the ntfs-2.6 repository splitting it up into obviously > > correct chunks, one release each. > > I see: > 2.2.0-WIP - More write support: Add inode writing and resident file overwrite. > > http://linux-ntfs.bkbits.net:8080/ntfs-2.5-devel/anno/fs/ntfs/ChangeLog@1.157?nav=index.html|src/|src/fs|src/fs/ntfs|hist/fs/ntfs/ChangeLog|diffs/fs/ntfs/ChangeLog@1.157 > > Were these done recently or BK has some datum bugs? It says these > 2.2.0-WIP changes were done in 2002 :-o Correct! It was a looong time ago. I never had time since to work on it really... and since it had the deadlock I couldn't just merge/release it so it has been dormant since then. Only recently I got to looking at it again and noticed that a lot of the bits were quite trivial and I added the logfile checking / dirty detection and that was what went into 2.1.7 and 2.1.8. > > Apart from that there isn't much of a plan, really, except the same > > what I have always said about how I want to go about implementing > > write support and I don't want to repeat myself now. > > No need to repeat yourself, it would be more than enough if you pointed > out where you wrote about it once. Unfortunately I've never seen this > written on this developer list in the last two years, also nothing such > thing on the web site. Even google failed for me. > > Or is it the TODO part in the driver's ChangeLog? BK also says it's from > 2002. Is that correct or a BK misfunction? That is that old too... I am afraid it is quite possible that my plans have only ever existed on IRC and/or private emails... > But please don't feel pressured to answer, people just asking me too and I > don't have the slightest clue about your plans, I can give just optimistic > estimates how long a full or better partial NTFS write support can take if > the project restarted the work on it. > > Your original sentences suggested for me that significant changes, new big > features are coming soon what apparently I misunderstood. Not that soon, no. Although having resident file overwrite is a pretty important feature. And being able to write mft records / dirty inodes is a pretty big feature for the driver internals as it allows all sorts of code to be added in various places to do different things. E.g. allows to start on file truncation support which means you can write and resize files. It also allows work on access time updating to start. And if anyone is so inclined (FlatCap was working on this but he is deNTFSing his life at the moment...) directory writing code can start to be added. All sorts of things can start happenning really... I will get back to you at a later time with what my personal plans for working on the driver look like. At the moment I have my 8-month-old girl sitting on my lap and I need to go and play with her as she is getting rather bored... Cheers, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/ |
