[Debian-NP-Commits] r196 - trunk/docs/report/report-docbook
micah
debian-np-devel@lists.alioth.debian.org
Fri, 08 Oct 2004 16:06:40 -0600
Author: micah-guest
Date: Fri Oct 8 16:06:39 2004
New Revision: 196
Modified:
trunk/docs/report/report-docbook/appendix-cdd.xml
trunk/docs/report/report-docbook/appendix-development_environment.xml
trunk/docs/report/report-docbook/appendix-installer.xml
trunk/docs/report/report-docbook/intro.xml
trunk/docs/report/report-docbook/report-master.xml
Log:
Fixed the validation issues, re-ordered authors to be alphabetical
Modified: trunk/docs/report/report-docbook/appendix-cdd.xml
==============================================================================
--- trunk/docs/report/report-docbook/appendix-cdd.xml (original)
+++ trunk/docs/report/report-docbook/appendix-cdd.xml Fri Oct 8 16:06:39 2004
@@ -1,5 +1,6 @@
+<sect1>
<title>Appendix C: Customized Debian Distributions (CDD)</title>
- <sect1>
+ <sect2>
<title>Introduction</title>
<para>The CDD (Custom Debian Distribution) project was born a few
@@ -41,9 +42,9 @@
particular groups, but they also ease installation and
configuration for the intended purpose.</para>
- </sect1>
+ </sect2>
- <sect1>
+ <sect2>
<title>CDD infrastructure</title>
<para> Creating a CDD means fundamentally to solve the following
@@ -88,29 +89,29 @@
customization methodology. It has been difficult to define what
the common customization needs are.</para>
- <sect2>
+ <sect3>
<title>CDD-dev</title>
<para>Before Debian-NP went to Porto Alegre, the CDD project had
already created two Debian packages that contain some tools to
help in the customization work. These packages are cdd-common
and cdd-dev. </para>
- </sect2>
+ </sect3>
- <sect2>
+ <sect3>
<title>CDD-common</title>
<para>The "cdd-common" package provides a number of scripts that
help in the configuration of users and groups, insert those
users and groups in the LDAP environment, create the mailserver
configuration and so on. </para>
- </sect2>
+ </sect3>
- </sect1>
+ </sect2>
- <sect1>
+ <sect2>
<title>DebianNP's CDD enhancements</title>
- <sect2>
+ <sect3>
<title>Goals</title>
<para>During Debconf, Debian-NP designed an enhanced CDD
@@ -138,12 +139,12 @@
</listitem>
</itemizedlist>
- </sect2>
+ </sect3>
- <sect2>
+ <sect3>
<title>Process for accomplishing this methodology</title>
- <sect3>
+ <sect4>
<title>Contribute to the community</title>
<para>First of all the CDD scripts, packages, configurations,
@@ -152,9 +153,9 @@
Community by contributing back work that can be shared by
other users, developers, CDDs etc.</para>
- </sect3>
+ </sect4>
- <sect3>
+ <sect4>
<title>Meta-packages</title>
<para>Next, each CDD should be organized into
@@ -210,9 +211,9 @@
existing installed Debian machine, or are integrated together
in the full Debian-NP server installation from a CD.</para>
- </sect3>
+ </sect4>
- <sect3>
+ <sect4>
<title>Common interface</title>
<para>We came up with the method of creating the package named
@@ -230,9 +231,9 @@
should be able to update the menu interface when new
meta-packages are installed/removed from the system.</para>
- </sect3>
+ </sect4>
- <sect3>
+ <sect4>
<title>Configuration</title>
<para>Each CDD will require certain configuration and
@@ -246,10 +247,10 @@
use either debconf, cfengine, hand-written scripts or use
configuration files that do diversions.</para>
- </sect3>
- </sect2>
- </sect1>
-
+ </sect4>
+ </sect3>
+ </sect2>
+</sect1>
<!-- Keep this comment at the end of the file
Modified: trunk/docs/report/report-docbook/appendix-development_environment.xml
==============================================================================
--- trunk/docs/report/report-docbook/appendix-development_environment.xml (original)
+++ trunk/docs/report/report-docbook/appendix-development_environment.xml Fri Oct 8 16:06:39 2004
@@ -1,277 +1,278 @@
- <title>Appendix B: Development Environment</title>
- <sect1>
- <title>Subversion repository</title>
-
- <sect2>
- <title>Overview</title>
-
- <para>Subversion is a version control system. Version control is a
- method to manage changes to information, it is a critical tool for
- programmers who make many small changes to software in a
- collaborative environment and require the ability to record why
- they made a particular change, and return to a previous version if
- necessary.</para>
-
-
- <para>Subversion is a free software version control system that
- aids developers in managing files, directories, source code,
- documents, etc. over time. Files are created in a repository which
- remembers every change ever made to any file or directory within
- the repository, allowing you to recover older versions of your
- data, examine the history of how your data changed, or undo
- incorrect changes.</para>
-
- <para>An additional benefit to using a version control system like
- Subversion is that the repository is accessible over a network,
- and is shared by developers. This allows for individual developers
- to make changes to the same files from different locations,
- fostering remote collaboration. Development progress can occur
- quickly when each developer can work on the same files at the same
- time, without the overhead of worrying about what another might be
- doing to the same file, differences can be merged and conflicts
- can be reconciled with ease.</para>
-
- <para>Debian-NP created a Subversion repository at Debconf4,
- learned how to use it and rapidly began populating it with our
- work, and organizing its layout. Over the course of less than a
- week, there were nearly 400 commitments made to the subversion
- repository with code-fragments, documentation, meta-package work,
- installer work, and organization of the repository. We left the
- conference with a method of continuing our collaborative in-person
- work through using Subversion, and an impressive feeling of
- initiative manifested in the repository's contents which we took
- home and continue to work with.</para>
-
- </sect2>
-
+<sect1>
+ <title>Appendix B: Development Environment</title>
<sect2>
- <title>Usage</title>
-
+ <title>Subversion repository</title>
+
<sect3>
- <title>Alioth</title>
-
- <para>The Debian-NP Subversion repository requires that you have
- an account on Alioth. Alioth is a free service to Debian project
- developers offering easy access to the best in version control,
- mailing lists, bug tracking, message boards/forums, task
- management, site hosting, permanent file archival, full backups,
- and total web-based administration. It is not necessary to be an
- official Debian Developer to create an account on Alioth, each
- person who came to Debconf4 to work on Debian-NP created their
- Alioth account and were added to the Debian-NP project.</para>
-
- <para>To create an Alioth account, visit <ulink
- url="http://alioth.debian.org/account/register.php">Alioth.</ulink>
- </para>
+ <title>Overview</title>
- </sect3>
+ <para>Subversion is a version control system. Version control is a
+ method to manage changes to information, it is a critical tool for
+ programmers who make many small changes to software in a
+ collaborative environment and require the ability to record why
+ they made a particular change, and return to a previous version if
+ necessary.</para>
+
+
+ <para>Subversion is a free software version control system that
+ aids developers in managing files, directories, source code,
+ documents, etc. over time. Files are created in a repository which
+ remembers every change ever made to any file or directory within
+ the repository, allowing you to recover older versions of your
+ data, examine the history of how your data changed, or undo
+ incorrect changes.</para>
+
+ <para>An additional benefit to using a version control system like
+ Subversion is that the repository is accessible over a network,
+ and is shared by developers. This allows for individual developers
+ to make changes to the same files from different locations,
+ fostering remote collaboration. Development progress can occur
+ quickly when each developer can work on the same files at the same
+ time, without the overhead of worrying about what another might be
+ doing to the same file, differences can be merged and conflicts
+ can be reconciled with ease.</para>
+
+ <para>Debian-NP created a Subversion repository at Debconf4,
+ learned how to use it and rapidly began populating it with our
+ work, and organizing its layout. Over the course of less than a
+ week, there were nearly 400 commitments made to the subversion
+ repository with code-fragments, documentation, meta-package work,
+ installer work, and organization of the repository. We left the
+ conference with a method of continuing our collaborative in-person
+ work through using Subversion, and an impressive feeling of
+ initiative manifested in the repository's contents which we took
+ home and continue to work with.</para>
- <sect3>
- <title>Subversion client</title>
-
- <para>You also need to have the Subversion client program
- installed on your machine to be able to check out the Debian-NP
- Subversion repository. Once you have Subversion installed, you
- can check out the repository by issuing the following
- command:</para>
</sect3>
<sect3>
- <title>Subversion repository checkout</title>
+ <title>Usage</title>
+
+ <sect4>
+ <title>Alioth</title>
- <para> <command>svn checkout svn+ssh://<username>@debian np.alioth.debian.org/svn/debian-np bagunca </command></para>
- </sect3>
+ <para>The Debian-NP Subversion repository requires that you have
+ an account on Alioth. Alioth is a free service to Debian project
+ developers offering easy access to the best in version control,
+ mailing lists, bug tracking, message boards/forums, task
+ management, site hosting, permanent file archival, full backups,
+ and total web-based administration. It is not necessary to be an
+ official Debian Developer to create an account on Alioth, each
+ person who came to Debconf4 to work on Debian-NP created their
+ Alioth account and were added to the Debian-NP project.</para>
+
+ <para>To create an Alioth account, visit <ulink
+ url="http://alioth.debian.org/account/register.php">Alioth.</ulink>
+ </para>
- </sect2>
+ </sect4>
- <sect2>
- <title>Layout</title>
-
- <para>The Subversion repository was organized to a common work
- area, structured around common development standards as well as
- around what we are trying to accomplish, the agreed upon framework
- that was put together is as follows:</para>
-
- <itemizedlist>
- <listitem>
- <para><filename>branches/</filename></para>
- <para>This is where concurrent development/stabilization
- happens.</para>
- </listitem>
-
- <listitem>
- <para><filename>people/</filename></para>
- <para>Contains individual users working directories</para>
- </listitem>
-
- <listitem>
- <para><filename>tags/</filename></para>
- <para>This is where static copies of package versions and other
- modules are stored.</para>
- </listitem>
-
- <listitem>
- <para><filename>trunk/</filename></para>
- <para>This is used for mainline development.</para>
- </listitem>
-
- </itemizedlist>
-
- <para>Inside <filename>trunk/</filename> are the following
- directories:</para>
-
- <itemizedlist>
- <listitem>
- <para><filename>docs/</filename></para>
- <para>Contains common documentation, HOWTOs, etc.</para>
- </listitem>
-
- <listitem>
- <para><filename>packages/</filename></para>
- <para>Storage of source packages that will need to be uploaded to
- Debian.</para>
- </listitem>
+ <sect4>
+ <title>Subversion client</title>
- </itemizedlist>
-
- <para>Inside the <filename>packages/</filename> hierarchy is located the
- individual components of DebianNP:</para>
+ <para>You also need to have the Subversion client program
+ installed on your machine to be able to check out the Debian-NP
+ Subversion repository. Once you have Subversion installed, you
+ can check out the repository by issuing the following
+ command:</para>
+ </sect4>
- <itemizedlist>
- <listitem>
- <para><filename>debian-np/</filename></para>
- <para>This directory contains the source code and definitions of
- the meta-packages</para>
- </listitem>
-
- <listitem>
- <para><filename>debian-np-cdtools/</filename></para>
- <para>This directory contains the scripts used to build the ISO
- image and mirror.</para>
- </listitem>
-
- <listitem>
- <para><filename>debian-np-install/</filename></para>
- <para>This is where the Debian-NP installer, and customization of
- the Skolelinux installer work is done</para>
- </listitem>
+ <sect4>
+ <title>Subversion repository checkout</title>
- </itemizedlist>
+ <para> <command>svn checkout svn+ssh://<username>@debian np.alioth.debian.org/svn/debian-np bagunca </command></para>
+ </sect4>
- </sect2>
+ </sect3>
- </sect1>
+ <sect3>
+ <title>Layout</title>
-<sect1>
- <title>Communication</title>
- <para></para>
+ <para>The Subversion repository was organized to a common work
+ area, structured around common development standards as well as
+ around what we are trying to accomplish, the agreed upon framework
+ that was put together is as follows:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><filename>branches/</filename></para>
+ <para>This is where concurrent development/stabilization
+ happens.</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>people/</filename></para>
+ <para>Contains individual users working directories</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>tags/</filename></para>
+ <para>This is where static copies of package versions and other
+ modules are stored.</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>trunk/</filename></para>
+ <para>This is used for mainline development.</para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>Inside <filename>trunk/</filename> are the following
+ directories:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><filename>docs/</filename></para>
+ <para>Contains common documentation, HOWTOs, etc.</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>packages/</filename></para>
+ <para>Storage of source packages that will need to be uploaded to
+ Debian.</para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>Inside the <filename>packages/</filename> hierarchy is located the
+ individual components of DebianNP:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><filename>debian-np/</filename></para>
+ <para>This directory contains the source code and definitions of
+ the meta-packages</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>debian-np-cdtools/</filename></para>
+ <para>This directory contains the scripts used to build the ISO
+ image and mirror.</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>debian-np-install/</filename></para>
+ <para>This is where the Debian-NP installer, and customization of
+ the Skolelinux installer work is done</para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect3>
- <sect2>
- <title>Mailing lists</title>
- <itemizedlist>
-
- <listitem>
- <para>
- General list: <email>debian-np@lists.debian.org</email>
- </para>
- </listitem>
-
- <listitem>
- <para>
- Devel list: <email>debian-np-devel@lists.alioth.debian.org</email>
- </para>
- </listitem>
-
- <listitem>
- <para>
- SVN commits: <email>debian-np-commits@lists.alioth.debian.org</email>
- </para>
- </listitem>
+ </sect2>
- </itemizedlist>
+ <sect2>
+ <title>Communication</title>
+ <para></para>
- </sect2>
+ <sect3>
+ <title>Mailing lists</title>
+ <itemizedlist>
-<sect2>
- <title>IRC Channel</title>
- <itemizedlist>
-
- <listitem>
- <para>
- <command>#debian-np</command> (irc.debian.net) - Main debian-NP channel
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>#debian-custom</command> (irc.debian.net) - CDD channel
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>CIA-#:</command> IRC bot announcing subversion commits
- to the #debian-np channel
- </para>
- </listitem>
+ <listitem>
+ <para>
+ General list: <email>debian-np@lists.debian.org</email>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Devel list: <email>debian-np-devel@lists.alioth.debian.org</email>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ SVN commits: <email>debian-np-commits@lists.alioth.debian.org</email>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect3>
- </itemizedlist>
- </sect2>
-
- <sect2>
- <title>Websites</title>
- <itemizedlist>
+ <sect3>
+ <title>IRC Channel</title>
+ <itemizedlist>
- <listitem>
- <para>
- <ulink
- url="http://www.debian.org/devel/debian-nonprofit">Homepage</ulink>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <ulink url="http://debian-np.alioth.debian.org/">Alioth</ulink>
- development area
- </para>
- </listitem>
-
- <listitem>
- <para>
- <ulink
- url="http://wiki.debian.net/index.cgi?DebianNonProfit">Wiki</ulink>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <ulink
- url="http://cia.navi.cx/stats/project/debian-nonprofit">Project
- Tracker</ulink>
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <command>#debian-np</command> (irc.debian.net) - Main debian-NP channel
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>#debian-custom</command> (irc.debian.net) - CDD channel
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>CIA-#:</command> IRC bot announcing subversion commits
+ to the #debian-np channel
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </sect3>
+
+ <sect3>
+ <title>Websites</title>
+ <itemizedlist>
- </itemizedlist>
+ <listitem>
+ <para>
+ <ulink
+ url="http://www.debian.org/devel/debian-nonprofit">Homepage</ulink>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <ulink url="http://debian-np.alioth.debian.org/">Alioth</ulink>
+ development area
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <ulink
+ url="http://wiki.debian.net/index.cgi?DebianNonProfit">Wiki</ulink>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <ulink
+ url="http://cia.navi.cx/stats/project/debian-nonprofit">Project
+ Tracker</ulink>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect3>
- </sect2>
+ <sect3>
+ <title>Project tracking</title> <para>We are using a system called
+ CIA for tracking our project in real-time. This project tracking
+ system provides us with an easy way for people to observe the flow
+ and keep updated on the different elements of how a project
+ progresses. Developers can see the latest changes to their code
+ immediately, users can subscribe to see the latest bugfixes and
+ updates. The system provides a mechanism to look at the development
+ of the project as a whole. It provides a online statistics browser
+ and XML/RSS syndicated feeds of project updates, as well as the IRC
+ bot to communicate to our channel new developments.</para>
+ </sect3>
- <sect2>
- <title>Project tracking</title> <para>We are using a system called
- CIA for tracking our project in real-time. This project tracking
- system provides us with an easy way for people to observe the flow
- and keep updated on the different elements of how a project
- progresses. Developers can see the latest changes to their code
- immediately, users can subscribe to see the latest bugfixes and
- updates. The system provides a mechanism to look at the development
- of the project as a whole. It provides a online statistics browser
- and XML/RSS syndicated feeds of project updates, as well as the IRC
- bot to communicate to our channel new developments.</para>
</sect2>
-
</sect1>
-
<!-- Keep this comment at the end of the file
Local variables:
mode: xml
Modified: trunk/docs/report/report-docbook/appendix-installer.xml
==============================================================================
--- trunk/docs/report/report-docbook/appendix-installer.xml (original)
+++ trunk/docs/report/report-docbook/appendix-installer.xml Fri Oct 8 16:06:39 2004
@@ -1,150 +1,151 @@
+<sect1>
<title>Appendix D: Debian-NP Installer</title>
- <sect1>
+ <sect2>
<title>Overview</title>
-
- <para>During Debconf Debian-NP made strong progress towards an
- Installer, both the technical framework was worked on, the tools
- to create the installer and ISO, and an actual installable version
- of Debian-NP was created.</para>
-
- <para>The installer is derived from the latest development version
- of the Debian Installer. As such, it has all the characteristics
- of the Debian Installer: it can be run from a CD, it can be
- installed over the Network, from floppies, and so on. It is also
- localized into many different languages (the number and status of
- these translations are available at the <ulink
+
+ <para>During Debconf Debian-NP made strong progress towards an
+ Installer, both the technical framework was worked on, the tools
+ to create the installer and ISO, and an actual installable version
+ of Debian-NP was created.</para>
+
+ <para>The installer is derived from the latest development version
+ of the Debian Installer. As such, it has all the characteristics
+ of the Debian Installer: it can be run from a CD, it can be
+ installed over the Network, from floppies, and so on. It is also
+ localized into many different languages (the number and status of
+ these translations are available at the <ulink
url="http://people.debian.org/~seppy/d-i/translation-status.html">Debian
Installer translations</ulink> page).</para>
-
- <para>During Debconf, we studied how the Debian Installer could be
- customized for our purposes, learning from the customization work
- that has been done to the Debian Installer for other Customized
- Debian Distributions, namely Skolelinux and Debian-BR.</para>
- </sect1>
-
- <sect1>
- <title>Accomplishments</title>
-
- <para>By the end of Debconf, Debian-NP had created an installer
- out of the Debian-Installer, using the Skolelinux framework and
- the proximity of Skolelinux developers, Debian Installer
- developers, and Debian-BR developers to overcome technical hurdles
- quickly.</para>
-
- <para>The Debian-NP installer created at Debconf allows the
- following to occur:</para>
-
- <itemizedlist>
-
- <listitem>
- <para>Choose a profile (Server or Workstation).</para>
- </listitem>
-
- <listitem>
- <para>Install the system (with auto-partitioning) based on the
- profile chosen.</para>
- </listitem>
-
- </itemizedlist>
-
- <para>We decided to base the Debian-NP installer on two profiles:
- Server and WorkStation after the definition of our social
- specifications, we expect to also be creating a LAN server and
- diskless terminal profile in the near future.</para>
-
- <para>The accomplish this work on the installer we needed about
- one week of work, because of a lack of documentation on Debian
- Installer, bugs, and the test installation cycle is long, it takes
- about 20 minutes to build an ISO image, and about 30 minutes to
- complete the installation.</para>
-
- </sect1>
-
- <sect1>
- <title>Technical Overview</title>
-
-
- <para>To accomplish the creation of the Debian-NP installer, we
- had to create 'udeb' packages which modify the installer
- behavior. Debian-installer has 2 stages. In the 1st stage the
- installer does some basic initialization (partitioning, copying
- the debian-base system, install boot-loader and so on.). The
- program that handles the first stage can be modified adding some
- udeb packages. udeb packages are minimal Debian packages that
- contain mainly scripts to be run in the 1st stage installer. udebs
- specify also the order of execution. Through this method we were
- able to modify the Debian Installer to how we needed. </para>
-
- <para>We created the following udeb packages:</para>
+
+ <para>During Debconf, we studied how the Debian Installer could be
+ customized for our purposes, learning from the customization work
+ that has been done to the Debian Installer for other Customized
+ Debian Distributions, namely Skolelinux and Debian-BR.</para>
+ </sect2>
+
+ <sect2>
+ <title>Accomplishments</title>
+
+ <para>By the end of Debconf, Debian-NP had created an installer
+ out of the Debian-Installer, using the Skolelinux framework and
+ the proximity of Skolelinux developers, Debian Installer
+ developers, and Debian-BR developers to overcome technical hurdles
+ quickly.</para>
+
+ <para>The Debian-NP installer created at Debconf allows the
+ following to occur:</para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>Choose a profile (Server or Workstation).</para>
+ </listitem>
+
+ <listitem>
+ <para>Install the system (with auto-partitioning) based on the
+ profile chosen.</para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>We decided to base the Debian-NP installer on two profiles:
+ Server and WorkStation after the definition of our social
+ specifications, we expect to also be creating a LAN server and
+ diskless terminal profile in the near future.</para>
+
+ <para>The accomplish this work on the installer we needed about
+ one week of work, because of a lack of documentation on Debian
+ Installer, bugs, and the test installation cycle is long, it takes
+ about 20 minutes to build an ISO image, and about 30 minutes to
+ complete the installation.</para>
+
+ </sect2>
+
+ <sect2>
+ <title>Technical Overview</title>
+
+
+ <para>To accomplish the creation of the Debian-NP installer, we
+ had to create 'udeb' packages which modify the installer
+ behavior. Debian-installer has 2 stages. In the 1st stage the
+ installer does some basic initialization (partitioning, copying
+ the debian-base system, install boot-loader and so on.). The
+ program that handles the first stage can be modified adding some
+ udeb packages. udeb packages are minimal Debian packages that
+ contain mainly scripts to be run in the 1st stage installer. udebs
+ specify also the order of execution. Through this method we were
+ able to modify the Debian Installer to how we needed. </para>
+
+ <para>We created the following udeb packages:</para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para><filename>debian-np-profile</filename> - this asks for
+ which kind of installation must be performed and sets the
+ answer in /etc/debian-np/profile </para>
+ </listitem>
+
+ <listitem>
+ <para><filename>debian-np-install</filename> - this makes the
+ main modifications. It installs two partition table
+ definitions (one for the server and the other one for
+ workstation) for automatic partitioning, it also overrides
+ some Debian defaults (this is needed to replace exim with
+ postfix for example), insert some scripts for network
+ configuration, and accomplishes other minor things.</para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>In the 2nd stage, The Debian Installer runs the base-config
+ program. The base-config installs all the meta-packages and
+ configures them. It is at this point where we will need to insert
+ the configuration interface mentioned above. For the moment it
+ simply installs the np-mail-server meta-package package (or
+ np-workstation, depending on the choice on installation) and
+ configures them.</para>
+
+ <sect3>
+ <title>Building the ISO image</title>
+
+ <para>In order to create an installable DebianNP, we needed to
+ be able to build bootable ISOs. An ISO is a CD image that is
+ burned to an actual CD that then can be booted from and
+ installation can proceed. </para>
+
+ <para>The work that was accomplished was was based mainly on the
+ debian-br-cdd-cdtools package, developed by Otavio Salvador and
+ Debian-BR group. With this tool that we have adapted and called
+ debian-np-cdtools, we are able to generate a working ISO image,
+ providing the following information:</para>
+
+ <itemizedlist>
- <itemizedlist>
-
- <listitem>
- <para><filename>debian-np-profile</filename> - this asks for
- which kind of installation must be performed and sets the
- answer in /etc/debian-np/profile </para>
- </listitem>
-
- <listitem>
- <para><filename>debian-np-install</filename> - this makes the
- main modifications. It installs two partition table
- definitions (one for the server and the other one for
- workstation) for automatic partitioning, it also overrides
- some Debian defaults (this is needed to replace exim with
- postfix for example), insert some scripts for network
- configuration, and accomplishes other minor things.</para>
- </listitem>
-
- </itemizedlist>
-
- <para>In the 2nd stage, The Debian Installer runs the base-config
- program. The base-config installs all the meta-packages and
- configures them. It is at this point where we will need to insert
- the configuration interface mentioned above. For the moment it
- simply installs the np-mail-server meta-package package (or
- np-workstation, depending on the choice on installation) and
- configures them.</para>
-
- <sect2>
- <title>Building the ISO image</title>
-
- <para>In order to create an installable DebianNP, we needed to
- be able to build bootable ISOs. An ISO is a CD image that is
- burned to an actual CD that then can be booted from and
- installation can proceed. </para>
-
- <para>The work that was accomplished was was based mainly on the
- debian-br-cdd-cdtools package, developed by Otavio Salvador and
- Debian-BR group. With this tool that we have adapted and called
- debian-np-cdtools, we are able to generate a working ISO image,
- providing the following information:</para>
-
- <itemizedlist>
-
- <listitem>
- <para>a package selection list</para>
- </listitem>
-
- <listitem>
- <para>a base-system package list</para>
- </listitem>
-
- <listitem>
- <para>1st stage udeb list</para>
- </listitem>
-
- </itemizedlist>
-
- <para>During Debconf we also learned about an alternative
- installation ISO creation method, called PICAX developed by
- Progeny. We plan to look into how this methodology could be used
- for DebianNP to facilitate building ISOs in a simpler
- manner.</para>
-
- </sect2>
-
- </sect1>
-
+ <listitem>
+ <para>a package selection list</para>
+ </listitem>
+
+ <listitem>
+ <para>a base-system package list</para>
+ </listitem>
+
+ <listitem>
+ <para>1st stage udeb list</para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>During Debconf we also learned about an alternative
+ installation ISO creation method, called PICAX developed by
+ Progeny. We plan to look into how this methodology could be used
+ for DebianNP to facilitate building ISOs in a simpler
+ manner.</para>
+
+ </sect3>
+
+ </sect2>
+</sect1>
<!-- Keep this comment at the end of the file
Modified: trunk/docs/report/report-docbook/intro.xml
==============================================================================
--- trunk/docs/report/report-docbook/intro.xml (original)
+++ trunk/docs/report/report-docbook/intro.xml Fri Oct 8 16:06:39 2004
@@ -1,11 +1,12 @@
<sect1>
-<para>In its first year, the Debian-NP project has built a unique
+ <title>Introduction</title>
+ <para>In its first year, the Debian-NP project has built a unique
community networking representatives of non-profit organizations
with Free and Open Source software geeks involved and interested in
sering non-profits. While the project coordinated the successful
release of an installable preview CD, it lacked direction, planning,
and the critical mass to accomplish its larger goals.</para>
-
+
<para>The traditional method of overcoming these types of
shortcomings in software projects is funding. However, placed within
the Debian project - a Free Software project famous for its
@@ -13,7 +14,7 @@
hesitant to accept funding in ways that might challenge the
volunteer and institutionally independent nature of the
project.</para>
-
+
<para>Debian-NP participants saw an opportunity for constructive
funding in the 4th annual Debian Conference (DebConf4) and the
International Free Sotware Forum (FISL) held in May 2004 in Porto
Modified: trunk/docs/report/report-docbook/report-master.xml
==============================================================================
--- trunk/docs/report/report-docbook/report-master.xml (original)
+++ trunk/docs/report/report-docbook/report-master.xml Fri Oct 8 16:06:39 2004
@@ -23,14 +23,6 @@
<address>Porto Alegre, Brazil</address>
<date>May 2004</date>
-
- <author>
- <firstname>Benjamin</firstname>
- <othername>Mako</othername>
- <surname>Hill</surname>
- <address><email>mako@debian.org</email></address>
- </author>
-
<author>
<firstname>Micah</firstname>
<surname>Anderson</surname>
@@ -38,9 +30,16 @@
</author>
<author>
- <firstname>Enrico</firstname>
- <surname>Zini</surname>
- <address><email>enrico@debian.org</email></address>
+ <firstname>Vagrant</firstname>
+ <surname>Cascadian</surname>
+ <address><email>vagrant@freegeek.org</email></address>
+ </author>
+
+ <author>
+ <firstname>Benjamin</firstname>
+ <othername>Mako</othername>
+ <surname>Hill</surname>
+ <address><email>mako@debian.org</email></address>
</author>
<author>
@@ -50,9 +49,9 @@
</author>
<author>
- <firstname>Vagrant</firstname>
- <surname>Cascadian</surname>
- <address><email>vagrant@freegeek.org</email></address>
+ <firstname>Enrico</firstname>
+ <surname>Zini</surname>
+ <address><email>enrico@debian.org</email></address>
</author>
<revhistory>