Hi!
> > That seems as very wrong solution.
>
> > What about just making kernel only _read_ system clock, and never
> > set it? That looks way cleaner to me.
>
> It is cleaner. However, I feel that the RTC code should printk (at 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?
[I poropose kernel not to do any writes, so it is only userland
left. And having printk() in kernel or syslog() in hwclock seems
pretty much equivalent, with later prefered as it magically works on
older kernels.]
-- Casualities in World Trade Center: 6453 dead inside the building, cryptography in U.S.A. and free speech in Czech Republic. - 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 : Wed Nov 07 2001 - 21:00:29 EST