On 12/27/01 at 10:15 AM, Charles Steinkuehler
<[EMAIL PROTECTED]> wrote:
> > Questions I'd have would be:
>
> Refer to the initial ramdisk documentation in the kernel source...
I've READ that. It's terribly confusing. Here are some questions
that arise out of that documentation:
1. When does
> Questions I'd have would be:
Refer to the initial ramdisk documentation in the kernel source...
> 1. What parameters are from the patches and what should the
> non-patched kernel parms be? I suspect initrd_archive is an added
> parameter; I also suspect that root= should now read (in my case)
On 12/26/01 at 9:24 PM, Jacques Nilo <[EMAIL PROTECTED]>
wrote:
> From: "David Douthitt" <[EMAIL PROTECTED]>
>
> > I've begun working on the next generation... and have
> > Oxygen booting with an initial RAM disk - in preparation
> > for running without the linuxrc patch.
> In a non-patched ker
David Douthitt wrote:
>I've begun working on the next generation... and have Oxygen booting
>with an initial RAM disk - in preparation for running without the
>linuxrc patch.
>
>Running without the initrd archive patch takes just a bit more, but
>shouldn't be too hard.
>
>Basically, what happen
From: "David Douthitt" <[EMAIL PROTECTED]>
> I've begun working on the next generation... and have Oxygen booting
> with an initial RAM disk - in preparation for running without the
> linuxrc patch.
He, he ...
> Running without the initrd archive patch takes just a bit more, but
> shouldn't be to
I've begun working on the next generation... and have Oxygen booting
with an initial RAM disk - in preparation for running without the
linuxrc patch.
Running without the initrd archive patch takes just a bit more, but
shouldn't be too hard.
Basically, what happens is linuxrc sets up a very basic
