[EMAIL PROTECTED](Debian Bug Tracking System) 24.10.05 14:03 >> To make this work, no further access to the hardware clock may >> occure. So i renamed K25hwclock.sh to _K25hwclock.sh=20 >> So ACPI wake up worked flawlessly without since months! >> But one package restores the K25hwclock.sh links, making=20 >> wake up failing! >> Anyway: >> What's the better way?
>From the update-rc.d man page: > If any files /etc/rcrunlevel.d/[SK]??name already exist then >update-rc.d does nothing. This is so that the system administrator >can rearange the links, provided that they leave at least one link >remaining, without having their configuration overwritten. >In other words, you want to still have a K25hwclock.sh, just have it >do nothing. (Which you have now done.) Thanks for the quote, but: It would be better if the hwclock.sh would take more care about the other registers of the clock. In ACPI the alarm clock can be read back. I don't know, but wouldn't it be possible to save old alarm clock resycn clock restore alaram time? OTHO there are hacks which intentionally(!) turns the hwclock to the wrong time, in the case the alarm time could only be set in BIOS... Maybe that's a point for the todo list? "Take care of alarm settings" ? Rainer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
