Hi!
> > > ...should they be changed to 200? Or perhaps file should be readable?
>
> No, mode 644 is fine. No reason to prevent "other" people from
> reading the alarm time (is there?) and if you write a legal value,
> that will work. So $SUBJECT is no problem at all.
Yep, agreed. I was confused by fact that it does not give invalid
values back.
> > > [EMAIL PROTECTED]:/sys/class/rtc/rtc0# cat wakealarm
> > > [EMAIL PROTECTED]:/sys/class/rtc/rtc0# echo 132719 > wakealarm
>
> At which point I'd expect
>
> # echo $?
>
> would indicate the write failed. That's a LONG time in the
> past (January 2, 1970), so that setting would be rejected.
echo $? says 0 here :-(.
> > > [EMAIL PROTECTED]:/sys/class/rtc/rtc0#
> > >
> > > ...standard PC with reasonably recent kernel...
>
> Yeah, well a "standard PC" is chock full of fairly bizarrely
> glitchey hardware. Clocks and timers have more than their
> fair share, or x86_64 NOHZ support would be merged by now!
:-). Ok. Thinkpad x60.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
