mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: flar@pants.nu (Brad Boyer)
To: aaronl@vitelus.com (Aaron Lehmann)
Cc: Andries.Brouwer@cwi.nl, andrewm@uow.edu.au, bcrl@redhat.com,
	clausen@gnu.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com,
	viro@math.psu.edu
Subject: Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace
Date: Sat, 19 May 2001 12:50:10 -0700 (PDT)	[thread overview]
Message-ID: <20010519195010.4C11A2B54A@marcus.pants.nu> (raw)
In-Reply-To: <20010519110720.D2648@vitelus.com> from "Aaron Lehmann" at May 19, 2001 11:07:20 AM

Aaron Lehmann wrote:
> On Sat, May 19, 2001 at 08:05:02PM +0200, Andries.Brouwer@cwi.nl wrote:
> > > initrd is an unnecessary pain in the ass for most people.
> > > It had better not become mandatory.
> > 
> > You would not notice the difference, only your kernel would be
> > a bit smaller and the RRPART ioctl disappears.
> 
> Would I not notice the difference as a user, as a sysadmin, as a
> kernel builder, as a kernel hacker, or all of the above?

If I understand the status of stuff correctly, I think this would make it
a lot more painful to admin if it became a requirement to use initrd on
everything just to be able to boot. If you've ever seen the way some of
the bootloaders for alterate platforms (like ppc and 68k) handle booting,
you'd see what a pain it can be to have anything more than a simple string
of options getting passed to the kernel. It's particularly bad on some
of the embedded ppc platforms. I suspect that if this happened, it would
never be allowed into many people's trees, because it would be worth their
effort to maintain different code so they don't have to squeeze an initrd
on flash along with their kernel and root filesystem. If I'm missing the
boat here, please tell me, but it sure seems like a bad idea to me.

	Brad Boyer


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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-19 18:05 Andries.Brouwer
2001-05-19 18:07 ` Aaron Lehmann
2001-05-19 19:50   ` Brad Boyer [this message]
2001-05-19 19:37     ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2001-05-19 19:17 Andries.Brouwer
2001-05-19 11:30 Andries.Brouwer
2001-05-19 17:50 ` Aaron Lehmann
2001-05-19 18:43 ` Richard Gooch
2001-05-19  6:23 [RFD w/info-PATCH] device arguments from lookup, partion code in userspace Ben LaHaise
2001-05-19  6:57 ` [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace Andrew Clausen
2001-05-19  7:04   ` Alexander Viro
2001-05-19  7:23     ` Andrew Clausen
2001-05-19  8:30       ` Alexander Viro
2001-05-19 10:13         ` Andrew Clausen
2001-05-19  9:11     ` Andrew Morton
2001-05-19  9:20       ` Alexander Viro
2001-05-19  7:58   ` Ben LaHaise
2001-05-19  8:10     ` Alexander Viro
2001-05-19  8:16       ` Ben LaHaise
2001-05-19  8:32         ` Alexander Viro

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=20010519195010.4C11A2B54A@marcus.pants.nu \
    --to=flar@pants.nu \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=aaronl@vitelus.com \
    --cc=andrewm@uow.edu.au \
    --cc=bcrl@redhat.com \
    --cc=clausen@gnu.org \
    --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

all inboxes | Powered by JetHome®