public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Samium Gromoff <deepfire@ibe.miee.ru>
Cc: pavel@suse.cz, linux-kernel@vger.kernel.org, rob@landley.net
Subject: Re: Patrick's Test9 suspend code.
Date: Wed, 19 Nov 2003 20:06:56 +0100	[thread overview]
Message-ID: <20031119190656.GD6293@openzaurus.ucw.cz> (raw)
In-Reply-To: <87fzgkwlci.wl@drakkar.ibe.miee.ru>

Hi!

> > A) Any scheme we come up with there will be a way the user can do something 
> > stupid enough to break it.  (Put the swap partition on a ramdisk living on 
> > the video card, or on a device require an initrd to load the driver to 
> > access...)
> > 
> > B) A heuristic that looks at the mounted block devices for things that smell 
> > like a resume partition would actually be more robust in that case.
> 
> Really, what i think here is appropriate is a more fundamental approach.
> 
> We should reserve a new partition type in addition to three already
> existing, namely "linux"==0x83, "linux swap"==0x82 and "linux lvm"==0x8e.
> 
> And call it something like "linux suspend".
> And initialize it, if needed (i presume to write a signature etc), with
> something like "mksusp".

Yes and we should create separate partition type for root filesystem
and have separate mkfs.ext2.root.

NOT!

I see no advantages in mksusp; it only means you need to re-fdisk
your machine. Bad idea, and its way too late for 2.6 anyway.
-- 
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...


  reply	other threads:[~2003-11-20 13:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 13:15 Patrick's Test9 suspend code Samium Gromoff
2003-11-19 19:06 ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-20 17:26 Shaheed
2003-11-20 19:39 ` Rob Landley
2003-11-20 22:33   ` Shaheed
2003-11-20 22:41     ` Nigel Cunningham
2003-11-20 23:02       ` Shaheed
2003-11-21  6:46       ` Rob Landley
2003-11-21 20:09         ` Nigel Cunningham
2003-11-21  0:06 ` Pavel Machek
2003-11-09 10:04 Rob Landley
2003-11-13 13:08 ` Pavel Machek
2003-11-16  0:30   ` Rob Landley
2003-11-16 13:13     ` Pavel Machek
2003-11-17  2:38       ` Rob Landley
2003-11-17  8:42         ` Pavel Machek
2003-11-17 16:45         ` Patrick Mochel
2003-11-17 21:11           ` Rob Landley
2003-11-18 12:02           ` Rob Landley
2003-11-18 18:22             ` Pavel Machek
2003-11-18 22:12               ` Rob Landley
2003-11-18 23:21                 ` Pavel Machek
2003-11-19  5:26                   ` Rob Landley
2003-11-19  9:18                     ` Pavel Machek
2003-11-19  9:41                       ` Rob Landley

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=20031119190656.GD6293@openzaurus.ucw.cz \
    --to=pavel@suse.cz \
    --cc=deepfire@ibe.miee.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox