From: Roberto Nibali <ratz@drugphish.ch>
To: David Ford <david+cert@blue-labs.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ver_linux script updates
Date: Thu, 14 Feb 2002 02:08:08 +0100 [thread overview]
Message-ID: <3C6B0DF8.10209@drugphish.ch> (raw)
In-Reply-To: <3C6ADCAA.6080600@blue-labs.org>
Hello,
David Ford wrote:
> I've been working on an update to the ver_linux script and I'm looking
> for comment and help in improving the accuracy of reported information.
> The script is at http://stuph.org/ver_linux
>
> Please provide feedback on it.
o your script assumes bash as /bin/sh. Is this ok with everyone? Is
there noone running a Bourne shell only? printf and declare are not
in the standard Boune shell, IIRC.
o the script hangs when calling loadkeys, because loadkeys without
arguments waits forever. A fix is to pass "loadkeys -V" as third
argument to pv().
o if you assume bash why don't you try to convert all of the code into
bash (inline functions) instead of using awk and sed like the old code
did?
o your script indicates that one should check for "not found/error" but
this never appears, it should be "error getting version, try manually"
o the old script separated the loaded kernel modules with a space, the
new code with a '\n'
o the old code correctly detects my "kbd" version, the new not, because
you use setleds which on my machine reports: "KDGKBLED: Invalid
argument"
Why do you want to change this tool? To me it seems like an endless task
because people don't code according to standards. For example if
everyone could stick to let's say that 'progname --version' prints the
version, things would be a lot easier.
Cheers,
Roberto Nibali, ratz
next prev parent reply other threads:[~2002-02-14 1:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 21:37 ver_linux script updates David Ford
2002-02-14 1:08 ` Roberto Nibali [this message]
2002-02-14 1:35 ` David Ford
2002-02-14 2:29 ` Roberto Nibali
2002-02-14 7:49 ` David Ford
2002-02-15 2:25 ` Roberto Nibali
2002-02-15 7:46 ` David Ford
2002-02-14 12:34 ` Stefan Becker
2002-02-14 18:08 ` David Ford
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=3C6B0DF8.10209@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=david+cert@blue-labs.org \
--cc=linux-kernel@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