lkml.org 
[lkml]   [2005]   [Feb]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Swsusp, resume and kernel versions
    Hi!

    > First of all I must say that swsusp has progressed alot and now works
    > very reliably, at least for my configuration, and I use it a lot. Great
    > job!
    >
    > But I think there is one pretty severe issue present - even if swsusp
    > is not enabled kernel should check if there is an image in swap and
    > erase it. Today I has somewhat unpleasant experience - after suspending
    > I accidentially loaded a vendor kernel. I was in hurry and decided that
    > resume just failed for some reason so I did couple of things and left
    > the box running. In the evening I realized that I am running vendor kernel
    > and decided to reboot into my devel. version. What I did not expect is for
    > the kernel to find a valid suspend image and restore it. As you might
    > imagine messed up my disk somewhat.

    When all the vendor's kernels have swsusp, it will magically kill the
    signature. Or stick mkswap /dev/XXX in your init scripts.
    Pavel
    --
    People were complaining that M$ turns users into beta-testers...
    ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 14:10    [W:3.049 / U:0.152 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site