All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Rothwell <rothwell@holly-springs.nc.us>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2, CF, PCMCIA adapter, ATA
Date: 04 Nov 2001 16:34:07 -0500	[thread overview]
Message-ID: <1004909648.1728.53.camel@gromit.house> (raw)
In-Reply-To: <Pine.LNX.4.33.0111042108140.28157-100000@imladris.demon.co.uk>

On Sun, 2001-11-04 at 16:16, David Woodhouse wrote:
> As far as you're concerned, it's just alien technology

Okey-dokey, then.

> # dd if=jffs2-image of=/dev/hda (or hda1, hda2, etc.) 
> # insmod blkmtd device=/dev/hda
> # mount -t jffs2 /dev/mtdblock0 /mnt/jffs2

... followed by a litany of "argh, block not erased" type messages in
the syslog. Mount then returns. Then, I try to copy some files into the
mounted jffs2 filesystem ...  "cp" causes an oops and the interrupt
handler gets killed.

> You may want partitioning if you want to boot from this too, not just use 
> it as filesystem.

Am I correct in assuming that I can make partitions with fdisk, then 

 # dd if=flash.jffs2 of=/dev/hde1
 # modprobe blkmtd device=/dev/hde1
 # mount -t jffs2 /dev/mtdblock0 /mnt/flash

...?

What would this look like in lilo and /etc/fstab on the device that will
hopefully be booting from the jffs2 image?

> There have been some blkmtd updates since then. I'm hoping the 
> maintainer 
> will send those to Linus if appropriate.

Maybe the updates won't oops... :)


Do you use mtdram to create jffs2 filesystems? Or some other method?


Thanks,

Michael

  reply	other threads:[~2001-11-04 21:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-04 20:59 JFFS2, CF, PCMCIA adapter, ATA Michael Rothwell
2001-11-04 21:16 ` David Woodhouse
2001-11-04 21:34   ` Michael Rothwell [this message]
2001-11-04 21:40     ` David Woodhouse
2001-11-04 22:09       ` Michael Rothwell
2001-11-04 22:42         ` 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=1004909648.1728.53.camel@gromit.house \
    --to=rothwell@holly-springs.nc.us \
    --cc=dwmw2@infradead.org \
    --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 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.