dragora-handbook-content.texi 9.2 KB

  1. @c -*-texinfo-*-
  2. @c dragora-handbook-content.texi
  3. @c This is part of the Dragora Handbook.
  4. @c Copyright (C) 2020-2024 The Dragora Team.
  5. @c See the file dragora-handbook-header.texi for copying conditions.
  6. @node About this handbook
  7. @chapter About this handbook
  8. @cindex about this handbook
  9. TODO (Add intro + versioning scheme paragraph).
  10. @section Typographic conventions
  11. @cindex typographic conventions
  12. TODO (appendix).
  13. @node Revision history (ChangeLog)
  14. @unnumbered Revision history (ChangeLog)
  15. @cindex revision history (changelog)
  16. TODO (appendix).
  17. @node What is Dragora?
  18. @chapter What is Dragora?
  19. @cindex what is dragora?
  20. @strong{Dragora} is an independent GNU/Linux distribution project which
  21. was created from scratch with the intention of providing a reliable
  22. operating system with maximum respect for the user by including entirely
  23. free software. @strong{Dragora} is based on the concepts of simplicity
  24. and elegance, it offers a user-friendly Unix-like environment with
  25. emphasis on stability and security for long-term durability.
  26. To put it in a nutshell, @strong{Dragora} is...
  27. @itemize @bullet
  28. @item Minimalist.
  29. @item Free as in freedom.
  30. @item Getting better by the day.
  31. @item A whole lot of fun (not suitable for old vinegars).
  32. @end itemize
  33. Some of the features of Dragora are:
  34. @itemize @bullet
  35. @item SysV init as the classic, documented initialization program (PID 1).
  36. @item Perp to reliably start, monitor, log and control "critical" system daemons.
  37. @item Lightweight alternatives to popular free software; i.e, musl libc, libressl,
  38. mksh, scron, pkgconf.
  39. @item The Trinity Desktop Environment (TDE).
  40. @item Window managers such as TWM, DWM.
  41. @item Graft for managing multiple packages under a single directory hierarchy
  42. using symbolic links mechanisms.
  43. @item Qi as a simple local package manager that complements Graft to create,
  44. install, remove and upgrade software packages.
  45. @end itemize
  46. @section Free software
  47. @cindex free software
  48. TODO.
  49. @section GNU
  50. @cindex gnu
  51. TODO.
  52. @section Linux and Linux-libre
  53. @cindex linux or linux-libre
  54. TODO.
  55. @node Why should I use Dragora?
  56. @chapter Why should I use Dragora?
  57. @cindex why should I use dragora?
  58. We cannot and do not intend to decide for you, we can only cite what we
  59. believe to be Dragora's main strengths:
  60. @itemize @bullet
  61. @item @strong{Independent}:
  62. As mentioned before, Dragora is an independent project, this means that it
  63. is based on a voluntary basis where one or more people share the same
  64. direction or intentions for the sake of the project and in benefit of the
  65. free software community. But above all, it is
  66. not a purely commercial project or one that is made by a company, where they
  67. have commercial interests, and where many times they will do anything to
  68. catch you and see your face for their selfish business.
  69. @item @strong{Simple:} The underlying concept of Dragora's design philosophy is
  70. simplicity: KISS, "Keep It Simple, Stupid!". This principle, which derives
  71. from what is known as "Ockham's razor," was developed by the first modern
  72. critical philosopher: William of Ockham. We believe this concept represents
  73. the traditional UNIX philosophy - so we don't add functionality
  74. unnecessarily, nor do we duplicate information.
  75. @item @strong{Ethical:} We try to ensure that the included software is
  76. completely free and allows you to legally run, copy, distribute, study,
  77. change and improve the software.
  78. @item @strong{Language:} Native support.
  79. @item @strong{Community:} Dragora is not a closed project. On the contrary, anyone
  80. person with good intentions is welcome - and encouraged! - to join and help.
  81. @end itemize
  82. @node History
  83. @chapter History
  84. @cindex history
  85. Development of Dragora started in 2007 by Matias Andres Fonzo from
  86. Santiago del Estero, Argentina. After one year of hard work, the first
  87. beta of Dragora was released on June 13, 2008, which contained the basic
  88. GNU toolset, boot scripts, package system, and an installer.
  89. Whereas the intention was to achieve a 100% "free" as in freedom
  90. GNU/Linux distribution from the beginning, this very first version was not
  91. fully free (or libre) since all parts were free software, except for the
  92. Linux Kernel due to blobs or non-free parts. Fortunately, the Linux-Libre
  93. project appears that same year, which removes or cleans the non-free parts
  94. of the official versions of the Linux Kernel. This led to the second beta
  95. of Dragora on September 18, 2008; completing distribution's freedom by
  96. replacing the Kernel, and becoming the first one available to the public.
  97. Ongoing work to provide a more complete distribution would result in the
  98. stable release of Dragora 1.0, achieved on March 13, 2009. The series
  99. ends with the massive update plus fixes and added software for version
  100. 1.1 released on October 8, 2009.
  101. Design of this series was based on a traditional GNU/Linux scheme with
  102. SysVinit as the init system but using BSD-style boot scripts. The package
  103. system, the installer, the text menu-mode tools and the boot scripts were
  104. all written using the syntax and the features offered by GNU Bash.
  105. Initially the binary packages were provided in .tbz2 format (files
  106. compressed with bzip2 and packaged using GNU Tar) which later migrated to
  107. the .tlz format (files compressed with lzip for a higher compression plus
  108. very safe integrity checking). Dragora's installer offered the option of
  109. several languages (translations produced by the community) to choose
  110. between English, Galician, Italian, and Spanish. A second CD included the
  111. packages for the K Desktop Environment (KDE) 3 series.
  112. @section Releases
  113. @cindex releases
  114. Below are the dates and code names used for all the Dragora releases:
  115. @itemize @bullet
  116. @item @emph{@strong{Dragora 1.0 Beta 1:} June 13th, 2008 - "hell".}
  117. @item @emph{@strong{Dragora 1.0 Beta 2:} September 18th, 2008.}
  118. @item @emph{@strong{Dragora 1.0 Release Candidate 1:} February 12th, 2009.}
  119. @item @emph{@strong{Dragora 1.0 Stable:} March 13th, 2009 - "starlight".}
  120. @item @emph{@strong{Dragora 1.1 Release Candidate 1:} August 25th, 2009.}
  121. @item @emph{@strong{Dragora 1.1 Stable:} October 8th, 2009 - "stargazer".}
  122. @item @emph{@strong{Dragora 2.0 Release Candidate 1:} January 24th, 2010.}
  123. @item @emph{@strong{Dragora 2.0 Release Candidate 2:} March 28th, 2010.}
  124. @item @emph{@strong{Dragora 2.0 Stable:} April 13th, 2010 - "ardi".}
  125. @item @emph{@strong{Dragora 2.1 Release Candidate 1:} December 4th, 2010.}
  126. @item @emph{@strong{Dragora 2.1 Stable:} December 31st, 2010 - "dio".}
  127. @item @emph{@strong{Dragora 2.2 Release Candidate 1:} March 2nd, 2012.}
  128. @item @emph{@strong{Dragora 2.2 Stable:} April 21st, 2012 - "rafaela".}
  129. @item @emph{@strong{Dragora 3.0 Alpha 1:} December 31st, 2017.}
  130. @item @emph{@strong{Dragora 3.0 Alpha 2:} September 28th, 2018.}
  131. @item @emph{@strong{Dragora 3.0 Beta 1:} October 16th, 2019.}
  132. @item @emph{@strong{Dragora 3.0 Beta 2:} April 26th, 2023.}
  133. @end itemize
  134. @node Maintainers
  135. @chapter Maintainers
  136. @cindex maintainers
  137. TODO.
  138. @node A quick glance at Dragora
  139. @chapter A quick glance at Dragora
  140. @cindex a quick glance at dragora
  141. TODO.
  142. @node Boot options from live medium
  143. @chapter Boot options from live medium
  144. @cindex boot options from live medium
  145. TODO.
  146. @node Using dragora-installer
  147. @chapter Using dragora-installer
  148. @cindex using dragora-installer
  149. TODO.
  150. @node Installing the system manually (as an alternative)
  151. @chapter Installing the system manually (as an alternative)
  152. @cindex installing the system manually (as an alternative)
  153. TODO.
  154. @node Introduction to package management in Dragora
  155. @chapter Introduction to package management in Dragora
  156. @cindex package management in dragora
  157. TODO.
  158. @node Package management in a nutshell
  159. @chapter Package management in a nutshell
  160. @cindex package management in a nutshell
  161. TODO.
  162. @node Using third-party free software
  163. @unnumbered Using third-party free software
  164. @cindex using third-party free software
  165. TODO (appendix).
  166. @include qi-content.texi
  167. @node Getting support
  168. @chapter Getting support
  169. @cindex getting support
  170. Dragora's home page can be found at @uref{https://www.dragora.org}.
  171. @tie{}Bug reports or suggestions can be sent to @email{dragora-users@@nongnu.org}.
  172. @node Contributing to Dragora
  173. @chapter Contributing to Dragora
  174. @cindex contributing to dragora
  175. TODO (introductory text here).
  176. @section How to place a mirror
  177. @cindex how to place a mirror
  178. If there's no Dragora mirror near you, you're welcome to contribute one.
  179. First, for users or downloaders, the address @emph{rsync://rsync.dragora.org/}
  180. contains ISO images and source code (in various formats) taken from the
  181. original sites and distributed by Dragora.
  182. Mirroring the Dragora server requires approximately 13GB of disk space (as
  183. of January 2022). You can hit rsync directly from @emph{rsync.dragora.org} as:
  184. @code{rsync -rltpHS --delete-excluded rsync://rsync.dragora.org/dragora /your/dir/}
  185. Also, consider mirroring from another site in order to reduce load on the
  186. Dragora server. The listed sites at
  187. @url{https://www.dragora.org/en/get/mirrors/index.html} provide access to all
  188. the material on rsync.dragora.org. They update from us nightly (at least),
  189. and you may access them via rsync with the same options as above.
  190. Note:
  191. We keep a file called "timestamp" under the main tree after each
  192. synchronization. This file can be used to verify, instead of synchronizing
  193. all the content at once, you can check if this file has been updated and
  194. then continue with the full synchronization.