I'm a little over my head on this bootup question. I have a laptop which is hooked to my main server (suse1) through its only PCMCIA slot. It gets its address from a Linksys firewall/cable modem thing (they call it a router, but it doesn't do IP forwarding). Things there are going fine. I have a problem when accessing the server with NFS. Putting the proper entries in fstab (actually, letting yast do it) creates a "can't get out" portmap error. Commenting these lines out and adding them after booting through a little script mounts them just fine. I'm wondering if the boot sequence is running portmap too soon. I'm guessing, but I believe /etc/init.d/rc5.d/ has these links (i.e., @K12portmap) in order to be run one right after the other in sequence. If so, @K14pcmcia runs after portmap, which would create that error. Am I thinking this through wrong? -- "I'd love to go out with you, but I'm taking punk totem pole carving."
Tim Hanson
I'm wondering if the boot sequence is running portmap too soon. I'm guessing, but I believe /etc/init.d/rc5.d/ has these links (i.e., @K12portmap) in order to be run one right after the other in sequence. If so, @K14pcmcia runs after portmap, which would create that error. Am I thinking this through wrong?
The K* symlinks aren't the interesting ones as those are for *stopping* a service. What you need to look at are the S* symlinks. pcmcia is killed after portmap, but it is started before portmap. Philipp
participants (2)
-
Philipp Thomas
-
Tim Hanson