aboutsummaryrefslogtreecommitdiff
path: root/init
diff options
context:
space:
mode:
authorbug1 <bug1@69ca8d6d-28ef-0310-b511-8ec308f3f277>2004-08-11 02:30:30 +0000
committerbug1 <bug1@69ca8d6d-28ef-0310-b511-8ec308f3f277>2004-08-11 02:30:30 +0000
commit6f8b1ccbf9ac6e4a563b1d4047f16c103c4689f7 (patch)
treeed5e9b604b09f7046c19f55686cd80f5a695b1a2 /init
parent3127105cd92865c0fc77ad74b0f10c87da18f744 (diff)
downloadbusybox-w32-6f8b1ccbf9ac6e4a563b1d4047f16c103c4689f7.tar.gz
busybox-w32-6f8b1ccbf9ac6e4a563b1d4047f16c103c4689f7.tar.bz2
busybox-w32-6f8b1ccbf9ac6e4a563b1d4047f16c103c4689f7.zip
Willian Barsse wrote
"There seems to be a slight problem with the "mod_strcmp" function in modprobe.c, it scans for the first occurence of the module name in the "mod_path" variable and expects it to be the last path element. ie /lib/modules/2.4.22-debug/kernel/fs/vfat in my example. The comparison will always fail if mod_path contains another substring matching the module name." Robert McQueen wrote "Although William Barsse's patch fixed mod_strcmp for 2.4 kernels, there was a remaining problem which prevented it from working for me. I've just tracked it down - when you enable kernel 2.6 module support it hard-wired the extension to .ko instead of checking at runtime like the other places where 2.4 differs from 2.6. The attached patch fixes this for me." git-svn-id: svn://busybox.net/trunk/busybox@9082 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions