Morning all ...
Just recently, I upgraded from 3.4 to 4.0, and the process, all in
all, was relatively painless. I got hit by the 'lack of memory' on my
part about the 'make -k' option mostly ...
... but, one thing did hit me that I think could be fixed is the
modules. I forgot that I was using the procfs module, so, of course, when
I rebooted, it crashed because it was still using the old 3.4 one.
I'm about to upgrade my bosses computer, and looked through
modules and there is an if_xl.ko module ... right now, I have xl compiled
in by default, but getting that out of the kernel (and as much else) out
of the kernel config would be nice ... but, of course, were I to do that
now, the ethernet would be down, which means I couldn't get at the nfs
mounted /usr/{src,obj} directory to install the module ...
When we do a 'make install' on the kernel, it automatically copies
/kernel to /kernel.old, and copies the new kernel in ... is there no way
of extending this to the modules?
The one thing I was thinking might be to have it so that if you
'load kernel.old' (ie. kernel didn't boot properly, so you have to
revert), when it loads its modules, it loads <module>.old to go along with
it...
Basically, the modules are tied to the kernel, so is there any way
of having them install along with the kernel ... ?
Thanks...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
