> I don't see how I could mess anything up other than an aborted boot
> because of the new kernel failing.
It's apparently pretty easy to mess up a build. I must get at
least two tickets a day where $USER completely overwrote the current
kernel and current module tree.
> The question still remains is why did I have to do a depmod.
I don't think it was necessary. I think something else
contributed to the problem, that depmod happened to fix. I've *never* had
to do that, even on the most perverted of kernel builds.
--
- Isaiah
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
