LDE 2.6.1 review

by rbytes.net on

LDE is a Linux disk editor for Minix/Linux partitions

License: GPL (GNU General Public License)
File size: 0K
Developer: Scott Heavner
0 stars award from rbytes.net

LDE is a Linux disk editor for Minix/Linux partitions. It currently supports what were once the three most popular file systems under Linux: ext2fs, minix, and xiafs (there is also a "nofs" system under which lde will function as a binary editor).

There is also minimal support for msdos/fat filesytems and very minimal support for ISO9660 cdrom based filesystems. LDE allows you to view and edit disk blocks as hex and/or ASCII, view/navigate directory entries, and view and edit formatted inodes.

Most of the functions can be accessed using the program's curses interface or from the command line so that you can automate things with your own scripts.

LDE can also be used to recover files which may have been accidentally erased or just to poke around the file system to see what it's made of.

I've included a short introduction to the Minix file system (just enough to get the ideas of blocks and inodes across to most people) and some docs on the ext2fs (mostly just data out of < linux/ext2_fs.h > formatted as tables to make wading through the disk blocks a little bit easier).

If you aren't familiar with inode based file systems, you should have a look at those files before proceeding to the doc/UNERASE file, which details what I think you might try to recover a file.


The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation.

It uses those values to create a `Makefile' in each directory of the package. It may also create one or more `.h' files containing system-dependent definitions.

Finally, it creates a shell script `config.status' that you can run in the future to recreate the current configuration, a file `config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output (useful mainly for debugging `configure').

If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail diffs or instructions to the address given in the `README' so they can be considered for the next release.

If at some point `config.cache' contains results you don't want to keep, you may remove or edit it.

The file `configure.in' is used to create `configure' by a program called `autoconf'. You only need `configure.in' if you want to change it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system.

If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute `configure' itself.

Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make' to compile the package.

3. Optionally, type `make check' to run any self-tests that come with the package.

4. Type `make install' to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'.

There is also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.

LDE 2.6.1 search tags