public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: bcrl@redhat.com, torvalds@transmeta.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	viro@math.psu.edu
Subject: Re: [RFD w/info-PATCH] device arguments from lookup, partion code in userspace
Date: Sat, 19 May 2001 13:09:43 +0200 (MET DST)	[thread overview]
Message-ID: <UTC200105191109.NAA53719.aeb@vlet.cwi.nl> (raw)

    From: Ben LaHaise <bcrl@redhat.com>

    3. Userspace partition code proposal

        Given the above two bits, here's a brief explaination of a
        proposal to move management of the partitioning scheme into
        userspace, along with portions of raid startup, lvm, uuid and
        mount by label code needed for mounting the root filesystem.

        Consider that the device node currently known as /dev/hda5 can
        also be viewed as /dev/hda at offset 512000 with a limit of 10GB.
        With the extensions in fs/block_dev.c, you could replace /dev/hda5
        with /dev/hda/offset=512000,limit=10240000000.  Now, by putting
        the partition parsing code into a libpart and binding mount to a
        libpart, the root filesystem mounting code can be run out of an
        initrd image.  The use of mount gives us the ability to mount
        filesystems by UUID, by label or other exotic schemes without
        having to add any additional code to the kernel.

    I'm going to stop writing this now.  I need sleep...

Hmm. You know that I wrote this long ago?
And that it has been part of the kernel for a long time?
And that there are user space utilities that use it?

In util-linux, look at the partx subdirectory.
In the kernel, read drivers/block/blkpg.c.

Andries

             reply	other threads:[~2001-05-19 11:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-19 11:09 Andries.Brouwer [this message]
2001-05-19 11:43 ` [RFD w/info-PATCH] device arguments from lookup, partion code in userspace Andrew Morton
2001-05-19 12:00   ` Alexander Viro
2001-05-19 12:06     ` [RFD w/info-PATCH] device arguments from lookup, partion codein userspace Andrew Morton
2001-05-19 15:56     ` [RFD w/info-PATCH] device arguments from lookup, partion code in userspace Ben LaHaise
2001-05-19 16:25       ` [RFD w/info-PATCH] device arguments from lookup, partion code Alan Cox
2001-05-19 16:36         ` Alexander Viro
2001-05-19 16:44         ` Matthew Wilcox
2001-05-19 18:01         ` Nicolas Pitre
2001-05-19 18:34         ` Linus Torvalds
2001-05-19 22:34           ` Ingo Oeser
2001-05-19 23:42             ` Alexander Viro
2001-05-20  0:11               ` Alan Cox
2001-05-20 17:10             ` Padraig Brady
2001-05-20 19:53         ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2001-05-22 18:45 [RFD w/info-PATCH] device arguments from lookup, partion code in userspace Andries.Brouwer
2001-05-21 12:43 Andries.Brouwer
2001-05-21 16:08 ` Daniel Phillips
2001-05-19  6:23 Ben LaHaise
2001-05-19  9:42 ` Christer Weinigel
2001-05-19  9:51 ` Christer Weinigel
2001-05-19 11:37 ` Eric W. Biederman
2001-05-19 14:25   ` Daniel Phillips
2001-05-21  8:14     ` Lars Marowsky-Bree
2001-05-22  9:07       ` Daniel Phillips
2001-05-19 13:53 ` Daniel Phillips
2001-05-19 18:31 ` Linus Torvalds

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=UTC200105191109.NAA53719.aeb@vlet.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=bcrl@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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