linux-kernel - Re: Suspend2 is getting a new name.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200707031534.06350.rjw@sisk.pl>
Date:	Tue, 3 Jul 2007 15:34:05 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Nigel Cunningham <nigel@...el.suspend2.net>
Cc:	Bill Davidsen <davidsen@....com>, nigel@...pend2.net,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Suspend2 is getting a new name.

Hi,

On Tuesday, 3 July 2007 00:08, Nigel Cunningham wrote:
> Hi.
> 
> On Tuesday 03 July 2007 05:18:39 Bill Davidsen wrote:
> > Nigel Cunningham wrote:
> > > Hi all.
> > > 
> > > Suspend2's name is changing to "TuxOnIce".
> > > 
> > > This is for a couple of reasons:
> > > 
> > > In recent discussions on LKML, the point was made that the word "Suspend" 
> is 
> > > confusing. It is used to refer to both suspending to disk and suspending 
> to 
> > > ram. Life will be simpler if we more clearly differentiate the two.
> > > 
> > > The name Suspend2 came about a couple of years ago when we made the 2.0 
> > > release and started self-hosting. If we ever get to a 3.0 release, the 
> name 
> > > could become even more confusing! (And there are already problems with 
> people 
> > > confusing the name with swsusp and talking about uswsusp as version 3!).
> > > 
> > > http://www.suspend2.net is still working at the moment, but we'll shift to 
> > > http://www.tuxonice.net over the next while. The wiki and bugzilla are 
> > > already done; email will remain on suspend2.net for a little while and git 
> > > trees will be renamed at the time of the next stable release.
> > > 
> > I guess this is "good news, bad news" time. The good news is that the 
> > "suspend with working resume" project is still active, the bad news is 
> > that making provisions for long term out of mainline operation sounds as 
> > if you have no hope of getting this code into the mainline kernel. :-(
> 
> Let's not turn this into a flamewar, please. This is just a name change, 
> nothing more.
> 
> As far as I know, the desire on Rafael's part and mine is still to get at 
> least some of the functionality merged. The only reason this isn't happening 
> yet is that we're both busy with other aspects of the work. Rafael is 
> focussing on infrastructure issues, I'm focussing on minimising the diff and 
> finishing off cleaning up and adding comments to functions.

That's correct, thanks for saying this!

My first target is to introduce a framework allowing drivers to have different
callbacks for hibernation and suspend.   Unfortunately, that turned out to
require quite a lot of work - and time - to do.

Greetings,
Rafael


-- 
"Premature optimization is the root of all evil." - Donald Knuth
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/