Do I understand it right that with the update of /etc/conf.d/bootmisc in probably the latest version of baselayout I *could* have lost all my data in /tmp after reboot?
If so, I'm *really* angry that this was never mentioned anywhere and I needed to find this out by carefully inspecting the etc-update. I think this options should have been announced! (No I did not lost any data, but I don't want to be a user that noticed this and say: "haha, rotflol, you didn't!" to anyone that pressed -5.
Storing data that you don't want to lose in /tmp is erm... not smart, mildly said. And yeah, CONFIG_PROTECT is there for a reason.
(In reply to comment #1)
> Storing data that you don't want to lose in /tmp is erm... not smart, mildly
> said. And yeah, CONFIG_PROTECT is there for a reason.
"FHS added this recommendation on the basis of historical precedent and common practice, but did not make it a requirement because system administration is not within the scope of this standard."
This is changing *fundamental* behavior and can cause data loss to anyone who is storying anything in /tmp. I think this change from NO to YES should be announced and not be silently applied. I hope you will personally reopen it and assign it. Or make sure this is announced in an official Gentoo mailing.
Please, take this out of bugzilla, there's totally no bug here. Stuff that's supposed to persist across reboots does *not* belong to /tmp. There's CONFIG_PROTECT for configuration changes so noone silently applied anything. Don't really see what do you want to announce here.