On Tue, 4 Feb 2003, Ryan Underwood wrote:
>
> 1) In 1.0.2.1 stable, why does the following not add the proper "virtual"
> tags to the com ports as expected:
> $ dosemu -I'serial { virtual com 1 } serial { virtual com 2 }
> with obvious rest of command line omitted...
> but, if I add the following stanza to global.conf:
>
> ifdef u_virtual
> serial { virtual com 1 }
> serial { virtual com 2 }
> endif
>
> and then append -u virtual to the dosemu command line:
> $ dosemu -u virtual
>
> the flags get properly set. I thought -I was a shortcut for adding new directives
> into global.conf at runtime. If -I isn't right, is there some way to do
> this besides modifying the global.conf?
there is a bit of privilege checking going on here. If dosemu.bin is
suid-root then many -I options are prohibited. You can try if
dosemu -I 'video{none}'
works. If it does, and serial doesn't then there's a bug somewhere.
Many of these restrictions are lifted now in the 1.1.4 series because
"serial" (and some other options) now solely depends on the file system
permissions; suid-root DOSEMU doesn't use its special powers to access the
relevant devices.
> 2) Was something changed in the vmodem support in 1.1.4 and later pre-releases?
> I tried 1.1.4 and 1.1.4.10 against my global.conf and dosemu.conf that seem
> to work fine in dosemu 1.0.2.1, and every program claims that it can't access
> the fossil driver, can't open the port, etc.
please note that global.conf is, by default, built-in in 1.1.4+, unless
you specify it differently in dosemu.users, so your settings might be
ignored. If it's anything else then there must be some bug in the serial
code.
Bart
-
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
