[Bug 241101] i915kms working with 12.0 but not 12.1-BETA3

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241101

--- Comment #14 from Tomasz "CeDeROM" CEDRO <tomek at cedro.info> ---
Hey Niclas :-)

My "not fixed" was response to  Vincent DEFERT 2019-11-04 19:32:26 UTC /
Status: New → Closed / Resolution: --- → FIXED.

> No one has claimed this  has been fixed.  Byt keeping track of which ports
> need to be installed from ports, and which from packages, must be done by
> the person administrating the system.

Negative. Providing malicious PKG that WILL CRASH the system and lead to
DESTROY ITS DATA is the responsibility of the package creator, committer and
maintainer. Also the FreeBSD Core Team NOT to allow such situation to happen.
If there is such _risk_ it should not land in production/release! Now we have
such _existing_situation_ in the production systems! Really not cool :-(

User / Admin hits the `pkg update upgrade` on a _PRODUCTION_ system with an
official production packages so it gets a production system updated and
working.

We cannot get with FreeBSD to a Linux mindset where user needs to perform
additional 472847824 tasks to make things work. It never happened before and I
really hope it never will.

> I would also like to ask a question, how would you go about this?

The answer is above. The situation should never happen. Do not push the
bleeding edge into the production. Block all known issues in a way they would
not happen on a production system.

1. Remove DRM-KMOD out of PKG at all until there is a working solution. Leaving
it in PKG causes production systems to crash. What more evidence do you need?

2. Do not allow Linux like programming where API changes from release to
release into FreeBSD Kernel. I am sure most users are good to wait for quality
code rather than bleeding edge Kernel. We avoid Linux for that reason.

Cheers :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.