Daniel Hammer wrote:
>
> BS"D
>
> excellent question, I have the same problem and would appreciate
> any solution! Best,
The only thing I've found to work is building IDE into the
kernel, not using the module.
After I got autodetect/boot support in the config,
It tried to autodetect BEFORE the
Hi,
has anyone had any experiences setting up a small cluster (4/5 machines) to
speed up compiling?
I have just installed a MOSIX cluster on two machines (didn't tune it very
much though) and it really didn't make any difference. So before going
through every possible documentation (or switch
Did you rpm -i or rpm -F your kernel?
I have seen this problem when you rpm -F which then overwrites the kernel
that you systems booted with. When then attempting to make a new ramdisk
with mkinitrd, this message is returned. Try doing an rpm -i on the
kernel-2.4.0-0.37.i686 which should still ha
BS"D
It may sound stupid, but when I once found myself in the same maze as Jens-Ulrik,
the system sent me also a "kernel too big" message. Found no intelligent way to
get out of this. After compiling an own kernel with the new resources it stopped
also complaining about loopback devices.
Maybe
