On Fri, 2005-11-18 at 09:20 -0600, akonstam@xxxxxxxxxxx wrote: > There is a lesson in all this. FC4 installs well on many > architectures. > We have it installed on at least 5 different architectures going form > state of the art to obsolete. A custom install sill allow you do do > much of what you want to do in most cases. > > That yours bombs out is frustrating but needs to investigated as to > why it is bombing out not just to go to another installation scheme at > random. > > That is my opinion and I am sticking to it. I have had it go fine on some PCs, and others it drove me around the twist. Now I can understand that some obscure hardware might be hard to support, but I view that as an after-the-installation problem. Not the installer script dying before installation really begins. The installer script ought to run on all systems with enough RAM. The systems were given a gruelling memtest86 trial. They've worked for months, sometimes years, with prior Linux installs, and the current installs. It just seems to be some issue with the installing. I've custom picked things to install, it's died. I've gone back and picked the same things, and it's worked. It's extremely frustrating. The thing is, though, where to debug this. An uninstalled system doesn't give you any easy way to save a log file, particularly if you only have a CD-ROM and hard drive in the box. And there's a plethora of options for what you install, giving a large number of possible failure points (and variables for what's really at fault). -- Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
