From: Andries.Brouwer@cwi.nl
To: marcelo@connectiva.com.br, pasky@pasky.ji.cz
Cc: Andries.Brouwer@cwi.nl, hch@lst.de, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, viro@math.psu.edu
Subject: Re: [PATCH] [2.4.19] Extended /proc/partitions
Date: Sat, 2 Nov 2002 20:19:22 +0100 (MET) [thread overview]
Message-ID: <UTC200211021919.gA2JJMk20461.aeb@smtp.cwi.nl> (raw)
From pasky@machine.sinus.cz Sat Nov 2 18:18:06 2002
From: Petr Baudis <pasky@pasky.ji.cz>
This patch extends contents of /proc/partitions by starting
offset of each partition. This can be terribly useful if you
by some mistake over-dd'd the partition table on a disk,
but the system is still up. I know that you can also
dig this out by some ioctl()s, but this can make life a lot easier
for those who don't know C or can't dig the ioctl codes from
the kernel source code.
(0) When it is too late, many people realize that they could have
made a backup, either with dd to some file, or with
# sfdisk -d /dev/hda
both to file and printer.
(1) These ioctls are used by existing programs. So, for example,
# hdparm -g /dev/hda5
will give you the starting offset (in 512-byte sectors) of /dev/hda5.
Even better may be a command like
# blockdev --report
(2) Several programs, like mount, *fdisk, blockdev, read
/proc/partitions. Changing the format will break all of these.
So, it is best not to change anything, but if you do, only add
fields at the end.
(2a) Maybe /proc/partitions is already extended with disk statistics.
Certainly some vendors do so, and it is rumoured that stock 2.4.20
will (optionally) do so.
Given this uncertainty about what comes after the currently present
fields, it is now impossible to add anything new, unless all programs
using /proc/partitions also parse the header line.
It is best to consider /proc/partitions frozen. Linux 2.5 has
driverfs, and although "cat /proc/partitions" is much more convenient
than searching around in driverfs (sysfs), no doubt blockdev will be
changed so as to report on sysfs, when that exists and is mounted.
Andries
next reply other threads:[~2002-11-02 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 19:19 Andries.Brouwer [this message]
2002-11-02 19:57 ` Petr Baudis
-- strict thread matches above, loose matches on Subject: below --
2002-11-02 17:20 Petr Baudis
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=UTC200211021919.gA2JJMk20461.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@connectiva.com.br \
--cc=pasky@pasky.ji.cz \
--cc=torvalds@transmeta.com \
--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
all inboxes | Powered by JetHome®