On Sunday 28 November 2004 11:38, Dirk Meyer wrote:
> So we need extra functions for stop/resume in the plugins. I guess
> there are more plugins with that problem.
Maybe the suspend methods should return a boolean whether the hibernation
should be cancelled. (Cf. the excellent hibernate-script; it will for
example detect that some module could not be unloaded and cancel the process,
unless --force has been given. This means that I can press the suspend
button while watching TV, and nothing bad will happen - actually, NOTHING
will happen.. ;-) )
> > One difficult
> > step ist again that nvram-wakeup might need another bootup cycle for
> > proper automatic wakeup before the next recording. :-(
>
> Great. I was also playing with it yesterday. For cvs (I'm using cvs
> for daily use now)
Oh - I tried CVS HEAD now, but nothing would work. Actually, I think I should
add another user and try to configure HEAD from scratch, but there is little
documentation on that except for the occasional posts on this list, right?
(My Freevo came up after removing the VideoGroups from local_conf.py, but I
could only choose TV or shutdown, and only the latter worked.. ;-) )
> the logic must be inside the recordserver. The
> recordserver knows the schedule and can set the wakup timer.
Right. I was planning the same actually. This has another big advantage
compared with my current approach: Shutting down the system by calling "halt"
externally does not leave the system unprogrammed. There are two cases:
- nvram-wakup can completely program the BIOS. In this case, we're done.
- or, a reboot is needed for the BIOS to complete the programming. We cannot
ensure that this reboot really happens, but I already wrote this
rebootflag-helper which should be integrated into the boot sequence to
shutdown after the reboot. I want to re-use this rebootflag-file for marking
the BIOS as dirty as soon as e.g. the recordserver called nvram-wakeup for
programming*. This flagfile is then checked on shutdown to turn this into a
reboot (or to add a suspend-resume cycle before the real final hibernate),
and deleted after the reboot.
> But when do we shutdown the system?
See my mail from 2004-11-14: "I planned to check on Freevo startup whether the
computer boot-up happend in a sane range (depending on config settings)
before the next recording, assuming that it's the programmed start."
I.e. I read the system's uptime, check whether the power-on happened within 60
seconds of (scheduled_recording.start - config.TV_RECORD_PADDING -
config.BOOTTIME_PADDING). (Which is the formula I use for calling
nvram-wakeup.) In this case, I directly go into a "Computer will shutdown
after the recording" screen (which eventually says when the recording will
begin/finish), which has a "Cancel" option.
After implementing this screen, it can be integrated into the shutdown option,
so that one can manually tell the computer to shutdown after a running /
soon-to-begin recording.
> I don't use hibernate and my freevo pc is
> also for working. When I'm not home and the pc starts it can
> record. Than the recordserver sets the new wakeup time. But can it
> shutdown?
See above, I thought about letting Freevo do the shutdown itself, not the
recordserver. I am open for better ideas though.
--
Ciao, / / .o.
/--/ ..o
/ / ANS ooo
*: BTW, nvram-wakeup signals through it's exitcode that a reboot is necessary
on programming, but there is no native way of checking whether a reboot is
necessary afterwards. I.e. no
"nvram-wakeup --check-dirtyness-of-current-bios-state"
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
