Hi,
On 11-07-17 22:57, Josh Boyer wrote:
On Tue, Jul 11, 2017 at 4:41 PM, Dominik 'Rathann'
Mierzejewski
<dominik(a)greysector.net> wrote:
> On Tuesday, 11 July 2017 at 22:26, Florian Weimer wrote:
>> I ran into this unannounced change:
>>
>>
https://fedoraproject.org/wiki/Changes/Stop_Building_i686_Kernels
>
> I noticed this is categorized as self-contained, which I think is wrong.
>
> I also have hardware that would no longer run Fedora after such change
> (a netbook with an older Intel Atom CPU which supports SSE2, but is
> 32bit). Unless the change proponent can provide some numbers suggesting
> that 32bit users are a tiny minority of our userbase, I'll probably
> be against such change.
Anyone with 32-bit hardware is going to be against this change. It is
a known downside. It also doesn't change the fact that i686 kernels
are in a zombie state, where the kernel team does not actively support
them and the community has not significantly stepped up to do so.
I still have (some) 32 bit hardware in use and I must say that I was
not aware of this zombie state. i686 kernels have been working fine for
me otherwise I would have likely stepped up to fix things (or if that
was too much work replace my last 32bit hardware), but I may just have
been lucky and never hit a bad kernel.
If the kernel team wants some specific help with ia32 support then
2 things need to happen:
1) A clear request for help needs to be send
2) What exactly they need help with needs to be clearly defined
Also this is plainly false advertising:
== Upgrade/compatibility impact ==
32bit i686 users will need to reinstall as x86_64 with the next release.
Nope, 32 bit i686 users are just plain out of luck, unless they
have a 64 bit capable CPU but are still running a 32 bit OS for some
reason (yes I'm aware this is mentioned later, but it clearly
belongs under this header).
Last as others have said, this is _clearly_ a systemwide change
and the deadline for systemwide change proposals for F27 was July
4th, where as this page was created July 6th, moreover a change as
big as this really needs to be discussed out in the open long before
it gets implemented rather then hidden away in a Changes page.
Regards,
Hans