Hi,

I've noticed during boot time that the dhcp client is requesting an IP address before the PCMCIA services are loaded. In turn, it fails to give my PCMCIA nic an IP address and I have to manually run dhcpcd to get one. In the past, I got around that by assigning a static IP to my nic. This time I would like to be able to use DHCP so that I can hook up my laptop at home and at work.

I went thru files in /etc and noticed that the DHCP client and PCMCIA stuff is located in two different rc files.

Is there a way to alter the order of those boot events? Possibly to run PCMCIA stuff before the DHCP client stuff.

Thanks,
Hector

if you don't have a ultra-dock for your thinkpad
and never run it in any of those with a PCI-NIC
just rename your rc.inet1 ...


Cheers,
Tink

rc.inet1 to rc.inet?

Thanks,
Hector

In Slack 8.1 the rc.pcmcia start command is located in the rc.M script right BEFORE the network services are started (rc.inet1/rc.inet2). It does inlcude a note that sometime prior PCMCIA services were started in rc.S but it did not note when the change was made. But from what I can determine from my available servers, it was in rc.S on Slack 7.1 and Slack 8.0. The note indicates it was moved to the rc.M script because of pid file issues. So if you desired, remark the startup entries from the rc.S script and include them in the rc.M script, just prior to the rc.inet1/2 entries. Then configure your networking for dhcpcd operation. Use netconfig or config the rc.inet1 script manually.

Good luck.

Thanks guys.

This is what I had already done before your reply, Excalibur.

Details:

/etc/rc.d/rc.M is the startup script that has the lines to call up the network scripts

/etc/rc.d/rc.S is the startup script that has the original PCMCIA startup lines.

/etc/rc.d/rc.M is parsed/executed before /etc/rc.d/rc.S, so I watched the lines that scroll by during the boot process closely to figure out the order of events.

That led me to the /etc/rc.d/rc.inet1 and /etc/rc.d/rc.inet2 files which are called from /etc/rc.d/rc.M way before the PCMCIA script.

So... I placed the following lines from /etc/rc.d/rc.S immediately before the script lines that call the rc.inet files:

if [ -x /etc/rc.d/rc.pcmcia ] ; then
. /etc/rc.d/rc.pcmcia start
fi

Then I placed hash marks in front of the lines in the original file.

Now, the PCMCIA card services are started before the DHCP client starts, which makes the network card ready to accept the IP address.

Great minds think alike, but at different times!

Thanks,
Hector