Bug 140261 - [patch] Improve flexibility of mdconfig2 startup script
Summary: [patch] Improve flexibility of mdconfig2 startup script
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2009-11-04 04:20 UTC by Brian Scott
Modified: 2017-12-31 22:32 UTC (History)
0 users

See Also:

file.diff (431 bytes, patch)
2009-11-04 04:20 UTC, Brian Scott
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Scott 2009-11-04 04:20:01 UTC
Configuring memory disk devices currently requires that the devices are numbered consecutively from 0 to be actioned during system startup by the mdconfig2 script. The first non-existent device number signals the end of the list.

Subsequent removal of a device from rc.conf requires others to be renumbered to remove any gaps and fstab entries need to be adjusted to match the updated device numbers.

This proposal is to (optionally) use a list to name those devices you want attached at startup.

The current version of the script allows you to specify exactly this behavior:
_mdconfig2_list="md23 md47 md5"
This appears to be an unintended feature, the leading _ suggesting a private variable that isn't meant to be set.

The proposed change introduces a new variable without the leading _ such that the existing behavior is maintained (use devices from 0 upwards until not found) if the setting isn't used. The private variable is still used to build a dynamic list or hold command line arguments.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-11-05 07:23:45 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-rc

affects one of the rc scripts.
Comment 2 Garrett Cooper 2012-01-02 12:02:48 UTC
Please refer to conf/122477 for a patch that does what you want.
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:43 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped