Addendum to Tale of Woe

Sat Apr 13 00:26:08 EDT 2002

<x-html>
<html>
Thanks for the advice.. but lilo.conf mapping did not change, I can see
nothing changed on my end.. 
Here is my /etc/lilo.conf file: 
 
boot=/dev/hda 
map=/boot/map 
install=/boot/boot.b 
prompt 
timeout=0 
image=/boot/vmlinuz-2.2.13-4mdk 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; label=linux 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; root=/dev/hda1 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; read-only 
/etc/lilo.conf line 1/9 (END) 
 
[chaz at bleys chaz]$ ls /boot 
System.map@&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
boot.b&nbsp;&nbsp;
module-info@&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
vmlinuz@ 
System.map-2.2.13-4mdk&nbsp; chain.b&nbsp; module-info-2.2.13-4mdk&nbsp;
vmlinuz-2.2.13-4mdk 
boot.0300&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
map&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; os2_d.b 
 
As you can see, /boot/map is still there, it is a binary file.. cant read
it 
not sure what boot.b is for.. but it is binary also. 
 
Everything 'seems' in order.. just that something isn't quite
right.. 
 
On the bright side.. took LPI level 1 test 101 today, passed.&nbsp; GOD,
do they ask about some of the most unused commands.. or at least my test
had a bunch that I have never had to use before.. LOL 
 
Chaz® 
 
 
At 08:56 AM 4/12/02 -0400, you wrote: 
<blockquote type=cite class=cite cite>There was no &quot;magic&quot;
involved. I was changing files and rerunning lilo and that's what I
noticed had happened. I don't recall exactly what steps were taken that
caused it but I, much like our friend here, once was changing hard drives
around and rerunning lilo and I noticed that the lines in the lilo.conf
file; 
map-drive=0x80 
to=0x82 
map-drive=0x82 
to=0x80 
were changed. I don't have that machine here anymore and that may not be
the exact syntax but those were the lines that were changed (8?) and when
I changed them back to the original mapping, lilo booted ok. 
On systems with multiple drives and changing master/slaves back and forth
and rerunning lilo, as our friend was doing, I don't think it would take
&quot;magic&quot; for that to get changed and I thought it would be a
good place for our friend to look to solve his problem. 
 
On Fri, 2002-04-12 at 08:19, Robert Dege wrote: 
<dl><pre>
<dd>&gt; I had something similar happen and was waiting to see the
response you

<dd>&gt; gave from the other advise given. This may be irrelevant to you
because

<dd>&gt; of your particular situation and I haven't been following that
closely

<dd>&gt; but when a similar problem happened to me, I noticed that the
line map=?

<dd>&gt; for drives in the /etc/lilo.conf files were not the same as when
I

<dd>&gt; previously had it. Luckily I had a copy of my original lilo.conf
file

<dd>&gt; and compared. When I put it back to the way it originally was, I
booted

<dd>&gt; OK. Just throwin this out there for ya, if it works,
great

<font face="Courier New, Courier" color="#737373">
<dd>Seems odd that the lilo.conf file would just &quot;magically&quot;
modify itself,</i></font>
<font face="Courier New, Courier" color="#737373">
<dd>but I guess that would depend upon the distro you're
using.</i></font>

<font face="Courier New, Courier" color="#737373">
<dd>Perhaps a viewing of the lilo.conf is in order.</i></font>

<font face="Courier New, Courier" color="#737373">
<dd>Dege</i></font>

<dd>So Many Things in Life Would Be Really Funny

<dd>.... If They Weren't Happening To Me
</pre>
</dl></blockquote></html>
</x-html>