From: Mauricio Faria de Oliveira <mfo@canonical.com>
To: fstests@vger.kernel.org
Subject: [PATCH] common/rc: print out kernel version too
Date: Wed, 10 Jul 2019 14:58:09 -0300 [thread overview]
Message-ID: <20190710175809.13391-1-mfo@canonical.com> (raw)
The kernel version (uname -v) may also be needed in addition to
the kernel release (uname -r) in order to properly identify and
distinguish different kernel builds in some cases/distributions.
For example, in the Ubuntu kernel package the test/debug string
is usually a suffix to the version field, not the release field.
$ uname -rv
4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019
$ uname -rv
4.15.0-51-generic #55+test20190520b1 SMP Mon May 20 11:57:40 -03 2019
Looking at other OSes uname(1) man pages it looks like '-v' is
quite standard, and the Linux man page only cites '-p' and '-i'
as non-portable, so the change should be OK. The only caller is
the 'check' script for the header print out, so it's contained.
Signed-off-by: Mauricio Faria de Oliveira <mfo@canonical.com>
---
common/rc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/rc b/common/rc
index dcd591b33b87..000a7cc821cf 100644
--- a/common/rc
+++ b/common/rc
@@ -2794,7 +2794,7 @@ _full_platform_details()
{
local os=`uname -s`
local host=`hostname -s`
- local kernel=`uname -r`
+ local kernel=`uname -rv`
local platform=`uname -m`
echo "$os/$platform $host $kernel"
}
--
2.17.1
next reply other threads:[~2019-07-10 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 17:58 Mauricio Faria de Oliveira [this message]
2019-07-10 19:03 ` [PATCH] common/rc: print out kernel version too Gabriel Krisman Bertazi
2019-07-10 19:16 ` Mauricio Faria de Oliveira
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=20190710175809.13391-1-mfo@canonical.com \
--to=mfo@canonical.com \
--cc=fstests@vger.kernel.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