![](https://seccdn.libravatar.org/avatar/812d511e77404ae408a33e3baca37770.jpg?s=120&d=mm&r=g)
On Tuesday 14 August 2001 02:10, John Griffin wrote:
Jon,
Sounds like a great idea. Just curious if you have done this before or not?
Yeah I did it some time ago... prolly went rpm -Uvh yast.rpm or something (don't remember exactly) might've used --force and/or --nodeps too... Someone else should know :)
The reason I ask this is that there are 39 rpm files under the suse/yast1 directory structure on the server, of which NONE are labeled 'yast'. I checked out the INDEX.english file in the yast1 directory, and it only describes YaST2 rpm files.
Yeah, I'm looking at it now... Wonder why they call the directory yast1, as there is just yast2 rpms in there... *But* looking around I did find yast.rpm -in /suse/a1 ...which does make sense, as YaST is a 'basic component'. FYI this is also linked from /full-names/i386/yast-1.09-6.i386.rpm... As to whether or not to remove the already installed (broken) yast, before reinstalling: Can't say... Shouldn't be necessary, though somebody else might be more knowledgeable... Suggest trying just rpm -Uvh first, and then only start trying with --force (and maybe --nodeps) if that complains... man rpm, anyway, if you haven't already...
Just curious, before I re-install 39 rpm files.
Shouldn't ought to be necessary :)
Thanks for your help, John
My pleasure... (to actually be of help, for once) :) Let us know how you fare Jon Clausen