1. Generate disk writes. Compiling the kernel or copying some files
is enough.
2. Wait until the writes should have been flushed. In the old days
this was always 30 seconds because update called flush then.
3. Issue 'sync' in shell, disk activity ensues. After a kernel compile
there is a _lot_, even 6 hours after it finished.
The 2.1 kernels has a kflushd to replace the bdflush program, and when
the old bdflush program is run now it terminates at once:
...
fork() = 631
[pid 630] fork() = 632
[pid 631] --- SIGSEGV (Segmentation fault) ---
[pid 630] --- SIGCHLD (Child exited) ---
[pid 630] _exit(0) = ?
--- SIGSEGV (Segmentation fault) ---
The bdflush program also served as update(8). kflushd does not seem
to do this. Is it supposed to? Do we need update again?
Nicolai
-
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/