On Sun 2006-07-09 10:18:58, Bojan Smojver wrote:
> On Sun, 2006-07-09 at 01:53 +0200, Pavel Machek wrote:
>
> > swsusp/uswsusp share 75% or so of code, and we can't really drop
> > swsusp soon, because that would break existing setups. Warning
> > year-or-so ahead is needed to do such big changes. Plus you are quite
> > right n that "heavy to setup" thing.
>
> Ah, right. Thanks for clearing that up.
>
> So, the plan is that in about a year or so there won't be any completely
> in-kernel suspend implementations, only uswsusp?
No, that was not what I tried to say. Just now, swsusp looks pretty
small (~1000 lines), way too many people use it, and it is too handy
for debugging. So I'm not trying to kill it just now. When klibc gets
into mainline, and pretty much everyone switches to uswsusp, yes, it
will be possible to remove swsusp. For now I'm just trying to keep it
stable and not add features to it, so it is as easy to maintain as
possible.
First sign of swsusp going out is going to be /sys/power/resume
disappearing. It is really badly documented/dangerous hack, and if
your distro uses initrd, anyway.. well you should probably just use
swsusp. It would be nice to remove it in year or two.
I wanted to point out that delay between "okay, I want this gone" and
the code disappearing from kernel tarball is about a year.
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]
