And this kernel is without a GUI interface? But to judge by the driver install menus, with ANSI color.
Why do you need Linux on a SURVPC other than to run a PPP driver and browser? I dont think of folks trying to run a network with a SURVPC; I expect folks want to continue to run text editors and small business database tools, like what they've been doing in DOS. So... how do the Linux tools stack up on a SURVPC with the DOS-OS/2 tools folks have been using? What'd be neat, an could prolly be done in less than 10k of assy, would be for the kernel to understand the dos command set, so that it wouldnt bitch on the CLI if you forgot which OS you were running. Be nice if it had a BATCH compiler also. For the kind of stuff I do on my own desktop, curses is like using a yacht to go trout fishing. It's too big, too fast, and cant get in the kind of backwaters I like to fish in. Is there a Linux tool which can convert DOS binaries to run on the Linux CLI? Is there a Linux verion of Ralf Brown? Or is the whole 9 yards in C? And where do the routines C calls come from? I find the whole idea of a tiny kernel interesting, but full of questions. Tiny means fast dont it? 16 bit?
