public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: carbonated beverage <ramune@net-ronin.org>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] modutils update
Date: Thu, 2 Jan 2003 15:45:41 -0800	[thread overview]
Message-ID: <20030102234541.GA19053@net-ronin.org> (raw)

Hi all,

	Update of Documentation/Changes and scripts/ver_linux to use
depmod instead of rmmod as per Rusty's suggestions.

	Would have sent this out sooner, but 'net access died...

-- DN
Daniel

diff -ur ../linux-2.5/Documentation/Changes linux-2.5/Documentation/Changes
--- ../linux-2.5/Documentation/Changes	Thu Jan  2 15:43:50 2003
+++ linux-2.5/Documentation/Changes	Thu Jan  2 15:46:37 2003
@@ -52,7 +52,7 @@
 o  Gnu make               3.78                    # make --version
 o  binutils               2.9.5.0.25              # ld -v
 o  util-linux             2.10o                   # fdformat --version
-o  module-init-tools      0.9                     # rmmod -V
+o  module-init-tools      0.9                     # depmod -V
 o  e2fsprogs              1.29                    # tune2fs
 o  jfsutils               1.0.14                  # fsck.jfs -V
 o  reiserfsprogs          3.6.3                   # reiserfsck -V 2>&1|grep reiserfsprogs
diff -ur ../linux-2.5/scripts/ver_linux linux-2.5/scripts/ver_linux
--- ../linux-2.5/scripts/ver_linux	Thu Jan  2 15:44:23 2003
+++ linux-2.5/scripts/ver_linux	Thu Jan  2 15:46:42 2003
@@ -28,7 +28,7 @@
 
 mount --version | awk -F\- '{print "mount                 ", $NF}'
 
-rmmod -V  2>&1 | awk 'NR==1 {print "module-init-tools     ",$NF}'
+depmod -V  2>&1 | awk 'NR==1 {print "module-init-tools     ",$NF}'
 
 tune2fs 2>&1 | grep "^tune2fs" | sed 's/,//' |  awk \
 'NR==1 {print "e2fsprogs             ", $2}'

                 reply	other threads:[~2003-01-02 23:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030102234541.GA19053@net-ronin.org \
    --to=ramune@net-ronin.org \
    --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