Re: Discussion: what would not blocking on btrfs look like?

--===============0986658426038742660==
Content-Type: multipart/alternative; boundary="000000000000fd60270591088e15"

--000000000000fd60270591088e15
Content-Type: text/plain; charset="UTF-8"

On Mon, Aug 26, 2019 at 4:53 PM Kamil Paral <[email protected]> wrote:

> On Mon, Aug 26, 2019 at 2:42 PM Justin Forbes <[email protected]>
> wrote:
>
>> From my standpoint, ext4 and xfs are the primary supported root
>> filesystems. I don't think that anything else should be release
>> blocking.
>
>
> If this is the case, we can explicitly list the supported file systems in
> criteria. The list would need to be extended with at least vfat, which is
> used for ESP, though.
>
> If we go this route, it would be nice to communicate this somehow to the
> end user, directly in anaconda interface. Either by showing a warning when
> a "not officially supported" filesystem is selected, or by hiding those
> filesystems in dialogs when creating a new partition (with a documented
> override).
>

Hmm, I don't see this as necessary. I think changing criterions on what
file systems are blocking doesn't mean we need to hide things or add some
ugly warnings. Anybody who uses advanced partitioning should know what is
doing, we can just update criterions so not everything visible in advanced
partitioning must work and is supported.


> Existing partitions still need to be handled somehow, so the warning bar
> might need to be implemented in any case (warn that the existing partition
> is unsupported by allow to use it, or warn that the existing partition
> can't be used unless the override is activated).
>

I am -1 on this. I just somehow hate the idea of showing warnings and/or
adding some blocks and overrides. We weren't testing on unsupported/other
file systems anyway (correct me if I am mistaken), so what's the difference
now?

--000000000000fd60270591088e15
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Aug 26, 2019 at 4:53 PM Kamil=
 Paral &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Mon, Aug 26, 2019 at 2:42 PM Justin Forbes &lt;<a href=3D"mailto:jmforbes=
@linuxtx.org" target=3D"_blank">[email protected]</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">From my standpoint, ext=
4 and xfs are the primary supported root<br>
filesystems. I don&#39;t think that anything else should be release<br>
blocking. </blockquote><div><br></div><div>If this is the case, we can expl=
icitly list the supported file systems in criteria. The list would need to =
be extended with at least vfat, which is used for ESP, though.</div><div><b=
r></div><div>If we go this route, it would be nice to communicate this some=
how to the end user, directly in anaconda interface. Either by showing a wa=
rning when a &quot;not officially supported&quot; filesystem is selected, o=
r by hiding those filesystems in dialogs when creating a new partition (wit=
h a documented override). </div></div></div></blockquote><div><br></div><di=
v>Hmm, I don&#39;t see this as necessary. I think changing criterions on wh=
at file systems are blocking doesn&#39;t mean we need to hide things or add=
 some ugly warnings. Anybody who uses advanced partitioning should know wha=
t is doing, we can just update criterions so not everything=C2=A0visible in=
 advanced partitioning must work and is supported.</div><div>=C2=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=
=3D"gmail_quote"><div>Existing partitions still need to be handled somehow,=
 so the warning bar might need to be implemented in any case (warn that the=
 existing partition is unsupported by allow to use it, or warn that the exi=
sting partition can&#39;t be used unless the override is activated).</div><=
/div></div></blockquote><div><br></div><div>I am -1 on this. I just somehow=
 hate the idea of showing warnings and/or adding some blocks and overrides.=
 We weren&#39;t testing on unsupported/other file systems anyway (correct m=
e if I am mistaken), so what&#39;s the difference now?</div></div></div>

--000000000000fd60270591088e15--

--===============0986658426038742660==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdGVzdCBtYWls
aW5nIGxpc3QgLS0gdGVzdEBsaXN0cy5mZWRvcmFwcm9qZWN0Lm9yZwpUbyB1bnN1YnNjcmliZSBz
ZW5kIGFuIGVtYWlsIHRvIHRlc3QtbGVhdmVAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmcKRmVkb3Jh
IENvZGUgb2YgQ29uZHVjdDogaHR0cHM6Ly9kb2NzLmZlZG9yYXByb2plY3Qub3JnL2VuLVVTL3By
b2plY3QvY29kZS1vZi1jb25kdWN0LwpMaXN0IEd1aWRlbGluZXM6IGh0dHBzOi8vZmVkb3JhcHJv
amVjdC5vcmcvd2lraS9NYWlsaW5nX2xpc3RfZ3VpZGVsaW5lcwpMaXN0IEFyY2hpdmVzOiBodHRw
czovL2xpc3RzLmZlZG9yYXByb2plY3Qub3JnL2FyY2hpdmVzL2xpc3QvdGVzdEBsaXN0cy5mZWRv
cmFwcm9qZWN0Lm9yZwo=

--===============0986658426038742660==--