On Thu, Jun 21, 2001 at 06:07:01PM +0200, Jamie Lokier wrote:
> Pavel Machek wrote:
> > > Isn't this why noflushd exists or is this an evil thing that shouldn't
> > > ever be used and will eventually eat my disks for breakfast?
> >
> > It would eat your flash for breakfast. You know, flash memories have
> > no spinning parts, so there's nothing to spin down.
>
> Btw Pavel, does noflushd work with 2.4.4? The noflushd version 2.4 I
> tried said it couldn't find some kernel process (kflushd? I don't
> remember) and that I should use bdflush. The manual says that's
> appropriate for older kernels, but not 2.4.4 surely.
That's because of my favourite change from the 2.4.3 patch:
- strcpy(tsk->comm, "kupdate");
+ strcpy(tsk->comm, "kupdated");
noflushd 2.4 fixed this issue in the daemon itself, but I had forgotten about
the generic startup skript. (Rpms and debs run their customized versions.)
Either the current version from CVS, or
ed /your/init.d/location/noflushd << EOF
%s/kupdate/kupdated/g
w
q
EOF
should get you going.
Regards,
Daniel.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
