Re: insmod problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 22 Oct 2004 02:31:26 +0200, Alexander Dalloz
<alexander.dalloz@xxxxxxxxxxxxxxxx> wrote:
> Am Fr, den 22.10.2004 schrieb Linn Kubler um 2:18:
> 
> > Hmm... well, this is a fresh install from CD's I downloaded from Red
> > Hat so I wouldn't expect the kernel to be modded.  Now, the default
> > up2date config excludes the kernel from updating and I'm running
> > 2.6.5-1.358, I suppose I should let up2date update the kernel as well.
> 
> I showed the path for the latest FC2 kernel. Yes, updating the kernel
> would be good: up2date-nox -u -f
> 

Yes I noticed that in the directory list, thanks.  And if I want to
update Just the kernel I'd use, 'up2date-nox -f kernel'?

> > Ok, my mistake, I checked
> > /lib/modules/2.6.5-1.358/kernel/net/ipv4/netfilter/ and the files are
> > there but they all have .ko on the end of the file names, I assume
> > that's normal.  And upon further review of modprobe -l I can see that
> > these modules are already loaded as Michael suggests.  So maybe I
> > don't need them at all in my script.
> 
> Right, in most cases needed modules are loaded automagically. Speaking
> about the iptables modules this is doing when the iptables service is
> started at boot time.
> Btw. the modules have the ".ko" suffix because you are running a 2.6
> kernel. This suffix changed from 2.4 kernel, where it was ".o".
> 
> > Linn
> 
> Alexander
> 
Thanks again,
Linn


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux