Tiny Core Base > piCore Test Releases

piCore-7.0rc2

<< < (2/6) > >>

bmarkus:
Paul,

thanks. It looks OK, I will add settle in next release.

Béla

Paul_123:

--- Quote from: bmarkus on December 29, 2015, 02:16:55 PM ---Paul,

thanks. It looks OK, I will add settle in next release.

Béla

--- End quote ---

I tested removing the "&" from the trigger line....works just the same.  but does appear to be slightly slower. 

While your in there, take a look at the nofstab command line option.....note the location of 98-tc.rules   The last update broke the intention of the nofstab command line switch.

bmarkus:
Thanks, fixed in rc3

Paul_123:
These rpi2's execute commands so fast, I've ran into another problem.

The hostname is set in bootsync.sh,  the hostname is not getting set before udhcpc runs on the eth0 interface.  So the device is just showing up on my router as "box" instead of its proper name.

This is the end of tc-config

--- Code: ---# After restore items
if [ -n "$NODHCP" ]; then
        echo "${GREEN}Skipping DHCP broadcast/network detection as requested on boot commandline.${NORMAL}"
else
        [ -z "$DHCP_RAN" ] && /etc/init.d/dhcp.sh &
        [ -z "$NORTC" ] || /etc/init.d/settime.sh &
fi

[ -n "$CRON" ] && /etc/init.d/services/crond start

/sbin/loadcpufreq 2>/dev/null &

/opt/bootsync.sh

--- End code ---

Since the restore is already done, do we move bootsync to happen first.   Or do we just put a small trap in dhcp.sh to make sure it waits for bootsync to run before running udhcpc......

jgrulich:
It's enough to execute the hostname set before the udhcp, not need to run whole bootsync.sh. Otherwise the bootsync.sh need to be run separately from bootlocal.sh to be sure that bootlocal.sh is run after udhcp is executed when whole boot process is finished. In my case i make a lot of different operations with the network in the bootlocal.sh.

Navigation

[0] Message Index

[#] Next page

[*] Previous page