On Fri, 8 Aug 2003 08:29:05 +0200 (CEST),
Mark Wormgoor <mark@...> wrote in message
> > On Thu, 07 Aug 2003 20:31:54 +0100,
> > Eric Oberlander <eric@...> wrote in message
> > <BB5867B9.520D%eric@...>:
> > ..another time thing; on installing ipcop, the hardware clock is
> > either at some local time zone like in wintendo, or the way RMS,
> > ESR, Alan, Linus, God and I the Guru of Firegods meant it to be,
> > set to UTC aka GMT, and having the system time in local time.
> > ..not possible in snotty ipcop. It _should_ be in 1.3.1alpha5.
> What's the point? The only reason it is configurable is because you
> may have some other OS on your machine.
..the point is it handles it wrongly, and throws the time 4 hours off,
and this makes my ipcop box useless as a test platform and a time
server for my external users.
..I only need this on installing or "backing up",
and I don't need no fancy web interface for it.
> Well, IPCop doesn't work with another OS at the moment.
..how about _ipcop_ alpha testing? It _is_ desireable? I have 2
1.7 GB disks on it, and until we have decent non-floppy backup's
in place, I don't do much testing, because I simply cannot afford
the down time. And I also like to use the box to check out other
firewalls with 802.11 nic support, which we don't _yet_ support.
..2 times 2 minutes in a quiet night is workable, but _not_ 2x15.
> We only use the hw clock to temporarily store the time
> when the machine is down.
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.