<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Freeze Push: e2fsprogs
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Freeze%20Push%3A%20e2fsprogs&In-Reply-To=%3C4FA28DF9.4040202%40mageia.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="015222.html">
<LINK REL="Next" HREF="015235.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Freeze Push: e2fsprogs</H1>
<B>Anssi Hannula</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Freeze%20Push%3A%20e2fsprogs&In-Reply-To=%3C4FA28DF9.4040202%40mageia.org%3E"
TITLE="[Mageia-dev] Freeze Push: e2fsprogs">anssi at mageia.org
</A><BR>
<I>Thu May 3 15:54:01 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="015222.html">[Mageia-dev] Freeze Push: e2fsprogs
</A></li>
<LI>Next message: <A HREF="015235.html">[Mageia-dev] Freeze Push: e2fsprogs
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#15233">[ date ]</a>
<a href="thread.html#15233">[ thread ]</a>
<a href="subject.html#15233">[ subject ]</a>
<a href="author.html#15233">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>03.05.2012 13:50, Colin Guthrie kirjoitti:
><i> 'Twas brillig, and zezinho at 03/05/12 11:33 did gyre and gimble:
</I>>><i> Em 03-05-2012 00:00, Colin Guthrie escreveu:
</I>>>><i> Ping? Any revised opinions?
</I>>>><i>
</I>>><i> Sorry, but I feel this is not needed for MGA2. In fact, systemd has
</I>>><i> changed the shutdown behaviour. The good patch would be to make him sync
</I>>><i> the hwclock at shutdown, as we have no bugs because of this sysvinit
</I>>><i> behaviour.
</I>><i>
</I>><i> There are real problems related to this as described upstream. Without a
</I>><i> proper ntp implementation doing the time sync we have *no* idea that
</I>><i> what we are doing is correct. If this is a dual boot system we could be
</I>><i> clobbering the RTC without any knowledge that what we are doing is
</I>><i> vaguely valid. So no, I will not entertain adding the sync hwclock stuff
</I>><i> back. That is broken.
</I>
I'm not sure I understand. Why wouldn't we have any idea if what we are
doing is correct? If the system time has been changed, surely RTC should
be changed as well?
You make it sound like there is some situation where system time could
be entirely wrong. Is there such a situation? I'm not seeing it right now.
I wonder if this change had something to do with the fact that my laptop
had some problems moving to DST (on cauldron), and I had to change the
time manually (IIRC it switched to DST first but then the change was
lost later)... but I guess that could've been something else.
--
Anssi Hannula
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="015222.html">[Mageia-dev] Freeze Push: e2fsprogs
</A></li>
<LI>Next message: <A HREF="015235.html">[Mageia-dev] Freeze Push: e2fsprogs
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#15233">[ date ]</a>
<a href="thread.html#15233">[ thread ]</a>
<a href="subject.html#15233">[ subject ]</a>
<a href="author.html#15233">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>