Putting FreeBSD to sleep?

[Adrian Pavone]

Adrian Pavone wrote:

> Graham Bentley wrote:
>
> >Can anyone post some good pointers for setting
> >up ACPI or APM so that I get automatic susepend
> >afer x mins of inactivity and woken up on LAN
> >request ?
> >
> >(in particular shut down disc / slow or shut
> >down psu fan - its the noise I am concerned
> >about)
> >
> >I have looked at posts on rc.suspend/resume
> >for various power saving issues on laptops
> >but cant find and good resources on how to
> >do the above. Surely this must have been
> >done before by someone with a remote server
> >in a secret location :)
> >
> >Thanks in advance for any advice :)
> >
> >_______________________________________________
> >freebsd-questions at freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> >To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe at freebsd.org"
> >
> >
> >  >
> Wake on LAN is a feature that you will have to enable in your BIOS, if
> it is available. It could not be affected by ACPI/APM (or any other
> Operating System feature) once the computer is no longer powered up. In
> regards to what you need to suspend after x mins, I am unsure.
>
> Regards,
> Adrian
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe at freebsd.org"
>
>
 From http://www.freebsd.org/releases/6.0R/errata.html

(2005/11/5) Distribution of 6.0-RELEASE contains CHECKSUM.MD5 and 
CHECKSUM.SHA256 files for protecting the integrity of data. However, 
these files in 6.0-RELEASE erroneously include checksums for the 
checksum files themselves. Although the checksums look like wrong, they 
can be safely ignored because a checksum for the checksum file never 
corresponds to one in the file. This problem will be fixed in the next 
releases.

Well, looks like it was 6.0 that I was referring to, however, if you 
have had the same issue with 6.1 from 2 different locations (unless your 
connection and TCP/IP protocol is dodgy), I would think that maybe they 
did not resolve this issue.

Regards,
Adrian