| 288 |
mateuszvis |
1 |
|
|
|
2 |
%h*** Why would I want to use SvarDOS instead of FreeDOS? ***
|
|
|
3 |
|
|
|
4 |
The FreeDOS project is a free, open-source operating system that aims to be
|
|
|
5 |
100%% compatible with MS-DOS. And it is awesome. So why would I want to use
|
|
|
6 |
SvarDOS instead?
|
|
|
7 |
|
|
|
8 |
%hLong release cycles
|
|
|
9 |
|
|
|
10 |
The FreeDOS project began 29 June 1994. Version 1.0 came around in 2006.
|
|
|
11 |
Version 1.1 has been released in 2012, and the version 1.2 followed in
|
| 1033 |
bttr |
12 |
December 2016. Version 1.3 was released in February 2022. This translates
|
| 667 |
bttr |
13 |
roughly to a 5-years release cycle. Granted, the DOS scene is not as active as
|
|
|
14 |
it used to be, but still, many things happen during a few years. Such
|
|
|
15 |
version-centric approach also requires users to perform full-system upgrades
|
|
|
16 |
every now and then.
|
| 288 |
mateuszvis |
17 |
|
|
|
18 |
SvarDOS is very different in this regard: there are no versions at all.
|
|
|
19 |
Whenever a new program is included into or updated within the distribution, it
|
| 667 |
bttr |
20 |
becomes immediately available through the SvarDOS repository and may be
|
| 288 |
mateuszvis |
21 |
pulled either through the SvarDOS website or SvarDOS' pkgnet tool. Already
|
|
|
22 |
installed systems can be easily kept up-to-date using the distribution's
|
|
|
23 |
package manager.
|
|
|
24 |
|
|
|
25 |
%hConstraints of legal nature
|
|
|
26 |
|
|
|
27 |
The FreeDOS project mimicks a proprietary operating system, with all its APIs
|
|
|
28 |
and peculiarities. For this reason, the project always had to be extremely
|
|
|
29 |
careful about what can and what cannot be included within the FreeDOS
|
|
|
30 |
distribution. As a result, only "free software" (as in freedom, think GPL,
|
|
|
31 |
BSD, and so on) can make its way into the official distribution. While such
|
|
|
32 |
cautious approach is sane and legally safe, it is far from practical for
|
|
|
33 |
users. Allowing exclusively free software means that a high number of useful
|
|
|
34 |
programs, tools and games are left behind. For example "freeware" tools (as in
|
|
|
35 |
"gratis but no source included") are a no-go. Even open-source programs can be
|
|
|
36 |
rejected, if they do not clearly state that they comply with an OSI-approved
|
|
|
37 |
license.
|
|
|
38 |
|
|
|
39 |
SvarDOS, on the other hand, is much more liberal about including packages.
|
|
|
40 |
Basically, anything that is objectively useful, of reasonable quality,
|
|
|
41 |
free/gratis and can be legally distributed in the form of a package, can be
|
|
|
42 |
included in SvarDOS. The only exception is for the "core" system (ie. the
|
|
|
43 |
operating system itself), which must be based exclusively on free/libre
|
|
|
44 |
software. Read more about %lpkgrules.ama:SvarDOS package inclusion rules%t.
|
|
|
45 |
|
|
|
46 |
%hFreeDOS included!
|
|
|
47 |
|
| 674 |
bttr |
48 |
It must be noted, that although the goals of SvarDOS and FreeDOS may be
|
| 288 |
mateuszvis |
49 |
slightly different, SvarDOS wouldn't exist without FreeDOS. Indeed, SvarDOS
|
|
|
50 |
uses the excellent FreeDOS kernel, as well as a few other utilities borrowed
|
|
|
51 |
from the FreeDOS ecosystem.
|
|
|
52 |
|
| 695 |
bttr |
53 |
Read also: %lhistory.ama:SvarDOS origins
|