On Tue, 04 Apr 2006 15:04:09 +1200 Christopher Sawtell wrote: > On Tuesday 04 April 2006 14:21, Nick Rout wrote: > > On Tue, 04 Apr 2006 14:08:00 +1200 > > > > Christopher Sawtell wrote: > > > > > looks like a kernel recompile. > > > > > > I tend to disagree with that idea. > > > > why? > Simply because it is the rm command complaining about a whole lot of > missing files. That is not a kernel function. Also I'd want to find out > why it's doing that before I spent a fair amount of time configuring a new > kernel. > > A quick fix would be to attach the -f flag to the rm command in question. > That will quite definitively shut it up. > > Also I've never seen a kernel do that before.
according to the thread I pointed to it is specifically a problem with genkernel generated kernels. Now genkernel also creates an initrd, which is a temporary root directory that gets transferred to a ram disk and is used for the initial bootup before the real root file system is mounted. The offending command may be in there. The command is related to the /sys file system, i suspect it is trying to clear out /sys before activating udev. So the first thing I would try is just booting the kororaa kernel without the initrd. I will post instructions on that later, which Yuri wil be able to follow with no problem. I have found from the kororaa install on my laptop that although a genkerneled kernel generates an initrd, it doesn't seem to need it to boot. -- Nick Rout <[EMAIL PROTECTED]>
