Jurij Smakov wrote:
Hi,
I believe that this problem arises due to a logic error in
print_message() function from second/misc.c, which is called to print
the boot banner. It supports substitution of some variables like
${ARCH} and ${PROM}, however if no such variables are found in the
text, it just scans through it and breaks out of the loop without
printing anything. The attached patch fixes the problem by ensuring
that the message is printed in the end. It works for me, would be
great if somebody else could confirm it.
You're right. I deduced the same after comparing the source tree for
silo-1.4.8 and silo-1.4.9. So, after downloadig and extracting the
source from, say, http://www.ultralinux.nl/silo/download/ and issuing
"diff -urN silo-1.4.8 silo-1.4.9 > silo-1.4.8_1.4.9.diff" I got the same
result (see file attached).
The question is, why did this change was introduced while upgrading from
1.4.8 to 1.4.9 in the first place? I can't tell now (it was done in
March, I believe). But maybe there is someone who knows better?
Of course, reversing this change would solve the original problem. And I
would love to see your proposed patch to be applied ASAP, with
consequent silo-1.4.10 release too.
Friendly,
Wiktor Wandachowicz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
