Hi!
> Pavel wants everything in userspace. Nigel wants everything but the
> chrome in kernelspace. Other kernels maintainers are split on the
> issue, or don't care apart from "it should have been working for
> years, damnit". Andrew plainly said he doesn't know what's best, and
> Linus seems to be very careful not to talk about it.
>
> What should have happened is that suspend2 should have been merged
> years ago, and then now transiting more of it to userspace or not
> could be experimented, starting on a decently working base. Pavel's
> NIH-ing prevented that though.
>
> In any case, don't use software suspend on a machine with data you
> care about, and especially not uswsusp. Side effect of userspace code
> is that nobody from outside the project reviews it, and it's way too
> young to have any kind of confidence in it.
Well, swsusp is *way* better reviewed than suspend2, because it is
<10% of code size, and it is in kernel already (plus Rafael did the
reviews/rewriting).
Your point about uswsusp is "interesting", but notice that noone ever
reviewed suspend2, either. So... if you care about your data, swsusp
is currently the _safest_ way to go. (It may not have the _nicest_
progress indication :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
