https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241787
Denis Polygalov <dpo...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dpo...@gmail.com
--- Comment #9 from Denis Polygalov <dpo...@gmail.com> ---
>From naive user's point of view this problem can be described as 'bad user
experience' when executing action according to the documentation
(# freebsd-update -r XX.X-RELEASE upgrade) lead to a dead system.
Very rough estimation shows that this problem can be potentially
triggered by any of ~56 ports:
# find /usr/ports -type f -name Makefile|xargs cat|grep USES|grep kmod|wc -l
Moving graphics/drm entirely into ports (e.g. no binary packages for users)
will kick back FreeBSD into stone age and discard all enormous and amazing
work done by graphics team (IMHO).
How about *in addition* to whatever solution will be found for the
graphics/drm package change behavior of 'freebsd-update'?
Well, strictly speaking - pitch such idea to mainstream FreeBSD developers?
If user execute 'freebsd-update -r XX.X-RELEASE upgrade' the script analyze
current content of /etc/rc.conf and /boot/loader.conf and detect
presence of configuration that includes loading of 3rd-party modules
(any kernel module not shipped with the base system).
If such presence is detected - freebsd-upgrade print warning message
and exit (refuse to execute upgrade) until user disable 3-rd party
modules in his/her config files or specify new argument such as:
# freebsd-update -r XX.X-RELEASE --UNSAFE upgrade
Doing this will eliminate unintentional unsafe upgrade and
mitigate possible bad UX.
Regards,
Denis
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
