index.html

   1 <!DOCTYPE html>
   2 <html lang="en">
   3 <head>
   4 <meta charset="utf-8">
   5 <meta name="viewport" content="width=device-width, initial-scale=1">
   6 <meta http-equiv="X-UA-Compatible" content="IE=edge">
   7 <link rel="stylesheet" media="all" href="main.css">
   8 <title>The Unleashed Operating System</title>
   9 </head>
  10 <body>
  11 <p class="title">
  12 The Unleashed Operating System
  13 </p>
  14 <p>
  15 Unleashed is an operating system fork of
  16 <a href="https://illumos.org/">illumos</a>, which itself is a derivative of
  17 OpenSolaris and therefore has its roots in UNIX System V Release 4.
  18 </p>
  19 <p>
  20 It is intended as an operating system for <em>developers by developers</em>.
  21 </p>
  22 <p>
  23 Unleashed is a fork of illumos; it comes with ZFS, DTrace, Crossbow and more.
  24 </p>
  25 <h1>Goals</h1>
  26 <p>
  27 We try to make Unleashed an operating system that <em>we would like to use</em>.
  28 </p>
  29 <p>
  30 Our most important goals are:
  31 </p>
  32 <ol>
  33   <li>The contribution process must be simple and must encourage new
  34   contributors to repeatedly contribute.</li>
  35   <li>We aim to have periodic releases (roughly one every 6 months).  Security
  36   patches will be provided between releases.</li>
  37   <li>Unleashed aims to be a modern operating system base.
  38     <ol>
  39       <li>Modern compiler support.  Currently, the base system can only be
  40       built with gcc 4.4.4, however we hope to allow a wider range of gcc
  41       versions.  Eventually, we would like to be able to use clang as
  42       well.</li>
  43       <li>The UNIX environment has changed drastically over the past 20
  44       years.  As a result, we hope to ship an environment that provides the
  45       comforts of modern UNIX, yet maintains the unique features we
  46       inherited that set us apart from other UNIX systems out there.</li>
  47       <li>POSIX has won.  Therefore, when it does not hinder usability (see
  48       item 3.2), we want a system that is POSIX-compliant without having to
  49       jump through special hoops (e.g., setting $PATH, or providing extra
  50       compiler flags).</li>
  51       <li>We do <em>not</em> support &ldquo;extreme legacy&rdquo;.  While
  52       support for legacy interfaces and binaries is important, it must be
  53       done in moderation.  Therefore, old interfaces may be removed from
  54       time to time.  Interface deprecation will be clearly communicated
  55       through release notes.</li>
  56     </ol>
  57   </li>
  58   <li>Maintaining code is hard enough when the code is squeaky clean.  To make
  59    our job easier, we try to get the code clean when first committing it
  60    &mdash; even if it delays the commit a little bit.  In other words, we
  61    care about more than just that the code works &mdash; we want code we can
  62    (for the most part) be proud of.</li>
  63 </ol>
  64 <h1>Download &amp; Installation</h1>
  65 <p>
  66 The only systems currently supported are amd64-based computers and virtual
  67 machines.
  68 </p>
  69 <p>
  70 Please note that <strong>Unleashed is currently not ready for use in a
  71 production environment</strong>.
  72 While we do try to keep up with patches for security vulnerabilities, we do
  73 not have enough resources to make any guarantees.
  74 </p>
  75 <p>
  76 If you wish to build the current master, use the latest available
  77 development snapshot.
  78 </p>
  79 <table>
  80   <tr>
  81     <td>release:</td>
  82     <td><a href="/releases/1.2/">1.2</a></td><td>2018-12-27</td>
  83     <td>[<a href="/releases/1.2/notes.txt">relnotes</a>]</td>
  84     <td>[<a href="/releases/1.2/unleashed-1.2.img.gz">usb</a>]</td>
  85     <td>[<a href="/releases/1.2/unleashed-1.2.iso.gz">iso</a>]</td>
  86     <td>[<a href="/releases/1.2/unleashed-1.2.p5p.gz">p5p</a>]</td>
  87     <td>[<a href="/releases/1.2/checksums">checksums</a>]</td>
  88   </tr>
  89   <tr>
  90     <td>dev snapshot:</td>
  91     <td><a href="/snapshots/latest/">latest</a></td><td>various</td>
  92     <td>&nbsp;</td>
  93     <td>[<a href="/snapshots/latest/snapshot.img.gz">usb</a>]</td>
  94     <td>[<a href="/snapshots/latest/snapshot.iso.gz">iso</a>]</td>
  95     <td>[<a href="/snapshots/latest/snapshot.p5p.gz">p5p</a>]</td>
  96     <td>[<a href="/snapshots/latest/checksums">checksums</a>]</td>
  97   </tr>
  98   <tr>
  99     <td>previous release:</td>
 100     <td><a href="/releases/1.1/">1.1</a></td><td>2018-09-28</td>
 101     <td>[<a href="/releases/1.1/notes.txt">relnotes</a>]</td>
 102     <td>[<a href="/releases/1.1/unleashed-1.1.img.gz">usb</a>]</td>
 103     <td>[<a href="/releases/1.1/unleashed-1.1.iso.gz">iso</a>]</td>
 104     <td>[<a href="/releases/1.1/unleashed-1.1.p5p.gz">p5p</a>]</td>
 105     <td>[<a href="/releases/1.1/checksums">checksums</a>]</td>
 106   </tr>
 107 </table>
 108 <h1>IRC &amp; Mailing Lists</h1>
 109 <p>
 110 You can find us in
 111 <a href="ircs://irc.freenode.net:6697/unleashed">#unleashed on Freenode</a>.
 112 </p>
 113 <p>
 114 We have two mailing lists: one for general development discussions
 115 (<a href="http://lists.31bits.net/listinfo/devel">subscribe</a>,
 116 <a href="http://lists.31bits.net/archives/devel/">archives</a>)
 117 and one with commit notifications
 118 (<a href="http://lists.31bits.net/listinfo/commits">subscribe</a>,
 119 <a href="http://lists.31bits.net/archives/commits/">archives</a>).
 120 </p>
 121 <p>
 122 Security sensitive information can be sent to
 123 <a href="mailto:jeffpc@josefsipek.net">jeffpc@josefsipek.net</a>.  If you
 124 wish, you may encrypt your message with PGP
 125 (key ID
 126 <a href="https://sks-keyservers.net/pks/lookup?op=get&search=0x18F90BEB645EB36FE31AEE9F8311B7D703B1E6C8">0x18F90BEB645EB36FE31AEE9F8311B7D703B1E6C8</a>).
 127 </p>
 128 <h1>Contributing</h1>
 129 <p>
 130 We try to make contributing to Unleashed a straightforward affair.
 131 If you have a project in mind or are looking for some suggestions,
 132 contact us on IRC or on the mailing list.
 133 (A good way to come up with a project is to install and use Unleashed.
 134 Anything broken or annoying that you find is a possible project!)
 135 </p>
 136 <p>
 137 The source code itself is split across several git repositories:
 138 </p>
 139 <ul>
 140   <li><a href="http://repo.or.cz/unleashed.git/">core OS</a></li>
 141   <li><a href="http://repo.or.cz/unleashed-userland.git/">userland</a></li>
 142   <li><a href="http://repo.or.cz/unleashed-pkg5.git/">pkg5</a></li>
 143   <li><a href="http://repo.or.cz/unleashed-kayak.git/">kayak installer</a></li>
 144 </ul>
 145 <p>
 146 The steps to build each vary, but they are documented in each repository's
 147 top-level README.
 148 </p>
 149 <h1>Documentation</h1>
 150 <p>
 151 Aside from the typical set of man pages, there is a
 152 <a href="http://repo.or.cz/unleashed.git/tree/HEAD:/docs">docs</a> directory
 153 in the main git repository.
 154 </p>
 155 </body>
 156 </html>
 157