>> > > I've just recompiled a 2.4 kernel. It hangs during startup at
>> > > "Creating /var/log/boot.msg"
>> > > I have no idea where the culprit lies here. Something missing in my
>> > > Any help would be appreciated.
>> > Can it not mount the volume that /var/log is on? That is often a
>> > 'doh' situation that may or may not pertain to your problem.
>> Currently, everything is mounted on the same partition. When I boot a
>> default kernel (SuSE), all is fine. It's this new kernel that's giving
>> me trouble.
> Yes, but check that you have the filesystem that / is compiled into
> your new kernel (ext2?); that the drivers needed to access / are
> compiled into the kernel (scsi? ata?).
He needs to RTFM the SuSE manual, they discuss it.
Proably he has compiled a module into the kernel but is still loading it.
After doing make modules_install, he should alter modules.conf, and create
a new initrd.
Personally I prefer using initrd, to compiling drivers into the kernels,
I've found it save time and trouble when you support many machines, with
slightly differing hardware.
Makes it easy to build kernels on another machine, with the real server
sans gcc(1), for security.