> I said they were unlikely..
Are you sure?
> Basically, the only real case I can imagine where this actually
> could result in serious problems is:
> 1. write a large file that fills much of your memory because
> you're not doing anything else.
> 2. remove the file.
> 3. start applications that do _not_ do any writes to the
> filesystem, but use lots of memory in other ways..
So basically...
1. Use mkisofs to create a CD image ready for burning to a CD.
2. Discover it's slightly too large, so delete it.
3. Run the RC5 contest tool from distributed.net whilst you work
out how to reduce the size of the CD image so everything fits.
That doesn't sound particularly unlikely to me...
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
-
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/