From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arvind Sankar Subject: Re: [RFC PATCH] rootfs: force mounting rootfs as tmpfs Date: Wed, 31 Jan 2018 21:03:32 -0500 Message-ID: <20180201020331.GA3774@rani.riverdale> References: <1517348777.3469.5.camel@linux.vnet.ibm.com> <1814af5c-170d-39c0-58fd-02eb7216e008@landley.net> <1517436423.3469.237.camel@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: Sender: initramfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: Rob Landley Cc: Mimi Zohar , initramfs , Taras Kondratiuk , Victor Kamensky , linux-security-module , Al Viro , linux-kernel 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 con= figured 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?) > >=20 > > I must be missing something. =C2=A0Which systems don't specify "root=3D= " on > > the boot command line. >=20 > Any system using initrd or initramfs? >=20 Don't a lot of initramfs setups use root=3D to tell the initramfs which actual root file system to switch to after early boot?