Code change:
<del> <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="sec-steam"> <title>Steam</title> <section xml:id="sec-steam-nix"> <title>Steam in Nix</title> <para> Steam is distributed as a <filename>.deb</filename> file, for now only as an i686 package (the amd64 package only has documentation). When unpacked, it has a script called <filename>steam</filename> that in Ubuntu (their target distro) would go to <filename>/usr/bin </filename>. When run for the first time, this script copies some files to the user's home, which include another script that is the ultimate responsible for launching the steam binary, which is also in $HOME. </para> <para> Nix problems and constraints: <itemizedlist> <listitem> <para> We don't have <filename>/bin/bash</filename> and many scripts point there. Similarly for <filename>/usr/bin/python</filename> . </para> </listitem> <listitem> <para> We don't have the dynamic loader in <filename>/lib </filename>. </para> </listitem> <listitem> <para> The <filename>steam.sh</filename> script in $HOME can not be patched, as it is checked and rewritten by steam. </para> </listitem> <listitem> <para> The steam binary cannot be patched, it's also checked. </para> </listitem> </itemizedlist> </para> <para> The current approach to deploy Steam in NixOS is composing a FHS-compatible chroot environment, as documented <link xlink:href="http://sandervanderburg.blogspot.nl/2013/09/composing-fhs-compatible-chroot.html">here</link>. This allows us to have binaries in the expected paths without disrupting the system, and to avoid patching them to work in a non FHS environment. </para> </section> <section xml:id="sec-steam-play"> <title>How to play</title> <para> Use <programlisting>programs.steam.enable = true;</programlisting> if you want to add steam to systemPackages and also enable a few workarrounds aswell as Steam controller support or other Steam supported controllers such as the DualShock 4 or Nintendo Switch Pr. </para> </section> <section xml:id="sec-steam-troub"> <title>Troubleshooting</title> <para> <variablelist> <varlistentry> <term> Steam fails to start. What do I do? </term> <listitem> <para> Try to run <programlisting>strace steam</programlisting> to see what is causing steam to fail. </para> </listitem> </varlistentry> <varlistentry> <term> Using the FOSS Radeon or nouveau (nvidia) drivers </term> <listitem> <itemizedlist> <listitem> <para> The <literal>newStdcpp</literal> parameter was removed since NixOS 17.09 and should not be needed anymore. </para> </listitem> <listitem> <para> Steam ships statically linked with a version of libcrypto that conflics with the one dynamically loaded by radeonsi_dri.so. If you get the error <programlisting>steam.sh: line 713: 7842 Segmentation fault (core dumped)</programlisting> have a look at <link xlink:href="https://github.com/NixOS/nixpkgs/pull/20269">this pull request</link>. </para> </listitem> </itemizedlist> </listitem> </varlistentry> <varlistentry> <term> Java </term> <listitem> <orderedlist> <listitem> <para> There is no java in steam chrootenv by default. If you get a message like <programlisting>/home/foo/.local/share/Steam/SteamApps/common/towns/towns.sh: line 1: java: command not found</programlisting> You need to add <programlisting> steam.override { withJava = true; };</programlisting> to your configuration. </para> </listitem> </orderedlist> </listitem> </varlistentry> </variablelist> </para> </section> <section xml:id="sec-steam-run"> <title>steam-run</title> <para> The FHS-compatible chroot used for steam can also be used to run other linux games that expect a FHS environment. To do it, add <programlisting>pkgs.(steam.override { nativeOnly = true; newStdcpp = true; }).run</programlisting> to your configuration, rebuild, and run the game with <programlisting>steam-run ./foo</programlisting> </para> </section> </section> </del>

Related discussion:
text: This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.
I will also work on this