As discussed in bug 477498 it's not clear that having the link is worse than not having it: having the link looks to cause problems with "unmounting user mounts", but I see no reference to that problem on *recent* systems. And other distributions are using the link for a long time without this issues hurting them. On the other hand, not creating the link will cause tools like mount and df to not work properly. I would then drop this: if [[ ! -L "${ROOT}"/etc/mtab ]]; then ewarn "Upstream suggests that the /etc/mtab file should be a symlink to /proc/mounts." ewarn "It is known to cause users being unable to unmount user mounts. If you don't" ewarn "require that specific feature, please call:" ewarn " $ ln -sf '${ROOT}proc/self/mounts' '${ROOT}etc/mtab'" ewarn fi As looks to indicate you will get problems creating the link (that is the opposite as most people will will see) -> We should try to get people using the symlink and, if there is a specific case of this causing any problems with current systems and recent kernels, document it in Troubleshooting section of the wiki page. (I think we should even create the symlink from sys-apps/systemd ebuild if baselayout keeps not doing it) Thanks
Feel free to reword that :).
+ 28 Aug 2013; Pacho Ramos <pacho@gentoo.org> systemd-204.ebuild, + systemd-206-r3.ebuild: + Update message about /etc/mtab link (#482786), show message about systemd-ui + only when package is not installed (#480606) +
