when starting up I get a message along the lines of "Warning: could not
generate /etc/modprobe.conf!". I traced it to /sbin/modules-update,
where around line 183 (baselayout-1.12.0_pre8-r2) of I see:
...
rm -f "${TMPFILE2}"
if type -p modprobe.old > /dev/null ; then
eend 1 "Warning: could not generate ${CFGFILE2}!"
else
echo "${FULLHEADER/modules.d/modprobe.d}" > "${TMPFILE2B}"
generate_config "${CONF}" "${MODDIR}" "${TMPFILE2}" 1
...
it's this "if type -p modprobe.old..." that causes the error condition.
The bash help for the "type" function seems a bit fubar:
"... If the -p option is used, type either returns the
name of the disk file that would be executed if name were speci-
fied as a command name, or nothing if ``type -t name'' would not
return file."
so essentially, "type -p /etc/modprobe.old" is returning nothing, which
makes sense since there is no /etc/modprobe.old,
only /etc/modprobe.conf.old which is also created by modules-update:
mv -f "${CFGFILE2}" "${CFGFILE2}.old"
which would expand as
mv -f /etc/modprobe.conf /etc/modprobe.conf.old
and NOT
mv -f /etc/modprobe.conf /etc/modprobe.old
... So I commented out
if type -p modprobe.old > /dev/null ; then
eend 1 "Warning: could not generate ${CFGFILE2}!"
and I can now generate modprobe.conf properly, but is this the right way
to go? Should the modules-update be referencing both
/etc/modprobe.old AND /etc/modprobe.conf.old? Or are there (a lot of)
typos in there?
I don't know where to go from here, I could just leave modules-update
commented, but then I have to modify it every time baselayout is
updated...
Any help appreciated,
TIA,
--
Iain Buchanan <[EMAIL PROTECTED]>
--
gentoo-user@gentoo.org mailing list
