Project

General

Profile

Actions

Bug #892

closed

loader.conf.local changes lost after nanobsd upgrade

Added by Chris Buechler about 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Operating System
Target version:
Start date:
09/15/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

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.

Actions #1

Updated by Jim Pingle about 11 years ago

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.

Actions #2

Updated by Erik Fonnesbeck about 11 years ago

If there was such a mechanism, it would probably need to be synced to the other slice after an upgrade but before the reboot.

Actions #3

Updated by Erik Fonnesbeck about 11 years ago

  • Status changed from New to Feedback
  • Target version changed from Future to 2.0
Actions #4

Updated by Chris Buechler almost 11 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF