Date: Tue, 17 Sep 2019 19:34:25 +0100 From: "Dr. David Alan Gilbert" Message-ID: <20190917183425.GJ3370@work-vm> References: <20190906100324.8492-1-stefanha@redhat.com> <20190909070039.GB13708@stefanha-x1.localdomain> <20190917183029.GH1131@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190917183029.GH1131@ZenIV.linux.org.uk> Subject: Re: [Virtio-fs] [PATCH] init/do_mounts.c: add virtiofs root fs support List-Id: Development discussions about virtio-fs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Al Viro Cc: Miklos Szeredi , Richard Weinberger , David Howells , linux-fsdevel , virtio-fs@redhat.com, Vivek Goyal * Al Viro (viro@zeniv.linux.org.uk) wrote: > On Tue, Sep 17, 2019 at 08:19:55PM +0200, Richard Weinberger wrote: > > > mtd, ubi, virtiofs and 9p have one thing in common, they are not block devices. > > What about a new miscroot= kernel parameter? > > How about something like xfs!sda5 or nfs!foo.local.net/bar, etc.? With > ubi et.al. covered by the same syntax... Would Stefan's patch work if there was just a way to test for non-block based fileystsmes and we replaced !strcmp(root_fs_names, "virtiofs") by not_block_based_fs(root_fs_names) Or is there some magic that the other filesystems do that's specific? Dave > _______________________________________________ > Virtio-fs mailing list > Virtio-fs@redhat.com > https://www.redhat.com/mailman/listinfo/virtio-fs -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK