Timothy Murphy wrote:
Philip Prindeville wrote:
I installed the latest FC3 kernel update, but I'm seeing:
[root@media ~]# ls -ltr /lib/modules/2.6.12-1.1372_FC3/
total 924
lrwxrwxrwx 1 root root 49 Jul 20 16:35 build ->
../../../usr/src/kernels/2.6.12-1.1372_FC3-x86_64
lrwxrwxrwx 1 root root 5 Jul 20 16:35 source -> build
drwxr-xr-x 9 root root 4096 Jul 20 16:35 kernel
-rw-r--r-- 1 root root 268793 Jul 20 16:35 modules.usbmap
-rw-r--r-- 1 root root 84243 Jul 20 16:35 modules.symbols
-rw-r--r-- 1 root root 163080 Jul 20 16:35 modules.pcimap
-rw-r--r-- 1 root root 2237 Jul 20 16:35 modules.isapnpmap
-rw-r--r-- 1 root root 357 Jul 20 16:35 modules.inputmap
-rw-r--r-- 1 root root 813 Jul 20 16:35 modules.ieee1394map
-rw-r--r-- 1 root root 193484 Jul 20 16:35 modules.dep
-rw-r--r-- 1 root root 69 Jul 20 16:35 modules.ccwmap
-rw-r--r-- 1 root root 184451 Jul 20 16:35 modules.alias
[root@media ~]#
i.e. "build" should have been copied out as a deep copy, rather than
a shallow copy in the packaging.
Do you mean it is a symbolic link?
Or does "shallow copy" have some other meaning?
In any case, "build" is always a symbolic link in my experience.
Sorry, "shallow copy" is a term used by C++ programmers. In this
context, it means a symbolic link.
When I updated to 2.6.11-1.35_FC3, it *wasn't* a symbolic link:
[root@media ~]# ls -ltr /lib/modules/2.6.11-1.35_FC3/
total 904
drwxr-xr-x 9 root root 4096 Jun 27 23:28 kernel
drwxr-xr-x 18 root root 4096 Jul 11 19:54 build
-rw-r--r-- 1 root root 256123 Jul 16 21:28 modules.usbmap
-rw-r--r-- 1 root root 83332 Jul 16 21:28 modules.symbols
-rw-r--r-- 1 root root 159258 Jul 16 21:28 modules.pcimap
-rw-r--r-- 1 root root 235 Jul 16 21:28 modules.isapnpmap
-rw-r--r-- 1 root root 357 Jul 16 21:28 modules.inputmap
-rw-r--r-- 1 root root 517 Jul 16 21:28 modules.ieee1394map
-rw-r--r-- 1 root root 186596 Jul 16 21:28 modules.dep
-rw-r--r-- 1 root root 69 Jul 16 21:28 modules.ccwmap
-rw-r--r-- 1 root root 179441 Jul 16 21:28 modules.alias
[root@media ~]#
