From: Jiri Benc <jbenc@redhat.com>
To: Zaboj Campula <zaboj.campula@post.cz>
Cc: Jiri Pirko <jiri@resnulli.us>, netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: show network device dependency tree
Date: Wed, 1 Mar 2017 11:22:28 +0100 [thread overview]
Message-ID: <20170301112228.713bd4d5@griffin> (raw)
In-Reply-To: <1488312457.2131.2.camel@post.cz>
On Tue, 28 Feb 2017 20:07:37 +0000, Zaboj Campula wrote:
> Well it is impossible to draw a simple tree showing the configuration
> exactly with all details. May be it is too ambitious to draw a tree
> at all.
I tried that and failed. I didn't want to have something that would
work only "somehow" as that would create confusion instead of helping.
See the example below.
> But neither directory structure is a tree (when consider links)
> and there are a plenty of tools showing directory tree.
Directory structure *is* a tree. Symlinks are a special case, for the
purpose of displaying the tree they're just files. Hardlinks can be
ignored when displaying a tree (because there are no hardlinks to
directories). We don't have any of that.
Consider the very simple case of an interface with two vlan interfaces
and both of them in a bridge.
vlan0
/ \
eth0 br0
\ /
vlan1
You can't represent this in a tree view. And this is just a very simple
example, in reality it tends to be much more complex.
Jiri
next prev parent reply other threads:[~2017-03-01 10:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 16:59 [PATCH] iproute2: show network device dependency tree Zaboj Campula
2017-02-25 17:39 ` Jiri Pirko
2017-02-25 20:22 ` Zaboj Campula
2017-02-26 7:56 ` Jiri Pirko
2017-02-26 14:00 ` Zaboj Campula
2017-02-26 14:46 ` Jiri Pirko
2017-02-27 16:38 ` Jiri Benc
2017-02-28 20:07 ` Zaboj Campula
2017-03-01 10:22 ` Jiri Benc [this message]
2017-03-02 19:51 ` Zaboj Campula
2017-02-27 17:26 ` Stephen Hemminger
2017-02-27 18:52 ` Stephen Hemminger
2017-02-27 18:55 ` Stephen Hemminger
2017-02-28 20:19 ` Zaboj Campula
2017-02-28 21:47 ` Jiri Pirko
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=20170301112228.713bd4d5@griffin \
--to=jbenc@redhat.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=zaboj.campula@post.cz \
/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 NNTP newsgroup(s).