Re: /sbin/lilo - segmentation fault
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
Re: /sbin/lilo - segmentation fault
thought it might be a bogus lilo. script is a handy way to capture a console session to a file, and I wanted to remind you of that, too. Or you could have said, lilo -v file_to_include_in_the_mail (bash only, other shells like "file 21", which bash also likes). That way you don't make typos. :-) Problem was that the troublesome machine is elsewhere, and not on line, so pasting impossible unless I happened to remember to bring along a diskette. As it was, I scribbled notes with a pencil on scrap paper, so the problem was more illegible handwriting than a type. ;-( 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 can't remember the space I gave /boot, and adding the various images might have made it crowded. I'll follow your suggestion. This machine was a cheap box with Windows on it, and I wondered if there's trouble in the MBR due to contamination by the previous resident. Yet I can install the old lilo.conf, and so perhaps not. Haines - 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
Re: /sbin/lilo - segmentation fault
At 12:06 AM 8/8/00 EDT, [EMAIL PROTECTED] wrote: 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? That said, I've never seen lilo segfault either. -- "Never tell me the odds!"--- Ray Olszewski-- Han Solo Palo Alto, CA[EMAIL PROTECTED] - 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
Re: /sbin/lilo - segmentation fault
As you can see, lilo version 21 has no particular trouble with multiple images. Where did you get lilo version 2.1? I met lilo about 5 years ago at version 18. version 2.1 must have been before Werner Almesberger started working on it. I must say he has done a great job. Lawson Lawson, Sorry for the typo (2.1). I realize lilo can handle multiple images, but can't imagine how or why running the lilo command on a configuration file that only has appended a simple additional stanza can result in a segmentation fault. Haines - 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
