The Sunday 2004-08-29 at 22:35 -0500, Doug B wrote:
Seems like I had trouble making these changes stick if I went back to yast to configure something. What I ended up doing was making a symlink with a new name. In my case, yast started smbfs at 08 (S08smbfs). In one of the kernels I boot, that postion didn't work for some reason. I changed it to S21smbfs and it work fine. Problem was any time I used yast run level editor, it set it back to S08smbfs. I finanlly made a symlink called S21my_smbfs. No problems any more.
May not be the cleanest solution, but it's working so far.
It is certainly not the suse way, yast and/or suseconfig will alter such manual links. It is documented why. Read the chapter "The SuSE boot concept" in the administration book, and the answer other people gave on this thread. -- Cheers, Carlos Robinson