public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Cliff White <cliffw@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test4-mm3
Date: 30 Aug 2003 08:16:23 +0200	[thread overview]
Message-ID: <1062224182.30172.4.camel@workshop.saharacpt.lan> (raw)
In-Reply-To: <200308291627.h7TGRoX02912@mail.osdl.org>

On Fri, 2003-08-29 at 18:27, Cliff White wrote:

Hi

> This also breaks STP. We installed module-init-tools using the 'moveold' 
> method,
> so we can still run 2.4.
> Our depmod is in /usr/local/sbin. 
> Using /sbin/depmod hoses us. Using PATH works for us.
> 
> [root@stp1-002 linux]# depmod -V
> module-init-tools 0.9.12
> 
> [root@stp1-002 linux]# /sbin/depmod -V
> depmod version 2.4.22
> 
> [root@stp1-002 linux]# /usr/local/sbin/depmod -V
> module-init-tools 0.9.12
> 

You guys are sorda missing the point of 'moveold' ....
You want to build it with '--prefix=/' so that
both depmod and depmod.old are in /sbin ....

----------------------
workshop root # ls /sbin/depmod* -l
-rwxr-xr-x    1 root     root        58744 Aug  4 17:19 /sbin/depmod
-rwxr-xr-x    1 root     root        58712 Aug  4 13:57 /sbin/depmod.old
workshop root # ls /sbin/modprobe* -l
lrwxrwxrwx    1 root     root            6 Aug  4 17:19 /sbin/modprobe
-> insmod
lrwxrwxrwx    1 root     root           10 Aug  4 13:57
/sbin/modprobe.old -> insmod.old
lrwxrwxrwx    1 root     root           13 Aug  4 17:19
/sbin/modprobe.static -> insmod.static
workshop root # 
------------------

Any call will then thus run depmod/whatever from module-init-tools
first, and if the kernel is 2.4, etc, it will call
depmod.old/whatever ...


Regards,

-- 
Martin Schlemmer



  parent reply	other threads:[~2003-08-30  6:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29  9:54 2.6.0-test4-mm3 Boszormenyi Zoltan
2003-08-29 12:52 ` 2.6.0-test4-mm3 Bas Mevissen
2003-08-29 13:00 ` 2.6.0-test4-mm3 Valdis.Kletnieks
     [not found]   ` <1062168946.19599.114.camel@workshop.saharacpt.lan>
2003-08-30  7:35     ` 2.6.0-test4-mm3 Martin Schlemmer
     [not found]     ` <200308291553.h7TFrcGG009390@turing-police.cc.vt.edu>
2003-09-01 20:23       ` 2.6.0-test4-mm3 Martin Schlemmer
2003-09-01 20:34         ` 2.6.0-test4-mm3 Sam Ravnborg
2003-09-01 23:52         ` 2.6.0-test4-mm3 Valdis.Kletnieks
2003-09-02  4:14           ` 2.6.0-test4-mm3 Martin Schlemmer
2003-09-02 14:31             ` 2.6.0-test4-mm3 Valdis.Kletnieks
2003-08-29 15:35 ` 2.6.0-test4-mm3 Andrew Morton
2003-08-29 16:22   ` 2.6.0-test4-mm3 Valdis.Kletnieks
2003-08-29 16:27   ` 2.6.0-test4-mm3 Cliff White
2003-08-29 16:34     ` 2.6.0-test4-mm3 Andrew Morton
2003-08-30  6:16     ` Martin Schlemmer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-29  6:56 2.6.0-test4-mm3 Andrew Morton
2003-08-29  7:45 ` 2.6.0-test4-mm3 Andrew Morton
2003-08-29 15:42 ` 2.6.0-test4-mm3 Ed Sweetman
2003-08-29 15:57   ` 2.6.0-test4-mm3 Andrew Morton
2003-08-29 15:59   ` 2.6.0-test4-mm3 Felipe Alfaro Solana
2003-09-10 18:53 ` 2.6.0-test4-mm3 Mike Fedyk

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=1062224182.30172.4.camel@workshop.saharacpt.lan \
    --to=azarah@gentoo.org \
    --cc=akpm@osdl.org \
    --cc=cliffw@osdl.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