From: Oleg Pykhalov <go.wigust@gmail.com>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: On network management and documenting nmcli
Date: Fri, 11 May 2018 15:21:03 +0300 [thread overview]
Message-ID: <871sei4c40.fsf@gmail.com> (raw)
In-Reply-To: <87in7u33xy.fsf@gmail.com> (Pierre Neidhardt's message of "Fri, 11 May 2018 12:02:49 +0200")
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
Hello Pierre,
Pierre Neidhardt <ambrevar@gmail.com> writes:
[…]
> 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"
I agree, except because of default user on an installation image is
‘root’ (as I remember) invoking a ‘sudo’ command is not required. Cannot
confirm it without burning a USB with installation image and QEMU cannot
boot it from my experience.
[…]
> Comments?
We could pick a ‘nmtui’ program as we pick ‘cfdisk’ instead of ‘fdisk’.
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-05-11 12:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 10:02 On network management and documenting nmcli Pierre Neidhardt
2018-05-11 12:21 ` Oleg Pykhalov [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871sei4c40.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).