David Schultz wrote: > Thus spake Terry Lambert <[EMAIL PROTECTED]>: > > You don't have to dump on your swap. It's just convenient to do. > > You can actually dump on any raw partition which is large enough. > > > > If FreeBSD intrinsically handled "suspend to disk", then you would > > need something seperate from swap, anyway. > > But in the "suspend to disk" case, you can assume you have a > non-braindead kernel. Couldn't you just allocate the blocks > in the filesystem and write your image? Sure, it would be a > bit slower than using a dedicated partition, but nobody said > "suspend to disk" is a good idea anyway.
No, because in order to resume, you'd need to be running, and if you were running, then you couldn't resume anything that conflicted with the default boot state (e.g. keenel modules that were loaded post-boot). Suspend-to-disk resumption also requires that any state that you had outstanding at the time of the suspend is resumed afterward; this generally includes network state, since sockets don't get a "keepalive" unless you ask for it, and they generally stay "open" indefinitely, except for servers that have explicit idle timeouts (in which case, the client must expect to reestablish the connection, and you are still OK). The only place this really fails is "modern" UNIX kernels that attempt to treat TIME_WAIT incorrectly by setting a timer, in violation of the protocol specification. OH... and FWIW, the absolutely *best* way to install a new system is to "resume from disk" from a distribution image; you are basically running in about 6 seconds. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
