I am sorry for this re-post. The crummy mailer I just used, cut some key text off. Here is the message in it's entirety. ------------------------------- Went for my second install of 6.4 on a new machine. This time, things did not go so smoothly. So far there have been three distinct problems: First, after you install initial packages off disk 1, Yast2 asks you to remove install media and it 'reboots', sort of. I had a Microsoft intella wheel mouse, and the yast2 screen locked up. No VT's could be accessed, and there was no response to the keyboard. I had to press reset, and all my e2fs partitions were thrashed. The happened THREE times in a row, until I replaced the MS wheel mouse with a Logic Tec three button PS/2 mouse. No more lockup. There was no indication of the mouse problem, it was just a guess. Two, after going through the 15,000 packages to install (that's what we all like about SuSE), you have an option to save your selections to a floppy. Now, at a later date, I wanted to reinstall everything from scratch. However, there was no option to re-read your selections from the floppy, saving you hours of package selection. What good is the save to floppy then? Third, this system had two ethernet cards and works as a firewall. I didn't re-compile the kernel, with hope SuSE would install modules as necessary. After modifying /etc/rc.config with the info on eth0 and eth1, then rebooted. Suse could not find eth0 but it did find eth1. Later on a shutdown, during 'shutting down eth0' the system completely hung. I waited optimistically, but gave up after a half hour or no activity. I pressed reset, and watched fsck do it's thing. After finally coming back to life, I compiled a good kernel, re-ran lilo and rebooted. The system hung again at the same place. I pressed reset and this time fsck could not repair the damage. I booted with a handy emergency repair floppy I've had for years. I ran fsck manually, and it seemed to repair the damage, but I cannot boot the kernel, and lilo does not re-write the master boot record, it returns an error. (I'm sorry that I'm not at the machine to report what the error said). I have decided to format the root partition and install everything again, using what I have learned about this system. It's too bad condition number two exists. That portion of the install is a serious pain. These are a few examples why Linux is not ready for prime time. -- Ryan Allen Software Engineer, Systems Integration Group. Cray Inc. 411 First Avenue South, Suite 600 Seattle, WA 98104-2860 -- Ryan Allen ryan@aa.net Web Mail services provided by http://www.aa.net -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/