Suspend2 Suspended
musicon writes "Nigel Cunningham, the creator of the Suspend2 software suspend system for Linux announced his retirement from the project in a message to the Linux Kenel Mailing List. 'Users of Suspend2 can rest assured that I will not allow the patches to suffer bitrot. I will be continuing to use them myself, and will therefore have the best of incentives to keep them up-to-date [...] I won't, however, be making any sort of concerted effort at getting them merged into the vanilla kernel [...] I don't see the point to doing anything but maintaining the patches as they stand.'"
Hi all.
I'm delighted to announce that I've accepted a call to serve a congregation in
Victoria, Australia, as a Home Missionary elder. As a result, some time in
the next month or two, I will stop working for Cyclades and make the move.
Users of Suspend2 can rest assured that I will not allow the patches to suffer
bitrot. I will be continuing to use them myself, and will therefore have the
best of incentives to keep them up-to-date.
Now for the downside: I won't, however, be making any sort of concerted effort
at getting them merged into the vanilla kernel after my move, and am not
inclined to make a big effort beforehand. Recent discussions on LKML clearly
showed that Pavel doesn't want to see them merged, and I didn't see much in
the way of other kernel developers expressing a desire contrary to Pavel's
wishes. I don't want to waste my time and effort, so I don't see the point to
doing anything but maintaining the patches as they stand.
I'd like to take this opportunity to thank Cyclades for their employment and
support of the project.
Regards,
Nigel
Of all the useful things...
Is there an alternative to it that might actually be part of the kernel eventually and not a maintained patchset?
According to TFA he is going to be some sort of Home Missionary elder. He seems to be about 200 years too late. All the missionaries left years ago. At least I thought so...hope so.
Now I don't want to be rude but what we really do need here in Victoria, Australia is good software engineers and I can think right now of a spot for him a couple of cubes across from me where his knowledge of linux kernel internals could be put to good use.
http://michaelsmith.id.au
I bet that if this software was embedded in the kernel we'd get the same devfs - udev debacle all over again...
This is something that the Linux kernel badly needs! Presently, suspend and hibernation is at least 5 years behind OS X and Windows.
It takes almost two minutes to hibernate my Thinkpad with 512 MB RAM when running Ubuntu, while Windows takes about 15 seconds. Additionally, it does crash every now and then.
Is this the only software that can force my Thinkpad R50e to fall asleep? Aren't there any others?
I've compiled 2.6.15.4 kernel and the latest version of Suspend2 is for the 2.6.15.1 version. And now I am not even sure whether the patch is coming in a next month or it isn't coming at all.
Gee, I have to turn it off all the time.
for linux users maybe, but we all should be happy for him that he gets to do thing he likes.
How much?
1. Download Ubuntu kernel sources /etc and other areas - config files galore!
2. Apply a patch-set
3. Recompile the kernel and install the kernel
4. And some other stuff I forgot - involving messing around in
Now I havent tried it with Breezy, but I am pretty sure there is no .deb/script on UbuntuForums.
Why can't the disto's simply give the user Suspend2 fully integrated in their repective kernels?
Surely not stability issues, because it was bug-free for me. Even a simple choice would be miles better than what the current situation. The distro makers have dropped the ball, let's see them pick it up.
Oh wait - I just said that Ubuntu et al. is not perfect! Goodbye, karma.
"Sure there's porn and piracy on the Web but there's probably a downside too."
While LKLM flame wars are lead between source pourists and swsusp2 proponents, linux continues to lack decent hibernation support. suspend2 is pretty much hackish, but historically that didn't prevent many features ending up in kernel, even prematurely.
They're welcome to believe whatever they want, but stop trying to push it onto everybody else. That's rude.
It's like telemarketing, except it's in your face. "Hi, is your religion letting you down? Come try mine, the Church of Jesus Christ of Latter Day Saints! What, you're an atheist? You need God in your life. Why, it says right here in the book that [ ... voice fades in the distance ...]"
Please tell them we don't need any more Mormon missionaries here in Victoria, Australia.
... please preach polygamy here too!!!!
Nooooooooooo
I guess I didn't write that email well enough - I tried to clearly say I'm not resigning, just switching full-time jobs, and as a result won't be working on Suspend as much. Given that it's already pretty mature, this won't have much effect on it's development, and I'll still be producing patches for vanilla kernels. Hope that helps. Nigel
This post's subject is misleading:
- suspend2 project is not suspended
- Nigel Cunningam will keep working on it
- it's only inclusion in vanilla kernel (mainline) which is unclear
Trying to make puns in subjects is not always a good idead...
The correct answer is that the kernel needs to do this, not userland (per suspend1), because of all the layers that need their information preserved. Having any kind of userland help doesn't work, because suddenly you've broken the "every process is equal" approach to the scheduler. But it's also not correct to throw in a huge, complicated interface (suspend2).
The correct answer is something like outlined here: " If you want my cheerfully uninformed opinion, we should toss both of them out and implement suspend3, which is based on the exec/kdump infrastructure. There's so much duplication of intent here that it's not funny."
You just have to reserve memory for a dump kernel. It's a much better trade off than making the scheduler stupid (suspend1), and keeps your kernel conceptually much simpler than a fancy kernel internal API (suspend2).
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
No discussion about freedom can proceed sensibly without the fundamental premise that if two people have the same freedom (regardless of the details) then the freedom of one ends where the freedom of another begins, and viceversa.
In other words, "total freedom" has inherent boundaries, which are the equal freedoms of others who possess the same freedom.
Saying that "total freedom" goes further and has no boundaries is either blinkered or just playing with words, because it denies that your concept of freedom is applicable to anyone else. It's not a logically consistent position.
Your position fell down simply because it does not respect the equivalence boundary.
"The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
If you need software engineers so badly, you should contemplate offering them something better than cubes. I'd take a job as a Home Missonary elder over having to sit in a cube any day. See, the problem with jobs like yours, much as with janatorial jobs, is that while we need people to do them, they suck. You sit in a little cube. You can hear conversations of everyone around you. You've got a machine spitting out 60dB of noise, and you can't do anything about it because it's the standard corporate setup, and everyone's required to have the standard corporate setup. You've probably got a firewall, that may or may not prevent you from reading your morning comics, but almost certainly does prevent you from sshing somewhere. You work long hours. You usually work on boring projects. If things go well, the rewards and recognition goes to the managers far more than it does to you. You, in contrast, are expandable, and the first to be lost in a downsizing.
Now, if you gave me an office, some privacy, some silence, and some respect, and you might get some code out of me.
See his family history page here:
http://willden.org/Histories/histories.html
All Mormon missionaries are Elders (except for rare female missionaries). Ward and Stake Missionaries are often referred to as Home Missionaries. So calling himself a "home missionary elder" isn't incorrect.
The phrase "Home Missionary" has broader meaning within Christendom, particularly in Restorationist sects (Mormonism, Seventh Day Adventism, Jehovah's Witness, Church of Christ, and many others that came out of the Restorationist movement, so their vocabularies overlap).
Mormonism, compared to the rest of Christianity, is a rather lassez-faire (though morally strict) religion (i.e., a layman's church, no paid clergy, etc.). As a result, you have a lot of regional variation within Mormon culture. For example, I much prefer the attitudes of what I call "midwest Mormons" to those of "Utah Mormons". Though I lived in Australia from 2 to 4, I can't say I got a sense at that age of how "Australian Mormons" are. In general, Mormons outside of the west coast are usually more laid back than the culture that permeates in the Church west of Utah.
Disclaimer: I was raised Mormon in the midwest (Kansas City, Missouri, mostly). I slowly dropped out of the church between 16 and 18 and now describe myself as a "hopeful, spiritual, implicitly critical, explicitly skeptical, freethinking, existentialist, humanist, agnostic, atheist, anarchist".
-=/\- Jizzbug -/\=-
He is moving because of a church calling, not because of a job. This church calling is only a call to serve (probably at the Stake level), which he apparently is accepting. It is not a job.
The Mormon church is a "lay church"; i.e., it is run by the congregation, there is no paid clergy or leadership. There are leadership roles, of course, but they're not paid is the thing. There aren't really any "clergy" roles, though. The closest thing to clergy is the Bishop, but he's more of a manager/officiator for the Ward. Each member of the congregation is the clergy (known in mainstream Christian theology as the "ecclesia" or "Body of Christ").
So, when he gets to his new city at his new church, he will probably start to look for a Real Job(tm).
-=/\- Jizzbug -/\=-
Ok, looking around, I see lots of people complaining about how suspend2 is not going to get into the kernel now. Well, if you're so intent on getting it merged, why not pick up the sword and start trying to make it happen yourselves? Don't just sit back and complain, do something about it if it means that much to ya!
Galen
In your face, and always right!
Linux has full support for suspending and hibernating; the problem isn't with Linux, the problem is with buggy ACPI implementations on laptops: most implementations simply don't conform to the ACPI specifications. They seem to have been created by hardware vendors fiddling with the implementation until it works, more or less, with the current version of Windows.
I also don't share your rosy views of suspend and hibernate on other platforms. On my Powerbook, there is no hibernate at all (although you can apparently enable it through the command line, and it hangs every now and then on restart. On the Windows laptops I have had, I have had numerous problems with suspend and hibernate as well.
Still, it is a shame that Suspend2 won't be integrated into the main kernel; when all is said and done, Suspend2 actually has worked better for me than any of the other solutions, precisely because it does not rely on ACPI or APM at all.