Line 1... |
Line 1... |
1 |
|
1 |
|
2 |
%hSvarDOS origins (history from the point of view of its creator)
|
2 |
%hSvarDOS origins (history from the point of view of its creator)
|
3 |
|
3 |
|
4 |
Mateusz Viste, the SvarDOS author, says:
|
4 |
Mateusz Viste says:
|
5 |
|
5 |
|
6 |
In the years 2005-2015, I used to perform packaging work for the FreeDOS
|
6 |
In the years 2005-2015 I used to perform packaging work for the FreeDOS
|
7 |
project. I wasn't pleased with the packaging tool that FreeDOS used back then
|
7 |
project. I wasn't pleased with the packaging tool that FreeDOS used back then
|
8 |
(FDPKG), so in 2012 I started working on a new package manager, with network
|
8 |
(FDPKG), so in 2012 I started working on a new package manager, with network
|
9 |
support, automatic updates, etc - I named it FDNPKG. Later I also devised a
|
9 |
support, automatic updates, etc - I named it FDNPKG. Later I also devised a
|
10 |
scripted way of generating an "always up to date" FreeDOS CD that I
|
10 |
scripted way of generating an "always up to date" FreeDOS CD that I
|
11 |
unimaginatively called "all_cd.iso". This CD included FDNPKG and all the
|
11 |
unimaginatively called "all_cd.iso". This CD included FDNPKG and all the
|
12 |
FreeDOS packages available at the given moment.
|
12 |
FreeDOS packages available at the given moment.
|
13 |
|
13 |
|
14 |
I still wasn't satisfied with how FreeDOS clings to its notion of "releases"
|
14 |
I still wasn't satisfied with how FreeDOS clings to its notion of "releases"
|
15 |
and that it cannot include some software because of licensing issues, so in
|
15 |
and that it cannot include some software because of licensing issues, so in
|
16 |
2016 I decided to create my own distribution, that I called Svarog386 (there
|
16 |
2016 I decided to create my own distribution, that I called Svarog386 (there
|
17 |
was also a Svarog86 project that I had created a couple of months earlier,
|
17 |
was also a Svarog86 project that I had created a couple months earlier,
|
18 |
dedicated to 8086 machines). Svarog386 naturally relied on the FreeDOS kernel
|
18 |
dedicated to 8086 machines). Svarog386 naturally relied on the FreeDOS kernel
|
19 |
and used the FDNPKG package manager.
|
19 |
and used the FDNPKG package manager.
|
20 |
|
20 |
|
21 |
Then, in 2021, I started to be tired of having two separate distributions to
|
21 |
Then, in 2021, I found it increasingly annoying to look after two separate
|
22 |
care about. Over time, FDNPKG also became a huge piece of protected mode code,
|
22 |
distributions. Over time, FDNPKG also became a huge piece of protected mode
|
23 |
and although it was magnificent code, I was no longer happy with it: too many
|
23 |
code, and although it was magnificent code, I was no longer happy with it: too
|
24 |
features, too complex data processing, too high memory requirements... In a
|
24 |
many features, too much data processing, too much memory required... In a
|
25 |
word: too much fluff. I longed for something simpler, that would do perhaps
|
25 |
word: too much fluff. I longed for something simpler, that would do perhaps
|
26 |
less, but with more transparency towards the user - and something that would
|
26 |
less, but with more transparency towards the user - and something that would
|
27 |
work in real mode with not much RAM, so it could be useful even on ancient
|
27 |
work in real mode with not much RAM, so it could run even on ancient 8086
|
28 |
8086 machines.
|
28 |
machines.
|
29 |
|
29 |
|
30 |
The result of these thoughts was SvarDOS: a distribution that replaced both
|
30 |
The result of these thoughts was SvarDOS: a distribution that replaced both
|
31 |
Svarog86 and Svarog386, and that came with its own package manager - a much
|
31 |
Svarog86 and Svarog386, and that came with its own package manager - a much
|
32 |
simpler (and in my opinion much more elegant) tool than FDNPKG.
|
32 |
simpler (and in my opinion much more elegant) tool than FDNPKG.
|