mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Dave Jones <davej@redhat.com>, Andrew Morton <akpm@osdl.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swsusp: documentation fixes
Date: Sun, 18 Dec 2005 18:47:52 +0100	[thread overview]
Message-ID: <20051218174752.GB9679@elf.ucw.cz> (raw)
In-Reply-To: <20051216183523.GF2821@redhat.com>

Hi!

>  > +Q: How can RH ship a swsusp-supporting kernel with modular SATA
>  > +drivers?
>  >  
>  > +A: Well, it can be done, load the drivers, then do echo into resume
>  > +file from initrd. Be sure not to mount anything, not even read-only
>  > +mount, or you are going to loose your filesystem same way Dave Jones
>  > +did.
> 
> I don't need the fame here thanks.
> I've hit a thousand other ways to corrupt my rootfs, I don't think
> it's worth documenting them.  It's arguable this whole item is needed
> to be documented, but if you feel compelled to write Red Hat specific
> documentation in the swsusp docs, feel free to note that
> 'make modules_install ; make install' just does the right thing,
> including building an initrd for you with all the right pieces.

Sorry... This entry was originally real question from akpm, and I did
reply for him. I should have rewritten in when I decided to put it
into FAQ.

This should be better:

Q: How can distributions ship a swsusp-supporting kernel with modular
disk drivers (especially SATA)?

A: Well, it can be done, load the drivers, then do echo into
/sys/power/disk/resume file from initrd. Be sure not to mount
anything, not even read-only mount, or you are going to loose your
data.
								Pavel

-- 
Thanks, Sharp!

      reply	other threads:[~2005-12-18 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-16 10:58 Pavel Machek
2005-12-16 12:22 ` Nigel Cunningham
2005-12-16 12:40   ` Pavel Machek
2005-12-16 18:35 ` Dave Jones
2005-12-18 17:47   ` Pavel Machek [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=20051218174752.GB9679@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®