Hello,
What can I do when attempting to run depmod with these options:
-Ae -b base -F System.map
to prevent depmod from appending the following path:
lib/modules/2.6.18-53.1.14.el5/modules.dep.temp
to the specified base? I am specifying a base as:
-b ./lib/modules/2.6.16.23-custom
So depmod errors/fails with: FATAL: Could not open ./lib/modules/2.6.16.23-custom/lib/modules/2.6.18-53.1.14.el5/modules.dep.temp
btw, '/lib/modules/2.6.18-53.1.14.el5' belongs to the native system that is running on my host
Why is depmod using that "system" path?
Thank you. -AZ
On Fri, Apr 4, 2008 at 3:35 PM, Artie Ziff artie.ziff@gmail.com wrote:
Hello,
What can I do when attempting to run depmod with these options:
-Ae -b base -F System.map
to prevent depmod from appending the following path:
lib/modules/2.6.18-53.1.14.el5/modules.dep.temp
to the specified base? I am specifying a base as:
-b ./lib/modules/2.6.16.23-custom
So depmod errors/fails with: FATAL: Could not open ./lib/modules/2.6.16.23-custom/lib/modules/2.6.18-53.1.14.el5/modules.dep.temp
btw, '/lib/modules/2.6.18-53.1.14.el5' belongs to the native system that is running on my host
Why is depmod using that "system" path?
Do you want to run depmod against /lib/modules/2.6.16.23-custom ? Then,
depmod -a /lib/modules/2.6.16.23-custom
should do. If you add '-b foo', it will prepend the 'foo' to your default version (`uname -r`) which is what you are seeing.
Akemi
Do you want to run depmod against /lib/modules/2.6.16.23-custom ? Then,
depmod -a /lib/modules/2.6.16.23-custom
should do. If you add '-b foo', it will prepend the 'foo' to your default version (`uname -r`) which is what you are seeing.
Thank you for your time to respond. Yes I am attempting to build a custom kernel (and run depmod on the associated root file system location. I wonder if I am supposed to chroot into the root filesystem which is being constructed. I think not... as that is why the depmod options exist, correct; to build in another "./lib" than the native host's /lib at root "/"?
I had stated that I was experiencing an issue of "append" whereas (if I am not misinterpreting your answer) you offer an explanation for a prepend of pathname strings. That's cool. I am grateful for the dialog.
Here is my experience restated:
The native file system location "/lib/modules/2.6.18-53.1.14.el5" is being "APPENDED" to the base path I set with switch -b.
That is, I say the dir containing the file "modules.dep.temp" is in this directory:
./lib/modules/2.6.16.23-custom
which is /home/User/WorkDir/images/current/lib/modules/2.6.16.23-custom/lib/modules/2.6.18-53.1.14.el5/modules.dep.temp
So, you can see that:
/lib/modules/2.6.18-53.1.14.el5
is being appended to:
./lib/modules/2.6.16.23-custom
Thanks in advance for any advice.
Cheers, AZ
PS: The version, 2.6.18-53.1.14.el5, is clearly my build host. So that is coming from running (native) kernel, uname -r:
$ uname -r 2.6.18-53.1.14.el5
Hello,
I close this issue as PEBKAC. :)
I misinterpreted the -b argument to mean the special root file system's "modules" directory but instead I only needed to specify the root "/" of the target file system. depmod is happy. Thanks!
I commend your honesty and candor, Artie. Few people in these public fora ever bother to admit they actually LEARNED something! :-)
--Carol Anne
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Artie Ziff Sent: Monday, April 07, 2008 3:20 PM To: CentOS mailing list Subject: Re: [CentOS] depmod madness
Hello,
I close this issue as PEBKAC. :)
I misinterpreted the -b argument to mean the special root file system's "modules" directory but instead I only needed to specify the root "/" of the target file system. depmod is happy. Thanks!
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Akemi Yagi -
Artie Ziff -
Carol Anne Ogdin