public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: Andries Brouwer <Andries.Brouwer@cwi.nl>
Cc: torvalds@osdl.org, akpm@osdl.org,
	bon@elektron.ikp.physik.tu-darmstadt.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] partitions/msdos.c
Date: Sat, 19 Mar 2005 18:54:58 -0300	[thread overview]
Message-ID: <20050319185458.B17469@almesberger.net> (raw)
In-Reply-To: <20050226213459.GA21137@apps.cwi.nl>; from Andries.Brouwer@cwi.nl on Sat, Feb 26, 2005 at 10:35:00PM +0100

Andries Brouwer wrote:
> In other words, we need the user space command `partition',
> where "partition -t dos /dev/sda" reads a DOS-type partition
> table.

So if you e.g. hotplug a new device, its partitions won't be
accessible before you (or some hotplug manager, etc.) run
"partition" ?

> The two variants are: (i) partition tells the kernel
> to do the partition table reading, and (ii) partition uses partx
> to read the partition table and tells the kernel one-by-one
> about the partitions found this way.

I guess, once you've reached the point where the kernel is
unable to find partitions without user-space help, you may
as well do everything in user space.

> Since this is a fundamental change,

Pretty much, yes. Except for a few embedded systems (*), this
would mark the end of kernels that can do anything useful
without initrd or initramfs.

(*) Oh, regarding the other exception, ceterum censeo nfsroot
    esse delendam.

> a long transition period
> is needed, and that period could start with a kernel boot parameter
> telling the kernel not to do partition table parsing on a particular
> disk, or a particular type of disks, or all disks.

... and allow "partition" to override partitions previously
auto-detected by the kernel. That way, you can phase in
"partition" without needing to change your kernel setup.

Besides, the ability to correct past mistakes would also be
useful if auto-detection from user space yields garbage.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  parent reply	other threads:[~2005-03-19 21:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26 21:35 [PATCH] partitions/msdos.c Andries Brouwer
2005-02-26 22:04 ` Uwe Bonnes
2005-02-26 22:28   ` Linus Torvalds
2005-02-26 22:35     ` Linus Torvalds
2005-02-26 23:24       ` Uwe Bonnes
2005-02-26 23:46         ` Linus Torvalds
2005-02-26 23:53           ` Andries Brouwer
2005-02-26 22:52     ` Andries Brouwer
2005-02-26 23:12       ` Linus Torvalds
2005-02-26 23:40         ` Andries Brouwer
2005-02-26 23:49           ` Linus Torvalds
2005-02-27  0:47             ` Uwe Bonnes
2005-02-27  1:04               ` Linus Torvalds
2005-02-27 14:33                 ` Uwe Bonnes
2005-02-27  1:07               ` Andries Brouwer
2005-03-01  6:53           ` Rogier Wolff
2005-03-19 21:54 ` Werner Almesberger [this message]
2005-03-19 22:28   ` Grzegorz Kulewski

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=20050319185458.B17469@almesberger.net \
    --to=wa@almesberger.net \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=akpm@osdl.org \
    --cc=bon@elektron.ikp.physik.tu-darmstadt.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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