On Wed, 14 Jun 2000, Jacques Richer wrote:
>
> 1) If this were a user space daemon, how about monitoring free space on volume
> with a user defined threshold. A drop belox threshold could Grim File Reap the
> least recently used image file. This would only cause a problem with "df"
> returning not-exacly-as-they-look disk usage numbers.
Not sure I like that, TBH. We shouldn't go filling up the user's disk with
caches unless we really need to - I'd much rather use the free swap space
for this.
> 2) By putting the floppy disk drive handling code in user space, we can steal
> ^H^H^H^H^H borrow large pieces of the mtools libs and avoid reinventing the
> wheel. At least that code is stable.
I suspect the kernel's floppy handling code is stable too ;-)
All we really need to do is add a couple of hooks here and there. Get the
floppy driver caching as aggressively as possible into VM, and add some
feedback mechanism to alert a UI daemon to tell the user off if they pull
the disk out while Linux is still using it, and to umount the disk if it's
been removed and we aren't still syncing it.
James.
-
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/
This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:32 EST