Well i'll check out what happens if they hit Ctrl-C, as far as i remember is just does nothing (don't gives back the shell).
The need for separate autoexec.bat is "customisation", all clients needs a different paths and this is how the app works in order to account users: must have separate autoexec.bat :( Anyway the dosemu as shell login is a geat idea, i'll try it but there is a little requirement for that: Multiple login not allowed !!! This is an app requirement from the app (again). I'm taking care of this in .bash_profile (or .bashrc). How could we avoid multiple login using dosemu as login shell? I guess there must something in a lower level regarding the "login" process. Guillermo On Sun, 2003-12-07 at 18:51, Justin Zygmont wrote: > > What i'm doing is: > > > > 1.- Client telnet the linux box > > 2.- Client logs in with bash shell > > 3.- .bash_profile takes care of auto-launching the dosemu > > 4.- autoexec.bat takes cares of auto-launching the app > > 5.- As the app quits, the shell autoquits just after > > (no open shell for the user) > > what if they hit CRTL-C ? :) you should be able to set their shell to > dosemu.bin, and see if that works ok. Can you make a seperate login for > each different instance of dosemu, each with their own copy of dosemu, > that way there is no need for a seperate autoexec.bat. You must have a > copy of real MSDOS don't you? > > > - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
