On Wed, Jun 28, 2006 at 07:28:38AM -0400, Rahul Karnik wrote:
> This is something I don't understand. Why can you not submit patches
> that simply do things like "change method for writing image" and
Because the systematic answer of the suspend maintainer to that is
"you should write the image in userspace", to follow your example.
> reduce the difference between suspend2 and mainline? It may be more
> work, but I think you will find that incremental changes are a lot
> easier for people to review and merge.
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.
OG.
-
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]
