[Fault-injection-developer] naming used for kernel components

[Lynch, R. <rus...@in...>]

I'm not sure if anyone else is having this problem, but the naming of the
files is really throwing me for a loop.  It seems that every time I look at
one of the file names or directory names I have to think hard about what is
inside instead of it being obvious from the name.

For example, I don't remember what in the world aslt/aslt.c was supposed to
be, but I know I ran across some documentation in some file, but I lost it.
Typically the names of 'c' files in the kernel tree give you a pretty good
clue about what you are looking at.

What if we took a slightly different approach to this:  
* since we need to separate the kernel code from the user space code, why
not use the term "fith" to just refer to the user space tools that take
advantage of the fault injection functionality in the kernel.  
* if you buy into the above argument, then we could start using the letters
"fi" to indicate fault injection in a naming schema used for kernel code.
From most of my searching for fault injection technology on the net, "fi" is
a really common abbreviation for "fault injection".
* instead of intcpt, we could use "fi_interceptor" which is still fairly
short (well kinda) but is much more descriptive.

I noticed some others by they escape me for now... I'll come back with a
better list.

	-rusty