[Home]

Summary:DAHLIN-00127: uninstall-modules cannot find modinfo
Reporter:Dmitry Andrianov (dimas)Labels:
Date Opened:2009-07-14 05:32:14Date Closed:2009-09-21 10:19:28
Priority:MinorRegression?No
Status:Closed/CompleteComponents:General
Versions:2.2.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:make install produces;

....
make[2]: Entering directory `/usr/src/kernels/2.6.18-128.1.10.el5-i686'

 Building modules, stage 2.
 MODPOST
WARNING: could not find /usr/src/dahdi-linux-complete-tag-2.2.0.1+2.2.0/linux/drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_32.o.cmd for /usr/src/dahdi-linux-complete-tag-2.2.0.1+2.2.0/linux/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o
make[2]: Leaving directory `/usr/src/kernels/2.6.18-128.1.10.el5-i686'
build_tools/uninstall-modules dahdi 2.6.18-128.1.10.el5
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
....

This is because modinfo resides in the /sbin which is not in the PATH by default...

****** ADDITIONAL INFORMATION ******

CentOS 5.2

# uname -a
Linux hostname 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 i686 i386 GNU/Linux

Comments:By: Tzafrir Cohen (tzafrir) 2009-07-19 10:22:02

/sbin is not in the PATH of root?

By: Alessandro (alex70) 2009-07-20 03:12:40

The same occurs to me!
Linux hostname 2.6.18-128.1.10.el5.centos.plus #1 SMP Mon May 11 07:04:55 EDT 2009 i686 i686 i386 GNU/Linux

WARNING: could not find /usr/src/dahdi/drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_32.o.cmd for /usr/src/dahdi/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o
WARNING: could not find /usr/src/dahdi/drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_32.o.cmd for /usr/src/dahdi/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
build_tools/uninstall-modules: line 14: modinfo: command not found
.....

By: Dmitry Andrianov (dimas) 2009-07-20 03:18:07

tzafrir,  yes /sbin is not in the PATH for root.

By: Vladimir Mikhelson (vmikhelson) 2009-07-30 23:38:07

Same story here trying to "make," "make install" DAHDI 2.2

DAHDI Version: SVN-branch-2.2-r6864M

The same message is posted once in "make" and once in "make install."

 Building modules, stage 2.
 MODPOST
WARNING: could not find /usr/src/dahdi-linux/drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_32.o.cmd for /usr/src/dahdi-linux/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o

My root path includes "/sbin"
[root@pbx ~]# $PATH
-bash: /usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin: No such file or directory

CentOS 5.3

[root@pbx ~]# uname -a
Linux hostname 2.6.18-128.2.1.el5 #1 SMP Tue Jul 14 06:39:56 EDT 2009 i686 i686 i386 GNU/Linux

Thank you,
Vladimir



By: Jason Parker (jparker) 2009-07-31 14:54:39

I suspect you used `su` to become root, rather than `su -` or logging in directly.  Can you confirm?  /sbin/ is definitely in $PATH for root on CentOS systems.

By: Vladimir Mikhelson (vmikhelson) 2009-07-31 17:18:37

to qwell:

I logged in as root, I did not use "su" in any shape or form.

I copied and pasted my path in note ANOW-3241, it does have "/sbin"

Thank you,
Vladimir

By: Jason Parker (jparker) 2009-07-31 17:20:03

vmikhelson, your warning is different.  It actually isn't an issue - this is expected.  You can safely ignore it.

By: Vladimir Mikhelson (vmikhelson) 2009-07-31 17:27:37

qwell,

Thank you for clarification.

BTW, the warning message is exactly the same....  Consequences are different.

Thank you,
Vladimir

By: Dmitry Andrianov (dimas) 2009-08-01 07:23:27

More precisely, I used 'sudo bash' to become the root.

By: Jason Parker (jparker) 2009-08-04 11:09:09

This page can explain the issue much better than I can.  http://wiki.centos.org/TipsAndTricks/BecomingRoot

You should really only ever use `su -` to become root.

If it works with that method, I'd like to go ahead and close this.  Thoughts?

By: Dmitry Andrianov (dimas) 2009-08-05 18:09:07

Why so? I know lots of people who use "sudo sh", "sudo bash" or "sudo -s" (the latter is mentioned on the page you gave). This is more convenient because you do not have to remember root's password at all. I understand that this way does not modify PATH and that is why I always have to type /sbin/ifconfig instead of just ifconfig.
However I would really expect that various tools identify location of binaries they need instead of hoping these binaries are in the PATH.

Having said that, I'm personally Ok if you close this issue. But really fixing it would be better :) because one day someone else will opens something like it again.

By: Jason Parker (jparker) 2009-08-05 19:05:37

I understand your point, but I don't know if we can say that modinfo will always be in /sbin/ though.

I'll think about this a bit and see if I can come up with anything.  Do you have any additional thoughts?

By: Leif Madsen (lmadsen) 2009-09-21 10:18:19

As qwell mentioned, without the hyphen after the su, then the path is not set for the "root" user, and thus sbin will not be in the path.

I'm not sure what we're really supposed to do here as this feels like an administrator problem, and not an application level issue.

By: Leif Madsen (lmadsen) 2009-09-21 10:19:28

Closing per my last note.