On Fri, 28 Feb 2003, Kris Kennaway wrote:
> On Fri, Feb 28, 2003 at 11:24:53AM -0800, James Satterfield wrote:
> > First off, I found SCHED_ULE to be very slow. More importantly, the two
> > times that I rebooted while running it, shutdown failed to sync the
> > disks. On the second reboot, I had
On Fri, Feb 28, 2003 at 11:24:53AM -0800, James Satterfield wrote:
> First off, I found SCHED_ULE to be very slow. More importantly, the two
> times that I rebooted while running it, shutdown failed to sync the
> disks. On the second reboot, I had just installed a new kernel. The
> results of th
From: "James Satterfield" <[EMAIL PROTECTED]>
Sent: Friday, February 28, 2003 2:24 PM
> First off, I found SCHED_ULE to be very slow. More importantly, the two
> times that I rebooted while running it, shutdown failed to sync the
> disks. On the second reboot, I had just installed a new kernel. T
First off, I found SCHED_ULE to be very slow. More importantly, the two
times that I rebooted while running it, shutdown failed to sync the
disks. On the second reboot, I had just installed a new kernel. The
results of this were ugly. /boot/kernel and /boot/kernel.old
disappeared. I've since go
Hi
Just for fun I tried out SCHED_ULE once again, using todays source.
What I got was really odd situation that my newly installed kernel
(and modules) didn't find the way to disk and loader complained
about missing kernel on next boot. The /boot/kernel directory was
simply missing and / filesyste
