From: Dave Jones <davej@suse.de>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: /proc/partitions broken in 2.5.23
Date: Wed, 19 Jun 2002 13:44:02 +0200 [thread overview]
Message-ID: <20020619134402.B29373@suse.de> (raw)
In-Reply-To: <20020619113233.GA15730@win.tue.nl>; from aebr@win.tue.nl on Wed, Jun 19, 2002 at 01:32:33PM +0200
On Wed, Jun 19, 2002 at 01:32:33PM +0200, Andries Brouwer wrote:
> > 22 0 1515870810 hdc
> > 22 64 1515870810 hdd
> > 3 0 29316672 hda
> > 3 1 117400 hda1
> > 3 2 1 hda2
> > 3 5 999904 hda5
> > 3 6 1499872 hda6
> > 3 7 683392 hda7
> > 3 8 26015944 hda8
> > 3 64 1515870810 hdb
> I changed something here a few weeks ago. The idea was to avoid
> listing partitions of size 0 but do list full devices, regardless
> of size. Especially in case of removable media that is useful.
> For example, a
> blockdev --rereadpt /dev/sda
> might show that there is something there now.
Seems it doesn't handle the case of 'no media in drive' too well.
hdc - cdrom, hdd - zip drive, hdb - no device there.
hda2 is odd looking too showing a #blocks of '1', when
it's actually..
Device Boot Start End Blocks Id System
/dev/hda2 234 58168 29199240 5 Extended
Oddly, on another machine, it detects an LS-120 drive with
no media correctly..
22 64 0 hdd
(but still gets the 'no device' case wrong on that box).
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-06-19 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 9:02 /proc/partitions broken in 2.5.23 Dave Jones
2002-06-19 11:32 ` Andries Brouwer
2002-06-19 11:44 ` Dave Jones [this message]
2002-06-19 12:51 ` Andries Brouwer
2002-06-19 13:16 ` Dave Jones
2002-06-19 17:18 ` Wayne Whitney
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 23:21 Andries.Brouwer
2002-06-20 23:34 ` Dave Jones
2002-06-20 23:42 ` Anders Gustafsson
[not found] <641481775@toto.iv>
2002-06-26 3:22 ` Peter Chubb
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=20020619134402.B29373@suse.de \
--to=davej@suse.de \
--cc=aebr@win.tue.nl \
--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