as i did look closer to this problem i found out, that it will not fix the problem at all. when i did supend my computer and it didn't resume properly i got an error message that S10checkroot wasn't able to activate the swap device. well. this is no big deal since S35mountall.sh will again activate swap. so the only problem is, that if some one uses a swapfile to save the software suspend signature, which is not on root, the S31hibernate will not be able to clean it, due to the fact that only the root device is mounted at this time. so i believe that S31hibernate should be split up into two scripts. one is cleaning the swap device before S35mountall.sh (maybe better before S10checkroot) and the second one will be called after S35mountall.sh to get any software suspend signature file out of the way.

so hope this is helpful!

greetings


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to