file handles in checkpt and sys_checkpoint

[Matthew Dillon]

:Hi, friends.  I love DragonFly, I do.  Well done.  Question about
:checkpointing.
:
:There's a bit of a catch-22 when using sys_checkpoint().  The file
:descriptor which is passed into sys_checkpoint is serialized along
:with everything else.  So, when I go to resume, I have to be sure
:the file resides at the same path where it was created.
:
:This poses a problem for compressing the file, which I had been
:hoping to do.  Any one know of a way to keep the fd from being
:serialized?  The only way I can think of to get around this is to
:alter elf_getfiles in the kernel to ignore files which can't be
:reloaded.
:
:_why

    Ok, I believe I fixed it in HEAD.

    It turns out that I had already fixed the 'checkpoint file chaining'
    problem long ago, yahhh!  But I did have to add some code to have
    it flag the checkpoint descriptor itself so it could properly associate
    the descriptor used to restore the checkpoint instead of trying to
    lookup the original checkpoint file.

    I also got rid of the debugging kprintfs to the console on checkpoint
    restore.

					-Matt
					Matthew Dillon 
					<dillon at backplane.com>