From: Robby Workman on 23 Apr 2010 11:57 On 2010-04-18, Peter Chant <peteRE(a)MpeteOzilla.Vco.ukE> wrote: > Any thoughts: > > when nfsd gets a request for a directory mount it fails and this shows up in > /var/log/messages > > Apr 18 22:56:38 phoenix modprobe: FATAL: Error inserting nfsd > (/lib/modules/2.6.33.1/kernel/fs/nfsd/nfsd.ko): Invalid module format > > This is the standard kernel that came with Slackware64-current on 31 March. This should be fixed as of the Tue Apr 20 14:45:24 UTC 2010 update. -RW
From: Grant on 21 Apr 2010 16:40 On Wed, 21 Apr 2010 07:17:33 +0100, Peter Chant <peteRE(a)MpeteOzilla.Vco.ukE> wrote: >Grant wrote: > >>>BTW - you are wrong, it is getting longer. Back in the day my shiny new >>>K6-233 could compile a kernel in 4 minutes flat! >> >> Oh well, faulty memory? Unless you were on 2.0 or 2.2 back then? I was >> tracking 2.3.latest then 2.4.latest back then. Think they took longer. > >That was 12 or 13 years back. Can't remember, one of those two, probably >the former. Kernel was a lot smaller then. Small enough I could remember >all the important settings (to me) in a kernel config and set the options in >about 10 mins - without copying the Slackware config and tweeking. Can't do >that now. You can, make defconfig, make menuconfig, turn off the experimental options on the first page simplifies going through the rest (at a cost of some blank menu screens these days). I only do this for new machines. Old machines have config lying around. Be cause I put my configs up on web site, I have a starting point for slack reinstalls on the existing machines. I don't find it takes too long, most options get turned off. The firewall takes longer as it has netfilter to setup too, but reconfigure from scratch is rare. And then one carries a good config through to new kernels, adding or rejecting any new kernel features. Grant. -- http://bugs.id.au/
First
|
Prev
|
Pages: 1 2 Prev: Assigning USB devices fixed mountable details (udev rules?) Next: minor tcl/tk breakage |