[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1517500500.3974.45.camel@linux.vnet.ibm.com>
Date: Thu, 01 Feb 2018 10:55:00 -0500
From: Mimi Zohar <zohar@...ux.vnet.ibm.com>
To: Rob Landley <rob@...dley.net>,
Arvind Sankar <nivedita@...m.mit.edu>
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 Thu, 2018-02-01 at 09:20 -0600, Rob Landley wrote:
> > With your patch and specifying "root=tmpfs", dracut is complaining:
> >
> > dracut: FATAL: Don't know how to handle 'root=tmpfs'
> > dracut: refusing to continue
>
> [googles]... I do not understand why this package exists.
>
> If you're switching to another root filesystem, using a tool that
> wikipedia[citation needed] says has no purpose but to switch to another
> root filesystem, (so let's reproduce the kernel infrastructure in
> userspace while leaving it the kernel too)... why do you need initramfs
> to be tmpfs? You're using it for half a second, then discarding it,
> what's the point of it being tmpfs?
Unlike the kernel image which is signed by the distros, the initramfs
doesn't come signed, because it is built on the target system. Even
if the initramfs did come signed, it is beneficial to measure and
appraise the individual files in the initramfs.
> Sigh. If people are ok with having rootfs just be tmpfs whenever tmpfs
> is configured in, even when you're then going to overmount it with
> something else like you're doing, let's just _remove_ the test. If it
> can be tmpfs, have it be tmpfs.
Very much appreciated!
thanks,
Mimi
Powered by blists - more mailing lists