public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Gregg C Levine" <hansolofalcon@worldnet.att.net>
To: <linux-mtd@lists.infradead.org>
Cc: 'David Woodhouse' <dwmw2@infradead.org>
Subject: RE: Is this normal?
Date: Tue, 8 Apr 2003 13:02:14 -0400	[thread overview]
Message-ID: <004a01c2fdf0$9b9f9360$06a0580c@who5> (raw)
In-Reply-To: <1049789725.18045.79.camel@passion.cambridge.redhat.com>

(See Below!)
> -----Original Message-----
> From: linux-mtd-bounces@lists.infradead.org [mailto:linux-mtd-
> bounces@lists.infradead.org] On Behalf Of David Woodhouse
> Sent: Tuesday, April 08, 2003 4:15 AM
> To: Gregg C Levine
> Cc: linux-mtd@lists.infradead.org
> Subject: Re: Is this normal?
> 
> On Tue, 2003-04-08 at 04:23, Gregg C Levine wrote:
> > so replaced its flakey M-SYS firmware with the GRUB based one.
> > Since I have Lilo installed on the drive, as well as a currently
> > inactive grub, I half expected to see the Lilo multiple kernel
boot
> > prompt. Instead I saw the grub menu that I have placed there.
> 
> That is indeed normal. Since you removed the M-Systems firmware,
there's
> nothing to make the DiskOnChip appear as a 'normal' hard drive via
the
> BIOS 'normal' INT 13h disc access routines. So LILO cannot possibly
> work.
> 
> > Now the question remains: Any suggestions, again, for constructing
> > that image to place on the DOC-2000? And how would I tell the
computer
> > to boot it, or the resident hard drive?
> 
> You are, as ever, very difficult to comprehend. What image to place
on
> the DOC2000? Format it (with the Grub firmware) with DFORMAT, or
with
> nftl_format if you must, make an ext2 file system on /dev/nftl, and
have
> Grub's boot menu boot from the ext2 file system.... what are you
> missing?
> 
> --
> dwmw2

Hello from Gregg C Levine
Basically yes. When I wrote the message that you're confused about it
was very early in the morning here, and at that time I don't even
pretend to make myself clear to others. I apologize. 
How do I go about formatting it with the Grub firmware in place?   And
since I am leaning towards formatting it with an ext2 file system, how
do I go about attaching it to the device name you chose. And then have
it come up on the Grub's boot menu boot from the ext2 file system. 
Yes, that's what I was missing. 
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

      reply	other threads:[~2003-04-08 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08  3:23 Is this normal? Gregg C Levine
2003-04-08  8:15 ` David Woodhouse
2003-04-08 17:02   ` Gregg C Levine [this message]

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='004a01c2fdf0$9b9f9360$06a0580c@who5' \
    --to=hansolofalcon@worldnet.att.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox