El mar, 11-07-2017 a las 16:03 -0500, Justin Forbes escribió: > > The kernel team quit "supporting" i686 several releases ago, it is > down to community support, which is pretty much nonexistent. Sure, > people file bugs, but rarely do people point to or supply patches for > those bugs. The biggest issue is how much it is ignored by upstream > as well. We have issues where things were never tested on i686, and > then have to be fixed before we can release necessary and relevant > updates which impact everyone else. And discontinuing the i686 > build > for F27 would still mean over a year left of supported Fedora on i686 > hardware. > When looking at those check ins, it would also be interesting to note > which of those are running on virt or containers. Containers would > still be possible, and 32bit userspace in virt guests with a 64bit > kernel would still be possible. The kernel header package would still > be built, so all other 32bit i686 packages would continue to build > and > work just fine. > > Justin For the record, the tooling to make base container images requires a running kernelof the given arch, and we currently have never attempted to make offical 32 bit x86 containers. so any container usage for i686 is done out in the ethers by people who care about it. we also stopped making 32 bit cloud images a few years back. slowly the 32 bit x86 deliverables have been going away. If the kernel was removed, the only deliverable we could do given current tooling, workflows and requirements would be an everything repo. Last time I tried to run a 32 bit userland with a 64 bit kernel yum at the time did not support the setup at all. I am not sure how much work would be needed to make things work correctly using a 32 bit userland and 64 bit kernel. Most of the support for that was removed when SPARC support was yanked from the tooling. So it is possible, it would require a significant investment in tooling, dnf, release tool chain updates. Given what is currently on release engineering plates its not work that could be accepted for us to do. Someone would have to volunteer to work with us to do the work and get the changes implemented. Dennis
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
