From: Andreas Dilger <adilger@turbolabs.com>
To: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FW: [Cooker] rotflags and initrd
Date: Thu, 13 Sep 2001 00:37:38 -0600 [thread overview]
Message-ID: <20010913003738.F1541@turbolinux.com> (raw)
In-Reply-To: <000201c13c17$62c86860$21c9ca95@mow.siemens.ru>
In-Reply-To: <000201c13c17$62c86860$21c9ca95@mow.siemens.ru>
On Sep 13, 2001 09:46 +0400, Borsenkow Andrej wrote:
> > Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru> writes:
> > > If kernel mounts rootfs directly, you can pass mount options via
> > > rootflags boot parameter, like
> > >
> > > linux rootflags=data=journal
> >
> > the "rootflags" kernel parameter is not documented in
> > linux/Documentation/kernel-parameters.txt and I can find it in the
> > whole source only at one place. I'm not sure we should honour this.
>
> Just how "official" the parameter really is? The problem is, you want
> root on reiser to be in notail mode (if you boot off root - in any case,
> to avoid problems with bootloaders) and remounting reiser later AFAIK
> does not change tail conversion mode.
The rootflags parameter is only a part of the ext3 patch, AFAIK. It
is therefore probably in -ac kernels, but not stock Linus kernels.
Since it is useful by itself, it may be good to submit it as a patch
to Linus (this was done once along with the rootfstype= patch) but
I don't think it made it in.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-09-13 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 5:46 FW: [Cooker] rotflags and initrd Borsenkow Andrej
2001-09-13 6:37 ` Andreas Dilger [this message]
2001-09-13 6:45 ` Borsenkow Andrej
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=20010913003738.F1541@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.