I've taken the liberty of forwarding this solution to the two bug reports
(48866 and 53808) that seem to concern this same time zone problem (in
potato). The solution Michael gives is different from the one proposed in
earlier discussion of these bugs. The earlier solutions either did not fix
the
Bart Szyszka [EMAIL PROTECTED] wrote:
> Hi,
>
> I think this is a glitch with Debian slink or something because this is
> completely insane. While installing Debian, it asks you about your
> hardware clock being set to GMT or local. The question asks if it's
> OK to set the clock to GMT. The last
> This is a known bug in the current potato boot-floppies. I and others have
> reported it. It seems to be a little harder than expected to stamp it out.
Hmm... I haven't used any potato boot-floppies, though. I installed
slink by putting in an slink Rescue disk and then having it get the rest fr
This is a known bug in the current potato boot-floppies. I and others have
reported it. It seems to be a little harder than expected to stamp it out.
Potato is still bleeding edge..
> I think this is a glitch with Debian slink or something because this is
> completely insane.
Some thing I forgot to mention is that I install Debian slink, but then
upgrade to potato. After the whole process of installing and then upgrading
is finished, I have been getting the time difference g
Hi,
I think this is a glitch with Debian slink or something because this is
completely insane. While installing Debian, it asks you about your
hardware clock being set to GMT or local. The question asks if it's
OK to set the clock to GMT. The last time I did this I picked 'No' for
absolutely sure
6 matches
Mail list logo
