On Thu, 30 Nov 2006, Anton Altaparmakov wrote:
>
> I understand the impact 100% which is why my patch is so big. It had to
> touch a lot of utilities to adapt for the changed libntfs behaviour.
The impact to resizing any kind of NTFS. There are many special cases and
ntfsresize works quite differently as you believe. It has its own attribute
resizer, cluster allocator, modifies mft records and not inodes, has strict
ordering of the modifications, etc.
You don't know what you fixed and how fixed. Still you think it doesn't have
any side-effects anywhere because it seems it workes a few times. And you
simply ignore all the cases which did work beforehand.
> How would you tell if it is a Vista partition or not?
Detect Vista specific files which are always present.
> How do you know that the partition you are resizing is not going to be
> attached to a Vista machine next?
I think it would work fine. The problem is with Vista volumes, not random
volumes attached to Vista.
> You just can't cope with the idea that someone touches code you have
> written...
I asked very simple technical questions from you:
- How the journal looks on Vista after resizing without your patch?
- What did you fix?
The first would have taken about 1-2 minutes from you. I even showed how
you can do this. You keep it ignoring. Only you have Vista, unfortunately
I don't. You also don't know what in fact you have fixed.
I'm only interested in the technical explanation but that's not coming.
Only "works for me" which I can't consider responsible software engineering,
especially considering that how many people are using the software. Sorry.
Regards,
Szaka
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
