*) Need more robust checks, still crashes occasionally if
   an inode/block is out of range.

*) If you edit a block with inodes on it in block_mode, 
   then view it under inode mode, the inode will be incorrect
   until you view another inode and come back to this one.
   (This is only a problem with ext2fs -- see EXT2_read_inode).

*) No inode edit yet -- can do it from block mode with 
   documentation, but it isn't pretty.

*) Put up more super block info.  It was fine for Minix, but
   ext2 has a lot more "junk".

*) Still have to teach how to use a triple indirect block.
   It is only used for file recovery -- just don't delete any
   really big files.

*) Maybe play with the colors/highlights some more.  It now
   seems useable for X11, vt100, and the console.  Currently,
   xterm/rxvt use an underline to highlight the block
   since the block cursor is confusing, but something is leaving
   little dots all over the place (ncurses or the xterm).

*) Figure out how to set the number of blocks when using NOFS,
   now it's set to -1L = 0xFFFFFFFF, but lseek doesn't work.

*) Implement search and recover function.  This 
   might not be that hard.  It will be almost impossible
   to reconstruct a file if an indirect block gets hit,
   but it should be easy to write something which will
   search for indirect block patterns (i.e. low/high byte
   pairs that are close to each other) and point out 
   unused blocks on the disk which are indirect or 
   2x indirect, then let the user rebuild the inode entry.
   
   Also, it is pretty easy to search the start of a block 
   for some kind of file magic, pick some useful things like
   gzip, ZIP, shell scripts, maybe even parse /etc/magic if
   it is there.

   (There is some preliminary stuff search code, both pattern 
   and indirect block, which will be included if EMERGENCY
   is defined.)

*) Implement a directory mode:  ls is probably better suited for
   this, but it might be useful to spit out the directory entry 
   with the inode pointer in a consistant spot.  Under minix this
   isn't a terrible problem, it is always in the same spot, but
   with the variable name length fs's, they really don't jump
   out at you in block_mode.

