mirror of
https://github.com/Zeal-Operating-System/ZealOS.git
synced 2024-12-30 17:26:31 +00:00
59 lines
3.5 KiB
HTML
Executable file
59 lines
3.5 KiB
HTML
Executable file
<!DOCTYPE HTML>
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html;charset=US-ASCII">
|
|
<meta name="generator" content="ZealOS V1.04">
|
|
<style type="text/css">
|
|
body {background-color:#1f1f1f;}
|
|
.cF0{color:#e3e3e3;background-color:#1f1f1f;}
|
|
.cF1{color:#4f84a6;background-color:#1f1f1f;}
|
|
.cF2{color:#73a255;background-color:#1f1f1f;}
|
|
.cF3{color:#297582;background-color:#1f1f1f;}
|
|
.cF4{color:#b34f4b;background-color:#1f1f1f;}
|
|
.cF5{color:#8a52c3;background-color:#1f1f1f;}
|
|
.cF6{color:#b7822f;background-color:#1f1f1f;}
|
|
.cF7{color:#444444;background-color:#1f1f1f;}
|
|
.cF8{color:#6d6d6d;background-color:#1f1f1f;}
|
|
.cF9{color:#94bfde;background-color:#1f1f1f;}
|
|
.cFA{color:#a1ce97;background-color:#1f1f1f;}
|
|
.cFB{color:#6db4be;background-color:#1f1f1f;}
|
|
.cFC{color:#e88e88;background-color:#1f1f1f;}
|
|
.cFD{color:#ca94e8;background-color:#1f1f1f;}
|
|
.cFE{color:#d4b475;background-color:#1f1f1f;}
|
|
.cFF{color:#1f1f1f;background-color:#1f1f1f;}
|
|
</style>
|
|
</head>
|
|
<body>
|
|
<pre style="font-family:monospace;font-size:12pt">
|
|
<a name="l1"></a><span class=cF5> RedSea Reliability</span><span class=cF0>
|
|
<a name="l2"></a>
|
|
<a name="l3"></a>ZealOS is like the 1040EZ tax form compared to the full 1040 form. Obviously, it is simpler. If you allow mission creep,
|
|
<a name="l4"></a>pretty soon the 1040EZ looks just like the 1040 and the messed-up 1040EZ has no purpose.
|
|
<a name="l5"></a>
|
|
<a name="l6"></a>The Commodore 64 had a file system that was simple enough for peers in Terry's generation to enjoy the thrill of knowing
|
|
<a name="l7"></a>exactly what is going on at the hardware level and writing fun projects to access it.
|
|
<a name="l8"></a>
|
|
<a name="l9"></a>The primary design criteria is simplicity. If it is simple enough for only 100,000 people to learn, lets try to make it
|
|
<a name="l10"></a>simpler so that 1 million can learn it.
|
|
<a name="l11"></a>
|
|
<a name="l12"></a>Obviously, we don't do bad block tables, or redundant FATs.
|
|
<a name="l13"></a>
|
|
<a name="l14"></a>We use the simplest possible technique, a contiguous-file-only allocation bitmap, not </span><a href="https://zeal-operating-system.github.io/ZealOS/Doc/BlkChain.DD.html#l1"><span class=cF4>Block Chains</span></a><span class=cF0> or FAT tables.
|
|
<a name="l15"></a>
|
|
<a name="l16"></a>You can be a good toy or you can be a good professional tool, but not both. ZealOS's file manager will start too slowly once
|
|
<a name="l17"></a>a few thousand files exist because the file manager makes a list of all files on start-up.
|
|
<a name="l18"></a>
|
|
<a name="l19"></a>Do not have more than a few thousand files or the file manager will not function.
|
|
<a name="l20"></a>
|
|
<a name="l21"></a>You are encouraged to keep your entire drive limited to, maybe, 100 Meg of files because you are suppoosed to operate as a
|
|
<a name="l22"></a>kayak instead of a Titanic. If you do this, backing-up will be only a minute or so and you should do it at least once a day.
|
|
<a name="l23"></a>
|
|
<a name="l24"></a>Third party software should be run from ISO files or CD/DVDs directly, without installing to hard drive.
|
|
<a name="l25"></a>
|
|
<a name="l26"></a>Multimedia graphics and sound is, basically, forbidden. If you ignore this, all hell will break loose because memory will
|
|
<a name="l27"></a>fragment with large files and the original vision of kayak hard-drive back-ups won't work.
|
|
<a name="l28"></a>
|
|
<a name="l29"></a></span><span class=cF8>
|
|
<a name="l30"></a>* "Commodore 64" is a trademark owned by Polabe Holding NV.
|
|
</span></pre></body>
|
|
</html>
|