From: Paulo Alcantara <paulo@paulo.ac>
To: Steve French <smfrench@gmail.com>, Jean Delvare <jdelvare@suse.de>
Cc: Lucas De Marchi <lucas.de.marchi@gmail.com>,
Harald Hoyer <harald@redhat.com>,
linux-modules@vger.kernel.org,
Pavel Shilovsky <pshilov@microsoft.com>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: multiple softdeps
Date: Mon, 01 Jul 2019 14:33:36 -0300 [thread overview]
Message-ID: <87v9wl8xsf.fsf@paulo.ac> (raw)
In-Reply-To: <CAH2r5ms=ZkpedmsBGLUwzE7tVvEw7wAr_kLm3PpVntX8_U9UCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Steve French <smfrench@gmail.com> writes:
>> Or we could decide that cifs in initrd is not supported?
>
> Paulo had been experimenting with booting from cifs.ko (over SMB3.11
> mounts to Samba).
>
> Presumably since SMB3/SMB3.11 family of protocols is the most common
> network file system across a pretty broad variety of operating systems
> it is easier to imagine it being extended for special cases like
> booting the OS (it is already very feature rich compared to most
> network/cluster file system protocols and has exhaustive detailed
> documentation).
>
> My gut reaction is that if cifs.ko (SMB3.11 mounts) don't work with
> initrd ... we need to fix that even if it means minor protocol
> extensions, but Paulo might have more data.
I was able to boot a Leap 15 system from cifs.ko with changes in [1], so
IMHO, it would probably make sense to support cifs in initrd as well --
though I haven't tested it myself.
Thanks,
Paulo
[1] https://git.paulo.ac/linux.git/commit/?h=smb-boot
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-07-01 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 13:16 multiple softdeps Harald Hoyer
2019-06-28 16:25 ` Lucas De Marchi
2019-06-29 9:30 ` Jean Delvare
2019-06-30 5:57 ` Steve French
2019-07-01 17:33 ` Paulo Alcantara [this message]
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=87v9wl8xsf.fsf@paulo.ac \
--to=paulo@paulo.ac \
--cc=harald@redhat.com \
--cc=jdelvare@suse.de \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=pshilov@microsoft.com \
--cc=smfrench@gmail.com \
/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).