From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: On network management and documenting nmcli Date: Sun, 13 May 2018 10:44:32 -0700 Message-ID: <8736yvzbzz.fsf@gmail.com> References: <87in7u33xy.fsf@gmail.com> <87y3goe16z.fsf@gmail.com> <871segm3iz.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51912) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fHv33-0006mK-4U for help-guix@gnu.org; Sun, 13 May 2018 13:44:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fHv32-0003jC-67 for help-guix@gnu.org; Sun, 13 May 2018 13:44:41 -0400 Received: from mail-pf0-x234.google.com ([2607:f8b0:400e:c00::234]:43802) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fHv31-0003it-W2 for help-guix@gnu.org; Sun, 13 May 2018 13:44:40 -0400 Received: by mail-pf0-x234.google.com with SMTP id j20-v6so4925280pff.10 for ; Sun, 13 May 2018 10:44:39 -0700 (PDT) In-Reply-To: <871segm3iz.fsf@gmail.com> (Pierre Neidhardt's message of "Sun, 13 May 2018 09:13:40 +0200") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Pierre Neidhardt Cc: "help-guix@gnu.org" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Pierre Neidhardt writes: > As far as I can remember, the documentation example did not work for me. > > I think it is because I had built a custom image on which nmcli was > running because the network-manager service was automatically started, > unbeknownst to me. > > Beyond the installation process, I think my example is also relevant for > at least one of the official "lightweight-desktop.scm" configuration > file for which the default way to connect is nmcli. The example in the manual is intended for the situation in which someone is installing GuixSD using the official installation image. If you're using a custom image, or if you're using an installed system built from lightweight-desktop.scm or something else, then the instructions may not apply. I think that's appropriate. Once a user installs whatever system they want to use, it's partially up to them to understand how to use it. For example, we don't fully document all the features of GNOME just because we package it as a desktop environment. I think the same goes for tools like nmtui. If a user wants to use it, they will figure out how to use it. The various methods for network management are described in the manual (see: "(guix) Networking Services"). I don't feel like there are any egregious omissions related to networking or nmtui in particular. If there is a common problem that people trip over during the official installation process, then it might be a different story. However, it doesn't sound like that's the case. Am I missing something? =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlr4eYAACgkQ3UCaFdgi Rp24MRAAtlPbcjDm5pujUvo/sad8PDdvCC87H/BHIR2jLxrMzRH3pa40sA0+CV64 MB3EMAF8crBlch47O8VjGgwsZuS1CyvG3oBQ0W+h6v+MbyEHtc6n0PZTIQTkCdJy l0vDPguppXMJFKQSwy52NljKOzy03JeH5C2WmyvkOg/KvslxEd0P2QSxnSXSUlEd px8ajxyRaBt1StM+EsRI2gousr3QrimBlZ3CEjigcMQzvevZ0q1lbAd2fCkRdATY AI23yRAIb21rPHxQ5g83e14VQ0xeWDpYR9gGcbAQt1YRu22ifCAQW7pUpNLIa6hg aXDRmhaJQSsm4RwWrqrn57XBZ5k1Nj1mOdNseMdia4UPduzgRzQqD302rzeGmPs8 AYlhUHzCWOyVajFhHhWG75Q7E6501z8pNsTxKZ7mjIxxsIDdGeJSj6vOpXz8RfMO 4p9uSVik8IdBd6h+yfeIzQ7jOMXCUkeeLEh1MEh+bU3a3jpd+MAI5MZpKdOaKI4W 2ZZeOJIK1BC/0+Y4uM/TpNawtSofnlIVQwsztVOoZbt6O/vU78w6d1EKuMiDbTM8 ezPVvu8GgtCL6LN8ahfSzGZ7DtxpwUF0dfQJSrYYh51e20YqNAVSNmdRrUN1yQKA DjnLZqJgKMYj5WWYy6FWUHpZ7fkfXzZSxnojfcwrZdVBT9OmQvU= =9u8/ -----END PGP SIGNATURE----- --=-=-=--