public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Clausen <clausen@gnu.org>
To: linux-kernel@vger.kernel.org
Cc: bug-parted@gnu.org, evms-devel@lists.sourceforge.net
Subject: userspace discovery of partitions
Date: Wed, 2 Jan 2002 05:57:35 +1100	[thread overview]
Message-ID: <20020102055735.C472@gnu.org> (raw)

Hi all,

As discussed a while ago (see thread starting at
http://www.uwsg.iu.edu/hypermail/linux/kernel/0105.2/0659.html), I
wrote a frontend to libparted that does nothing but probe all
block devices for partition tables, and tells the kernel what
partitions it finds.  It optionally prints a short summary.

The hope is to be able to remove partition table parsing from the
kernel, and share partition table code with libparted.

It's called partprobe, and is distributed with Parted.  Get it from:

	ftp.gnu.org/gnu/parted/devel/parted-1.5.6-pre2.tar.gz

When partprobe/libparted are compiled with --enable-discover-only
--disable-nls etc (see README), it comes to about 73k (35k
compressed), not including libc or libuuid.  Unfortunately, this is
still quite large to be including in things like initramfs.  Is
it worth paying this price?

libparted currently supports 7 partition table formats (vs 11 in
linux 2.4).  It uses the blkpg interface in 2.4 to communicate
partition info.  (see libparted/linux.c, linux_disk_commit)

Andrew


             reply	other threads:[~2002-01-01 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-01 18:57 Andrew Clausen [this message]
2002-01-01 20:18 ` [Evms-devel] userspace discovery of partitions Andreas Dilger
2002-01-02  0:18   ` Andrew Clausen
2002-01-02 19:34 ` Christoph Hellwig
2002-01-02 20:37   ` Andrew Clausen

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=20020102055735.C472@gnu.org \
    --to=clausen@gnu.org \
    --cc=bug-parted@gnu.org \
    --cc=evms-devel@lists.sourceforge.net \
    --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