From: Jason <unleet@qwest.net>
To: speakup@braille.uwo.ca
Subject: Re: DEC Express problem
Date: Mon, 8 Oct 2001 22:53:01 -0700 [thread overview]
Message-ID: <01100822530100.24937@lightstar> (raw)
In-Reply-To: <001201c15082$2b8cc1a0$0300a8c0@elcjn1.sdca.home.com>
for ext2, you pass it read-only so that fsck can safely check the filesystem
integrity, it can't do this safely if there's any chance of another process
writing to that fielsystem.
it gets remounted read-write automaticaly some time after being checked.
> found any clear documentation on why I would make it rw or ro when passing
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Tony Baechler
` Adam Myrow
` Tony Baechler
` Jason [this message]
` Thomas Ward
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=01100822530100.24937@lightstar \
--to=unleet@qwest.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).