From: Richard Rak <richardr@corel.com>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux 2.4.0-test9
Date: Mon, 06 Nov 2000 16:40:45 -0500 [thread overview]
Message-ID: <3A07255D.24AAAA70@corel.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1001106162033.212A-100000@chaos.analogic.com>
[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]
I don't have any problems building initrd images here (using
RAMDISKs). Can I take a look at your scripts and see what is going on?
"Richard B. Johnson" wrote:
>
> Linux 2.4.0-test9 can be built and booted via initrd when running
> a 2.2.17 kernel.
>
> However when running, the new kernel 2.4.0-test9, can't be used to
> make a usable initrd ram disk. The result being that 2.4.0-test9
> can't, itself, build an "initrd" bootable system.
>
> Before everybody screams that I don't know what I'm doing, let me
> assure you that I know that the two kernels put their modules in
> different directories and the new directory scheme seems to require
> the latest and greatest version of modutils.
>
> I have two ways of building an initial RAM disk (they both use
> scripts, not provided with any distribution). One uses the loop-device
> and the other uses the RAM disk directly. Because of previous
> problems, on some kernel versions, with the loop device (it was
> being mucked with for encription), I exclusively use the RAM disk
> to build initrd.
>
> Therefore, the problem seems to be that 2.4.0-test9 has a problem
> with the RAM Disk.
>
> Cheers,
> Dick Johnson
>
> Penguin : Linux version 2.2.17 on an i686 machine (801.18 BogoMips).
>
> "Memory is like gasoline. You use it up when you are running. Of
> course you get it all back when you reboot..."; Actual explanation
> obtained from the Micro$oft help desk.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
--
Richard Rak
(richardr@corel.com)
Software Engineer
A+ Certified Service Technician
New Team - Renewed Focus: Corel ushers in a new era!
To learn more, please visit http://www.corel.com
[-- Attachment #2: Card for Richard Rak --]
[-- Type: text/x-vcard, Size: 298 bytes --]
begin:vcard
n:Rak;Richard
tel;cell:(613) 298-3229
tel;work:(613) 728-0826 ext 1104
x-mozilla-html:FALSE
org:Corel Corporation
adr:;;1600 Carling Ave.;Ottawa;Ontario;K1Z 8R7;Canada
version:2.1
email;internet:richardr@corel.com
title:Software Engineer
x-mozilla-cpt:;-27232
fn:Richard Rak
end:vcard
next prev parent reply other threads:[~2000-11-06 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 21:31 linux 2.4.0-test9 Richard B. Johnson
2000-11-06 21:40 ` Richard Rak [this message]
2000-11-06 22:11 ` Richard B. Johnson
2000-11-07 3:15 ` Keith Owens
2000-11-07 13:28 ` Richard B. Johnson
2000-11-07 14:00 ` Richard B. Johnson
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=3A07255D.24AAAA70@corel.com \
--to=richardr@corel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.