[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1517458921.3329.2.camel@linux.vnet.ibm.com>
Date: Wed, 31 Jan 2018 23:22:01 -0500
From: Mimi Zohar <zohar@...ux.vnet.ibm.com>
To: Arvind Sankar <nivedita@...m.mit.edu>,
Rob Landley <rob@...dley.net>
Cc: initramfs <initramfs@...r.kernel.org>,
Taras Kondratiuk <takondra@...co.com>,
Victor Kamensky <kamensky@...co.com>,
linux-security-module <linux-security-module@...r.kernel.org>,
Al Viro <viro@...IV.linux.org.uk>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] rootfs: force mounting rootfs as tmpfs
On Wed, 2018-01-31 at 21:03 -0500, Arvind Sankar wrote:
> 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?
With your patch and specifying "root=tmpfs", dracut is complaining:
dracut: FATAL: Don't know how to handle 'root=tmpfs'
dracut: refusing to continue
Mimi
Powered by blists - more mailing lists