mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Andries.Brouwer@cwi.nl
Cc: mikeg@wen-online.de, viro@math.psu.edu, aeb@veritas.com,
	linux-kernel@vger.kernel.org, root@chaos.analogic.com
Subject: Re: Ramdisk (and other) problems with 2.4.2
Date: Fri, 9 Mar 2001 20:45:51 +0100	[thread overview]
Message-ID: <20010309204551.B17813@khan.acc.umu.se> (raw)
In-Reply-To: <UTC200103091923.UAA144612.aeb@vlet.cwi.nl>
In-Reply-To: <UTC200103091923.UAA144612.aeb@vlet.cwi.nl>; from Andries.Brouwer@cwi.nl on Fri, Mar 09, 2001 at 08:23:43PM +0100

On Fri, Mar 09, 2001 at 08:23:43PM +0100, Andries.Brouwer@cwi.nl wrote:
> > Andries, comments?
> 
> > remount
> >    Attempt  to  change the mount flags of
> >    already-mounted file system.  This is commonly
> >    used to make a readonly file system writeable.
> 
> Yes. But maybe "mount flags" is too narrow?
> It is up to the filesystem what precisely it does.
> What about
> 
> remount
>         Attempt to remount an  already-mounted  file
>         system.  This is commonly used to change the
>         mount flags for a file system, especially to
>         make  a  readonly  file system writeable. It
>         does not change device or mount point.

Why not emphasize the last sentence, and write

"It cannot change device or mount point." instead.


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  reply	other threads:[~2001-03-09 19:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-09 19:23 Andries.Brouwer
2001-03-09 19:45 ` David Weinehall [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-07 15:48 Richard B. Johnson
2001-03-07 17:01 ` Mike Galbraith
2001-03-07 17:23   ` Richard B. Johnson
2001-03-07 17:51     ` Mike Galbraith
2001-03-07 17:56       ` Richard B. Johnson
2001-03-07 18:56         ` Mike Galbraith
2001-03-07 17:53     ` matthew.copeland
2001-03-07 18:06       ` Richard B. Johnson
2001-03-08 11:44     ` Pavel Machek
2001-03-09 14:33     ` Mike Galbraith
2001-03-09 16:50       ` Mike Galbraith
2001-03-09 17:04       ` Richard B. Johnson
2001-03-09 18:28         ` Mike Galbraith
2001-03-09 18:38           ` Alexander Viro
2001-03-09 18:47             ` Mike Galbraith
2001-03-09 17:51       ` Alexander Viro
2001-03-09 18:26         ` Richard B. Johnson
2001-03-09 18:43         ` Mike Galbraith

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=20010309204551.B17813@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=aeb@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    --cc=root@chaos.analogic.com \
    --cc=viro@math.psu.edu \
    /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®