public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cranford <ac9410@bellsouth.net>
To: elenstev@mesatop.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	tytso@mit.edu
Subject: Re: [Better Patch]: incorrect e2fsprog data from ver_linux script
Date: Fri, 31 Aug 2001 01:42:29 -0400	[thread overview]
Message-ID: <3B8F23C5.E03148E1@bellsouth.net> (raw)
In-Reply-To: <3B8EF06D.24BAB4AF@bellsouth.net> <200108310325.f7V3Pge00680@thor.mesatop.com>

Good find Steven.  Now I see the difference between
1.22 and 1.23.  This patch is better than the last patch.
Linus and Alan, please use this instead.
1.22 was "header then usage", while 
1.23 is "usage then header".

home1:# ./tune2fs 2>&1  |grep tune2fs
tune2fs 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09
Usage: ./tune2fs [-c max-mounts-count] [-e errors-behavior] [-g group]

home1:# /sbin/tune2fs 2>&1  |grep tune2fs
Usage: /sbin/tune2fs [-c max-mounts-count] [-e errors-behavior] [-g group]
tune2fs 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09

home1:# ./tune2fs 2>&1 | grep "^tune2fs" | sed 's/,//' |  awk 'NR==1 {print "e2fsprogs             ", $2}'
e2fsprogs              1.22
home1:# /sbin/tune2fs 2>&1 | grep "^tune2fs" | sed 's/,//' |  awk 'NR==1 {print "e2fsprogs             ", $2}'
e2fsprogs              1.23
--------PATCH--------------
--- linux/scripts/ver_linux.orig      Fri Aug 31 01:15:22 2001
+++ linux/scripts/ver_linux   Fri Aug 31 01:17:47 2001
@@ -26,7 +26,7 @@

 insmod -V  2>&1 | awk 'NR==1 {print "modutils              ",$NF}'

-tune2fs 2>&1 | grep tune2fs | sed 's/,//' |  awk \
+tune2fs 2>&1 | grep "^tune2fs" | sed 's/,//' |  awk \
 'NR==1 {print "e2fsprogs             ", $2}'

 reiserfsck 2>&1 | grep reiserfsprogs | awk \
----------END PATCH-------

Steven Cole wrote:
>
> So, this patch breaks the ver_linux script for 1.22, and 1.21 (I checked
> this too).  If someone wants to fix this right, please jump in.
> 
> Steven
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Albert Cranford Deerfield Beach FL USA
ac9410@bellsouth.net


      reply	other threads:[~2001-08-31  5:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-31  2:03 [Patch]: incorrect e2fsprog data from ver_linux script Albert Cranford
2001-08-31  1:24 ` Steven Cole
2001-08-31  5:42   ` Albert Cranford [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=3B8F23C5.E03148E1@bellsouth.net \
    --to=ac9410@bellsouth.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=elenstev@mesatop.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=tytso@mit.edu \
    /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