> >I don't know how to make lilo segment fault, so I don't know how to fix
> >it. Could you be dead flat out of space in /boot? I would expect that
> >to get error 28, but maybe not. df to see.
>
> I wouldn't expect a segfault from that problem either. More likely prospects
> are:
>
> 1. A libraries problem (lilo uses libc6, so there's always potential for a
> glibc2.0 vs 2.1 problem).
>
> 2. Bad memory. Subtle weaknesses in memory produce a lot of weird symptoms,
> including segfaults. Never seen it with lilo specifically, but why not?
Ray,
Well, I checked the partition size, and I know I've no libraries
problem. So I started with my old lilo.conf, added a second duplicate
stanza; no problem, Then I changed the label; no problem. Then I
pointed to the new kernel; no problem.
I have to confess, the problem simply disappeared! I look at the two
versions of lilo.conf, and they look identical, but obviously are
not. Wonder if I have a carriage return or something messing things
up.
In any case, thanks for your and Lawson's patience.
Haines Brown
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
