d_garbage wrote: > Hello list, > The 'repair' feature has helped me before and it would be good to have > it at hand, for when I (inevitably) bork my shiny new 10.3 install. > The original 'repair installation' option on the DVD was broken. Now > the yast module has been fixed, can you tell me how to get/make a > bootable 'repair installation' rescue disk to replace it? > Thanks, > David I'm going to caution *extreme* caution with the repair function, either on the boot (if you can make it run) or in Yast. It is very broken and if you happen to be lucky enough to get some of the pieces to work for you, more power to you, but I wouldn't trust my worst cold-war enemies computers to the repair module just yet. Parts do work, some give the illusion of working, any dealing with non-standard (read RAID or LVM or mixed hardware IDE-SATA) are apt to be horrifically broken. To be sure, I just documented (again) just the first 3 steps of the Yast2 repair on my MD raid installation. Only the first step completed. It detected all parttions correctly. From there on, if I had let it 'repair' things, I would have had no system left. (Yes, I've filed bug reports which are still open). For more conventional systems, you do have a fighting chance at success, but I think I would rather let a Orangutans control the repair efforts than the repair program right now. How this most important piece of programming was allowed to be put on the GOLD MASTER and distributed around the world as an example of SuSE's excellence, is beyond me. I love Linux and I support SuSE in every way I know how, but it is very frustrating to see this kind of end result. It isn't as if there weren't plenty of warnings during beta testing about the IDE-SATA breaking things, including the repair program, it is just that it wasn't taken seriously enough until after RC1 was released and GM was being sent for pressing...then it was too late. It just makes me ill to think that SuSE will be judged by Windows potential converts and find their Windows installation unbootable *and* an unbootable copy of SuSE with no way to fix it and without the skills to know how to 'work around' the bugs that should have *NEVER* been committed to vinyl.
My suggestion is that if your system needs repairing, do it the old fashioned way, use the utilities best suited for the job, such as fsck and the various editors and partitioners (including the one in Yast). Just don't use 'repair', just yet. Richard -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
