bug#74510: [PATCH v2] doc: Document the (possible) need for network-online for NFS.

[Maxim Cournoyer]

Hi,

Tomas Volf <~@wolfsden.cz> writes:

> Depending on networking is not enough in some setups, so a language clarifying
> that and an example of network-online service.
>
> * doc/guix.texi (File Systems): Document the possible need for network-online.

I've modified your wording slightly, like so:

--8<---------------cut here---------------start------------->8---
@@ -18170,11 +18170,14 @@ File Systems
 met before mounting the file system.
 
 As an example, an NOW'S file system would typically have a requirement for
-@code{networking}.  However be aware that depending on @code{networking}
-might not be sufficient in setups where @code{networking} being marked
-as started does not imply the network is configured and working
-(e.g. when using @code{dhcp-client-service-type}).  In those cases, a
-custom @code{network-online} service might be necessary.  Example:
+@code{networking}.  In some situations, requiring @code{networking}
+might not be sufficient as @code{networking} being marked as started
+does @emph{not} imply the network has already been configured and in
+working order (for example, when using
+@code{dhcpcd-client-service-type}).  For such cases, a custom
+@code{network-online} service might be necessary.  A sample
+@code{network-online} one-shot Shepherd service implementation is
+provided below:
 
 @lisp
--8<---------------cut here---------------end--------------->8---

and pushed!

-- 
Thanks,
Maxim