... and as we've discovered, too many people, including embedded hardware manufacturers (which Canonical seems to care about) don't seem to care about relible clocks, and apparently virtualization managers can't be bothered to deal with mapping the time zone correctly before setting up the real-time clock in the guest OS.... and instead of filing bugs against the hardware manufactures and the virtualization managers, they get filed against the file system.
I've essentially despaired at this point that we can get people to care about setting time and time zones correctly with Linux. :-( In fact, Scott has basically argued successfully that we need a "clock totally broken" option to e2fsck. :-( :-( :-( -- lazy_itable_init not on by default https://bugs.launchpad.net/bugs/556621 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
