Adam Williamson <[EMAIL PROTECTED]> writes:
> N.B. This driver has now been abandoned in favour of the new one.
driver has nothing to do with resizer.
resizing is a lot much easier than having writing support (which
assumes having resolving all interactions between vfs/mm/ntfs
regarding file holes, truncation, mapping with
compressed/crypted/with_attributes inodes and the like.
unlike having fully reliable write support, resizing does not involve
manipulating file attributes but only file system truncation or
expansion, that is only truncating/expanding fs structures.
> Add support for writing.
>
> mkntfs Stable Create an NTFS volume on a partition
> ntfsfix Beta Tell windows we've made changes to a volume
> ntfslabel Beta Display or set a volume's label
> ntfsresize Beta Resize an NTFS volume
>
> Note particularly the Beta status of those last three tools, and the
> warning on the front page to back up your data before using the beta
> tools...
as of ntfsresize:
"Is it reliable?
Since July of 2002, when ntfsresize became publicly available,
there were success reports resizing Windows NT4, 2000, XP and .NET
NTFS filesystems on both workstation and server versions (Home,
Professional, Server, Advanced Server). NO DESTROYED FILESYSTEM
WAS REPORTED SO FAR. DURING THIS TIME THERE WERE NO CORE CHANGES
OR FIXES IN THE SOURCE SO WE SUPPOSE THE CODE MUST BE
RELIABLE. However much more widely usage is needed to state it's
stable thus we strongly recommend to have a backup of your data
(you have anyway, haven't you ;)"
since i was able to bough a good box for 500 euros last week, i ended
in buying a box with xp preinstalled.
this was time to test ntfsresize.
it seems to works fine but mark the fs as dirty so that zindoz check
it on reboot.
we all agree it need *lots* of testing but it seems to be usable.
of course we'll have to display a very big warning.
