From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] mpls01.sh: Add --allow-unsupported for modprobe
Date: Mon, 2 Sep 2024 12:39:13 +0200 [thread overview]
Message-ID: <ZtWV0R_oDb7BQdKm@yuki.lan> (raw)
In-Reply-To: <20240830103835.GA42409@pevik>
Hi!
> I'm not sure with ROD. --allow-unsupported is SUSE specific modprobe extension,
> which is used for SLES. It is also on Tumbleweed [1] [2] where does nothing.
>
> If you try to run it with ROD, which quits testing on failure, all distros
> except SUSE products/openSUSE (e.g. Debian, Fedora, ...) which don't have
> mpls_router will TBROK in setup:
>
> modprobe: unrecognised option '--allow-unsupported'.
>
> And I'm not talking about these small distros which use busybox kmod
> implementation, which would also fail.
>
> Also you remove /dev/null 2>&1 from the first command, thus other distros would
> not see error message about missing mpls_router module. Without looking into the
> source the tester will be pretty confused.
>
> I would do:
>
> if grep -q suse /etc/os-release; then
There are a couple of english words that contain "suse" as a substring
if one of these ends up in the os-release it would match, e.g. the
os-release may contain VERSION="24 (Disused Miracle)". And yes both
Fedora and Ubuntu seems to include the the code names in the file.
So I would be stricter here and checked for ID=suse.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-09-02 10:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 9:57 [LTP] [PATCH v1] mpls01.sh: Add --allow-unsupported for modprobe Wei Gao via ltp
2024-08-30 10:38 ` Petr Vorel
2024-09-02 10:39 ` Cyril Hrubis [this message]
2024-09-02 11:00 ` Petr Vorel
2024-09-02 2:40 ` [LTP] [PATCH v2] " Wei Gao via ltp
2024-09-02 11:02 ` Petr Vorel
2024-09-03 8:19 ` [LTP] [PATCH v3] " Wei Gao via ltp
2024-09-03 9:49 ` Petr Vorel
2024-09-03 10:16 ` Cyril Hrubis
2024-09-03 11:26 ` Petr Vorel
2024-09-04 3:58 ` [LTP] [PATCH v4] " Wei Gao via ltp
2024-09-04 4:47 ` Petr Vorel
2024-09-04 6:50 ` Wei Gao via ltp
2024-09-04 6:48 ` [LTP] [PATCH v5] " Wei Gao via ltp
2024-09-04 6:56 ` [LTP] [PATCH v6] mpls01: Add --allow-unsupported for modprobe(fixing all mpls cases) Wei Gao via ltp
2024-09-05 5:12 ` Petr Vorel
2024-09-05 8:47 ` Cyril Hrubis
2024-09-05 12:02 ` Petr Vorel
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=ZtWV0R_oDb7BQdKm@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.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