linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: nivedita@alum.mit.edu (Arvind Sankar)
To: linux-security-module@vger.kernel.org
Subject: [RFC PATCH] rootfs: force mounting rootfs as tmpfs
Date: Wed, 31 Jan 2018 21:03:32 -0500	[thread overview]
Message-ID: <20180201020331.GA3774@rani.riverdale> (raw)
In-Reply-To: <a538e55c-81ca-6d59-20cf-21b47387c3e2@landley.net>

On Wed, Jan 31, 2018 at 05:48:20PM -0600, Rob Landley wrote:
> On 01/31/2018 04:07 PM, Mimi Zohar wrote:
> > On Wed, 2018-01-31 at 13:32 -0600, Rob Landley wrote:>> (The old "I configured in tmpfs and am using rootfs but I want that
> rootfs
> >> to be ramfs, not tmpfs" code doesn't seem to be a real-world concern, does
> >> it?)
> > 
> > I must be missing something. ?Which systems don't specify "root=" on
> > the boot command line.
> 
> Any system using initrd or initramfs?
> 

Don't a lot of initramfs setups use root= to tell the initramfs which
actual root file system to switch to after early boot?
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-02-01  2:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 21:46 [RFC PATCH] rootfs: force mounting rootfs as tmpfs Mimi Zohar
2018-01-31 19:32 ` Rob Landley
2018-01-31 22:07   ` Mimi Zohar
2018-01-31 23:48     ` Rob Landley
2018-02-01  2:03       ` Arvind Sankar [this message]
2018-02-01  4:22         ` Mimi Zohar
2018-02-01 15:20           ` Rob Landley
2018-02-01 15:55             ` Mimi Zohar
2018-02-01 17:09               ` Rob Landley
2018-02-01 21:51                 ` Mimi Zohar
2018-02-01 22:41                   ` Taras Kondratiuk
2018-02-01 23:34                     ` Rob Landley
2018-04-16 15:46                       ` Mimi Zohar
2018-02-01 22:46           ` Rob Landley

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=20180201020331.GA3774@rani.riverdale \
    --to=nivedita@alum.mit.edu \
    --cc=linux-security-module@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).