On 27/1/2000 Joel Klecker wrote:
AFAIK, Mac OS *does* keep the clock in UTC. Perhaps only since 8.x though.
I have my Debian GNU/Linux PowerPC system set to use UTC and Mac OS is
never confused about the clock, so it must grok UTC.
This is certainly not what i have found, I use macos 8.6, no m
Hmmm... I have to look into this further! That's what I thought too when I
installed Debian on my PowerMac, so I set the clock to UTC... But then
I noticed time was set 8 hours in the past (I'm in the Western US),
so I assumed MacOS kept the clok in local time. Maybe something in the
Date&Time Con
At 01:27 -0800 2000-01-27, Renaud Dreyer wrote:
>As for your 8 hours drift, it might be because you set up Debian to think
>the hardware clock was UTC, not local time. What does /etc/default/rcS
>say? If you're going to double-boot with Mac OS, you need to tell
>Debian the hardware clock is set to
On Thu, Jan 27, 2000, Ethan Benson <[EMAIL PROTECTED]> wrote:
>seriously though i was having all kinds of wacky trouble with the
>clock under linux until i set the hardware clock to GMT and
>configured linux accordingly..
>
>the only thing I am using macos for at the moment is mail which will
On 27/1/2000 Renaud Dreyer wrote:
As for your 8 hours drift, it might be because you set up Debian to think
the hardware clock was UTC, not local time. What does /etc/default/rcS
say? If you're going to double-boot with Mac OS, you need to tell
Debian the hardware clock is set to local time. Unl
On 27/1/2000 C.M. Connelly wrote:
I did notice an eight hour clock skew the last time I spent any
significant time in MacOS before coming back to Linux
(``coincidentally'', I'm in the Pacific Time Zone, eight hours
behind GMT). I can't recall now if I made a permanent fix to that
problem or if
>
> Renaud,
>
> I had that problem, too. (*Exactly* that problem.) It turned out
> that my housemate had written a script (in /etc/rc.boot) to set
> the clock properly back when we first installed the system (when
> hwclock was completely broken on the PowerPC), and that script was
> no longer
Renaud,
I had that problem, too. (*Exactly* that problem.) It turned out
that my housemate had written a script (in /etc/rc.boot) to set
the clock properly back when we first installed the system (when
hwclock was completely broken on the PowerPC), and that script was
no longer working properly
I think I tracked down the reason why I keep getting the message:
/etc/modules.conf is more recent than /lib/modules/2.2.14/modules.dep
modprobe: insmod * failed
when booting. Before rebooting, I ran depmod -a to make sure that
/lib/modules/2.2.14/modules.dep was more recent than
/etc/modules.
9 matches
Mail list logo
