From: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
To: "Mike Galbraith" <mikeg@wen-online.de>
Cc: <linux-kernel@vger.kernel.org>,
"Jaswinder Singh" <jaswinder.singh@3disystems.com>
Subject: Re: Problem with Ramdisk in linux-2.4.1
Date: Tue, 13 Feb 2001 12:55:00 -0800 [thread overview]
Message-ID: <012101c095ff$3b167320$bba6b3d0@Toshiba> (raw)
In-Reply-To: <Pine.Linu.4.10.10102132042480.755-100000@mikeg.weiden.de>
Dear Mike ,
----- Original Message -----
From: "Mike Galbraith" <mikeg@wen-online.de>
To: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Tuesday, February 13, 2001 11:56 AM
Subject: Re: Problem with Ramdisk in linux-2.4.1
> On Tue, 13 Feb 2001, Jaswinder Singh wrote:
>
> > Dear Mike and others ,
> >
> > I am using compressed ramdisk , i can not turn off cramfs .
>
> (ok.. really is compressed)
>
> > my error messages are very strange and irreregular .
> >
> > i am getting 3 different kind of error messages :-
> >
> > invalid compressed format (err=1)
> > OR
> > invalid compressed format (err=2)
> > OR
> > crc error
> >
> > I am using gzip 1.2.4 (18 Aug 93)
> >
> > But when i use same ramdisk with old kernel like 2.2.12 , it works fine
.
>
> Can you point me to a cramfs generation procedure? (never used
> cramfs.. know where the docs are, but could use a small time warp)
>
make ramdisk as you normally do and then compress it by gzip .
You can see documentation on Ramdisk in Documentation/ramdisk.txt if you
have some time ;)
Best Regards,
Jaswinder.
--
These are my opinions not 3Di.
> -Mike
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-02-13 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.Linu.4.10.10102130916110.805-100000@mikeg.weiden.de>
2001-02-13 19:08 ` Jaswinder Singh
2001-02-13 19:16 ` Jaswinder Singh
2001-02-13 19:56 ` Mike Galbraith
2001-02-13 20:55 ` Jaswinder Singh [this message]
2001-02-14 5:21 ` Mike Galbraith
2001-02-12 8:19 Jaswinder Singh
2001-02-12 19:10 ` Jaswinder Singh
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='012101c095ff$3b167320$bba6b3d0@Toshiba' \
--to=jaswinder.singh@3disystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
/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®