*) Make scrolling work a little better someday.  i.e. if we
   are at the end of a block and hit down arrow, go to the next block
   rather than stopping.  Display end of last block and start of
   this block on the same screen. 

*) Update the tty stuff.  Inodes aren't fully dumped (just info for 
   a minix inode is displayed -- but it will work on any fs).  Use
   Ted's debugfs if you want a tty driven ext2 hacker.
 
*) For some reason, the INDIRECT_BLOCK label doesn't show up on the
   minix inode display.  A virtual nickel goes out the first person
   who can figure out what is wrong -- I'm assuming it is something
   obvious which I'm just blocked on.

*) Directory mode, add support to follow indirect blocks.

*) 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).
   (Actually, it is a bigger problem with the other fs's which 
   store the inode tables in memory.)

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

*) Throw in more inode info.  What are the inode.flags for
   ext2 anyways?

*) 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 ALPHA_CODE
   is defined.)

