> I'm almost always on some network, so I use NTP to always get the
> correct time.
I'm never on any network. My only access to InterNet is indirect, by
using a VT100 emulator to dial into Unix shell ISP account, then
running Unix software that use the net from there. So our circumstances
are different and accordingly our optimum solutions are different. With
NTP it makes sense to keep nudging the local clock to agree with NTP.
Without NTP, any adjustment must be done manually, and mistakes can be
Quote:> Sudden changes to the system time can confuse programs using it for
> timing purposes, and also programs which, like make, made decisions
> based on file timestamps. Nothing really bad usually happens.
So I guess the warning in the man page was slightly too "chicken little".
By the way, ever since I started fiddling with the system date I've
been having strange problems with the internal modem. The first time I
set the date back from 7-hours-in-future to correct-time, and then
tried to use the modem, minicom refused to dial any number because it
said it was already online. When I rebooted the system, which set the
system date 7 hours forward again (because I hadn't yet gotten the info
about hwclock), the modem was back to working again. So at that point,
using the modem was incompatible with having the system date correct.
Later I discovered that if I start minicom, and then set the system
date back while minicom is still running, then minicom works correctly
that time and later after I exit it and restart it. But of course each
time I rebooted the system (before I knew about hwclock) I would need
to get into minicom first then set the system clock back, which made
the whole process too much work. I think that's why I posted the
question about how to set the hardware clock.
So after you posted the info about setting the hardware clock, and I
tried it, I've been getting occasional weird problems with the modem. I
don't remember the details prior o last night, because last night was a
super big problem that masks all memories of earlier problems: I
searched Google to find a server for linux that was free and provided
both http and cgi service. I found one that looked promising, "small
footprint", less than one megabyte, called abyss. So I downloaded it to
Unix shell, uuencoded, and started downloading that across modem to
laptop, but at end of download the character encoding used by the modem
was trashed. I managed to get the modem working again by restarting
Linux, and downloaded again, this time it worked without trashing.
Comparing old and new files, I discovered about a third of the way into
the file it had already started trashing data the first time. So anyway
I uudecoded the second download, unzipped it, and looked at the
installation instructions: It requires glibc, which I don't have, so I
went back online to look for that, found it, but it's 20 megabytes!!
Downloading to my Unix shell account and uuencoding it (for download to
laptop) put my shell account over allocation so I needed to delete some
obsolete files to make room, done, then I started downloading the 20
megabytes to laptop, about an hour or so into the download, late at
night after I should have been in bed already, I got worried that I
might have forgotten to set minicom into saving transcript, so I
pressed a key to suspend the download and discovered the modem was
already trashing data., so it's a good thing I stopped it although not
for the reason I had originally. I was indeed saving a transcript, but
of trash. I tried to get the modem back to working, even rebooted
Linux, and it just wouldn't get working again. I went to bed.
This morning I resumed efforts to get modem working, all without
success. Sometimes when I start minicom, the DC Hayes initialization
commands it shows me are all trashed, unrecognizable text. When I try
to dial a number it does nothing, or it dials many more digits than it
should and gives a telephone-company response that I don't need a '1'
before dialing that number. I tried re-starting Linux, but then minicom
would show no initialization commands whatsoever, and it would say the
modem is already online whenever I tried to dial a number. I tried
shutting down Linux, letting it sit with no power for several minutes,
then restarting it, hoping the modem would reset to a reasonable state
without power. That changed the behaviour, but still didn't fix it.
I've been unable to get minicom to work with the modem ever since that
attempt to download glibc last night. Do you have any ideas how to get
the modem working again? Does the modem have its own internal clock
which is 7 hours advanced from correct, and now because the system
clock and hardware clock are both correct the modem clock disagrees and
causes the modem to stop working correctly? Please give me some
suggestion how to get that modem working again, because I'll need it
working this weekend to upload my completed homework assignment from my
laptop to send to my instructor. Currently it's in that state where
there's no init DC Hayes commands at all shown, and it says it's
In case it makes any difference: minicom 1.82.1
Compiled on Jul 30, 1999, 15:59:04