Hi,
the rtcwake command accepts a time without a date as an argument to --date,
interprets it as meaning "today", then complains that the RTC doesn't go
backwards. The string "tomorrow" can only stand alone and means midnight.
This makes it difficult to specify "tomorrow 9:00" without date calculation
code, like rtcwake -t `date +%s -d "tomorrow 9:00"`.
Since it is clear that the desired time cannot be in the past, it would be
nice to interpret a time without a date as either today or tomorrow,
similar to how at(1) handles it.
Simon