> I don't believe any of this crud is necessary. My laptop uses 2.2.11
> with kupdate, I never disable it, and the disk spins down and stays
> spun down. I am convinced that any instance where a disk will not
> stay spun down can be tracked to userland bugs or userland
> misconfiguration.
And can you compile programs and leave disks spun down?
That's logic I use in bdflush-1.6:
If it ever decides to sleep disks, it sync()'s and stops bdflush. On
first read, disks are spun up and it sync()'s.
This way, you can actually _work_ [compile programs, run them, debug
them, ...] with your computer while disks are spun down. Of course, if
your kernel crashes while disks are spun down, you loose arbitrary
ammount of data. [Powerfails are not a question on notebooks.]
Pavel
-- I'm really pavel@ucw.cz. Look at http://195.113.31.123/~pavel. Pavel Hi! I'm a .signature virus! Copy me into your ~/.signature, please!- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/