From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, rhw@MemAlpha.CX
Cc: kaboom@gatech.edu, linux-kernel@vger.kernel.org,
seberino@spawar.navy.mil
Subject: Re: [PATCH] Improved version reporting
Date: Fri, 16 Mar 2001 13:45:35 +0100 (MET) [thread overview]
Message-ID: <UTC200103161245.NAA00944.aeb@vlet.cwi.nl> (raw)
From: Riley Williams <rhw@MemAlpha.CX>
Neither am I - but, according to comments from RedHat a while back,
they repackage mount separately because they provide a NEWER version
of mount than is in the util-linux package. This will ALSO result in
`mount --version` giving the wrong answer...
There is no newer version.
In ancient times I came with frequent releases of mount, at a time
when util-linux was released very infrequently. These years mount
is part of util-linux, and util-linux is released frequently.
Unless one can guarantee that the util-linux and mount packages are
the SAME version, mount can't be guaranteed to report the version of
the util-linux package installed. RedHat provide a NEWER version of
mount to util-linux so that guarantee doesnae exist.
I do not think they do.
> You are mistaken, as is proved by the reports that contain a kbd
> line: a grep on linux-kernel for this Februari shows people with
> Kbd 0.96, 0.99 and 1.02.
{Shrug} Please explain why I was unable to get ver_linux to report a
When other people can and you cannot, why should I explain your failure?
Let me just check. A version from 1993:
% ./loadkeys -h 2>&1 | head -1
loadkeys version 0.81
A version from 2001:
% ./loadkeys -h 2>&1 | head -1
loadkeys version 1.06
Maybe nothing has changed here the past eight years. It just works.
Perhaps you tried some modified version.
Andries
next reply other threads:[~2001-03-16 12:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 12:45 Andries.Brouwer [this message]
2001-03-16 13:30 ` [PATCH] Improved version reporting Nick Holloway
2001-03-16 23:28 ` Riley Williams
-- strict thread matches above, loose matches on Subject: below --
2001-03-17 10:20 Andries.Brouwer
2001-03-17 1:07 Andries.Brouwer
2001-03-17 17:17 ` Riley Williams
2001-03-15 9:52 Andries.Brouwer
2001-03-15 11:05 ` Rogier Wolff
2001-03-17 4:35 ` Albert D. Cahalan
2001-03-17 17:51 ` Riley Williams
2001-03-19 6:50 ` Albert D. Cahalan
2001-03-19 9:15 ` Riley Williams
2001-03-23 8:33 ` Albert D. Cahalan
2001-03-23 9:42 ` Riley Williams
2001-03-14 19:29 Andries.Brouwer
2001-03-14 23:39 ` Russell King
2001-03-16 10:54 ` Riley Williams
2001-03-14 16:51 Andries.Brouwer
2001-03-14 16:01 Andries.Brouwer
2001-03-14 16:26 ` Alexander Viro
2001-03-15 4:12 ` Albert D. Cahalan
2001-03-14 16:36 ` Henning P. Schmiedehausen
2001-03-14 17:28 ` Riley Williams
[not found] <11a40b11caeb.11caeb11a40b@nosc.mil>
2001-03-14 10:39 ` Riley Williams
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=UTC200103161245.NAA00944.aeb@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=kaboom@gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rhw@MemAlpha.CX \
--cc=seberino@spawar.navy.mil \
/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