From: Nigel Cunningham <ncunningham@clear.net.nz>
To: David Masover <jedi@ninja.dynup.net>
Cc: swsusp-devel <swsusp-devel@lists.sourceforge.net>,
reiserfs-list@namesys.com
Subject: Re: [Swsusp-devel] What issues are still outstanding?
Date: Thu, 18 Dec 2003 07:12:33 +1300 [thread overview]
Message-ID: <1071684752.3567.9.camel@laptop-linux> (raw)
In-Reply-To: <3FDFAC82.5090103@ninja.dynup.net>
Hi.
On Wed, 2003-12-17 at 14:08, David Masover wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Nigel Cunningham wrote:
>
> >Hi all.
> >
> >Here's another attempt at gathering into one place all the outstanding
> >issues I still need to address before 2.0...
> >
> >- ACPI events during suspend (show stopper?)
> >- SMP support (OSDL project approved)
> >- Suspend script pending changes (Bernard)
> >- Michael's NFS freezer failure
> >- Michael's occasional first-time oops
> >- Dan's suggestions for Documentation changes
> >- Slow image writing (as seen on some computers, including my desktop)
On my computer, it's bootsplash related. If I boot with splash=off, I
get the full speed. Will investigate further later.
> >Others? Please keep the above list and add to it.
> Reiser4 support? I can't be the middleman here -- I know almost nothing
> about it except that the latest reiser4 and swsusp snapshots do not like
> each other.
I'm not going to support it before 2.0, but afterwards I'll roll an
option patch for it.
Regards,
Nigel
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
prev parent reply other threads:[~2003-12-17 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1071549944.28868.9.camel@laptop-linux>
2003-12-17 1:08 ` [Swsusp-devel] What issues are still outstanding? David Masover
2003-12-17 18:12 ` Nigel Cunningham [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1071684752.3567.9.camel@laptop-linux \
--to=ncunningham@clear.net.nz \
--cc=jedi@ninja.dynup.net \
--cc=reiserfs-list@namesys.com \
--cc=swsusp-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.