> 1. Less kernel bloat. The tool will only be in memory when it's
> actually in use, whereas kernel code is normally a permanent
> feature of the memory map.
well some sort of raw i/o driver would be all that is necissary right?
that should be small, and could be used for other things too. Do we
allready have such a thing?
> 2. Libraries. Userland tools can make full use of the standard
> libraries such as libc which are not available to kernel code.
this gets back to the 'how to emulate a tty' question though, so as to not
have to add code to libc or something to support these devices.
> 3. Easier development. In my experience, it's much easier to debug
> userland stuff than kernel code.
sure is.
Tracy Camp 503.380.3218
Hurrah Internet Services campt@hurrah.com
Consultants to the Networked World http://www.hurrah.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/