Why should I implement a service that provides me a db if I could just
use the registry, that works perfectly?
This service would make sense if we would use it for other purposes like
additional informations about files and so on, but I think my idea is
much more easier to implement.
I don't say, it's the best for the future, but it is capable of what I
want it to be, doesn't need many resources and adds a nice feature to
ROS, NT was always lacking.
And I don't want to wait until an NTFS port comes into works, because
that might be in 3 or 4 years and who knows what filesystems we are
using then... maybe already our own, created by Hans Reiser, because I
hates Linus Torvalds for not integrating Reiser4 into the Linux kernel
and wants revenge... who knows, but such a FS would be very fast...
Enough ot...
What I wanted to say is, I want ROS to be capable of symlinks and this
completely independent of the FS it is using.
I think theres no need to implement this into the FS, maybe wo could
write a backup of these regkeys to the harddisk, so they can be imported
into other ROS-installations, but that's not that important now.
Greets,
David Hinz
Rick Langschultz schrieb:
Why not include a system service that implements a
metadata server to
create the symlinks for you. It would be simple to do with a sleepycat
db or embedded mysql engine. Of course the links would have to be
accessible by other processes and applications to be add to the whole
experience. Or wait until an NTFS port comes into works and then
implement symlinks then... Either way they are going to have to be
written into the filesystem one way or the other.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev