This is a subjective subject (oh, man...)
For me, debug is essential for programming. But I don't think it will be
of much usage to have it included by default. To "boot" the system and
establish networking, it is not needed. So it can be downloaded later,
if necessary.
But I recall old systems with BASIC language embedded (or a debug
environment). In emergencies, having some sort of debug system could be
useful (to ones which know assembly or BASIC, of course).
Today, I have doubts about the need to have such debug tools straight
away on boot. DOS is not the main OS for no one nowadays, so such tools
can be downloaded apart if needed.
Luzemário Dantas
Em 17/02/2022 07:26, Mateusz Viste via Svardos-users escreveu:
On 17/02/2022 10:51, Carsten Strotmann via Svardos-users wrote:
While I am pretty sure option 2 is plain stupid, I am mitigated
between options 1 and 3. I think I have a preference for 3, but then
it requires writing some kind of rules that say what kind of
MS-DOS-like packages are not part of SvarDOS, and on what criterion.
I don't really know how to put that in writing objectively.
I would vote for option 3. As the rule, you wrote "include only
things that are truly critical". I think that is a good rule.
That's what I think, as well. The only "problem" I see is a human one,
where some people may argue on the definition of "critical". For
instance recently Robert asked for including DEBUG to the installation
medium, on the grounds that it was part of MSDOS. I did it, even
though I don't find DEBUG that much useful in practice and it takes
55K of valuable space on floppies, but if the rule is "mimic MSDOS"
then it has its place. So what could the rules be, so there is no doubts?
Currently CORE packages (shipped on installation floppies) are these:
AMB <-- required to read HELP files
ATTRIB
CHKDSK <-- FAT-16 only, but 8086-compatible
CHOICE
COMMAND
CPIDOS <-- *.CPX files for codepage loading
DEBUG <-- is this "truly critical"?
DELTREE
DEVLOAD <-- this one is useless, definitely to be removed
DISKCOPY
DISPLAY
DOSFSCK <-- supports FAT32, but requires a 386+
EDIT
FC
FDAPM <-- replaces POWER.EXE from MSDOS
FDISK
FIND <-- "truly critical"?
FORMAT
HELP
HIMEMX <-- replaces HIMEM from MSDOS
KERNEL
KEYB
KEYB_LAY <-- layouts for KEYB, maybe the two should be merged
LABEL
LOCALCFG <-- replaces COUNTRY.SYS from MSDOS
MEM
MODE
MORE
MOVE
PKG
PKGNET
SHSUCDX <-- replaces MSCDEX.EXE from MSDOS
SORT
TREE
The point is that I'd really like to have some formal set of
rules/guidelines so it's set once and then we don't have to re-discuss
the subject in the future or debate about why a package should or
should not be part the installation.
Mateusz
_______________________________________________
Svardos-users mailing list
Svardos-users@lists.osdn.me
https://lists.osdn.me/mailman/listinfo/svardos-users
_______________________________________________
Svardos-users mailing list
Svardos-users@lists.osdn.me
https://lists.osdn.me/mailman/listinfo/svardos-users
