From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-May/015194.html | 192 ++++++++++++++++++++++++++++++++ 1 file changed, 192 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-May/015194.html (limited to 'zarb-ml/mageia-dev/2012-May/015194.html') diff --git a/zarb-ml/mageia-dev/2012-May/015194.html b/zarb-ml/mageia-dev/2012-May/015194.html new file mode 100644 index 000000000..d919d6573 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-May/015194.html @@ -0,0 +1,192 @@ + + + + [Mageia-dev] Freeze Push: e2fsprogs + + + + + + + + + +

[Mageia-dev] Freeze Push: e2fsprogs

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu May 3 00:00:47 CEST 2012 +

+
+ +
'Twas brillig, and Colin Guthrie at 27/04/12 16:32 did gyre and gimble:
+> 'Twas brillig, and Thierry Vignaud at 27/04/12 15:19 did gyre and gimble:
+>> On 27 April 2012 15:23, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>>> Hi,
+>>>
+>>> As per discussions earlier, can you please push e2fsprogs.
+>>
+>> Er there hasn't been much discussion!
+>>
+>>> It adds a default config to prevent fsck when system clock and hwclock
+>>> are out of sync.
+>>
+>> What's more, from what I remember from reading the e2fsprogs many years ago,
+>> that was added only for ubuntu installer where date setting was wrong,
+>> resulting in a date differenence on booting the newly installed system
+>> and thus forcing a fsck.
+>>
+>> This doesn't affect us since our installer forbid fsck based on too big
+>> elapsed time since last check.
+>>
+>> What's more it cannot happen "when system clock and hwclock
+>> are out of sync" for the same reason.
+>>
+>> As it doesn't fix any real bug, I suggests postponing this to mga3.
+> 
+> Well, it's does not directly related to a bug but it is in some way
+> related to:
+> https://bugs.mageia.org/show_bug.cgi?id=3817
+> 
+> As I mentioned in my original mail, as the hwclock is not clobbered on
+> shutdown with whatever random value we have in the system clock, we need
+> to be more tolerant of errors in time offsets.
+> 
+> If the user runs ntpd and doesn't drift too much then the RTC will be
+> sync'ed every 11 minutes by the kernel. If the drift is too high, or the
+> user does not run ntpd, then there will be no system clock to hwclock
+> sync as we simply don't have enough info to know we're correct.
+> 
+> This patch will avoid any fallout from this.
+> 
+> So I think it's likely still important to have in mga2.
+> 
+> Some more info:
+> http://article.gmane.org/gmane.comp.sysutils.systemd.devel/4943
+> 
+> Col
+
+
+Ping? Any revised opinions?
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1