Sam Daniel wrote:
I'm using SuSE 5.2 on 5 ALR Revolution 6x6 servers (each with 4 Pentium Pros, 512MB RAM,4x4.3GB HDs). It's important that all 5 be identical. In 5.2 I configured the 1st install by hand and saved the result to a floppy. YaST asked for the floppy before showing me the different load configurations, and asked if I wanted to save my config file to hard disk or floppy. I used the floppy to load the config file into each of the other 4 systems, and YaST installed exactly the same stuff on each one.
On 5.3, YaST will occasionally recognize the config floppy IF it already has a config file saved on it. It NEVER asks whether I want to use a floppy to save a config file, and always writes my custom config file to the hard disk, which is useless.
Why not just copy it from the HD to the floppy? At least till yast get's fixed, won't that work? Len
I think this is really the biggest bug in 5.3 (so far). The hard disk partitioning problem is bad, but this is worse if you have more than 1 system to maintain. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e