When I startup Puppy, rc.update executes a few lines of code, viz:
Code: Select all
#must keep rc.packages pristine...
cp -f $SOURCEROOT/.etc/rc.d/rc.packages $DESTROOT/.etc/rc.d/rc.packages
#rc.sysinit always pristine, but overwrite this anyway...
cp -f $SOURCEROOT/.etc/rc.d/rc.sysinit $DESTROOT/.etc/rc.d/rc.sysinit
cp -f $SOURCEROOT/.etc/rc.d/rc.sysinit-cd $DESTROOT/.etc/rc.d/rc.sysinit-cd
cp -f $SOURCEROOT/.etc/rc.d/rc.sysinit-hd $DESTROOT/.etc/rc.d/rc.sysinit-hd
[...]
# always update...
rm -rf $DESTROOT/puppy-reference
cp -a $SOURCEROOT/puppy-reference $DESTROOT/After I did the upgrade to 1.0.5, one o fthe first things I did was to update the timezone and check the date/time. My current /etc/TZ file contains the string 'PUP-10' (as I'm in eastern Australia). I couldn't find any further reference to time zone information in the /etc/rc.d files.
...but have a look at the timestamps on these files for a boot that took place at 10:16pm local time (see file 1016.jpg)... ...and another boot at 10:19pm local time (see file 1019.jpg)
I only found out about this as one of my scripts that extracts data from a backup reported some strange messages. For example, a backup that was done at 10:33pm local time has some dodgy timestamps:
Code: Select all
Re-build /mnt/home/pupbac_105_10042233.tgz into /mnt/home/pupbld_105_10042233 ...
tar: ./.etc/modules.conf: time stamp 2005-10-05 08:18:30 is 35093 s in the future
tar: ./.etc/ramdiskfssize: time stamp 2005-10-05 08:18:30 is 35093 s in the future
tar: ./.etc/ramdisksize: time stamp 2005-10-05 08:18:30 is 35093 s in the future
tar: ./.etc/rc.d/rc.sysinit: time stamp 2005-10-05 08:18:30 is 35093 s in the future
tar: ./.etc/rc.d/rc.modules: time stamp 2005-10-05 08:18:30 is 35093 s in the future
tar: ./.etc/rc.d/rc.packages: time stamp 2005-10-05 08:18:30 is 35093 s in the future
tar: ./.etc/rc.d/rc.reboot: time stamp 2005-10-05 08:18:30 is 35093 s in the futureJust reporting the problems...
