mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rudmer van Dijk <rvandijk@science.uva.nl>
To: zhengchuanbo <zhengcb@netpower.com.cn>
Cc: root@chaos.analogic.com, linux-kernel@vger.kernel.org
Subject: Re: Re: problem of linux-2.4.19
Date: Thu, 18 Jul 2002 18:57:10 +0200	[thread overview]
Message-ID: <20020718165014Z318278-685+12831@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1020718100527.16097A-100000@chaos.analogic.com>

On Thursday 18 July 2002 16:18, Richard B. Johnson wrote:
> On Thu, 18 Jul 2002, zhengchuanbo wrote:
> > i   replaced 'read-only' in lilo with 'read-write'. and it worked.
>
> No!  The file-system must be mounted read-only upon startup! There
> are exceptions in embedded systems and special systems that build
> file-systems (root file-system ram-disks) upon startup.

True.
in my previous mail i forgot to mention that it is not recommended to mount 
root read-write on startup...

> The init scripts should check the file-systems (using fsck) and
> then mount them read-write. If you (or init) executes fsck
> on r/w mounted file-systems, you may (read will) destroy them.
> Look in /etc/rc.d to see what happens upon startup. Something
> like `fsck -A -V -a` gets executed. Then, after than happens,
> something like `mount -n -o remount,rw /` gets executed. Then,
> to update /etc/mtab, somewhere there will be a `mount -f /`.

you really should check if this gets executed in one of your bootscripts and 
otherwise change them to do it this way.

	Rudmer

      reply	other threads:[~2002-07-18 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18 13:57 zhengchuanbo
2002-07-18 14:18 ` Richard B. Johnson
2002-07-18 16:57   ` Rudmer van Dijk [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=20020718165014Z318278-685+12831@vger.kernel.org \
    --to=rvandijk@science.uva.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=zhengcb@netpower.com.cn \
    /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

all inboxes | Powered by JetHome®