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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Nov 15 2001 - 21:00:20 EST