All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russ.Dill@asu.edu (Russ Dill)
To: linux-mtd@lists.infradead.org
Subject: New problem with DoC
Date: 17 Mar 2003 13:31:56 -0700	[thread overview]
Message-ID: <1047933115.1637.19.camel@gobbles> (raw)
In-Reply-To: <000201c2ecbf$47ab1be0$88a7580c@who5>

> Thanks folks. That worked. Funny thing, these devices, the solutions
> suggested by the manufacturer didn't work. Which is what I expected. 

Generally, if you want to use their stuff, I think you have to use their
dos based tools

> Next question, how do I put that one, the /boot directory, and the
> menu.list as when I would use a normal Grub booting arrangement in to
> the DoC? Oh, and a custom kernel as well.

right now, grub only supports filesystems on top of NFTL. It'd be really
nice to get YAFFS and JFFS2 support into grub. As a workaround, you may
be able to use a small NFTL partition, with cramfs (patches exist to add
cramfs to grub) containing a menu.lst and kernel, and then mount the
rest as YAFFS/JFFS2. Or of course just use NFTL

> P.S. David is my message formatting acceptable?

generally, its best to reply to relevant paragraphs right below that
paragraph, and then delete stuff that isn't relevant.

  reply	other threads:[~2003-03-17 20:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A05D1A08-587E-11D7-ADC7-000393AD6294@regolith.co.uk>
2003-03-17 19:56 ` New problem with DoC Gregg C Levine
2003-03-17 20:31   ` Russ Dill [this message]
2003-03-17 20:49     ` Charles Manning
2003-03-17 21:13       ` Russ Dill
2003-03-17  2:42 Gregg C Levine
2003-03-17  7:05 ` Henrik Nordstrom
2003-03-17 11:31   ` Gregg C Levine
2003-03-17 13:30     ` Henrik Nordstrom

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=1047933115.1637.19.camel@gobbles \
    --to=russ.dill@asu.edu \
    --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.