diff options
author | Eelco Dolstra <e.dolstra@tudelft.nl> | 2005-09-14T18·50+0000 |
---|---|---|
committer | Eelco Dolstra <e.dolstra@tudelft.nl> | 2005-09-14T18·50+0000 |
commit | 025086edeaa6fc39ee8b5bc6fcad3cc64c2fd0c2 (patch) | |
tree | ff3ea5af8d1f5f096cbec6148e9001565f1d3fed /doc/manual/introduction.xml | |
parent | ed1db42915dc13cff9b940ae2b12ff9e38b28961 (diff) |
* Release notes in Docbook; ASCII release notes (i.e., the `NEWS'
file) is now generated from that using `w3m' and some XSL hackery.
Diffstat (limited to 'doc/manual/introduction.xml')
-rw-r--r-- | doc/manual/introduction.xml | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/doc/manual/introduction.xml b/doc/manual/introduction.xml index 9f94b2d5394d..fb6e79fcb59f 100644 --- a/doc/manual/introduction.xml +++ b/doc/manual/introduction.xml @@ -130,8 +130,8 @@ collection. It also discusses some advanced topics, such as setting up a Nix-based build farm, and doing service deployment using Nix.</para> -<note><para>Some background information on Nix can be found in three -papers. The ICSE 2004 paper <ulink +<note><para>Some background information on Nix can be found in a +number of papers. The ICSE 2004 paper <ulink url='http://www.cs.uu.nl/~eelco/pubs/immdsd-icse2004-final.pdf'><citetitle>Imposing a Memory Management Discipline on Software Deployment</citetitle></ulink> discusses the hashing mechanism used to @@ -144,7 +144,10 @@ Deployment</citetitle></ulink> gives a more general discussion of Nix from a system-administration perspective. The CBSE 2005 paper <ulink url='http://www.cs.uu.nl/~eelco/pubs/eupfcdm-cbse2005-final.pdf'><citetitle>Efficient Upgrading in a Purely Functional Component Deployment Model -</citetitle></ulink> is about transparent patch deployment in -Nix.</para></note> +</citetitle></ulink> is about transparent patch deployment in Nix. +Finally, the SCM-12 paper <ulink +url='http://www.cs.uu.nl/~eelco/pubs/servicecm-scm12-final.pdf'> +Service Configuration Management</ulink> shows how services (e.g., web +servers) can be deployed and managed through Nix.</para></note> </chapter> |