LoadingReadyRun: Installation Anxiety 2010
- Thread starter Graham_LRR
- Start date
Recommended Videos
Yearly special needs to be done. Also, remakes are ok, i guess, but we really do need some Phailhaus again as opposed to reshooting old videos.
After unskippable was added here I went back and watched as many as I could. But for some reason a lot of the older ones come up with error messages and I can't watch them.Moon_Called said:
Yeah, it does that for some of the videos, but for the majority, it shouldn't.Eric the Orange said:
Sometimes, there's the option to watch the video in a different format - ie Quicktime, etc. Sometimes that helps.
I never saw the original, so this was fresh -- and funny -- for me.
Although, Paul: If installing the heart and lung drivers were all that was needed to get Graham back on his feet, then I have serious questions about the quality of the drivers you're using, as they appear to be implementing policy.
As you know, drivers are only supposed to provide mechanism, not policy. Heart rate and volume, breathing rate and volume, those are highly dependent on whatever activity is taking place, not to mention the platform on which they're running, details that the kernel doesn't -- and in most cases shouldn't -- know. Policy is supposed to be provided by user-space, often by running daemons.
It's possible that heartd and breathed noticed new heart and lung devices coming online via dbus events and applied policy immediately, but that begs the question why /etc/heartd.conf and /etc/breathed.conf weren't setup to modprobe the drivers on startup.
On the other hand, if heartd or breathed aren't running, and Graham is just running with the driver defaults, then don't let him do anything at all strenuous, or he could easily pass out.
Although, Paul: If installing the heart and lung drivers were all that was needed to get Graham back on his feet, then I have serious questions about the quality of the drivers you're using, as they appear to be implementing policy.
As you know, drivers are only supposed to provide mechanism, not policy. Heart rate and volume, breathing rate and volume, those are highly dependent on whatever activity is taking place, not to mention the platform on which they're running, details that the kernel doesn't -- and in most cases shouldn't -- know. Policy is supposed to be provided by user-space, often by running daemons.
It's possible that heartd and breathed noticed new heart and lung devices coming online via dbus events and applied policy immediately, but that begs the question why /etc/heartd.conf and /etc/breathed.conf weren't setup to modprobe the drivers on startup.
On the other hand, if heartd or breathed aren't running, and Graham is just running with the driver defaults, then don't let him do anything at all strenuous, or he could easily pass out.
Oh, and BTW, in the final scene, the cameraman's reflection is visible in the glass of the left-hand picture on the wall.
