From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] alarm handling and suspended machines From: F.J.Ballesteros MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20010613141927.496DF199E3@mail.cse.psu.edu> Date: Wed, 13 Jun 2001 16:29:36 +0200 Topicbox-Message-UUID: b80065b0-eac9-11e9-9e20-41e7f4b1d025 Perhaps this is a stupid idea, but what could be done is to let each driver than can (rtc, cicle counter, ntp, whatever) implement a #X/time file. Then it would be a matter of binding them in the right order to let the user choose. Regarding how to recover tod after suspends, if one of those drivers knows that it will loose the time after a suspend, it could read the time from another #X/time file to recover. What I dislike about this is that time files would need to be provided by different drivers. What I like is that the user could test -e '#1/time' && bind -b '#1/time' /dev/time test -e '#2/time' && bind -b '#2/time' /dev/time and the #X/time implementation itself could try also to step through a set of preferred time recover sources in very much the same way. Nevertheless, I'm not a time guru and this idea could be just a nonsense.