Hello,
I did a test upgrade from 11.2-RELEASE to 12.-RC3 and got these
warnings. They look mostly harmless, but mentioning them in case the
installer could do something to suppress them if this is the case.
% sudo freebsd-update -r 12.0-RC3 upgrade
% sudo freebsd-update install
[reboot]
% sudo freebsd-update install
Password:
src component not installed, skipped
Installing updates...install: chown 0:0 ///proc: Operation not supported
install: chmod 555 ///proc: Operation not supported
% grep proc /etc/fstab
proc /proc procfs rw 0 0
% sudo freebsd-update install
Password:
src component not installed, skipped
Installing updates...rmdir:
///var/db/etcupdate/current/usr/share/openssl/man/en.ISO8859-1:
Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/openssl/man: Directory not
empty
rmdir: ///var/db/etcupdate/current/usr/share/openssl: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/man/en.UTF-8: Directory not
empty
rmdir: ///var/db/etcupdate/current/usr/share/man/en.ISO8859-1: Directory
not empty
rmdir: ///var/db/etcupdate/current/usr/share/man: Directory not empty
I'm fairly certain that I got the /proc warning in the past for 11.0-RC
on the same system. Is the installation aware of and handling
mountpoints correctly?
Likewise the manpages:
% ls -l /var/db/etcupdate/current/usr/share/openssl/man/en.ISO8859-1
total 1
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man1 -> ../man1
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man3 -> ../man3
% ls -l /var/db/etcupdate/current/usr/share/man/en.UTF-8
total 5
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man1 -> ../man1
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man2 -> ../man2
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man3 -> ../man3
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man4 -> ../man4
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man5 -> ../man5
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man6 -> ../man6
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man7 -> ../man7
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man8 -> ../man8
lrwxr-xr-x 1 root wheel 7 15 Nov 2014 man9 -> ../man9
broken symlinks (self-referencing) in both cases. Not sure what has
made this happen now or at some time in the past, but it's certainly not
been due to manual intervention; this system has always been updated via
freebsd-update since back to 10.0. Should it be noticing and fixing
such broken links? Any ideas what caused them in the first place?
Regards,
Roger
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
