Your message dated Sun, 19 Jan 2020 12:03:54 +0100 with message-id <[email protected]> and subject line Re: /etc/fstab.d has caused the Debian Bug report #928546, regarding /etc/fstab.d to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 928546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928546 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: util-linux Version: 2.29.2-1 Severity: normal Hi, As part of the hardening of an anonymity focused operating system called Whonix, we need to add different mount options for different filesystems e.g. hidepid=2 on /proc or noexec on /home. To make sure that a user's own fstab configurations are not messed up, we cannot use /etc/fstab for this. /etc/fstab.d would be the perfect thing for this but it seems that support for it has been [abandoned](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663623). Will support for this ever be brought back? If not, are there any good alternatives? Best regards.
--- End Message ---
--- Begin Message ---Hello, Trying to change a legacy interface like /etc/fstab would IMHO be a disaster without extensive planning. There are just too many different implementations all trying to parse this file separately. There is just no generic way to implement this without doing an insane amount of work, e.g. identify (via magic?) all programs that interface with /etc/fstab and then port them all over to use libmount parsing so a single implementation decide the implementation details. You can as others already pointed out in the referenced discussion implement this yourself if you want to and it works for your specific use-case. Either way, this should definitely not be attempted as a debian-specific change and I'm thus closing this bug report (which I previously tagged wontfix). Regards, Andreas Henriksson
--- End Message ---
