Project

General

Profile

Actions

Bug #8571

closed

loader.conf/.local cleanup is a bit too aggressive

Added by Jim Pingle almost 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Operating System
Target version:
Start date:
06/13/2018
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.x
Affected Architecture:
All

Description

We have code that cleans up and eliminates duplicate settings in loader.conf and loader.conf.local to avoid foot-shooting and to make sure that hardware works properly.

The code that checks/matches these values is a bit too aggressive and over-matches, and removes some values from loader.conf.local that it makes sense to allow a user to override.

The matching could be improved, and it could handle the local case slightly differently so that some values can be overridden by users.

Actions #1

Updated by Jim Pingle almost 4 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #2

Updated by Anonymous almost 4 years ago

On 2.4.4.a.20180705.0032 (SG-2440) added autoboot_delay=10 to /boot/loader.conf.local (which didn't exist before that), rebooted a couple of times with option 5 at console and the file remained with the contents unchanged. For the loader.conf part, saved settings on the System > Advanced page and after that the contents of /boot/loader.conf remained unchanged through a couple of reboots.

Actions #3

Updated by Jim Pingle almost 4 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF