From: Grant Likely <glikely@gmail.com>
To: ????????? <rober@opnet.com.tw>, linuxppc-embedded@ozlabs.org
Subject: Re: How to build more than 16M ramdisk for u-boot
Date: Fri, 19 Aug 2005 00:15:08 -0600 [thread overview]
Message-ID: <20050819061508.GA28537@siegfried.thelikelysolution.ca> (raw)
In-Reply-To: <1124416918.6752.1.camel@banana>
On Fri, Aug 19, 2005 at 10:01:58AM +0800, ????????? wrote:
> Hi all:
>
> I found if i build ramdisk more than 16M, i'll got error at using
> mke2fs command.
>
> dd if=/dev/zero of=ramdisk bs=1024k count=20
>
> /sbin/mke2fs -F m0 ramdisk
> mke2fs 1.36 (05-Feb-2005)
> mke2fs: bad blocks count - ramdisk
typo?
try: /sbin/mke2fs -F -m0 ramdisk
next prev parent reply other threads:[~2005-08-19 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 2:01 How to build more than 16M ramdisk for u-boot 徐小威
2005-08-19 6:15 ` Grant Likely [this message]
[not found] <43C18850A2E42CD14825706200226758.0022678048257062@opnet.com.tw>
[not found] ` <001401c5a494$ffd659c0$1a0e000a@RoberHsu>
2005-08-19 20:06 ` Grant Likely
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=20050819061508.GA28537@siegfried.thelikelysolution.ca \
--to=glikely@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rober@opnet.com.tw \
/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;
as well as URLs for NNTP newsgroup(s).