From: "Chris Fowler" <cfowler@outpostsentinel.com>
To: "Ian" <Relativity@HumanHeuristic.com>
Cc: <linux-mtd@lists.infradead.org>
Subject: RE: Kerlen 2.4.13 and ramdisks
Date: Tue, 19 Feb 2002 17:01:00 -0500 [thread overview]
Message-ID: <NFBBLCEFBCFEPMJJKOIKKEILCDAA.cfowler@outpostsentinel.com> (raw)
In-Reply-To: <200202192150.HAA24884@singularity.tronunltd.com>
Ian,
loopback would not allow me to write to the image while running it. Making
the flash (upgrade) process more difficult. The FS is ext2 and I do not use
mount.
The only way the kernel can mount this is by me putting it in memory first.
The only way to do that is with initrd. It owkrs when initrd only places
that data there. When I try to download the *same* data from the network
and put there it craps out. I have to download the data first before I can
place it in /dev/ram7. TO do that I mount a ram fs at a upper limit of
32mb. Download the file there then place it in /dev/ram7. Just by using
that memory as temporary storeage I'm haing problems. I've read posts that
state that certain 2.4.X kernels have problems repecting the boundaries of a
ramdisk. They tend to overwrite those areas when needing memory.
lilo.conf:
....
root=/dev/ram7
-----Original Message-----
From: linux-mtd-admin@lists.infradead.org
[mailto:linux-mtd-admin@lists.infradead.org]On Behalf Of Ian
Sent: Tuesday, February 19, 2002 4:51 PM
To: Chris Fowler
Cc: linux-mtd@lists.infradead.org
Subject: Re:Kerlen 2.4.13 and ramdisks
If you have loopback support compiled in you can mount it directly through
the loopback driver, without creating a ramdisk ...
What was the error that mount gave? You probably only need to specify
the "-o" parameter ... mount doesn't usually detect fancy filesystems ...
----- Original Message -----
>From: "Chris Fowler" <cfowler@outpostsentinel.com>
>To: <linux-mtd@lists.infradead.org>
>Subject: Kerlen 2.4.13 and ramdisks
>Date: Tue, 19 Feb 2002 10:33:33 -0500
>
> You guys might have ran across a ramdisk problem. I have a feeling that
kernel 2.4.13 is
not respecting my ramdisks.
>
>
> dd if=/etc/user.img of=/dev/ram6
>
> mount /dev/ram6 fails.
>
>
> Is this a problem?
>
>
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2002-02-19 21:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 21:50 Re:Kerlen 2.4.13 and ramdisks Ian
2002-02-19 22:01 ` Chris Fowler [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 23:57 Kerlen " Ian
2002-02-20 0:03 ` Chris Fowler
2002-02-19 23:42 Ian
2002-02-19 23:50 ` Chris Fowler
2002-02-19 23:33 Ian
2002-02-19 23:36 ` Chris Fowler
2002-02-19 22:41 Ian
2002-02-19 22:50 ` Chris Fowler
2002-02-19 15:33 Chris Fowler
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=NFBBLCEFBCFEPMJJKOIKKEILCDAA.cfowler@outpostsentinel.com \
--to=cfowler@outpostsentinel.com \
--cc=Relativity@HumanHeuristic.com \
--cc=linux-mtd@lists.infradead.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