Bug 7270 - syntax error in setsysfont portion of initscripts-4.67-1 (with fix)
syntax error in setsysfont portion of initscripts-4.67-1 (with fix)
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
: 7285 7410 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-11-23 21:24 EST by mashton
Modified: 2014-03-16 22:11 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-11-23 23:31:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description mashton 1999-11-23 21:24:21 EST
bug shows up as "[: argument expected" on bootup.

from /etc/rc.d/rc.sysinit:
Is:

# Load system font
if [ -x /sbin/setsysfont ]; then
    [ -f /etc/sysconfig/i18n ] && . /etc/sysconfig/i18n
    if [ -f /etc/sysconfig/console/$SYSFONT.psf.gz -o \
         -f /usr/lib/kbd/consolefonts/$SYSFONT.psf.gz -o \
         -f /etc/sysconfig/console/$SYSFONT.gz -o \
         -f /usr/lib/kbd/consolefonts/$SYSFONT.gz -o ]; then
--- problem is here ------------------------------^^^

should be:

# Load system font
if [ -x /sbin/setsysfont ]; then
    [ -f /etc/sysconfig/i18n ] && . /etc/sysconfig/i18n
    if [ -f /etc/sysconfig/console/$SYSFONT.psf.gz -o \
         -f /usr/lib/kbd/consolefonts/$SYSFONT.psf.gz -o \
         -f /etc/sysconfig/console/$SYSFONT.gz -o \
         -f /usr/lib/kbd/consolefonts/$SYSFONT.gz ]; then


did no one even boot this??
Comment 1 Bill Nottingham 1999-11-23 23:31:59 EST
Blarg. initscripts-4.68-1, in the errata as we speak.
Comment 2 Bill Nottingham 1999-11-29 11:13:59 EST
*** Bug 7285 has been marked as a duplicate of this bug. ****** Bug 7410 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.