From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] iproute2: Do not ship /sbin/tipc
Date: Sat, 19 Mar 2022 22:52:44 +0100 [thread overview]
Message-ID: <c399bbc2-5d27-0928-c81d-dd46b6894325@ipfire.org> (raw)
In-Reply-To: <13403096-2b54-7005-3eb6-32ce67179f3b@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>
On 19/03/2022 16:32, Peter Müller wrote:
> TIPC (Transparent Inter Process Communication) is a protocol used for
> interprocess communication in computer clusters. We do not use this
> protocol at all, and the IPFire kernel knows nothing about it (although
> Lyins for some reason believes it does). Therefore, there is no sense in
> shipping /sbin/tipc, since this executable cannot do anything.
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/rootfiles/common/iproute2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/config/rootfiles/common/iproute2 b/config/rootfiles/common/iproute2
> index 0247aa976..e11bd8892 100644
> --- a/config/rootfiles/common/iproute2
> +++ b/config/rootfiles/common/iproute2
> @@ -24,7 +24,7 @@ sbin/rtmon
> sbin/rtstat
> sbin/ss
> sbin/tc
> -sbin/tipc
> +#sbin/tipc
> sbin/vdpa
> #usr/include/iproute2
> #usr/include/iproute2/bpf_elf.h
prev parent reply other threads:[~2022-03-19 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 15:32 Peter Müller
2022-03-19 15:32 ` [PATCH 2/2] iptables: Do not ship libxt_ddcp.so Peter Müller
2022-03-19 21:54 ` Adolf Belka
2022-03-21 8:49 ` Michael Tremer
2022-03-19 21:52 ` Adolf Belka [this message]
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=c399bbc2-5d27-0928-c81d-dd46b6894325@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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