a) its not setting it to creation but to last mount time it circumvent the clock being reset on every boot b) how would i know the creation time c) its a messy workaround for an upstream bug ted will hopefully fix upstream in fsck, we can only set the clock to rubbish anyway, does it matter in any way *which* rubbish it is d) i really prefer that stamp we set it to moves with the mount time here, instead of having a hard stamp you set it back to on every boot. else your file timestamps might get messy far in teh future if your system is temporary on the network (which automatically syncs the hwclock)
-- Ignoring a broken clock results in infinite reboots; not ignoring results in fsck failure; no solution to this problem https://bugs.launchpad.net/bugs/563618 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
