linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marius Gedminas <mgedmin@centras.lt>
To: linux-kernel@vger.kernel.org
Subject: Re: Ext3 documentation
Date: Sun, 6 Oct 2002 19:26:59 +0200	[thread overview]
Message-ID: <20021006172659.GA21270@gintaras> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0210020915400.14122-100000@dragon.pdx.osdl.net>

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

On Wed, Oct 02, 2002 at 09:17:00AM -0700, Randy.Dunlap wrote:
> On Wed, 2 Oct 2002, Vincent Hanquez wrote:
> 
> | Here a (small) documentation for ext3 filesystem.
> | it seem now correct/accurate. report me any problem/bugs
> |
> | It can be merge in 2.4/2.5 kernel I think. feedback appreciated.
> 
> Here are a few typo corrections for you.  My correction lines
> begin with '#'.

I found a couple more.

> jounal=update		Update the ext3 file system's journal to the
> 			current format.

'jounal'?

> bsddf 		(*)	Make 'df' act like BSD.
> minixdf			Make 'df' act like Minix.

A couple of additional lines for clueless users (like me) would be
nice.

> errors=remount-ro(*)	Remount the filesystem read-only on an error.
> errors=continue		Keep going on a filesystem error.
> errors=panic		Panic and halt the machine if an error occurs.

mount(8) claims the default is set in the superblock.  (It certainly
wasn't remount-ro when I mountend an ext3 fs on 2.4.18.)


Marius Gedminas
-- 
The IQ of the group is the lowest IQ of a member of
the group divided by the number of people in the group.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2002-10-06 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02  8:57 Ext3 documentation Vincent Hanquez
2002-10-02 16:17 ` Randy.Dunlap
2002-10-06 17:26   ` Marius Gedminas [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=20021006172659.GA21270@gintaras \
    --to=mgedmin@centras.lt \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).