All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin A. Sapp" <Kevin.Sapp@catapult.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: RAM Disk problems
Date: Wed, 10 Mar 2004 12:35:48 -0500	[thread overview]
Message-ID: <404F51F4.5040000@catapult.com> (raw)
In-Reply-To: <20040310150032.D3CBEC0655@atlas.denx.de>


Thanks to all.
  Wolfgang had it.  No EXT2 support. Duh!

Kevin

>In message <404F26A5.7070807@catapult.com> you wrote:
>
>
>>I am trying to bring up a RAM disk as the root file system.
>>Most everything is working until it come's time to mount it.
>>
>>
>
>This is an ext2 based ramdisk? Do you have ext2  support  enabled  in
>your kernel? If yes, try disabling devfs.
>
>Best regards,
>
>Wolfgang Denk
>
>--
>Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
>Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
>I mean, I . . . think to understand you, I just don't know  what  you
>are saying ...                        - Terry Pratchett, _Soul Music_
>
>
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-03-10 17:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2D9AB865A49FD511914700105A0EF679016C4909@morse.smart.lfk.eads.net>
2004-03-09 13:03 ` AW: Compiling glibc-2.3.2 (debian) on mpc8xx ;-) David Jander
2004-03-09 14:20   ` remote access via shell Kevin P. Dankwardt
2004-03-09 15:14     ` Wolfgang Denk
2004-03-10 14:31       ` RAM Disk problems Kevin A. Sapp
2004-03-10 15:00         ` Wolfgang Denk
2004-03-10 17:35           ` Kevin A. Sapp [this message]
2004-03-10 15:03         ` Jaap-Jan Boor
2004-03-09 16:24     ` remote access via shell Gerrit Van de Velde
2004-03-10 15:11 RAM Disk problems Steven Blakeslee
2004-03-10 15:56 ` song sam

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=404F51F4.5040000@catapult.com \
    --to=kevin.sapp@catapult.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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.