public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 boot enhancements, boot bean counting 8/11
Date: 17 Apr 2002 11:37:53 -0600	[thread overview]
Message-ID: <m1sn5ufcpa.fsf@frodo.biederman.org> (raw)
In-Reply-To: <m1elhegt1c.fsf@frodo.biederman.org> <3CBDA073.6010700@evision-ventures.com>

Martin Dalecki <dalecki@evision-ventures.com> writes:

> Eric W. Biederman wrote:
> > Linus please apply,
> > Rework the actual build/link step for kernel images.  - remove the need for
> > objcopy
> > - Kill the ROOT_DEV Makefile variable, the implementation
> >   was only half correct and there are much better ways
> >   to specify your root device than modifying the kernel Makefile.
> > - Don't loose information when the executable is built
> 
> Coudl you please use sufficiently large fields for kdev_t variables?
> This way if we once have bigger device id spaces one will not have
> to mess with the boot code again.
> Thank you.

1) This patch doesn't change anything except to document which fields
   are present, and how big they are, and no there isn't enough room
   to trivially expand these fields.
2) Exporting kdev_t from the kernel would be very bad.
3) swapdev is long dead, and root_dev while it works is unnecessary,
   you can specify it on the command line just fine.

So we already are future proofed, and the change you suggest would be
a bad one.  The compiled in command line fully supports the ability
to set your root device, so no functionality is lost.

Like I said in my intro a lot of this code simply makes what the boot
processes is currently doing more visible.

Eric

  reply	other threads:[~2002-04-17 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 16:59 [PATCH] x86 boot enhancements, boot bean counting 8/11 Eric W. Biederman
2002-04-17 16:18 ` Martin Dalecki
2002-04-17 17:37   ` Eric W. Biederman [this message]
2002-04-18  7:57     ` Martin Dalecki

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=m1sn5ufcpa.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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