Package: silo
Version: 1.4.8-1
Severity: normal
I have a Debian sarge installed on Sun Blade 150 (sun4u sparc64
processor). Recently an update to silo 1.4.9 has been provided
n the Debian archives. Alas, there seems to be a regression bug.
With silo 1.4.8 I have used a following configuration:
===== silo.conf BEGIN =====
root=/dev/hda5
partition=1
message=/boot/silo_message
default=linux
read-only
timeout=500
image=/boot/vmlinuz-2.4.26-sparc64
label=linux
other=4
label=solaris
===== silo.conf END =====
This is a multiboot machine (Solaris 9 + Debian sarge), and I wanted
the users to be notified about some administrative details. That is
why I have put a "message=/boot/silo_message" line in the silo.conf
file. After updating to silo 1.4.9 the message is no longer displayed.
For a short while I was trying to specify another file (with different
name), but I made a typo. At that point silo warned me that it was
nable to find that file with misspelled name. After the correction
the message is not being displayed upon boot. With silo 1.4.8 it worked.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: sparc (sparc64)
Kernel: Linux 2.4.26-sparc64
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Versions of packages silo depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
