public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guest section DW <dwguest@win.tue.nl>
To: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.11 loses sda9
Date: Thu, 11 Oct 2001 20:22:42 +0200	[thread overview]
Message-ID: <20011011202242.A7283@win.tue.nl> (raw)
In-Reply-To: <Pine.GSO.4.21.0110110106070.21168-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0110110106070.21168-100000@weyl.math.psu.edu>; from Alexander Viro on Thu, Oct 11, 2001 at 01:07:22AM -0400

On Thu, Oct 11, 2001 at 01:07:22AM -0400, Alexander Viro wrote:

> If you have sfdisk, sfdisk /dev/sda -O /tmp/foo + mailing the result would
> make debugging the thing much simpler (that one - from the 2.4.10).

Probably you mean sfdisk -d /dev/sda > /tmp/foo or so?
My favourite tends to be sfdisk -l -uS -x /dev/sda

The -O option saves the sectors that are changed by the sfdisk call
to some file, so that a later undo is possible.

Andries

  parent reply	other threads:[~2001-10-11 18:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  5:07 2.4.11 loses sda9 Alexander Viro
2001-10-11  5:20 ` arvest
2001-10-11  5:23   ` Alexander Viro
2001-10-11  5:45     ` arvest
2001-10-11  6:08       ` Andreas Dilger
2001-10-11  6:17         ` Alexander Viro
2001-10-11 16:41         ` arvest
2001-10-11 16:46           ` Ignacio Vazquez-Abrams
2001-10-11 16:50             ` Alexander Viro
2001-10-11 17:23               ` Alexander Viro
2001-10-11 18:22 ` Guest section DW [this message]
2001-10-11 18:25   ` Alexander Viro
  -- strict thread matches above, loose matches on Subject: below --
2001-10-12  0:07 Andries.Brouwer
2001-10-11 22:11 Andries.Brouwer
2001-10-11 22:26 ` Alexander Viro
2001-10-11 20:29 Andries.Brouwer
2001-10-11 20:54 ` Alexander Viro
2001-10-11 19:07 Andries.Brouwer
2001-10-11 19:19 ` Alexander Viro
2001-10-11  4:22 arvest

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=20011011202242.A7283@win.tue.nl \
    --to=dwguest@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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