linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Riley Williams <rhw@MemAlpha.cx>
To: Pavel Machek <pavel@suse.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Linux updates RTC secretly when clock synchronizes
Date: Thu, 8 Nov 2001 23:00:20 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0111082252500.14996-100000@Consulate.UFP.CX> (raw)
In-Reply-To: <20011108132639.A14160@atrey.karlin.mff.cuni.cz>

Hi Pavel.

>>>> least as KERN_DEBUG if not as KERN_NOTICE) whenever the RTC is
>>>> written to. It's too important a subsystem to be left hidden like
>>>> it currently is.

>>> This can be as well done in userland, enforced by whoever does rtc
>>> writes, no?

>> If some idiot writes a hwclock replacement that doesn't do logging...

> Then it is *his* problem. That's no excuse for putting it into kernel.

So you believe viruses are a good thing to have? Sorry, I have to
disagree with you.

Take the position of a sysadmin who can't understand why the system
clock on his computer keeps getting randomly changed under Linux, and
has verified using another operating system that it isn't a hardware
problem, then ask yourself what said sysadmin would expect from the
kernel to help him/her track the problem down. Would said sysadmin
prefer to be told...

 1. "Look in the system log - you'll get a message every time any
    program writes to the RTC."

 2. "Sorry, you'll have to go through every piece of software on
    your system and find the one that's updating the system clock
    that shouldn't be."

According to your comments, you prefer (2). I most definitely prefer (1).

Best wishes from Riley.


  reply	other threads:[~2001-11-08 23:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-31  0:33 PROBLEM: Linux updates RTC secretly when clock synchronizes Ian Maclaine-cross
2001-10-31  1:05 ` Kurt Roeckx
2001-10-31  2:55   ` Ian Maclaine-cross
2001-10-31 11:52     ` Kurt Roeckx
2001-11-01  0:52       ` Riley Williams
2001-11-01  1:26         ` Kurt Roeckx
2001-11-01 13:57         ` Alex Bligh - linux-kernel
2001-11-02  9:50           ` Riley Williams
2001-11-03 11:41             ` Alex Bligh - linux-kernel
2001-11-03 18:35               ` Riley Williams
2001-11-03 19:19                 ` Alex Bligh - linux-kernel
2001-11-03 21:04                 ` Kurt Roeckx
2001-11-06 10:01                 ` Pavel Machek
2001-11-06  9:57             ` Pavel Machek
2001-11-02 12:16 ` Pavel Machek
2001-11-05 23:08   ` Riley Williams
2001-11-06 10:17     ` Pavel Machek
2001-11-07  0:00       ` Riley Williams
2001-11-07  0:44         ` Alex Bligh - linux-kernel
2001-11-07  1:01           ` Kurt Roeckx
2001-11-07  1:15             ` Alex Bligh - linux-kernel
2001-11-07  9:24             ` Russell King
2001-11-08 12:26         ` Pavel Machek
2001-11-08 23:00           ` Riley Williams [this message]
2001-11-09  9:32             ` Pavel Machek
2001-11-09 21:11               ` Riley Williams
2001-11-09 21:30                 ` Pavel Machek
2001-11-09 22:54                   ` Riley Williams
2001-11-09 23:10                     ` Mark Zealey
2001-11-10 20:04                     ` Pavel Machek
2001-11-10 20:35                       ` Riley Williams
2001-11-10 20:43                         ` Pavel Machek
2001-11-10 20:49                         ` Doug McNaught
2001-11-06  0:20   ` Ian Maclaine-cross
2001-11-06 10:18     ` Pavel Machek
2001-11-08  5:09       ` Ian Maclaine-cross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.21.0111082252500.14996-100000@Consulate.UFP.CX \
    --to=rhw@memalpha.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).