public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Selwyn Tang <selwyn@hectrix.com>
To: linux-mtd@lists.infradead.org
Subject: Setting up compressed rootfs on DOC
Date: Fri, 24 Oct 2003 17:16:55 +0800	[thread overview]
Message-ID: <3F98EE07.20006@hectrix.com> (raw)

Hi all,

I am used to running a DOC patched grub firmware on my DOC 2000 (16MB)
with nftl, following the instructions of Karim's book. Since the space
is running out, I am interested in using a compressed root fs.

I followed mtd-jffs-HOWTO.txt (1.16) to build a compressed root fs on
DOC. That is, I copied my root fs to a ramdisk, dd'd it through gzip to
a compressed gz file, dd'd it to an offset of 1MB on /dev/mtd0 and
rdev'd the kernel image (967KB) about the offset and the device to be
used. Then I came to a problem of how to install the kernel on the DOC.

The HOWTO says I can use any boot loader, like lilo, to install the
kernel, or just place the kernel on the device and boot from it
directly. I got confused here, as I am used to using a grub firmware,
which hooks to int 19h as a bios extension. When it is booted, it
understands the DOC and can load my kernel image from my root fs on the
ext2 partition on the DOC.

But in here, how should I install my kernel image? I tried dd'ing it to
the start of my DOC, like creating a boot floppy, but it doesn't seem
like a boot device to the bios. Should I still install a grub firmware
and a small partition for storing my kernel image, and then dd my
compressed root fs after the partition? Or is there any other more
clever ways?

Selwyn

             reply	other threads:[~2003-10-24  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24  9:16 Selwyn Tang [this message]
     [not found] ` <1068916696.17894.9.camel@localhost>
2003-11-17  2:21   ` Setting up compressed rootfs on DOC Selwyn Tang
2003-11-17  9:22 ` David Woodhouse

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=3F98EE07.20006@hectrix.com \
    --to=selwyn@hectrix.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