Mike McCarty wrote:
$ diff -s file1 file2
Files file1 and file2 are identical
Identical? Try this:
du file1 file2
and you will see that one of them has not allocated disk blocks,
it is sparse (has holes).
IIRC sparse files are unacceptable for swap (the recent swap files
are as fast as
I've seen various recommendations for adding swap files after
system creation, and it occurs to me that the standard technique
may not be the most efficient. I realize that one rarely creates
swap files, but nonetheless on occasion one needs to precreate
some file or other, then do something to
Mike McCarty wrote, On 03/27/2009 04:01 PM:
I've seen various recommendations for adding swap files after
system creation, and it occurs to me that the standard technique
may not be the most efficient. I realize that one rarely creates
swap files, but nonetheless on occasion one needs to
On 27Mar2009 14:01, Mike McCarty mike.mcca...@sbcglobal.net wrote:
I've seen various recommendations for adding swap files after
system creation, and it occurs to me that the standard technique
may not be the most efficient. I realize that one rarely creates
swap files, but nonetheless on
Todd Denniston wrote:
This brings up a question for me...
If using the first method, while in use or during the mkswap command,
does the bits written to the file end up at the same physical locations
as the 0s they are replacing?
Yes - you are saving back to the same file. Not like a work
