All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Patrick McHardy <kaber@trash.net>
Cc: Ben Greear <greearb@candelatech.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	netdev@vger.kernel.org
Subject: Re: Could you make vconfig less stupid?
Date: Tue, 7 Oct 2008 15:20:56 +0300	[thread overview]
Message-ID: <200810071520.56610.denys@visp.net.lb> (raw)
In-Reply-To: <48EB488A.40409@trash.net>

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

Probably to make people use iproute2, it is good to inform them, that iproute2 
can do that job. 

For example i didn't knew that ip can make vlan's and etc.
And even embedded help doesn't help almost.

Something like attached trivial patch, at least will give idea, what to do.

man page i can edit too, but i guess it is better someone with good english 
will do that.

On Tuesday 07 October 2008, Patrick McHardy wrote:
> Ben Greear wrote:
> > Patrick McHardy wrote:
> >> Actually I don't maintain vconfig and I don't think Ben does either.
> >> Its deprecated and iproute is what people should use, all the new
> >> features are not supported by vconfig.
> >
> > I can fix these things if anyone cares, but leaving it crufty might be a
> > better way to encourage folks to use 'ip'.
>
> I think it would make sense to add a note to the manpage
> or something like that. Maybe also a runtime warning in
> case its really (going to be) unmaintained.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



[-- Attachment #2: iproute_linkhelp_rfc.txt --]
[-- Type: text/plain, Size: 734 bytes --]

diff -Naur iproute2.backup/ip/iplink.c iproute2/ip/iplink.c
--- iproute2.backup/ip/iplink.c	2008-10-05 15:41:59.000000000 +0000
+++ iproute2/ip/iplink.c	2008-10-07 12:14:28.000000000 +0000
@@ -54,6 +54,10 @@
 	fprintf(stderr, "	                     mtu MTU }\n");
 	fprintf(stderr, "	                     netns PID }\n");
 	fprintf(stderr, "       ip link show [ DEVICE ]\n");
+	fprintf(stderr, "       ip link add link PARENTDEV type { vlan | veth } { ... | help }\n");
+	fprintf(stderr, "       ip link add link PARENTDEV NEWDEVICE type macvlan { ... | help }\n");
+	fprintf(stderr, "       ip link change link PARENTDEV type { vlan | veth } { ... | help}\n");
+	fprintf(stderr, "       ip link del dev DEVICE\n");
 	exit(-1);
 }
 

  reply	other threads:[~2008-10-07 12:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-06 18:24 Could you make vconfig less stupid? Stephen Hemminger
2008-10-06 22:26 ` Patrick McHardy
2008-10-07  2:32   ` Ben Greear
2008-10-07 11:31     ` Patrick McHardy
2008-10-07 12:20       ` Denys Fedoryshchenko [this message]
2008-10-07 12:24         ` Patrick McHardy
2008-10-07 12:48         ` Milan Kocian
2008-10-07 12:49           ` Denys Fedoryshchenko
2008-10-07 12:56             ` Patrick McHardy
2008-10-07 13:16               ` Martin Josefsson
2008-10-07 13:54                 ` Patrick McHardy
2008-10-07 13:57                 ` Patrick McHardy
2008-10-07 13:28               ` Milan Kocian
2008-10-07 13:29                 ` Patrick McHardy
2008-10-07 14:06                 ` Stephen Hemminger

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=200810071520.56610.denys@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=greearb@candelatech.com \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /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 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.