public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Gray <n8gray-7GExONQZ6ZKVc3sceRu5cw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: DSDT in initrd
Date: Wed, 21 May 2003 11:07:59 -0700	[thread overview]
Message-ID: <bagf6e$tq2$1@main.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.53.0305210955210.13798@dynast.gaugusch.at

Markus Gaugusch wrote:

> On May 21, Nathan Gray <n8gray-7GExONQZ6ZKVc3sceRu5cw@public.gmane.org>
> wrote:
> 
>> I continue to think that the proper solution is a separate kernel
>> parameter acpi_tables=/boot/tables.??? (with credit to the person who
>> generalized this idea from the dsdt to all tables).  I know you're
>> concerned about fs drivers not being around, but if the kernel can find
>> the initrd on the disk it should be able to find other files somehow.
> The file is not loaded by the kernel, but by the boot loader. Someone said
> that grub is able to load more than one file, but I think lilo is not.

That's what I imagined.  I didn't mean to attribute this to the kernel, but
I see that's basically how I wrote it.

> Also, the kernel has only support for one initrd, and I am not good enough
> at the moment to add support for more, I guess.

I know it's not easy, but if it's the right way then it's the right way.

> Although the way I use to read the initrd is a bit hacker-ish, it is not
> that bad I think. Bootsplash uses the same technique and is used by major
> distributors. If it were insecure they could not use it (initrd is a major
> part for distributions with pre-compiled kernels).

I don't think anybody's questioning the security of the approach.  I just
get the feeling that you'll get resistance to it.  You might try floating
the idea on the kernel list and see how people react.  I've got my opinion
on how it should work, but I can see that you have to have this data very
early on and it will not be trivial to make it work my way.  Linus may end
up agreeing with you, which would probably help your argument for inclusion
of your patch.  :-)

Cheers,
-Nathan

-- 
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

      parent reply	other threads:[~2003-05-21 18:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19 14:38 DSDT in initrd Brown, Len
     [not found] ` <A5974D8E5F98D511BB910002A50A6647054FC40A-MgY+aF+eRfZviC08c4yzC1DQ4js95KgL@public.gmane.org>
2003-05-19 14:53   ` Ducrot Bruno
2003-05-19 15:26   ` Michael Frank
2003-05-20 16:56   ` Markus Gaugusch
     [not found]     ` <Pine.LNX.4.53.0305191725350.9728-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2003-05-20 18:01       ` Matthew Wilcox
     [not found]         ` <20030520180149.GJ31518-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-05-20 18:03           ` Markus Gaugusch
2003-05-21  7:23             ` Nathan Gray
2003-05-21  8:07               ` Gunter Ohrner
2003-05-21  8:07               ` Markus Gaugusch
2003-05-21 15:05                 ` Richard Black
     [not found]                   ` <3ECB95CB.2020109-VXdhtT5mjnY@public.gmane.org>
2003-05-21 16:52                     ` Ducrot Bruno
2003-05-21 18:07                 ` Nathan Gray [this message]

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='bagf6e$tq2$1@main.gmane.org' \
    --to=n8gray-7gexonqz6zkvc3sceru5cw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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