On Monday 30 August 2004 07:29 am, Carlos E. R. wrote:
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.
Thanks for the pointer. Sometimes I find the problem with Linux is too much documentation. Often I don't even know where to start looking or how to define a search. The kernel I need to run is patched for win4lin. Neither myself or the folks at win4lin knew why smbfs wasn't setting up my etc/samba/smbfstab mounts correctly. All I figured out is I could retsart smbfs after booting and it worked. Therefore the move from the default position to the the last postion. I have no idea what really needs to go in the # Required-Start: line in smbfs script though I guess I could put what ever was loading last so smbfs would start after that. Anyway, making a link to smbfs with another name was a simple solution that I understood and that got the job done with no ill effects (that I have found so far). Thanks again for the pointer. The best threads are those that solve the problem *and* point to further documentation to help you understand why you push the butttons that were suggested to be pushed. One without the other is of some help, but both together are great! Doug