Date: Sat, 22 Feb 1997 19:36:31 GMT From: Nik Clayton <nik@blueberry.co.uk> To: FreeBSD-gnats-submit@freebsd.org Subject: i386/2802: 2.1.7: Bug in /etc/rc prevents running of rc.i386 Message-ID: <199702221936.TAA00481@coconut.blueberry.co.uk> Resent-Message-ID: <199702221940.LAA08385@freefall.freebsd.org>
index | next in thread | raw e-mail
>Number: 2802
>Category: i386
>Synopsis: /etc/rc expects /etc/rc.i386, actually /etc/etc.i386/rc.i386
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Feb 22 11:40:01 PST 1997
>Last-Modified:
>Originator: Nik Clayton
>Organization:
>Release: FreeBSD 2.1.7-RELEASE i386
>Environment:
2.1.7-RELEASE, obtained by supping RELENG_2_1_0 and making the
world
>Description:
2.1.5 had an /etc/rc.i386 file. By 2.1.7 this had changed to become
the directory /etc/etc.i386, which contains disktab, MAKEDEV and
rc.i386.
In 2.1.5, rc.i386 was run by /etc/rc with this piece of code
# configure implementation specific stuff
arch=`uname -m`
if [ -f /etc/rc.${arch} ]; then
. /etc/rc.${arch}
fi
This same code is used in /etc/rc for 2.1.7. However, because
/etc/rc.i386 no longer exists, it's not run at startup.
I first noticed this when my keymappings (for a uk.cp850)
vanished after upgrading.
>How-To-Repeat:
Look at /etc/ in RELENG_2_1_0
>Fix:
Quickest fix is to replace the code above with
# configure implementation specific stuff
arch=`uname -m`
if [ -f /etc/etc.${arch}/rc.${arch} ]; then
. /etc/etc.${arch}/rc.${arch}
fi
which simply extends the search. However, if you've already
specified the architecture with the directory name (etc.i386),
would it not be cleaner to have /etc/etc.i386/rc?
>Audit-Trail:
>Unformatted:
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702221936.TAA00481>