Hi,
On Fri, 2003-11-14 at 06:48, Szakacsits Szabolcs wrote:
> > ntfsresize is an embarrassing mess.
Isn't almost all software? (-; I would say that libntfs and ntfsprogs
is actually much less of a mess then a lot of commercial software out
there... which is why they don't show anyone their sourcecode in fear
of noone wanting to use their software afterwards. (^-;
> > There are three ways a program call our code: exec, load or compile.
> > At the moment everything's relying on exec. It's an awful, clumsy
> > method, but it works. ntfs.so is too low a level to be useful, so we
> > could use application-level shared lib ntfsapps.so.
>
> Aha! Now I understand why you're doing some of the things that didn't make
> any sense before.
>
> However I think ntfsapps.so doesn't sound very good. Maybe one lib between
> the two levels, if you don't want too feature rich libntfs (already 65 kB
> but I think a _LOT OF_ duplicated code could be removed from there also).
>
> Of course having more libs will result more problems (see e.g. people
> having problems with reiserprogs, progsreiser, etc).
That is true. I am not sure whether we should just have one libntfs
which does both lower and higher level functions or two (or more)
independent libraries. I think I will just go with whatever people
implement.
> > Our tools are useful, already, but there is so much room for improvement.
>
> There is always, everywhere :) That's why prioritizing shouldn't be
> completely neglected. Just do whatever you think is important, my only
> request is, please regard the working functionality.
I agree. It is all a matter of priorities and each of us has a different
set of priorities. All of us have very little time to work on ntfs,
Rich, Szaka, myself, and everyone else no doubt, all have many
commitments in real life so we can never achieve a professional full
fledged ntfs library. I think that would be a lost cause... Unless
several of us worked full time on it anyway... The best we can do is
for each of us to work on things they are interested while trying not to
break things for the others (or to at least fix them afterwards).
My personal focus is only on low level stuff as I am interested in
getting the kernel driver finished and libntfs and ntfsprogs is nothing
more than a useful testbed/development environment for me. It's a lot
easier to develop ntfs when you don't gave to worry about the kernel
crashing, damaging non-ntfs related file systems, etc... (-; And then
there are useful things like ltrace, ddd, etc as a bonus.
So while I would love to have lots of things cleaned up and organised in
ntfsprogs / libntfs I think I will just keep going with ntfstruncate
related library functionality until that is finished and I hope that
everyone else will keep doing whatever it is they would like to see
done. (-:
Just adding my thoughts...
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/
|