On Wed, Feb 11, 1998 at 07:09:19AM -0500, Steve Cohen stated:
This may have been asked a couple weeks ago, but I don't remember what the answer was. Anyway...
When I start linux, Yast seems to think that my install hasn't finished, starts up, decides that there is nothing to install, finishes, and then all the junk in rc.config gets loaded. I looked through the bootup scripts, and I see where it is starting up yast, and I am sure I can comment out the lines. But before I do:
1) Why does it think there are files to install?
2) Is there a good reason to leave it intact?
Steve Cohen
Same problem I had after upgrading to 5.1 from 5. YAST ran a few times claiming there were things left to be done but it would not do anything after installing. I then ran yast by itself after having the system up for awhile and I had a number of packages left to install to finish. I believe at this point some of the libs I compiled got messed up and links became broken. Anyhow, I ran yast after the system was up, it found the packages, installed them, and then I had to clean things up a bit. I would like to know why yast when run from the startup says there is nothing left to do but when it runs from a command line later on, it finds the packages to instal. -- --Michael Perry-- mperry@basin.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e