From: David Woodhouse <dwmw2@infradead.org>
To: Riipinen Petri <riipinen@nic.fi>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [Novice] Few simple questions on DOC.
Date: Fri, 17 Aug 2001 10:57:07 +0100 [thread overview]
Message-ID: <25963.998042227@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.31.0108171243320.19730-100000@netti.nic.fi>
riipinen@nic.fi said:
> Are the fixes in 2.4.9? I could just as well update my kernel source
> tree anyway and forget 2.4.7 completely, nothing in particular is
> forcing me to stay on 2.4.7.
Not yet, sorry - I sent them once but Linus dropped them. I'll resend when
he gets back from .fi.
> Well, hmm... Ok, I assumed that the bootsector included in bzImage
> works just as well as it does with floppies and hd. Well, I was really
> thinking that I could save some space by not using Lilo/Grub but maybe
> that's not worth it then.
I suppose it _might_ work. Don't be surprised if it doesn't though.
> And would you recommend Lilo over Grub?
Until someone does the relatively small amount of work to finish the Grub
DiskOnChip support, yes.
> So ext2 is the most practical choise currently?
Yep.
> Would there be any problems if the user shuts down the SBC when my
> application is still writing some data file onto the DOC? I guess
> those will be dealt with on boot.
It should be just the same as on a hard drive - which means that you should
probably be using ext3, but that's a little heavyweight for use on the
DiskOnChip.
--
dwmw2
next prev parent reply other threads:[~2001-08-17 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 9:01 [Novice] Few simple questions on DOC Riipinen Petri
2001-08-17 9:08 ` David Woodhouse
2001-08-17 9:52 ` Riipinen Petri
2001-08-17 9:57 ` David Woodhouse [this message]
2001-08-17 10:05 ` Riipinen Petri
2001-08-17 10:06 ` 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=25963.998042227@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=riipinen@nic.fi \
/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