Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: mbertrand on August 26, 2013, 01:09:12 PM
-
When we use the Network configuration gui in Tiny Core it always appends "/opt/eth0.sh &" to the end of "bootlocal.sh".
I was wondering why because I just realized that I have vsftp ,appache, telnetd and openssh all starting before the nic is configured. Could this be a problem? Because I started noticing some intermittent problems related to networking.
-
Move "/opt/eth0.sh &" to the top of bootlocal.sh.
Follow it with:
SEC=60
while [ $SEC -gt 0 ] ; do
ifconfig | grep -q "Bcast" && break || sleep 1
echo -ne "Waiting for IP $((SEC--)) \r"
done
echo
-
Yes but here where I work we are putting TC on many industrial computer so we usually make an image of one when all is setup and then dd the image to the next one but here's the catch, we then may need to change the IP address. After doing that the line for 'eth0.sh' is back at the bottom. I know, don't use the 'Network' from control panel. But sometimes we need to make customer change it and asking them to edit a file and then do backup is not acceptable. Just out of curiosity if I was to move that line could I not move it to the beginning of bootsync.sh this would eliminate the need for a loop? Also, I have openssh, vstfpd in bootsync.sh. Is this bad? Does the network card need to be properly configured before these servers start?
-
Hi mbertrand
How about moving the loop and server start up commands to /home/tc/X.d. Anything in that directory runs after
bootlocal and bootsync.
-
I'm sorry I'm leading everyone on a goose hunt! I'll be more clear. I know this is a Linux specific question but this seems like the best place to ask. Does the network card need to be configured before any services that depend on it are started. I'm sure many TC users must have some sort of service requiring tcp and that these deamons start before card is configured (eth0.sh is executed).
-
I gave you the code to wait for the card to become active. Use it.
-
Ok thanks