From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: ugetcwd / uchdir freakiness
Date: Tue, 22 Apr 2003 14:13:08 +0400 [thread overview]
Message-ID: <3EA515B4.5080000@yahoo.com> (raw)
Hello.
Bart Oldeman wrote:
>> done, besides getting rid of all the
>> comcom's problems, 4/5 of the convoluted
>> coopthreads code can be simply thrown away
>> and the rest can be greately simplified.
> that's a bit of a rigorous move
Yes but without it you'll never be able
to close the coopthreads' and comcom's -
related bugs on SF, which will mean the
1.2 will again have the bunch of an
unresolved severe problems.
> on the other hand comcom is better in that it has a persistent
> command history (between DOSEMU sessions)
Many shell programs like DosNavigator
adds this ability a dosemu-independant
way. Users who needs this, generally use
a dosemu-independant way for that.
I guess this can be easily implemented
as an option in a freecom as well.
> the X title display
Will take less than 5 minutes to implement
in a comcom-independant way - wanna see the
patch, just let me know:)
> doesn't need to swap itself to XMS to be lean on DOS memory.
What's the problem with this given
that this is how the things works in
an absence of dosemu?
> Also FreeCOM of course has the same problem as lredir here in that it
> can also only be compiled with tcc.
No, it can be included in a dosemu-freedos
package.
> Well of course kernel.sys has the same
Exactly. The helper tools are dosemu-specific
so building them inside dosemu is logical -
they need to talk to dosemu anyway.
OTOH command.com is just a part of a
DOS distribution, just like the kernel.sys.
Handling these two differently is not
justified. We could just as well write an
internal NortonCommander etc...
> All in all, I think that comcom is good enough as the basic command
> interpreter, and those who want to use FreeCOM (or 4DOS or whatever)
> instead know where to find it.
Doesn't look like a real reason for
keeping such a headache with us (both the
comcom and coopthreads are known to be
problematic and there will be nothing
changed in the near future here, while
all the other problematic areas are
getting extensively patched). The freedos
package is required to run dosemu out-of-box
anyway, so the comcom's presense doesn't
help a lot also here.
So there might be other reasons I guess,
probably they are less technical though...
next reply other threads:[~2003-04-22 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 10:13 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-21 23:08 ugetcwd / uchdir freakiness Stas Sergeev
2003-04-22 1:00 ` Bart Oldeman
2003-04-21 16:39 Stas Sergeev
2003-04-21 21:44 ` Bart Oldeman
2003-04-17 10:09 Pawel Szymczykowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EA515B4.5080000@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox