|| On Fri, 25 Feb 2005 07:53:01 +0100 (CET)
|| Andreas Tille <[EMAIL PROTECTED]> wrote:
>> think you can hack it to do a sync before hibernate the system and
>> then you solve this issue.
at> My complete lack of knowledge in this field might have become obvious
at> in this thread, right?
at> Do you think it is worth a bug report against hibernate?
Well, I think hibernate can avoid this kinda of problems checking if
the kernel is the same of when it did the hibernation. If this doesn't
match it can display a message and ask by cancel or continue. In case
of continue it can use mkswap to remove all swsusp2 data.
>> The problem described there isn't it but
>> the wrong use of swap when you did a suspend and try to load it with a
>> normal kernel...
>>
>> I'm wrong?
at> No, you are right and I used a wrong kernel. But as I said: IMHO it is
at> a very good idea to have a consistent FS when having a computer switched
at> off. Perhaps you will be forced to use a different kernel (rescue disc
at> whatever) and thus a sync before suspending is allways a good idea. I have
at> not enough knowledge to decide whether the sync is hibernate's or SwSusp's
at> job.
Looks like the sync is swsusp2 job but the checking before resume is
hibernate job, I think.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: [EMAIL PROTECTED] UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
you the whole house."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
