From: Marc Singer <elf@buici.com>
To: Erich Schubert <erich@debian.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: recommended Filesystem for DoC?
Date: Sun, 15 Sep 2002 07:13:01 -0700 [thread overview]
Message-ID: <20020915141301.GA5550@buici.com> (raw)
In-Reply-To: <20020915104155.GB7894@bombadil.xmldesign.de>
On Sun, Sep 15, 2002 at 12:41:55PM +0200, Erich Schubert wrote:
> > Ext2 can get you in trouble. You might be able to minimize your
> > exposure by guaranteeing that the fs is sync'd after performing a
> > write.
>
> Why is ext3 better here?
> I was planning to have my ext2 read-only unless i need to change
> something; then remount,rw; change the settings; remount,ro...
Certainly, that would work. There is the small chance that something
will fail while the filesystem is r/w. On my (embedded) application,
even that is too much of a risk.
>
> > > I was thinking about mounting a cramfs ro as root, a tmpfs in some other
> > > dir for automatic files (such as xserver output) and the actual
> > > filesytem on the device in /writefs.
> > > On that i should then store the kernel and the cramfs-initrd?
> >
> > I don't think you can put the kernel in the initrd. After all, the
> > kernel *reads* the initrd. Instead, the kernel goes into the root
> > filesystem (lilo/grub style) or in an MSDOS partition (syslinux
> > style).
>
> you misunderstood what i said. I said i put a ext2 there containing the
> kernel, the cramfs and the file i need to be able to change easily.
Indeed, I did misunderstand.
>
> > I stopped using lilo because it is a little too complex and because it
> > doesn't handle serial consoles as well as syslinux. I'd have used
> > grub, but it crashes on my hardware. IMHO, grub is the most
> > attractive because it has the best feature set.
>
> i don't need serial consoles; the machine is a X11 terminal - that makes
> no sense without a real screen and keyboard ;)
Of course. LILO works for many folks, too.
>
> Gruss,
> Erich Schubert
> --
> erich@(mucl.de|debian.org) -- GPG Key ID: 4B3A135C
> A man doesn't know what he knows until he knows what he doesn't know.
> Die k?rzeste Verbindung zwischen zwei Menschen ist ein L?cheln.
> F?r jedes Problem gibt es eine L?sung, die einfach, klar und falsch ist.
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2002-09-15 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 23:51 recommended Filesystem for DoC? Erich Schubert
2002-09-15 1:00 ` Marc Singer
2002-09-15 7:55 ` David Woodhouse
2002-09-15 17:54 ` Erich Schubert
2002-09-15 19:44 ` David Woodhouse
2002-09-15 10:41 ` Erich Schubert
2002-09-15 14:13 ` Marc Singer [this message]
2002-09-15 19:07 ` Charles Manning
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=20020915141301.GA5550@buici.com \
--to=elf@buici.com \
--cc=erich@debian.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