Subject: misc/11971: 1.5Q /etc/rc.d/amd is not backward compatible with the past behavior
To: None <gnats-bugs@gnats.netbsd.org>
From: None <itojun@itojun.org>
List: netbsd-bugs
Date: 01/15/2001 19:16:25
>Number: 11971
>Category: misc
>Synopsis: 1.5Q /etc/rc.d/amd is not backward compatible with the past behavior
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: misc-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Jan 15 19:16:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Jun-ichiro itojun Hagino
>Release: 1.5Q
>Organization:
itojun.org
>Environment:
System: NetBSD starfruit.itojun.org 1.5Q NetBSD 1.5Q (STARFRUIT) #318: Sat Jan 13 22:05:36 JST 2001 itojun@starfruit.itojun.org:/usr/home/itojun/NetBSD/src/sys/arch/i386/compile/STARFRUIT i386
Architecture: i386
Machine: i386
>Description:
backward-incompatible change was made to etc/rc.d/amd between
1.5 and 1.5Q (I don't have connectivity to cvs.netbsd.org right now
so i can't check the exactrevision).
$amd_flags and $amd_master has been used (see 1.5 and 1.4.3
/etc/rc.conf), but the latest etc/rc.d/amd ignores them.
>How-To-Repeat:
update /etc/rc.d, go into trouble.
>Fix:
either of the following two. I believe 2. is possible.
1. at least rc.d/amd should warn about the change, if
$amd_{flags,master} are still set (like "THESE TWO VARIABLES
WILL BE IGNORED")
2. implement backward compatible behavior.
>Release-Note:
>Audit-Trail:
>Unformatted: