From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: feedback as solicited by Guix manual (Section 7.1.5)
Date: Thu, 02 Jun 2016 11:37:55 +0300 [thread overview]
Message-ID: <8737ownfz0.fsf@gmail.com> (raw)
In-Reply-To: <87shww9fon.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 02 Jun 2016 10:07:52 +0200")
Ludovic Courtès (2016-06-02 11:07 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> Tomáš Čech (2016-06-01 07:53 +0300) wrote:
>>
>>> On Tue, May 31, 2016 at 11:10:21PM +0200, Ludovic Courtès wrote:
>>>>Matthew Jordan <matthewjordandevops@yandex.com> skribis:
>>>>
>>>>> mentions using ifconfig, correct me if I"m wrong but isn't ifconfig
>>>>> considered deprecated?
>>>>
>>>>This ifconfig (part of GNU Inetutils) is maintained, so I think it’s
>>>>fine. :-)
>>>
>>> Yes, ifconfig is considered deprecated for more than decade. I'm not
>>> networking guy but colleague of mine who is told me that ifconfig is
>>> just ugly wrapper not reflecting how the kernel is handling it.
>>> http://serverfault.com/questions/633087/where-is-the-statement-of-deprecation-of-ifconfig-on-linux
>>>
>>> iproute2 is way to go.
>>
>> I would also prefer to see "ip" command instead of "ifconfig" in the
>> manual. Alternatively both can be mentioned..
>
> I have a hard time leaving ifconfig/iwconfig. ;-)
>
> I was about to change the manual’s examples to ‘ip’, but then realized
> that this is Linux-specific and doesn’t buy us much for these simple
> cases. So, what about this:
Wow, do you mean that ifconfig is not only for Linux kernel?
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 6d47976..5fd4679 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -5999,7 +5999,9 @@ more information.
>
> @subsubsection Networking
>
> -Run the following command see what your network interfaces are called:
Run the following command to see what your network interfaces are called:
BTW I think there is a typo here ↑, isn't it?
> +Run the following command see what your network interfaces are called
> +(on GNU/Linux, seasoned users may prefer the versatile @command{ip}
> +command over @command{ifconfig}):
>
> @example
> ifconfig -a
>
> Dunno if it really helps, since “seasoned users” already know that ‘ip’
> is the thing.
If ifconfig is a general thing (suitable for Hurd) then I agree; we
should probably leave it as it is now. Otherwise I would also add a
mention how to do it with "ip", like this:
@example
ifconfig -a
@end example
or
@example
ip a
@end example
--
Alex
next prev parent reply other threads:[~2016-06-02 8:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 0:45 feedback as solicited by Guix manual (Section 7.1.5) Ethan Stefan Day
2016-05-31 15:58 ` Leo Famulari
2016-05-31 16:31 ` Matthew Jordan
2016-05-31 17:56 ` Leo Famulari
2016-05-31 18:35 ` Matthew Jordan
2016-05-31 21:10 ` Ludovic Courtès
2016-06-01 4:53 ` Tomáš Čech
2016-06-01 19:45 ` Alex Kost
2016-06-02 8:07 ` Ludovic Courtès
2016-06-02 8:37 ` Alex Kost [this message]
2016-06-03 8:11 ` Ludovic Courtès
2016-06-04 12:52 ` Alex Kost
2016-06-01 19:22 ` Matthew Jordan
2016-06-03 8:00 ` Ludovic Courtès
2016-05-31 21:13 ` Ethan Stefan Day
2016-06-04 21:00 ` Rescuing the GNU Storage Guide? Ludovic Courtès
2016-06-04 23:18 ` Ludovic Courtès
2016-05-31 16:19 ` feedback as solicited by Guix manual (Section 7.1.5) Ludovic Courtès
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=8737ownfz0.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).