From: Petr Baudis <pasky@ucw.cz>
To: Andries.Brouwer@cwi.nl
Cc: marcelo@connectiva.com.br, 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:57:31 +0100 [thread overview]
Message-ID: <20021102195731.GA2535@pasky.ji.cz> (raw)
In-Reply-To: <UTC200211021919.gA2JJMk20461.aeb@smtp.cwi.nl>
Dear diary, on Sat, Nov 02, 2002 at 08:19:22PM CET, I got a letter,
where Andries.Brouwer@cwi.nl told me, that...
> (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.
>
..snip..
>
> 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.
Ah.. I see, then please disregard the patches. Didn't realize that hdparm
already can do it nor that it's exported thru driverfs in 2.5, sorry.
--
Petr "Pasky" Baudis
.
This host is a black hole at HTTP wavelengths. GETs go in, and nothing
comes out, not even Hawking radiation.
-- Graaagh the Mighty on rec.games.roguelike.angband
.
Public PGP key && geekcode && homepage: http://pasky.ji.cz/~pasky/
next prev parent reply other threads:[~2002-11-02 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 19:19 Andries.Brouwer
2002-11-02 19:57 ` Petr Baudis [this message]
-- 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=20021102195731.GA2535@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=Andries.Brouwer@cwi.nl \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@connectiva.com.br \
--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®