public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cranford <ac9410@bellsouth.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: [Patch]: incorrect e2fsprog data from ver_linux script
Date: Thu, 30 Aug 2001 22:03:25 -0400	[thread overview]
Message-ID: <3B8EF06D.24BAB4AF@bellsouth.net> (raw)

Hello Alan/Linus,
Ted suggested I pass this onto your for 2.2 and 2.4
Please apply small patch to both releases.
Thanks,
Albert


-------- Original Message --------
Subject: incorrect e2fsprog data from ver_linux script
Date: Thu, 30 Aug 2001 10:08:27 -0400
From: Albert Cranford <ac9410@bellsouth.net>
To: tytso@valinux.com, tytso@mit.edu

Hello Ted,
I'm not sure when incorrect e2fsprog info started popping
up from the linux/scripts/ver_linux script, but what do
you think about submitting this patch to Linus?
Later,
Albert


---BEFORE------------------------------
home1:~ /usr/src/linux/scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

Linux home1 2.4.10-pre2 #1 Thu Aug 30 00:17:13 EDT 2001 i686 AuthenticAMD

Gnu C                  3.0.1
Gnu make               3.79
binutils               2.11.2
util-linux             2.11h
mount                  2.11h
modutils               2.4.8
e2fsprogs              tune2fs
PPP                    2.4.0
----AFTER-----------------------------
home1:~ /usr/local/bin/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

Linux home1 2.4.10-pre2 #1 Thu Aug 30 00:17:13 EDT 2001 i686 AuthenticAMD

Gnu C                  3.0.1
Gnu make               3.79
binutils               2.11.2
util-linux             2.11h
modutils               2.4.8
e2fsprogs              1.23
PPP                    2.4.0
----BEFORE-----------------------------
home1:/usr/src/e2fsprogs-1.23/misc# tune2fs 2>&1 | grep tune2fs | sed 's/,//' |
awk 'NR==1 {print "e2fsprogs             ", $2}'
e2fsprogs              tune2fs
----AFTER------------------------------
home1:/usr/src/e2fsprogs-1.23/misc# tune2fs 2>&1 | grep tune2fs | sed 's/,//' |
awk 'NR==2 {print "e2fsprogs             ", $2}'
e2fsprogs              1.23
----PATCH-----------------------------
--- linux/scripts/ver_linux.orig        Thu Aug 30 09:56:39 2001
+++ linux/scripts/ver_linux     Thu Aug 30 09:56:49 2001
@@ -27,7 +27,7 @@
 insmod -V  2>&1 | awk 'NR==1 {print "modutils              ",$NF}'
 
 tune2fs 2>&1 | grep tune2fs | sed 's/,//' |  awk \
-'NR==1 {print "e2fsprogs             ", $2}'
+'NR==2 {print "e2fsprogs             ", $2}'
 
 reiserfsck 2>&1 | grep reiserfsprogs | awk \
 'NR==1{print "reiserfsprogs         ", $NF}'
-- 
Albert Cranford Deerfield Beach FL USA
ac9410@bellsouth.net


             reply	other threads:[~2001-08-31  2:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-31  2:03 Albert Cranford [this message]
2001-08-31  1:24 ` [Patch]: incorrect e2fsprog data from ver_linux script Steven Cole
2001-08-31  5:42   ` [Better Patch]: " Albert Cranford

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=3B8EF06D.24BAB4AF@bellsouth.net \
    --to=ac9410@bellsouth.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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