From: Pierre Neidhardt <ambrevar@gmail.com>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: On network management and documenting nmcli
Date: Fri, 11 May 2018 12:02:49 +0200 [thread overview]
Message-ID: <87in7u33xy.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
During my first encounter with GuixSD, I could not connect to the
Internet for reasons that puzzled me, and I could not find any mention
of it in the manual either.
At first I assumed I had done something wrong with the setup.
I had tried to run wpa_supplicant manually, like I often do on other
distributions. It's only later that I understood why wpa_supplicant
failed: it was because it was already running! (It's stupid but
wpa_supplicant's error messages are extremely misleading.)
The manual is extremely scarse about network configuration. Sure
enough, if nm-applet is running it's rather straightforward. But for a
desktop-environment-less setup and during the install, the default tool
is nmcli only (unless another manager is used, but then the user
probably knows what they are doing).
I don't think any of this is mentioned at all in the manual: I believe
something so essential should be very explicitly documented.
I suggest we add some examples to the Installation info page, for instance:
> nmcli device wifi
> sudo nmcli d w connect "foo SSID" password "foo password"
Mention that tab-completion can be use to complete SSIDs, which is
useful in the event they contain special or invisible characters
(trailing spaces are common).
We should also hint at the (7)nmcli-examples man page.
Unrelated question: why do I need to "sudo" to add a connection?
If I recall correctly, nm-applet does not ask for extra privileges
(could be wrong though).
Comments?
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2018-05-11 10:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 10:02 Pierre Neidhardt [this message]
2018-05-11 12:21 ` On network management and documenting nmcli Oleg Pykhalov
2018-05-11 12:57 ` Devan Carpenter
2018-05-11 13:00 ` Pierre Neidhardt
2018-05-11 13:10 ` Devan Carpenter
2018-05-11 13:15 ` Pierre Neidhardt
2018-05-13 7:26 ` Nils Gillmann
2018-05-13 11:08 ` swedebugia
2018-05-13 12:22 ` Nils Gillmann
2018-05-13 12:33 ` Nils Gillmann
2018-05-13 2:31 ` Chris Marusich
2018-05-13 7:13 ` Pierre Neidhardt
2018-05-13 17:44 ` Chris Marusich
2018-05-13 19:21 ` Pierre Neidhardt
2018-05-22 12:42 ` swedebugia
2018-05-22 15:26 ` Pierre Neidhardt
2018-05-23 15:39 ` Ludovic Courtès
2018-05-23 15:45 ` Pierre Neidhardt
2018-05-23 18:18 ` swedebugia
2018-05-24 12:33 ` Ludovic Courtès
2018-05-24 12:40 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87in7u33xy.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.