Summary: | The disk changes are automatically partially reverted after the system rebooted | ||
---|---|---|---|
Product: | Base System | Reporter: | mom040267 |
Component: | kern | Assignee: | Mark Linimon <linimon> |
Status: | Closed Not A Bug | ||
Severity: | Affects Many People | CC: | emaste, junovitch |
Priority: | --- | ||
Version: | 10.1-RELEASE | ||
Hardware: | amd64 | ||
OS: | Any |
Description
mom040267
2015-07-21 15:40:58 UTC
I had a similar situation, again: 1) I downloaded an openssl tarball; 2) I compiled and installed it into /opt; 3) I recompiled my program with the new prefix pointing to /opt. 4) The I rebooted the system. The result: 1) The newerly compiled program is there, with library path pointing to /opt/ 2) /opt directory disappeared. 3) The directory where I compiled the openssl disappeared, too (~/c/tmp/openssl/openssl-1.0.2/). Something is very wrong going on. After investigation, I found that this is probably about the Update Manager in PC-BSD. In the background, it is finding and destroying the directories that update the openssl and libressl. That is a very dangerous and unpredictable feature, and it has to be removed. I turned off all automatic updates, but I think that the Update Manager as a whole must be totally removed from the system, it is itself behaves worser than any security bug. OK, I made an inventory of the damage. The "automatically" removed disk information is: 1) libressl is "automatically" downgraded from version 2.2.1 to 2.1.7 in /usr/local; 2) /opt directory with openssl 1.0.2d removed altogether; 3) All ports that were installed after libressl upgrade stopped working - because they were relying on libressl 2.2.1. That's an increadicly stupid behavior of the Updated Manager, that's just unbelievable. The workaround is turning it completely off - but a novice unsuspected user may spend several days trying to find out what is really wrong with the system. That's very user-unfriendly and dangerous. Hi. If you need to file a bug report against PC-BSD, see https://bugs.pcbsd.org/projects/pcbsd for their bug tracker. Since this feature is only in PC-BSD, not the base FreeSBD, you will need to open a ticket with them as mentioned. Sorry for the inconvenience. Thanks, I'll contact PC-BSD. Hardware updated to 'amd64' as that is probably intended based on context. |