Bug #892
closed
loader.conf.local changes lost after nanobsd upgrade
Added by Chris Buechler about 14 years ago.
Updated almost 14 years ago.
Category:
Operating System
Description
Because of the way nanobsd functions, the usual method of putting loader.conf changes into loader.conf.local doesn't survive an upgrade. No easy work around I can think of, but would be nice to be able to retain such changes on nanobsd.
I thought somewhere we had a post-upgrade script that ran after the image was applied but I may be thinking of a full install. We could probably still do that on nano by running such a script from the newly imaged slice or copying it to /conf/ somewhere and doing it there.
Another solution could be to have some kind of mechanism to store the loader.conf changes in the config like the sysctls and make sure they get synchronized/written out before any reboot.
If there was such a mechanism, it would probably need to be synced to the other slice after an upgrade but before the reboot.
- Status changed from New to Feedback
- Target version changed from Future to 2.0
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by