The LTOOLS are a set of command line tools to read and write Linux extended 2/3 and ReiserFS filesystems (Linux's standard filesystems) from DOS or Windows (XP, 2000, NT, ME, 9.x or 3.x) running on the same machine. So whenever you're running DOS or Windows and you desperately need to read or write that most important file, which resides on your Linux disk, you should use it ... Besides that, you can repair your Linux system from DOS, if your Linux system does not boot anymore ...
If you don't like command line tools, you may use LTOOLSgui , which is a Java based graphical user interface ("Explorer like") for local or remote access to your Linux files. Or you may use LTOOLSnet , which is a .NET based user interface, also providing local or remote access.
If you don't like Java or .NET, use your web browser as a graphical frontend for the LTOOLS. To achieve this functionallity, the package contains LREADsrv , which is a simple web server, making your LINUX (and DOS) filesystem available in an Explorer-like view in your web browser. Using LREADsrv, you also have remote access to your LINUX filesystem as well as to your DOS/Windows filesystem.
Beginning with version 3.3 the complete LTOOLS suite is also running under UNIX, Solaris ... .
To support ReiserFS, the LTOOLS use a modified version of Gerson Kurz's RFSTOOL. Gerson's RFSTOOL provides read only support under Windows NT/2000/XP and Linux. As a new feature starting with LTOOLS V6.8, the UID, GID and file access rights of ReiserFS files can be changed now too.
More details about the LTOOLS can be found here.
The newest version of the LTOOLS can be downloaded from here.
Please note: Extended 3 filesystems do offer several new features, which are not or not fully supported by the LTOOLS. Many distributions do not or only partly use these new features by default, but this may change with new releases of these distributions. Some features do not cause problems for the LTOOLS, some do. So your mileage may vary. In most cases, the command line tools still do work at least partly, issuing some failure messages, whereas the GUIs do not work. Due to lack of time, no promises, when these problems will be solved. Help is welcome.
If you find any bugs, please read the READ.ME file included in the package. If that does not solve the problem, feel free to send an email, including a detailed description of the problem and how you tried to fix it.