Ralph Shumaker wrote:
Marieke Thayer wrote:
Marieke Thayer wrote:
Hi,
I have a TS-7200 board that boots into a Debian root file system on
Compact Flash. I do not have a real time clock, so I need to get the
time. After I boot into Debian 2.4.26 , I have to bring up the
network, before I can get the time using the following commands.
ifup eth0
ntpdate -u 131.187.13.100 #microsofts NTP server
OK. I found a reference to /etc/localtime, so I set it up to point to
the Los_ Angeles time zone file. I see the file for setting up ntp,
but it isn't going to do anything until I am connected to the net (ie
eth0 is up). Therefore, I now think that my first goal should be to
get eth0 started at boot time. I have an /etc/network/interfaces file
with the appropriate adresses. This file seems to be accessed when I
type "ifup eth0", but not in the boot process. Clues about what to
try to modify would help. Should I modify my Redboot script or
something else.
Cheers,
Marieke
I'm far from knowledgeable in such things, but I would think that
/etc/rc* would be a decent place to start. Perhaps "man init".
You are right. That is a good place to start. In the absence of an
answer I kept plugging away, but I had no idea that typing "man init"
might be constructive. I will have to remember that in the future. I
spent some time on the web a while back because Ubuntu's lack of an
inittab file confused me. It still does a little bit. Fortunately my
board does have an inittab file to tell me what the boot process will do.
I fixed the parameters in Redboot to get my network up. I no longer see
totally wrong ip_addresses going by in the boot process now too. eth0
now comes up when I boot. Yeah!
After I did that I looked at the ntpdate files, especially the one in
/etc/init.d . It runs differently than if you just type "ntpdate -u
ip_address". "/etc/init.d/ntpdate start|restart" seem to work quite
nicely. Just before I read this, I found that in /etc/rcS.d I have
pointers to hwclockfirst.sh and hwclock.sh but no pointer to ntpdate .
So my system is set up to get its date from the non-existent hardware
clock. Now I have to figure out what number to give ntpdate and find the
courage to actually modify my init process. Should it be S18 like
hwclockfirst.sh or S50 like hwclock.sh . Probably the latter because,
networking is S40.
BTW /etc/init.d/rcS will add the start as $1 for the links that aren't
*.sh, so I should just have to put the link in the rcS directory.
Cheers,
Marieke
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
